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 TQ to ServiceRequest Map (Experimental)

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

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

This ConceptMap represents a mapping from the HL7 V2 Datatype TQ to the FHIR ServiceRequest Resource.

This ConceptMap represents the mapping from the HL7 V2 TQ Data Type to the FHIR ServiceRequest 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
1TQ.1QuantityCQ01ServiceRequest.quantityQuantityServiceRequest.Quantity01CQ[Quantity]
2TQ.2IntervalRI01ServiceRequest.occurrenceTimingServiceRequest.Timing01RI[Timing]
3TQ.3DurationST01If the value and unit in TQ.3 can be unambiguously parsed where the unit is translatable into UCUM and the field contains nothing else.ServiceRequest.occurenceTiming.repeat.boundsDuration.valueServiceRequest.decimal01See notes on TQ.3 in v2.5.1 for likely formats that will be used in the v2 message.
3TQ.3DurationST01If the value and unit in TQ.3 can be unambiguously parsed where the unit is translatable into UCUM and the field contains nothing else.ServiceRequest.occurenceTiming.repeat.boundsDuration.unitServiceRequest.string01See notes on TQ.3 in v2.5.1 for likely formats that will be used in the v2 message.
3TQ.3DurationST01If the value and unit in TQ.3 can be unambiguously parsed where the unit is translatable into UCUM and the field contains nothing else.ServiceRequest.occurenceTiming.repeat.boundsDuration.system01"UCUM"
3TQ.3DurationST01If TQ.3 cannot be parsed/translated into the duration datatypeoccurrenceTiming.repeat.extension??-durationServiceRequest.string01
4TQ.4Start Date/TimeTS01ServiceRequest.occurrenceTiming.repeat.boundsPeriod.startServiceRequest.dateTime01TS[DateTime]
5TQ.5End Date/TimeTS01ServiceRequest.occurrenceTiming.repeat.boundsPeriod.endServiceRequest.dateTime01TS[DateTime]
6TQ.6PriorityST01ServiceRequest.priorityServiceRequest.code01ExtendedPriorityCodesA translation from the text priority in the v2 message to a coded value in the request-priority value set will be required.
7TQ.7ConditionST01extension??-conditionServiceRequest.string01
8TQ.8TextTX01ServiceRequest.note(ServiceRequest.Annotation.text)Reference(ServiceRequest.Annotation)0-1
9TQ.9ConjunctionID01
10TQ.10Order SequencingOSD01
11TQ.11Occurrence DurationCE01Note that the v2 base standard data type of CE is incorrect, but since it always has been CE it is not clear how implementers actually put a time and unit in this field. It is up to the implementer how best to parse this and use the occurrenceTiming.repeat.duration and durationUnits.
12TQ.12Total OccurrencesNM01ServiceRequest.occurrenceTiming.repeat.countServiceRequest.positiveInt01

Generated Narrative: ConceptMap datatype-tq-to-servicerequest

Mapping from TQ to ServiceRequest


Group 1 Mapping from unspecified code system to unspecified code system

Source CodeRelationshipTarget CodeComment
TQ.1 (Quantity)is equivalent toquantityQuantity
TQ.2 (Interval)is equivalent tooccurrenceTiming
TQ.3 (Duration)is equivalent tooccurenceTiming.repeat.boundsDuration.valueSee notes on TQ.3 in v2.5.1 for likely formats that will be used in the v2 message.
TQ.3 (Duration)is equivalent tooccurenceTiming.repeat.boundsDuration.unitSee notes on TQ.3 in v2.5.1 for likely formats that will be used in the v2 message.
TQ.3 (Duration)is equivalent tooccurenceTiming.repeat.boundsDuration.system
TQ.4 (Start Date/Time)is equivalent tooccurrenceTiming.repeat.boundsPeriod.start
TQ.5 (End Date/Time)is equivalent tooccurrenceTiming.repeat.boundsPeriod.end
TQ.6 (Priority)is equivalent topriorityA translation from the text priority in the v2 message to a coded value in the request-priority value set will be required.
TQ.8 (Text)is equivalent tonote(Annotation.text)
TQ.12 (Total Occurrences)is equivalent tooccurrenceTiming.repeat.count

Notes: