This page is part of the FHIR Specification (v5.0.0-ballot: R5 Ballot - see ballot notes). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2
Patient Administration Work Group | Maturity Level: 3 | Trial Use | Use Context: Any |
This is a value set defined by the FHIR project.
Summary
Defining URL: | http://hl7.org/fhir/ValueSet/encounter-participant-type |
Version: | 5.0.0-ballot |
Name: | ParticipantType |
Title: | |
Status: | draft |
Definition: | This value set defines a set of codes that can be used to indicate how an individual participates in an encounter. |
Committee: | Patient Administration Work Group |
OID: | 2.16.840.1.113883.4.642.3.250 (for OID based terminology systems) |
Flags: |
This value set is used in the following places:
This value set includes codes based on the following rules:
http://terminology.hl7.org/CodeSystem/v3-ParticipationType
where concept is-a _ParticipationAncillary http://terminology.hl7.org/CodeSystem/participant-type
This value set excludes codes based on the following rules:
http://terminology.hl7.org/CodeSystem/v3-ParticipationType
Code | Display | Definition |
_ParticipationAncillary | ParticipationAncillary | Participations related, but not primary to an act. The Referring, Admitting, and Discharging practitioners must be the same person as those authoring the ControlAct event for their respective trigger events. |
This expansion generated 10 Sep 2022
This value set contains 9 concepts
Expansion based on:
Code | System | Display | Definition |
ADM | http://terminology.hl7.org/CodeSystem/v3-ParticipationType | admitter | The practitioner who is responsible for admitting a patient to a patient encounter. |
ATND | http://terminology.hl7.org/CodeSystem/v3-ParticipationType | attender | The practitioner that has responsibility for overseeing a patient's care during a patient encounter. |
CALLBCK | http://terminology.hl7.org/CodeSystem/v3-ParticipationType | callback contact | A person or organization who should be contacted for follow-up questions about the act in place of the author. |
CON | http://terminology.hl7.org/CodeSystem/v3-ParticipationType | consultant | An advisor participating in the service by performing evaluations and making recommendations. |
DIS | http://terminology.hl7.org/CodeSystem/v3-ParticipationType | discharger | The practitioner who is responsible for the discharge of a patient from a patient encounter. |
ESC | http://terminology.hl7.org/CodeSystem/v3-ParticipationType | escort | Only with Transportation services. A person who escorts the patient. |
REF | http://terminology.hl7.org/CodeSystem/v3-ParticipationType | referrer | A person having referred the subject of the service to the performer (referring physician). Typically, a referring physician will receive a report. |
translator | http://terminology.hl7.org/CodeSystem/participant-type | Translator | A translator who is facilitating communication with the patient during the encounter. |
emergency | http://terminology.hl7.org/CodeSystem/participant-type | Emergency | A person to be contacted in case of an emergency during the encounter. |
See the full registry of value sets defined as part of FHIR.
Explanation of the columns that may appear on this page:
Lvl | A few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information |
Source | 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). If the code is in italics, this indicates that the code is not selectable ('Abstract') |
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 |