This page is part of the US Core (v8.0.0-ballot: STU8 Ballot 1) based on FHIR (HL7® FHIR® Standard) R4. The current version which supersedes this version is 7.0.0. For a full list of available versions, see the Directory of published versions
Official URL: http://hl7.org/fhir/us/core/ValueSet/us-core-laboratory-test-codes | Version: 8.0.0-ballot | |||
Standards status: Trial-use | Maturity Level: 3 | Computable Name: USCoreLaboratoryTestCodes | ||
Other Identifiers: OID:2.16.840.1.113883.4.642.40.2.48.25 | ||||
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 |
Laboratory LOINC codes: From the introduction to August 2022 LOINC Users' guide; "The current scope of the existing laboratory portion of the LOINC database includes all observations reported by clinical laboratories, including the specialty areas: chemistry, including therapeutic drug monitoring and toxicology; hematology; serology; blood bank; microbiology; cytology; surgical pathology; and fertility.
References
Changes since version 7.0.0:
Generated Narrative: ValueSet us-core-laboratory-test-codes
http://loinc.org
where CLASSTYPE = 1
Generated Narrative: ValueSet
Expansion based on Loinc v2.78
This value set contains 0 concepts
Code | System | Display |
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 |