US Core Implementation Guide, published by HL7 International / Cross-Group Projects. This is not an authorized publication; it is the continuous build for version 7.0.0-ballot). This version is based on the current content of https://github.com/HL7/US-Core/ and changes regularly. See the Directory of published versions

• Narrative Content
• XML
• JSON
• TTL

ValueSet: US Core Encounter Type

Official URL: http://hl7.org/fhir/us/core/ValueSet/us-core-encounter-type				Version: 7.0.0-ballot
Standards status: Trial-use			Maturity Level: 3	Computable Name: USCoreEncounterType
Copyright/Legal: 1. This value set includes content from SNOMED CT, which is copyright © 2002+ International Health Terminology Standards Development Organisation (IHTSDO), and distributed by agreement between IHTSDO and HL7. Implementer use of SNOMED CT is not covered by this agreement. Current Procedural Terminology (CPT) is copyright 2020 American Medical Association. All rights reserved

The type of encounter: a specific code indicating type of service provided. This value set includes codes from SNOMED CT decending from the concept 308335008 (Patient encounter procedure (procedure)) and codes from the Current Procedure and Terminology (CPT) found in the following CPT sections:

• 99201-99499 E/M - 99500-99600 home health (mainly nonphysician, such as newborn care in home) - 99605-99607 medication management - 98966-98968 non physician telephone services (subscription to AMA Required)

References

• US Core Encounter Profile

Logical Definition (CLD)

 

Expansion

---

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