DCHART and DCHARTE: EMS Narrative Format and Examples

DCHART organizes an EMS narrative into Dispatch, Chief complaint, History, Assessment, Rx or treatment, and Transport. DCHARTE adds another section: in Wintergreen Fire and Rescue’s published format, E means Exceptions. Use the expansion required by your agency or course.

The practical goal is a readable patient-care report that shows where information came from, what the crew found, what care occurred and what happened next. NASEMSO includes DCHART among narrative formats that add context to structured documentation. National Model EMS Clinical Guidelines, page 371

This guide includes a complete written example, an exception-and-correction case, a transport-refusal excerpt and a blank worksheet. Examples are fictional. Paramedic educator review: pending. Sources checked October 23, 2026.

DCHART at a glance

• D — Dispatch: What the call information said, the response and arrival.
• C — Chief complaint: The patient’s presenting concern, with its source.
• H — History: Relevant reported circumstances, symptoms and background.
• A — Assessment: What the crew actually observed, examined or measured.
• R — Rx / treatment: What was done, by whom and when, followed by the response.
• T — Transport: Movement, destination, changes en route and disposition.
• E — Exceptions, where locally defined: A specific limitation or unusual event and its consequences.

For example, “dispatch reported a possible fracture,” “the patient reported ankle pain,” and “the crew observed lateral ankle swelling” are three different claims. None alone establishes a confirmed fracture. Preserve those distinctions when turning rough notes into polished prose.

DCHART, DCHARTE and local variants

Use the structure required by your service. The table compares each source’s format and publication date.

Geographic scope: These operational sources are U.S.-based. In Canada, use your provincial authority’s and service’s requirements for narrative structure, record completion and corrections.

Wintergreen’s Appendix A connects transport documentation to the receiving person and describes signature difficulties as an example of an exception under its agency policy. Wintergreen EMS Quality Management Reporting, Appendix A

Axon’s student guidance separates the patient’s chief complaint, assessment and impressions. Students using DCHARTI should follow their course’s section labels and rubric. Axon D-CHART-I guidance

Before writing, identify the agency template, required structured fields, authentication process and destination-copy workflow. A good narrative cannot compensate for the wrong patient, an incomplete medication administration field or a missing receiving record.

Keep reported information separate from assessed facts

A sentence should tell the next reader both what is known and how it is known. “Patient reports no regular medicines” is not the same as a verified medication reconciliation. “No open wound seen over the left ankle” describes a specific observation; “skin normal” claims much more.

Use these distinctions in every section:

• Reported: Identify the speaker or record. A bystander’s estimate of an event time remains an estimate.
• Observed or measured: Name the finding, time and relevant conditions. Oxygen saturation without room-air or supplemental-oxygen context may lose meaning.
• Interpreted: State the clinical impression and uncertainty separately from the underlying facts, in the locally designated location.
• Completed: Describe the action and response. Planned treatment, a requested consultation and an accepted transfer are different states.

When sources disagree, preserve the disagreement. If dispatch says “fall” but the patient describes sitting down because of dizziness, do not silently rewrite one source to match the other. Document the additional history and the assessment it prompted. The medical documentation guide explains how to add later information without rewriting the original chronology.

Example 1: a complete DCHART narrative

DC-01 source packet

This fictional encounter supplies every fact used in the finished narrative.

Context and reports: Unit 24 is dispatched at 10:02 for “fall, possible ankle fracture” and arrives at 10:10. The crew’s response is non-emergency. The patient, Alex Mason, age 31, is seated on a pavement. Alex says, “My left ankle hurts when I try to stand,” and reports tripping off a curb at approximately 09:55. Alex reports no head strike, loss of consciousness, neck pain or back pain, no regular medicines and no known medication allergies. These are patient reports; no external medication or allergy record is available. Alex reports no treatment before the crew arrived.

Crew findings: At 10:12, Alex is alert and conversing. The crew observes swelling over the left lateral ankle and no open wound over that area. The left foot is warm; a dorsalis pedis pulse is palpable; toe movement and sensation are present. Pulse is 94/min, blood pressure 128/80 mmHg, respiratory rate 18/min and oxygen saturation 98% on room air. Alex rates pain 6/10. The crew’s documented impression is left ankle injury, with fracture not confirmed.

Completed care and reassessment: At 10:17, the crew applies padded support to the left ankle under the fictional agency’s authorized care plan. At 10:23, the foot remains warm, the dorsalis pedis pulse remains palpable, and toe movement and sensation remain present. Pulse is 90/min, blood pressure 126/78 mmHg, respiratory rate 18/min and oxygen saturation 98% on room air. Alex still rates pain 6/10. No medicine is administered.

Movement and transfer: The crew assists Alex to the stretcher without weight-bearing on the left leg and secures the stretcher restraints. Non-emergency transport begins at 10:25. Arrival at Example Hospital ED is 10:40. At 10:43, RN Lee accepts care after a verbal handoff; the crew supplies the interim care record. No further change is observed or reported during transport. Final electronic-report delivery remains a separate documentation step.

Finished DCHART narrative

D — Dispatch: Unit 24 dispatched at 10:02 for a reported fall with possible ankle fracture. Responded non-emergency and arrived at 10:10; Alex Mason, 31, was seated on a pavement.

C — Chief complaint: Patient stated, “My left ankle hurts when I try to stand.”

H — History: Patient reported tripping off a curb at approximately 09:55. Patient denied head strike, loss of consciousness, neck pain and back pain. Reported no regular medicines, no known medication allergies and no treatment before crew arrival. No external medication/allergy record was available for verification.

A — Assessment: At 10:12, patient alert and conversing. Swelling observed over left lateral ankle; no open wound seen in that area. Left foot warm, dorsalis pedis pulse palpable, toe movement and sensation present. Pulse 94/min, BP 128/80 mmHg, respirations 18/min, SpO₂ 98% on room air; patient-reported pain 6/10. Impression: left ankle injury; fracture not confirmed.

R — Treatment: Padded support applied to left ankle at 10:17 under the authorized care plan. At 10:23, left foot remained warm, dorsalis pedis pulse palpable, toe movement and sensation present. Pulse 90/min, BP 126/78 mmHg, respirations 18/min, SpO₂ 98% on room air. Patient continued to report pain 6/10. No medicine administered.

T — Transport: Assisted to stretcher without weight-bearing on left leg; stretcher restraints secured. Departed at 10:25 for non-emergency transport to Example Hospital ED. No further change observed or reported en route. Arrived at 10:40. RN Lee accepted care at 10:43 following verbal handoff; interim care record supplied.

Why these wording choices matter

The narrative retains a possible fracture in dispatch information without promoting it to a confirmed diagnosis. It preserves patient-reported negatives without claiming a complete normal examination. It also records an unchanged pain score rather than inserting a reassuring response to treatment.

The final paragraph records care acceptance, the verbal handoff and the interim record supplied. Final-report delivery and hospital diagnosis are separate facts. Capture any required receiving signature through the local process; writing a recipient’s name is not itself a signature.

Notice what was not added: a full normal neurological examination, a verified allergy list, an X-ray result or analgesia. The clinical note examples use the same source-to-sentence approach in other settings.

Example 2: DCHARTE exceptions and a later correction

DC-02 source packet

In this separate fictional encounter, a crew’s automated blood-pressure attempt at 15:04 produces an error message and no reading. A manual measurement at 15:07 is 118/76 mmHg. The provider records that measurement with its method and time. During draft review, the provider notices the ePCR has associated 118/76 with 15:04 and labeled it automated.

At 15:18, before finalizing the report, the provider corrects the structured observation to 15:07, manual, following the ePCR’s correction workflow. At 15:20, the provider reopens the saved report and verifies that the observation and narrative agree. No earlier valid blood-pressure reading is supplied.

For the mock record below, the fictional provider is Paramedic Morgan. The erroneous entry was saved at 15:09 as observation BP-02, revision 1. The unsuccessful automated attempt is recorded separately as ATT-01, without a numeric result.

Corresponding narrative and exception

A — Assessment: Automated BP attempt at 15:04 returned an error without a reading. Manual BP at 15:07 was 118/76 mmHg.

E — Exceptions: Automated BP measurement was unsuccessful; a manual reading was obtained. During draft review at 15:18, the BP observation’s method and time were corrected from automated/15:04 to manual/15:07. Saved observation and narrative agreement verified at 15:20.

Record the exception alongside the accurate assessment entry and the system’s correction history, using the locally designated section. An error discovered after report release also needs the approved addendum and receiving-copy process.

This fictional correction sequence shows how an accurate value can be paired with an incorrect acquisition method or time.

DC-02 structured record before and after correction

Record field	Before: revision 1	After: revision 2
Encounter / observation	DC-02 / BP-02	DC-02 / BP-02 — same observation, not a new reading
Blood pressure	118/76 mmHg	118/76 mmHg — value and units unchanged
Acquired at	15:04 — incorrect	15:07 — matches the manual measurement
Method	Automated — incorrect	Manual
Saved / edited by	15:09 / Paramedic Morgan	15:18 / Paramedic Morgan — edit time, not acquisition time
Separate attempt ATT-01	15:04, automated, error; no numeric reading	Unchanged — retained as an unsuccessful attempt, not a zero BP

Mock correction history and recheck

1. 15:09 · revision 1 · Morgan: BP-02 saved as 118/76 mmHg, automated/15:04. Original entry retained in history.
2. 15:18 · revision 2 · Morgan: Acquisition time 15:04 → 15:07; method automated → manual. Reason: value linked to the failed automated attempt instead of the later manual measurement. Value and units unchanged.
3. 15:20 · verification · Morgan: Reopened BP-02 and the saved narrative. Both show manual/15:07, 118/76 mmHg; ATT-01 still has no reading. This verification is not another measurement or a receiving-copy acknowledgment.

The corrected acquisition time is 15:07, not the 15:18 editing time. Keeping ATT-01 separate preserves the failed attempt without turning it into a second valid measurement. The history retains the original error; the current observation and narrative show the corrected facts. A corrected draft alone does not establish that a previously released receiving copy was updated.

Example 3: documenting a transport refusal

NASEMSO’s U.S. model guidance calls for documenting capacity, the risks discussed and the patient’s understanding, medical-direction involvement, and the plan and companion after EMS leaves. Being oriented or signing a form alone does not demonstrate the whole discussion. Capacity concerns require medical-direction involvement; local rules determine authority, required contacts and forms. NASEMSO patient-refusal guidance, pages 23–25

DC-03 source packet: a different ending to DC-01

Fictional teaching excerpt. Keep DC-01’s findings and accepted care through 10:23, but replace its transport ending with the facts below. Apply the service’s current refusal policy for capacity assessment, medical-direction contact and signatures.

• Choice and capacity: At 10:24 Alex declines ambulance transport, not the assessment or support already provided: “I want my sister to take me to the ED.” Paramedic Morgan records that Alex communicates a consistent choice, explains the injury concern and compares ambulance transport with the proposed private journey. Alex reports no alcohol or drug use; Morgan observes no impairment during this discussion and identifies no communication barrier. Morgan’s supplied assessment is that Alex has capacity for this decision, with that reasoning recorded.
• Discussion and response: Morgan recommends ambulance transport for further evaluation and explains that a fracture remains possible, delay may worsen the injury and deterioration during a private journey would lack EMS care. Alex responds, “It could be broken, and waiting could make it worse. If something changes in my sister’s car, there won’t be a crew with us. I still want her to take me.”
• Local process and disposition: Under the fictional service’s refusal procedure, Morgan contacts medical direction at 10:28. Dr. Rivera advises reoffering ambulance transport, documenting the decision and giving instructions to seek emergency assessment and call EMS again if Alex changes their mind or the condition worsens. Morgan does so; Alex still declines and repeats the recontact instruction. At 10:32 Alex signs the refusal record with Morgan as witness. Sister Jamie is present and agrees to remain with Alex and accompany Alex directly to the ED. EMS departs at 10:35; arrival at the ED is not verified.

Corresponding refusal and disposition excerpt

A — Decision-making assessment: At 10:24, Alex communicated a consistent transport choice and compared the offered ambulance journey with the proposed private journey. Patient reported no alcohol/drug use; no impairment observed during discussion and no communication barrier identified. Morgan assessed capacity for this decision on the documented understanding and reasoning, not orientation alone.

R — Discussion: Ambulance transport for further evaluation recommended; possible fracture, harm from delay and absence of EMS care during a private journey explained. Patient stated, “It could be broken, and waiting could make it worse. If something changes in my sister’s car, there won’t be a crew with us. I still want her to take me.” Dr. Rivera contacted at 10:28 under the service’s refusal procedure. Transport reoffered and emergency-assessment/recontact advice given as directed. Patient repeated the recontact instruction and maintained refusal of ambulance transport.

T / locally required refusal section: Assessment and padded support accepted; ambulance transport declined because patient wanted sister to drive. Refusal signed at 10:32; Morgan witnessed. Jamie present and agreed to remain with Alex and accompany Alex directly to the ED. Crew departed at 10:35. ED arrival not verified.

The patient’s intended journey is not a completed handoff. Keep the refusal record and required structured disposition consistent with the narrative; do not label this “refused all care” or “safe for discharge.”

Reconcile the narrative with the ePCR fields

The NEMSIS dictionary defines eNarrative.01, Patient Care Report Narrative. That narrative sits within a larger data model; entering prose does not automatically populate or validate the rest of the report. NEMSIS narrative specification, version 3.5.1

For DC-01, compare three representations: the supplied evidence, the narrative and the relevant structured destination.

Practice: find the unsupported claims

Suppose a draft says: “Patient sustained an ankle fracture. Neurologically intact, allergies verified. Pain improved after treatment. Arrived and transferred care at 10:40; report complete.” Compare each clause with DC-01 before opening the review.

Show the claim-by-claim review

Fracture: Not confirmed. The call information used “possible”; the crew impression remains left ankle injury.

Neurologically intact: Broader than the supplied examination. Record the actual toe movement and sensation findings, with time.

Allergies verified: Unsupported. The history was patient-reported, with no external record available.

Pain improved: Contradicted. The reported score remained 6/10 at 10:23.

Transfer at 10:40: Incorrect chronology. Arrival was 10:40; RN Lee accepted care at 10:43.

Report complete: Not established by the handoff. The source supplies an interim record, not confirmed final electronic delivery.

Repair: Replace the clauses with the attributed facts in the finished narrative, reconcile the affected structured fields, then verify the saved report. Fixing only the prose leaves contradictory data in place.

Copyable DCHART and DCHARTE template

Copy the blank prompts into your agency-approved workspace. Keep the optional E section only if it matches your local format. Enter identifiers and clinical information only in the authorized record system.

For an uncomplicated report, several prompts may combine into one clear sentence. For a changing patient, use time-stamped subsections so repeated assessment and treatment remain readable. The structure should reduce the effort of finding facts, not force the encounter into six equally sized paragraphs.

The template also separates event time from entry time. A later entry can truthfully describe an earlier intervention when its timing and authorship are clear; it must not look as though the intervention happened when the text was typed.

Review the report before you finalize it

Use a source-based review rather than checking whether every heading contains text:

1. Match the patient and encounter. Confirm the correct report before inserting a narrative. Reused templates must not retain another patient’s identifying details or findings.
2. Trace each meaningful assertion. Identify the source for symptom negatives, allergy history, examination findings and the clinical impression. Delete unsupported additions or obtain and document the missing information.
3. Check chronology across headings. Dispatch, arrival, assessment, treatment, reassessment and acceptance should remain distinguishable. Do not let a later measurement appear in an earlier pre-alert.
4. Pair actions with actual responses. “Support applied” needs the supplied reassessment; it does not imply pain relief. Record unsuccessful attempts and their consequences accurately.
5. Reconcile disposition and exceptions. Distinguish transport, arrival and accepted care. Identify any declined element precisely, along with the actual discussion and local refusal documentation.
6. Inspect the saved record. Compare narrative, structured observations and corrections. Confirm required record delivery separately from the live handoff and assign any unfinished documentation task.

When the report cannot be completed because information is missing, state what is missing and who will address it through the agency workflow. Do not manufacture a normal examination to make a section look finished. For a focused call to a receiving clinician, the SBAR examples demonstrate how a request and the receiver’s actual response differ from a written encounter narrative.

Using dictation or AI to organize the narrative

Dictation can transcribe rough notes; generative tools can reorganize them under DCHART headings. Both need a check for names, negation, measurement units and timestamps. A fluent draft can still change “no reading” into a normal reading or turn a planned action into completed care.

New York State’s March 2026 EMS advisory keeps responsibility for clinical decisions and documentation with the provider. It addresses agency oversight, protection of patient information and review of AI-generated material. Its requirements are jurisdiction-specific; obtain approval for the actual recording, processing and storage workflow used by your service. NYS EMS Advisory 26-01

Vero publishes this guide and offers clinical-documentation software. See its emergency-medicine workflow page for product details. Evaluate drafting tools using the source-fidelity and saved-record checks above.