Analysis of clinical specimens to obtain information about the health of a patient.

Data Element

Documented findings of the analysis of a tested specimen. Includes both structured and unstructured (narrative) components.


Improve the defintion of the different types of result values

As highlighted in comment and also requested by including more detail around the type of results, with furhter constraint on the hierachies within SNOMED CT that properly represent the expected concepts: narrative (not coded) - usable for human consumption qualitative (coded) using different hierarchies within SNOMED CT: organism hierarchy for micro results, qualifier value for ordinal results, clinical findings for any others quantitative using UCUM to express the unit of measure (as also pointed out in this comment: APHL also supports the reconciliation (as requested in this comment: with this level 2 data element Laboratory Result Value but prefers that name for this element.

CAP Comment on Values/Results Data Element

The College of American Pathologists (CAP) recommends replacing this data element with the Level 2 data element Laboratory Result Value. 

Laboratory results (date and timestamps)

Vizient recommends adding to USCDI v3 Laboratory results (date and timestamps). Date and time stamps would allow for trending of labs over time. This could be especially helpful when initially adding patient data into Fast Healthcare Interoperability Resources (FHIR) databases since the upload date would be similar for all results.

Rename the element to Result Value; clarify its definition/use

This element should be called Result Value (to differentiate it from the performed test, which some also refer to as "result") (in v2 reported in OBX-5, in C-CDA and FHIR in observation.value). While the definition indicates this captures structured and unstructured data it is missing all the detail around how to address the different formats:
  • unstructured = narrative results use formated text, are human readable, but not easily usable for computers and harder to use in data comparison
  • structured results fall into several categories and should be represented as follows:
    • For qualitative tests:
      • Coded to SNOMED CT drawn from organism hierarchy for organism names; drwan from qualifier hierachy for presence/absence findings and other ordinal results; drawn from clinical findings for pathology, microscopy, microbiology
      • include the original text the coding was based on, if different from the description of the code
    • For quantitative tests:
      • include (in a separate field) the units of measure – coded to UCUM) - this should NOT be sent as a string in a single result field
      • use a structured numeric datatype to allow support for ranges, ratios and smaller than/greater than statements 
This is a subtype of the proposed element Observation Value (, so if that is added clarification between when to use which would be needed. This is a CLIA required element.

Addition to my comment above

The level 2 element supports the renaming - these two elements need to be reconciled.

Applicable stsandards for lab results

The Regenstrief LOINC team recommends adding the following Applicable Standard(s) text to the Values/Results row: “SNOMED CT for qualitative results, UCUM units of measure to accompany quantitative results.”

Clarify applicable standards for lab results

There is a need for appropriate lab codes (LOINC and SNOMED) to pass from LIS to EHR.  The codes need to be readily available in the EHR.  We are aware that this is a known issue: Lab results that are physical quantities should use UCUM for units. Coded lab results for microorganisms should use SNOMED CT.  Antimicrobial susceptibility test interpretation should use HL7 V3 Observation Interpretation.  

Log in or register to post comments