HL7 Version 2 to FHIR
1.0.0 - STU 1 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 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: Datatype ED to DocumentReference Map (Experimental)

Official URL: http://hl7.org/fhir/uv/v2mappings/ConceptMap/datatype-ed-to-documentreference Version: 1.0.0
Standards status: Informative Computable Name: DatatypeEDToDocumentReference

Copyright/Legal: Copyright (c) 2025, HL7 International, Inc., All Rights Reserved.

This ConceptMap represents a mapping from the HL7 V2 Datatype ED to the FHIR DocumentReference Resource.

This ConceptMap represents the mapping from the HL7 V2 ED Data Type to the FHIR DocumentReference Resource. See also the FHIR Shorthand or the CSV Source.

HL7 v2Condition (IF True, args)HL7 FHIRComments
Sort OrderIdentifierNameData TypeCardinality - MinCardinality - MaxComputable ANTLRComputable FHIRPathNarrativeFHIR AttributeProposed ExtensionData TypeCardinality - MinCardinality - MaxData Type MappingVocabulary Mapping
(IS, ID, CE, CEN, CWE)
Assignment
0DocumentReference.status"current"
1ED.1Source ApplicationHD01
2ED.2Type of DataID11IF ED.3 NOT VALUEDDocumentReference.content.attachment.extension.urluri11"https://hl7.org/fhir/StructureDefinition/alternate-codes"
2ED.2Type of DataID11IF ED.3 NOT VALUEDDocumentReference.content.attachment.extension.valueCodeableConceptCodeableConcept11
3ED.3Data SubtypeID01DocumentReference.content.attachment.contentTypecode01
4ED.4EncodingID11
5ED.5DataTX11DocumentReference.content.attachment.database64Binary01/convert from A or HEX to binary64/Implementations are not always accurate, so to be safe you may want to always assess OBX-5.5 to determine the correct .contentType.

Mapping from (not specified) to (not specified)


Group 1 Mapping from unspecified code system to unspecified code system

Source Concept DetailsRelationshipTarget Concept DetailsComment
Codes from ComputableANTLRCodes from
ED.2Type of DataIF ED.3 NOT VALUEDis equivalent tocontent.attachment.extension[1].urlcontent.attachment.extension[1].url
ED.2Type of DataIF ED.3 NOT VALUEDis equivalent tocontent.attachment.extension[1].valueCodeableConceptcontent.attachment.extension[1].valueCodeableConcept
ED.3Data Subtypeis equivalent tocontent.attachment.contentTypecontent.attachment.contentType
ED.5Datais equivalent tocontent.attachment.datacontent.attachment.dataImplementations are not always accurate, so to be safe you may want to always assess OBX-5.5 to determine the correct .contentType.

Notes: