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

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

ValueSet: R5V3RoleClassManagedEntityForR4B

Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R5-v3-RoleClassManagedEntity-for-R4B Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: R5V3RoleClassManagedEntityForR4B

This cross-version ValueSet represents content from http://terminology.hl7.org/ValueSet/v3-RoleClassManagedEntity|2.0.0 for use in FHIR R4B.

This value set is part of the cross-version definitions generated to enable use of the value set http://terminology.hl7.org/ValueSet/v3-RoleClassManagedEntity|2.0.0 as defined in FHIR R5 in FHIR R4B.

The source value set is bound to the following FHIR R5 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-RoleClassManagedEntity|2.0.0, defined in FHIR R5 does not have any mapping to FHIR R4B

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-RoleClass version 📍3.1.0
    CodeDisplayDefinition
    ACCESSaccessA role in which the playing entity (material) provides access to another entity. The principal use case is intravenous (or other bodily) access lines that preexist and need to be referred to for medication routing instructions.
    HLDheld entityEntity that is currently in the possession of a holder (scoper), who holds, or uses it, usually based on some agreement with the owner.
    MNTmaintained entityAn entity (player) that is maintained by another entity (scoper). This is typical role held by durable equipment. The scoper assumes responsibility for proper operation, quality, and safety.
    OWNowned entityAn Entity (player) for which someone (scoper) is granted by law the right to call the material (player) his own. This entitles the scoper to make decisions about the disposition of that material.

 

Expansion

This value set expansion contains 4 concepts.

SystemVersionCodeDisplayDefinitionJSONXML
http://terminology.hl7.org/CodeSystem/v3-RoleClass3.1.0  ACCESSaccess

A role in which the playing entity (material) provides access to another entity. The principal use case is intravenous (or other bodily) access lines that preexist and need to be referred to for medication routing instructions.

http://terminology.hl7.org/CodeSystem/v3-RoleClass3.1.0  HLDheld entity

Entity that is currently in the possession of a holder (scoper), who holds, or uses it, usually based on some agreement with the owner.

http://terminology.hl7.org/CodeSystem/v3-RoleClass3.1.0  MNTmaintained entity

An entity (player) that is maintained by another entity (scoper). This is typical role held by durable equipment. The scoper assumes responsibility for proper operation, quality, and safety.

http://terminology.hl7.org/CodeSystem/v3-RoleClass3.1.0  OWNowned entity

An Entity (player) for which someone (scoper) is granted by law the right to call the material (player) his own. This entitles the scoper to make decisions about the disposition of that material.

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