When Hippo contacts a patient or you record an outcome in Hippo, relevant activity can be written back into the patient’s EMIS record.

This means you can see a record of Hippo recall activity without needing to log into Hippo every time.

Exactly what appears depends on how the patient was contacted and whether your practice uses Hippo’s default or custom SNOMED writebacks.

Open the patient in EMIS and check their:

Hippo writebacks appear alongside other coded activity on the patient record.

When Hippo sends an automated recall, it writes recall activity back to the patient record.

By default, Hippo uses:

714311000000108 – Patient recall administration

This records that Hippo contacted the patient.

Depending on your Recall Campaign settings, the writeback may also contain information about the recall that was sent.

Patient recall administration is an administrative recall code.

It does not mean:

It simply records the recall activity.

Practices can choose to use different SNOMED codes for their recall messages.

For example, you might want a diabetes recall to write back a diabetes-specific invitation code rather than the default Patient recall administration code.

In that case, the code you’ve configured will appear in EMIS when that recall is sent.

For example with the code for Asthma :

See Condition-Specific SNOMED Writebacks and Using Custom SNOMED Codes and Writeback Messages for more information.

When you manually follow up a patient through the Recall List and save an outcome using Action Patient, Hippo can write that activity back to EMIS too.

The writeback will reflect the SNOMED code selected when you save the outcome.

For example, you might record that:

For example, selecting Patient declined recall does not automatically mean a clinical decline for the underlying care has been recorded.

If the patient has actually declined the care itself, make sure you select the appropriate clinical decline code before saving.

Some Hippo recall messages include patient response options.

Where a patient submits a response, the relevant recall activity can be written back to their clinical record.

The exact writeback depends on the response and the SNOMED configuration being used by your practice.

This gives you an audit trail of the patient interaction alongside the rest of their recall history.

Patient-submitted health information works slightly differently.

For example, a patient might submit:

These results are not written straight into EMIS.

Instead, they appear in Hippo’s Unapproved Basic Health Data worklist.

A member of your team reviews the information first.

If it’s correct, select Save to record and Hippo will write the approved information into EMIS using the relevant clinical codes.

If the information is incorrect, you can cancel it and nothing is written to the patient record.

Hippo writebacks normally appear shortly after the relevant action takes place.

For example:

Automated recall sent → writeback follows the recall activity

Action Patient saved → writeback follows the saved outcome

Questionnaire approved → information is written back after you approve it

If Hippo shows that the activity happened but you still can’t see the expected writeback in EMIS, check both Consultations and Care History.

If it’s still missing, get in touch with us.

EMIS may display a slightly different description from the wording you see in Hippo.

That doesn’t necessarily mean a different code has been used.

For SNOMED codes, the most important thing is the SNOMED concept ID.

If the concept ID matches, it’s the same underlying clinical code even if the wording displayed by EMIS is slightly different.

For an automated campaign, check the Recall Flow settings.

You can see which writeback configuration is being used for the messages in that campaign.

Depending on your setup, this may be:

For manual recalls, check the SNOMED code selected in the Action Patient pop-up before saving.

That’s Hippo’s default automated recall writeback.

It records that recall activity took place but does not itself mean the patient has completed or declined the care.

Yes.

You can use custom or condition-specific SNOMED codes for recall writebacks where appropriate.

See Using Custom SNOMED Codes and Writeback Messages for more information.

Because a recall writeback records contact activity, not completion of the clinical care.

The patient will remain due until Hippo sees the relevant completion, decline or exception code required by that clinical indicator.

Recording the outcome through Action Patient does not create the appointment.

You still need to book the patient into the appropriate appointment in EMIS.

Patient-submitted health information needs to be reviewed first.

Check Unapproved Basic Health Data in Hippo. Once a member of staff approves the submission, it can be written to the clinical record.

Check both Consultations and Care History in EMIS.

If the activity is visible in Hippo but the expected writeback still isn’t appearing, message us with the campaign and date so we can investigate.

Hippo writebacks give you a record of recall activity directly in EMIS.

The main things to remember are:

📨 Automated recalls → written back using the campaign’s configured SNOMED code

🎬 Action Patient → writes back the code selected when the outcome is saved

📅 Manual “Booked appointment” outcomes → do not create an EMIS appointment

🩺 Questionnaire data → only writes back after your team reviews and approves it

And remember: a recall writeback records what happened during the recall process. It doesn’t necessarily mean the underlying clinical care is complete.