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 TQnull to Task Map (Experimental)

Official URL: http://hl7.org/fhir/uv/v2mappings/datatype-tq-priority-to-task Version: 1.0.0-ballot
Active as of 2024-07-28 Computable Name: DatatypeTQPriorityToTask

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

This ConceptMap represents the mapping from the HL7 V2 TQ Data Type to the FHIR Task 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 MappingVocabularyAssignment
1TQ.1QuantityCQ01
2TQ.2IntervalRI01
3TQ.3DurationST01
3TQ.3DurationST01
4TQ.4Start Date/TimeTS01
5TQ.5End Date/TimeTS01
6TQ.6PriorityST01Task.priorityTask.code01PriorityA translation from the text priority in the v2 message to a coded value in the request-priority value set will be required.
7TQ.7ConditionST01
8TQ.8TextTX01
9TQ.9ConjunctionID01
10TQ.10Order SequencingOSD01
11TQ.11Occurrence DurationCE01
12TQ.12Total OccurrencesNM01

Generated Narrative: ConceptMap datatype-tq-priority-to-task

Mapping from TQ to Task


Group 1 Mapping from unspecified code system to unspecified code system

Source Concept DetailsRelationshipTarget Concept DetailsCommentProperties
Codes from vocabularymapCodes from
TQ.6PriorityPriorityis equivalent toprioritypriorityA translation from the text priority in the v2 message to a coded value in the request-priority value set will be required.

Notes: