Understanding Your Data Coverage
[SCREENSHOT — example Consult response showing inline coverage caveat]
Submitting Your Volume Data
Jiro estimates your coverage percentage using self-reported encounter volume. This information is not collected during onboarding. Jiro prompts you when specific signals indicate a potential coverage limitation — for example, a low data quality score, activity that appears inconsistent with HCO benchmark comparisons, or a reported hours mismatch.
When a prompt is triggered, a banner appears on your Practice page with a link to the volume data form.
[SCREENSHOT — Practice page coverage data collection banner with CTA]
Information requested per practice location:
- Outpatient and telehealth encounters per week
- Consult and emergency department encounters per week
- Unique inpatient patients per week
Physicians practicing across multiple locations complete the form for each location. The form accommodates multi-location workflows and does not require all entries to be submitted at once.
Providing this data enables Jiro to calculate a coverage estimate and assign a more precise confidence tier to your metrics. Until volume data is submitted, metrics display at the lowest applicable confidence level for your tier.
Volume data is used to calibrate how Jiro communicates data reliability to you. It is not used for benchmarking and is not shared externally.
[SCREENSHOT — volume data collection form showing per-location, per-setting inputs]
Coverage and Your Pro Subscription
Before upgrading to a Pro subscription, Jiro presents a coverage disclosure within the subscription flow. The disclosure describes the 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.
[SCREENSHOT — pre-paywall coverage disclosure in the subscription upgrade flow]
Notes
- Coverage and data quality are distinct signals. Low coverage does not indicate that your data is inaccurate — it indicates that Jiro's view of your practice is partial.
- 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 may use different coverage thresholds than medical claims metrics. [NEEDS CONTENT: confirm once JH-1354 is resolved.]
Related Articles
- How to Cite Jiro in Research
- Time & Refresh Cadence
- Common Reasons Data to your Practice