Incident and Error Reporting in the NHS Lab: What Every Biomedical Scientist Should Know
Incident and Error Reporting in the NHS Lab: What Every Biomedical Scientist Should Know
Errors happen in every healthcare setting, including the laboratory. What matters is not that mistakes occur, but how they are identified, reported, investigated, and prevented from recurring. Understanding incident reporting is a fundamental competency for Biomedical Scientists and a topic that appears frequently in NHS interviews across all bandings.
Types of Laboratory Incidents
Laboratory incidents are typically categorised according to where in the testing process they occur. This framework helps identify patterns and target improvements effectively.
Pre-Analytical Errors
Pre-analytical errors account for the majority of laboratory incidents — estimates suggest up to 70% of all laboratory errors occur before the sample reaches the analyser. Common examples include:
- Incorrect patient identification — wrong patient labelled on the sample
- Haemolysed, clotted, or insufficient samples — rendering them unsuitable for analysis
- Incorrect sample type — blood collected into the wrong tube or anticoagulant
- Transport delays — samples not reaching the laboratory within acceptable timeframes
- Request form errors — missing clinical details, wrong tests requested, or illegible handwriting on paper forms
Analytical Errors
These occur during the testing process itself and include:
- Analyser malfunction producing inaccurate results
- Reagent deterioration or use of expired materials
- Calibration failures not detected by quality control
- Operator error — incorrect dilutions, wrong method selection, or sample mix-up on the analyser
Post-Analytical Errors
Post-analytical errors occur after the result has been generated:
- Transcription errors — results entered incorrectly into the LIMS
- Results issued on the wrong patient record
- Failure to communicate critical results within the required timeframe
- Inappropriate clinical interpretation or incorrect reference range applied
- Delayed result authorisation causing clinical impact
The Datix Reporting System
Most NHS Trusts use Datix (or the newer Datix Cloud IQ) as their incident reporting system. Datix provides a standardised electronic platform for recording, investigating, and tracking incidents across the organisation.
When you identify or are involved in a laboratory incident, the expectation is that you report it on Datix promptly. The report should include a factual description of what happened, when it happened, who was involved, what immediate action was taken, and what the actual or potential impact on the patient was.
Datix reports are reviewed by the laboratory quality team and, depending on severity, may be escalated to departmental management, the Trust's governance team, or external bodies. The system allows tracking of trends over time, which is essential for identifying systemic issues rather than just one-off events.
Root Cause Analysis
For significant incidents, a Root Cause Analysis (RCA) is carried out to understand not just what happened, but why. The aim is to look beyond the immediate cause and identify the underlying system failures that allowed the incident to occur.
Common RCA tools used in NHS laboratories include:
- Fishbone (Ishikawa) diagrams — categorising contributing factors under headings such as people, process, equipment, environment, and materials
- 5 Whys technique — repeatedly asking "why" to drill down from the surface cause to the root cause
- Timeline analysis — mapping out the sequence of events to identify where the process broke down
No-Blame Culture and Duty of Candour
The NHS promotes a no-blame (or just) culture around incident reporting. The principle is that staff should feel safe to report errors without fear of punitive action. This is essential because under-reporting of incidents is one of the greatest risks to patient safety — problems that are not reported cannot be fixed.
This does not mean there is no accountability. Deliberate harmful acts, reckless behaviour, or repeated failures to follow established procedures are treated differently. But genuine errors made in good faith, when reported openly, should be treated as learning opportunities.
Duty of candour is a legal and professional obligation. When an incident causes harm or has the potential to cause harm to a patient, the organisation must inform the patient (or their family), apologise, and explain what happened and what steps are being taken to prevent recurrence. The HCPC Standards of Conduct, Performance and Ethics also require registrants to be open and honest when things go wrong.
Transfusion-Specific Reporting: SHOT and SABRE
Blood transfusion laboratories have additional reporting obligations due to the critical safety risks associated with transfusion.
- SHOT (Serious Hazards of Transfusion) is the UK's independent haemovigilance scheme. It collects and analyses reports of adverse events and reactions related to transfusion. Participation is voluntary but strongly expected. SHOT publishes an annual report identifying trends and making recommendations for practice improvement.
- SABRE (Serious Adverse Blood Reactions and Events) is the MHRA's mandatory reporting system for serious adverse reactions and events related to blood components. Reporting to SABRE is a legal requirement under the Blood Safety and Quality Regulations 2005.
How Incidents Link to ISO 15189 and Quality Management
Incident reporting is a core requirement of ISO 15189:2022, the standard against which NHS laboratories are accredited by UKAS. The standard requires laboratories to have a documented procedure for identifying, recording, and managing non-conformities and incidents.
Specifically, laboratories must demonstrate:
- A clear incident reporting procedure accessible to all staff
- Timely investigation of incidents with root cause analysis where appropriate
- Documented corrective and preventive actions (CAPA)
- Evidence that learning from incidents is shared with staff
- Trend analysis of incidents to identify systemic issues
- Regular management review of incident data
What to Do When You Make an Error
If you make an error or discover one, follow these steps:
1. Ensure immediate patient safety — if a result has been issued incorrectly, contact the requesting clinician immediately to prevent clinical harm 2. Preserve the evidence — do not discard samples, printouts, or other materials that may be needed for investigation 3. Inform your supervisor or section lead promptly and honestly 4. Complete a Datix report with a factual, objective account of what happened 5. Participate in the investigation openly, providing all relevant information 6. Reflect on the incident as a learning experience and document this in your CPD record
Attempting to cover up an error is far more serious than the error itself. Openness and honesty are professional obligations under the HCPC Standards.
Common Interview Questions
Interviewers frequently explore your understanding of incident reporting. Be prepared for questions such as:
- "Tell me about a time you made an error in the laboratory. What did you do?"
- "How would you handle discovering a colleague has made a mistake?"
- "What is the purpose of incident reporting?"
- "How does a no-blame culture differ from no accountability?"
Key Points
- Laboratory errors are categorised as pre-analytical, analytical, and post-analytical, with pre-analytical errors being the most common
- Datix is the standard NHS incident reporting system — all staff are expected to report incidents promptly
- Root cause analysis looks beyond the immediate cause to identify systemic failures and drive improvement
- The NHS promotes a no-blame culture to encourage open reporting, supported by the duty of candour
- Transfusion incidents require reporting to SHOT (voluntary haemovigilance) and SABRE (mandatory MHRA reporting)
- Incident management is a core requirement of ISO 15189 accreditation
- If you make an error, prioritise patient safety, report honestly, and treat it as a learning opportunity