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

Data Element
Laboratory results: date and timestamps
Description

Date and timestamps associated with the completion of laboratory results, that are meta data associated with laboratory results
Submitted By: Joel Andress / Centers for Medicare and Medicaid Services (CMS) Center for Clinical Standards and Quality (CCSQ)
Data Element Information
Data Element Description Date and timestamps associated with the completion of laboratory results, that are meta data associated with laboratory results
Rationale for Separate Consideration The current concept of laboratory tests, including results are included in USCDI v1. To add clinical context to those results, recommending requiring the associated date and timestamps (meta data).
Use Case Description(s)
Use Case Description Laboratory tests with associated results and metadata are used extensively in CMS quality measures across programs including IQR, QPP, and Promoting Interoperability to define measurement populations and numerator events. The date and timestamps associated with lab tests are critical for defining which tests occur within the measurement period, and help associate tests to specific encounters or visits and are standard metadata for labs.
Estimate the breadth of applicability of the use case(s) for this data element 4,000+ hospitals and 1 million providers currently capture, access and exchange laboratory results with associated metadata (date and timestamps)
eCQI resource center, includes measure specifications for CMS program eCQMs (i.e. CMS 349, CMS 529): https://ecqi.healthit.gov/ecqms
Link to use case project page https://ecqi.healthit.gov/ecqms
Use Case Description Date and timestamps for laboratory tests are also critical pieces of information exchanged with test results for clinical care and care decision support. A result itself is not useful unless the context of the timing of that result is also available.
Estimate the breadth of applicability of the use case(s) for this data element All healthcare providers and laboratories who are collecting labs are also collecting associated date and timestamps for when tests are taken, when results are returned, and often when results are entered in EHR systems.
Healthcare Aims
  • Improving patient experience of care (quality and/or satisfaction)
  • Improving the health of populations
Maturity of Use and Technical Specifications for Data Element
Applicable Standard(s) LOINC codes for labs—date and timestamps collected in standard format
Additional Specifications Many technical specifications include laboratory test specifications—all require an associated date and timestamp as part of the information:
HL7 FHIR US Core Implementation Guide STU3 based on FHIR R4, Observation Laboratory Test Profile, collection date and timestamp (effective date time) must be supported by the profile (https://www.hl7.org/fhir/us/core/StructureDefinition-us-core-observation-lab.html )
CMS Quality Data Model (QDM) version 5.5 Guidance, relevant authored and resulted date/times (https://ecqi.healthit.gov/sites/default/files/QDM-v5.5-Guidance-Update-May-2020-508.pdf)
HL7 C-CDA Release 2.0 (http://www.hl7.org/implement/standards/product_brief.cfm?product_id=492)
Current Use This data element has been used at scale between multiple different production environments to support the majority of anticipated stakeholders
Supporting Artifacts Date/time stamps associated with laboratory test results are used at scale by hospitals, providers, and laboratories. Widely available within EHR systems:
https://fhir.cerner.com/millennium/r4/diagnostic/observation/ https://fhir.epic.com/Specifications?api=998
https://mydata.athenahealth.com/fhirapidoc

https://ecqi.healthit.gov/ecqms
Extent of exchange 5 or more. This data element has been tested at scale between multiple different production environments to support the majority of anticipated stakeholders.
Supporting Artifacts Laboratory date/time metadata is electronically exchanged for quality measurement used across CMS programs via QRDA files and other architectures.
This metadata is also exchanged for virtually all instances a laboratory result is being exchanged, as it is important for clinical context and interpretation of results.
https://ecqi.healthit.gov/qrda
http://www.hl7.org/implement/standards/product_brief.cfm?product_id=7

https://ecqi.healthit.gov/qrda
Potential Challenges
Restrictions on Standardization (e.g. proprietary code) No challenges anticipated
Restrictions on Use (e.g. licensing, user fees) None
Privacy and Security Concerns This data, like any patient data, should be exchanged securely. Current processes exist, governed by CMS and ONC, to securely transfer this data.
Estimate of Overall Burden No burden estimated—metadata already in use across the entire stakeholder community.
Other Implementation Challenges N/A
ASTP Evaluation Details
Each submitted Data Element has been evaluated based on the following criteria. The overall Level classification is a composite of the maturity based on these individual criteria. This information can be used to identify areas that require additional work to raise the overall classification level and consideration for inclusion in future versions of USCDI
Criterion #1
Maturity - Current Standards		 Level 2 - Data element is represented by a terminology standard or SDO-balloted technical specification or implementation guide.
Criterion #2
Maturity - Current Use 		Level 2 - Data element is captured, stored, or accessed in multiple production EHRs or other HIT modules from more than one developer.
Criterion #3
Maturity - Current Exchange		 Level 2 - Data element is electronically exchanged between more than two production EHRs or other HIT modules of different developers using available interoperability standards.
Criterion #4
Use Case(s) - Breadth of Applicability		 Level 0 - Use cases apply to a limited number of care settings or specialties, or data element represents a specialization of other, more general data elements.
Evaluation Comment This data element represents a specific type of existing USCDI data element Author Time Stamp in the Provenance data class.

Comment

Submitted by hantran on

CAP Comment on Laboratory results: date and timestamps

Data Element: Laboratory results: date and timestamps

  • Corresponding CLIA Reporting Requirement: The test report date
  • Description: The College of American Pathologists (CAP) supports the inclusion of this Level 2 data element into USCDI v4, corresponding to the time of result transmission. This inclusion will align the USCDI with CLIA’s Test Report Date reporting requirement. The CLIA requirements are required for laboratory reporting and should be used as the basis for laboratory and public health reporting standards. For future iterations of USCDI, we would suggest collapsing this data element with the Laboratory Test Performed Date data element called “Date/time of the analysis,” which is the name of the OBX-19 field of the HL7 2.5.1 standard. The CAP may submit this new data element for USCDI v5 in 2023.
  • Vocabulary Standard: The CAP recommends replacing the listed standards for this data element with the value format from the OBX-19 field in HL7 2.5.1, which is a version of the Health Level Seven (HL7) standard that defines methods for transferring and sharing data between various healthcare systems and providers. HL7 2.5.1 OBX-19 is aligned with the ISO 8601 international standard for communicating date and time information.

Submitted by Riki Merrick on

APHL Comments on ISA 2022

This definition is not sufficient, there are many dates of interest to a laboratory test result, so a single “Date” is not appropriate; the date and time of analysis, which may be the same as the Laboratory Test Performed Date attribute, the date the result was released and the date of the overall report. From a clinical perspective the most important date for a laboratory test is the date/time of specimen collection, as that gives the clinician the temporal context of the observation which is the same as the Specimen collection date/time attribute

#1 APHL suggests clarifying the name and the definition to a single one of the above mentioned dates so that this element does not overlap with others defined in USCDI.

Submitted by CDC_DSMH_WG on

CDC's comment on behalf of CSTE for USCDI v4

 

  •  CSTE strongly recommends that the following data elements should be included in USCDI v4 as proposed.
  1. Type of specimen - this is critical for triggering electronic case reports and for making decisions on which cases are invasive (e.g., for S. pneumoniae, MRSA, Group A strep).
  2. Result status - knowing that a result is preliminary, or final is critical for determining the certainty of the existence of a critical public health condition.

 

  • CSTE supports collection of more granular laboratory data to support case adjudication and reporting as well as patient deduplication and linking of data from cases to ELR, which can be critical. The variables we recommend be added to USCDI v4 include:
  1. Name of testing/performing laboratory and associated identifiers (CLIA)(HIGH PRIORITY)
  2. Name of ordering provider and submitter
  3. Address of testing/performing laboratory
  4. Accession number at testing laboratory (HIGH PRIORITY for matching purposes)
  5. Date the test was ordered
  6. Date the test was performed (needs to be reconciled with results date/timestamp)
  7. Laboratory test value
  8. Specimen source site (HIGH PRIORITY)
  9. Specimen collection date and time (HIGH PRIORITY) (Needs to be reconciled with Test Date=Clinically relevant time)
  10. Test result value (needs to be reconciled with values/results in USCDI V1 and V2), units, reference range and interpretation (HIGH PRIORITY)
  11. Abnormal flag (HIGH PRIORITY)
  12. Test kit identifier
  • Dates and times are critical to evaluating the timeliness of reporting - it is a major indicator for the performance of public health surveillance systems and without this information it is unknown how data exchange is impacting the ability for public health to respond in a timely fashion. Although the date and time data are generated by the system, in practice it has been observed that availability of this data to Public Health Departments is sparse for use in timeliness analysis. Therefore, it is recommended that the following elements are added as part of the core data set.

Submitted by CDC_DSMH_WG on

CDC's Consolidated Comment

Additional use case:

  • Use case background: For cardiovascular disease prevention and treatment, particularly cholesterol management, laboratory-related data elements are vitally important for quality improvement related to clinical treatment as well as public health surveillance. Patients who have LDL-C values of ≥190 mg/dL are considered to have severe hypercholesterolemia and are recommended to be on a high-intensity statin. They are at high risk for having an atherosclerotic cardiovascular disease (ASCVD) event. Having information about their LDL-C values is critically important for understanding level of risk and for monitoring the impact that statin treatment (or other lipid-lowering agents) has on their LDL levels. Moreover, both laboratory result value and the date/timestamps are important for ensuring patients have LDL-C screening done in accordance with clinical guidelines. These data elements are currently in or will be part of future proposed iterations of CMS347, Statin Therapy for the Prevention and Treatment of Cardiovascular Disease, currently used in multiple CMS quality reporting programs, HRSA’s Uniform Data System, and the CDC/NACDD Multistate EHR-based Network for Disease Surveillance (MENDS). Chronic disease surveillance for diabetes (A1c), and chronic kidney disease (estimated glomerular filtration rate [eGFR] and/or urine albumin-to creatinine ratio [uACR]) also rely on the use of laboratory result values

Link to use case:

  • https://chronicdisease.org/page/MENDSINFO/

Implementation Guide:

  1. HL7 FHIR Quality Measure STU2 for FHIR R4 Implementation Guide - Quality Measure STU2 for FHIR R4 Implementation Guide (hl7.org)
  2. HL7 FHIR® Implementation Guide: Electronic Case Reporting (eCR) - US Realm 2.0.0 - STU 2 - HL7.FHIR.US.ECR\Home Page - FHIR v4.0.1 (http://build.fhir.org/ig/HL7/case-reporting/)
  3. HL7 CDA® R2 Implementation Guide: Public Health Case Report - the Electronic Initial Case Report (eICR) Release 2, STU Release 3.0 - HL7 Standards Product Brief - HL7 CDA® R2 (http://www.hl7.org/implement/standards/product_brief.cfm?product_id=436)
  4. HL7 FHIR Health Care Surveys Content Implementation Guide (http://hl7.org/fhir/us/health-care-surveys-reporting/2022Jan/);
  5. HL7 FHIR Central Cancer Registry Reporting Content Implementation Guide (http://hl7.org/fhir/us/central-cancer-registry-reporting/2022Jan/).
  6. 17 message mapping guides (MMGs) used for under the National Notifiable Diseases Surveillance System (NNDSS) (https://ndc.services.cdc.gov/message-mapping-guides/)

CSTE Comment:

  • CSTE strongly recommends that the following data elements should be included in USCDI v3 as proposed.
  1. Type of specimen - this is critical for triggering electronic case reports and for making decisions on which cases are invasive (e.g., for S. pneumoniae, MRSA, Group A strep).
  2. Result status - knowing that a result is preliminary, or final is critical for determining the certainty of the existence of a critical public health condition.

 

  • CSTE supports collection of more granular laboratory data to support case adjudication and reporting as well as patient deduplication and linking of data from cases to ELR, which can be critical. The variables we recommend be added to USCDI v3 include:
  1. Name of testing/performing laboratory and associated identifiers (CLIA)(HIGH PRIORITY)
  2. Name of ordering provider and submitter
  3. Address of testing/performing laboratory
  4. Accession number at testing laboratory (HIGH PRIORITY for matching purposes)
  5. Date the test was ordered
  6. Date the test was performed (needs to be reconciled with results date/timestamp)
  7. Laboratory test value
  8. Specimen source site (HIGH PRIORITY)
  9. Specimen collection date and time (HIGH PRIORITY) (Needs to be reconciled with Test Date=Clinically relevant time)
  10. Test result value (needs to be reconciled with values/results in USCDI V1 and V2), units, reference range and interpretation (HIGH PRIORITY)
  11. Abnormal flag (HIGH PRIORITY)
  12. Test kit identifier

 

  • Dates and times are critical to evaluating the timeliness of reporting - it is a major indicator for the performance of public health surveillance systems and without this information it is unknown how data exchange is impacting the ability for public health to respond in a timely fashion. Although the date and time data are generated by the system, in practice it has been observed that availability of this data to Public Health Departments is sparse for use in timeliness analysis. Therefore, it is recommended that the following elements are added as part of the core data set.

 

WA DOH Comment:

  • The date and time of testing and when the results are observed and recorded in the system denotes the timeliness of reporting. The element reflects one of the major indicators for performance of Public Health Surveillance Systems and timeliness of reporting is critical for Public Health action.
  • Although the date and time data are generated by the system, in practice it has been observed that availability of this data to Public Health Departments is sparse for use in timeliness analysis. Therefore, it is recommended that the following elements are added as part of the core data set.

The elements recommended are:

  1. Date/Time of Testing
  2. Date/Time of Results

 

 

 

Submitted by CDC_DSMH_WG on

Unified Comment from CDC

  • Additional Use Case: This is a standard data item used by central cancer registries in all states. Data received through data exchange from pathology laboratories to central cancer registries for CDC and NCI’s national cancer surveillance systems, as required by law. 
     
  • This element is used by CMS Quality Reporting and is marked Required or MustSupport in the FHIR QI Core IG
     
  • CSTE supports inclusion of this measure into USCDI v3

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