Time & Refresh Cadence
- Overview
- 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
Overview
Jiro surfaces practice intelligence from real-world claims data. Because claims move through payers, clearinghouses, and adjudication systems before reaching the platform, the data you see reflects patterns and performance from the recent past, not current activity. This reference explains the data lag your practice experiences and the refresh schedule for each Jiro feature.
Understanding Data Lag
Data lag is the interval between a clinical event and its appearance in Jiro. Claims are rendered, submitted, and adjudicated by a payer before flowing into the data pipeline. The lag varies by claim type along with availability from data vendors and sources.
Pharmacy Claims
Pharmacy data appears fastest, reaching 90% completeness in approximately two weeks due to rapid billing cycles.
Open Claims
Open (in-process) claims reach 90% completeness in approximately eight weeks. These claims are more current than fully adjudicated claims but not yet finalized.
Closed Claims
Closed (fully adjudicated) claims typically reach 90% completeness in approximately six months and are updated monthly.
Qualified Entity Data
Medicaid and Medicare claims (Qualified Entity data) carry the longest lag, reaching 90% completeness in approximately nine months. Government claims require extended adjudication time.
Data Quality: Complete vs. Recent vs. Latest
Practice offers three viewing modes so you can balance data completeness against recency:
Complete View
- Data lag: Approximately six months
- Completeness: 90% or greater of submitted claims
- Use when: You require fully adjudicated, verified data for clinical judgment or peer comparison
- Best for: Quality reporting, peer benchmarking, historical trend analysis, risk assessment
Recent View
- Data lag: Approximately eight weeks
- Completeness: Includes preliminary findings from pharmacy and open claims that are submitted but not yet fully adjudicated
- Use when: You want current practice patterns with a shorter processing delay
- Best for: Monitoring recent activity, early trend detection, timely performance assessment
Latest View
- Data lag: The shortest available, showing the newest data as it arrives
- Completeness: Far less adjudicated than Complete or Recent views, since claims have had the least time to process
- Use when: You want the most current snapshot possible, understanding that it reflects the least verified data
- Best for: Spotting emerging patterns as early as possible, with the tradeoff of lower confidence
Toggle between views on your Practice dashboard. Each metric displays its time frame, so you always know which view you're looking at.
Product Refresh Cadences
Each Jiro feature updates on its own schedule based on data availability and quality standards:
| Feature | Refresh Cadence | What It Provides | Data Quality Requirement |
|---|---|---|---|
| Metrics | Weekly or monthly | 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) | Proactive clinical, operational, and financial signals flagging significant changes or benchmarking opportunities. | Data must exceed 85% completeness and quality threshold. |
| Referrals | Monthly | Referral patterns inferred from matched claims across providers | Directional, not a complete record. Coverage is naturally sparse since it depends on both sides of a referral generating a claim |
| Reimbursements | Tied to closed claims only, analyzes previous completed year | Payment amounts based on adjudicated claims | Only reliable once the claim closes |
| Denials | Monthly; Analyzes previous 12 completed months | What is driving your denied claims, which payer are responsible, and how your denial rate compares to peers. | Fully denied claims. Partially denied claims, pending claims, or claims under appeal are not included. |
| Encounter Coding | Monthly; Analyzes 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. |
| Research | Weekly | Patterns in care delivery, patient outcomes, and population trends from real-world data. | Real-world claims data and ICD-10 codes that are specific to each card. Click into a Research article to view its design and cohorts. |
| Discover | Weekly (after initial population) | At least five new clinical articles tailored to your specialty. | Requires complete profile and 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 has recently cleared the claims pipeline. For examples of how data lag affects specific metric values, see Common Reasons Data May Appear Inaccurate.
Cadence Figures Are Goals, Not Guarantees
Refresh volume depends on data availability and quality filters. Weeks with lower claims volume or tighter quality standards may produce fewer new items.
Your Data View Choice Affects What You See
Complete view surfaces insights from fully adjudicated claims (higher confidence, longer lag). Recent and latest views include preliminary findings from open claims (faster, less complete adjudication). Choose the view that fits your clinical decision-making needs.
Quality Thresholds Filter What Appears
Features like Spotlights only surface insights when underlying data meets 85% completeness standards. If you notice fewer Spotlights than usual, claims processing volume or completeness may be temporarily lower.
Panel Size & Specialty Limit What Surfaces
Clinicians with smaller panels or narrow specialties may see fewer Metrics or Discover articles than colleagues with larger data volume. Some items do not appear if data volume is insufficient, quality thresholds are not met, or content falls outside your clinical 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
- Pharmacy data lags the shortest (approximately two weeks to 90% completeness). Medicaid and Medicare claims take the longest (approximately nine months).
- Complete, Recent and Latest views serve different purposes. Neither is "correct", choose based on whether you prioritize accuracy or recency.
- The 85% completeness threshold for Spotlights is applied automatically and cannot be adjusted. This ensures insights are based on reliable data.
- Data lag is structural. Claims processing speed is determined by payer and adjudication systems, not by Jiro.