HL7 v2.9.1 Vocabulary
0.2.0 - ci-build

HL7 v2.9.1 Vocabulary, published by HL7/FO. This guide is not an authorized publication; it is the continuous build for version 0.2.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/frankoemig/hl7.v2.terminology.v291/ and changes regularly. See the Directory of published versions

## CodeSystem: Relationship Type (2.9.1 - 1.0.0) (Experimental)

Official URL: http://terminology.hl7.org/v2plusvocab/CodeSystem/v2CS-relationshipType | Version: 1.0.0
Active as of 2026-03-13 | Computable Name: V2CS-relationshipType
Other Identifiers: OID:2.16.840.1.113883.18.448, urn:ietf:rfc:3986#Uniform Resource Identifier (URI)#http://terminology.hl7.org/v2plusvocab/CodeSystem/v2-0948
Copyright/Legal: HL7 Inc., 2026

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

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

- Hl7VSrelationshipType

Properties

This code system defines the following properties for its concepts

Name | Code | URI | Type | Description
version introduced | versionIntroduced | http://terminology.hl7.org/v2plusvocab/CodeSystem/Property#versionIntroduced | string | version when was this code introduced
version deprecated | versionDeprecated | http://terminology.hl7.org/v2plusvocab/CodeSystem/Property#versionDeprecated | string | version when was this code deprecated
status | status | http://hl7.org/fhir/concept-properties#status | code | A code that indicates the status of the concept. Typical values are active, experimental, deprecated, and retired
comment, to suppress IG-publisher warning, to be replaced with standard later | comment | http://terminology.hl7.org/v2plusvocab/CodeSystem/Property#comment | string | A string that provides additional detail pertinent to the use or understanding of the concept
usage | usage | http://terminology.hl7.org/v2plusvocab/CodeSystem/Property#usage | string | usage notes for this code
modified | modified | http://terminology.hl7.org/v2plusvocab/CodeSystem/Property#modified | dateTime | date of last modification

Concepts

This case-sensitive code system `http://terminology.hl7.org/v2plusvocab/CodeSystem/v2CS-relationshipType` defines the following codes:

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