Reporting what went wrong — and what nearly did
Every clinic has incidents: a patient's file opened under someone else's name, an allergy nobody read, a fall in the waiting room. Only a fraction are ever reported, and the reason is rarely carelessness — it is fear of blame. This guide explains how reporting becomes a safe habit, and how patient complaints are handled until they are closed.
Every clinic has mistakes, however capable its staff: a patient's file opened under another patient's name, a recorded drug allergy nobody read before the prescription, a sample sent with the wrong label, an elderly patient who falls in the waiting room. Most of what happens never reaches any record — not from neglect, but because whoever saw it found no reason to write it down and plenty of reasons not to.
A reporting system is not a form to fill in; it is a habit to build. This guide explains how: what to report, how to grade harm, who reviews, when a report is closed — and then how patient complaints are handled, each with its own answer date.
Why reporting has to be free of blame
If reporting a mistake means the reporter gets blamed, reporting stops — and the first thing to disappear is the near miss: the error caught before it reached the patient, the cheapest lesson a clinic can learn. That is why the Dubai Health Authority's standards for managing sentinel events state plainly that they are not designed to assign blame, but to find and solve problems.
No blame does not mean no accountability. A review looks at what happened and why: an unclear procedure, pressure on the appointment book, a faulty device, two files with similar names. Deliberate recklessness or repeated disregard of procedures is dealt with through its own HR route, not in the incident register.
What to report
- Falls in the clinic or from an examination chair.
- Medication errors: wrong drug, dose or patient, or an allergy not respected.
- Unexpected procedure complications.
- Missed or delayed diagnosis, including a test result nobody looked at.
- Infection and sterilisation: an instrument not sterilised as it should have been, or an infection linked to the clinic.
- Equipment failures that affected, or nearly affected, a patient.
- Wrong patient identification: a file, sample or prescription for someone else.
- Security and aggression towards staff or patients.
- Near misses: any of the above caught before it reached the patient.
A near miss is worth more than an incident
An error caught before it reached the patient exposes the same gap that will cause the next incident, without anyone paying for the lesson. A clinic that records many incidents and very few near misses does not have better safety; it has weaker reporting.
Grading harm
| Harm level | Example | Usual response |
|---|---|---|
| No harm | A wrong drug dispensed and caught before the patient took it | Routine review and learning |
| Minor harm | A small bruise after a fall | Routine review and follow-up with the patient |
| Moderate harm | An extra procedure the patient needed because of the error | Deeper review and a corrective plan |
| Severe harm | Permanent harm, or urgent hospital treatment | Immediate escalation; check whether the regulator must be told |
| Death | An unexpected death linked to care | Immediate escalation; notify the regulator as it requires |
Severe harm and death are what most regulators call sentinel events, and each regulator has its own reporting route and deadlines for them. A harm level may be changed after review, but the change must leave a visible trace: harm quietly downgraded after the event is exactly what an inspector looks for.
What regulators and accreditation bodies expect
The details differ from country to country, but the direction is the same: a written reporting system, a documented review, and sentinel events reported to the regulator within its deadlines. In Saudi Arabia, facilities working to the standards of CBAHI, the national accreditation body, run an occurrence and variance reporting policy alongside a sentinel event policy that calls for root cause analysis, and the Saudi Patient Safety Center, set up in 2017, defines a sentinel event as an adverse event that leads, or could lead, to catastrophic outcomes. In Abu Dhabi the Department of Health has a standard for incident reporting and management in the facilities it licenses, and in Dubai the Dubai Health Authority has standards for notifying and managing sentinel events.
The deadlines themselves — hours or days from discovery — differ between regulators and change between versions of their standards, so do not rely on a figure you heard somewhere. Read your regulator's current text, write the deadline into the clinic's procedure, and name who makes the notification.
From report to closed
Report the same day
What happened, when, with which patient if any, and what was done straight away. Describe facts, not judgements: the patient was given…, not the nurse neglected….
A quick read within a day
The owner or a manager reads the report and checks the harm grading. A report of severe harm or a death is escalated at once, and whether the regulator must be told is checked.
A review that looks for causes
What allowed the error: a procedure, the schedule, a device, communication? The questions are about why, not who.
Decide and act
What will change: a revised procedure, training, a change to a system — with who is responsible and by when.
Close with a written outcome
No report is closed until what the review found and what the clinic learned are written down. Then tell the reporter what changed — that is what makes them report again.
Patient complaints: a separate register, an answer date for each
A complaint is not an incident, though it may reveal one. A patient complains about waiting, about how a member of staff treated them, about a bill they did not understand, about a result nobody called them about. Record every complaint with how it came in — in person, by phone, by email, in writing, or in an online review — what it is about, and who made it and how to reach them.
Every complaint gets an answer date. In the markets we checked, we found no fixed legal deadline for answering complaints at private clinics, so set your own and keep to it: fourteen days is a reasonable outer limit, and a simple complaint is answered within days. A complaint left unanswered can end up with the regulator or in a public review; handling public reviews is covered in the guide to local SEO for clinics.
- Acknowledge the complaint quickly, even before you have a full answer.
- Give each complaint one owner who follows it until it closes.
- Do not close a complaint until the answer given to the complainant is recorded.
- Never discuss a patient's details in public, even when replying to a negative review; their health data is protected, as the patient data protection checklist explains.
- If a complaint reveals an incident, record it in the incident register too.
Who sees the reports
A reporter sees their own reports; the reviewers — the owner and managers — see all reports at their sites. Staff do not browse colleagues' reports, because a report that anyone might read will not be written honestly. And any change to a harm level or category leaves a trace in the activity log. For how to divide permissions more generally, see the guide to clinic staff roles and permissions.
The records you keep
- The incident register: date and time, category, harm level, patient if any, immediate action, who reviewed it, what they found, and the closing date.
- The complaint register: date received, channel and subject, the answer date, and the answer itself with its date.
- Evidence of learning: minutes of the meetings or training that followed reviews.
- What was reported to the regulator: when, what, and by whom.
A ten-minute monthly review
- Reports by category, and the share that are near misses.
- Reports still awaiting review, and complaints past their answer date.
- The theme that keeps recurring across incidents or complaints, even when each case is small.
- What actually changed after last month's reviews.
How 3yadtk handles incidents and complaints
3yadtk has an Incidents & complaints page in its menu. Any member of staff can report an incident or a near miss — when it happened, its category, the harm level from no harm to death, the patient if there was one, what happened and what was done straight away — and sees only their own reports. The owner and managers see and review every report at their sites, and a report cannot be marked reviewed or closed until what the review found is written down; any change to a report's harm level or category is recorded in the activity log. An open report of severe harm or a death shows in red on the bell, as one that is usually reportable to the regulator; the notification itself is the clinic's to make. Patient complaints are recorded with how they came in, what they are about, who made them and how to reach them; each gets an answer date 14 days from receipt, the bell flags those due within three days or late, and a complaint closes only once the answer is recorded.
Safe reporting, and no review closed without an outcome
A register for incidents and near misses where each person sees their own reports, reviews with a written outcome, and complaints with an answer date — on the one plan.
See the features