HL7 ADT^A12 (Cancel Transfer)
ADT^A12, ADT^A29 share a single message structure in HL7v2 - the standard defines the same segments and groups for each, and they differ in what the trigger event means rather than in what the message carries. Its v2.8.2 structure carries 10 segments and groups, 4 of them required.
Trigger events sharing this structure
The HL7v2 standard defines the same segments and groups for each of these trigger events. They differ in what the event means, not in what the message carries, so the structure below applies to all of them.
| ADT^A12 | Cancel Transfer |
| ADT^A29 | Delete Person Information |
Full message structure (v2.8.2)
Every segment and group the standard defines for ADT^A12, in order, straight from the machine-readable specification. Indented rows sit inside the repeating group above them. R is required, O optional, C conditional; ∞ means the group or segment may repeat without a defined limit.
| Segment / group | Usage | Repeats |
|---|---|---|
| MSH | R | 1 |
| SFT | O | ∞ |
| UAC | O | 1 |
| EVN | R | 1 |
| PID | R | 1 |
| PD1 | O | 1 |
| PV1 | R | 1 |
| PV2 | O | 1 |
| DB1 | O | ∞ |
| OBX | O | ∞ |
Which HL7v2 versions changed ADT^A12?
ADT^A12 has been defined since v2.1. Consecutive versions sharing an identical structure are grouped, so a single row spanning several versions means nothing changed across them.
| Versions | What changed |
|---|---|
| v2.1 | First defined, with 5 segments and groups. |
| v2.2 | Added OBX, PV2. |
| v2.3 - v2.4 | Added DB1, PD1. |
| v2.5 - v2.5.1 | Added SFT. |
| v2.6 | Added UAC. |
| v2.7 - v2.8.2 | Removed DG1. |