Time & Refresh Cadence
- Understanding Data Lag
- Data Quality: Complete vs. Recent vs. Latest
- Product Refresh Cadences
- What This Means for Your Practice
- Frequently Asked Questions
- Important to Remember
- Related Articles
Knowing how often Jiro's data updates, and why it trails clinical activity, helps you read your numbers with the right context. Data lag is the interval between a clinical event and its appearance in Jiro. It occurs because claims pass through payers, clearinghouses, and adjudication before they reach Jiro.
Update schedules vary by feature and claim type, so the data you see reflects the recent past, not current activity.
Understanding Data Lag
Claims pass through payers, clearinghouses, and adjudication before they appear in Jiro. The data you see reflects patterns from the recent past, not current activity. Data lag is the interval between a clinical event and its appearance in Jiro. The lag varies by claim type.
Pharmacy Claims
Pharmacy claims have the shortest lag. They reach 90% completeness in approximately two weeks because of rapid billing cycles.
Open Claims
Open claims usually come from clearinghouses. They reach 90% completeness in approximately eight weeks. They are more current than fully adjudicated claims but are not yet finalized.
Closed Claims
Closed claims usually come from insurance plans (payers). They typically reach 90% completeness in approximately six months and are updated monthly.
QE (Qualified Entity) Claims
QE claims have the longest lag. Medicare and Medicaid data reaches 90% completeness in approximately nine months because government claims require extended adjudication time.
Data Quality: Complete vs. Recent vs. Latest
Practice offers three views so you can balance how complete your numbers are against how recent they are. Jiro data refreshes on a schedule, so recent activity may not appear yet.
| View | Data Lag | Completeness | Best For |
|---|---|---|---|
| Complete | About 6 months | 90% or more of submitted claims | Quality reporting, peer benchmarking, historical trend analysis, risk assessment |
| Recent | About 8 weeks | Includes preliminary findings from pharmacy and open claims that are not yet fully adjudicated | Reviewing recent activity, early trend detection |
| Latest | Shortest available | Far less adjudicated than Complete or Recent | Spotting emerging patterns as early as possible, with lower confidence |
Each view serves a different purpose. No view is "correct". Choose Complete when accuracy matters most. Choose Recent or Latest when recency matters most.
Product Refresh Cadences
|
Feature |
Refresh Cadence |
What Refreshes Provide |
Data Quality Requirements |
|---|---|---|---|
| Metrics | Weekly or monthly (varies by Metric) | Updated metric values based on the claim type each metric uses. | Varies by metric type (pharmacy claims update faster; specialist or inpatient claims update more slowly). |
| Spotlights | Weekly (after initial population) | Clinical, operational, and financial signals that flag significant Metric changes or benchmarking opportunities. | Data must exceed 85% completeness and the quality threshold. |
| Referrals | Monthly | Referral patterns inferred from matched claims across providers. | Directional, not a complete record. Coverage is naturally sparse because it depends on both sides of a referral generating a claim. |
| Reimbursements | Tied to closed claims only; covers the previous completed year. | Payment amounts based on adjudicated claims. | Reliable only once the claim closes. |
| Denials | Monthly; covers the previous 12 completed months | What is driving your denied claims, which payers are responsible, and how your denial rate compares to peers. | Fully denied claims only. Partially denied claims, pending claims, and claims under appeal are not included. |
| Encounter Coding | Monthly; covers the previous 12 completed months | How you code your office and outpatient visits compared to your peers. | Office and outpatient professional claims. Institutional and facility claims are not included. |
| Discover | Weekly (after initial population) | At least five new clinical articles tailored to your specialty. | Requires a complete profile and a 24–48 hour initial setup period. |
What This Means for Your Practice
Refreshes Reflect the Recent Past
Metrics, Research, and Spotlights reflect clinical activity from prior months. That activity has recently finished claims processing.
Cadence Figures Are Goals, Not Guarantees
The number of new items per refresh depends on data availability and quality filters. Weeks with lower claims volume or tighter quality standards may produce fewer new items.
Your Data View Affects What You See
Choose the data view that fits your clinical decision-making needs. Each view balances speed against how fully claims have been resolved.
- Complete: shows insights from fully adjudicated claims. Confidence is higher and the lag is longer.
- Recent: includes preliminary findings from pharmacy and open claims. It is faster, but claims are less fully adjudicated.
- Latest: shows the newest available data. It is the fastest view, and claims are far less adjudicated.
Quality Thresholds Filter What Appears
Features such as Spotlights surface insights only when the underlying data meets the 85% completeness standard. If you see less than usual, claims volume or completeness may be temporarily lower.
Panel Size & Specialty Limit What Surfaces
Clinicians with smaller panels or narrow specialties may see fewer Metrics, Research summaries, or Discover articles than colleagues with larger data volume. Items may not appear in three cases: data quality is insufficient, quality thresholds are not met, or the content falls outside your scope.
Frequently Asked Questions
How often does my data update? Different Jiro features update on different schedules based on data type and availability. See the Product Refresh Cadences table for specifics. Metrics refresh weekly or monthly depending on metric type. Spotlights appear weekly after initial population. Discover adds new content weekly after your initial 24–48 hour setup period.
Why does my data look dated? Claims processing time varies by claim type and payer. Jiro's refresh schedule cannot exceed the pace at which claims are submitted and adjudicated. Use Complete view for fully finalized data, or Recent/Latest view for the current snapshot even if some claims are still processing.
When should I use Complete view versus Recent view versus Latest view? Use Complete view for clinical decisions requiring high confidence in data accuracy, such as quality reporting, peer comparison, or risk assessment. Use Recent view to monitor your current practice patterns and detect emerging trends with a shorter processing delay. Use Latest view when you want the newest data available, understanding that it reflects the least adjudicated, lowest-confidence snapshot. You can toggle between all three based on your immediate need.
Why do some Metrics update while others remain unchanged? Pharmacy claim-based metrics update faster because pharmacy data reaches completeness more rapidly. Metrics using inpatient or specialist claims finalize more slowly. Some metrics are tied to annual or episodic clinical events, which further varies refresh timing.
Why are there fewer Spotlights some weeks? Spotlights appear only when underlying data meets the 85% completeness standard. When claims processing slows or data quality dips temporarily, fewer Spotlights are generated that week. This threshold ensures signal accuracy.
Do refreshes change my historical Metric values? Yes. Refreshes may adjust prior values if submitted claims are updated or reclassified. When this occurs, historical Metrics are revised to reflect greater accuracy. This ensures trend analysis remains valid
Something appears inaccurate. What should I do? Review the metric definition and calculation details to verify parameters. If the value still seems incorrect, use the in-app help feature and include context. Note whether you're viewing Complete or Recent/Latest data, as this affects which claims are included in calculations.
Important to Remember
- Jiro data reflects the recent past, not current activity, because claims pass through payers, clearinghouses, and adjudication before they appear.
- Complete view has about 6 months of lag and is best for quality reporting and peer benchmarking. Recent and Latest are faster but less adjudicated.
- Spotlights appear only when data exceeds 85% completeness and meets the quality threshold, so some weeks may show fewer.
- Referrals are directional, not a complete record, because coverage is sparse when it depends on both sides of a referral generating a claim.
- Refreshes may adjust prior Metric values when submitted claims are updated or reclassified.