Message MDM_T02 to Bundle Map
| V2 Segment | Display | FHIR Target | Equivalence |
|---|---|---|---|
MDM_T02.MSH | Message Header | BundleMessageHeader[1]Processing of the MSH segment results in the creation of a new MessageHeader resource Provenance[1]If the FHIR transformation does not yield a FHIR message, but only a set of resource (APIs, repository, etc.) than one should consider attaching this Provenance resource instance to the relevant FHIR resources generated. Provenance[2]If the FHIR transformation does not yield a FHIR Bunlde, but only a set of resource (APIs, repository, etc.) than one should consider attaching this Provenance resource instance to the relevant FHIR resources generated. | equivalentequivalentequivalentequivalent |
MDM_T02.SFT | Software Segment | Provenance[1].entity.what(Device)If the software does not represent the original source system Provenance[1].entity.what(Device)If the software represents the original source system | equivalentequivalent |
MDM_T02.EVN | Event Type | Provenance[3] | equivalent |
MDM_T02.PID | Patient Identification | Patient[1]Processing of the PID segment results in the creation of a new Patient resource Provenance[4] | equivalentequivalent |
MDM_T02.PV1 | Patient Visit | Encounter[1]Processing of the PV1 segment results in the creation of a new Encounter resource BasicPatient[1]Coverage[1] | equivalentequivalentequivalentequivalent |
MDM_T02.COMMON_ORDER.ORC | Common order segment | ServiceRequest[1]Processing of each ORC segment results in the creation of a new ServiceRequest resource Provenance[3]Using Provenance is the preferred way, but a local implementation may decide to add extensions to the main resource. As the use and guidance of Provenance matures we wil revisit this later. | equivalentequivalent |
MDM_T02.COMMON_ORDER.TIMING.TQ1 | Timing/Quantity | ServiceRequest[1] | equivalent |
MDM_T02.COMMON_ORDER.OBR | Observation request segment | ServiceRequest[1] | equivalent |
MDM_T02.COMMON_ORDER.NTE | Notes and comments about the observation (OBR) | ServiceRequest[1] | equivalent |
MDM_T02.TXA | Document Notification | DocumentReference[1]Note for detailed mapping to use ProvenanceIt is up to the implementer to be sensitive whether this message is new to the receiver or an update to a prior one and only update Provenance for new updates. Also, as TXA-8 Edit Date Time can repeat, a separate Provenance instance must be created for each edit date time of interest.\ must be valued to the seconds and with the appropriate/correct timezone | equivalentequivalent |
MDM_T02.OBSERVATION.OBX | Observation/Result (one or more required) | DocumentReference[1] | equivalent |
MDM_T02.OBSERVATION.NTE | Notes and comments about the observation (OBX) | DocumentReference[1] | equivalent |