Release 4B

This page is part of the FHIR Specification (v4.3.0: R4B - STU). 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

4.4.1.319 Value Set http://hl7.org/fhir/ValueSet/encounter-type

Patient Administration Work Group Maturity Level: 1Draft Use Context: Not Intended for Production use

This is a value set defined by the FHIR project.

Summary

Defining URL:http://hl7.org/fhir/ValueSet/encounter-type
Version:4.3.0
Name:EncounterType
Title:
Definition:

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.

Committee:Patient Administration Work Group
OID:2.16.840.1.113883.4.642.3.248 (for OID based terminology systems)
Source ResourceXML / JSON

This value set is used in the following places:


 

This expansion generated 28 May 2022


This value set contains 4 concepts

Expansion based on EncounterType v4.3.0 (CodeSystem)

All codes in this table are from the system http://terminology.hl7.org/CodeSystem/encounter-type

CodeDisplay
  ADMSAnnual diabetes mellitus screening
  BD/BM-clinBone drilling/bone marrow punction in clinic
  CCS60Infant colon screening - 60 minutes
  OKIOutpatient Kenacort injection

 

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


Explanation of the columns that may appear on this page:

LvlA 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
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
DisplayThe 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
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code