Opioid Prescribing Support Implementation Guide
2016.4.0 - CI Build
Opioid Prescribing Support Implementation Guide, published by Centers for Disease Control and Prevention (CDC). This guide is not an authorized publication; it is the continuous build for version 2016.4.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/cqframework/opioid-cds-r4/ and changes regularly. See the Directory of published versions
Official URL: http://fhir.org/guides/cdc/opioid-cds/ValueSet/observation-category-laboratory | Version: 2016.4.0 | |||
Active as of 2024-08-29 | Computable Name: ValuesetObservationCategoryLaboratory |
Laboratory Observation Category
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
No formal definition provided for this ValueSet
Generated Narrative: ValueSet observation-category-laboratory
This value set expansion contains 1 concepts.
Code | System | Display | Definition |
laboratory | http://terminology.hl7.org/CodeSystem/observation-category | Laboratory | The results of observations generated by laboratories. Laboratory results are typically generated by laboratories providing analytic services in areas such as chemistry, hematology, serology, histology, cytology, anatomic pathology (including digital pathology), microbiology, and/or virology. These observations are based on analysis of specimens obtained from the patient and submitted to the laboratory. |
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 |