ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
Associated Certification Criteria
Measurement/ Metric
JustificationTesting MethodologyCare SettingExpected outcomes
Standards Updates and version
Method used for standard update
Date of Standard Update Notification ONC ACB : Customers
Conformance measureResult summary
success or challenges in measuring
Date/Timeframe
2
3
Application Programming Interfaces
4
§ 170.315(g)(7) Application access - patient selectionApplication access - patient selection - Use Case The use case tests the performance of the certified technology to facilitate Application Access- patient selection, to promote interoperability. Use case is an effective method to appropriately test the performance and functionality described. 1. Login into DOX External API Data Receiver with the user who has given an access to Data Export settings from FO Menu security.
2. From DOX External API Data Receiver -search patient with lastname/firstname/dob/phonenumber or cominations of these attributes and select download path.
3. We can Select any one of Data Type "All data" and "Select Date" Options, as desired by user.
4.By selecting "All data" we can view the Health Summary data with
ALLERGIES AND ADVERSE REACTIONS ,MEDICATIONS,PROBLEMS,REASON FOR REFERRAL,REASON FOR VISIT,PROCEDURES,CLINICAL INSTRUCTIONS,FUNCTIONAL STATUS,MENTAL STATUS,IMMUNIZATIONS, VITAL SIGNS,PLAN OF CARE,SOCIAL HISTORY,ADMINISTERED MEDICATIONS,FAMILY HISTORY,IMPLANTS,HEALTH CONCERNS AND FUNCTIONAL , COGNITIVE STATUS
APPOINTMENTS,PATIENT NAME,DOB,GENDER,RACE,ETHNICITY,LANGUAGE,VISIT INFORMATION and ADDRESS.
5.Click on "Get Appointments" and we can see the list of Appointments with Appt Datetime, Provider, Location, AccessView, Viewed Time and Downoaded Time.
6.Select one from Appointment list and click on Icon button we can view the Health Summary details depending upon the sections options.
7.Select "Export to PDF" or "Excel" file to local folder with data Provider, Location, Measuring Period, PatientID, Patient Name, DOB, Sex, Phone/Email, Status and Patient Status. 8 .Click Details button to access API syntax and interaction descriptions documentation. Providers' use of the Application Access- patient selection component will be observed for success of Application Access- Patient Selection, to promote interoperability.
This test methodology will appropriately test the performance and the conformance of the implementation.
All Medical Office Care Settings were used for testing case It is expected that Real World Testing shows the Application Access - Patient Selection functions successfully, is conformant/compliant to § 170.315(g)(7) certification criteria. Authorized users can successfully use Application Access - Patient Selection functionality, without errors. Users will be able to use Access Application and Patient Selection functionality in the certified health IT and in the care and practice settings for which it is marketed for use. Issues/ Error rates will be tracked across these functions as part of a base line for the initial testing year. NANANANA Key Finding: DOX monitored independent use of certification criteria § 170.315(g)(7) and found that no users/customers used the feature on their own. DOX contacted customers and queried as to why features were not used- customers were resistent to using features and stated they " slowed them down too much and required too much additional work." So DOX Saw consideratble resistance by users/ customers to change/acceptance of technology. DOX did assist/ walk 1 users/ customers through § 170.315(g)(7) certifcation criteria/ feature. Testing was performed as described under testing methodology (Column D), quarterly, as described under milestones. Results and data produced during Real World Testing were assessed and revealed- Application access- patient selection functions successfully, is conformant/compliant to § 170.315(g)(7) certification criteria. Authorized users can successfully perform Appication access and select patient functionality. Users were able to Access the application and perform patient selection functionaity in the Medical Office care and practice settings for which it is marketed for use. Issues/ Error rates was 0 of the 4 performed. This number will be used as the new base line and efforts will try to improve this number for testing next year (2026).Issues/ Error rates was 0 of the 4 performed. This number will be used as the new base line and efforts will try to improve this number for testing next year (2026).Q1 4/1/25 for ( 1/1/25- 3/31/25) Q2 7/1/25 for ( 4/1/25- 6/30/25) Q3 10/1/25 for ( 7/1/25- 9/30/25) Q4 1/1/26 for ( 10/1/25- 12/31/25)
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
§ 170.315(g)(9) Application access- all data requestApplication access- all data request - Use Case The use case tests the performance of the certified technology to create Application Access- All Data Request, to promote interoperability. Use case is an effective method to appropriately test the performance and functionality described. 1. Login into DOX External API Data Receiver with the user who has given an access to Data Export settings from FO Menu security
2. From DOX External API Data Receiver search patient with lastname/firstname/dob/phonenumber or cominations of these attributes and select download path.
3. We can Select any one of Data Type "All data" or "Selected Date" Options.
4.By selecting "All data" we can view the Health Summary data with
ALLERGIES AND ADVERSE REACTIONS ,MEDICATIONS,PROBLEMS,REASON FOR REFERRAL,REASON FOR VISIT,PROCEDURES,CLINICAL INSTRUCTIONS,FUNCTIONAL STATUS,MENTAL STATUS,IMMUNIZATIONS, VITAL SIGNS,PLAN OF CARE,SOCIAL HISTORY,ADMINISTERED MEDICATIONS,FAMILY HISTORY,IMPLANTS,HEALTH CONCERNS AND FUNCTIONAL , COGNITIVE STATUS
APPOINTMENTS,PATIENT NAME,DOB,GENDER,RACE,ETHNICITY,LANGUAGE,VISIT INFORMATION and ADDRESS.
5.Click on "Get Appointments" and we can see the list of Appointments with Appt Datetime, Provider, Location, AccessView, Viewed Time and Downoaded Time.
6.Select one from Appointment list and click on Icon button we can view the Health Summary details depending upon the sections options.
7.Select "Export to PDF" or "Excel" file to local folder with data Provider, Location, Measuring Period, PatientID, Patient Name, DOB, Sex, Phone/Email, Status and Patient Status. 8..Click Details button to access API syntax and interaction descriptions documentation. Providers' use of the Application Access- all data request component will be observed for success , and to promote interoperability.
This test methodology will appropriately test the performance and the conformance of the implementation. 		All Medical Office Care Settings were used for testing case It is expected that Real World Testing shows the Application Access-All Data Request functions successfully, is conformant/compliant to § 170.315(g)(9) certification criteria. Authorized users can successfully use Application Access- All Data Request functionality, without errors. Users will be able to successfully Access Application and Request All Data, in the certified health IT and in the care and practice settings for which it is marketed for use. Issues/ Error rates will be tracked across these functions as part of a base line for the initial testing year. NANANANA Key Finding: DOX monitored independent use of certification criteria § 170.315(g)(9) and found that no users/customers used the feature on their own. DOX contacted customers and queried as to why features were not used- customers were resistent to using features and stated they " slowed them down too much and required too much additional work." So DOX Saw considerable resistance by users/ customers to change/acceptance of technology. DOX did assist/ walk 1 users/ customers through § 170.315(g)(9) certifcation criteria/ feature. Testing was performed as described under testing methodology (Column D), quarterly, as described under milestones. Results and data produced during Real World Testing were assessed and revealed- Appication Access- All Data Request functions successfully, is conformant/compliant to § 170.315(g)(9) certification criteria. Authorized users can successfully create transitions of care/referral summaries, CCDA, as well as send and receive files. Users were able to exchange electronic health information (EHI) successfully, as well as access the application and request all data in the Medical Office care and practice settings for which it is marketed for use. Issues/ Error rates was 0 of the 4 performed. This number will be used as the new base line and efforts will try to improve this number for testing next year (2026).Issues/ Error rates was 0 of the 4 performed. This number will be used as the new base line and efforts will try to improve this number for testing next year (2026).Q1 4/1/25 for ( 1/1/25- 3/31/25) Q2 7/1/25 for ( 4/1/25- 6/30/25) Q3 10/1/25 for ( 7/1/25- 9/30/25) Q4 1/1/26 for ( 10/1/25- 12/31/25)
22
23
24
§ 170.315(g)(10) Application Programming Interface ( API ) - Application access — Standardized API for patient and population services. Application access — Standardized API for patient and population services. Use CaseThe use case tests the performance of the certified technology to create Application Programming Interface (API), access — Standardized API for patient and population services, to promote interoperability. Use case is an effective method to appropriately test the performance and functionality described. 1. Login into DOX External API Data Receiver with the user who has given an access to Data Export settings from FO Menu security
All Medical Office Care Settings were used for testing case
It is expected that Real World Testing shows the Application Programming Interface (API) functions successfully, is conformant/compliant to § 170.315(g)(10) certification criteria. Authorized users can successfully use Application Programming Interface ( API ) functionality, without errors. Users will be able to successfully Access Application and Request All Data, in the certified health IT and in the care and practice settings for which it is marketed for use. Issues/ Error rates will be tracked across these functions as part of a base line for the initial testing year. NANANANA Key Finding: DOX monitored independent use of certification criteria § 170.315(g)(10) and found that no users/customers used the feature on their own. DOX contacted customers and queried as to why features were not used- customers were resistent to using features and stated they " slowed them down too much and required too much additional work." So DOX Saw considerable resistance by users/ customers to change/acceptance of technology. DOX did assist/ walk 1 users/ customers through § 170.315(g)(10) certifcation criteria/ feature. Testing was performed as described under testing methodology (Column D) with Health Samurai relied upon software, quarterly, as described under milestones. Results and data produced during Real World Testing were assessed and revealed- Application Programming Interface (API) functions successfully, is conformant/compliant to § 170.315(g)(10) certification criteria. Authorized users can successfully create transitions of care/referral summaries, CCDA, as well as send and receive files. Users were able to exchange electronic health information (EHI) and APIs functioned successfully, as well as access the application and request all data in the Medical Office care and practice settings for which it is marketed for use. Issues/ Error rates was 0 of the 4 performed. This number will be used as the initial base line for testing and efforts will try to improve this number for testing next year (2026).Issues/ Error rates was 0 of the 4 performed. This number will be used as the initial base line for testing and efforts will try to improve this number for testing next year (2026).Q1 4/1/25 for ( 1/1/25- 3/31/25) Q2 7/1/25 for ( 4/1/25- 6/30/25) Q3 10/1/25 for ( 7/1/25- 9/30/25) Q4 1/1/26 for ( 10/1/25- 12/31/25)
25
2. From DOX External API Data Receiver search patient with lastname/firstname/dob/phonenumber or cominations of these attributes and select download path.
26
3. We can Select any one of Data Type "All data", "Chart Note(s)", or "Selected Date" Options.
27
4.By selecting "All data" we can view the Helath Summary data with
28
 ALLERGIES AND ADVERSE REACTIONS ,MEDICATIONS,PROBLEMS,REASON FOR REFERRAL,REASON FOR VISIT,PROCEDURES,CLINICAL INSTRUCTIONS,FUNCTIONAL STATUS,MENTAL STATUS,IMMUNIZATIONS, VITAL SIGNS,PLAN OF CARE,SOCIAL HISTORY,ADMINISTERED MEDICATIONS,FAMILY HISTORY,IMPLANTS,HEALTH CONCERNS AND FUNCTIONAL , COGNITIVE STATUS
29
 APPOINTMENTS,PATIENT NAME,DOB,GENDER,RACE,ETHNICITY,LANGUAGE,VISIT INFORMATION and ADDRESS.
30
5.Click on "Get Appointments" and we can see the list of Appointments with Appt Datetime, Provider, Location, AccessView, Viewed Time and Downoaded Time.
31
6.Select one from Appointment list and click on Icon button we can view the Health Summary details depending upon the sections options.
32
7.Select "Export to PDF" or "Excel" file to local folder with data Provider, Location, Measuring Period, PatientID, Patient Name, DOB, Sex, Phone/Email, Status and Patient Status. 8..Click Details button to access API syntax and interaction descriptions documentation. Providers' use of the Application Access- all data request component will be observed for success , and to promote interoperability.
33
 This test methodology will appropriately test the performance and the conformance of the implementation.
34
RESULTS SUMMARY 2025 Summary of Testing Methods and key Findings: DOX EMR completed all testing methods as use cases and as described for each criteria in Test Medthodology column D. Key Finding: DOX monitored the independent use of all the certification criteria required by ONC for Real World Testing (All cirteria tested are listed in column A). DOX found that no users/customers used the features on their own. DOX contacted customers and queried as to why features were not used- customers were resistent to using features and stated they " slowed them down too much and required too much additional work." So DOX Saw consideratble resistance by users/ customers to change/resistance to acceptance of technology. DOX did assist/ walk 1 users/ customers through test use of all certifcation criteria/ features. Testing was performed as described under testing methodology (Column D), quarterly, as described under milestones. Results and data produced during Real World Testing were assessed and revealed- All criteria functioned successfully, were conformant/compliant to certification criteria for which they were created. Authorized users successfully performed test of functionality for each criteria and all criteria functionality were met without errors or issues and in the Medical Office care and practice settings for which it is marketed for use. Issues/ Error rates was 0 on all performed criteria. This number will be used as the new base line and efforts will try to improve this number for testing next year (2026).Issues/ Error rates were performed as descibed for each measure above. These numbers will be used as the base line for testing and efforts will try to improve this number for testing next year (2026).Q1 4/1/25 for ( 1/1/25- 3/31/25) Q2 7/1/25 for ( 4/1/25- 6/30/25) Q3 10/1/25 for ( 7/1/25- 9/30/25) Q4 1/1/26 for ( 10/1/25- 12/31/25)
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100