Sources: 3 · Verified 2026-10-27
A cancelled appointment is not resolved when the cancellation is recorded. It is resolved when the patient is rebooked, referred elsewhere, or decides not to return. The gap between those two events is rescheduling latency, and it is usually invisible in a report that counts cancellations but not their aftermath.
Latency study at a glance
| Factor | Details |
|---|---|
| Start | The cancellation or clinic move timestamp |
| Stop | Rebooked, referred, or declined |
| Initiator | Patient, clinic, or provider |
| Censor | Unresolved at the observation window |
Why cancellations look resolved too early
The cancellation is recorded, the slot is released, and the report counts the event as handled. The patient may still be waiting for a new date, or may have given up. Because the second event is not measured, the practice cannot tell whether its rebooking outreach works. The cancellation count falls while access quietly deteriorates, and the next available appointment drifts further out.
Latency checkpoints
| Category | Specific Tasks | Planning Estimate / Note |
|---|---|---|
| Define |
| Before the cycle |
| Attribute |
| Per cancellation |
| Follow |
| Daily |
| Analyze |
| Monthly |
- Category
- Define
- Specific Tasks
- Write the start event
- Define resolved states
- Set the window
- Planning Estimate / Note
- Before the cycle
- Category
- Attribute
- Specific Tasks
- Record the initiator
- Record the reason
- Link the original slot
- Planning Estimate / Note
- Per cancellation
- Category
- Follow
- Specific Tasks
- Record outreach attempts
- Record the new date
- Record a decline
- Planning Estimate / Note
- Daily
- Category
- Analyze
- Specific Tasks
- Median and quartiles
- Segment by initiator
- Inspect the tail
- Planning Estimate / Note
- Monthly
Latency measures compared
| Decision factor | Cancellation count | Time to rebook |
|---|---|---|
| Start | Not defined | Cancellation timestamp |
| End | Not measured | Rebooked or closed |
| Initiator | Blended | Patient, clinic, provider |
| Tail | Hidden in the average | Quartiles and open cases |
Start
- Cancellation count
- Not defined
- Time to rebook
- Cancellation timestamp
End
- Cancellation count
- Not measured
- Time to rebook
- Rebooked or closed
Initiator
- Cancellation count
- Blended
- Time to rebook
- Patient, clinic, provider
Tail
- Cancellation count
- Hidden in the average
- Time to rebook
- Quartiles and open cases
What a latency measure changes
Every cancellation starts a clock that stops when the patient is rebooked, referred, or declines. The initiator is recorded, so a clinic move is not blended with a patient cancellation. The monthly report shows the median, the upper quartile, and the share still open. The practice can see that patient-initiated cancellations rebook quickly when the coordinator calls within an hour, while clinic moves wait for a provider template change.
A monthly latency review
The analyst pulls 120 cancellations. Ninety-four are patient-initiated, eighteen are clinic moves, and eight are provider moves. Median time to rebook is 1.4 days for patient cancellations and 9 days for clinic moves. Twenty-two cases remain open at thirty days, mostly patients who did not answer two attempts. The team adds a second contact channel and a script that offers a specific date rather than a general invitation to call back.
Controls that keep the measure meaningful
| Success Factor | How To Do It | Results You Get |
|---|---|---|
| Clear start | Use the system cancellation time | Comparable cases |
| Resolved states | Rebooked, referred, declined | No ambiguous closure |
| Initiator split | Attribute every case | Correct intervention |
| Tail review | Inspect the slowest decile | A process fix |
- Success Factor
- Clear start
- How To Do It
- Use the system cancellation time
- Results You Get
- Comparable cases
- Success Factor
- Resolved states
- How To Do It
- Rebooked, referred, declined
- Results You Get
- No ambiguous closure
- Success Factor
- Initiator split
- How To Do It
- Attribute every case
- Results You Get
- Correct intervention
- Success Factor
- Tail review
- How To Do It
- Inspect the slowest decile
- Results You Get
- A process fix
Mistakes that distort the measure
Closing a case when the outreach attempt is made rather than when the patient is rebooked. Blending clinic and patient cancellations. Dropping unresolved cases from the median. Using the appointment date instead of the cancellation date as the start. Recording a rebook without linking it to the original slot. Each mistake makes the process look faster and the access problem harder to see.
Why latency belongs to scheduling operations
The cancellation, the outreach, and the new appointment all live in the scheduling record. A measure built from billing or the clinical note misses the patient who never returns. Scheduling can see the original slot, the attempts, and the outcome, which is exactly the sequence needed to improve the process.
Research methodology
This study design defines cancellation start events, resolved states, initiator attribution, and censoring for open cases. It does not report an observed latency.
This is a measurement framework. It does not establish a service standard for rebooking.
Data sources and methodology
This brief reports published findings as stated by each source. It does not combine study populations into a new benchmark; local operators should treat the figures as context and measure their own workflow.
- AHRQ, CAHPS Surveys: Access and communication measures
- CMS, Provider Resources: Service and coverage context
- HHS, HIPAA Privacy Rule: Patient contact and data handling
Frequently asked questions
Should a clinic-initiated move count?
How do we treat a patient who does not want to rebook?
What window should we use?
Report the open cases beside the median
A short median with a large unresolved tail is not a fast process. Show both before drawing a conclusion.
Book a Free Consultation →


