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 measure
USCDI updated certification criteria (and USCDI version)
Result summary
success or challenges in measuring
Date/Timeframe
2
3
Care Coordination
4
§ 170.315(b)(1) Transitions of careTransitions of care - Use Case The use case tests the performance of the certified technology to create Transitions of Care/referral summaries, CCDA, as well as send and receive files, using edge protocal, to promote interoperability. Use case is an effective method to appropriately test the performance and functionality described.1. Login into DOX with the user who has privileges to export CCDA.
2. Select menu items Tools-->Export CCDA
3. Search and select the patient for whom need to generate CCDA file (Patient can be searched with last name/first name/dob/phone number or combinations of these attributes)
4. Select the destination path to generate CCDA
5. Finally click on "Generate" will export the required patient CCDA file to the destination path. For Receive - at step 2 above- click Import CCCA option. Select patient. On next pop up - click Import CCDA. When import is complete- click View File button, to view CCDA Providers' use of the Transition of Care component will be observed for successful creation of care/referral summaries, CCDA file and all its components, and users ability to both successfully send and receive files to promote interoperability.
This test methodology will appropriately test the performance and the conformance of the implementation. 		Medical Office Care Settings will be used. This setting tests deployment and tracking of documentation and funtionality within and outside of the medical office setting and the environment of its intended use. The medical office setting will be used for all real world testing described. It is expected that Real World Testing shows Transitions of Care functions successfully, is conformant/compliant to § 170.315(b)(1) certification criteria. Authorized users can successfully create transitions of care/referral summaries, CCDA, as well as send and receive files, without errors. Users will be able to exchange electronic health information (EHI), as well as send, receive and use 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.USCDI v1Cures Update12/27/2022 : N/ATransitions of Careb1 – USCDI v1 Key Finding: DOX monitored independent use of certification criteria § 170.315(b)(1) including standards updates as noted in column G and found that users/customers used the feature on their own minimally, 1 use per year to meet minimal requirements. DOX contacted customers and queried as to why features ws used only minimaly and resistent to using features and stated attempting to use feature " slowed them down too much and required too much additional work." So DOX Saw consideratble resistance by users/ customers to change/acceptance of technology. Testing was performed as described under testing methodology (Column D), quarterly, as described under milestongs. Results and data produced during Real World Testing were assessed and revealed- Transitions of Care functions successfully, is conformant/compliant to § 170.315(b)(1) including standards updates as noted in column G, for 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 send, receive and use in the certified health IT and in the Medical Office care and practice settings for which it is marketed for use. Issues/ Error rates was 0 of the 13 performed. This number will be used as the base line for the initial testing year and efforts will try to improve this number for testing next year (2025).Issues/ Error rates was 0 of the 11 performed. This number will be used as the new standard and efforts will try to improve this number for testing next year (2025).Q1 4/1/24 for ( 1/1/24- 3/31/24) Q2 7/1/24 for ( 4/1/24- 6/30/24) Q3 10/1/24 for ( 7/1/24- 9/30/24) Q4 1/1/25 for ( 10/1/25- 12/31/24)
5
6
7
§ 170.315(b)(9) Care planCare plan - Use Case The use case tests the performance of the certified technology to create a Care Plan, to promote interoperability. Use case is an effective method to appropriately test the performance and functionality described. 1. Login into DOX with the user and select menu items Tools --> Import Patient Files
2. Select option CCDA and Import CCDA file from external data patient file into DOX Application and Click on Attach Button.
3. Imported attached CCDA patient data file will see in Refferal Summary Tab.
4. Select Tab Refferal Summary.
5. We can see the Download Date, Referral Date ,Referral From and User Name columns.
7. By clicking on View Button to view selecting sections options and depending upon the Order of sections options to view the referral Summary data.
8. We can view Patient Info,Contact info and all information related to
ALLERGIES AND ADVERSE REACTIONS ,MEDICATIONS,PROBLEMS,REASON FOR REFERRAL,REASON FOR VISIT,PROCEDURES,FUNCTIONAL STATUS,MENTAL STATUS,IMMUNIZATIONS,
VITAL SIGNS,RESULTS,SOCIAL HISTORY,TREATMENT PLAN,FAMILY HISTORY,INSTRUCTIONS,Implants,Health Concerns and Goals Section. Note- click any component to edit/change or delete entire component, as desired by user. 9. To create care plan, at step 2 above, select option to Create Care Plan. Field will display to allow user to select desired components. Then click Generate button. File will be generated for view of created Care Plan. Providers' use of the component will be observed for successful creation of Care Plan, including Record, Change, Access, Create, and Receive Care Plan to promote interoperability.
This test methodology will appropriately test the performance and the conformance of the implementation. 		All Medical Office Care Settings will be used for testing case as described previouslyIt is expected that Real World Testing shows the Create Care Plan functions successfully, is conformant/compliant to § 170.315(b)(9) certification criteria. Authorized users can successfully create Care Plan Record, Change, Access, Create and Receive, without errors. Users will be able to create care plan and its requirements 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.
Key Finding: DOX monitored independent use of certification criteria § 170.315(b)(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(b)(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- Creation of Care Plan functions successfully, is conformant/compliant to § 170.315(b)(9) certification criteria. Authorized users can successfully create care plan as intended and as anticipated. Users were able to exchange electronic health information (EHI) successfully, as well as createe a care plans 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 (2025).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 (2025).Q1 4/1/24 for ( 1/1/24- 3/31/24) Q2 7/1/24 for ( 4/1/24- 6/30/24) Q3 10/1/24 for ( 7/1/24- 9/30/24) Q4 1/1/25 for ( 10/1/25- 12/31/24)
8
9
§ 170.315(b)(10) Data exportData ExportThe testing methodology (column D) describes, tests and validates the performance of the certified technology to create Data Export, to promote interoperability , meets the criteria for this measure and is functional for healthcare providers. The described Methodology is an effective method to appropriately test the performance and real world functionality for healthcare providers and users of the application. 1. Login into DOX with the user who has privileges to export CCDA. 2. Select menu items Tools--> Patient Portability 3. Search and select the patient for whom need to generate CCDA file for multiple patients (Patient can be searched with lastname/firstname/dob/phonenumber or combinations of these attributes). Then select all desired elements, full chart note or All chart notes. Be sure to include date or date range. 4. Select the destination path to generate CCDA. 5. Finally click on "Generate" will export the requested CCDA file to the destination path. Providers' use of the Data Export component will be observed for successful Export of Data and all its required components, to promote interoperability.
This test methodology will appropriately test the performance and the conformance of the implementation.
Medical Office Care Settings as described previously
It is expected that Real World Testing shows Export data functions successfully, is conformant/compliant to § 170.315(b)(10) certification criteria. Authorized users can successfully export data, without errors. Users will be able to use the feature in the certified health IT and in the care and practice settings for which it is marketed for use. Error rates will be tracked across these functions and trended over time. N/A Key Finding: DOX monitored independent use of certification criteria § 170.315(b)(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(b)(10) 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- B10 Data Export functions successfully, is conformant/compliant to § 170.315(b)(10) certification criteria. Authorized users can successfully create B10 Data Export as intended and as anticipated. Users were able to exchange electronic health information (EHI) successfully, as well as create B10 Data Export 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 (2025).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 (2025).Q1 4/1/24 for ( 1/1/24- 3/31/24) Q2 7/1/24 for ( 4/1/24- 6/30/24) Q3 10/1/24 for ( 7/1/24- 9/30/24) Q4 1/1/25 for ( 10/1/25- 12/31/24)
10
11
12
13
14
15
16
17
Clinical Quality Measures
18
§ 170.315(c)(1) Clinical Quality Measures (CQMs) - Record and exportClinical Quality Measures (CQMs) - Record and export - Use Case The use case tests the performance of the certified technology to create Clinical Quality Measures – Record and Export, to promote interoperability. Use case is an effective method to appropriately test the performance and functionality described. 1. Login into DOX with the user.
2. Select menu items Tools--> CQM - Record + Export
3. CQM data is recorded to as necessary to calculate each CQM. Then click Calculate/View button. CQM report will generate with required details ( note #6 below)
4. To Export QRDA I and QRDA III from DOX , select Menu Item from Tools --> PQRI.
5. From PQRI to Export report - select Report Name, Reporting Period,Provider,Location ,Start and End Date based on options selections we can view Patients data.
6. In Consolidate Tab we can view pie chart graph with Denominator and Numerator Count with Bench Mark.
7. In Detailed Tab we can see Patients details with Staus,Exclusion and Exception. Providers' use of the CQMs- record and export component will be observed for successful creation of Clinical Quality Measures – Record and Export to promote interoperability.
This test methodology will appropriately test the performance and the conformance of the implementation. 		All Medical Office Care Settings will be used for testing case as described previously It is expected that Real World Testing shows Clinical Quality Measures – Record and Export functionality is successful and is conformant/compliant to § 170.315(c)(1) certification criteria. Authorized users can successfully use Clinical Quality Measures – Record and Export without errors. Users will be able to record and export CQMs 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. Key Finding: DOX monitored independent use of certification criteria § 170.315(c)(1) 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(c)(1) 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- Clinical Quality Measures, Record and Export functions successfully, is conformant/compliant to § 170.315(c)(1) certification criteria. Authorized users can successfully record and export clinical quality measues. Users were able to exchange electronic health information (EHI) successfully, record and export CQMs 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 (2025).Issues/ Error rates was 0 of the 4 performed. This number will be used as the new base line for the testing year and efforts will try to improve this number for testing next year (2025).Q1 4/1/24 for ( 1/1/24- 3/31/24) Q2 7/1/24 for ( 4/1/24- 6/30/24) Q3 10/1/24 for ( 7/1/24- 9/30/24) Q4 1/1/25 for ( 10/1/25- 12/31/24)
19
20
21
22
23
24
25
26
27
§ 170.315(c)(2) Clinical quality measures (CQMs) - import and calculateClinical quality measures (CQMs) - import and calculate - Use Case The use case tests the performance of the certified technology to create Clinical Quality Measures – Import and Calculate, to promote interoperability. Use case is an effective method to appropriately test the performance and functionality described. 1. Qualified user will be logged into the DOX system.
2. Select menu items Tools--> Import QRDA
3. From Import QRDA select QRDA file path and to read CQM Patient data into DOX Application with all report Types.
4. To Generate QRDA I and QRDA III from DOX , select Menu Item from Tools --> PQRI.
5. From PQRI to view report - select Report Name, Reporting Period,Provider,Location ,Start and End Date based on options selections we can view Patients data.
6. In Consolidate Tab we can view pie chart graph with Denominator and Numerator Count with Bench Mark.
7. In Detailed Tab we can see Patients details with Staus, Exclusion and Exception. Providers' use of the CQM- import and calculate component will be observed for successful creation of Clinical Quality Measures – Import and calculate, to promote interoperability.
This test methodology will appropriately test the performance and the conformance of the implementation. 		All Medical Office Care Settings will be used for testing case as described previously It is expected that Real World Testing shows the Clinical Quality Measures – Import and Calculate functions successfully, and is conformant/compliant to § 170.315(c)(2) certification criteria. Authorized users can successfully create Clinical Quality Measures – Import and Calculate, without errors. Users will be able to successfully use the CQMs- import and calculate 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. Key Finding: DOX monitored independent use of certification criteria § 170.315(c)(2) 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(c)(2) 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- Clinical Quality Measures- Import and Calculate functions successfully, is conformant/compliant to § 170.315(c)(2) certification criteria. Authorized users can successfully import and calculate CQMs. Users were able to exchange electronic health information (EHI) successfully, as well as import and calculate CQMs 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 (2025).Issues/ Error rates was 0 of the 4 performed. This number will be used as the base line for the initial testing year and efforts will try to improve this number for testing next year (2025).Q1 4/1/24 for ( 1/1/24- 3/31/24) Q2 7/1/24 for ( 4/1/24- 6/30/24) Q3 10/1/24 for ( 7/1/24- 9/30/24) Q4 1/1/25 for ( 10/1/25- 12/31/24)
28
29
30
31
32
33
34
35
36
§ 170.315(c)(3) Clinical quality measures (CQMs) - reportClinical quality measures (CQMs) - report - Use Case The use case tests the performance of the certified technology to create Clinical Quality Measures – Report, to promote interoperability. Use case is an effective method to appropriately test the performance and functionality described. 1. Login into DOX with the user.
2. Select menu items Tools--> QRDA
3. From Import QRDA select QRDA file path and to read CQM Patient data into DOX Application with all report Types in to Dox Application.
4. To Generate QRDA I and QRDA III from DOX application , select Menu Item from Tools --> CQMs.
5. From CQM to view report - select Report Name, Reporting Period,Provider,Location ,Start and End Date based on options selections we can view Patients data.
6. In Consolidate Tab we can view pie chart graph with Denominator and Numerator Count with Bench Mark.
7. In Detailed Tab we can see Patients details with Staus,Exclusion and Exception. 8. Check box for desired file type QRDA cat 3 or QRDa cat 1 file, then click Generate. Desired file type will be generated. To transmit created Cat3 or Cat1 file - select Export button. On new pop up- select desired file path, then click Send button. Providers' use of the CQMs- report component will be observed for successful creation of Clinical Quality Measures – Report to promote interoperability.
This test methodology will appropriately test the performance and the conformance of the implementation. 		All Medical Office Care Settings will be used for testing case as described previously It is expected that Real World Testing shows the Clinical Quality Measures – Report feature functions successfully, and is conformant/compliant to § 170.315(c)(3) certification criteria. Authorized users can successfully create Clinical Quality Measures – Report, without errors. Users will be able to create and report CQMs 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. 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- Clinical Quality Measure- Report functions successfully, is conformant/compliant to § 170.315(c)(3) certification criteria. Authorized users can successfully create and report CQMs. Users were able to exchange electronic health information (EHI) successfully, as well as create and report CQMs in the Medical Office care and practice settings for which it is marketed for use. Issues/ Error rates was 0 of the 54 performed. This number will be used as the new base line and efforts will try to improve this number for testing next year (2025).Issues/ Error rates was 0 of the 54 performed. This number will be used as the new base line and efforts will try to improve this number for testing next year (2025).Q1 4/1/24 for ( 1/1/24- 3/31/24) Q2 7/1/24 for ( 4/1/24- 6/30/24) Q3 10/1/24 for ( 7/1/24- 9/30/24) Q4 1/1/25 for ( 10/1/25- 12/31/24)
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
Electronic Exchange
52
§ 170.315(h)(1) Direct ProjectDirect Project - Use Case The use case tests the performance of the certified technology in Direct Project functionality, to promote interoperability. Use case is an effective method to appropriately test the performance and functionality described.
1. Login into DOX with the user.
2. Select menu items Tools--> Export CCDA --> EMR Direct
3. Search and select the patient for whom need to generate CCDA file (Patient can be searched with lastname/firstname/dob/phonenumber or cominations of these attributes)
4. Select the destination path to generate CCDA and to send mail using EMR Direct messaging in XML or PDF format of CCDA file.
5. To View the Mails in DOXPA that are received from EMR Direct Select menu items Tools-->EMR Direct .
6. From EMR Direct click on Invoke EMR Direct URL will open from DOXPA and login EMR Direct and we can see sent mails. Providers' use of the Direct Project component will be observed for success of Direct Project, to promote interoperability.
This test methodology will appropriately test the performance and the conformance of the implementation.
All Medical Office Care Settings will be used for testing case as described previously It is expected that Real World Testing shows Direct Project functions successfully, is conformant/compliant to § 170.315(h)(1) certification criteria. Authorized users can successfully use Direct Project, without errors. Users will be able to use Direct Project and all its 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. Key Finding: DOX monitored independent use of certification criteria § 170.315(h)(1) 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(h)(1) certifcation criteria/ feature. Testing was pe5formed as described under testing methodology (Column D), quarterly, as described under milestones. Results and data produced during Real World Testing were assessed and revealed- Direct Project functions successfully, is conformant/compliant to § 170.315(h)(1) certification criteria. Authorized users can successfully perform electronic exchange, direct project functionality. Users were able to exchange electronic health information (EHI), direct project successfully 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 (2024).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 (2025).Q1 4/1/24 for ( 1/1/24- 3/31/24) Q2 7/1/24 for ( 4/1/24- 6/30/24) Q3 10/1/24 for ( 7/1/24- 9/30/24) Q4 1/1/25 for ( 10/1/25- 12/31/24)
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
Application Programming Interfaces
72
§ 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 will be used for testing case as described previously 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. 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 (2025).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 (2025).Q1 4/1/24 for ( 1/1/24- 3/31/24) Q2 7/1/24 for ( 4/1/24- 6/30/24) Q3 10/1/24 for ( 7/1/24- 9/30/24) Q4 1/1/25 for ( 10/1/25- 12/31/24)
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
§ 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 will be used for testing case as described previously 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. USCDI v1Cures Update12/27/2022 : N/AApplication Access- all data requestg9 – USCDI v1 Key Finding: DOX monitored independent use of certification criteria § 170.315(g)(9) with standards updates as listed in column G 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)(9) certifcation criteria/ feature with new standards described in column G. 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 (2025).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 (2025).Q1 4/1/24 for ( 1/1/24- 3/31/24) Q2 7/1/24 for ( 4/1/24- 6/30/24) Q3 10/1/24 for ( 7/1/24- 9/30/24) Q4 1/1/25 for ( 10/1/25- 12/31/24)
90
91
92
§ 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 will be used for testing case as described previously
 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. 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), 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 (2025).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 (2025).Q1 4/1/24 for ( 1/1/24- 3/31/24) Q2 7/1/24 for ( 4/1/24- 6/30/24) Q3 10/1/24 for ( 7/1/24- 9/30/24) Q4 1/1/25 for ( 10/1/25- 12/31/24)
93
2. From DOX External API Data Receiver search patient with lastname/firstname/dob/phonenumber or cominations of these attributes and select download path.
94
3. We can Select any one of Data Type "All data", "Chart Note(s)", or "Selected Date" Options.
95
4.By selecting "All data" we can view the Helath Summary data with
96
 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
97
 APPOINTMENTS,PATIENT NAME,DOB,GENDER,RACE,ETHNICITY,LANGUAGE,VISIT INFORMATION and ADDRESS.
98
5.Click on "Get Appointments" and we can see the list of Appointments with Appt Datetime, Provider, Location, AccessView, Viewed Time and Downoaded Time.
99
6.Select one from Appointment list and click on Icon button we can view the Health Summary details depending upon the sections options.
100
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.