HL7 Terminology (THO)
6.0.0 - Continuous Process Integration (ci build) International flag

HL7 Terminology (THO), published by HL7 International - Vocabulary Work Group. This guide is not an authorized publication; it is the continuous build for version 6.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/UTG/ and changes regularly. See the Directory of published versions

CodeSystem: v2CS-relationshipType

Official URL: http://terminology.hl7.org/CodeSystem/v2-0948 Version: 2.0.0
Active as of 2019-12-01 Responsible: Health Level Seven International Computable Name: V2CSRelationshipType
Other Identifiers: OID:2.16.840.1.113883.18.448

Copyright/Legal: This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html

HL7-defined code system of concepts that identify the type of relationship identified by Relationship Instance Identifier (REL-3) that is established between the Source Information Instance (REL-4) and the Target Information Instance (REL-5).

Underlying Master Code System for V2 table 0948 (Relationship Type)

This Code system is referenced in the content logical definition of the following value sets:

Generated Narrative: CodeSystem v2-0948


This code system defines the following properties for its concepts

status status http://terminology.hl7.org/CodeSystem/utg-concept-properties#status code Status of the concept
deprecated deprecated http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-table-deprecated code Version of HL7 in which the code was deprecated
V2 Concept Comment v2-concComment http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concComment string V2 Concept Comment


This case-sensitive code system http://terminology.hl7.org/CodeSystem/v2-0948 defines the following codes in a Is-A hierarchy:

CodeDisplayDefinitionV2 Concept Comment
CAUS Causes/caused Source universal service identifier causes/caused the outcome(s) on the target Example: a procedure caused complication(s)
COMP Component of Target universal service identifier is a component of source universal identifier Example: one care plan activity (target) is a component of another care plan activity (source)
CONCR Concurrently Source and target universal service identifier should start concurrently Example: two care plan activities should start concurrently
EVID Evidence Source universal service identifier provides evidence for target universal service identifier Example: observation result provides evidence for certain care plan activity or treatment action
INTF Interferes / interfered Source universal service identifier interferes / interfered with fulfilment of target universal service identifier Example: patient financial or physical constraints interferes / interfered with fulfilment of goal
LIMIT Limits/limited Source universal service identifier limits/limited the fulfillment of target universal service identifier Example: patient condition limits the extend that planned treatment can be implemented
SUCCD Succeeds Target universal service identifier should succeed (starts after end of) source universal service identifier Example: one care plan activity (target) should start after completion of another (source)
SVTGT Service target Target universal service identifier is the object of the service identified by the source universal service identifier Example: An order requests clarification or interpretation of a previous clinical laboratory test result
TRIG Triggers/triggered Source universal service identifier triggers action of target universal service identifier Example: a bleeding complication triggers the review and change in anti-coagulant dosage


2023-11-14reviseMarc DuteauTSMGAdd standard copyright and contact to internal content; up-476
2020-05-06reviseTed KleinVocabulary WGMigrated to the UTG maintenance environment and publishing tooling.