HL7 Terminology
1.0.0 - Publication

This page is part of the HL7 Terminology (v1.0.0: Release) based on FHIR R4. This is the current published version. For a full list of available versions, see the Directory of published versions

RoleClassEquivalentEntity

Summary

Defining URL:http://terminology.hl7.org/ValueSet/v3-RoleClassEquivalentEntity
Version:2.0.0
Name:RoleClassEquivalentEntity
Status:Active
Title:RoleClassEquivalentEntity
OID:2.16.840.1.113883.1.11.20270 (for OID based terminology systems)
Source Resource:XML / JSON / Turtle

References

This value set is not used

Content Logical Definition

Logical Definition (CLD)

 

Expansion

This value set contains 3 concepts

Expansion based on RoleClass v2.0.0 (CodeSystem)

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

LvlCodeDisplayDefinition
0EQUIVequivalent entity**Description:** Specifies the player Entity (the equivalent Entity) as an Entity that is considered to be equivalent to a reference Entity (scoper). The equivalence is in principle a symmetric relationship, however, it is expected that the scoper is a reference entity which serves as reference entity for multiple different equivalent entities. **Examples:** An innovator's medicine formulation is the reference for "generics", i.e., formulations manufactured differently but having been proven to be biologically equivalent to the reference medicine. Another example is a reference ingredient that serves as basis for quantity specifications (basis of strength, e.g., metoprolol succinate specified in terms of metoprolol tartrate.)
1  SAMEsameThe "same" role asserts an identity between playing and scoping entities, i.e., that they are in fact two records of the same entity instance, and, in the case of discrepancies (e.g different DOB, gender), that one or both are in error. *Usage:* playing and scoping entities must have same classCode, but need not have identical attributes or values. *Example:* a provider registry maintains sets of conflicting demographic data for what is reported to be the same individual.
1  SUBYsubsumed byRelates a prevailing record of an Entity (scoper) with another record (player) that it subsumes. *Examples:* Show a correct new Person object (scoper) that subsumes one or more duplicate Person objects that had accidentally been created for the same physical person. *Constraints:* Both the player and scoper must have the same classCode.

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