HL7 Terminology (THO)
5.5.0 - Publication International flag

This page is part of the HL7 Terminology (v5.5.0: Release) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, 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: urn:ietf:rfc:3986#Uniform Resource Identifier (URI)#urn: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

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:


This code system defines the following properties for its concepts

statushttp://terminology.hl7.org/CodeSystem/utg-concept-properties#statuscodeStatus of the concept
deprecatedhttp://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-table-deprecatedcodeVersion of HL7 in which the code was deprecated
v2-concCommenthttp://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concCommentstringV2 Concept Comment


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

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


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.