A rehab coordinator opens her morning dashboard. Thirty active physical therapy (PT) referrals. Each one shows the same thing: Authorized. In progress. Open.

The authorization tells her the service is approved. But it doesn’t tell her whether the care is really happening. What she needs is visibility into the visits that fulfill it:

• Visit four happened Monday
• Visit five was missed.
• Visit six still has no documentation.
• Visit seven isn’t scheduled at all.

Until now, no EMR has ever modeled multi-visit PACE services at the encounter level, leaving every team blind to whether care actually happened.

This is just one referral. Multiply it across 30 active PT orders, and the visibility gap becomes nearly impossible to manage manually.

At best, EMRs collapse a referral like this into one referral with one authorization, and one line in the service log. But this single line often represents a multi-visit service. One authorized PT service, for example, can represent 12 individual visits over three weeks. For a PACE program, this means twelve separate answers to “Did this happen, and can we prove it?”

This blind spot lands on the IDT, who is left managing care delivery in the dark, without a clear view of whether participants are actually receiving the care that was ordered.

The workarounds built by necessity

Forced to rely on software that stops at the authorization boundary, PACE teams end up building their own bridges between disconnected workflows:

• Service request shows the referral and authorization, but not the individual encounters.
• Scheduling shows the appointments, but not whether they were completed or documented.
• Clinical documentation shows notes, but they are often stacked inside a single parent service file where earlier encounters get buried or overwritten.

To connect these three workflows, teams improvise with side spreadsheets to track scheduled, completed, and missed visits; manual cross-checks between calendars and service logs; and stacked note searches to confirm whether each encounter was documented.

These workarounds exist for one reason: no EMR has ever supported encounter-level tracking for multi-visit services. Every system collapses a recurring service as a single record.

CareHub is the first to break this limitation.

Visibility built around the encounter

Today, CareHub introduces encounter-level service tracking—a new model for how EMRs track multi-visit services. Instead of collapsing multi-visit services into a single record, CareHub treats each visit as its own connected encounter.

With CareHub’s Multi-Visit Service Tracking, a 12-visit PT order becomes 12 distinct, linked encounters, resulting in:

• Clear status at every step: The IDT sees visit four is documented, visit five is completed and awaiting a note, and visit six is scheduled for Thursday, all without opening five different screens or emailing a coordinator.
• Unified clinical and operational tracking: Scheduling updates and clinical notes map to the specific visit they belong to, keeping documentation clean, chronological, and audit-ready.
• Proactive gap detection: Missed visits trigger immediate visibility, allowing care managers to intervene before a two-week delay results in a participant’s functional decline.

In CareHub’s exclusive encounter-level model, a 12-visit PT order becomes 12 distinct, linked encounters—not one collapsed line that hides visit details.

Encounter-level workflow for multi-visit services

In CareHub, recurring appointments automatically generate their own visit records, with each tied to a single service and authorization. A missed visit surfaces the moment it’s missed, without anyone searching for it. Scheduling status lives at the visit level, so there’s no risk of a missed visit getting buried under an “in progress” service.  Clinical notes attach to the specific encounter they represent (vs. the entire order), building a documentation trail that’s trackable and audit-ready by design. And as visits move through their stages, the service updates automatically In CareHub, closing only when every required encounter is complete.

CareHub’s encounter-level model closes the gap between an authorized service and the visits that actually deliver it. When every visit stays connected to its authorization, the IDT knows what’s done, what’s outstanding, and where attention is needed next—without ever reconstructing care in the dark again.

Give your IDT encounter-level clarity. See how CareHub’s multi-visit service tracking works.

Missed last month’s updates? Check out the July CareHub EMR updates.