HL7 Terminology (THO)
5.5.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 5.5.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: RoleLinkType

Official URL: http://terminology.hl7.org/CodeSystem/v3-RoleLinkType Version: 3.0.0
Active as of 2019-03-20 Responsible: Health Level Seven International Computable Name: RoleLinkType
Other Identifiers: urn:ietf:rfc:3986#Uniform Resource Identifier (URI)#urn:oid:2.16.840.1.113883.5.107

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

A code specifying the meaning and purpose of every RoleLink instance. Each of its values implies specific constraints to what kinds of Role objects can be related and in which way.

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

Properties

This code system defines the following properties for its concepts

CodeURITypeDescription
SpecializesCodingThe child code is a more narrow version of the concept represented by the parent code. I.e. Every child concept is also a valid parent concept. Used to allow determination of subsumption. Must be transitive, irreflexive, antisymmetric.
GeneralizesCodingInverse of Specializes. Only included as a derived relationship.
internalIdhttp://terminology.hl7.org/CodeSystem/utg-concept-properties#v3-internal-idcodeThe internal identifier for the concept in the HL7 Access database repository.
Name:Role:inboundLink:RoleLinkhttp://terminology.hl7.org/CodeSystem/utg-concept-properties#rim-Role-inboundcodeName of inboundLink relationship from Role to RoleLink
Name:Role:outboundLink:RoleLinkhttp://terminology.hl7.org/CodeSystem/utg-concept-properties#rim-Role-outboundcodeName of outboundLink relationship from Role to RoleLink
Sort:Role:inboundLink:RoleLinkhttp://terminology.hl7.org/CodeSystem/utg-concept-properties#rim-Role-inbound-sortcodeSort key for inboundLink relationship from Role to RoleLink
Sort:Role:outboundLink:RoleLinkhttp://terminology.hl7.org/CodeSystem/utg-concept-properties#rim-Role-outbound-sortcodeSort key for outboundLink relationship from Role to RoleLink
statushttp://hl7.org/fhir/concept-properties#statuscodeDesignation of a concept's state. Normally is not populated unless the state is retired.

Concepts

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

LvlCodeDisplayDefinitioninternalIdName:Role:inboundLink:RoleLinkName:Role:outboundLink:RoleLinkSort:Role:inboundLink:RoleLinkSort:Role:outboundLink:RoleLinkstatus
1REL related

An action taken with respect to a subject Entity by a regulatory or authoritative body with supervisory capacity over that entity. The action is taken in response to behavior by the subject Entity that body finds to be undesirable.

Suspension, license restrictions, monetary fine, letter of reprimand, mandated training, mandated supervision, etc.Examples:

21429relatedrelatedToA________A________active
2  BACKUP is backup for

This relationship indicates the source Role is available to the target Role as a backup. An entity in a backup role will be available as a substitute or replacement in the event that the entity assigned the role is unavailable. In medical roles where it is critical that the function be performed and there is a possibility that the individual assigned may be ill or otherwise indisposed, another individual is assigned to cover for the individual originally assigned the role. A backup may be required to be identified, but unless the backup is actually used, he/she would not assume the assigned entity role.

21302backupbackupForAE_______AE_______active
2  CONT has contact

This relationship indicates the target Role provides or receives information regarding the target role. For example, AssignedEntity is a contact for a ServiceDeliveryLocation.

23100contactForcontactAF_______AF_______active
2  DIRAUTH has direct authority over

The source Role has direct authority over the target role in a chain of authority.

11605directAuthoritydirectAuthorityOverAA_______AA_______active
2  IDENT Identification

Description: The source role provides identification for the target role. The source role must be IDENT. The player entity of the source role is constrained to be the same as (i.e. the equivalent of, or equal to) the player of the target role if present. If the player is absent from the source role, then it is assumed to be the same as the player of the target role.

22184active
2  INDAUTH has indirect authority over

The source Role has indirect authority over the target role in a chain of authority.

11606indirectAuthorityindirectAuthorithyOverAB_______AB_______active
2  PART has part

The target Role is part of the Source Role.

11604partOfpartAC_______AC_______active
2  REPL replaces

This relationship indicates that the source Role replaces (or subsumes) the target Role. Allows for new identifiers and/or new effective time for a registry entry or a certification, etc.

15952replacedByreplacementOfAD_______AD_______active

History

DateActionAuthorCustodianComment
2023-11-14reviseMarc DuteauTSMGAdd standard copyright and contact to internal content; up-476
2022-10-18reviseMarc DuteauTSMGFixing missing metadata; up-349
2022-02-17 00:00:32+1100reviseGrahame GrieveVocabulary WGPopulate Missing caseSensitive property; UP-286
2020-05-06reviseTed KleinVocabulary WGMigrated to the UTG maintenance environment and publishing tooling.