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

Data Element
Specimen collection date/time
Submitted By: Nedra Garrett / Centers for Disease Control and Prevention
Data Element Information
Data Element Description Date/time when clinical specimen was collected from subject patient.
Use Case Description(s)
Use Case Description 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. Specimen type and specimen site provides information useful in interpreting laboratory findings to determine severity and transmissibility.
Estimate the breadth of applicability of the use case(s) for this data element Over 3000 public health agencies in the US would use these data elements for disease surveillance and control activities.
Link to use case project page https://www.cdc.gov/elr/index.html
Healthcare Aims
  • Improving the health of populations
Maturity of Use and Technical Specifications for Data Element
Applicable Standard(s) LOINC
https://phinvads.cdc.gov/vads/SearchVocab.action
Additional Specifications N/A
Current Use Extensively used in production environments
Supporting Artifacts These are standard elements in HL7 laboratory messaging
https://www.cdc.gov/elr/index.html
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 These data elements are standard components of HL7 electronic test order and reporting (ETOR) messages between clinical setting and clinical laboratorories and of HL7 electronic laboratory reporting (ELR) messages sent from clinical laboratories to public health.
https://www.cdc.gov/elr/index.html
Potential Challenges
Restrictions on Standardization (e.g. proprietary code) None
Restrictions on Use (e.g. licensing, user fees) None
Privacy and Security Concerns None
Estimate of Overall Burden N/A
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 Performance Time in the Procedures data class.

Comment

Submitted by CDC_DSMH_WG on

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.

Submitted by CDC_DSMH_WG on

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.

Submitted by hantran on

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.

Submitted by CDC_DSMH_WG on

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.

Submitted by hantran on

CAP Comment on Specimen collection date/time

Data Element: Specimen collection date/time

  • Description: The College of American Pathologists (CAP) supports the inclusion of this Level 2 data element into USCDI v4. While this is not a CLIA requirement, the specimen collection time defines the clinically applicable time of the result, which is crucial for correct interpretation of the result by care providers and correct response by public health agencies in emergency (eg, pandemic) preparedness and response settings. For future iterations of USCDI, we may recommend replacing this data element with two data elements corresponding to the OBX-14 and SPM-17 fields in HL7 2.5.1. The data elements should be named “Date/time of the observation” which is the name of OBX-14, and “Date/time of specimen collection,” which is a minor variation on the name of SPM-17. Date/time of the observation refers to the clinically-relevant date/time associated with the measurement. When there is testing of a specimen, HL7 2.5.1 specifies that the content of OBX-14 and SPM-17 should be identical. Having these two data elements allows for documentation of specimen collection time in rare cases where the clinically relevant time and specimen collection time might differ. The CAP may submit these new data elements for USCDI v5 in 2023.
  • Vocabulary Standard: The 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.

Submitted by Riki Merrick on

APHL Comments on ISA 2022

APHL supports inclusion of this data element in the Laboratory class of USCDI V4 because it is a CLIA required element and represents the clinically relevant time of laboratory results, which means it provides the temporal context to the clinician.

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 laboratories to central cancer registries for CDC and NCI’s national cancer surveillance systems, as required by law.  

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