What is Transfer-of-Care-R4-Hackathon FHIR Messaging Solution Data Mapping?
This content is not relevant to the Transfer-of-Care-R4-Hackathon as the transport solution design has not been defined
Any FHIR Messaging Solution will require some mapping to the FHIR resources included in the message bundle. This section only concerns mapping to the Bundle and MessageBundle profiles, the payload specification will need to be consulted for payload mapping information. The sender of the eDischarge will need to either create Bundle and MessageHeader data items or source from them from its own data store. When it sources from its own data store then a mapping will need to be done. Some data items such as UUIDs for identifiers for example will always need to be created by a sending systems.
Existing Systems
Pre-existing systems which for example are HL7 V2 based will find lots of guidance on mapping V2 to FHIR Bundles.
The table below illustrates V2 MSH mapping to FHIR MessageHeader resource.
| Element | V2 segment | Description |
|---|---|---|
| Identifier | MSH-10 | Message Control ID |
| Timestamp | MSH-7 | Message Date/time |
| Event | MSH-9.2 | observation-provideDerived from the second component of the Message Type field. Its value comes from HL7 table 3 |
| Source.name | MSH-3 | Sending application name |
| Source.software | MSH-3 | Sending application name |
| Source.endpoint | MSH-24 | Sending network address |
| Destination.name | MSH-5 | Receiving application |
| Destination.endpoint | MSH-25 | Receiving network address |
| data | References to the ‘root’ resource of the message. |