Skip to main content

❕Patient Out of Area

See which patients were marked as out of area during manual recalls and follow up with next steps like de-registration.

Updated over 2 months ago

The Patient Out of Area list helps practices track patients who are no longer living in the local area, as identified during manual recalls.

❗️It’s important to note that this list is not triggered by address changes in EMIS. It’s based purely on the outcomes submitted by your manual recall team when speaking to patients.


🔁 How do patients end up on this list?

When recalling a patient manually, if the patient tells you they’ve moved out of area, follow these steps:

1️⃣ On the the Recall List, click "See Patient"

2️⃣ Click the “Action Patient” button

3️⃣ Select the outcome “No longer in area - Declined recall”

4️⃣ Write a note, toggle whether you want to save to the EHR + submit

Once submitted, this will automatically add the patient to the Patient Out of Area list under the Worklists section in Hippo.


🔎 Where to find the list

1️⃣ Go to the Worklists tab in the top navigation bar

2️⃣ Click the “Patient Out of Area” card

3️⃣ You’ll see all patients who were marked as out of area during manual recall attempts


✅ What should we do with patients on this list?

This list acts as a follow-up queue for your admin or clinical teams. For each patient, you might want to:

  • Review the patient’s EMIS record to confirm they’ve genuinely moved

  • Start the de-registration process, if appropriate

  • Add any internal notes in EMIS for future reference

  • Once you’ve taken any necessary action, mark the entry in Hippo as either:

    • Complete, or

    • Cancelled (if no action is needed)

❗This list does not clear automatically — it stays visible until someone in your team manually marks the case as resolved.


💡 Why this matters

🧭 Helps keep your patient list up to date

⛔ Prevents unnecessary future recalls for patients no longer in your catchment

🧹 Supports list cleaning workflows to improve practice data quality

Did this answer your question?