HL7 Terminology (THO)
6.0.0 - Publication International flag

This page is part of the HL7 Terminology (v6.0.0: Release) based on FHIR (HL7® FHIR® Standard) v5.0.0. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

ValueSet: x_DocumentEntrySubject

Official URL: http://terminology.hl7.org/ValueSet/v3-xDocumentEntrySubject Version: 3.0.0
Active as of 2014-03-26 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)

Logical Definition (CLD)

Generated Narrative: ValueSet v3-xDocumentEntrySubject

Language: en

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-RoleClass
    CodeDisplayDefinition
    PATpatientA 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.
    PRSpersonal relationshipLinks 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.
    SPECspecimenA role played by a material entity that is a specimen for an act. It is scoped by the source of the specimen.

 

Expansion

Generated Narrative: ValueSet

Language: en

Expansion based on codesystem RoleClass v4.0.0 (CodeSystem)

This value set contains 3 concepts

CodeSystemDisplayDefinition
  PAThttp://terminology.hl7.org/CodeSystem/v3-RoleClasspatient

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.

  PRShttp://terminology.hl7.org/CodeSystem/v3-RoleClasspersonal 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.

  SPEChttp://terminology.hl7.org/CodeSystem/v3-RoleClassspecimen

A role played by a material entity that is a specimen for an act. It is scoped by the source of the specimen.

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