Description (*Please confirm or update this field for the new USCDI version*)
Time and/or date a procedure is performed.
Examples include but are not limited to vaccine or medication administration times, surgery start time, and time ultrasound performed.
Submitted By: Sheila Abner
/ CDC/NHSN
Data Element Information
Use Case Description(s)
Use Case Description
Surgical site infections are reported to NHSN as part of nationwide healthcare-associated infections surveillance. Data reported to NHSN on surgical site infections associated with colon and abdominal hysterectomy operative procedures are submitted to CMS.
Data elements associated with orders for isolation / transmission precautions (status of patient on the following types of isolation precautions: contact, airborne, droplet) are needed for public health reporting on patients with suspected cases of contagious diseases. Feedback is requested regarding the most appropriate class for these data elements. Another option might be Encounter or possibly part of a new class such as Service Request.
Estimate the breadth of applicability of the use case(s) for this data element
Beginning 15 years ago with 300 hospitals, NHSN now serves approximately 25,000 medical facilities tracking HAIs. Current participants include acute care hospitals, long-term acute care hospitals, psychiatric hospitals, rehabilitation hospitals, outpatient dialysis centers, ambulatory surgery centers, and nursing homes, with hospitals and dialysis facilities representing the majority of facilities reporting data. Participation among the other facility types is expected to continue to grow in coming years.
5 or more. This data element has been tested at scale between multiple different production environments to support the majority of anticipated stakeholders.
Potential Challenges
Restrictions on Standardization (e.g. proprietary code)
none known
Restrictions on Use (e.g. licensing, user fees)
none known
Privacy and Security Concerns
none known
Estimate of Overall Burden
Moderate burden. Orders for isolation are currently irregularly implemented, so there is a need for more consistent documentation. Implementing appropriate transmission-based precautions is important for individual patient care as well as facility infection control. Easy access to isolation status of a patient for situational awareness is critical.
Recommendation: CMS CCSQ requests clarification be provided for the Performance Time data element regarding the types of times that could be captured. While CMS CCSQ supports the inclusion of a data element for the collection and exchange of medication administration date and time, CMS notes medication administration date and time would be more appropriate for inclusion in the Medication data class, rather than the Procedures data class.
CAP Comment: The ONC has issued a request for information as to whether a single USCDI data element Time of Procedure satisfies the community submissions to add timing elements to a variety of USCDI data classes. The CAP does not support the use of a single Time of Procedure data element for pathology and laboratory purposes, as it cannot clearly represent the laboratory times and dates that are required by regulation to be reportable. For example, it is unclear whether a single data element named Time of Procedure is indicating the time of the sampling procedure or the time of the analytic procedure. Separate laboratory data elements are necessary to represent regulatorily mandated laboratory dates and times in the USCDI. With respect to current USCDI submissions, this single Time of Procedure data element would not be sufficient to represent the Level 2 laboratory time data elements which are necessary for interoperability and should be added into the USCDI.
A procedure use case may include multiple timing type data elements within a procedure (e.g. in-room time, time of induction, surgery start). Similar to labs, we recommend new data element called Type of Timing to capture these types of observations within a Procedure.
Recommend 'Time of Procedure' be specified like labs. For example, procedures with anesthesia for example will include in-room time, time of induction, surgery start, etc.
Comments from NACCHO: NACCHO expects that this data element will not provide much value to Local Health Departments as not every procedure has these kinds of values.
IMO supports the inclusion of proposed Level 2 Data Elements for Procedure Timing and Location of Procedure in USCDI V3. These data elements are incorporated in mature technical specifications including CDA R2 Implementation Guide: Healthcare Associated Infection (HAI) Reports, Release 3. ONC certified HIT should be capable of exchanging these data elements.
The Multiple Chronic Conditions eCare Plan project successfully tested this element at the Sep 2020 and Jan 2021 FHIR connectathons and has implemented it at the OHSU testing site.
The CDC Division for Heart Disease and Stroke Prevention and the Million Hearts® 2022 Hearts national initiative (co-led by and the Centers for Medicare & Medicaid Services) uses this data as it is available for monitoring and evaluation to prevent 1 million heart attacks and strokes in 5 years. Furthermore, the CDC plans to leverage this data further in the future for surveillance and epidemiology studies if advanced through policy and available from EHRs. The Multi-state EHR-based Network for Disease Surveillance (MENDS) pilot will use electronic health record (EHR) data collected in clinical settings leading to a real-time, chronic disease surveillance model to plan and evaluate short-term outcomes of policies and program interventions.This field is for general comments on this specific data element. To submit new USCDI data classes and/or data elements, please use the USCDI ONDEC system: https://healthit.gov/ONDEC
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:
In the "Data Class" drop-down menu, select the appropriate data class you want to comment on.
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.
Note that the Data Class field will automatically populate based on your current location in the platform:
If you are on a data class page, the field will be set to that specific data class
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:
In the "Data Element" drop-down menu, select the specific data element you want to comment on.
The drop-down menu will display only the elements available under the data class you selected in the previous step.
You can use the search function within the drop-down to quickly locate a specific data element.
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.
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:
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."
This will redirect you to the ONDEC (ONC New Data Element and Class) Submission System.
In the ONDEC system, follow the provided instructions to submit your proposal for a new data class or element.
Once your proposal is submitted through ONDEC, it will be reviewed separately from the commenting process.
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:
After completing your first comment, click the link labeled "Comment on another data element" at the bottom of the form.
A new comment section will appear, allowing you to enter details for your additional comment.
For each additional comment, you must select the appropriate data class and data element from the drop-down menus.
Complete the Subject and Comment fields for your additional comment.
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.
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:
Click the "Save and Exit" button at the bottom of the form.
Your comment will be saved as a draft that you can access and complete later.
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.
Click this button to continue working on your draft.
You will be taken to a review page where you can:
Select "Submit Comment" to officially submit your feedback.
Click "Edit" to return to the comment form and make changes
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:
Click the "Review and Submit" button at the bottom of the form.
This will take you to a review screen displaying your comment(s) in full.
Review all information for accuracy and completeness.
On this review screen, you have three options:
Click "Submit Comment" to officially submit your feedback
Click "Edit" to return to the comment form and make changes
Click "Discard Draft" to delete the comment and start fresh
The review screen also includes a "Print" button that allows you to create a printed copy of your comments for your records.
If you choose to submit, your comment will be recorded in the system and made available for review by the appropriate stakeholders.
Fig 6 The review screen allows users to verify comment content and make any necessary modifications before final submission.
Submitted by rdillaire on
CMS-CCSQ Requests clarification on Performance Time
Recommendation: CMS CCSQ requests clarification be provided for the Performance Time data element regarding the types of times that could be captured. While CMS CCSQ supports the inclusion of a data element for the collection and exchange of medication administration date and time, CMS notes medication administration date and time would be more appropriate for inclusion in the Medication data class, rather than the Procedures data class.