US Core Implementation Guide, published by HL7 International / Cross-Group Projects. This guide is not an authorized publication; it is the continuous build for version 8.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/US-Core/ and changes regularly. See the Directory of published versions
Official URL: http://hl7.org/fhir/us/core/ValueSet/us-core-diagnosticreport-category | Version: 8.0.0 | |||
Standards status: Trial-use | Maturity Level: 3 | Computable Name: USCoreDiagnosticReportCategory | ||
Other Identifiers: OID:2.16.840.1.113883.4.642.40.2.48.8 | ||||
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 Diagnostic Report Category Value Set is a 'starter set' of categories supported for fetching and Diagnostic Reports and notes.
References
Generated Narrative: ValueSet us-core-diagnosticreport-category
http://loinc.org
Code | Display |
LP29684-5 | Radiology |
LP29708-2 | Cardiology |
LP7839-6 | Pathology |
Generated Narrative: ValueSet
Expansion based on Loinc v2.78
This value set contains 3 concepts
Code | System | Display |
LP29684-5 | http://loinc.org | RAD |
LP29708-2 | http://loinc.org | Card |
LP7839-6 | http://loinc.org | PATH |
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 |