LAB-QM-010 — Occurrence and Deviation Management Policy
Type: Policy · Version: V0 · Status: DRAFT — UNAPPROVED · Served read-only from the bundled QMS copies. The Drive master is untouched.
Rendered in-browser from the project's Word file LAB-QM-010-occurrence-management-policy.docx (policies-docx / forms-docx — the file Junry reviews). Formatting is faithful, not pixel-perfect; the DOCX is the official copy.
1.0 Purpose
This policy establishes a systematic process for identifying, reporting, immediately containing, investigating, and tracking any occurrence, nonconformity, near-miss, or procedural deviation in the Tarangnan Community Hospital (TCH) Clinical Laboratory.
It ensures that events compromising laboratory quality, patient safety, or QMS integrity are addressed promptly through immediate correction and routed to corrective action, while providing clear governance for the authorization and control of planned and emergency deviations from approved procedures.
2.0 Scope
This policy applies to all Medical Technologists and Laboratory Aides across all sections of the TCH Clinical Laboratory. It governs all occurrences, safety incidents, adverse events, near-misses, client complaints involving quality issues, and procedural deviations (planned, unplanned, and emergency) encountered across pre-examination, examination, post-examination, and point-of-care testing (POCT) processes.
3.0 Definitions
- Occurrence — any event or circumstance associated with laboratory operations that departs from normal expectations or compromises service quality, patient safety, or QMS integrity, regardless of whether actual harm occurred.
- Nonconformity — the non-fulfilment of an established requirement, whether procedural, statutory, regulatory, or quality-related.
- Near-Miss — an unplanned event or error caught before affecting patient care, specimen integrity, or result reporting.
- Deviation — a departure from an approved laboratory policy, standard operating procedure, or specification.
- Planned Deviation — a temporary, pre-approved departure from written protocol necessitated by exceptional operational circumstances (e.g., equipment breakdown or manufacturer supply disruptions), approved prior to execution.
- Sentinel Event — an unexpected occurrence involving death or serious physical or psychological injury, requiring immediate hospital-wide escalation.
4.0 Responsibility
4.1 Hospital Director
- Approves this policy and provides institutional support and resources required for occurrence investigations, containment, and preventive system repairs.
- Receives immediate notification of sentinel events and reviews occurrence trends during Management Review.
4.2 Pathologist
- Clinically evaluates occurrences, deviations, and adverse events that impact patient safety or result validity.
- Reviews and authorizes planned deviations, clinical containment measures, and closure of major occurrence investigations.
4.3 Chief Medical Technologist / Laboratory Quality Manager
- Logs, classifies, and investigates all reported occurrences, incidents, and deviations using F-QM-010-A-V0.
- Implements immediate containment actions and coordinates with Corrective and Preventive Action Policy when root cause analysis and corrective action are warranted.
- Analyzes occurrence trends monthly and presents consolidated reports at quarterly CQI meetings and annual Management Review.
4.4 Medical Technologists
- Identify, immediately contain, and report technical occurrences, testing errors, equipment breakdowns, QC failures, or deviations within 24 hours (or immediately if patient safety is threatened).
- Document occurrence details accurately in F-QM-010-A-V0 and participate in root cause investigations.
- Adhere strictly to approved standard operating procedures and initiate planned deviation requests in advance when necessary.
4.5 Laboratory Aides
- Immediately report any specimen spill, handling accident, facility hazard, broken container, or physical discrepancy observed during support duties to a Medical Technologist or the Chief Medical Technologist.
- Follow safety and containment instructions promptly during incident response.
- Laboratory Aides do not perform, verify, authorize, interpret, or release technical examinations or results.
5.0 Policy / Procedure
5.1 Policy Statement & Non-Punitive Reporting Culture
- Mandatory Reporting: Any Medical Technologist or Laboratory Aide who discovers, is involved in, or observes an occurrence, incident, or deviation shall report it promptly.
- Non-Punitive Quality Culture: Occurrence reporting is an essential quality improvement mechanism designed to identify system weaknesses and prevent recurrence. Personnel reporting genuine errors, system faults, or near-misses shall not be subject to disciplinary retaliation. Any issue involving willful misconduct, gross negligence, or unauthorized intentional acts is handled separately under Internal Laboratory Rules and Regulations Policy, ensuring that the reporting function of this policy remains uninhibited.
5.2 Occurrence and Deviation Classification
- Classification by Type: - Pre-Analytical: Patient misidentification, improper phlebotomy collection, specimen mislabeling, inadequate volume, hemolysis, or transit delay. - Analytical: Equipment failure (HORIBA Pentra XLR, chemistry analyzer), calibration failure, unacceptable IQC results, or reagent degradation. - Post-Analytical: Reporting transcription error in the Excel LIS, delayed critical value notification, or lost laboratory record. - Procedural Deviation: Planned, unplanned, or emergency departures from written standard operating procedures. - Safety / Environmental Incident: Sharps injury, chemical or biohazard spill, electrical fault, or facility infrastructure failure. - Near-Miss: An error intercepted prior to specimen processing or result release.
- Classification by Severity: - Minor: No adverse impact on patient safety, result accuracy, or operational compliance (e.g., minor delay caught before clinical impact, transient non-systemic error). - Major: Actual or high-risk potential impact on patient care, clinical diagnosis, result integrity, or staff safety (e.g., erroneous report issued, mislabeled specimen tested, critical value notification failure). - Sentinel Event: An unexpected event involving death, permanent harm, or severe temporary harm, triggering immediate hospital-wide escalation.
5.3 Occurrence and Incident Reporting
- Timeframe: Occurrences shall be reported on F-QM-010-A-V0 as soon as possible during the same shift, and no later than 24 hours following discovery.
- Verbal Notification: Where an occurrence poses an active risk to patient health or involves an erroneously released test result, the discovering staff member shall notify the Chief Medical Technologist / Laboratory Quality Manager or attending physician immediately by telephone or in person.
5.4 Immediate Containment and Action
Upon notification or discovery of an occurrence, the discovering staff member and Chief Medical Technologist / Laboratory Quality Manager shall immediately implement containment controls (see Figure 1):
Figure 1 — Occurrence containment, severity triage, and escalation flow
- Halt affected testing or quarantine suspect analyzers, reagents, or supplies;
- Withhold or recall questionable examination results, and issue amended reports per Amended Results Policy if erroneous results were communicated;
- Secure immediate medical evaluation and prophylaxis for sharps injuries or biohazard exposures;
- Log the occurrence in the master log section of F-QM-010-A-V0.
5.5 Investigation and Routing to CAPA
- Investigation Process: The Chief Medical Technologist / Laboratory Quality Manager shall investigate the occurrence proportionate to its severity, documenting the sequence of events, direct and contributing causes, patient impact, and recurrence likelihood in F-QM-010-A-V0.
- Routing to Corrective Action: - Minor, isolated occurrences resolved through immediate correction may be closed locally in F-QM-010-A-V0. - Major occurrences, recurring minor trends, or systemic procedural failures shall be formally routed to Corrective and Preventive Action Policy for root-cause analysis (5 Whys or Fishbone diagram) and structured corrective and preventive action.
- Escalation to Sentinel Event Review: Any occurrence meeting the hospital sentinel event definition shall be immediately reported to the Hospital Director and Pathologist for hospital-wide sentinel event analysis.
5.6 Control and Authorization of Procedural Deviations and Exceptions
- Prohibition of Unauthorized Deviations: Performing laboratory examinations contrary to standard operating procedures or using expired reagents is strictly prohibited per DOH A.O. 2021-0037 Annex C Item A.5, unless authorized through this section.
- Planned Deviations: - When an unavoidable operational situation requires temporary deviation from a written SOP without compromising test accuracy or safety, the initiating Medical Technologist shall submit a deviation justification in F-QM-010-A-V0 in advance. - The Chief Medical Technologist / Laboratory Quality Manager reviews the risk impact, and the Pathologist provides written authorization before the deviation is implemented. - Approvals are valid for a single specified batch, event, or timeframe only.
- Unplanned and Emergency Deviations: Unplanned departures caused by sudden equipment breakdown or emergency departures necessary to protect patient life shall be documented immediately post-event in F-QM-010-A-V0 and submitted to the Pathologist for review within 24 hours.
5.7 Complaints, Safety Incidents, Adverse Events, and Trending
- Customer and Clinical Complaints: Complaints from patients or clinical users that reveal a laboratory quality or diagnostic concern shall be logged and investigated as occurrences under this policy. (Administrative feedback channels and resolution timelines are governed by Scope of Service and Laboratory User Information Policy).
- Safety and Adverse Events: Adverse events, staff injuries, and biohazard spills shall be documented in F-QM-010-A-V0 and reviewed with the hospital safety officer.
- Monthly Trending: The Chief Medical Technologist / Laboratory Quality Manager shall review all occurrence records monthly to identify recurring failure modes, analyzer vulnerabilities, or training deficits. Trend analyses feed the CQI Committee and Quality Indicators program under Continual Improvement and Performance Improvement Program Policy and annual Management Review under Management Review.
6.0 Records
| Form No. | Form Title | Parent Policy | Status | Version |
|---|---|---|---|---|
| F-QM-010-A-V0 | Incident, Occurrence, and Deviation Report & Log | LAB-QM-010 | Active (Draft) | V0 |
All records generated under this policy, including incident reports, deviation justifications, immediate containment logs, and investigation summaries, shall be controlled in accordance with Control of Records and retained per Laboratory Retention Schedule Policy.
7.0 References
- DOH-Philippines QMS Tool, Section 4 — Monitoring Performance; Section 5 — Quality Improvement Activities; Section 7 — Safety and Environment
- DOH Administrative Order No. 2021-0037, Annex A — General Guidelines; Annex B1 — Technical Standards for Clinical Laboratories; Annex C — Prohibited Acts
- ISO 15189:2022, Clause 7.5 — Nonconforming work; Clause 7.7 — Complaints; Clause 8.7 — Nonconformities and corrective actions
- WHO LQMS Handbook, Chapter 14 — Occurrence Management
Companion policies:
- Corrective and Preventive Action Policy — root cause analysis and corrective action for systemic nonconformities and major occurrences
- Risk Management — risk evaluation and updates to the laboratory risk register for identified hazards
- Internal Laboratory Rules and Regulations Policy — administrative handling of staff conduct separate from quality occurrence reporting
Controlled visual annex:
- IG-07 — Occurrence to CAPA — one-page visual annex to this policy (shared annex with LAB-QM-011), controlled under Document Control Policy Section 5.2.6 and registered in F-QM-002-B-V0. Master files: infographics/IG-07-Occurrence-to-CAPA-LAB-QM-010-011.png (PNG, print PDF, and editable HTML).
