Understanding Your Data Coverage
- Overview
- What Coverage Means
- Coverage & Data Quality: What's the Difference?
- Your Coverage Tier
- How Coverage Affects Jiro Features
- Important To Remember
- Related Articles
Overview
Coverage determines how much of your clinical activity is represented in Jiro's real-world data. Understanding your coverage tier enables you to interpret metrics reliably and engage with Jiro's features using appropriate clinical context. This reference explains how coverage is calculated, what your coverage tier signifies, and how it influences your experience across the platform.
You may see "coverage" referenced in other Jiro documents. Important distinction:
- Database Coverage: Jiro accesses approximately 60–70% of U.S. medical claims nationally through third-party providers and other data sources.
- Account Coverage: Varies by user. Account coverage is the amount of an individual's practice Jiro captures, based on your claims volume relative to your practice size.
This document focuses on your account coverage. For database coverage details, see the Data Sources page.
What Coverage Means
Coverage is the proportion of your total claims that Jiro captures, expressed as a ratio of claims on file to total estimated claims generated. Because your actual claims volume is not directly observable, coverage is approximated.
When coverage is high, Jiro's data closely reflects your clinical activity. When coverage is lower, the data represents a partial, directional view of your practice. Data refreshes monthly, so your coverage may change month-to-month based on your claims data availability.
Coverage vs. Data Quality: What's The Difference?
Data Quality measures whether the real-world data Jiro holds is complete and mature. It reflects delivery lag and the recency of data processing within Jiro's systems.
Coverage measures what percentage of your total clinical activity is present in Jiro's real-world data. It reflects how much of your patient panel and clinical volume Jiro can access.
A metric can have high data quality (the data Jiro holds is mature and complete) while also having low coverage (Jiro holds only a fraction of your total claims). Neither signal indicates inaccurate data, but rather the scope and completeness of what Jiro can measure.
You are able to filter your metric views by Data Quality. For more information, see Time and Refresh Cadence.
Your Coverage Tier
Jiro assigns your account to one of four coverage tiers based on the ratio of captured real-world data to your total estimated clinical volume. Your tier governs how your metrics and Jiro features behave. If you have questions about what tier you fall in, reach out to Jiro Support.
| Tier | What It Means | How Jiro Responds |
|---|---|---|
| No Data | No claims are on file for your NPI. Common for residents and physicians who have recently joined. | Specialty-level benchmarks and comparisons are available. Individualized metrics are not displayed. Discover and Consult remain accessible using non-personalized data. |
| Low | Claims data exists but represents a small portion of your estimated total volume. | Metrics and Discover cards draw on less specific data (specialty-level or location-level) rather than individual-level claims. |
| Medium | A meaningful portion of your claims is captured, but gaps remain. | Individualized Metrics and Discover cards are available, but metrics should be treated as a directional indicator of your practice. |
| High | Real-world data closely reflects your total clinical activity. | Fully individualized Metrics and Discover cards. |
How Coverage Affects Jiro Features
Your coverage tier determines how Jiro's features respond when surfacing personalized information. Different features handle incomplete or low-coverage using the same principle: specificity adjusts based on available data.
Practice - Spotlights
Spotlights will surface depending on the individual metrics you have data for.
Practice - Clinical Metrics
Each individual metric has its own calculation rules. Metric cards are displayed when you have sufficient data to form insights. “No data available” is displayed for metrics in which your coverage is too low to calculate a reliable insight.
Practice - Financial Metrics
Referral data often has naturally sparse coverage. Documented referral data is directional, relying on a “sending” and “receiving” party. Opportunities are still relevant, based on the location of your practice. Reimbursements pull from closed claims, which are subject to data lag. These will show similar coverage to your clinical metrics.
Research
Not affected by data coverage.
Consult
When coverage is low, Consult responses may include inline caveats indicating that personalized clinical context is derived from limited real-world data.
Discover
When your coverage is limited, these cards are individualized to you at the specialty or location level rather than individual practice level, maintaining relevance to your clinical context.
Important To Remember
- Coverage and data quality are distinct signals. Low coverage indicates that Jiro's view of your practice is partial, not that your data is inaccurate.
- Low coverage does not disable Jiro features. Jiro adjusts the specificity of personalization progressively rather than removing access.
- Coverage estimates are refined over time as additional real-world data is processed and as volume data is submitted.
- Pharmacy claims metrics use different coverage thresholds than medical claims metrics.
- Data refreshes monthly. Your coverage may improve as additional data is processed.
- Coverage is calculated on a per-NPI basis. If you practice across multiple locations or organizations, each NPI has its own coverage tier.