HL7 Terminology (THO)
5.3.0 - Publication
This page is part of the HL7 Terminology (v5.3.0: Release) based on FHIR R4. 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
Official URL: http://terminology.hl7.org/ValueSet/v3-xServiceEventPerformer | Version: 2.0.0 | |||
Active as of 2014-03-26 | Computable Name: XServiceEventPerformer | |||
Other Identifiers: id: urn:oid:2.16.840.1.113883.1.11.19601 |
Clones using this x_domain should have a name “performer”.
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-ParticipationType
Code | Display | Definition |
PPRF | primary performer | The principal or primary performer of the act. |
PRF | performer | **Definition:** A person, non-person living subject, organization or device that who actually and principally carries out the action. Device should only be assigned as a performer in circumstances where the device is performing independent of human intervention. Need not be the principal responsible actor. **Exampe:** A surgery resident operating under supervision of attending surgeon, a search and rescue dog locating survivors, an electronic laboratory analyzer or the laboratory discipline requested to perform a laboratory test. The performer may also be the patient in self-care, e.g. fingerstick blood sugar. The traditional order filler is a performer. This information should accompany every service event. **Note:** that existing HL7 designs assign an organization as the playing entity of the Role that is the performer. These designs should be revised in subsequent releases to make this the scooping entity for the role involved. |
SPRF | secondary performer | A person assisting in an act through his substantial presence and involvement This includes: assistants, technicians, associates, or whatever the job titles may be. |
This value set contains 3 concepts
Expansion based on codesystem ParticipationType v4.0.0 (CodeSystem)
Code | System | Display | Definition |
PPRF | http://terminology.hl7.org/CodeSystem/v3-ParticipationType | primary performer | The principal or primary performer of the act. |
PRF | http://terminology.hl7.org/CodeSystem/v3-ParticipationType | performer | Definition: A person, non-person living subject, organization or device that who actually and principally carries out the action. Device should only be assigned as a performer in circumstances where the device is performing independent of human intervention. Need not be the principal responsible actor. Exampe: A surgery resident operating under supervision of attending surgeon, a search and rescue dog locating survivors, an electronic laboratory analyzer or the laboratory discipline requested to perform a laboratory test. The performer may also be the patient in self-care, e.g. fingerstick blood sugar. The traditional order filler is a performer. This information should accompany every service event. Note: that existing HL7 designs assign an organization as the playing entity of the Role that is the performer. These designs should be revised in subsequent releases to make this the scooping entity for the role involved. |
SPRF | http://terminology.hl7.org/CodeSystem/v3-ParticipationType | secondary performer | A person assisting in an act through his substantial presence and involvement This includes: assistants, technicians, associates, or whatever the job titles may be. |
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
Date | Action | Author | Custodian | Comment |
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 |