The Between-Visit Gap: The Most Overlooked Data Problem in Specialty Care Analytics
- SolvEdge
- Mar 05, 2026
- 6 mins read
If you mapped the analytics coverage of a typical orthopedic or specialty care episode, it would look something like this: a dense cluster of data at the initial consultation, another cluster at the procedure, a cluster at the inpatient stay, and then a long, largely empty stretch between discharge and the six-week follow-up appointment.
That stretch isn’t empty clinically. Patients are recovering, or not. Rehab is happening, or being skipped. Pain is being managed, or becoming a complication. Care coordinators are supposed to be reaching out, or they’re behind on their caseload. Discharge instructions are being followed, or they’re in a drawer.
Every one of these events has performance implications. Most of them generate no analytics data whatsoever.
This is the between-visit gap and in specialty care, it is quietly responsible for a disproportionate share of adverse outcomes, readmission events, protocol failures, and bundled payment overruns.
Where Healthcare Analytics Goes Silent
The Encounter-Centric Analytics Model
The dominant architecture in healthcare analytics was built around clinical encounters. An encounter happens a visit, a procedure, a diagnostic test, an admission and that encounter generates structured data in the EHR. That data flows into the analytics environment. Reports are generated. Performance is assessed.
This model makes sense for a fee-for-service world, where the unit of analysis is the individual billable encounter. But healthcare has been moving steadily away from that model for over a decade. Value-based care, bundled payments, and population health management all require a fundamentally different analytics architecture one that measures performance across the episode rather than at individual encounters within it.
The architecture hasn’t fully followed the model.
What Happens in the Gaps
Between the procedure and the six-week follow-up, the following things typically occur with zero systematic analytics monitoring in most specialty care facilities:
A care coordinator is supposed to call the patient at day 7, day 14, and day 21. Sometimes they do. Sometimes their caseload prevents it. The call that didn’t happen generates no data. The protocol deviation is invisible.
The patient is prescribed three physical therapy sessions per week for four weeks. They attend two in week one, one in week two, and then stop entirely. The PT scheduling system has this data. The analytics environment doesn’t.
The patient reports increasing pain on their day-14 PROM survey. The flag is generated. Nobody on the care team is notified for five days because the alert routing wasn’t configured correctly. The response delay generates no data.
Each of these events is a facility performance failure. Each one has measurable clinical and financial consequences. None of them appear in the analytics dashboard until at best they’re manually reconstructed after a readmission event.
The Real Cost of Between-Visit Blindness
Between-visit data blindness has three distinct cost layers in specialty care, each operating independently but compounding in aggregate.
Clinical Cost
Protocol adherence in orthopedic and post-acute care drives outcomes in ways that are well-documented but rarely monitored in real time. Rehabilitation frequency, wound care compliance, medication adherence, and activity level in the immediate post-operative window are all predictive of outcomes at 30, 60, and 90 days.
When facilities don’t have real-time visibility into care protocol performance between encounters, they lose the intervention window that exists before outcomes deteriorate. Clinically, this manifests as complications that were identifiable before they became acute and would have been, with the right data.
Operational Cost
Care coordination is one of the highest-leverage operational investments a specialty care facility can make. A well-executed care coordination program in orthopedic surgery can measurably reduce LOS, readmission rates, and episode cost.
But care coordination performance is almost entirely invisible in encounter-centric analytics. If a care coordinator’s outreach cadence is falling behind if day-14 calls are consistently happening on day-19, or not at all the operational failure is generating no analytical signal until a patient outcome event surfaces it.
Facility reported outcomes, integrated into a healthcare analytics platform built for continuous monitoring, capture care coordination performance as it happens. Operational managers can see caseload adherence, outreach completion rates, and protocol deviation patterns in real time rather than through retrospective incident review.
Financial Cost in Value-Based Care
The financial architecture of bundled payments makes between-visit data blindness a direct revenue risk. In a 90-day episode bundle for a total joint replacement, every clinical event and care process within that window affects the reconciliation.
Readmissions, extended LOS, unplanned ED visits these are the expensive tail events that bundled payment models are designed to incentivize facilities to prevent. And the precursor signals for all of them exist in the between-visit window: declining PT adherence, escalating PROM scores, care coordination gaps, protocol deviations.
Facilities with encounter-centric analytics see the tail events. Facilities with continuous facility reported outcomes monitoring see the precursor signals and have the opportunity to respond before the financial exposure materializes.
A Real Scenario: The Orthopedic Program With Strong Metrics and Poor Outcomes
A regional orthopedic center had, by conventional analytics measures, a high-performing joint replacement program. Surgical outcomes were strong. Patient satisfaction at discharge was high. PROM capture rates exceeded CMS benchmarks. Quality measure scores were competitive.
Their bundled payment performance, however, was consistently marginal. 90-day readmission rates for total hip replacements were running 2.3 percentage points above their internal target. The finance team kept flagging it. The clinical team kept reviewing it. No one could identify a consistent clinical cause.
The root cause wasn’t clinical. It was operational, and it was invisible to their analytics environment.
An audit of the post-discharge period for a cohort of readmitted patients showed a consistent pattern: care coordination outreach had occurred at a lower frequency than prescribed, PT attendance had dropped below the protocol threshold in weeks two and three, and PROM flags had been acknowledged but not actioned within the required response window.
None of these data points were in their analytics dashboard. They were all in the scheduling system, the care coordinator’s task log, and the PROM platform unconnected to each other and invisible to the performance monitoring environment.
When the facility restructured its healthcare analytics platform to ingest facility reported outcomes continuously including care coordination completion rates, PT adherence data, and PROM response workflows the between-visit picture became visible for the first time. Operational interventions were possible while patients were still inside the episode window.
The readmission rate dropped 1.9 percentage points over two quarters. The bundled payment margin recovered. Nothing in the clinical protocols had changed.
What Facility Reported Outcomes Capture That Encounter Data Doesn't
The distinction between encounter data and facility reported outcomes is worth being precise about, because it’s where most analytics discussions lose their operational specificity.
Encounter data is generated at the moment of a scheduled clinical interaction: the procedure, the visit, the test, the admission. It captures what happened at the care event.
Facility reported outcomes capture what the facility did between care events: whether care coordination protocols were followed, whether outreach occurred on schedule, whether operational workflows completed as designed, whether the facility delivered on the care commitments embedded in its clinical protocols.
The gap between these two data streams is the gap between a record of what happened to the patient and an account of how the facility performed as a care delivery system.
A mature healthcare analytics platform needs both. Encounter data tells you the clinical story. Facility reported outcomes tell you the organizational accountability story and in value-based care, the accountability story is where performance improvement actually happens.
Building Continuous Analytics Across the Care Episode
The Five Between-Visit Data Streams Most Facilities Ignore
For specialty care administrators building or rebuilding their analytics infrastructure, five between-visit data streams have the highest impact on both clinical outcomes and financial performance and are most commonly absent from the analytics environment:
1. Care Coordination Outreach Completion Are post-discharge calls happening on the prescribed schedule? At what completion rate? When they don’t happen, what’s the operational reason? This data exists in care coordination task management systems and almost never reaches the analytics dashboard.
2. Rehabilitation Protocol Adherence PT attendance rates against the prescribed protocol are one of the strongest predictors of joint replacement outcomes. This data sits in the PT scheduling system. It needs to flow into your healthcare analytics platform in real time.
3. PROM Response Latency Not just whether patients complete PROM surveys, but how quickly care team members respond to flagged results. Response latency is a facility performance metric. It predicts whether PROM data will actually influence care decisions.
4. Discharge Instruction Comprehension Tracking Facilities that measure patient comprehension of discharge protocols through structured follow-up verification rather than assumed compliance see consistently better between-visit adherence. The comprehension data is a facility reported outcome. Most facilities don’t collect it systematically.
5. Protocol Deviation Documentation When care protocols are modified for individual patients, those modifications should be documented as facility reported outcomes, not just clinical notes. Analytics environments that capture protocol deviation rates enable evidence-based protocol improvement over time.
What Changes When You Close the Gap
The shift from encounter-centric to continuous episode analytics isn’t a technology event. It’s an operational transformation.
What changes practically: care coordinators have dashboards that show them protocol adherence status for each patient in real time, not through manual chart review. Department heads see between-visit operational performance as a live metric alongside clinical outcomes. Finance teams see episode-level cost and quality performance during the episode window, not after it closes.
What changes strategically: the organization develops a genuine understanding of its care processes not just its care outcomes. It knows not only that certain patients recover better, but what the facility did differently during the episode that explains the outcome. That knowledge is the foundation of evidence-based protocol improvement.
Facility reported outcomes, continuously monitored across the between-visit window, are how specialty care facilities stop managing outcomes retrospectively and start shaping them prospectively.
Frequently Asked Questions
The between-visit data gap refers to the absence of systematic analytics monitoring during the periods between scheduled clinical encounters post-operative recovery windows, rehabilitation periods, and care coordination intervals. During these gaps, care processes continue generating performance-relevant events, but most healthcare analytics platforms capture no facility-level data, leaving organizations blind to operational failures until they manifest as clinical or financial outcomes.
Facility reported outcomes capture care-process performance data continuously including care coordination activity, rehabilitation protocol adherence, PROM response workflows, and operational throughput regardless of whether a scheduled clinical encounter is occurring. When integrated into a healthcare analytics platform, FROs provide real-time visibility into facility performance across the full episode window, closing the data gaps that encounter-centric analytics leaves open.
Bundled payment contracts measure total episode performance across a defined window typically 90 days for major procedures. Clinical and operational events occurring between scheduled encounters care coordination gaps, rehabilitation non-adherence, delayed PROM response are among the strongest predictors of the readmission and complication events that drive bundled payment overruns. Facilities with continuous facility reported outcomes monitoring can identify and address these risk signals during the episode window, before they affect financial reconciliation.
SolvEdge FRO is a healthcare analytics platform built for continuous episode monitoring capturing facility reported outcomes across the full care continuum so specialty care facilities can see, manage, and improve performance between encounters, not just at them.