This is the real world test plan for CY 2022 for the Visiontree VTOC v5.1.1 certified modular EHR solution. It provides the real world test measurements and metrics that meet the intent and objectives of ONC's Condition of Certification and Maintenance of Certification requirement for real world testing (§ 170.405 Real world testing) to evaluate compliance with the certification criteria and interoperability of exchanging electronic health information (EHI) within the care and practice setting which it is targeted for use.
As ONC has stated in its rule, "The objective of real world testing is to verify the extent to which certified health IT deployed in operational production settings is demonstrating continued compliance to certification criteria and functioning with the intended use cases as part of the overall maintenance of a health IT's certification." We have worked toward this objective in designing our test plan and its subsequent real world testing measurements and metrics.
This document builds toward the final testing measurements and metrics we will use to evaluate our product interoperability within production settings. Within each measure, we document planned testing methodology, associated ONC criteria, justification for measurement, expected outcomes from the testing, care settings applied for this measure, and if applicable the number of clients to use the our real world testing approach, including how our test cases were created, our selected methodology, the number of client/practice sites to use, and our general approach and justification for decisions.
We have included our timeline and milestones for completing the real world testing in CY 2022 and information about compliance with the Standards Version Advancement Process updates.
This Real World Testing plan is complete with all required elements, including measures that address all certification criteria and care settings. All information in this plan is up to date and fully addresses the health IT developer's Real World Testing requirements.
For CY 2022, we are not planning to make any version updates on approved standards through the SVAP process. Standard (and version) All standards versions are those specified in USCDI v1.
The measurements for our real world testing plan are described below. Each measurement contains:
In each measurement evaluate, we elaborate specifically on our justification for choosing this measure and the expected outcomes. All measurements were chosen to best evaluate compliance with the certification criteria and interoperability of exchanging electronic health information (EHI) within the certified EHR.
Per the ONC requirements, we have include at least one measurement/metric that addresses each applicable certification criterion in the Health IT Module's scope of certification.
For each measurement, a testing methodology is used. For our test plan, we use the following methodologies.
The VTOC patient portal is primarily targeted to the ambulatory and oncology health settings, and our measures were design for this setting in mind. In each measure, we do also address the care settings targeted and note any necessary adjustment or specific factor to consider with this specific measure. Within each measure, we note the minimum number of clients or client sites we plan to use for this measure evaluation.
This measure is tracking and counting how many patients are given login access to their patient portal account and able to access their patient data on the portal over the course of a given interval.
The interval for this measure will be 3 months, and we will record the results of unique patient accessing their accounts during this time.
VTOC is an interoperable, standalone patient portal that integrates with other EHRs, and its primarily use is for patients is to view their health information so that they can be an active participant in their healthcare decisions and treatment.
This measure provides several key data points to confirm and verify real world interoperability.
This measure will provide a numeric value to indicate how often this interoperability feature is being used. An increment to this measure indicates that the EHR can supply patient health data to the patient portal and provide an account for the patient to use in accessing this data.
The measurement will produce numeric results over a given interval. We will utilize various reports and audit logs, including Automated Measure (315.g.2) reports, to determine our measure count.
A successful measure increment indicates compliance to the underlying ONC criteria. It will show that the EHR can submit patient health data to the patient portal on a regular and consistent basis as well provide an account for the patient to use in accessing this data.
Successfully completing this measure also implies users have a general understanding of the EHR functional operations for this EHR Module and an overall support for the user experience.
We will use the measure count to establish a historic baseline of expected interoperability use so it can be used in subsequent real world testing efforts.