HL7 Terminology (THO)
2.1.34 - Continuous Process Integration (ci build) [UP-218]

HL7 Terminology (THO), published by HL7 International - Vocabulary Work Group. This is not an authorized publication; it is the continuous build for version 2.1.34). 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


Defining URL:http://terminology.hl7.org/CodeSystem/v2-0948
Status:Active as of 2019-12-01

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).

Publisher:HL7, Inc

Copyright HL7. Licensed under creative commons public domain

Content:Complete: All the concepts defined by the code system are included in the code system resource
OID:2.16.840.1.113883.18.448 (for OID based terminology systems)
Value Set:http://terminology.hl7.org/ValueSet/v2-0948 ( is the value set for all codes in this code system)
Source Resource:XML / JSON / Turtle

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


statushttp://terminology.hl7.org/CodeSystem/utg-concept-properties#statusStatus of the conceptcode
deprecatedhttp://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-table-deprecatedVersion of HL7 in which the code was deprecatedcode
v2-concCommenthttp://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concCommentV2 Concept Commentstring

This code system http://terminology.hl7.org/CodeSystem/v2-0948 defines the following codes:

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


2020-05-06reviseVocabulary WGTed KleinMigrated to the UTG maintenance environment and publishing tooling.