Properties This code system defines the following properties for its concepts Code URI Type Description Specializes Coding The 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. Generalizes Coding Inverse of Specializes. Only included as a derived relationship. internalId http://terminology.hl7.org/CodeSystem/utg-concept-properties#v3-internal-id code The internal identifier for the concept in the HL7 Access database repository. Name:Role:inboundLink:RoleLink http://terminology.hl7.org/CodeSystem/utg-concept-properties#rim-Role-inbound code Name of inboundLink relationship from Role to RoleLink Name:Role:outboundLink:RoleLink http://terminology.hl7.org/CodeSystem/utg-concept-properties#rim-Role-outbound code Name of outboundLink relationship from Role to RoleLink Sort:Role:inboundLink:RoleLink http://terminology.hl7.org/CodeSystem/utg-concept-properties#rim-Role-inbound-sort code Sort key for inboundLink relationship from Role to RoleLink Sort:Role:outboundLink:RoleLink http://terminology.hl7.org/CodeSystem/utg-concept-properties#rim-Role-outbound-sort code Sort key for outboundLink relationship from Role to RoleLink status http://hl7.org/fhir/concept-properties#status code Designation 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 hierarchy: Lvl Code Display Definition internalId Name:Role:inboundLink:RoleLink Name:Role:outboundLink:RoleLink Sort:Role:inboundLink:RoleLink Sort:Role:outboundLink:RoleLink status 1 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: 21429 related relatedTo A________ 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. 21302 backup backupFor AE_______ 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. 23100 contactFor contact AF_______ AF_______ active 2 DIRAUTH has direct authority over The source Role has direct authority over the target role in a chain of authority. 11605 directAuthority directAuthorityOver AA_______ 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. 22184 active 2 INDAUTH has indirect authority over The source Role has indirect authority over the target role in a chain of authority. 11606 indirectAuthority indirectAuthorithyOver AB_______ AB_______ active 2 PART has part The target Role is part of the Source Role. 11604 partOf part AC_______ 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. 15952 replacedBy replacementOf AD_______ AD_______ active
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 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
The 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.
Inverse of Specializes. Only included as a derived relationship.
The internal identifier for the concept in the HL7 Access database repository.
Name of inboundLink relationship from Role to RoleLink
Name of outboundLink relationship from Role to RoleLink
Sort key for inboundLink relationship from Role to RoleLink
Sort key for outboundLink relationship from Role to RoleLink
Designation of a concept's state. Normally is not populated unless the state is retired.
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:*
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.
This relationship indicates the target Role provides or receives information regarding the target role. For example, AssignedEntity is a contact for a ServiceDeliveryLocation.
The source Role has direct authority over the target role in a chain of authority.
**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.
The source Role has indirect authority over the target role in a chain of authority.
The target Role is part of the Source Role.
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.