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 ORC to DiagnosticReport Map (Experimental)

Official URL: http://hl7.org/fhir/uv/v2mappings/segment-orc-to-diagnosticreport Version: 1.0.0-ballot
Active as of 2024-12-20 Computable Name: SegmentORCToDiagnosticReport

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

This ConceptMap represents a mapping from the HL7 V2 Segment ORC to the FHIR DiagnosticReport Resource.

This ConceptMap represents the mapping from the HL7 V2 ORC Segment to the FHIR DiagnosticReport 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
1ORC-1Order ControlID11
2ORC-2Placer Order NumberEI01DiagnosticReport.identifierDiagnosticReport.Identifier0-1EI[Identifier-Extension]
2ORC-2Placer Order NumberEI01DiagnosticReport.identifier.type.coding.codeDiagnosticReport.code01"PLAC"
2ORC-2Placer Order NumberEI01DiagnosticReport.identifier.type.coding.systemDiagnosticReport.uri01"http://terminology.hl7.org/CodeSystem/v2-0203"
2ORC-2Placer Order NumberEI01DiagnosticReport.basedOn(DiagnosticReport.ServiceRequest)Reference(DiagnosticReport.ServiceRequest)0-1The Placer Order Number may be used to find the ServiceRequest with the same ID to link the ServiceRequest and the DiagnosticReport which fulfills the order. Ideally, DiagnosticReport.identifier will be unique. Depending on how the resulting system populates the Filler ID, it may be desirable to concatenate the Filler ID with the procedure code and/or date/time to create a unique identifier.
3ORC-3Filler Order NumberEI01DiagnosticReport.identifierDiagnosticReport.Identifier0-1EI[Identifier-Extension]
3ORC-3Filler Order NumberEI01DiagnosticReport.identifier.type.coding.codeDiagnosticReport.code01"FILL"
3ORC-3Filler Order NumberEI01DiagnosticReport.identifier.type.coding.systemDiagnosticReport.uri01"http://terminology.hl7.org/CodeSystem/v2-0203"
4ORC-4Placer Group NumberEIP01DiagnosticReport.identifierDiagnosticReport.Identifier0-1EIP[Identifier-FillerAssignedIdentifier]
4ORC-4Placer Group NumberEIP01DiagnosticReport.identifierDiagnosticReport.Identifier0-1EIP[Identifier-PlacerAssignedIdentifier]
5ORC-5Order StatusID01
6ORC-6Response FlagID01
7ORC-7Quantity/TimingTQ0-1
8ORC-8Parent OrderEIP01
9ORC-9Date/Time of TransactionDTM01extension??-businessEvent
10ORC-10Entered ByXCN0-1
11ORC-11Verified ByXCN0-1
12ORC-12Ordering ProviderXCN0-1
13ORC-13Enterer's LocationPL01
14ORC-14Call Back Phone NumberXTN02
15ORC-15Order Effective Date/TimeDTM01
16ORC-16Order Control Code ReasonCWE01DiagnosticReport.extension.urlDiagnosticReport.uri11"http://hl7.org/fhir/StructureDefinition/event-statusReason"
16ORC-16Order Control Code ReasonCWE01DiagnosticReport.extension.valueCodeableConceptDiagnosticReport.CodeableConcept11CWE[CodeableConcept]
17ORC-17Entering OrganizationCWE01
18ORC-18Entering DeviceCWE01
19ORC-19Action ByXCN0-1
20ORC-20Advanced Beneficiary Notice CodeCWE01
21ORC-21Ordering Facility NameXON0-1
22ORC-22Ordering Facility AddressXAD0-1
23ORC-23Ordering Facility Phone NumberXTN0-1
24ORC-24Ordering Provider AddressXAD0-1
25ORC-25Order Status ModifierCWE01
26ORC-26Advanced Beneficiary Notice Override ReasonCWE01
27ORC-27Filler's Expected Availability Date/TimeDTM01
28ORC-28Confidentiality CodeCWE01
29ORC-29Order TypeCWE01
30ORC-30Enterer Authorization ModeCNE01
31ORC-31Parent Universal Service IdentifierCWE01
32ORC-32Advanced Beneficiary Notice DateDT01
33ORC-33Alternate Placer Order NumberCX0-1
34ORC-34Order Workflow ProfileCWE0-1

Generated Narrative: ConceptMap segment-orc-to-diagnosticreport

Mapping from ORC to DiagnosticReport


Group 1 Mapping from unspecified code system to unspecified code system

Source CodeRelationshipTarget CodeComment
ORC-2 (Placer Order Number)is equivalent toidentifier[1]
ORC-2 (Placer Order Number)is equivalent toidentifier[1].type.coding.code
ORC-2 (Placer Order Number)is equivalent toidentifier[1].type.coding.system
ORC-2 (Placer Order Number)is equivalent tobasedOn(ServiceRequest)The Placer Order Number may be used to find the ServiceRequest with the same ID to link the ServiceRequest and the DiagnosticReport which fulfills the order. Ideally, DiagnosticReport.identifier will be unique. Depending on how the resulting system populates the Filler ID, it may be desirable to concatenate the Filler ID with the procedure code and/or date/time to create a unique identifier.\
ORC-3 (Filler Order Number)is equivalent toidentifier[2]
ORC-3 (Filler Order Number)is equivalent toidentifier[2].type.coding.code
ORC-3 (Filler Order Number)is equivalent toidentifier[2].type.coding.system
ORC-4 (Placer Group Number)is equivalent toidentifier[3]
ORC-4 (Placer Group Number)is equivalent toidentifier[4]
ORC-16 (Order Control Code Reason)is equivalent toextension[1].url
ORC-16 (Order Control Code Reason)is equivalent toextension[1].valueCodeableConcept

Notes: