HL7 ACC Accident
HL7 field reference ACC fields from HL7 v2.5.1 Show fields
These are the generated fields for the version selected at the top of the page. The document stays the same, but the reference panel follows that version.
Fields
| Field | Name | Required | Repeatable | Type | Table |
|---|---|---|---|---|---|
| ACC.1 | Accident Date/Time | No | No | TS | |
| ACC.2 | Accident Code | No | No | CE | 0050 |
| ACC.3 | Accident Location | No | No | ST | |
| ACC.4 | Auto Accident State | No | No | CE | 0347 |
| ACC.5 | Accident Job Related Indicator | No | No | ID | 0136 |
| ACC.6 | Accident Death Indicator | No | No | ID | 0136 |
| ACC.7 | Entered By | No | No | XCN | |
| ACC.8 | Accident Description | No | No | ST | |
| ACC.9 | Brought In By | No | No | ST | |
| ACC.10 | Police Notified Indicator | No | No | ID | 0136 |
| ACC.11 | Accident Address | No | No | XAD |
ACC is the HL7 Accident segment. The ACC segment contains patient information relative to an accident in which the patient has been involved.
Billing and reimbursement segments tend to be driven by local business rules, so the safest habit is to map only the fields the receiving profile actually expects.
The v2.5.1 structures show ACC in ADR_A19 (Patient query), ADT_A01 (Admit/visit notification), ADT_A03 (Discharge/end visit), ADT_A05 (Pre-admit a patient), and 10 other message structures. That tells you where it can appear, but the local implementation guide still decides which optional fields are meaningful.
These are good fields to test in HL7 Soup Web before mapping, because billing feeds often fail on small code, identifier, or quantity assumptions. In Integration Soup, I would keep the local code mapping visible rather than burying it in a one-off transform.
So this page stays intentionally practical: what each field is for, what shape the generated v2.5.1 data gives it, and where I would be careful before mapping it.
ACC-1 is when the accident occurred, not when the patient arrived, registered, or was admitted. If the source only knows the date, do not invent a time. Accident timing can matter for claims, workers' compensation, legal reporting, and clinical context, so precision should be honest.
ACC-2 describes the type of accident. HL7 points implementers toward accident code values, and many real billing/reporting workflows use ICD external cause style coding. Keep it aligned with DG1/diagnosis coding and the payer or registry rules that actually consume it.
ACC-3 is an older text-style accident location field. It can be useful for a short human description such as "worksite", "home", or "intersection", but it is not as structured as ACC-11. If the address matters, use ACC-11 rather than forcing everything into this field.
ACC-4 is retained mostly for backward compatibility and US-style auto-accident claim requirements. In v2.5 thinking, the state is part of the accident address, so ACC-11 is usually the cleaner place to represent it. Populate ACC-4 only when a receiver or claim form explicitly asks for it.
ACC-5 flags whether the accident is job related. That can change payer routing, workers' compensation handling, and downstream billing rules. Do not infer it casually from location or employer name; use the registration, claim, or occupational-health source that is allowed to make the statement.
ACC-6 says whether the accident resulted in death. This is a high-impact administrative value, so treat unknown, not asked, and no as different states if the local profile supports that distinction. Do not set it from a stale screen field just because the claim segment allows it.
ACC-7 identifies the person who entered the accident information. This is audit context, not necessarily the treating clinician, witness, or reporting officer. Preserve staff identifiers where possible so corrections can be traced back to the source workflow.
ACC-8 is narrative context for the accident. It is useful for humans and for claim review, but do not hide codable facts here if the receiver needs structured fields. If the accident type, address, job-related flag, or police notification drives workflow, send those fields properly.
ACC-9 records who or what brought the patient in after the accident, often as local text. It might be ambulance, police, family, self, or another source depending on the interface guide. Keep it short and do not turn it into a full transport history.
ACC-10 says whether police were notified. Unknown is not the same as no. If the receiver routes claims, legal notifications, or reporting tasks from this flag, define how the sending system represents not asked, patient declined, and not applicable.
ACC-11 is the structured accident address. Use it when location details need to survive beyond display: state, postcode, country, county, and address type should stay in their components. This is the field I would prefer over ACC-3 and ACC-4 when the receiver can handle it.