2022 Real World Testing Results: CareVue 2.1/Open Vista 2

GENERAL INFORMATION

Developer Name: CareVue, a Division of Medsphere Systems Corporation

Plan Report ID Number: [RWTP-0000250]

Product Name(s):  

  • CareVue
  • OpenVista CareVue

Version Number(s):

  • CareVue v.2.1
  • OpenVista CareVue v.2

Product List (CHPL) ID(s):

  • CareVue – 15.04.04.2806.Open.02.01.1.210401
  • OpenVista CareVue – 15.04.04.2806.Open.02.00.1.171108       

ONC-ACB Certification ID:

  • CareVue – 15.04.04.2806.Open.02.02.1.221222 (current)
  • CareVue – 15.04.04.2806.Open.02.01.1.210401 (previous)
  • OpenVista CareVue – 15.04.04.2806.Open.02.00.1.171108

Developer Real World Testing Plan Page URL:

Developer Real World Testing Results Report Page URL:

CHANGES TO ORIGINAL PLAN

Summary of Change
[Summarize each element that changed between the plan and actual execution of Real World Testing]
Reason
[Describe the reason this change occurred]
Impact
[Describe what impact this change had on the execution of your Real World Testing activities]
Original plan included a milestone that indicated we would begin capturing data for e-prescribing measures in July 2022 following the code release. However, we introduced code that allowed for us to review previous data so our results include data previous to July 2022 as well.The reason for this change was that we wrote the code in a way that allowed us to analyze previous data so we were not just looking at transactions that occurred after the code release.We believe this change had a positive impact on our results as it displays the number of transactions throughout the year as opposed to two quarters.

WITHDRAWN PRODUCTS

Not applicable

SUMMARY OF TESTING METHODS AND KEY FINDINGS

To demonstrate the features used in the interoperability measures, we created scripts that would log certain descriptive information into tables that we could review and perform data analysis against. We were able to review success and failure rates of certain interoperability functions to ensure the feature was functioning and to be able to work with our clients to increase adoption where suitable. During our testing, we encountered an area where we did have to work with additional sources in order to get the exact data called out in our plan but ultimately were able to obtain the data.


In cases where we gathered the data and the data indicated that no utilization was actually being performed in the real world, we reverted to an internal test environment to conduct testing against the feature along with the standards to ensure the feature was functioning as designed and certified.


For each of the methods that we used, whether collecting real world data or reverting to an internal test environment, the results shared in this report reflect the real world success rate of utilization of interoperability features or confirmation that the feature is working as intended.

STANDARDS UPDATES (INCLUDING STANDARDS VERSION ADVANCEMENT PROCESS (SVAP) AND UNITED STATES CORE DATA FOR INTEROPERABILITY (USCDI))

No, none of my products include these voluntary standards.

Standard (and version)This product utilizes all standards associated with the 2015 certification method

Care Settings

Inpatient care setting was used to obtain the results for this report.

Metrics and Outcomes

Measurement /MetricAssociated Criterion(a)Relied Upon Software (if applicable)Outcomes
Measure 1.1 Provider exchange (sending and receiving)170.315(b)(1) Transitions of Care, 170.315(b)(2) Clinical Information Reconciliation and Incorporation, 170.315e(1) View, download, and transmit to 3rd party, Data Export and 170.315(h)(1) Direct Project,Surescripts Clinical Direct MessagingSystem logs were used to retrieve data that represented the transmission of CCDs by providers. Overall, we had 291 attempted transmissions with 264 being successful, resulting in a 0.9% error rate.

Other analysis indicated that for some clients, utilization seemed to decrease over each quarter, while most clients remained in the same vicinity through out the year.
Measure 1.2 Patient exchange (Download and Transmit)170.315(b)(1) Transitions of Care, 170.315(b)(2) Clinical Information Reconciliation and Incorporation, 170.315e(1) View, download, and transmit to 3rd party, Data Export and 170.315 (h)(1) Direct Project,Surescripts Clinical Direct MessagingSystem logs were used to retrieve data representative of patients performing download and then transmitting their health data to an outside source. Overall, we had 25 transmission attempts in which all 25 attempts were successful, resulting in a 100% success rate.

We also reviewed the transmission methods of these attempts which showed almost an even split. The results showed 12 encrypted transmission methods with 13 unencrypted transmission methods.
Measure 2 Data Export170.315(b)(6) Data ExportNot ApplicableSystem logs were used to retrieve data representative of when the batch export was utilized. The results indicated that this function has a very low utilization rate. Throughout the year, this function was only used 1 time in which it was successful, resulting in a 100% success rate. Upon further review, we did find that this batch export, although only ran once, did contain 7,613 files and ran successfully without limitations.

E-Prescribing

Measurement /MetricAssociated Criterion(a)Relied Upon Software (if applicable)Outcomes
Measure 3 E-prescribing successful transmissions170.315(b)(3) Electronic PrescribingNewCropSystem logs were used to retrieve data representative of the function when users create a prescription and electronically transmit the prescription to a pharmacy. In total, 154,481prescriptions were transmitted electronically, with 18 of those transmissions failing. This resulted in a 0.012% error rate.
Other observations indicated that the number of transmissions for prescriptions remained consistent throughout the year by practice.

Transmission of HL7 messages

Measurement /MetricAssociated Criterion(a)Relied Upon Software (if applicable)Outcomes
Measure 4.1 Transmission of messages to outside entities170.315(f)(1) Transmission to immunization registries,
170.315(f)(2) Transmission to public health agencies – Syndromic surveillance,
170.315(f)(3) Transmission to public health agencies – reportable laboratory tests and value/results.
MirthSystem logs were used to retrieve data representative of the HL7 messages that were transmitted. Overall, there were 972.178 HL7 messages that were sent with 253 of those messages failing. This results in a 0.03 % error which falls within our anticipated error rate of less than 10% due to issues with network connectivity.
We also drilled into the data to determine individual rates of specific transmissions. We found that Syndromic messages were being transmitted more than labs and immunizations with 937,103 of the total messages were related to Syndromic activity.
Measure 4.2 Health care surveys170.315(f)(7) Transmission to public health agencies – health care surveysNot applicableUpon reviewing system logs it was found that no clients were using the function of health care surveys. To adhere to our plan, we reverted to an internal test environment to ensure the function was still working as designed. Overall, this resulted with a 100% success rate.

Export Data File

Measurement /MetricAssociated Criterion(a)Relied Upon Software (if applicable)Outcomes
Measure 5 Export Data File (export of QRDA files)170.315(c)(1) record and exportNot ApplicableSystem logs were used to retrieve data representative of when QRDA cat 1 files were exported. Overall, there were 2,758 files exported which all were successful, resulting in a 100% success rate. We also noted that these exports all occurred during Q1 which was anticipated.

API Requests

Measurement /MetricAssociated Criterion(a)Relied Upon Software (if applicable)Outcomes
Measure 6 API Requests170.315(g)(7) Application Access – Patient Selection,
170.315(g)(8) Application Access – Data Category Request,
170.315(g)(9) Application Access-All Data Request
Not ApplicableUpon reviewing system logs it was found that no clients were using these functions. To adhere to our plan, we reverted to an internal test environment to recreate the requests for patient selection, data category and all data. Using the test environment, all requests were performed and successful resulting in a 100% success rate.

KEY MILESTONES

Key MilestoneCare SettingDate/Timeframe
Deployment of code allowing ability to capture additional information in system logs.InpatientFebruary 2022
Deployment of code allowing ability to capture additional information in system logs needed for the e-prescribing measure only.InpatientJuly 2022
Collection and review of dataInpatientMarch 2022,
June 2022,
September 2022
December 2022
Compiled all data in aggregate analysisInpatientDecember 2022
Create and submit aggregate results reportInpatientJanuary/February 2023

Acknowledgement Signature

This Real World Testing Results Report is complete with all required elements, including measures that address all certification criteria and care settings. All information in this report is up to date and fully addresses the health IT developer’s Real World Testing requirements.

Authorized Representative Name:Nicki Anderson, Director, Compliance
Authorized Representative Email:nicki.anderson@medsphere.com
Authorized Representative Phone:760.979.6531
Authorized Representative Signature:Nicki Anderson
Date:January 27, 2023