Understanding Your Data Coverage
- Overview
- What Coverage Means
- Coverage & Data Quality: What's the Difference?
- Your Coverage Tier
- Coverage Confidence On Your Metrics
- How Coverage Affects Jiro Features
- Coverage & Your Pro Subscription
- 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. This is the same for all Jiro users.
- Account Coverage: How much of your individual practice Jiro captures, based on your claims volume relative to your practice size. This varies per user.
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 using encounter volume data you provide.
When coverage is high, Jiro's data closely reflects your clinical activity. When coverage is lower, the data represents a partial view of your practice. Jiro surfaces this limitation directly on your metrics so you can interpret results with appropriate clinical context.
Data refreshes monthly. Coverage estimates improve as additional real-world data is processed and as volume data you submit is incorporated into Jiro's calculations.
Coverage vs. Data Quality: What's The Difference?
Jiro uses two separate signals to characterize data reliability. Understanding the distinction helps you interpret what each indicator means.
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.
Both signals appear on your metrics and address different questions. A metric can show high data quality (the data Jiro holds is mature and complete) while also showing low coverage (Jiro holds only a fraction of your total claims). Neither signal indicates inaccurate data. Both indicate the scope and completeness of what Jiro can measure.
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.
| 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. Research and Consult remain accessible using non-personalized data. |
| Low | Claims data exists but represents a small portion of your estimated total volume. | Metrics and Research cards draw on less specific data (specialty-level or location-level) rather than individual-level claims. A disclaimer appears alongside affected metrics. |
| Medium | A meaningful portion of your claims is captured, but gaps remain. | Individualized Metrics and Research cards are available with confidence indicators and caveats where coverage limitations may affect interpretation. |
| High | Real-world data closely reflects your total clinical activity. | Full individualized Metrics and Research cards. Confidence indicators reflect high reliability. |
Coverage Confidence on Your Metrics
Each metric on your Practice page carries a confidence indicator (High, Medium, or Low) derived from your current coverage tier. The indicator reflects how reliably that metric represents your individual practice given the real-world data available to Jiro.
The confidence indicator is independent of the Full Data / Latest Data toggle, which controls the time window applied to your data. Both indicators can appear on a metric simultaneously.
Selecting the confidence indicator opens a tooltip that explains what the confidence level means for that metric and how it relates to your coverage.
How Coverage Affects Jiro Features
Your coverage tier determines how Jiro's features respond when surfacing personalized information. Different surfaces handle incomplete or low-coverage data using the same principle: specificity adjusts based on available data.
Research
Individualized Research cards are currently unavailable, clinicians see Research based on specialty.
Consult
When coverage is low, Consult responses may include inline caveats indicating that personalized clinical context is derived from limited real-world data.
Spotlights
Spotlights also adjust their specificity based on coverage. When your coverage is limited, these features present patterns at the specialty or location level rather than individual practice level, maintaining relevance to your clinical context.
Referrals
Referral data often has naturally sparse coverage. Documented referral data is directional, relying on a “sending” and “receiving” party. Because of this limitation, Referral cards include explicit coverage caveats to provide appropriate context for interpreting referral patterns.
Coverage and Your Pro Subscription
Before upgrading to a Pro subscription, Jiro presents a coverage disclosure within the subscription flow. The disclosure describes data limitations that may apply to your account, explains what coverage means, identifies your current coverage level, and provides a path to submit volume data if coverage is limited. The disclosure does not prevent subscription. It ensures you have the relevant information before proceeding.
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 estimates 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. Coverage thresholds and metrics are subject to change as Jiro's data infrastructure and clinical evidence evolve.