Real World Testing 2025 (RWT)
Care Coordination | |||||
Passed | Passed | ||||
§ 170.315(b)(1) Transitions of care | § 170.315(b)(10) EHI export | ||||
§ 170.315(b)(2) Clinical information reconciliation and incorporation | |||||
Clinical Quality Measures | Application Programming Interfaces | ||||
Passed | Passed | ||||
§ 170.315(c)(1) — record and export | § 170.315(g)(7) Application access— patient selection | ||||
§ 170.315(c)(2) — import and calculate | § 170.315(g)(9) Application access— all data request | ||||
§ 170.315(c)(3) — report | § 170.315(g)(10) Standardized API for patient and population services | ||||
Public Health | |||||
Passed | |||||
§ 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 | |||||
Electronic Exchange | |||||
Passed | |||||
§ 170.315(h)(1) Direct Project |
Criteria | Care Setting | Measurement Period | Date | Key Milestones | ||||
---|---|---|---|---|---|---|---|---|
Care Coordination | ||||||||
§ 170.315(b)(1) Transitions of care § 170.315(b)(2) Clinical information reconciliation and incorporation § 170.315(h)(1) Direct Project: from the Electronic Exchange Category |
Ambulatory |
|
May, 2025 |
|
||||
June, 2025 |
|
|||||||
July, 2025 | Recipient uses scorecard to grade C-CDA | |||||||
August, 2025 |
|
|||||||
September, 2025 |
|
|||||||
September, 2025 | Calculate and compile metrics | |||||||
§ 170.315(b)(10) EHI export | Ambulatory |
|
July, 2025 |
|
||||
July, 2025 | Use the Edge Test Tool to check validity of output file(s) | |||||||
July, 2025 | Calculate and compile metrics | |||||||
Clinical Quality Measures | ||||||||
§ 170.315(c)(1)—record and export § 170.315(c)(2)—import and calculate § 170.315(c)(3)—report |
Ambulatory |
|
August, 2025 |
|
||||
August, 2025 | The file should upload and be accepted by the environment without error. | |||||||
August, 2025 | All populations of all measures should match. | |||||||
August, 2025 | Calculate and compile metrics | |||||||
Public Health | ||||||||
§ 170.315(f)(1) Transmission to immunization registries | Ambulatory |
|
July, 2025 |
|
||||
July, 2025 | Validate that immunization interface is functioning as expected | |||||||
July, 2025 | Verify immunization data was received in registry. | |||||||
July, 2025 | Verify immunization data was received in HIE Portal | |||||||
July, 2025 | Calculate and compile metrics | |||||||
§ 170.315(f)(5) Transmission to public health agencies — electronic case reporting | Ambulatory |
|
July, 2025 | eCR messages are successfully received and processed by public health agency | ||||
July, 2025 | Functioning eCR interface to public health agency | |||||||
July, 2025 | Calculate and compile metrics | |||||||
§ 170.315(f)(7) Transmission to public health agencies — health care surveys | Ambulatory |
|
July, 2025 |
|
||||
July, 2025 | Responses are converted to HL7 CDA documents for transmission. | |||||||
July, 2025 | Calculate and compile metrics | |||||||
Application Programming Interfaces | ||||||||
§ 170.315(g)(7) Application access— patient selection § 170.315(g)(9) Application access— all data request |
Ambulatory |
|
August, 2025 |
|
||||
August, 2025 | Encounter is created and visually confirmed | |||||||
August, 2025 |
|
|||||||
August, 2025 | Visually validate Assessment, Plan of Treatment and Health Concerns narrative text | |||||||
August, 2025 | Calculate and compile metrics | |||||||
§ 170.315(g)(10) Standardized API for patient and population services | Ambulatory & Inpatient |
|
May, 2025 |
|
||||
June, 2025 | Encounter is created and visually confirmed | |||||||
July, 2025 |
|
|||||||
May, 2025 |
|
|||||||
June, 2025 | Data is rendered correctly: Provider compares patient data in app to patient data in EHR and notes any discrepancies. | |||||||
May, 2025 |
|
|||||||
June, 2025 | Data is rendered correctly: Provider compares patient data in app to patient data in EHR and notes any discrepancies. | |||||||
August, 2025 | ||||||||
Electronic Exchange | ||||||||
§ 170.315(h)(1) Direct Project (Included with (b)(1),(b)(2) in the CareCoordination Category) |
Ambulatory |
|
SEE CARE COORDINATION | SEE CARE COORDINATION |
Table of Contents Link | Associated Certification Criteria: § 170.315(b)(1) Transition of Care (Cures Update) § 170.315(b)(2) Clinical information reconciliation and incorporation § 170.315(h)(1) Direct Project |
|||||||||||||||
Measure Description: Send and receive Transition of Care (TOC) messages with other providers to close the referral loop. The patient's ePHI will be exchanged using a C-CDA 2.1 Care Referral or Referral Note and DIRECT secure messaging for data transport. |
Justification:
We chose to concentrate on the aspects of this criterion that would:
|
|||||||||||||||
Metric Description:
|
Standards Implemented: (SVAP)
|
|||||||||||||||
Developer Info:
CloudCraft, LLC 1860 Biddle Road Dover, NC 28526 Care Setting: Ambulatory |
Product Info:
Product Name: CloudCraft Software Product Version: 9 CHPL ID: 15.04.04.3071.Clou.09.01.1.221227 Relied upon software: Product Name: Dynamic Health IT, Inc., ConnectEHR +BulkFHIR Product Version: FHIR4-B Product Name: MaxMD Direct mdEmail Product Version: Version 3.0 SOAP |
Methods Use to Demonstrate Interoperability:
|
||||||||||||||
Test Step | Testing Procedure | Expected Outcomes | Key Milestone Date | Key Milestone | Outcomes | Comment(s) | ||||||||||
1 |
Identify Trading Partner (TP) and coordinate with TP for sending/receiving clinical documents using production data as described in this RWT plan. |
|
May, 2025 | |||||||||||||
2 |
Patient A has encounter with care provider and data is captured in EHR. Care provider initiates TOC Care Referral to the TP EHR via DIRECT and to the HIE |
|
||||||||||||||
3 |
* Referral Dept. choses the appropriate provider to refer the patient to based off of scheduling & tracking |
|
June, 2025 | |||||||||||||
* |
Next steps take place in trading partner's EHR. | |||||||||||||||
4 |
Validate that C-CDA for Patient A contains USCDIv1 data elements. | Recipient uses scorecard to grade C-CDA | July, 2025 | |||||||||||||
5 |
Trading partner refers Patient A from TP EHR to system under test by generating C- CDA Clinical Document. |
|
||||||||||||||
6 |
In system under test, tester acknowledges receipt of valid Clinical Document. |
|
August, 2025 | |||||||||||||
7 |
In system under test, the incoming data is incorporated via reconciliation into Patient A's existing medical record. |
|
September, 2025 | |||||||||||||
8 |
Calculate and compile metrics | September, 2025 | ||||||||||||||
Attestation
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. |
||||||||||||||||
|
Table of Contents | Associated Certification Criteria: § 170.315(b)(10) - Electronic Health Information export |
|||||||||||||||
Measure Description: Export all available “electronic protected health information” (EHI) data elements for a population of patients for use in a different health information technology product or a third party system. This export can be used for many purposes, including data portability when a physician practice switches to a new EHR platform. |
Justification:
We chose to concentrate on the aspects of this criterion that would:
|
|||||||||||||||
Metric Description:
|
Standards Implemented: N/A | |||||||||||||||
Developer Info:
CloudCraft, LLC 1860 Biddle Road Dover, NC 28526 Care Setting: Ambulatory |
Product Info:
Product Name: CloudCraft Software Product Version: 9 CHPL ID: 15.04.04.3071.Clou.09.01.1.221227 |
Methods Use to Demonstrate Interoperability:
|
||||||||||||||
Test Step | Testing Procedure | Expected Outcomes | Key Milestone Date | Key Milestone | Outcomes | Comment(s) | ||||||||||
1 |
Using production data in an actual live environment or copy of live environment, demonstrate the ability to configure data export for all patients, specific patients, and/or by location |
|
July, 2025 | |||||||||||||
2 |
Demonstrate the ability to limit the set of users who can create CCDA batch exports | Logging in as a VendorAdmin will allow access to the export functionality | ||||||||||||||
3 |
Confirm users roles that have been denied export summary access cannot create CCDA batch exports | Logging in as a non-VendorAdmin will not allow access to the export functionality | ||||||||||||||
4 |
Create and validate a batch export for a single patient | Use the Edge Test Tool to check validity of output file(s) | July, 2025 | |||||||||||||
5 |
Create and validate a CCDA batch export for a patient population |
|
||||||||||||||
6 |
Save the export summary to a preferred location at the time of export. |
|
||||||||||||||
7 |
Using a 3rd Party App, the Provider attempts a Standalone Provider or EHR Practitioner Launch to see a list of their patients |
|
||||||||||||||
8 |
The Provider chooses a patient and requests all FHIR Document Reference resources for that patient |
|
||||||||||||||
9 |
The 3rd Party App converts the FHIR Document Reference resources back to their original format for the Provider to download and view |
|
||||||||||||||
10 |
Calculate and compile metrics. | July, 2025 | ||||||||||||||
Attestation
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. |
||||||||||||||||
|
Table of Contents | Associated Certification Criteria: § 170.315(c)(1) - Clinical quality measures (CQMS) — record and export § 170.315(c)(2) - Clinical quality measures (CQMS) — import and calculate § 170.315(c)(3) - Clinical quality measures (CQMS) — report |
|||||||||||||||
Measure Description:
|
Justification:
We chose to concentrate on the aspects of this criterion that would closely follow the actual activities of Cloud Craft users with respect to eCQM calculatlon and output:
|
|||||||||||||||
Metric Description:
|
Standards Implemented: No updates have been made. | |||||||||||||||
Developer Info:
CloudCraft, LLC 1860 Biddle Road Dover, NC 28526 Care Setting: Ambulatory |
Product Info:
Product Name: CloudCraft Software Product Version: 9 CHPL ID: 15.04.04.3071.Clou.09.01.1.221227 Relied upon Software: Product Name: Dynamic Health IT, CQMsolution Product Version: 24 |
Methods Use to Demonstrate Interoperability:
|
||||||||||||||
Test Step | Testing Procedure | Expected Outcomes | Key Milestone Date | Key Milestone | Outcomes | Comment(s) | ||||||||||
1 |
Identify Trading Partner (TP) and coordinate with TP for calculating and reporting electronic clinical quality measures (eCQMs) using production data as described in this RWT plan |
|
August, 2025 | |||||||||||||
2 |
Identify six EP (Eligible Professional) eCQMs for RWT | Based on historical data, select the most popular eCQMs. | ||||||||||||||
3 |
Identify a one calendar year reporting period with adequate patient data for reporting | Admins with sufficient familiarity with the physician practice's clinical activities should be able to choose a period with an appropriate amount of quality data. | ||||||||||||||
4 |
Capture and record clinical quality measure (CQM) data in Trading Partner's (TP) EHR. Since manual data entry for an adequate quantity of data would be onerous, we will use actual patient data.
|
Data ready for report generation | ||||||||||||||
5 |
Correctly calculate numerator, denominator, exclusion and exception values for selected eCQMs. | The CQMsolution report should complete with no errors. | ||||||||||||||
6 |
Spot-check 10 patients for each measure, ensuring that some are in the denominator only, some are in the numerator and denominator and, if possible, some are exclusions or exceptions. |
Use Patient List to check which categories Initial Patient Population (IPP), Denominator (Den), Exclusions (Excl), Numerator (Num) or Exceptions (Excp) each patient falls into. For each spot-check patient, use the drill-down to confirm that the patient data in CQMsolution (encounters, codes, demographics) matches the patient data in the EHR and that the patient is correctly categorized in CQMsolution. |
||||||||||||||
7 |
Upload the generated MIPS QRDA III file to QPP. | The file should upload and be accepted by the environment without error. | August, 2025 | |||||||||||||
8 |
Check the submission environment's measure calculation results and compare them to CQMsolution's calculation results. | All populations of all measures should match. | August, 2025 | |||||||||||||
9 |
Calculate and compile metrics. | August, 2025 | ||||||||||||||
Attestation
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. |
||||||||||||||||
|
Table of Contents | Associated Certification Criteria: § 170.315(f)(1) - Transmission to immunization registries |
|||||||||||||||
Measure Description: Create and transmit Immunization information. Enable a user to request, access, and display, a patient's evaluated immunization history and the immunization forecast from an immunization registry | Justification: We chose to concentrate on the aspects of this criterion that would provide the most patient care value in an actual setting. lmmunization registries can be very helpful in directing and informing patient care and in cost control through identification of needed immunizations and elimination of redundant immunizations. In our experience, there is a wide variation in immunization registry capabilities and some do not yet have the ability to handle a bi-directional query/response type of interface. That's why we offered the Alternate Test Approach. | |||||||||||||||
Metric Description:
|
Standards Implemented: N/A | |||||||||||||||
Developer Info:
CloudCraft, LLC 1860 Biddle Road Dover, NC 28526 Care Setting: Ambulatory |
Product Info:
Product Name: CloudCraft Software Product Version: 9 CHPL ID: 15.04.04.3071.Clou.09.01.1.221227 |
Methods Use to Demonstrate Interoperability:
|
||||||||||||||
Test Step | Testing Procedure | Expected Outcomes | Key Milestone Date | Key Milestone | Outcomes | Comment(s) | ||||||||||
1 |
Identify Trading Partner (TP) and coordinate with TP for transmitting immunization records using production data as described in this RWT plan |
|
July, 2025 | |||||||||||||
2 |
Implement bi-directional immunization interface (if interface not already in place) | Validate that immunization interface is functioning as expected | July, 2025 | |||||||||||||
3 |
Production data is requested for all patients on the schedule. Once received, the data is structured and staged. | If production, determine whether an actual patient or a test patient will be used. | ||||||||||||||
4 |
User Verifies the Immunization Received and Reconciles with EHR Data |
|
||||||||||||||
5 |
Create a new immunization record | For one of the patients in step 4, record an immunization in Client EHR. | ||||||||||||||
6 |
Run immunization process to send all updated immuniation for all patients seen in a batch registry process. | Record send functionality and verify logs for successful transmission | ||||||||||||||
7 |
Access registry to verify that immunization data was received. | Verify immunization data was received in registry. | July, 2025 | |||||||||||||
8 |
Access HIE Portal to verify that immunization data was received | Verify immunization data was received in HIE Portal | July, 2025 | |||||||||||||
9 |
Calculate and compile metrics. | Using Log Data calculate the Metrics and presents to User Admin specifics statuses | July, 2025 | |||||||||||||
Attestation
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. |
||||||||||||||||
|
Table of Contents | Associated Certification Criteria: § 170.315(f)(5) Transmission to public health agencies-electronic case reporting |
|||||||||||||||
Measure Description: Create Electronic Case Reports (eCR) for transmission to public health agency based on a specific LOINC, ICD-10 and SNOMED codes entered in patient's encounter. eCR functionality looks up the patient's codes in the table and, if appropriate, sends an eCR message to the health agency. | Justification: We chose to focus on aspects of this criterion that would provide the most patient care value in an actual setting. Public health registries can be very helpful to patient care, epidemiologists and government for identifying disease outbreaks, epidemics and even pandemics. | |||||||||||||||
Metric Description:
|
Standards Implemented: NA | |||||||||||||||
Developer Info:
CloudCraft, LLC 1860 Biddle Road Dover, NC 28526 Care Setting: Ambulatory |
Product Info:
Product Name: CloudCraft Software Product Version: 9 CHPL ID: 15.04.04.3071.Clou.09.01.1.221227 |
Methods Use to Demonstrate Interoperability:
|
||||||||||||||
Test Step | Testing Procedure | Expected Outcomes | Key Milestone Date | Key Milestone | Outcomes | Comment(s) | ||||||||||
1 |
Identify Cloudcraft Client who either:
|
eCR messages are successfully received and processed by public health agency. | July, 2025 | |||||||||||||
2 |
Implement send-only public health interface (if interface not already in place).
|
Functioning eCR interface to public health agency | July, 2025 | |||||||||||||
3 |
Create a patient encounters.
|
Patient registered queued for interface | ||||||||||||||
4 |
Enter lab results through EHR or Lab interface. Make sure LOINC codes correspond to codes present in the Trigger Events table that lists reportable LOINC codes. | Patient queued for interface | ||||||||||||||
5 |
Run eCR process to send to public health agency (assuming process in batch, rather than real-time). | Messages sent to public health agency | ||||||||||||||
6 |
Query agency to verify that public health data was received for patients from step 3 and 4. | Public health successfully processed by agency. | ||||||||||||||
7 |
Calculate and compile metrics. | July, 2025 | ||||||||||||||
Attestation
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. |
||||||||||||||||
|
Table of Contents | Associated Certification Criteria: § 170.315(f)(7) Transmission to public health agencies-health care surveys |
|||||||||||||||
Measure Description: Create health care survey information for electronic transmission. | Justification: We chose to focus on aspects of this criterion that would provide insight into patient experience and feedback. And, provide supervisory board oversight through analytics, providing customer feedback for each board meeting. | |||||||||||||||
Metric Description:
100% of providers configuring a survey will have the ability to configure in the EHR. 100% of the survey questions shall be available for management analytics. 100% of all non-aggregated survey data shall be aggregated on a supervisory board portal, for board oversight. |
Standards Implemented: NA | |||||||||||||||
Developer Info:
CloudCraft, LLC 1860 Biddle Road Dover, NC 28526 Care Setting: Ambulatory |
Product Info:
Product Name: CloudCraft Software Product Version: 9 CHPL ID: 15.04.04.3071.Clou.09.01.1.221227 |
Methods Use to Demonstrate Interoperability: HL7 Standard for CDA | ||||||||||||||
Test Step | Testing Procedure | Expected Outcomes | Key Milestone Date | Key Milestone | Outcomes | Comment(s) | ||||||||||
1 |
Participation in National Hospital Medical Care Survey is voluntary.
|
|
July, 2025 | |||||||||||||
2 |
For a period of time, monitor the system as the below steps(3-5) take place continuously. | Many patient visits will occur during the period of time, generating a sufficient amount of data for calculating the metrics at the end of testing. | ||||||||||||||
3 |
Front desk notifies patients of survey availability |
|
||||||||||||||
4 |
Aggregate and anonymize survey responses. | Responses are deidentified then compiled by location and provider. | ||||||||||||||
5 |
Survey responses are transmitted to CDC via bulk upload for review. | Responses are converted to HL7 CDA documents for transmission. | July, 2025 | |||||||||||||
6 |
Calculate and compile metrics. | July, 2025 | ||||||||||||||
Attestation
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. |
||||||||||||||||
|
Table of Contents | Associated Certification Criteria: § 170.315(g)(7) Application access— patient selection § 170.315(g)(9) Application access— all data request |
|||||||||||||||
Measure Description: Enable a patient's to access their electronic health data through a Personal Health Record (PHR) app on their smartphone. They have had a healthcare encounter with a provider using an EHR that is integrated with the Dynamic FHIR API and Patient Portal modules of ConnectEHR. They would like to view the results from that encounter along with the rest of their electronic health record. | Justification: CMS has a focus on empowering patients by providing them with an electronic copy of their health record. We agree that this is very important for patient satisfaction and improving population health in general. | |||||||||||||||
Metric Description:
|
Standards Implemented:
|
|||||||||||||||
Developer Info:
CloudCraft, LLC 1860 Biddle Road Dover, NC 28526 Care Setting: Ambulatory |
Product Info:
Product Name: CloudCraft Software Product Version: 9 CHPL ID: 15.04.04.3071.Clou.09.01.1.221227 |
Methods Use to Demonstrate Interoperability:
|
||||||||||||||
Test Step | Testing Procedure | Expected Outcomes | Key Milestone Date | Key Milestone | Outcomes | Comment(s) | ||||||||||
1 |
Identify Trading Partner (TP) and coordinate with TP tor providing patients timely access to their ePHI using production data as described in this RWT plan |
|
August, 2025 | |||||||||||||
2 |
Patient A has encounter with care provider who uses EHR described above | Encounter is created and visually confirmed | August, 2025 | |||||||||||||
3 |
Provider captures USCDIv1 data elements in EHR | USCDIv1 data elements are validated in the system | ||||||||||||||
4 |
Provider manually generates Care/Referral Summary C-CDA post-visit or ensures that the EHR generates one automatically | C-CDA is confirmed for the specified patient | ||||||||||||||
5 |
Patient A uses Dynamic Patient Portal login to view clinical information |
|
||||||||||||||
6 |
Patient A uses portal login credentials to log into PHR app | Specific patient ID and token are returned for authentication and data requests | ||||||||||||||
7 |
PHR app displays full set of data for all data categories |
|
August, 2025 | |||||||||||||
8 |
PHR app returns full set of data for a given category | PHR app will display and all data to be displayed for each data category | ||||||||||||||
9 |
PHR app returns data in a computable format using specified standards | Data is confirmed to be in XML or JSON format | ||||||||||||||
10 |
PHR app returns full and accurate data for a specific date and specific date range |
|
||||||||||||||
11 |
Via visual inspection of PHR app, the data is verified to include Assessment, Plan of Treatment and Health concerns are specified as narrative text | Visually validate Assessment Plan of Treatment and Health Concerns narrative text | August, 2025 | |||||||||||||
12 |
Calculate and compile metrics. | August, 2025 | ||||||||||||||
Attestation
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. |
||||||||||||||||
|
Table of Contents | Associated Certification Criteria: § 170.315(g)(10) Standardized API for patient and population services |
|||||||||||||||
Measure Description: Provide a standardized FHIR-based API that supports bulk data requests to provide patients, providers and niche specialty applications to consume patient data enabling improved interoperability, improved patient care and better overall population health. | Justification: We chose to concentrate on the aspects of this criterion that would empower clinicians with flexibility in choosing new and innovative healthcare technology. Historically, it has been difficult for builders of niche applications to access necessary patient demographic and clinical data for smooth, seamless use of their applications. Likewise, clinicians have often felt forced to stick with cumbersome, difficult-to-use EHR technology because of the cost and complexity of migrating their patient data. | |||||||||||||||
Metric Description:
|
Standards Implemented: (SVAP)
|
|||||||||||||||
Developer Info:
CloudCraft, LLC 1860 Biddle Road Dover, NC 28526 Care Setting: Ambulatory |
Product Info:
Product Name: CloudCraft Software Product Version: 9 CHPL ID: 15.04.04.3071.Clou.09.01.1.221227 |
Methods Use to Demonstrate Interoperability:
|
||||||||||||||
Test Step | Testing Procedure | Expected Outcomes | Key Milestone Date | Key Milestone | Outcomes | Comment(s) | ||||||||||
These Test Steps Cover Single Patient API Access |
||||||||||||||||
1 |
Identify Trading Partner (TP) and coordinate with TP for providing patients timely access to their ePHI using production data as described in this RWT plan. |
|
May, 2025 | |||||||||||||
2 |
Patient A has encounter with care provider who uses EHR described above. | Encounter is created and visually confirmed | June, 2025 | |||||||||||||
3 |
Provider captures USCDIv1 data elements in EHR | USCDIv1 data elements are validated in the system | ||||||||||||||
4 |
Provider manually generates Care/Referral Summary C-CDA post-visit or ensures that the EHR generates one automatically. | C-CDA is confirmed for the specified patient | ||||||||||||||
5 |
Patient A uses Dynamic Patient Portal login to view clinical information |
|
||||||||||||||
6 |
Patient A uses portal login credentials to log into PHR app | Specific patient ID and token are returned for authentication and data requests | ||||||||||||||
7 |
PHR app displays full set of data for each data category |
|
July, 2025 | |||||||||||||
8 |
PHR app returns full set of data for a given category | PHR app will display and all data to be displayed for each data category | ||||||||||||||
9 |
PHR app returns data in a computable format using specified standards. | Data is confirmed to be in XML or JSON format | ||||||||||||||
10 |
PHR app returns full and accurate data for a specific date and specific date range |
|
||||||||||||||
11 |
Via visual inspection, the data is verified to include Assessment, Plan of Treatment and Health concerns are specified as narrative text | Visually validate Assessment, Plan of Treatment and Health Concerns narrative text | ||||||||||||||
These Test Steps Cover Care Coordination via 3rd Part App |
||||||||||||||||
1a |
Identify Trading Partner (TP) and coordinate with TP for providing patients timely access to their ePHI using production data as described in this RWT plan. |
|
May, 2025 | |||||||||||||
2a |
Provider logs into app and triggers FHIR API data retrieval |
|
||||||||||||||
3a |
Provider views and validates data in app |
|
June, 2025 | |||||||||||||
These Test Steps Cover Bulk Data for Care Coordination |
||||||||||||||||
1b |
Identify Trading Partner (TP) and coordinate with TP for providing patients timely access to their ePHI using production data as described in this RWT plan. |
|
May, 2025 | |||||||||||||
2b |
Provider logs into app and views patient data |
|
||||||||||||||
3b |
Provider validates data in app |
|
June, 2025 | |||||||||||||
12 |
Calculate and compile metrics | August, 2025 | ||||||||||||||
Attestation
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. |
||||||||||||||||
|