Real World Testing Results Report
QSmartCare
Executive Summary
This is the test report for CY 2023 real world testing for QSmartCare, a certified EHR solution from Magilen Enterprises Inc. This is the document to our CY 2023 real world test plan that describes our approach for conducting real world testing in CY 2023 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 2023 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: 20221007mag
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.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. However, to verify the capabilities still work in a production environment. We created test patients and exported them as C-CDA records. We then validated them for compliance and coverage of USCDI v1 data elements. We also confirmed our DataMotionDirect HISP was functional for our Direct exchange capabilities. |
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. However, to verify the capabilities still work in a production environment. We created test patients and exported them as C-CDA records. We then validated them for compliance and coverage of USCDI v1 data elements. We also confirmed our DataMotionDirect HISP was functional for our Direct exchange capabilities. |
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 2023 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)(6) Data export |
We did not have any request for use our Data Export functionality in CY 2023 so our metrics for this measure are 0. |
No Impact |
|
170.315(c)(1) Clinical quality measures (CQMs) Record and Export |
During CY 2023, 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. |
No Impact |
|
170.315(c)(2) Clinical quality measures (CQMs) Import and calculate |
During CY 2023, 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 |
No Impact |
|
170.315(c)(3) CQMs – report |
During CY 2023, 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 |
No Impact |
|
170.315(f)(1) Transmission to Immunization Registries |
During CY 2023, 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 2023, 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)(9) Care Plan |
Create - Our users did not create any care plan document. Therefore, our metric results were 0. |
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 2023 to 31 Dec 2023. 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 2023, 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 |
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 |
|
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 |
|
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. |
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. |
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. |
NA |
|
5 |
170.315(g)(7, 9) API |
|
We did not have any developers use our API functionality in CY 2023 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)(6) Data export |
|
We did not have any developers use our Data Export functionality in CY 2023 so our metrics for this measure are 0. We verified that the data export was accessible and working fine. |
NA |
|
7 |
170.315(c)(1) Clinical quality measures (CQMs) Record and Export |
|
During CY 2023, 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. |
NA |
|
8 |
170.315(c)(2) Clinical quality measures (CQMs) Import and calculate |
|
During CY 2023, 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. |
NA |
|
9 |
170.315(c)(3) Clinical quality measures (CQMs) Report |
|
During CY 2023, 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. |
NA |
|
10 |
170.315(f)(1) Transmission to Immunization Registries |
|
We did not have any users enter the immunization in CY 2023 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. We have a testing methodology for these capabilities to test the plan below to demonstrate the feature is available and functions as expected. |
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. We have a testing methodology for these capabilities to test the plan below to demonstrate the feature is available and functions as expected should any users elect to begin using this feature. |
NA |
|
14 |
170 315(b)(9) Care Plan |
|
Our users did not create any care plan document. Therefore, our metric results were 0. |
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 |
October 2022 |
|
Identified the user participants to participate in the test plan |
Facilities: Inpatient |
December 2022 |
|
Confirmed that participants can log into their accounts and are ready to start the RWT test plan |
Facilities: Inpatient |
February 2023 |
|
Followed up with providers and authorized representatives regularly to understand any issues arising with the data collection. |
Facilities: Inpatient |
March 2023 |
|
Ended Real-World Testing period/final collection of all data for analysis. |
Facilities: Inpatient |
June 2023 |
|
Real World Testing data analysis and generation of report. |
Facilities: Inpatient |
August 2023 |
|
Submitted Real World Testing report to ACB (per their instructions) |
Facilities: Inpatient |
January 2024 |
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/02/2024