STU3 Candidate

This page is part of the FHIR Specification (v1.8.0: STU 3 Draft). 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: R4B R4 R3 R2

4.3.1.286 Value Set http://hl7.org/fhir/ValueSet/participantrequired

This is a value set defined by the FHIR project.

Summary

Defining URL: http://hl7.org/fhir/ValueSet/participantrequired
Name: ParticipantRequired
Definition: Is the Participant required to attend the appointment.
Committee: Patient Administration Work Group
OID: 2.16.840.1.113883.4.642.2.286 (for OID based terminology systems)
Source Resource XML / JSON

This value set is used in the following places:

4.3.1.286.1 Content Logical Definition

This value set includes codes from the following code systems:

 

4.3.1.286.2 Expansion

This expansion generated 06 Dec 2016

This value set contains 3 concepts

Expansion based on http://hl7.org/fhir/participantrequired version 1.8.0

All codes from system http://hl7.org/fhir/participantrequired

Code Display Definition
required Required The participant is required to attend the appointment.
optional Optional The participant may optionally attend the appointment.
information-only Information Only The participant is excluded from the appointment, and may not be informed of the appointment taking place. (Appointment is about them, not for them - such as 2 doctors discussing results about a patient's test).

 

See the full registry of value sets defined as part of FHIR.

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
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)
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