HL7 Terminology (THO)
5.4.0 - Continuous Process Integration (ci build) International flag

HL7 Terminology (THO), published by HL7 International - Vocabulary Work Group. This guide is not an authorized publication; it is the continuous build for version 5.4.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/UTG/ and changes regularly. See the Directory of published versions

ValueSet: RoleClassOntological

Official URL: http://terminology.hl7.org/ValueSet/v3-RoleClassOntological Version: 3.0.0
Active as of 2014-03-26 Responsible: Health Level Seven International Computable Name: RoleClassOntological
Other Identifiers: urn:ietf:rfc:3986#Uniform Resource Identifier (URI)#urn:oid:2.16.840.1.113883.1.11.10428

Copyright/Legal: This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license

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

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)

This value set includes codes based on the following rules:

This value set excludes codes based on the following rules:

 

Expansion

Expansion based on codesystem RoleClass v4.0.0 (CodeSystem)

This value set contains 7 concepts.

CodeSystemDisplayInactiveDefinitionstatus
  EQUIVhttp://terminology.hl7.org/CodeSystem/v3-RoleClassequivalent 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.)

  SAMEhttp://terminology.hl7.org/CodeSystem/v3-RoleClasssame

The "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.

  SUBYhttp://terminology.hl7.org/CodeSystem/v3-RoleClasssubsumed by

Relates 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.

  GENhttp://terminology.hl7.org/CodeSystem/v3-RoleClasshas generalization

Relates a specialized material concept (player) to its generalization (scoper).

  GRIChttp://terminology.hl7.org/CodeSystem/v3-RoleClasshas generic

A special link between pharmaceuticals indicating that the target (scoper) is a generic for the source (player).

  INSThttp://terminology.hl7.org/CodeSystem/v3-RoleClassinstance

An individual piece of material (player) instantiating a class of material (scoper).

  SUBShttp://terminology.hl7.org/CodeSystem/v3-RoleClasssubsumerinactive

An entity that subsumes the identity of another. Used in the context of merging documented entity instances. Both the player and scoper must have the same classCode.

The use of this code is deprecated in favor of the term SUBY which is its inverse and is more ontologically correct.

deprecated

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

History

DateActionCustodianAuthorComment
2023-11-14reviseTSMGMarc DuteauAdd standard copyright and contact to internal content; up-476
2022-10-18reviseTSMGMarc DuteauFixing missing metadata; up-349
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