NEMT Passenger Fall Incident Report

Complete it as soon as the passenger is safe and the immediate response is underway, while details are still fresh. It is meant for falls that happen during boarding, in transit, or while alighting from a non-emergency medical transport vehicle. If the event did not involve a fall, use a different incident form. Prompt completion helps preserve an accurate audit trail.

The driver, attendant, dispatcher, or on-scene supervisor can complete it, depending on who observed the event and who has the most accurate details. The reporter should be the person best positioned to record the timeline, location, passenger status, and immediate actions. A supervisor can review and supplement the record after the initial submission. The key is to avoid secondhand guessing when direct observation is available.

It captures the submission notice, incident timing and location, vehicle and trip identifiers, a plain-language fall description, passenger information, injury and medical response details, witness statements, immediate actions, scene conditions, and corrective action notes. It also includes an attachment field for photos or supporting documents. The structure is designed to support follow-up review without collecting unnecessary data. Keep entries specific and factual.

Yes. Use only the passenger identifier and assistance status needed to document the incident and support follow-up. Avoid collecting extra PII that does not help explain the fall or the response. If your organization uses a passenger ID instead of a full name, that is often better for data minimization. Add consent or disclosure language if your workflow requires it.

Common mistakes include leaving the incident phase blank, writing vague descriptions like 'lost balance,' and failing to record what happened immediately after the fall. Another frequent issue is skipping witness details or not noting scene conditions such as wet steps, poor lighting, or mobility aid use. Reports are also weakened when corrective action is left generic instead of tied to the actual cause. The form works best when each field is completed with concrete facts.

It creates a consistent record of what happened, who observed it, what assistance was provided, and what follow-up was required. That structure helps supervisors review the event, compare accounts, and identify whether a vehicle, route, or boarding process contributed to the fall. The attachment field can preserve supporting evidence such as photos or notes. A clear timeline is often more useful than a long narrative.

Yes. You can add conditional logic for injury severity, wheelchair or walker use, or whether emergency services were contacted. You can also rename fields to match your dispatch system, add required vs optional rules, and include an anonymous submission option if your workflow needs it. Keep the form lean and only expand it where the extra data will be used. That helps maintain usability and reduces incomplete submissions.

The submission should route to a supervisor, safety lead, or compliance reviewer for follow-up and corrective action. The reviewer should confirm whether medical attention, passenger notification, vehicle inspection, or staff retraining is needed. The form should make that handoff explicit so the reporter knows the report was received and what happens next. If your process includes an audit trail, this is the place to capture it.