Extensions for Using Data Elements from FHIR R4 in FHIR R5
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR R4 in FHIR R5 - Downloaded Version null See the Directory of published versions

ValueSet: R4V3RoleLinkTypeForR5

Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R4-v3-RoleLinkType-for-R5 Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Responsible: HL7 International / Terminology Infrastructure Computable Name: R4V3RoleLinkTypeForR5

This cross-version ValueSet represents content from http://terminology.hl7.org/ValueSet/v3-RoleLinkType|2018-08-12 for use in FHIR R5.

This value set is part of the cross-version definitions generated to enable use of the value set http://terminology.hl7.org/ValueSet/v3-RoleLinkType|2018-08-12 as defined in FHIR R4 in FHIR R5.

The source value set is bound to the following FHIR R4 elements:

Note that all concepts are included in this cross-version definition because no concepts have compatible representations

Following are the generation technical comments:

FHIR ValueSet http://terminology.hl7.org/ValueSet/v3-RoleLinkType|2018-08-12, defined in FHIR R4 does not have any mapping to FHIR R5

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 these codes as defined in http://terminology.hl7.org/CodeSystem/v3-RoleLinkType version 📍2018-08-12
    CodeDisplayDefinition
    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.
    CONThas contactThis relationship indicates the target Role provides or receives information regarding the target role. For example, AssignedEntity is a contact for a ServiceDeliveryLocation.
    DIRAUTHhas direct authority overThe source Role has direct authority over the target role in a chain of authority.
    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.
    INDAUTHhas indirect authority overThe source Role has indirect authority over the target role in a chain of authority.
    PARThas partThe target Role is part of the Source Role.
    RELrelatedAn 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:
    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.

 

Expansion

This value set expansion contains 8 concepts.

SystemVersionCodeDisplayDefinitionJSONXML
http://terminology.hl7.org/CodeSystem/v3-RoleLinkType2018-08-12  BACKUPis 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.

http://terminology.hl7.org/CodeSystem/v3-RoleLinkType2018-08-12  CONThas contact

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

http://terminology.hl7.org/CodeSystem/v3-RoleLinkType2018-08-12  DIRAUTHhas direct authority over

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

http://terminology.hl7.org/CodeSystem/v3-RoleLinkType2018-08-12  IDENTIdentification

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.

http://terminology.hl7.org/CodeSystem/v3-RoleLinkType2018-08-12  INDAUTHhas indirect authority over

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

http://terminology.hl7.org/CodeSystem/v3-RoleLinkType2018-08-12  PARThas part

The target Role is part of the Source Role.

http://terminology.hl7.org/CodeSystem/v3-RoleLinkType2018-08-12  RELrelated

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:
http://terminology.hl7.org/CodeSystem/v3-RoleLinkType2018-08-12  REPLreplaces

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
System 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