Guessing at the cause
Write what happened, not why you think it happened. Causes belong in the review, where the team checks facts before deciding anything.
Healthcare & MedicalForms
Clinical incident report form: facts in order, no blame
A clinical incident report form records an event that did or could have affected a patient's care or safety, such as a medication mix-up, a fall or an equipment failure, along with the facts a reviewer needs to understand it. It should capture what happened in order, who was involved by role, what was done at the time and whether the patient was harmed, without guessing at causes. An urgent event is handled first through your emergency and escalation process, and the written report follows.
A filled example
A completed example with invented details, for a near miss
Example only, not a real submission
- Date of the event
- March 3, 2026 (example)
- Approximate time
- About 2:30 pm
- Where it happened
- Medication room, first floor
- Reporter's role
- Nurse on duty
- Patient reference
- Internal reference CI-0427
- Type of event
- Medication-related: a label did not match the order
- What happened
- A dose was prepared from a label that did not match the order. A second check caught the mismatch before anything was given.
- Immediate actions taken
- The dose was set aside, the ordering clinician was told, and the second check was completed before anything else happened.
- Possible harm
- No harm: caught before the patient received it
Field blueprint
Facts to capture, in the order a reviewer needs them
| Field | Type | Required | Why you ask it |
|---|---|---|---|
Date of the event | Date | Required | Ties the report to a day, so the review and any later deadline can be checked. |
Approximate timeFor example, about 2:30 pm. Write unknown if you cannot tell. | Short text | Required | The order of events matters in the review. A rough time is enough. |
Where it happenedExam or treatment roomProcedure areaMedication roomWaiting areaLaboratoryOther (describe in what happened) | Dropdown | Required | Points the review to the process that applies in that place. |
Reporter's roleClinicianNurse or clinical staffFront desk or administrative staffOther | Dropdown | Required | Tells reviewers which part of the event the reporter saw first-hand. |
Patient referenceUse the internal reference your quality team gives you, not the patient's full name, unless your process requires otherwise. | Short text | Required | Links the report to the right case without spreading identifiers through the report. |
Type of eventMedication-relatedFall or injuryEquipment or device problemWrong patient or wrong procedureCommunication or handoff problemOther | Single choice | Required | Tells the reviewer which group handles that kind of event. |
What happenedDescribe the facts in order: what was seen, done and said. Leave out guesses about the cause. | Long text | Required | This is the main account the review starts from. |
Immediate actions takenSay what was done at the time, and by role rather than by name. | Long text | Required | Shows whether the patient was kept safe while the event was being handled. |
Possible harmNo harmPossible harm, still being assessedHarm occurredNot sure yet | Single choice | Required | Helps the team decide how quickly to respond, using the categories your policy defines. |
Other people who saw itRoles only, such as pharmacy technician. | Short text | Optional | Identifies people who can add facts to the review. |
Reporter email | Required | Lets the quality team ask follow-up questions about the facts. | |
Limits of this reportI understand this report does not replace emergency care or my clinic's urgent escalation | Multiple choice | Required | Makes clear that the form is the written record, not the response to an urgent event. |
Mistakes to avoid
Mistakes that weaken the report or expose people
Naming people or the patient in the narrative
Use roles, such as the nurse on duty, and the internal reference. A name typed into free text is hard to remove once it reaches the grid or an export.
Using the form as the emergency response
If a patient is in danger, treat the patient and use your emergency process first. The form is the written record, not a call for help, and a new report reaches the creator only after the hourly production run.
Leaving out near misses
An error caught before it reached the patient is still information. Report it under the event type that fits, and say how it was caught.
Sending clinical reports to Customer Care by default
The optional Customer Care case is built for customer requests. Turn it on only if your quality team works its queue there, and keep clinical reports out of it otherwise.
After a response arrives
Route each report to the people who own it
Name the reader and the escalation route
Decide who reads each new report on the same working day, and how urgent events are escalated, by phone or in person, as your policy says. The creator is notified after processing, so the escalation route cannot depend on that notice.
Restrict the grid and the exports
The grid and CSV export contain sensitive narrative. Decide who can view and export submissions, and where any copies are kept.
Move the final record into your quality system
Copy the reviewed report into the system where your retention and access rules apply. The form is an intake point, not the file of record.
Send other reports to other routes
A staff injury uses the workplace incident process, and a complaint from a patient or family goes through complaint handling. Tell reporters where each one goes before they start.
Working checklist
Before you submit, check these items
Before you start
- Check that the patient is safe and that the clinical team knows what happened
- Note when you first became aware of the event
- Keep any equipment or medicine as found, if your policy says to
Facts to capture
- What happened, in order, with approximate times
- Who was involved, by role
- What was done at the time, and by whom, by role
- Whether the patient was harmed, as far as is known
Before you submit
- Remove names of patients and other people from the free-text boxes
- Choose the harm category your policy defines, or Not sure yet
- Use the escalation route for anything urgent, then submit the report
Frequently asked questions
What belongs on an incident report form?
The date, an approximate time, the location, the reporter's role, the type of event, the facts in order, the immediate actions and whether the patient was harmed. Leave out opinions about blame and personal details the review does not need.
Is a clinical incident report the same as a workplace incident report?
No. A workplace report covers injuries and hazards for staff and visitors under your workplace process. A clinical report covers events that affected or could have affected patient care or safety. Some events need both, so write down which process applies to each one.
Can I attach a photo or a document to the report?
Not in this form. Attain OS does not accept file uploads, so keep photos and documents in the system your quality team uses, and refer to them in the report by reference.
Should clinical incident reports be anonymous?
That depends on your reporting policy. Protection for people who report safety events varies with policy and law, so ask your counsel which protections apply before you promise any reporter one.
Browse by category
More reports in Healthcare & Medical
Intake forms
Insurance Information Update
Consent forms
Medical Records Release
Intake forms
Patient Intake Form
Surveys
Patient Satisfaction Survey
Orders
Prescription Refill
Consent forms
Telehealth Consent
How to build it
Choose a category and a form type in the wizard. Answer three Atty Suggestions questions, then give the form a title. Atty builds the fields in the background. Edit the fields and ask Atty to refine them, then publish and share the /f/ link.
