HL7 Terminology
1.0.0 - Publication

This page is part of the HL7 Terminology (v1.0.0: Release) based on FHIR R4. This is the current published version. For a full list of available versions, see the Directory of published versions

v2CS-relationshipType

Summary

Defining URL:http://terminology.hl7.org/CodeSystem/v2-0948
Version:2.1.0
Name:V2CSRelationshipType
Title:v2CS-relationshipType
Status:Active
Content:All the concepts defined by the code system are included in the code system resource
Definition:

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
OID:2.16.840.1.113883.18.448 (for OID based terminology systems)
Content Mode:Complete
Value Set:http://terminology.hl7.org/ValueSet/v2-0948 ( is the value set for all codes in this code system)
Copyright:

Copyright HL7. Licensed under creative commons public domain

Source Resource:XML / JSON / Turtle

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

v2CS-relationshipType

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

Copyright Statement: Copyright HL7. Licensed under creative commons public domain

Properties

CodeURLDescriptionType
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 Table StatusV2 Concept Comment
CAUS Causes/causedSource universal service identifier causes/caused the outcome(s) on the targetNExample: a procedure caused complication(s)
COMP Component ofTarget universal service identifier is a component of source universal identifierNExample: one care plan activity (target) is a component of another care plan activity (source)
CONCR ConcurrentlySource and target universal service identifier should start concurrentlyNExample: two care plan activities should start concurrently
EVID EvidenceSource universal service identifier provides evidence for target universal service identifierNExample: 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 identifierNExample: 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 identifierNExample: 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 identifierNExample: 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 identifierNExample: 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 identifierNExample: a bleeding complication triggers the review and change in anti-coagulant dosage

History

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