FHIR Cross-Version Extensions package for FHIR R4 from FHIR R5 - Version 0.0.1-snapshot-2. See the Directory of published versions
| Official URL: http://hl7.org/fhir/5.0/ValueSet/R5-v3-xDocumentEntrySubject-for-R4 | Version: 0.0.1-snapshot-2 | |||
| Standards status: Informative | Maturity Level: 0 | Computable Name: R5_v3_xDocumentEntrySubject_for_R4 | ||
| This cross-version ValueSet represents concepts from http://terminology.hl7.org/ValueSet/v3-xDocumentEntrySubject | 2.0.0 for use in FHIR R4. Concepts not present here have direct equivalent mappings crossing all versions from R5 to R4. |
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://terminology.hl7.org/CodeSystem/v3-RoleClass version 3.1.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. |
This value set expansion contains 3 concepts.
| Code | System | Display | Definition |
| PAT | http://terminology.hl7.org/CodeSystem/v3-RoleClass | 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 | http://terminology.hl7.org/CodeSystem/v3-RoleClass | 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 | http://terminology.hl7.org/CodeSystem/v3-RoleClass | specimen | 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 |