Activity performed for or on a patient as part of the provision of care.

Data Element
Procedure Sequence
Description
A number to uniquely identify procedure entries.
Submitted By: Jenna Stern / Vizient
Data Element Information
Data Element Description A number to uniquely identify procedure entries.
Rationale for Separate Consideration Procedure Sequence data element would be related to the Procedure element and possibly even Procedure Time if that is also added. Together, we would be able to differentiate when different procedures occurred to give clarity on various times associated with procedures.
Use Case Description(s)
Use Case Description Addition of Procedure Sequence and Procedure Time would allow for quality and performance improvement measures to be collected and analyzed based on the availability of sequencing and times. Procedure Time would allow for scheduled case start and end time, patient in room and patient out of room, anesthesia start and end time, incision start and end time, and recovery start and end time data elements to be collected. Time studies and procedure practice variation could be done with the availability of Procedure Time. Procedure Sequence could then further tie in studying time spent on procedure and outcomes related to procedure time or sequence of events (including time spent at each stage).
Estimate the breadth of applicability of the use case(s) for this data element Many requestors in the healthcare quality and peformance improvement space would access and utilize the Procedure Sequence and Procedure Time to further augment the data collected through the Procedure Element. Additionally, providers and payers could utilize this information for their own tracking purposes and to address variation in procedural care. Lastly, this element could tie into a future ExplanationOfBenefit or Claim USCDI Data Class to further give patients insight to their procedural data. Vizient receives data from over 1000 facility participants, both Vizient and our members are currently collecting these data points through manual submissions. Improved standardization would reduce hospital burden when it is reported and make the information more accessible.
Healthcare Aims
  • Improving patient experience of care (quality and/or satisfaction)
  • Improving the health of populations
  • Reducing the cost of care
  • Improving provider experience of care
Maturity of Use and Technical Specifications for Data Element
Applicable Standard(s) N/A
Additional Specifications Procedure Sequence is currently available via the Industry Standard ExplanationOfBenefit R4 FHIR Resource. Procedure.sequence is available within this resource. Procedures sequence is also available within the similar Claim FHIR Resource. https://build.fhir.org/explanationofbenefit-definitions.html#ExplanationOfBenefit.procedure.sequence. Also utilized in CARIN Blue Button IG (https://build.fhir.org/ig/HL7/carin-bb/StructureDefinition-C4BB-ExplanationOfBenefit.html and https://build.fhir.org/ig/HL7/carin-bb/StructureDefinition-C4BB-ExplanationOfBenefit-definitions.html#ExplanationOfBenefit.item).
Current Use In limited use in production environments
Supporting Artifacts Procedure sequence is currently collected and used in several EHR systems including Epic’s production environment. This data element is utilized by various healthcare performance improvement organizations for the associated use cases discussed. Epic on FHIR currently has Procedure sequence available via the ExplanationOfBenefit resource.
https://fhir.epic.com/Specifications?api=1072 See also: Industry Standard ExplanationOfBenefit R4 FHIR Resource: https://build.fhir.org/explanationofbenefit-definitions.html#ExplanationOfBenefit.procedure.sequence. CARIN Blue Button IG: https://build.fh
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 Members are currently manually submitting this data element to Vizient. Vizient understands hospitals submit this data element to other outside entities, including payers and patients. Vizient receives this data and sends it back to hospitals.
https://fhir.epic.com/Specifications?api=1072
Potential Challenges
Restrictions on Standardization (e.g. proprietary code) Due to the Procedure Sequence data element being a sequence number, it is a integer that will be passed from the EHR system already being collected. There is not a vocabulary, terminology or content to reference as it will follow the basic integer structural standard.
Restrictions on Use (e.g. licensing, user fees) To our knowledge, does not require any licensing or user fees.
Privacy and Security Concerns Same privacy and security concerns associated with collection of Procedure data element in general. No additional privacy and security concerns added with sequencing.
Estimate of Overall Burden Data already available via various EHR systems including Epic. Data has also been retrived from Cerner hospitals too. Data element does not need to be calculated by patient or provider.
Data Sequence may be an optionally collected data type which may be provided by EHR vendors, but it is not mandatory that such vendors offers this data element to our knowledge. Structure does exist already within the EHR frameworks.
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 1 - Data element is captured, stored, or accessed in at least one production EHR or HIT module.
Criterion #3
Maturity - Current Exchange		 Level 1 - Data element is electronically exchanged between two production EHRs or other HIT modules 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 Data represented by this element is needed in a very narrow set of use cases.

Comment

Submitted by erjones on

Please Include Procedure Sequence in USCDI v5

Consistent with Vizient’s comments regarding USCDI v4, the addition of Procedure Sequence would provide further clarification as to which steps took place from start to finish for each procedure. This information could help support performance improvement, among other benefits.

Submitted by erjones on

Please Include Procedure Sequence in USCDI v4

Consistent with Vizient’s comments regarding USCDI v3, the addition of Procedure Sequence would provide further clarification as to which steps took place from start to finish for each procedure. This information could help support performance improvement, among other benefits.

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
Submit CommentDiscard Draft