Tip · EMIS/SystmOne · 23 Jun 2026 · 2 min read

SystmOne: build a weekly safety net for unsent referrals

One practice used SystmOne reporting and Batch Reporting to catch referral letters that were written but never coded as sent.

01 / What's changed

In a case study published by TPP in April 2026, a practice built a report finding patients who had a referral letter generated but no matching referral code added afterwards.
Referrals had sometimes slipped through between a GP writing the letter and the secretaries sending it. The practice started with Two Week Wait referrals.
The report runs automatically each week using Batch Reporting, and SystmOne creates a task for the secretarial team with the patient list to work through.

Practices using SystmOne, especially those where referral letters pass between clinicians and an admin team.

Map your referral steps and note which code, if any, is added when a referral is actually sent. The report only works if that step is coded consistently.
Build a report for patients with a referral letter but no sent code, starting with your highest-risk referral type.
Test it with your management team before handing it over. The practice in the case study tested for two weeks before rolling it out.
Schedule it weekly and route the results as a task to a named team, not an individual. TPP's reporting page says reports can be scheduled with a notification when results are ready.