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: Datatype ED to Attachment Map (Experimental)

Official URL: http://hl7.org/fhir/uv/v2mappings/datatype-ed-to-attachment Version: 1.0.0-ballot
Active as of 2024-10-30 Computable Name: DatatypeEDToAttachment

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

This ConceptMap represents a mapping from the HL7 V2 Datatype ED to the FHIR Attachment Data Type.

This ConceptMap represents the mapping from the HL7 V2 ED Data Type to the FHIR Attachment Data Type. 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
1ED.1Source ApplicationHD01
2ED.2Type of DataID11IF ED.3 NOT VALUEDAttachment.extension.urlAttachment.uri11"https://hl7.org/fhir/StructureDefinition/alternate-codes"
2ED.2Type of DataID11IF ED.3 NOT VALUEDAttachment.extension.valueCodeableConceptAttachment.CodeableConcept11
3ED.3Data SubtypeID01Attachment.contentTypeAttachment.code01
4ED.4EncodingID11
5ED.5DataTX11IF ED.4 IN ("Base64")Attachment.dataAttachment.base64Binary01Implementations are not always accurate, so to be safe you may want to always assess OBX-5.5 to determine the correct .contentType.
5ED.5DataTX11IF ED.4 IN ("A", (HEX")Attachment.dataAttachment.base64Binary01/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.

Generated Narrative: ConceptMap datatype-ed-to-attachment

Mapping from ED to Attachment


Group 1 Mapping from unspecified code system to unspecified code system

Source CodeRelationshipTarget CodeComment
ED.2 (Type of Data)is equivalent toextension[1].url
ED.2 (Type of Data)is equivalent toextension[1].valueCodeableConcept
ED.3 (Data Subtype)is equivalent tocontentType
ED.5 (Data)is equivalent todataImplementations are not always accurate, so to be safe you may want to always assess OBX-5.5 to determine the correct .contentType.
ED.5 (Data)is equivalent todataImplementations are not always accurate, so to be safe you may want to always assess OBX-5.5 to determine the correct .contentType.

Notes: