HL7.TERMINOLOGY\RoleLinkType

This page is part of the HL7 Terminology (v2.1.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions

ValueSet: RoleLinkType

Summary

Defining URL:

http://terminology.hl7.org/ValueSet/v3-RoleLinkType

Version:

2.0.0

Name:

RoleLinkType

Status:

Active as of 2014-03-26

Definition:

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.

OID:

2.16.840.1.113883.1.11.11603 (for OID based terminology systems)

Source Resource:

XML / JSON / Turtle

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

Include all codes defined in http://terminology.hl7.org/CodeSystem/v3-RoleLinkType

Expansion

This value set contains 8 concepts

Expansion based on RoleLinkType v2.0.0 (CodeSystem)

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

Lvl	Code	Display	Definition
0	REL	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:
1	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.
1	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.
1	DIRAUTH	has direct authority over	The source Role has direct authority over the target role in a chain of authority.
1	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.
1	INDAUTH	has indirect authority over	The source Role has indirect authority over the target role in a chain of authority.
1	PART	has part	The target Role is part of the Source Role.
1	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.

Explanation of the columns that may appear on this page:

Level

A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies

Source

The source of the definition of the code (when the value set draws in codes defined elsewhere)

Code

The code (used as the code in the resource instance)

Display

The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application

Definition

An explanation of the meaning of the concept

Comments

Additional notes about how to use the code

History

Date

Action

Author

Custodian

Comment

2020-05-06

revise