HL7 Terminology
2.1.0 - Publication

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: RoleClassManagedEntity

Summary

Defining URL:http://terminology.hl7.org/ValueSet/v3-RoleClassManagedEntity
Version:2.0.0
Name:RoleClassManagedEntity
Status:Active as of 2014-03-26
Definition:

**Description:**A value set of role classCodes related to entity management.

OID:2.16.840.1.113883.1.11.20298 (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 these codes as defined in http://terminology.hl7.org/CodeSystem/v3-RoleClass
    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 contains 4 concepts

Expansion based on RoleClass v3.0.0 (CodeSystem)

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

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.

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

DateActionCustodianAuthorComment
2020-05-06reviseVocabulary WGTed KleinMigrated to the UTG maintenance environment and publishing tooling.
2014-03-26revise2014T1_2014-03-26_001283 (RIM release ID)Vocabulary (Woody Beeler) (no record of original request)Lock all vaue sets untouched since 2014-03-26 to trackingId 2014T1_2014_03_26