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

Data Element
Value/Result
Description (*Please confirm or update this field for the new USCDI version*)

Documented findings of a tested specimen including structured and unstructured components.

Applicable Vocabulary Standard(s)

Applicable Standards (*Please confirm or update this field for the new USCDI version*)
  • SNOMED Clinical Terms (SNOMED CT®) U.S. Edition

View guidance on Applicable Vocabulary Standards and versioning.

Comment

Submitted by BLampkins_CSTE on

CSTE Comment - v5

CSTE is supportive of Riki Merrick's comment from April 2024.

Submitted by Riki Merrick on

Clarify the different formats supported by this data element

As previously commented the definition should be more precise and indicate relationships to other UCSDI elements, when required (first part copied from Regenstrief comment on USCDI+): Recorded value or findings of the analytical test performed on a specimen. Note that the scale of the test influences the format of this data element:
For quantitative tests the format is numeric or structured numeric (to support ranges, titers etc) and often must be interpreted in conjunction with the element "Result Unit of Measure"
For qualitative tests the format can be structured and is coded for ordinal or nominal scale or unstructured text (short or formatted) for narrative scale.
Vocabulary binding is only valid for coded qualitative result types - depending on the scale the binding shifts, so the binding should be more prescriptive based on scale of test:
For nominal scale often SCT in organism hierarchy, example value set: https://phinvads.cdc.gov/vads/ViewValueSet.action?id=64089FFA-B015-4DC7-B470-F20DF5B13BFA
For ordinal scale use SCT from qualifier hierarchy: https://phinvads.cdc.gov/vads/ViewValueSet.action?id=815C6DD4-C5A6-DF11-9BDD-0015173D1785

Corresponds to CLIA element in §493.1291(c)(6), §493.1291(c)(7) in CLIA 42 CFR 493.1291 - Test Report (http://www.ecfr.gov/cgi-bin/text-idx?SID=1248e3189da5e5f936e55315402bc38b&node=pt42.5.493&rgn=div5#se42.5.493_11291)

Submitted by Riki Merrick on

Improve the defintion of the different types of result values

As highlighted in comment https://www.healthit.gov/isa/comment/7016 and also requested by https://www.healthit.gov/isa/comment/3231 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: https://www.healthit.gov/isa/comment/3321)

APHL also supports the reconciliation (as requested in this comment: https://www.healthit.gov/isa/comment/11901) with this level 2 data element Laboratory Result Value but prefers that name for this element.

Submitted by hantran on

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. 

Submitted by jenna.stern on

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.

Submitted by Riki Merrick APHL on

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 (https://www.healthit.gov/isa/taxonomy/term/1401/level-2), so if that is added clarification between when to use which would be needed.

This is a CLIA required element.

Submitted by Riki Merrick APHL on

Addition to my comment above

The level 2 element https://www.healthit.gov/isa/taxonomy/term/2446/level-2 supports the renaming - these two elements need to be reconciled.

Submitted by sabhyankar on

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.”

Submitted by sabner on

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: https://www.healthit.gov/public-course/interoperability-lab-exchange/HITRC_lsn1085/docs/LIS_Implementation_Challenges_Guide.pdf

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

FormGuide

Help

1. Optional: Background Text / Cover Letter

The "Optional Background Text / Cover Letter" field provides space for additional context or introductory information related to your comment.

If you wish to provide context, explanation, or an introduction to your comment, enter this information in the field labeled "Optional Background Text / Cover Letter." This is entirely optional and is most useful when submitting multiple related comments or when additional background would help reviewers understand your feedback.

If you are only commenting on a single data class or element, you may leave this field blank.

2. Select the Data Class

To specify which data class your comment addresses:

  1. In the "Data Class" drop-down menu, select the appropriate data class you want to comment on.
  2. If you are providing a general comment that is not specific to a data element, select "General" from the options. Comments with this designation will be displayed on the USCDI landing page.
  3. Note that the Data Class field will automatically populate based on your current location in the platform:
    1. If you are on a data class page, the field will be set to that specific data class
    2. If you are on a data element page, the corresponding data class will be pre-selected
       

3. Select the Data Element

To specify which data element your comment addresses:

  1. In the "Data Element" drop-down menu, select the specific data element you want to comment on.
  2. The drop-down menu will display only the elements available under the data class you selected in the previous step.
  3. You can use the search function within the drop-down to quickly locate a specific data element.
  4. If you are commenting on the data class itself rather than a specific element, you may leave this field blank.

Note: Comments on a specific data element will appear on the respective data element page, while comments on a data class (without a specific element selected) will appear on the landing page for that data class.
 

Data Class and Data Element

Fig 1 The "Data Class" and "Data Element" dropdown menus allow users to specify the exact content they wish to comment on.

4. Optional: Propose New Data Class or Element

If you cannot find the appropriate data class or element for your comment:

  1. Instead of clicking the "Comment On An Existing Data Class Or Element" button, click the adjacent button labeled "Propose a New Data Class or Data Element."
  2. This will redirect you to the ONDEC (ONC New Data Element and Class) Submission System.
  3. In the ONDEC system, follow the provided instructions to submit your proposal for a new data class or element.
  4. Once your proposal is submitted through ONDEC, it will be reviewed separately from the commenting process.
Propose New Data Class or Element

Fig 2 The "Propose a New Data Class or Data Element" button redirects users to the ONDEC Submission System for proposing new data elements not currently available in the system.

5. Complete the Comment Form

Fill out the required fields in the comment form:

Subject: Enter a brief, descriptive title that summarizes your comment. This helps reviewers quickly understand the nature of your feedback.

Comment: In this field, provide the full details of your comment or feedback. Be as clear and specific as possible about your suggestions, concerns, or observations. Include any relevant details that support your position.

6. Optional: Add Additional Comments

If you need to comment on multiple data classes or elements:

  1. After completing your first comment, click the link labeled "Comment on another data element" at the bottom of the form.
  2. A new comment section will appear, allowing you to enter details for your additional comment.
  3. For each additional comment, you must select the appropriate data class and data element from the drop-down menus.
  4. Complete the Subject and Comment fields for your additional comment.
  5. Repeat this process for each additional comment you wish to submit.

Fig 3 The "Comment on another data element" link enables users to create multiple comments addressing different elements within a single submission.

7. Optional: Upload Supporting Files

The platform allows you to upload supporting documentation to enhance your comment:

  • Locate the "File Upload" section at the bottom of the comment form.
  • Click to upload any files (such as PDFs or documents) that provide additional context, evidence, or clarification for your comment.

Important: If you have already entered your comments using the form fields, there is no need to upload duplicate content in PDF format. The file upload feature is intended for supplementary materials only. Please avoid uploading files that contain the same information already provided in your comment text.

Upload Supporting Files

Fig 4 The "File Upload" section permits users to attach supporting documentation that supplements their written comments.

8. Optional: Save and Exit

If you need to pause your work and return to complete your comment later:

  1. Click the "Save and Exit" button at the bottom of the form.
  2. Your comment will be saved as a draft that you can access and complete later.
  3. When you return to the platform, you will see a red triangle with an exclamation mark next to the “Return to saved Comment” button, indicating that you have saved comments in draft status.
  4. Click this button to continue working on your draft.
  5. You will be taken to a review page where you can:
    1. Select "Submit Comment" to officially submit your feedback.
    2. Click "Edit" to return to the comment form and make changes
    3. Select "Discard Draft" to delete the saved draft and start fresh

Fig 5 A red triangle with exclamation mark indicator appears next to the “Return to saved Comment” button when draft comments are saved in the system.

9. Review and Submit

Once you have completed your comment:

  1. Click the "Review and Submit" button at the bottom of the form.
  2. This will take you to a review screen displaying your comment(s) in full.
  3. Review all information for accuracy and completeness.
  4. On this review screen, you have three options: 
    1. Click "Submit Comment" to officially submit your feedback
    2. Click "Edit" to return to the comment form and make changes
    3. Click "Discard Draft" to delete the comment and start fresh
  5. The review screen also includes a "Print" button that allows you to create a printed copy of your comments for your records. 
  6. If you choose to submit, your comment will be recorded in the system and made available for review by the appropriate stakeholders.
Review and Submit

Fig 6 The review screen allows users to verify comment content and make any necessary modifications before final submission.

USCDI Comments

Close

Add a New Comment

Review comment and Submit

Edit
Comment #1
PDF, Doc, Docx
Max Size : 10 MB