By Ryan Smith  •  Updated: September 2026  •  9 Min Read

Quick answer: A compliant EMS documentation workflow captures medical necessity, level of service, and origin and destination on every run report, checks each report for completeness within a day or two of the transport, and trains crews to write narratives a payer reviewer can follow. It also controls how patient data moves between the field, the ePCR, and billing under HIPAA.

Documentation is where ambulance billing succeeds or fails, long before a coder touches the claim. A consistent documentation workflow protects revenue, shortens the time to payment, and protects the agency if a payer ever audits its claims.

Start with what payers actually require

Medical necessity, level of service, and origin and destination each have to be supported by the run report itself. They cannot be implied by the dispatch type, the crew’s certification level, or the fact that the call came through 911. Build documentation templates around these three requirements explicitly, rather than relying on a single free-text narrative field.

The five elements every run report should capture

What a strong narrative looks like

Compare two narratives for the same non-emergency transfer:

The second version gives a reviewer the specific facts that make ambulance transport necessary. Structured formats such as SOAP or CHART help crews include those facts consistently.

Signatures are their own compliance area

Medicare generally requires the patient’s signature authorizing the claim. When the patient is physically or mentally unable to sign, Medicare allows specific alternatives, such as an authorized representative or a crew member statement supported by records from the receiving facility. Train crews on these rules, because a missing or improper signature can make an otherwise well-documented claim unbillable.

For non-emergency transports, track the PCS

Scheduled, repetitive non-emergency transports require a Physician Certification Statement dated no earlier than 60 days before the transport, and unscheduled non-emergency transports should have one obtained within 48 hours after the trip. The PCS supports medical necessity, but it does not replace the crew’s narrative. Payers expect the two to agree.

Build compliance checks into the workflow, not after it

Agencies with fewer denials tend to review documentation completeness within 24 to 48 hours of the transport, while the crew can still recall and correct details. A same-shift or next-shift QA review catches far more than a monthly audit does. Set clear rules for which gaps send a report back to the crew, such as a missing signature, a missing mileage reading, or a narrative that does not explain medical necessity.

Train for the documentation, not just the protocol

Clinical protocol training teaches crews what to do. Documentation training teaches them how to write down what they did in language a payer’s medical necessity reviewer will recognize. Both matter, and they are not the same training. Short, recurring sessions built around real (de-identified) run reports from your own agency tend to stick better than annual lectures. Our guide to ALS and BLS modifier combinations is a useful companion for this training.

HIPAA and data handling

A compliant workflow also controls how patient information moves between the field, the ePCR system, and the billing team: encrypted transfer, access limited to staff who need it, and an audit trail showing who touched a record and when. Any outside billing company that handles your patient data should sign a Business Associate Agreement. A clean audit trail also makes it easier to answer a payer’s request for additional documentation quickly. You can read how we handle this in our HIPAA notice.

Documentation gaps are the leading source of the most common ambulance billing denials. Our ambulance coding service reviews run reports for medical necessity and flags gaps back to crews before claims go out.

Frequently asked questions

What makes an ambulance run report support medical necessity?

It describes the patient’s specific condition and explains why any other means of transport would have endangered them. Useful details include vital signs, mental status, mobility limits, the need for monitoring or oxygen, and anything that prevented the patient from sitting upright or traveling safely.

Who can sign the claim if the patient is unable to sign?

Medicare allows alternatives when the patient is physically or mentally unable to sign, including an authorized representative or a crew member statement supported by documentation from the receiving facility. The reason the patient could not sign should be recorded on the run report.

How soon after a transport should documentation be reviewed?

Ideally within 24 to 48 hours, while the crew can still recall details and correct gaps. Reviews done weeks later, at the time of billing, often find problems that can no longer be fixed.

Does a PCS replace the crew’s narrative?

No. A Physician Certification Statement supports medical necessity for non-emergency transports, but payers still expect the run report to describe the patient’s condition. The PCS and the narrative should agree with each other.

Want a second opinion on whether your documentation would hold up in a medical necessity review? Request a free billing audit and we’ll walk through a sample of your recent run reports with you.