Last updated on Wednesday, 21, October, 2026
Table of Contents
Punjab Healthcare Commission MSDS: How to Document Patient Safety Incidents and Sentinel Events
Under the Punjab Healthcare Commission (PHC) MSDS, a hospital must define sentinel events in writing, monitor adverse events such as medication errors and unplanned returns to theatre, and analyse serious events in depth, with corrective action written down. A named quality improvement coordinator and a multidisciplinary quality committee make sure it happens. These requirements sit in the Continuous Quality Improvement (CQI) area of the MSDS, not in the medical record standards.
This guide explains what the MSDS asks for, what to record when an incident happens, who should be responsible, and how to avoid the common gaps. It is based on the PHC MSDS for hospitals (2012 edition).
| Regulator | Punjab Healthcare Commission (PHC) |
| Framework | Minimum Service Delivery Standards (MSDS) for hospitals |
| Area | Continuous Quality Improvement (CQI) |
| Standards | 16 (CQI-1), 17 (CQI-2) and 18 (CQI-3) |
| Indicators covered here | 93, 95, 101 to 104, 106 and 107 |
| Applies to | Hospitals. Clinics and small facilities have their own PHC standards, so check the one for your category |
The MSDS has ten functional areas. For the full picture, see our guide to the Punjab Healthcare Commission MSDS.
What the PHC MSDS requires
The MSDS does not use the phrase “incident reporting”. It asks for three connected things: a structure to own quality and safety, monitoring of adverse events, and a defined process for sentinel events.
| Indicator | What the MSDS asks for | What a reviewer can check |
|---|---|---|
| 93 (Standard 16) | A multidisciplinary quality improvement committee with terms of reference, methods, reporting structure, minutes and defined responsibilities | The committee plan and minutes |
| 95 (Standard 16) | A designated quality improvement coordinator with a job description | The appointment and job description |
| 101 (Standard 17) | Monitoring of invasive procedures, including adverse occurrences, unplanned return to the operating room within 24 hours and related readmission within 24 hours | Committee minutes showing the monitoring |
| 102 (Standard 17) | Monitoring of adverse drug events, such as allergic reactions, wrong dose, wrong drug or wrong patient, and how each was managed | Committee minutes and the events recorded |
| 103 (Standard 17) | Reporting and follow-up of adverse occurrences related to anaesthesia | Reports and follow-up |
| 104 (Standard 17) | Reporting and follow-up of adverse occurrences related to blood and blood products | Reports and follow-up |
| 106 (Standard 18) | A written definition of sentinel events, with a minimum list (see below) | The written list |
| 107 (Standard 18) | Intensive analysis of sentinel events, with corrective action | Analyses from the past 12 months; if there were none, how the hospital would report and analyse one |
Indicator 107 is explicit about quality. An analysis that only blames an individual does not count. It should look at causes and contributing factors, and end in a corrective action such as a policy change or staff training.
What counts as a sentinel event
Indicator 106 asks each hospital to write its own definition of a sentinel event. The MSDS sets a minimum list that the definition should include:
- Unexpected deaths, including infants, mothers and suicides
- Serious adverse events that caused, or could have caused, harm, including unplanned return to the operating room within 24 hours, readmission within 24 hours, wrong patient, wrong site, wrong procedure and medication error
- Patient violence against staff
- Violence against patients
- Infant abduction
- Baby switching
The MSDS describes including near misses as good practice but does not require it. A hospital that also logs near misses gives its quality committee earlier warning, so consider adding them to your policy. The MSDS does not define “incident” or “near miss”, so write your own plain definitions and apply them the same way across departments.
What to document when an incident happens
The MSDS tells you what to monitor and analyse, not which form to use. The fields below are practical guidance, not PHC requirements. They are built so that the record can answer the questions a reviewer asks under Indicators 101 to 107: what happened, what you did, what you learned, and who owns the follow-up.
| Field | What to write |
|---|---|
| Reference number and date and time of the event | A unique incident number, and when it happened |
| Where it happened | Ward, theatre, emergency room or other area |
| Patient | Medical record number (use the number, not the name, when the record is shared with a committee) |
| Event type | Adverse drug event, procedure complication, anaesthesia, blood product, fall, violence, other; and whether it meets your sentinel event list |
| What happened | Facts only, in plain words, with no blame |
| Effect on the patient | Harm, if any, and the patient’s condition |
| Immediate action | What staff did at once, and who was told |
| Reported by | Name, role, date and time of the report |
| Analysis | Causes and contributing factors. For a sentinel event, a full review of what led to it |
| Corrective and preventive action | What will change: policy, training, equipment or process |
| Responsible person and due date | One named person per action, with a date |
| Status | Open, in progress, closed, with the date of review by the quality committee |
Many hospitals keep the incident record separate from the patient’s clinical notes, while the medical record itself still shows the facts of the patient’s care. For those rules, see our guide to PHC MSDS medical record requirements.
Who is responsible
The MSDS names two roles and leaves the rest to the hospital:
- The quality improvement coordinator (Indicator 95): a designated person with a job description who runs the quality programme day to day.
- The multidisciplinary quality committee (Indicator 93): reviews what is monitored, keeps minutes and holds departments to their actions.
The MSDS does not name a patient safety officer, and Indicator 107 does not say who must carry out an analysis. So write it down yourself. A workable split is practical guidance, not a PHC rule: any staff member can report; the department head checks the facts; the coordinator logs and tracks the case; the committee reviews every sentinel event; and each corrective action has one named owner and a due date.
That last point answers the question “who is the responsible staff member?”. An action with no owner, or an owner with no date, looks unfinished to a reviewer.
Where hospitals fall short
These are gaps to look for in your own hospital, each tied to what the MSDS asks. They are practical observations, not PHC findings.
- No written sentinel event list, or a list that leaves out items from the minimum set (Indicator 106).
- Events handled but not written down, so the quality committee never sees them (Indicators 101 to 104).
- Analysis that stops at “who made the mistake”, with no look at causes or contributing factors (Indicator 107).
- Corrective actions with no owner, no date and no follow-up.
- No quality committee minutes, or minutes that never mention safety events (Indicator 93).
- No designated coordinator, so no one tracks cases to closure (Indicator 95).
- Departments that report differently, because the definitions are not shared.
- A culture of blame, which teaches staff not to report.
How to put this in place: six steps
- Appoint the owners. Name a quality improvement coordinator and set up the quality committee, with terms of reference and a minute book (Indicators 93 and 95).
- Write your sentinel event definition. Start from the PHC minimum list and add what suits your services (Indicator 106).
- Set up one incident form. Use the fields in the template above, and make it easy for any staff member to submit.
- Monitor the key areas. Track invasive procedures, adverse drug events, anaesthesia and blood products, and review them in committee meetings (Indicators 101 to 104).
- Analyse serious events properly. Look for causes and contributing factors, not for someone to blame, and record the corrective action (Indicator 107).
- Close the loop. Give every action one owner and a due date, check it at the next committee meeting, and note the result.
The same action-log idea, applied to record reviews, is covered in our guide to corrective and preventive action in hospitals.
How InstaCare Hospital Management software can support incident documentation
Software does not make a hospital compliant. Compliance depends on your policy, your people and what they do after an incident. What a digital system can do is make the paperwork easier to keep and harder to lose.
When you look at any hospital system, check whether it can:
- Capture each incident on one structured form instead of loose papers.
- Route the report to the department head and the quality coordinator.
- Assign each corrective action to one named person with a due date, and show what is overdue.
- Keep a searchable log with the status of every case.
- Produce a summary for the quality committee’s meetings.
- Limit who can see incident details.
To see how InstaCare’s hospital management software handles records, access and reporting in a hospital, request a demo and ask how your incident workflow could be set up.
Frequently asked questions
What does the PHC MSDS require for patient safety incidents?
It asks hospitals to run a quality improvement programme with a committee and a coordinator, monitor adverse events in key areas, define sentinel events in writing, and analyse sentinel events in depth with documented corrective action (Indicators 93, 95, 101 to 104, 106 and 107).
What is a sentinel event under the PHC MSDS?
The MSDS does not give one definition. It asks each hospital to define its own and sets a minimum list: unexpected deaths, serious adverse events, violence against staff or patients, infant abduction and baby switching.
Do hospitals have to report incidents to the PHC?
The indicators covered in this guide do not set a requirement to report incidents to the PHC. Check the current MSDS and any PHC notice that applies to your category of hospital.
Is a near miss a sentinel event?
Not in the MSDS minimum list. The MSDS calls including near misses good practice, so it is optional but useful.
Who is responsible for incident follow-up?
The MSDS requires a quality improvement coordinator and a quality committee. Beyond that, give each corrective action one named owner and a due date.
Does software make a hospital compliant?
No. Software can help you record, assign and track incidents, but compliance depends on your policies and on what your staff do.
Request a demo to see how InstaCare’s hospital software could support your incident workflow.
