REAL WORLD TESTING RESULTS REPORT 2025

General Information

Plan Report ID Number: 20241105emp

Developer Name

eMedPractice, LLC

Product Name(s)

eMedicalPractice

Version Number(s)

2.0

Product List (CHPL) ID(s)

15.02.05.2898.EMED.01.01.1.220112

Certified Health IT

2015 Edition

Developer Real World Testing Page URL

Changes to Original Plan

Summary of Change Reason Impact
The scope of this report has been refined to focus exclusively on API certification criteria (G7, G9, and G10). This enables a more detailed and targeted analysis of API functionality and interoperability testing results. The report now concentrates solely on application access and standardized API requirements. Coverage is now restricted to application access and standardized API requirements, enabling a deeper and more comprehensive analysis of real-world API testing outcomes.
The testing scope was strategically refined to align with observed customer usage patterns of API features, ensuring that testing efforts accurately reflect real-world implementation and operational behavior. This refinement was informed by a detailed analysis of 2025. Customer adoption trends and API usage metrics. Testing activities were primarily conducted in stage and production environments where API functionality is actively utilized, with controlled and appropriately simulated testing scenarios employed as necessary to validate full functional coverage and ensure end-to-end interoperability.

standards updates

(STANDARDS VERSION ADVANCEMENT PROCESS (SVAP) STANDARDS UPDATES)
Standard (and version) For the g10 criterion:

170.215(b)(1)(i) 4.0.0 HL7® FHIR® US Core Implementation Guide STU 4.0.0, June 2021

170.215(c)(2) HL7® FHIR® SMART Application Launch Framework Implementation Guide Release 2.0.0, November 26, 2021

170.215(d)(1) HL7® FHIR® Bulk Data Access (Flat FHIR®) (v2.0.0: STU 2), November 26, 2021

Updated certification criteria and associated products 170.315(g)(10) for eMedicalPractice
Health IT Module CHPL ID 15.02.05.2898.EMED.01.01.1.220112
Date of ONC ACB notification 11/16/2024
Date of customer notification (SVAP only) 12/01/2022
Conformance measure Measurement/metric from the RWT Plan associated with g10 (170.315(g)(10) Standardized API for patient and population services).

Summary of Testing Methods and Key Findings

Test Plan:

The test cases incorporated actions performed by multiple user types to accurately capture required data elements and workflow variations. In select scenarios, real-world patient data was utilized to validate compliance with specific certification requirements, including confirmation of successful data transmission and status handling. Compliance with applicable required standards was verified through a combination of manual inspection and the use of ONC-recommended testing tools, ensuring thorough and reliable validation of certification criteria.

Test Methods:

The following test methods were used to complete testing of conformance with the certification criteria requirements.

  • Entry of simulation data
  • Analysis of log data & log files
  • Testing with ONC-approved testing tools
  • Real time patient centric scenarios in production environment

Lessons learned:

Working with real-world data consistently presents challenges, particularly due to the frequent identification of data formatting inconsistencies. Despite these challenges, the customer-used tools demonstrated reliable and effective functionality overall, supporting successful processing and validation of the required data.

Key Findings:

Testing confirmed the API functionality for patient data access performed as certified in stage and production environments. The system successfully authenticated patient API requests and returned USCDI data elements in the required formats (C-CDA and FHIR). One performance-related challenge with large dataset exports was identified and mitigated.

Associated Certification Criteria

The following are the list of certification criteria associated with the measure and relied upon software.

Measurement/Metric Description Justification Relied Upon Software
170.315(g)(7) Application access - patient selection

Demonstration of a patient's ability to make a data request through API for one or more data elements from the USCDI data set.

This is to justify that if a patient makes a request for a data category for one or more of the data elements in the USCDI data set from an API.
170.315(g)(9) Application access - all data request

Demonstration of a patient's ability to make a data request through API for one or more data elements from the USCDI Data Set.

This is to justify that if a patient makes a request for complete data elements in the USCDI Data set from an API.
170.315(g)(10) Standardized API for patient and population services

Healthcare data standard(FHIR) with an application programming interface (API) for representing and exchanging electronic health records.

This is to justify that if a patient data can be exchanged between two health care providers using FHIR

Care Setting(s)

Care Setting Justification

The selected specialty facility settings are representative of all of the settings that are currently using the eMedicalPractice. The test results are same for all specialties & facilities.

Ambulatory Primary care

Ambulatory Primary care PCPB

Ambulatory Primary care GC

Ambulatory Primary care PCP

Ambulatory Primary care NMG

Ambulatory Pulmonary

Ambulatory Pulmonary PA

Ambulatory Cardiology

Ambulatory Cardiology HM

Ambulatory Cardiology AZ

Execution & Outcomes

Measurement/Metric Care Settings Associated Criterion Relied Upon Software Execution Plan Actual Outcomes Results Evidence Challenges Encountered Time Frame for Key Milestones
170.315(g)(7) Application access - patient selection Ambulatory Pulmonary PA
Ambulatory Primary care PCPB
Ambulatory Primary care PCP
Total number patient API authentication requests came in. Total number patient API requests completed by checking in log. Data errors/accuracy will be tracked over the time and trended over the time. The test was conducted with 5 test patients on stage environment to gain the API access and search patients. Got the access to patient search API and returned API access token. Patient were found based on the provided search criteria. 4th Quarter
170.315(g)(9) Application access - all data request Ambulatory Primary care PCP
Ambulatory Primary care PCPB
Total number patient API authentication requests came in. Total number of patient API requests completed for all data by checking in log. Error rates will be tracked and trended over time. Test was performed on our stage environment. A total of 5 sample test patients were used to validate the application’s data response. Successfully API connection was made. Sent the API token along with patient search criteria.
Received one or more patient USDCI data elements for each request.
API returned a Valid C-CDA V2 XML document with data for the requested date range for all sections including all required sections. 4th Quarter
170.315(g)(10) Standardized API for patient and population services Ambulatory Primary care PCP
Ambulatory Primary care PCPB
Registered an account and sent the request to pull patient data using Healthcare data standard(FHIR) with an application programming interface (API) Tested this in stage(inferno tool) environment.
Testing involved executing the 7 test cases.
1)Patient authentication and authorization via OAuth 2.0
2)Retrieving patient demographics, medications, and conditions via FHIR API
3)Validating the response format and conformance with USCDI standards.
1)Successfully authenticated
2)Patient data returned in FHIR R4 format
3)Medications returned as FHIR resources
Payload truncation due to size limits. Inconsistent client registration behavior 4th Quarter

Key Milestones

Key Milestone Care Setting Date/Timeframe

Identified various ambulatory care settings and start capturing the data & logs

Ambulatory

1st Quarter of 2025

with final data collection, datasets generated and analyzed during the current study.

Ambulatory

1st, 2nd, 3rd & 4th Quarter of 2025

Report the final data to ACB

Ambulatory

01/28/2026

Disclaimer

eMedicalPractice is committed to Real World Testing (RWT) plan as much as possible but execution of this plan is dependent on eMedicalPractice customer participation on the RWT activity throughout calendar year 2025, based on their availability, which is beyond eMedicalPractice’s control. eMedicalPractice strives to review the plan on an ongoing basis and may modify the RWT plan steps as and when necessary to fully meet the needs of RWT. There are a few criteria that needs mentioning owing to less adoption by the industry or by customer base.

Attestation

This Real World Testing 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 & Reporting requirements.

Authorized Representative Name

Nandu Dhanekula

Authorized Representative Email

Nandu@emedpractice.com

Authorized Representative Phone

561-921-0978

Authorized Representative Signature
Date

01/28/2026

REAL WORLD TESTING PLANS & REPORTS

Scroll to Top