Release 5 Preview #1

This page is part of the FHIR Specification (v4.2.0: R5 Preview #1). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4 R3

4.4.2.107 HL7 v3 Value Set RoleLinkType

Vocabulary Work Group Maturity Level: N/AExternal Use Context: Any

This value set (http://terminology.hl7.org/ValueSet/v3-RoleLinkType) is defined as part of HL7 v3.

Summary

Defining URL:http://terminology.hl7.org/ValueSet/v3-RoleLinkType
Version:2019-07-31
Name:v3.RoleLinkType
Title:v3 Code System RoleLinkType
Definition:

**** MISSING DEFINITIONS ****

OID:2.16.840.1.113883.1.11.11603 (for OID based terminology systems)
Source ResourceXML / JSON

This value set is used in the following places:

  • CodeSystem: This value set is the designated 'entire code system' value set for v3.RoleLinkType

This value set includes codes from the following code systems:

 

This expansion generated 31 Dec 2019


This value set contains 8 concepts

Expansion based on http://terminology.hl7.org/CodeSystem/v3-RoleLinkType version 2019-07-31

All codes from system http://terminology.hl7.org/CodeSystem/v3-RoleLinkType

LvlCodeDisplayDefinition
0RELrelatedAn 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:
1  BACKUPis backup forThis 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.
1  CONThas contactThis relationship indicates the target Role provides or receives information regarding the target role. For example, AssignedEntity is a contact for a ServiceDeliveryLocation.
1  DIRAUTHhas direct authority overThe source Role has direct authority over the target role in a chain of authority.
1  IDENTIdentificationDescription: 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.
1  INDAUTHhas indirect authority overThe source Role has indirect authority over the target role in a chain of authority.
1  PARThas partThe target Role is part of the Source Role.
1  REPLreplacesThis 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.