QSmartCare | Real World Testing Plan

Real world Testing - QSmartcare

Real World Testing Results Report

QSmartCare

Executive Summary

This is the test report for CY 2024 real world testing for QSmartCare, a certified EHR solution from Magilen Enterprises Inc. This is the document to our CY 2024 real world test plan that describes our approach for conducting real world testing in CY 2024 and how the testing measures we employed.

Our findings show that QSmartCare certified EHR is working as it was certified as no errors or non-compliances were observed. We did make some adjustments and add in some compliance testing as several of our measures had metrics of “0” results because our clinician users do not perform the certified functionality in daily workflows.

For each of our CY 2024 Real World Testing Measures, we have recorded our results and findings. If any non-conformities or errors were encountered, we noted them. Our signed attestation of compliance with the real world testing requirements is on the following page.

General Information

Plan Report ID Number: 20231108mag

Developer Name: Magilen Enterprises, Inc

Product Name(s): QSmartCare

Version Number(s): 1.0

Certified Health IT Product List (CHPL) ID(S):

· 15.05.05.3098.MAGE.01.00.1.220127

· https://chpl.healthit.gov/#/listing/10803

Developer Real World Testing Page URL: https://qsmartcare.com/real-world-testing-documentation.html

Changes to Original Plan

Changes to the approach for Real World Testing that differ from what was outlined in the plan, are noted here

Summary of Change	Reason for Change	Impact
170.315(b)(1) Transitions of care - Receive	Because our users do not share clinical data via the C-CDA and Direct messaging, our metric results were 0. We have used audit logs and database queries to confirm this result get the required metrics for this Real World Testing. We tested in our mirror environment that the C-CDAs are successfully received and/or incorporated upon receipt from a 3rd party via Direct messaging during a transition of care event.	No Impact
170.315(b)(1) Transitions of care - Send	Because our users do not share clinical data via the C-CDA and Direct messaging, our metric results were 0. We have used audit logs and database queries to confirm this result get the required metrics for this Real World Testing. We created C-CDA test patients in our mirror environment and validated the the C-VDAs are successfully sent from the EHR Module to a 3rd party via Direct messaging during a transition of care event	No Impact
170.315(b)(2) Clinical information reconciliation and incorporation:	Because our users do not share clinical data via the C-CDA and Direct messaging, our metric results were 0. However, to verify these capabilities are still working in a production environment we created C-CDA test patients and validated. We were able to incorporate problems, medications, and medication allergies from test patients. We also confirmed our DataMotionDirect HISP was functional for our Direct exchange capabilities.	No Impact
170.315(e)(1) View, download, and transmit to 3rd party	Patient portal was not used by our patients so our metric results were 0. However, to verify the capabilities still work in a production environment. We created C-CDA test patients and validated that we were able to login as patient in patient portal and view, download and transmit data to 3rd party.	No Impact
170.315(g)(7,9) API	We did not have any request for use our API functionality in CY 2024 so our metrics for this measure are 0. We created C-CDA test patients and validated that we were able to view the patient information via API using the Postman tool. We were able to successfully confirm our API works in a production setting	No Impact
170.315(b)(10) Electronic Health Information Export	We did not have any request for use our EHI Export functionality in CY 2024 so our metrics for this measure are 0. To make sure that the feature is working fine we tested in our mirror environment, only authorized user was able to login and perform an export of data for single and multiple patient and demonstrated to be functioning without any problems.	No Impact
170.315(c)(1) Clinical quality measures (CQMs) Record and Export	During CY 2024, our users did not submit any eCQMs because they did not participate in the MIPS program nor any other program requiring eCQMs. As a result, our test results for this metric are 0. We confirmed our certified capabilities are working fine in production environment. We created a patient details record in our mirror environment to make sure the feature is working correctly. This way, the user can export QRDA 1 files for both single and multiple patients at any time without additional assistance from developers, and it has been shown to work without any issues.	No Impact
170.315(c)(2) Clinical quality measures (CQMs) Import and calculate	During CY 2024, our users did not submit any eCQMs because they did not participate in the MIPS program nor any other program requiring eCQMs. As a result, our test results for this metric are 0. We confirmed our certified capabilities are working fine in production environment. In order to ensure that the feature is functioning properly, we developed a mirror environment where the user can import QRDA 1 files whenever they want and without further help from developers, and it has been shown to work without any issues.	No Impact
170.315(c)(3) CQMs – report	During CY 2024, our users did not submit any eCQMs because they did not participate in the MIPS program nor any other program requiring eCQMs. As a result, our test results for this metric are 0. We confirmed our certified capabilities are working fine in production environment. In order to ensure that the feature is functioning properly, we developed a mirror environment where the user can import QRDA files and then generate a report by entering the start and end date for the required measure by clicking the QRDA III icon to download the files, and it has been shown to work without any issues.	No Impact
170.315(f)(1) Transmission to Immunization Registries	During CY 2024, our users did not have enter the immunization so our metrics for this measure are 0. We verified that the immunization interface is active and working between the QSmartCare and public health registry.	No Impact
170.315(f)(2) Public Health - Syndromic Surveillance	During CY 2024, none of our users reported data to syndromic surveillance registries electronically, hence data for this measure could not be collected. We verified that the syndromic surveillance interface is active and working between the QSmartCare and public health registry.	No Impact
170.315(b)(3) Electronic prescribing:	Our users have not performed the prescription-related electronic transactions (eRx) using required standards. So, it is not possible to demonstrate the correct standards used because as wound care physician we do not receipt other facility and have no incentive to participate. To make sure that the feature is working fine we tested in our mirror environment as mentioned the scenarios below and demonstrated to be functioning without any problems. a) New Prescription: We verified that a prescriber can successfully create and send a prescription for a new medication to the pharmacy in a mirror environment. The prescription must be sent electronically and received by the pharmacy’s system without error. b) Cancelling a Prescription: Confirm that when a prescriber cancels a prescription, the pharmacy receives the cancellation in real-time, and that the system accurately reflects the voided status. c) Changing a Prescription: Verify that changes made to a prescription (whether it’s dosage, frequency, etc.) are sent correctly to the pharmacy and are reflected in their system accurately. d) Denied Prescription Requests: Check that if a prescription is denied, the system captures the denial and enables follow-up actions (such as modifying the prescription or contacting the patient). e) Renewal Requests: Verify that the prescriber can receive and respond to a renewal request accurately, ensuring that the renewal request is either approved or denied with the appropriate communication sent to the pharmacy.	No Impact
170.315(h)(1) Direct Project	Our users have not sent / received any health information using direct project. Therefore, the metric measure for this is 0. To make sure that the feature is working fine we tested in our mirror environment and demonstrated to be functioning without any problems we created C-CDA test patients and validated we were able to incorporate problems, medications, and medication allergies from them. We also confirmed our DataMotionDirect HISP was functionality for our Direct exchange capabilities.	No Impact
170 315(b)(9) Care Plan	Create - Our users did not create any care plan document. Therefore, our metric results were 0. Receive -Our users do not share clinical data via the C-CDA and Direct messaging, our metric results were 0. However, to verify the capabilities still work in a production environment. We created C-CDA test patients in our mirror environment and validated we were able to incorporate careplan document. We also confirmed our DataMotionDirect HISP was functionality for our Direct exchange capabilities.	No Impact
170 315(g)(10) Standardized API for Patient and Population Service	We did not have any request for use our API functionality in CY 2024 so our metrics for this measure are 0. We created C-CDA test patients and validated that we were able to view the patient information via API using the Postman tool. We were able to successfully confirm our API works in a production setting	No Impact

Withdrawn Products

No products have been withdrawn

Summary of Testing Methods and Key Findings

We have used audit logs and database queries to get the required metrics for this Real World Testing. All the operations mentioned in our RWT plan are tested. Data was collected from 1 Jan 2024 to 31 Dec 2024. We have collected data based on the usage. All the functionalities worked as excepted, and the outcomes are documented below. In our testing, we did confirm that our users do not utilize Direct messaging. Our EHR is only used by one healthcare provider (ourselves) and our provider have not used Direct to send/receive C-CDAs thus far. During our testing, we did not discover any errors or criteria non-conformities.

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

[✓ ] Yes, I have products certified with voluntary SVAP or USCDI standards. (If yes, please complete the table below.

[ ] No, none of my products include these voluntary standards.

In CY 2024, we updated our product to support the Cures certification requirement and were certified accordingly. We implemented USCDI v1 and the C-CDA Companion Guide Release 3 and were certified on those versions.

Standard (and version)	USCDI v1
Updated certification criteria and associated product	b1, b2, e1, g9
CHPL Product Number	15.05.05.3098.MAGE.01.00.1.220127
Conformance Measures	Measures 1 and 2 for b1 Measure 3 for b2 Measure 4 for e1 Measure 5 for g9

SVAP Standards Updates

Standard (and version)	a) 170.202(a)(2) Applicability Statement for Secure Health Transport Version 1.3, May 2021 (Direct) for b1 b) 170.205(a)(5) HL7® CDA R2 Implementation Guide: C-CDA Templates for Clinical Notes R2.1 Companion Guide, Release 3-US Realm, May 2022 for b1, b2, b9, e1, g9 c) 170.204(a)(1) Web Content Accessibility Guidelines (WCAG) 2.1, June 05, 2018 (Level A Conformance) for e1
Updated certification criteria and associated product	b1, b2, b9, e1, g9
Health IT Module CHPL ID	15.05.05.3098.MAGE.01.00.1.220127
Method used for standard update	SVAP
Date of ONC-ACB notification	11/16/2022
Date of customer notification (SVAP only)	12/25/2022
Conformance measure	Measures 1 and 2 for b1 Measure 3 for b2 Measure 4 for e1 Measure 5 for g9 Measure 14 for b9
USCDI-updated certification criteria (and USCDI version)	N/A

Care Settings

Facilities:Inpatient

Speciality:Wound Care

Metrics and Outcome

Measure	Criteria	Replied Upon Software	Outcomes	Challenges Encountered
1	170.315(b)(1) Transitions of care - Receive	Data Motion	In our testing, we did confirm that our users do not utilize Direct messaging. Our EHR is only used by one healthcare provider (ourselves) and our provider have not used Direct to send/receive C-CDAs thus far. We tested in our mirror environment that the C-CDAs are successfully received and/or incorporated upon receipt from a 3rd party via Direct messaging during a transition of care event.	NA
2	170.315(b)(1) Transitions of care - Send	Data Motion	In our testing, we did confirm that our users do not utilize Direct messaging. Our EHR is only used by one healthcare provider (ourselves) and our provider have not used Direct to send/receive C-CDAs thus far. We created C-CDA test patients in our mirror environment and validated the the C-VDAs are successfully sent from the EHR Module to a 3rd party via Direct messaging during a transition of care event	NA
3	170.315(b)(2) Clinical information reconciliation and incorporation:		Our users do not share clinical data via the C-CDA and Direct messaging, our metric results were 0. However, to verify the capabilities still work in a production environment. We created C-CDA test patients and validated we were able to incorporate problems, medications, and medication allergies from them. We also confirmed our DataMotionDirect HISP was functionality for our Direct exchange capabilities.	NA
4	170.315(e)(1) View, download, and transmit to 3rd party:		In our testing, we did confirm that the patient portal was not used by the patients. We verified that the portal was accessible and working fine. To make sure that the feature is working fine we tested in our mirror environment and demonstrated to be functioning without any problems by creating C-CDA test patients and validated that we were able to login as patient in patient portal and view, download and transmit data to 3rd party.	NA
5	170.315(g)(7, 9) API		We did not have any developers use our API functionality in CY 2024 so our metrics for this measure are 0. We created C-CDA test patients and validated that we were able to view the patient information via API using the Postman tool. We were able to successfully confirm our API works in a production setting	NA
6	170.315(b)(10) Electronic Health Information Export		We did not have any developers use our Data Export functionality in CY 2024 so our metrics for this measure are 0. We verified that the data export was accessible and working fine. To make sure that the feature is working fine we tested in our mirror environment, only authorized user was able to login and perform an export of data for single and multiple patient and demonstrated to be functioning without any problems.	NA
7	170.315(c)(1) Clinical quality measures (CQMs) Record and Export		During CY 2024, our users did not submit any eCQMs. As a result, our test results for this metric are 0. We confirmed our certified capabilities are working fine. We created a patient details record in our mirror environment to make sure the feature is working correctly. This way, the user can export QRDA 1 files for both single and multiple patients at any time without additional assistance from developers, and it has been shown to work without any issues.	NA
8	170.315(c)(2) Clinical quality measures (CQMs) Import and calculate		During CY 2024, our users did not submit any eCQMs. As a result, our test results for this metric are 0. We confirmed our certified capabilities are working fine. In order to ensure that the feature is functioning properly, we developed a mirror environment where the user can import QRDA 1 files whenever they want and without further help from developers, and it has been shown to work without any issues.	NA
9	170.315(c)(3) Clinical quality measures (CQMs) Report		During CY 2024, our users did not submit any eCQMs. As a result, our test results for this metric are 0. We confirmed our certified capabilities are working fine. In order to ensure that the feature is functioning properly, we developed a mirror environment where the user can import QRDA files and then generate a report by entering the start and end date for the required measure by clicking the QRDA III icon to download the files, and it has been shown to work without any issues.	NA
10	170.315(f)(1) Transmission to Immunization Registries		We did not have any users enter the immunization in CY 2024 so our metrics for this measure are 0. We verified that the immunization interface is active and working between the QSmartcare and public health registry.	NA
11	170.315(f)(2) Public Health - Syndromic Surveillance:		None of our users reported data to syndromic surveillance registries electronically, hence data for this measure could not be collected. We verified that the syndromic surveillance interface is active and working between the QSmartCare and public health registry.	NA
12	170.315(b)(3) Electronic prescribing:	New Crop	Our users have not performed the prescription-related electronic transactions (eRx) using required standards. So, it is not possible to demonstrate the correct standards used because as wound care physician we do not receipt other facility and have no incentive to participate. To make sure that the feature is working fine we tested in our mirror environment as mentioned the scenarios below and demonstrated to be functioning without any problems. a) New Prescription: We verified that a prescriber can successfully create and send a prescription for a new medication to the pharmacy in a mirror environment. The prescription must be sent electronically and received by the pharmacy’s system without error. b) Cancelling a Prescription: Confirm that when a prescriber cancels a prescription, the pharmacy receives the cancellation in real-time, and that the system accurately reflects the voided status. c) Changing a Prescription: Verify that changes made to a prescription (whether it’s dosage, frequency, etc.) are sent correctly to the pharmacy and are reflected in their system accurately. d) Denied Prescription Requests: Check that if a prescription is denied, the system captures the denial and enables follow-up actions (such as modifying the prescription or contacting the patient). e) Renewal Requests: Verify that the prescriber can receive and respond to a renewal request accurately, ensuring that the renewal request is either approved or denied with the appropriate communication sent to the pharmacy.	NA
13	170.315(h)(1) Direct Project	Data Motion	Our users have not sent / received any health information using direct project. Therefore, the metric measure for this is 0. To make sure that the feature is working fine we tested in our mirror environment and demonstrated to be functioning without any problems we created C-CDA test patients and validated we were able to incorporate problems, medications, and medication allergies from them. We also confirmed our DataMotionDirect HISP was functionality for our Direct exchange capabilities.	NA
14	170 315(b)(9) Care Plan		Our users did not create any care plan document. Therefore, our metric results were 0. Receive - Our users do not share clinical data via the C-CDA and Direct messaging, our metric results were 0. However, to verify the capabilities still work in a production environment. We created C-CDA test patients in our mirror environment and validated we were able to incorporate careplan document from them. We also confirmed our DataMotionDirect HISP was functionality for our Direct exchange capabilities.	NA
15	170 315(g)(10) Standardized API for Patient and Population Service		We did not have any request for use our API functionality in CY 2024 so our metrics for this measure are 0. We created C-CDA test patients and validated that we were able to view the patient information via API using the Postman tool. We were able to successfully confirm our API works in a production setting	NA

Key Milestones

Key Milestones	Care Setting	Data Timeframe
Released of documentation for the Real-World Testing to be provided to authorized representatives and providers.	Facilities: Inpatient Specialties: Wound Care	October 2023
Identified the user participants to participate in the test plan	Facilities: Inpatient Specialties: Wound Care	December 2023
Confirmed that participants can log into their accounts and are ready to start the RWT test plan	Facilities: Inpatient Specialties: Wound Care	February 2024
Followed up with providers and authorized representatives regularly to understand any issues arising with the data collection.	Facilities: Inpatient Specialties: Wound Care	March 2024
Ended Real-World Testing period/final collection of all data for analysis.	Facilities: Inpatient Specialties: Wound Care	June 2024
Real World Testing data analysis and generation of report.	Facilities: Inpatient Specialties: Wound Care	August 2024
Submitted Real World Testing report to ACB (per their instructions)	Facilities: Inpatient Specialties: Wound Care	January 2025

Developer Attestation

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

Authorized Representative Name: Steven Magilen

Authorized Representative Email: smagilen@magilen.com

Authorized Representative Phone: (305) 466-9988

Authorized Representative Signature:

Date: 01/16/2025