PipeHat Open PipeHat
HL7 V2 | TRIGGER EVENT T06

MDM^T06: Document addendum notification and content

Document addendum notification and content. It's sent as a MDM message (Medical document management) with the MDM_T02 message structure.

Message type
MDM · Medical document management
Trigger event
T06
Message structure
MDM_T02 · per HL7's current table 0354; older versions sometimes paired events differently
In MSH-9
MDM^T06^MDM_T02
Response
ACK · General acknowledgment message

Segments in MDM_T02 and their FHIR resources

The segments of the MDM_T02 structure as listed in the HL7 v2-to-FHIR Implementation Guide, with the FHIR resources each one maps to. Square brackets mean optional and braces mean the segment can repeat. Indented segments belong to the group above them; “required” means required whenever that group is present.

SegmentNameRequiredFHIR resources
MSHMessage HeaderYesBundle MessageHeader Provenance
[{SFT}]Software SegmentNo · repeatsProvenance
[ UAC ]User Authentication CredentialNo—
EVNEvent TypeYesProvenance
PIDPatient IdentificationYesPatient Provenance
PV1Patient VisitYesEncounter Basic Patient Coverage
COMMON_ORDER groupNo · repeats
ORCCommon order segmentYesServiceRequest Provenance
TIMING groupNo · repeats
TQ1Timing/QuantityYesServiceRequest
[{TQ2}]Timing/Quantity Order SequenceNo · repeats—
OBRObservation request segmentYesServiceRequest
[{ NTE }]Notes and comments about the observation (OBR)No · repeatsServiceRequest
TXADocument NotificationYesDocumentReference Provenance
[{CON}]Consent SegmentNo · repeats—
OBSERVATION groupYes · repeats
OBXObservation/Result (one or more required)YesDocumentReference
[{ NTE }]Notes and comments about the observation (OBX)No · repeatsDocumentReference

Other events with the MDM_T02 structure

Source: HL7 Terminology (THO) 7.4.0 and the HL7 v2-to-FHIR Implementation Guide 1.0.0, published by HL7 International under CC0. Check your trading partner's specification for the values they actually send.