The Last Mile of Notification: Auditing Receipt and Action in UK Pathogen Reporting

Notifiable pathogen reporting is often audited at the point of dispatch. A laboratory can show that a result was authorised, that a notification was generated, and that a message left the building. It cannot, from that evidence alone, show that a clinician saw the result, understood its significance, or initiated the right response. For notifiable pathogens, that gap matters. Statutory notification to the UK Health Security Agency is one duty; clinical escalation is another. An audit that treats the two as a single transaction will miss the last mile.

The gap between dispatch and action

In 2026, many UK laboratories work within mixed electronic environments. A result may be validated in the laboratory information management system, pushed to a secure clinical messaging channel, copied to an infection prevention and control inbox, and notified separately to UKHSA. Each step can succeed technically while the loop remains open clinically. Out-of-hours working makes the problem sharper: an on-call clinician may be contactable only through a switchboard, a ward may be using a generic inbox, or a secure message may sit unread until the next routine check.

The audit question is therefore not simply whether the laboratory sent the result. It is whether the laboratory can produce a defensible account of receipt, acknowledgement and action. That is a governance question, not a communications preference.

What counts as closure?

A useful closed-loop audit defines four states. The first is dispatch: the result has been sent by the intended route to the intended destination. The second is receipt: there is evidence that the message arrived, such as an electronic delivery receipt, a read receipt, a telephone log, or a contemporaneous note of a verbal handover. The third is acknowledgement: a named clinician or responsible team has accepted the result. The fourth is action: there is a documented clinical or infection control response, or a documented decision that no further action is required.

A read receipt is not clinical acknowledgement. An acknowledgement without a recorded action is not closure. The distinction protects both laboratory and clinical teams. It also prevents an audit from collapsing into a count of messages sent, which is easy to produce and weak as assurance.

Designing the audit

Start with a defined sampling frame. Include notifiable organism results over a fixed period, stratified by organism or local risk rating, time of day, route of communication and receiving ward or department. A practical approach is to review 30 to 50 cases per stratum where volume allows, with deliberate inclusion of weekends, bank holidays and out-of-hours periods. Review the laboratory system, secure messaging records, telephone logs, ward notes and infection control records together. Apply data minimisation and record only what is needed to test the pathway.

The audit should separate statutory notification from clinical escalation. A notification to UKHSA does not discharge the laboratory's responsibility to communicate a clinically urgent result to the treating team, and a clinical message does not replace a statutory notification. The two records should be linked by case identifier, not merged into one timestamp.

The audit template

A workable template records the following fields for each case:

• Case identifier and organism
• Notification category and local risk rating
• Time the result was authorised
• Time the statutory notification was sent to UKHSA
• Time the clinical result was sent and the route used
• Destination and named recipient or team
• Receipt evidence and timestamp
• Acknowledgement by a named clinician or team, with timestamp
• Local escalation timer, set by risk
• Escalation performed, with time and method
• Documented action: review, treatment, isolation, infection control advice, or a recorded decision that no action was required
• Ward feedback recorded
• Exception code and assigned owner

Escalation timers should be locally agreed and risk-based, not presented as national standards. A suggested local scheme might use 30 minutes for urgent out-of-hours results, four hours for routine in-hours results, and a next-working-day threshold for low-risk results that still require acknowledgement. The exact figures matter less than consistency, visibility and review.

Exception logs and timers

Not every delay is a failure, but every exception needs a code and an owner. Useful exception categories include no receipt evidence, receipt without acknowledgement, acknowledgement without documented action, wrong destination, outdated contact details, duplicate messaging, out-of-hours delay and system downtime. Record the time taken to close each exception and review the log weekly. Look for patterns by route, ward and time of day rather than ranking individuals. If the same ward repeatedly fails to acknowledge, the correct response is to examine workflow and staffing, not to issue a generic reminder.

Ward-level feedback metrics

A closed-loop audit should produce a small set of metrics that ward managers and infection control teams can use. These include the proportion of cases with receipt confirmation, the proportion acknowledged within the local timer, the proportion with documented action, the time to close exceptions, the repeat exception rate by ward or route, and the completion rate of feedback to clinical teams. Report aggregate figures with caution where numbers are small. Share the results with ward managers and ask what would make acknowledgement easier. An audit that adds a second inbox without removing friction will fail.

Out-of-hours is the stress test

Most reporting loops are weakest at night and at weekends. A retrospective tracer of overnight and weekend notifications should check who was on call, how contact was made, when the result was acknowledged and whether the action was recorded. Contact details should be tested quarterly, including bank holidays. Failed contact attempts should be documented as part of the audit trail, not reconstructed later from memory.

Governance and re-audit

Report the audit monthly to laboratory governance, infection prevention and control, and patient safety forums. Assign an executive owner and set a re-audit date after any pathway change. The audit should align with statutory notification requirements and local incident reporting, not duplicate them. Its purpose is to prove the chain, identify where it breaks, and fix the break.

A notifiable result is a clinical handover, not a postal event. The laboratory's assurance question is not whether the message was sent, but whether receipt and action can be demonstrated. That is a harder standard. It is also the one that patients and public health depend on.