Where the work can stall
Referral documents can arrive through several channels and require careful entry into a practice system. Missing details create follow-up work, while recalls and administrative reminders compete with front-desk priorities.
This example is deliberately limited to administration. Clinical urgency, diagnosis, treatment, eligibility and triage remain outside the workflow.
A possible workflow
- Receive referrals through approved channels and retain the source document within the practice's controlled environment.
- Extract administrative fields such as referrer, patient details, referral reason as written and relevant dates.
- Flag missing or uncertain information and prepare a follow-up draft for reception staff.
- Use approved appointment rules to prepare recall and reminder drafts for staff review or an existing authorised sending process.
- Record who reviewed each item and keep clinical content out of generated administrative decisions.
What good operation looks like
A privacy and security assessment comes before implementation. The practice decides where information is processed, who can access it, what is logged and how long records are kept.
The system makes uncertainty visible and routes any clinical question to an appropriately qualified person.
Where people stay responsible
This example excludes diagnosis, clinical advice and autonomous urgency decisions. Any real implementation needs privacy and clinical governance assessment.
- Practice staff verify extracted patient and referral information against the source.
- No clinical decision, urgency assessment or treatment recommendation is generated.
- Health information stays within systems and configurations approved by the practice.
- Messages follow the practice's consent, identity-checking and communication procedures.
Limitations to test
- Scans, handwriting and incomplete referrals can make extraction unreliable.
- Administrative language can still carry clinical significance and must be escalated when uncertain.
- Health information requires stronger governance than a general office workflow; convenience does not lower that obligation.
Measuring it
Test routing accuracy and escalation failures using an approved evaluation set before considering real information.
Agree the test sample, measurement period and acceptance criteria before a pilot. Include checking, corrections and running costs when comparing the proposed workflow with the current process.
Our evidence and corrections policy ↗