This page is part of the FHIR Specification (v5.0.0: R5 - STU). This is the current published version. 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: 1 | Draft | Use Context: Country: World, Not Intended for Production use |
Official URL: http://hl7.org/fhir/ValueSet/encounter-type
|
Version: 5.0.0 | |||
draft as of 2023-03-26 | Computable Name: EncounterType | |||
Flags: Experimental | OID: 2.16.840.1.113883.4.642.3.248 |
This value set is used in the following places:
This example value set defines a set of codes that can be used to indicate the type of encounter: a specific code indicating type of service provided.
http://terminology.hl7.org/CodeSystem/encounter-type
This expansion generated 26 Mar 2023
This value set contains 4 concepts
Expansion based on Encounter type v0.1.0 (CodeSystem)
Code | System | Display |
ADMS | http://terminology.hl7.org/CodeSystem/encounter-type | Annual diabetes mellitus screening |
BD/BM-clin | http://terminology.hl7.org/CodeSystem/encounter-type | Bone drilling/bone marrow punction in clinic |
CCS60 | http://terminology.hl7.org/CodeSystem/encounter-type | Infant colon screening - 60 minutes |
OKI | http://terminology.hl7.org/CodeSystem/encounter-type | Outpatient Kenacort injection |
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 |