Time & Refresh Cadence
- Understanding Data Lag
- Product Refresh Cadences
- What This Means For You
- Frequently Asked Questions
- Related Articles
Jiro Health pulls from a large, de-identified, aggregated national claims database. Because claims move through payers, clearinghouses, and adjudication systems before reaching the platform, the data you see reflects a snapshot of the recent past — not current activity.
Each Jiro product also has its own update cadence. Understanding both the underlying data lag and the product-level refresh schedule will help you accurately interpret what you see.
Understanding Data Lag
Data lag refers to the gap between a clinical event and when it appears in Jiro. Claims are rendered, submitted, and adjudicated by a payer before they flow into the data pipeline.
Pharmacy claims arrive quickest. Pharmacy data takes approximately two weeks to reach 90% completeness, due to the rapid billing cycle for prescriptions.
Open claims reach completeness in approximately six weeks. This data is more current than closed claims but is not yet fully adjudicated.
Closed claims typically lag six months before reaching 90% completeness. They are fully adjudicated and updated monthly.
Qualified Entity (QE) data — Medicaid and Medicare claims — carries the longest lag, approximately nine months to 90% completeness. Government claims take longer to adjudicate.
Product Refresh Cadences
|
Feature |
Refresh Cadence |
What It Provides |
| Metrics | Weekly or monthly | New Metric values based on the claim type each Metric relies on |
| Spotlights | Weekly | Three to four Spotlights per week |
| Insights | Biweekly | Three distinct Insights, sufficiently different from the prior batch |
| Discover | Weekly after sign-up | At least five new Discover article summaries tailored to your specialty |
What This Means for You
Refreshes reflect the recent past, not today. Metrics, Insights, and Spotlights reflect data or clinical activity from prior months that has recently cleared the claims pipeline. For a detailed look at what data lag looks like in practice, see Common Reasons Data May Appear Inaccurate.
The cadence figures represent goals, not guarantees. Refresh volume depends on available data and quality filters. Weeks with limited incoming claims or tighter quality thresholds may produce fewer new items.
Panel size and specialty affect what surfaces. Clinicians with smaller panels or narrow specialties may see fewer Metrics, Insights, or Discover summaries than colleagues with broader data volume. Certain items may not appear if data volume is low, quality thresholds are not met, or the content falls outside your clinical scope.
Frequently Asked Questions
How often does my data update? Different parts of Jiro update on different cadences, depending on the availability of different claim types and the literature pipeline. See the Product Refresh Cadences table above for specifics.
Why does my data look old? Certain medical claims take longer to be finalized than others. Jiro's refresh cadence cannot outpace the speed at which claims are submitted and adjudicated through payer systems.
Why do I see fewer Insights and Discover summaries than a colleague? Differences in panel composition and specialty can lead to variation in surfaced Insights and Discover summaries between clinicians.
Why do some of my Metrics update while others stay the same? Metrics using pharmacy claims typically update faster because pharmacy data reaches completeness quickly. Metrics relying on inpatient or specialist claims are slower to finalize. Some Metrics are tied to annual or episodic events, which further varies their refresh cadence.
Will a refresh change my historical performance data? Refreshes may adjust past values if submitted claims are updated or reclassified. When this occurs, historical Metrics are revised to reflect greater accuracy.
What if something looks obviously wrong? Review the drill-down or definition for the Metric in question to confirm its parameters. If the item still seems off, use the in-app feedback button and include comments to help the team investigate.
Related Articles
Version History
Updated: April 17, 2026
Reviewed by: Claude, Help Scout Docs Reviewer
Approved by: [Name, Title]