HL7 PDA Patient Death and Autopsy
HL7 field reference PDA 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 |
|---|---|---|---|---|---|
| PDA.1 | Death Cause Code | No | Yes | CE | |
| PDA.2 | Death Location | No | No | PL | |
| PDA.3 | Death Certified Indicator | No | No | ID | 0136 |
| PDA.4 | Death Certificate Signed Date/Time | No | No | TS | |
| PDA.5 | Death Certified By | No | No | XCN | |
| PDA.6 | Autopsy Indicator | No | No | ID | 0136 |
| PDA.7 | Autopsy Start and End Date/Time | No | No | DR | |
| PDA.8 | Autopsy Performed By | No | No | XCN | |
| PDA.9 | Coroner Indicator | No | No | ID | 0136 |
PDA carries patient death and autopsy detail for patient-administration and reporting workflows.
Patient-administration segments add detail around the person, visit, account, diagnosis, procedure, insurance, merge, death, disability, and grouping state carried by the message.
These fields often drive matching, billing, encounter routing, reporting, and front-desk workflow. Separate patient identity, visit identity, account identity, and clinical facts carefully.
The v2.5.1 structures show PDA in ADT_A01 - Admit/visit notification, ADT_A02 - Transfer a patient, and ADT_A03 - Discharge/end visit. That tells you where it can appear, but the implementation guide still decides which optional fields are meaningful.
For practical interface work, read the generated field panel for datatype, required, repeatable, and table details, then use the notes below to decide what the field should mean in the receiving workflow.
PDA-1 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
This field can repeat. Use repetitions for separate real-world values, not as a workaround for putting several unrelated ideas in one field.
PDA-2 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
PDA-3 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
The generated panel links this to HL7 table 0136; many real interfaces narrow that list further, so follow the receiver's implementation guide.
PDA-4 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
PDA-5 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
PDA-6 tells the receiver the state of this patient-administration workflow. Status fields often drive workflow branches, so use the agreed code and do not infer a status just because another field looks complete.
The coded value should follow HL7 table 0136 or the narrower table in the local profile.
PDA-7 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
For effective and end dates, make the boundary rule explicit. Receivers need to know whether the value is inclusive, exclusive, planned, actual, or merely informational.
PDA-8 carries Autopsy Performed By for this patient-administration workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
PDA-9 tells the receiver the state of this patient-administration workflow. Status fields often drive workflow branches, so use the agreed code and do not infer a status just because another field looks complete.
The coded value should follow HL7 table 0136 or the narrower table in the local profile.
Related links
- PID - Patient Identification
- PD1 - Patient Additional Demographic
- PV1 - Patient Visit
- PV2 - Patient Visit - Additional Information
- DG1 - Diagnosis
- DRG - Diagnosis Related Group
- PR1 - Procedures
- IN1 - Insurance
- IN2 - Insurance Additional Information
- IN3 - Insurance Additional Information, Certification