| Submitted By: Jenna Stern / Vizient | |
|---|---|
| Data Element Information | |
| 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). |
| Estimated number of stakeholders capturing, accessing using or exchanging | 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 |
|
| 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 |
| Number of organizations/individuals with which this data element has been electronically exchanged | 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. |
| ONC Evaluation Details Each submitted Data Element has been evaluated based on the following 4 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 |
|
|---|---|
| Maturity – Standards/Technical Specifications | Level 1/2 - Must be represented by a vocabulary standard or an element of a published technical specification |
| Maturity - Current Use | Level 2 - Used at scale in more than 2 different production environments |
| Maturity - Current Exchange | Level 2 - Demonstrates exchange between 4 or more organizations with different EHR/HIT systems |
| Breadth of Applicability - # Stakeholders Impacted | Level 2 - Used by a majority of patients, providers or events requiring its use |
Comment