FHIR Cross-Version Extensions package for FHIR R4B from FHIR R3 - Version 0.0.1-snapshot-2. See the Directory of published versions
| Official URL: http://hl7.org/fhir/3.0/ValueSet/R3-v2-0277-for-R4B | Version: 0.0.1-snapshot-2 | |||
| Standards status: Informative | Maturity Level: 0 | Computable Name: R3_v2_0277_for_R4B | ||
| This cross-version ValueSet represents concepts from http://hl7.org/fhir/ValueSet/v2-0277 | 2.8.2 for use in FHIR R4B. Concepts not present here have direct equivalent mappings crossing all versions from R3 to R4B. |
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://hl7.org/fhir/v2/0277 version 2.8.2| Code | Display |
| Complete | A request to add a completed appointment, used to maintain records of completed appointments that did not appear in the schedule (e.g. STAT, walk-in, etc.) |
| Normal | Routine schedule request type – default if not valued |
| Tentative | A request for a tentative (e.g. “penciled in”) appointment |
This value set expansion contains 3 concepts.
| Code | System | Display |
| Complete | http://hl7.org/fhir/v2/0277 | A request to add a completed appointment, used to maintain records of completed appointments that did not appear in the schedule (e.g. STAT, walk-in, etc.) |
| Normal | http://hl7.org/fhir/v2/0277 | Routine schedule request type – default if not valued |
| Tentative | http://hl7.org/fhir/v2/0277 | A request for a tentative (e.g. “penciled in”) appointment |
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 |