HL7 Version 2 to FHIR
1.0.0-ballot - ballot International flag

HL7 Version 2 to FHIR, published by HL7 International / Orders and Observations. This guide is not an authorized publication; it is the continuous build for version 1.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/v2-to-fhir/ and changes regularly. See the Directory of published versions

ConceptMap: Segment MSH to Bundle Map (Experimental)

Official URL: http://hl7.org/fhir/uv/v2mappings/segment-msh-to-bundle Version: 1.0.0-ballot
Active as of 2024-10-30 Computable Name: SegmentMSHToBundle

Copyright/Legal: Copyright (c) 2020, 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 v2Condition (IF True, args)HL7 FHIRComments
Sort OrderIdentifierNameData TypeCardinality - MinCardinality - MaxComputable ANTLRComputable FHIRPathNarrativeFHIR AttributeExtensionData TypeCardinality - MinCardinality - MaxData Type MappingVocabulary Mapping
(IS, ID, CE, CEN, CWE)
Assignment
0MSHBundle.typeBundle.code11"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.
1MSH-1Field SeparatorST11
2MSH-2Encoding CharactersST11
3MSH-3Sending ApplicationHD01
4MSH-4Sending FacilityHD01
5MSH-5Receiving ApplicationHD01
6MSH-6Receiving FacilityHD01
7MSH-7Date/Time of MessageDTM11Bundle.timestampBundle.instant01Note 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.
8MSH-8SecurityST01
9MSH-9Message TypeMSG11
10MSH-10Message Control IDST11Bundle.identifier.valueBundle.string01
10MSH-10Message Control IDST11Bundle.identifier.systemBundle.uri01/to be determined by the implementer/
11MSH-11Processing IDPT11
12MSH-12Version IDVID11
13MSH-13Sequence NumberNM01
14MSH-14Continuation PointerST01
15MSH-15Accept Acknowledgment TypeID01
16MSH-16Application Acknowledgment TypeID01
17MSH-17Country CodeID01
18MSH-18Character SetID0-1
19MSH-19Principal Language Of MessageCWE01
20MSH-20Alternate Character Set Handling SchemeID01
21MSH-21Message Profile IdentifierEI0-1
22MSH-22Sending Responsible OrganizationXON01
23MSH-23Receiving Responsible OrganizationXON01
24MSH-24Sending Network AddressHD01
25MSH-25Receiving Network AddressHD01
26MSH-26Security Classification TagCWE01
27MSH-27Security Handling InstructionsCWE0-1
28MSH-28Special Access Restriction InstructionsST0-1

Generated Narrative: ConceptMap segment-msh-to-bundle

Mapping from MSH to Bundle


Group 1 Mapping from unspecified code system to unspecified code system

Source CodeRelationshipTarget CodeComment
MSHis equivalent totypeNote 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 totimestampNote 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 toidentifier.value
MSH-10 (Message Control ID)is equivalent toidentifier.system

Notes: