Hippo Recaller integrates directly with your clinical system (EMIS or SystmOne) so it can identify which patients need care and help your team recall them efficiently.
Here’s how the connection works, what data is accessed, and how it stays up to date.
🔁 Daily syncs — no manual searches needed
Hippo automatically pulls patient data from your clinical system once every 24 hours.
Each sync checks:
Which patients are registered with your practice
What care has already been completed and coded
Whether the patient meets the criteria for any current recall campaigns
You don’t need to run searches, upload files, or manually export anything. Hippo handles it for you.
🔒 What data does Hippo access?
To make recalls work properly, Hippo needs access to a limited set of clinical data for each patient. This includes:
Demographics (name, DOB, NHS number)
Contact details (phone, email, mobile)
Clinical codes related to conditions and care (e.g. QOF, vaccinations, reviews)
Appointment history
Your practice’s clinician roles and slot types
💡 Hippo does not access or store free-text notes or non-recall-related data.
🕵️♀️ How does Hippo stay in sync?
Every night, Hippo re-runs its internal searches using live data from your clinical system.
This means:
Patients who have just completed care are automatically removed from recall lists
Patients who were missed previously (e.g. due to a recent code entry) will be picked up
You’re always working with the most up-to-date list - not a static export
📁 How is this data used?
Hippo uses the data it pulls to:
Decide which patients need recalling
Determine what care is still outstanding
Suggest appointment combinations
Trigger automated invites
Power analytics and recall outcome tracking
🛡 Data protection and privacy
Hippo follows strict NHS data protection standards:
All data is handled within UK-based, NHS-compliant infrastructure
Patients are only included if they’re currently registered with your practice
Data is deleted automatically if a patient deregisters or becomes inactive
📖 You can read more in our Information Governance and Data Handling Overview.