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 Provenance Map (Experimental)

Official URL: http://hl7.org/fhir/uv/v2mappings/segment-msh-source-to-provenance Version: 1.0.0-ballot
Active as of 2024-12-20 Computable Name: SegmentMSHSourceToProvenance

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 Provenance Resource.

This ConceptMap represents the mapping from the HL7 V2 MSH Segment to the FHIR Provenance 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
0MSHwhen you hold on to/persist the v2 message in a data storeProvenance.entity.what(Provenance.DocumentReference.content.attachment.url)If there is an interest in holding to the original message by the recipient
0MSHwhen you do not hold on to/persist the v2 message in a data storeProvenance.entity.what(Provenance.DocumentReference.content.attachment.data)/v2.txt or v2.xml into base 64/If there is an interest in holding to the original message by the recipient
0MSHwhen you do not hold on to/persist the v2 message in a data storeProvenance.entity.what(Provenance.DocumentReference.status)"current"If there is an interest in holding to the original message by the recipient
0MSHProvenance.entity.role"source"
1MSH-1Field SeparatorST11
2MSH-2Encoding CharactersST11
3MSH-3Sending ApplicationHD01IF MSH-3 AND MSH-24 VALUEDProvenance.entity.what(Provenance.Device.identifier)Reference(Provenance.Device)HD[Identifier]
3MSH-3Sending ApplicationHD01IF MSH-3 AND MSH-24 VALUEDProvenance.entity.roleProvenance.code"source"
4MSH-4Sending FacilityHD01IF MSH-22 NOT VALUEDProvenance.agent.who(Provenance.Organization)Reference(Provenance.Organization)11HD[Organization]
4MSH-4Sending FacilityHD01IF MSH-22 NOT VALUEDProvenance.agent.type.coding.codeProvenance.code01"author"
4MSH-4Sending FacilityHD01IF MSH-22 NOT VALUEDProvenance.agent.type.coding.systemProvenance.uri01"http://terminology.hl7.org/CodeSystem/provenance-participant-type"
5MSH-5Receiving ApplicationHD01
6MSH-6Receiving FacilityHD01
7MSH-7Date/Time of MessageDTM11Provenance.recorded11We note that this could have been mapped to the Provenance.occurred[x] attribute, but since Provenance.recorded is required and these two times are virtually the same, we opted to map to Provenance.recorded.
7MSH-7Date/Time of MessageDTM11Provenance.occurred01
8MSH-8SecurityST01
9MSH-9Message TypeMSG11Provenance.activity.coding.displayProvenance.string"message - "+MSG.1+"^"+MSG.2+"^"+MSG.3
10MSH-10Message Control IDST11
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-1If MSH-21 can be translated into a uri, it can be used to populate Provenance.policy
22MSH-22Sending Responsible OrganizationXON01Provenance.agent.who(Provenance.Organization)Reference(Provenance.Organization)11XON[Organization]
22MSH-22Sending Responsible OrganizationXON01Provenance.agent.type.coding.codeProvenance.code01"author"
22MSH-22Sending Responsible OrganizationXON01Provenance.agent.type.coding.systemProvenance.uri01"http://terminology.hl7.org/CodeSystem/provenance-participant-type"
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-source-to-provenance

Mapping from MSH to Provenance


Group 1 Mapping from unspecified code system to unspecified code system

Source CodeRelationshipTarget CodeComment
MSHis equivalent toentity[1].what(DocumentReference.content.attachment.url)If there is an interest in holding to the original message by the recipient
MSHis equivalent toentity[1].what(DocumentReference.content.attachment.data)If there is an interest in holding to the original message by the recipient
MSHis equivalent toentity[1].what(DocumentReference.status)If there is an interest in holding to the original message by the recipient
MSHis equivalent toentity[1].role
MSH-3 (Sending Application)is equivalent toentity[2].what(Device.identifier)
MSH-3 (Sending Application)is equivalent toentity[2].role
MSH-4 (Sending Facility)is equivalent toagent[1].who(Organization)
MSH-4 (Sending Facility)is equivalent toagent[1].type.coding.code
MSH-4 (Sending Facility)is equivalent toagent[1].type.coding.system
MSH-7 (Date/Time of Message)is equivalent torecordedWe note that this could have been mapped to the Provenance.occurred[x] attribute, but since Provenance.recorded is required and these two times are virtually the same, we opted to map to Provenance.recorded.
MSH-7 (Date/Time of Message)is equivalent tooccurred
MSH-9 (Message Type)is equivalent toactivity.coding.display
MSH-22 (Sending Responsible Organization)is equivalent toagent[2].who(Organization)
MSH-22 (Sending Responsible Organization)is equivalent toagent[2].type.coding.code
MSH-22 (Sending Responsible Organization)is equivalent toagent[2].type.coding.system

Notes: