HL7 Version 2 to FHIR
1.0.0 - STU 1

HL7 Version 2 to FHIR - Downloaded Version 1.0.0 See the Directory of published versions

## ConceptMap: Segment MSH to Bundle Map (Experimental)

Official URL: http://hl7.org/fhir/uv/v2mappings/ConceptMap/segment-msh-to-bundle | Version: 1.0.0
Standards status: Informative | Computable Name: SegmentMSHToBundle
Copyright/Legal: Copyright (c) 2025, HL7 International, Inc., All Rights Reserved.

This ConceptMap represents a mapping from the HL7 V2 Segment MSH to the FHIR Bundle Resource.

This ConceptMap represents the mapping from the HL7 V2 MSH Segment to the FHIR Bundle Resource. See also the FHIR Shorthand or the CSV Source.

HL7 v2 | Condition (IF True, args) | HL7 FHIR | Comments
--- | --- | --- | ---
Sort Order | Identifier | Name | Data Type | Cardinality - Min | Cardinality - Max | Computable ANTLR | Computable FHIRPath | Narrative | FHIR Attribute | Extension | Data Type | Cardinality - Min | Cardinality - Max | Data Type Mapping | Vocabulary Mapping (IS, ID, CE, CEN, CWE) | Assignment
0 | MSH |  |  |  |  |  |  |  | Bundle.type |  | code | 1 | 1 |  |  | "message" | Note that the assignment is according to the mapping principles for mapping definitions only. There is no expectation that this is the actual Bundle.type being mapped to based on local implementation considerations. Unless the progression actually is a FHIR Message.
1 | MSH-1 | Field Separator | ST | 1 | 1 |  |  |  |  |  |  |  |  |  |  |  |
2 | MSH-2 | Encoding Characters | ST | 1 | 1 |  |  |  |  |  |  |  |  |  |  |  |
3 | MSH-3 | Sending Application | HD | 0 | 1 |  |  |  |  |  |  |  |  |  |  |  |
4 | MSH-4 | Sending Facility | HD | 0 | 1 |  |  |  |  |  |  |  |  |  |  |  |
5 | MSH-5 | Receiving Application | HD | 0 | 1 |  |  |  |  |  |  |  |  |  |  |  |
6 | MSH-6 | Receiving Facility | HD | 0 | 1 |  |  |  |  |  |  |  |  |  |  |  |
7 | MSH-7 | Date/Time of Message | DTM | 1 | 1 |  |  |  | Bundle.timestamp |  | instant | 0 | 1 |  |  |  | Note that MSH-7 does not require a time offset while Bundle.timestamp does. Implementers should configure the actual mapping according to local context of the transaction.
8 | MSH-8 | Security | ST | 0 | 1 |  |  |  |  |  |  |  |  |  |  |  |
9 | MSH-9 | Message Type | MSG | 1 | 1 |  |  |  |  |  |  |  |  |  |  |  |
10 | MSH-10 | Message Control ID | ST | 1 | 1 |  |  |  | Bundle.identifier.value |  | string | 0 | 1 |  |  |  |
10 | MSH-10 | Message Control ID | ST | 1 | 1 |  |  |  | Bundle.identifier.system |  | uri | 0 | 1 |  |  | /to be determined by the implementer/ |
11 | MSH-11 | Processing ID | PT | 1 | 1 |  |  |  |  |  |  |  |  |  |  |  |
12 | MSH-12 | Version ID | VID | 1 | 1 |  |  |  |  |  |  |  |  |  |  |  |
13 | MSH-13 | Sequence Number | NM | 0 | 1 |  |  |  |  |  |  |  |  |  |  |  |
14 | MSH-14 | Continuation Pointer | ST | 0 | 1 |  |  |  |  |  |  |  |  |  |  |  |
15 | MSH-15 | Accept Acknowledgment Type | ID | 0 | 1 |  |  |  |  |  |  |  |  |  |  |  |
16 | MSH-16 | Application Acknowledgment Type | ID | 0 | 1 |  |  |  |  |  |  |  |  |  |  |  |
17 | MSH-17 | Country Code | ID | 0 | 1 |  |  |  |  |  |  |  |  |  |  |  |
18 | MSH-18 | Character Set | ID | 0 | -1 |  |  |  |  |  |  |  |  |  |  |  |
19 | MSH-19 | Principal Language Of Message | CWE | 0 | 1 |  |  |  |  |  |  |  |  |  |  |  |
20 | MSH-20 | Alternate Character Set Handling Scheme | ID | 0 | 1 |  |  |  |  |  |  |  |  |  |  |  |
21 | MSH-21 | Message Profile Identifier | EI | 0 | -1 |  |  |  |  |  |  |  |  |  |  |  |
22 | MSH-22 | Sending Responsible Organization | XON | 0 | 1 |  |  |  |  |  |  |  |  |  |  |  |
23 | MSH-23 | Receiving Responsible Organization | XON | 0 | 1 |  |  |  |  |  |  |  |  |  |  |  |
24 | MSH-24 | Sending Network Address | HD | 0 | 1 |  |  |  |  |  |  |  |  |  |  |  |
25 | MSH-25 | Receiving Network Address | HD | 0 | 1 |  |  |  |  |  |  |  |  |  |  |  |
26 | MSH-26 | Security Classification Tag | CWE | 0 | 1 |  |  |  |  |  |  |  |  |  |  |  |
27 | MSH-27 | Security Handling Instructions | CWE | 0 | -1 |  |  |  |  |  |  |  |  |  |  |  |
28 | MSH-28 | Special Access Restriction Instructions | ST | 0 | -1 |  |  |  |  |  |  |  |  |  |  |  |

Mapping from (not specified) to (not specified)

Group 1 Mapping from `unspecified code system` to `unspecified code system`

Source Code | Relationship | Target Code | Comment
MSH | is equivalent to | type | Note that the assignment is according to the mapping principles for mapping definitions only. There is no expectation that this is the actual Bundle.type being mapped to based on local implementation considerations. Unless the progression actually is a FHIR Message.
MSH-7 (Date/Time of Message) | is equivalent to | timestamp | Note that MSH-7 does not require a time offset while Bundle.timestamp does. Implementers should configure the actual mapping according to local context of the transaction.
MSH-10 (Message Control ID) | is equivalent to | identifier.value |
MSH-10 (Message Control ID) | is equivalent to | identifier.system |

### Notes: