Incident review: change the system instead of hiding the error

An incident may involve an adverse event, possible ocular exposure, cooling failure, treatment of the wrong area, documentation failure or a break in clean workflow. Immediate actions protect the affected person; the subsequent review protects future clients.

Stop and provide care first

Unusual pain, epidermal discolouration, blistering, skin injury, cooling failure, smoke or possible eye exposure requires treatment to stop. Place the device in a safe state, assess the client through the approved pathway and arrange medical care according to urgency. Visual symptoms after possible eye exposure require urgent ophthalmic evaluation.

Documentation begins immediately: time, treatment area, observed signs, client words, device, parameters, cooling, protection, actions and people in the room. Photographs are taken only with consent and stored securely. You cannot edit the treatment record retroactively without a change log or ask colleagues to agree on a convenient version.

Build the chronology without accusation

Each participant separately describes what they saw and did. The questions are built around the process: what information was available, what the interface showed, how the device was checked, what interruptions occurred. The wording “why were you inattentive?” assigns a reason in advance and hides the conditions.

Save the device log, service messages, map, schedule, training and consumables status. The fact is separated from the conclusion: “the cooling ceased to be felt after the signal” is different from “the practitioner broke the cooling.” If the data are unknown, this is noted.

• Stop treatment, assess the client and complete any mandatory notification.
• Preserve the treatment record, device logs, consented photographs, equipment and relevant consumables.
• Assign follow-up contact with the client and one person in charge.
• Separate immediate risk limitation from final cause analysis.

Look for causes at several levels

The action immediately preceding an incident is rarely the only explanation. Review the interface, attachment labels, access to the IFU, staff authorisation, workload, shift handover, servicing, lighting, noise and the ability to stop. If two devices look alike and the system does not require model confirmation, an operator error is also a process-design failure.

Analysis does not remove personal responsibility where it applies, but does not end with punishment. The question is: what change will make a safe action easier and more noticeable, and a mistake more difficult? The answer may be an access restriction, clearer labelling, a competency check, supervised training or rescheduling affected clients.

Verify that the corrective action works

The corrective action receives an owner, a due date, and a completion criterion. “We had a conversation” does not show new reliability. The team tests the updated workflow with scenarios, looks at the following treatment records and checks whether the measure has created a different risk. The temporary restriction is lifted only after documented clearance.

The client receives honest information, follow-up contact and a channel for questions, in line with policy and legal requirements. Details of the incident must not become a training post containing recognisable information. For learning, use an anonymised account of the causes and decisions. Transparency means verifiable correction, not public disclosure of someone else’s story.