Real World Testing Real World Testing Results 2025

menu close

Real World Testing Results 2025 (RWT)

General Information

Developer Name CloudCraft Software
Product Name CloudCraft Software
Version Number 9.0
Certified Health IT Edition 2015 Cures Update
Product List (CHPL) ID 15.04.04.3071.Clou.09.01.1.221227
Real World Testing Public URL https://cloudcraftsoftware.com/realworldtesting.html

Changes to Original Plan

Summary of Change Reason Impact
Removed below criteria from testing:
  • 170.315(b)(1) Transitions of care
  • 170.315(b)(2) Clinical information reconciliation and incorporation
  • 170.315(b)(10) Electronic Health Information export
  • 170.315(c)(1) Record and Export
  • 170.315(c)(2) Import and Calculate
  • 170.315(c)(3) Report
  • 170.315(f)(1) Transmission to immunization registries
  • 170.315(f)(5) Transmission to public health agencies — electronic case reporting
  • 170.315(f)(7) Transmission to public health agencies — health care surveys
  • 170.315(h)(1) Direct Project
 ASTP/ONC’s enforcement discretion due to Executive Order (EO) 14192. No measurable impact.
Utilized b.well as a PHR to validate 170.315(g)(10) instead of MyLinks as described in the plan. During the testing period, the MyLinks staging servers were unexpectedly taken offline. We were able to redirect and utilize the Walgreens app, powered by b.well, instead. No measurable impact.

Summary of Testing Methods and Key Findings

Several patients were successfully accessed via the Walgreens app, powered by b.well, utilizing the Dynamic FHIR API. All patient information was thoroughly inspected to ensure the data shown in Walgreens was identical to the original data in CloudCraft. No discrepancies or missing data were found.

The below criteria were tested:

§ 170.315(g)(7) Application access— patient selection
§ 170.315(g)(9) Application access— all data request
§ 170.315(g)(10) Standardized API for patient and population services

Care setting(s) that were tested for real world interoperability

Ambulatory

Voluntary updates to the standards and implementation specifications approved through SVAP (if applicable)

N/A

Metrics and Outcomes

Measurement/Metric Associated Criteria Outcomes Relied Upon Software
Patient is able to retrieve FHIR API data from PHR app for 100% of encounters. (g)(7) Application access— patient selection
(g)(9) Application access— all data request		 100% data retrieved. ConnectEHR
Dynamic FHIR
Inferno / Walgreens
(powered by b.well)
In 100% of encounters from Step #1, PHR data matches data from EHR. This will be confirmed by visual validation of CCDS. (g)(7) Application access— patient selection
(g)(9) Application access— all data request		 All information matched. ConnectEHR
Dynamic FHIR
Inferno / Walgreens
(powered by b.well)
100 percent of encounters where Patient is able to retrieve FHIR API data from PHR app. (g)(10) Standardized API for patient and population services 100% data retrieved. ConnectEHR
Dynamic FHIR
Inferno / Walgreens
(powered by b.well)
100 percent of encounters from Step #1 where Patient’s PHR data matches data from EHR. This will be done by visual validation of the following FHIR resources:
a. Demographics
b. Problems
c. Medications
d. Allergies
 (g)(10) Standardized API for patient and population services All information matched. ConnectEHR
Dynamic FHIR
Inferno / Walgreens
(powered by b.well)
100 percent of encounters where Provider is able to retrieve FHIR API data from app. (g)(10) Standardized API for patient and population services 100% data retrieved. ConnectEHR
Dynamic FHIR
Inferno
100 percent of encounters from Step #3 where data for randomly-selected patients as presented in app matches data from EHR. This will be done by visual validation of the following FHIR resources:
a. Demographics
b. Problems
c. Medications
d. Allergies 		(g)(10) Standardized API for patient and population services All information matched. ConnectEHR
Dynamic FHIR
Inferno

Key Milestones

Key Milestone Care Setting Date/Timeframe
Calculate and compile metrics Ambulatory August 2025
  • Partner with PHR or identify existing PHR that can receive patient clinical data as described in this RWT plan.
  • Ensure that PHR has functionality to access the Dynamic FHIR API, as described here.
  • Partner with EHR that is integrated with the Dynamic FHIR API and Patient Portal modules of ConnectEHR.
Ambulatory August 2025
Encounter is created and visually confirmed Ambulatory August 2025
  • Dynamic FHIR API has transformed C-CDA into FHIR resources.
  • PHR app consumes FHIR resources to populate EHR data
Ambulatory August 2025
Visually validate Assessment, Plan of Treatment and Health Concerns narrative text Ambulatory August 2025
Calculate and compile metrics Ambulatory August 2025
  • The identified testing location is able to select a subset of survey questions that are relevant to its activities.
  • Location confirms availability of survey option in patient portal.
 Ambulatory July 2025
Responses are converted to HL7 CDA documents for transmission. Ambulatory July 2025
Calculate and compile metrics Ambulatory July 2025