On this page
- What is recall completion tracking, and how is it different from contact status?
- Why does this distinction matter?
- What does each recall status prove?
- What role do claims and other completion evidence play?
- Who should approve status definitions?
- How should you measure recall completion?
- A one-page status policy
Key takeaways
- Contact status records staff activity; completion evidence records what happened to the patient.
- Scheduled, checked in and completed encounter are different states with different strength of evidence.
- Canceled and no-show appointments should reopen the recall automatically, not wait for the next report.
- Status definitions and closure rules should be approved once, centrally, so every location reports the same way.
Patient contact status shows what staff did, not what happened to the patient. A recall marked contacted, scheduled or even checked in can still end with no completed care, because appointments get canceled, patients do not show, and visits do not always include the service the recall was for. Recall completion tracking should close a recall only on evidence that the care happened, such as a completed encounter or procedure for the right service, or a documented exception.
Many recall programs look busy and still leave patients overdue. The usual cause is not effort. It is a status model that treats activity as an outcome.
What is recall completion tracking, and how is it different from contact status?
Contact status is a record of outreach: a call made, a message sent, a voicemail left, a callback requested. Completion is a record of care: the visit or procedure the recall called for happened and is documented. The two live in different places, are updated by different people and answer different questions.
Contact status answers "what should we do next for this patient?" Completion answers "can we close this recall?" A practice that uses one field for both will close recalls too early or keep calling patients who were already seen.
Why does this distinction matter?
It matters because the gap between contact and completion is where patients are lost. A scheduler books a patient and marks the recall done. Weeks later the appointment is canceled, and nothing puts the patient back on the list. On paper the recall program worked. In the record the patient is still overdue, and the practice has an unrecorded operational gap.
The same pattern shows up with orders and referrals. How to track unresolved medical orders through completion covers it for orders; the logic is identical.
What does each recall status prove?
Each status proves something specific and stops short of something else. The table below is a starting point for writing your own definitions.
| Status | What it proves | What it does not prove | What should happen next |
|---|---|---|---|
| Contacted | Staff reached the patient or left a message | That the patient agreed, booked or received care | Record the outcome; plan the next step |
| No answer | An attempt was made | Anything about the patient's intent or care status | Schedule the next attempt per cadence |
| Scheduled | An appointment exists | That the right service is booked, inside the window, or will happen | Link the appointment to the recall; keep the recall open |
| Canceled | The booked appointment will not happen | Why, or whether the patient rebooked | Return the recall to the open queue |
| No-show | The patient did not arrive | Whether care happened elsewhere | Return to the queue; reach out again |
| Checked in | The patient arrived for a visit | That the recalled service was performed | Watch for the encounter or procedure record |
| Completed encounter | A visit was documented | That it was the visit type or procedure the recall needed | Close only if it matches the recall's service |
| Completed procedure | The procedure was performed and documented | That the result or follow-up interval has been set | Close the recall; the new interval starts a new recall if clinically indicated |
| Done elsewhere | Staff recorded care at another facility | That it happened, unless external evidence confirms it | Close as an exception with a reason and source |
Contacted and no answer
These are outreach outcomes. They decide the cadence of the next attempt and help with staffing, but neither changes the recall's clinical state. A recall with ten contact attempts and no booking is still overdue.
Scheduled
Scheduled is progress, not completion. Check three things: the appointment is for the service the recall needs, it falls inside the window, and it is linked to the recall so a later change is caught. A follow-up office visit booked against a surveillance procedure recall does not satisfy that recall, even though it looks like a match on a busy list. Reminder tools protect the appointment, but they do not close the recall; patient recall software vs. reminder software explains the split.
Canceled and no-show
These are the most common points of leakage. Both should reopen the recall automatically. If reopening depends on someone remembering, it will often not happen, and the patient drops out of view until the next audit. Cancellation and no-show rebooking tools exist to catch exactly this.
Checked in
Check-in confirms the patient arrived. It does not confirm what was done. For visit recalls, check-in plus a completed encounter is usually enough. For procedure recalls, look for the procedure record itself.
Completed encounter and completed procedure
These are the strongest evidence most practices hold in the EHR. Matching should be on service, not just date: a completed visit with a different provider for an unrelated problem does not close a surveillance recall.
What role do claims and other completion evidence play?
Claims and health information exchange data can add evidence the EHR does not hold, particularly for care completed at another facility. A claim for the recalled service, or an HIE record of a procedure elsewhere, can confirm an external completion that staff could only note from a patient's word. These feeds are optional and not every practice has them. Where they are not connected, a done-elsewhere closure should carry a reason and source, and reporting should keep it separate from verified completions.
Who should approve status definitions?
Status definitions decide what counts as closed, so they shape every number leadership sees. If one location closes recalls on scheduled and another on completed procedure, their completion rates cannot be compared. If schedulers decide which visit types satisfy a surveillance recall, the practice is making a clinical judgment in an operational workflow.
A sound approach:
- Operations leaders draft the status list and outcome codes.
- A clinical reviewer approves which evidence closes each recall type and which exceptions are allowed.
- The practice administrator publishes the definitions and trains every location on them.
- Reports show verified completions, exceptions and open recalls separately.
How should you measure recall completion?
Measure the share of overdue recalls that end in completed care within a set period, by service line and location, with exceptions reported separately. Illustrative example: if a location starts a quarter with 200 overdue recalls and 80 end in a verified completed visit or procedure, its completion rate for that cohort is 80 divided by 200. Contact attempts per recall are a useful staffing measure but should never stand in for this number. The same rule applies to care-management outreach: a call is not enrollment, which needs clinician review and patient consent. Care management intelligence flags candidates for that review; it does not enroll anyone.
Be careful about cause. A recall completed after outreach may have been completed anyway. Report completions as care completed after the recall was identified, compared with a baseline, rather than as proof that outreach caused it.
A one-page status policy
Most practices can fit the whole policy on one page: the status list, the outcome codes, which evidence closes each recall type, who can record an exception and how reopening works. Print it, train on it, and review it whenever a new location or EHR joins.
Software can enforce the reopening and closing rules so they do not depend on memory. Patient recall software such as Nuvory treats completion as evidence rather than status: a canceled appointment puts the recall back in the queue, and the recall closes only when the visit or procedure is documented. Where claims or HIE feeds are connected (see pricing for which plans include them), matching for care at other facilities becomes more precise. For the wider process, see the patient recall management guide and the rest of the patient recall guides.
Recall completion tracking checklist
- Write down a definition for each recall status your staff use.
- Separate outreach outcome codes from care completion statuses.
- Decide which evidence closes each recall type: encounter, procedure, result or documented exception.
- Reopen recalls automatically when an appointment is canceled or becomes a no-show.
- Require a reason and source for every done-elsewhere closure.
- Have a clinical reviewer approve completion rules for procedure and surveillance recalls.
- Report verified completions separately from contact attempts.
Frequently asked questions
Should a recall close when the patient schedules?
No. Scheduling moves the recall forward, but the appointment can still be canceled, missed or booked for the wrong service. Keep the recall open, link it to the appointment, and close it when a completed encounter or procedure that matches the recall appears in the record.
What counts as completion evidence for a recall?
Usually a completed encounter or procedure for the service the recall calls for, documented in the EHR. Where connected, claims or health information exchange data can confirm care completed elsewhere. The exact rules for each recall type should be approved by a clinical reviewer at the practice.
How should done-elsewhere closures be handled?
Record the reason and, where possible, the facility and source of the information. Close the recall as an exception, not as a completion here, and report it separately. External data, where available, can confirm the closure later.
Are outreach metrics still useful?
Yes, for staffing and process. Attempts per recall, reach rates and time to first contact help managers plan the work. They should be reported next to verified completion, not in place of it, because activity does not show whether care happened.