Release 4

This page is part of the FHIR Specification (v4.0.1: R4 - Mixed Normative and STU) in it's permanent home (it will always be available at this URL). 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 Code System RoleLinkType

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

This code system (http://terminology.hl7.org/CodeSystem/v3-RoleLinkType) is defined as part of HL7 v3.

Summary

Defining URL:http://terminology.hl7.org/CodeSystem/v3-RoleLinkType
Version:2018-08-12
Name:v3.RoleLinkType
Title:v3 Code System RoleLinkType
Definition:

**** MISSING DEFINITIONS ****

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

This Code system is used in the following value sets:

Release Date: 2018-08-12

LevelCodeDisplayDefinition
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:
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.
2  CONT has contactThis relationship indicates the target Role provides or receives information regarding the target role. For example, AssignedEntity is a contact for a ServiceDeliveryLocation.
2  DIRAUTH has direct authority over The source Role has direct authority over the target role in a chain of authority.
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.
2  INDAUTH has indirect authority over The source Role has indirect authority over the target role in a chain of authority.
2  PART has part The target Role is part of the Source Role.
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.