OneView Hospital Quality Release Notes

What's New in OneView Hospital Quality 5.0.4


Release Date: Monday, December 10, 2018


Version 5.0.4 is the last scheduled release of OneView for the 2018 reporting period.


Below is a link to the Submission Wizard Help Guide with Step-by-step instructions for using the HQ Submission Wizard in OneView for both scheduling and preparing your submission.

https://support.acmeware.com/KB/View/918-oneview-hq-submission-wizard-help-guide


Here's a summary of what's new in this update:


New Features and Enhancements: (for all platforms unless specified)


Submission Wizard:

  • Updated the PI Reporting Period in the Submission Wizard to check for a minimum 90 days. If the from and through dates are less than 90 days, you will get an error message and not be able to advance to the next screen.
  • Updated submission wizard to prevent compiles from running when Save and Exit is clicked while creating a new submission.  This will prevent another compile prior to locking the submission.


Clinical Quality Measures:

  • MAGIC: Improved performance for compile job
  • CS: Updated code to perform faster when gathering ED Encounters.  Impact: No measure numbers affected. Customer Support Ticket: #4950


Manage Dictionaries:

  • Added a link in the Manage Programs/Measures to the OneView HQ Help Guide: Manage Programs/Measures on the Customer Support Portal.
  • CPOE: Added (Medicaid Only) to CPOE Dictionary in Manage Dictionaries > PI Measures.



OneView Update Service:

  • Internal clean up with the compile log data so we can monitor the daily compile logs in the OneView Update service on Azure.


Reports:

  • Added universal list of providers to all reporting references for CQM and OM reports after each compile. Impact: Reports that list providers use this universal list.


Fixes: (for all platforms unless specified)


Please Note: Customer Support Tickets referenced below may be Acmeware client specific and are not visible to all clients on the Customer Support Portal.


Reports:

  • Corrected issue with Reports using [By Provider] in the drop down. Impact: Reports using [By Provider] cause issues due to failure to finish gathering all provider data (duplicate attending providers listed on some accounts). Customer Support Ticket: #5319


Manage Dictionaries:

  • Corrected issue for Non-Acute Care Services saving distinct values if service code existed in both ABS/MIS service dictionaries. Impact: Users are now able to save dictionary. Customer Support Ticket: #4475


Promoting Interoperability Objective Measures:

  • CS: Stage 3: Fixed an issue that was preventing the compile from finishing. Impact: If the issue occurred the compile would stop and numbers would not change.
  • eRx:
    • Corrected an issue that was preventing controlled substances in the dictionary from being included in the eRx numbers. Impact: eRx will include controlled substances added to the dictionary.
    • Per CMS, we have included cancelled prescriptions for inclusion in the measure. Impact: Possible increase in the denominator and numerator.
  • 6.15: Stage 3: Corrected issue with Patient Generated Data causing a zero denominator. Impact: Denominator will increase for Patient Generated Health Data. Customer Support Ticket: #5458
  • 6.0: Corrected issues with pre-compiled data. Impact: The issues impact the build which would get resolved on upgrade. Customer Support Ticket: #5247
  • 6.0, 6.1, and 6.15: MR: Med Reconciliation has a new ActivityEvent description: Order Continued on Discharge. Impact: The change could increase the numerator by including at this new activity event.Customer Support Ticket: #4386


Clinical Quality Measures:

  • ALL Platforms:
    • ED: Corrected an issue with the way we handle datetimes impacting the measure calculation by ignoring seconds to align with CMS QRDA implementation guide. Impact: ED patient population and therefore ED calculation times could change depending on visit documentation.
    • Procedure performed items did not get an end date set; therefore, flags requiring an ending date were not set.  Impact: May affect measures looking for Procedures using the temporal ends after, ends before, etc. Customer Support Ticket #2662
    • STK-8, CAC-1: Added check for education materials when a query's group response was saving the element name, not the code, in the query response.  Impact: May pick up education materials if site had documentation set up in this way. Customer Support Ticket: #4770
    • VTE:
      • Corrected issue with temporal logic returning wrong value for 2 flags and setting them for each patient's visit regardless of the timing of the event. (if the patient had a Procedure of General or Neuraxial Anesthesia on any visit). Customer Support Ticket:  #5151
      • If a service timestamp ends and immediately starts for same service, code now combines the times for that service into one entry.  Impact: VTE-1/VTE-2 numbers may change because ICU LOS timing could change. Customer Support Ticket: #4509
      • VTE-2: For Oral Factor Med Admin, the timing was switched between the "ICU Encounter" and the "Anesthesia after ICU Encounter". Impact: Measure numerator could increase or decrease depending on each visit's documentation.
  • CS:
    • Rename invalid table name to the correct table name - previously thought to be corrected in 5.0.3.
    • Replaced deprecated table AdmSpecialCareServices with new table AdmSpecCareServices because of MEDITECH changes. Customer Support Ticket: #4279
  • MAGIC: Corrected issue with Initial Population data collection code that had references to wrong MEDITECH platform. Impact: The number of patients in the initial population will change. Customer Support Ticket: #5295
  • CS, MAGIC: Fixed issue where some discharge meds that had a status of cancelled were not showing up on patients.  Impact: May increase numerator and decrease exclusion and not met patients for measures relying on discharged meds. Customer Support Ticket: 5284
  • MAT 6.1x: VTE: Corrected issue with Procedure Performed items that had an end date earlier than the start date causing QRDA rejections upon submission. Impact: The patient population may increase or decrease depending on the timing of the Procedure Performed.