US Core Implementation Guide
7.0.0 - STU7 United States of America flag

This page is part of the US Core (v7.0.0: STU7) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions. Page versions: STU6.1 STU6 STU5 STU4 STU3

ValueSet: US Core Clinical Note Type

Official URL: http://hl7.org/fhir/us/core/ValueSet/us-core-clinical-note-type Version: 7.0.0
Standards status: Trial-use Maturity Level: 3 Computable Name: USCoreClinicalNoteType
Other Identifiers: OID:2.16.840.1.113883.4.642.40.2.48.5

Copyright/Legal: This material contains content from LOINC (http://loinc.org). LOINC is copyright © 1995-2020, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license at http://loinc.org/license. LOINC® is a registered United States trademark of Regenstrief Institute, Inc

The US Core Clinical Note Type Value Set is a ‘starter set’ of types supported for fetching and storing clinical notes.

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

 

Expansion

Expansion based on Loinc v2.77

This value set contains 5 concepts.

CodeSystemDisplay
  18842-5http://loinc.orgDischarge summary
  11488-4http://loinc.orgConsult note
  34117-2http://loinc.orgHistory and physical note
  11506-3http://loinc.orgProgress note
  28570-0http://loinc.orgProcedure note

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