Laboratory

CSTE Comment - v6

CSTE supports inclusion of this data element in USCDI V6. Please see previously submitted CSTE comments for additional recommendations.

CMS-CCSQ Support Specimen Collection Date/Time for USCDI v6

Data Element: Specimen Collection Date/Time (Level 0)

1. Recommendation: Advance the Specimen Collection Date/Time data element to Level 2 and add to Final USCDI v6. 
2. Rationale: The Specimen Collection Date/Time data element in the Laboratory data class can be critical for providing context in quality measurement. This data element provides key information needed to confirm diagnoses, understand disease severity, and classify cases that require public health intervention, including outbreak identification and response. Knowing the date and time of specimen collection helps determine when a patient has a laboratory-verified illness. This data element helps healthcare providers interpret test findings correctly, especially in urgent care settings like Intensive Care Units (ICUs) and emergency rooms as well as during public health response to infectious disease outbreaks. The collection date and time of a specimen is particularly important in understanding when a disease process was present in a patient, which helps interpret laboratory findings for severity and transmissibility. Current CMS quality measures require date/time elements for different aspects of laboratory tests such as collection, recording, and reporting. Elevating this data element to Final USCDI v6 will be significant in helping to ensure accurate and effective patient care in addition to comprehensive and timely public health response. CMS would also highly recommend date/time data elements be incorporated to other areas to enhance collection and reporting of key healthcare activities such as radiology, immunizations, and clinical notes.

APHL requests inclusion of this critical element in V6

APHL supports inclusion of this discrete data element until the design of USCDI accomodates a mechanism for each use case to define further constraints around generic data elements, as otherwise the clinical context and signifcance of when to collect this element cannot be sufficently described.
APHL points out that specimen collection is not normally modeled as a procedure in the EHR-s and LIS and hence it is not a type of procedure date/time.
For public health, this is used to to determine onset of a case (for some conditions and if onset date is not available), as a proxy for infectious/contagious period, to calculate turnaround time/timeliness metrics or as a proxy date for classifying a specimen result for temporal aggregation if other dates are not available. It is essential for understanding laboratory situational awareness. It is different from order date, as sometimes the order is placed well before the specimen was collected.
It is called out as a required element of the test request in a test report in 42 CFR 493.1241(c)(6) (https://www.ecfr.gov/current/title-42/part-493/subject-group-ECFR5f8f0b6639946fd#p-493.1241(c)(6)): "The date and, if appropriate, time of specimen collection."
This element maps to in V2 = SPM-17 (Specimen Collection Date/Time) https://www.hl7.eu/refactored/segSPM.html#1765 and also in OBR-7 (Observation Date/Time) = https://www.hl7.eu/refactored/segOBR.html#241 for speicmen based observations (and OBR-7 is Required for results in the base standard ORU^R01 message), in FHIR = observation.effectiveTime for specimen based observations and specimen.collected (either DateTime or Period)
Rationale for elevating to V6 level: 
Every lab evaluates each specimen it receives prior to performing the ordered test(s) based on the acceptiblity criteria, that are part of every lab's catalog: most test have one for time ranges, which is calculated using the specimen collection date/time to the specimen received date time for example: SPECIMEN STABILITY INFORMATION: https://www.mayocliniclabs.com/test-catalog/overview/75759#Specimen, time delay elements are also used to evaluate reserach studies (https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6816912/) and highlighted in 9.1 Required Activities and Documentation in Guidelines on Good Clinical Laboratory Practice (https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2213906/).
It is a "Must Support" (represented by usage code "RE") data element in SPM-17, but required in OBR-7 in the base LRI profile (https://www.hl7.org/implement/standards/product_brief.cfm?product_id=279) and Required in both SPM-17 and OBR-7 in NAACR (https://www.naaccr.org/pathology-laboratory-electronic-reporting/) and ELR R1 IGs (https://www.hl7.org/implement/standards/product_brief.cfm?product_id=98). ELR R1 has been part of certification requirements for lab result reporting to public health since MU1 as called out "Implementation specifications. HL7 Version 2.5.1 Implementation Guide: Electronic Laboratory Reporting to Public Health, Release 1 (US Realm) (incorporated by reference in § 170.299) with Errata and Clarifications, (incorporated by reference in § 170.299) and ELR 2.5.1 Clarification Document for EHR Technology Certification, (incorporated by reference in § 170.299)." in https://www.ecfr.gov/current/title-45/part-170/section-170.205#p-170.205(g) - covers these 3 criteria for at least being level 2: Represented by a terminology standard or SDO-balloted technical specification or implementation guide.
Data element is captured, stored, or accessed in multiple production EHRs or other HIT modules from more than one developer.
Data element is electronically exchanged between more than two production EHRs or other HIT modules of different developers using available interoperability standards.

CSTE Comment - v5

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 v5 include:

Name of testing/performing laboratory and associated identifiers (CLIA) (HIGH PRIORITY)
Name of ordering provider and submitter
Address of testing/performing laboratory 
Accession number at testing laboratory (HIGH PRIORITY for matching purposes)
Date the test was ordered
Date the test was performed (needs to be reconciled with results date/timestamp)
Specimen collection date and time (HIGH PRIORITY) (Needs to be reconciled with Test Date=Clinically relevant time)
Test result value (needs to be reconciled with values/results in USCDI V1 and V2), units, reference range and interpretation (HIGH PRIORITY)
Abnormal flag (HIGH PRIORITY)
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
 

CDC's comment for USCDI Draft v5

CDC supports the inclusion of this data element in USCDI v5 as it is an element that may be necessary for calculation of our digital quality metrics from FHIR data. 

Conceptualizing Laboratory Specimen collection date/time as a procedure time may not be clinically correct. In certain situations, such as during a surgery, the procedure time, i.e., Surgery start time, could be different from the time the specimen is obtained.

Laboratory specimen collection date/time is used for laboratory situational awareness and surveillance needs. This date/time is used as a proxy for infectious/contagious period. It is different from order date, as sometimes the order is placed well before the specimen was collected.

This is used in public health to determine onset of a case (for some conditions and if onset date is not available) and also, as with other dates, is used to assess timeliness of data and lab processes. 

Additional Resources for 4):

CLIA Requirement (https://www.ecfr.gov/current/title-42/part-493/subject-group-ECFR5f8f0b6639946fd#p-493.1241(c)(6)). 

In this study, look at Table 1 where they indicate time delay as a reason for specimen rejection. Specimen collection time is needed to calculate the time delay. 

“The request form must document unique study-participant identifiers, specimen collection date and time, study participant demographics, specimen type, and the collector’s (phlebotomist’s) identity” from this study. 

For this study, see the relationship between temperature and time. Collection time is crucial to know if the specimen is viable. 

In this Mayo Clinic’s document time delay is again a reason for rejection. 

Overarching Comment: 

There are extensive comments that have been submitted in support of the specific, granular date/timestamps for laboratory data, including a very granular one submitted by CMS. We agree with these, and CSTE explained it best in their existing comment: “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.” 

These are required data elements in the many laboratory data-public health exchange standards (including the dominant one used for laboratory data exchange currently, ELR 251 r1).

Clinical value of Specimen collection date/time

As a practicing physician I cannot fully understand or utilize exchanged laboratory data without knowing the date and time that the specimen was collected.  This information is critical to be able to interpret results that change over time, especially in an intensive care setting, such as the Emergency Department, Labor & Delivery, operating room, ICU, etc..  As noted in the numerous comments received from laboratory and public health organizations supporting the inclusion of this data element, this data is routinely collected and exchanged and should therefore be added to USCDI as a CORE data element for exchange.

CDC's comment on behalf of CSTE for USCDI v5

• 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 v5 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. Specimen collection date and time (HIGH PRIORITY) (Needs to be reconciled with Test Date=Clinically relevant time)
8. Test result value (needs to be reconciled with values/results in USCDI V1 and V2), units, reference range and interpretation (HIGH PRIORITY)
9. Abnormal flag (HIGH PRIORITY)
10. 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.

CDC's Consolidated Comment for USCDI v5

• Specimen collection date/time is created at the provider side when a specimen is collected for laboratory testing. EHRs capture it during test order creation and exchange it with the laboratory as part of the order message. A proper test interpretation can only be given for most test types with knowing the specimen collection date/time. Laboratories are required to receive this as per CLIA requirement §493.1291(c)(6). Additionally, Disease reporting to public health relies on data from the EHR for the identification of reportable events and to provide critical information used in confirming a diagnosis, understanding the severity, and classifying a case of disease that requires public health intervention for prevention, treatment, control, and outbreak identification and response. The specimen collection date is particularly important for public health in understanding when laboratory-confirmable evidence of a disease process was present in the patient. This data element can provide important time trends and surge capacity information during public health response.
• This may seem represented by the “Performance time” element applicable to a procedure. The specimen collection method is different from a procedure. It is currently not considered a procedure in EHR data collection methods, and considering so will be a major deviation from current practice. Specimen collection date/time is considered a test's “clinically relevant time” and not a procedure.
• NAACCR Comment: Agreed, important for cancer (and other public health) reporting.
• NACCHO Comment: Supports CDC's comment.

CAP Comment on Specimen collection date/time

• Data Class: Laboratory
• Data Element: Specimen Collection Date/Time
• CAP Comment:
  • One single Time of Procedure data element cannot clearly represent all the many times and dates associated with laboratory and pathology data, including this Specimen collection date/time data element, which is required in regulation and represents the date/time when clinical specimen was collected from subject patient.
  • This data element should be combined with the Laboratory Test Performed Date Level 2 data element, titled Specimen Collection Date/Time, and included as a data element in USCDI v4. This data element should accommodate time zone differences.
  • This data element aligns with the FHIR observation.effective data element (if greater alignment with FHIR is desired, this data element could also be renamed Laboratory Results Effective). CLIA specifies the use of this data element if appropriate.
• Vocabulary Standard: The College of American Pathologists (CAP) recommends the value format from the SPM-17 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. The CAP supports the use of the HL7 2.5.1 standard because the standard was designed to help laboratories comply with CLIA requirements. HL7 2.5.1 SPM-17 is aligned with the ISO 8601 international standard for communicating date and time information.

CDC's Consolidated Comment for USCDI v4

• CDC-CMS Joint Priority  

Disease reporting to public health relies on data from the EHR for identification of reportable events and to provide critical information used in confirming a diagnosis, understanding severity and classifying a case of disease that requires public health intervention for prevention, treatment, control, and outbreak identification and response. The specimen collection date is of particular importance for public health in understanding when laboratory confirmable evidence of a disease process was present in the patient. Required by CLIA (42 CFR 493.1241 (c) (6)). Procedure time is test performed date/time.  This element has been reported to cancer registries for over a decade with no issues.

• Comments from NACCHO: NACCHO supports including the data element specimen collection date/time
• Comments from CSTE: CSTE agrees with CDC's recommendation for this data element.