Coding and Exception Reporting for Recalls
Introduction
Importance of Correct Coding
Using the correct codes ensures that:
Recalls are recorded accurately in the patient’s record.
Practices can track patient engagement and identify those needing further outreach.
QOF compliance is maintained, preventing lost income due to unmet targets.
Key Codes for Recall Documentation
For all recall invitations, Primary Care IT suggests that the same code: QOF quality indicator-related care invitation (Concept ID: 1109921000000106) is applied to the patient’s record:
Exception Reporting for Non-Responders
If a patient does not engage with recall efforts after multiple invitations, practices may apply exception reporting to ensure compliance.
Eligibility for Exception Reporting
Patients may be exception reported if they:
Have received at least two documented invitations but did not respond.
Have declined the recall in writing or verbally.
Are deemed unsuitable for recall due to clinical judgment (e.g., end-of-life care, severe mental health conditions).
Key Codes for Exception Reporting
Closing a Recall Episode
Once a recall has been actioned or exception reporting applied, it is important to correctly close the recall episode.
Steps to Close a Recall:
Double-click on the OneRecall alert in EMIS.
Select the appropriate action:
Record the review as completed.
Apply exception reporting if necessary.
Set an interim follow-up if further review is needed before the next scheduled recall.
Save the record, ensuring correct codes are applied.
Best Practices for Coding and Exception Reporting
Maintain a consistent approach – Ensure all staff follow the same coding structure to avoid discrepancies.
Audit recall data regularly – Run searches to identify uncoded recalls or incorrect exception reporting.
Use clear documentation – Add notes where necessary to justify exception reporting decisions.
Next Steps
Now that recall coding and exception reporting are covered, the next article will focus on reviewing patients identified in OneRecall and ensuring follow ups in EMIS
Related Articles
Managing Non-Responders and Follow-Up Recalls
Introduction The Primary Care IT lesson on implementation of OneRecall contains more detailed stepped instructions Not all patients respond to initial recall invitations. Effective management of non-responders ensures that patients receive necessary ...Managing Patient Queries and Concerns about Recalls
Introduction The Primary Care IT lesson on implementation of OneRecall contains more detailed stepped instructions Patients may have questions or concerns about their recalls, including why they are being recalled, how to book an appointment, and ...Finalising OneRecall: Reporting, Performance Review, and Continuous Improvement
Introduction The Primary Care IT lesson on implementation of OneRecall contains more detailed stepped instructions Once OneRecall is fully implemented, it is essential to regularly review performance, track recall completion rates, and refine ...030 NHS Health Check Reporting
The NHS Health Check reporting searches in folder 030 as provided to help Practices report their NHS Health Check activity for the previous quarter. A separate folder of searches (020C NHS Health Check) is provided to help the Practice's invitation ...OneTemplate Coding
Purpose: This template is for use by clinical coders when receiving external communications from other agencies. What does it actually do? It is designed to contain everything a clinical coding team would need to process letters, record relevant ...