HL7 Terminology (THO)
3.1.0 - Publication International flag

This page is part of the HL7 Terminology (v3.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: RoleClassOntological

Official URL: http://terminology.hl7.org/ValueSet/v3-RoleClassOntological Version: 2.0.0
Active as of 2014-03-26 Computable Name: RoleClassOntological
Other Identifiers: : urn:oid:2.16.840.1.113883.1.11.10428

A relationship in which the scoping Entity defines or specifies what the playing Entity is. Thus, the player’s “being” (Greek: ontos) is specified.


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)

This value set includes codes based on the following rules:

This value set excludes codes based on the following rules:



This value set contains 6 concepts

Expansion based on RoleClass v3.1.0 (CodeSystem)

All codes in this table are from the system http://terminology.hl7.org/CodeSystem/v3-RoleClass

EQUIVequivalent 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.)
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.
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.
GENhas generalizationRelates a specialized material concept (player) to its generalization (scoper).
GRIChas genericA special link between pharmaceuticals indicating that the target (scoper) is a generic for the source (player).
INSTinstanceAn individual piece of material (player) instantiating a class of material (scoper).

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


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