HL7 Terminology (THO)
7.1.0 - Continuous Process Integration (ci build)
HL7 Terminology (THO), published by HL7 International - Vocabulary Work Group. This guide is not an authorized publication; it is the continuous build for version 7.1.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
| Official URL: http://terminology.hl7.org/ValueSet/v3-xDocumentEntrySubject | Version: 3.0.0 | ||||
| Responsible: Health Level Seven International | Computable Name: XDocumentEntrySubject | ||||
| Other Identifiers: OID:2.16.840.1.113883.1.11.19367 | |||||
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 |
|||||
Used to represent the role(s) of those who can serve as subjects of the contents of a clinical document.
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| Code | Display | Definition |
| PAT | patient | A Role of a LivingSubject (player) as an actual or potential recipient of health care services from a healthcare provider organization (scoper). *Usage Note:* Communication about relationships between patients and specific healthcare practitioners (people) is not done via scoper. Instead this is generally done using the CareProvision act. This allows linkage between patient and a particular healthcare practitioner role and also allows description of the type of care involved in the relationship. |
| PRS | personal relationship | Links two entities with classCode PSN (person) in a personal relationship. The character of the relationship must be defined by a PersonalRelationshipRoleType code. The player and scoper are determined by PersonalRelationshipRoleType code as well. |
| SPEC | specimen | A role played by a material entity that is a specimen for an act. It is scoped by the source of the specimen. |
Expansion performed internally based on codesystem RoleClass v5.0.0 (CodeSystem)
This value set contains 3 concepts
| System | Code | Display (en) | Definition | JSON | XML |
http://terminology.hl7.org/CodeSystem/v3-RoleClass | PAT | patient | A Role of a LivingSubject (player) as an actual or potential recipient of health care services from a healthcare provider organization (scoper). Usage Note: Communication about relationships between patients and specific healthcare practitioners (people) is not done via scoper. Instead this is generally done using the CareProvision act. This allows linkage between patient and a particular healthcare practitioner role and also allows description of the type of care involved in the relationship. | ||
http://terminology.hl7.org/CodeSystem/v3-RoleClass | PRS | personal relationship | Links two entities with classCode PSN (person) in a personal relationship. The character of the relationship must be defined by a PersonalRelationshipRoleType code. The player and scoper are determined by PersonalRelationshipRoleType code as well. | ||
http://terminology.hl7.org/CodeSystem/v3-RoleClass | SPEC | specimen | A role played by a material entity that is a specimen for an act. It is scoped by the source of the specimen. |
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 |