HL7 Terminology (THO)
7.1.0 - Publication
This page is part of the HL7 Terminology (v7.1.0: Release) based on FHIR (HL7® FHIR® Standard) v5.0.0. This is the current published version. For a full list of available versions, see the Directory of published versions
| Official URL: http://terminology.hl7.org/ValueSet/v3-RoleClassSame | Version: 3.0.0 | ||||
| Responsible: Health Level Seven International | Computable Name: RoleClassSame | ||||
| Other Identifiers: OID:2.16.840.1.113883.1.11.20168 | |||||
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.html |
|||||
The "same" roleclass asserts an identity between playing and scoping entities: that they are in fact instances of the same entity 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.
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
Language: en
http://terminology.hl7.org/CodeSystem/v3-RoleClass version 📦5.0.0 where concept is-a SAME
Expansion performed internally based on codesystem RoleClass v5.0.0 (CodeSystem)
This value set contains 1 concepts
| System | Code | Display (en) | Definition | JSON | XML |
http://terminology.hl7.org/CodeSystem/v3-RoleClass | SAME | same | 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. |
Description of the above table(s).
History
| Date | Action | Author | Custodian | Comment |
| 2023-11-14 | revise | Marc Duteau | TSMG | Add standard copyright and contact to internal content; up-476 |
| 2022-10-18 | revise | Marc Duteau | TSMG | Fixing missing metadata; up-349 |
| 2020-05-06 | revise | Ted Klein | Vocabulary WG | Migrated to the UTG maintenance environment and publishing tooling. |
| 2014-03-26 | revise | Vocabulary (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 |