GlossaryFire and EMS reporting
Patient care report
A patient care report documents an EMS encounter, assessment, care, and response. Learn why it differs from an incident count, transport, or invoice.
A patient care report, or PCR, is an EMS record documenting a patient-related encounter, including relevant assessment, care, and response information. It records what was reported, observed, and done within that encounter. It can be electronic or use another approved format, depending on the organization and applicable requirements.
Read the record in context
A report can include information supplied by a patient or others, findings recorded by personnel, times, interventions, and disposition. These parts serve different purposes. A reported symptom is not identical to an observed finding, and a field assessment is not necessarily a final hospital diagnosis.
NEMSIS's data dictionary separates patient-care record identification from incident identification and organizes clinical and response data into distinct sections. That structure illustrates why a PCR is more than a dispatch category or a transport count. NEMSIS version 3.5.1 dictionary.
Example
Hypothetical example: A crew evaluates a person after a fall. The record documents the history provided, the crew's assessment, and the disposition of the encounter. The person is not transported by that unit.
The lack of a transport does not by itself mean there was no patient encounter, assessment, or report. To understand what occurred, read the documented disposition and relevant narrative instead of treating transport as a substitute for all other care information.
Common confusion
A PCR is not necessarily one unique emergency. Several responding units or agencies can create separate documentation connected to the same event. Conversely, a report identifier and an incident identifier can refer to different levels of the reporting structure. Counting report numbers alone does not establish a unique patient or incident count.
It also differs from a billing record. Charges and payment information answer administrative questions; they do not replace the full account of the encounter. Nor does a public incident-summary row establish what information exists in the patient's locally maintained record.
Limits of summaries and access
A statistical export can contain only selected fields from the reporting environment. Before analyzing it, check the record unit, eligibility rules, data-standard version, and treatment of missing information. An empty field should not automatically be read as proof that a condition or action was absent.
Specific patient records can contain sensitive personal and clinical information. Request procedures and authorization requirements depend on the responsible organization and applicable law. The availability of anonymous aggregate statistics does not establish that individual reports are publicly releasable. Keep those distinct when describing what a dataset or records request can provide.