Difference between revisions of "Safety-enhanced design (MU3))"
From OpenEMR Project Wiki
Bradymiller (talk | contribs) |
|||
| (17 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
= Overview = | = Overview = | ||
:The first usability testing was completed by the 2022 Cohort of the Professional Certificate in Health Information Technology at Columbia University for the a1, a2, a5, a9, a14 certification criteria. | :The first usability testing was completed by the 2022 Cohort of the Professional Certificate in Health Information Technology at Columbia University for the a1, a2, a5, a9, a14 certification criteria. | ||
: | :A 2024 addendum to the usability study is being conducted by OpenEMR for the b11 certification criteria. | ||
= Usability Test Report = | = Usability Test Report = | ||
:[[Media:OpenEMR Usability Report.pdf|OpenEMR Usability Test Report]] | :[[Media:OpenEMR Usability Report.pdf|OpenEMR Usability Test Report - 2022]] | ||
= UCD Process = | = UCD Process = | ||
| Line 15: | Line 15: | ||
:*a9: Clinical decision support (2022 task 1) (completed in 2022 and hidden below) | :*a9: Clinical decision support (2022 task 1) (completed in 2022 and hidden below) | ||
:*a14: Implantable device list (2022 task 3) (completed in 2022 and hidden below) | :*a14: Implantable device list (2022 task 3) (completed in 2022 and hidden below) | ||
:*'''b11: Decision Intervention | :*'''b11: Decision Support Intervention 2024 addendum (2024 task 1,2,3)''' | ||
= Research = | = Research = | ||
| Line 30: | Line 30: | ||
* These are duplicate official testing demos that contain 1 patient (Ed Smith). Official testing demos completely reset daily at around 1:00 am pacific time; when official testing demos completely reset, they are rebuilt on top of most recent codebase. Official testing demos use private credentials (ie. public will not be able to access them) that are only known to the official testers. | * These are duplicate official testing demos that contain 1 patient (Ed Smith). Official testing demos completely reset daily at around 1:00 am pacific time; when official testing demos completely reset, they are rebuilt on top of most recent codebase. Official testing demos use private credentials (ie. public will not be able to access them) that are only known to the official testers. | ||
<!-- bug here in the actual first | <!-- bug here in the actual first demo without a letter when opening patient summary screen, so will not use it --> | ||
:* [https://eight.openemr.io/a/openemr/index.php Testing Demo A] | :* [https://eight.openemr.io/a/openemr/index.php Testing Demo A] | ||
:* [https://eight.openemr.io/b/openemr/index.php Testing Demo B] | :* [https://eight.openemr.io/b/openemr/index.php Testing Demo B] | ||
| Line 41: | Line 41: | ||
= Usability training demos = | = Usability training demos = | ||
* The point of these training demos is to allow training by multiple users, which pick Ed Smith patient to run through the below training guides on. Training demos completely reset daily at around 1:00 am pacific time; when training demos completely reset, they are rebuilt on top of most recent codebase. Training demos use public credentials, which are username:admin password:Administrator1! | * The point of these training demos is to allow training by multiple users, which pick Ed Smith patient to run through the below training guides on. Training demos completely reset daily at around 1:00 am pacific time; when training demos completely reset, they are rebuilt on top of most recent codebase. Training demos use public credentials, which are username:admin password:Administrator1! | ||
<!-- bug here in the actual first | <!-- bug here in the actual first demo without a letter when opening patient summary screen, so will not use it --> | ||
:* [https://seven.openemr.io/a/openemr/index.php Training Demo A] | :* [https://seven.openemr.io/a/openemr/index.php Training Demo A] | ||
:* [https://seven.openemr.io/b/openemr/index.php Training Demo B] | :* [https://seven.openemr.io/b/openemr/index.php Training Demo B] | ||
| Line 51: | Line 51: | ||
= Usability testing scenario = | = Usability testing scenario = | ||
:* Ed Smith is a patient in the user's clinic. In this scenario, the user will ' | :* Ed Smith is a patient in the user's clinic. In this scenario, the user will 'update Prostate Cancer Screening rule to explain the rule's usage of patient's biological birth sex', 'provide rule feedback on incorrect application of Pap Smear rule for Ed Smith due to incorrect biological birth sex', and 'update 3rd party decision support intervention source attribute field information'. | ||
:* The following is the testing guide that will be used during testing by the users: [[Usability Testing Guide]] | :* The following is the testing guide that will be used during testing by the users: [[Usability Testing Guide]] | ||
| Line 115: | Line 115: | ||
--> | --> | ||
==Task 1: View and update Decision Intervention | ==Task 1: View and update Decision Support Intervention source attribute information.== | ||
* Test: | * Test: | ||
:* Update Prostate Cancer Screening rule to explain the rule's usage of patient's | :* Update Prostate Cancer Screening rule to explain the rule's usage of patient's biological birth sex. | ||
* Scenario: | * Scenario: | ||
:* The OpenEMR internal CDR is missing source attribute information on how it's Prostate Cancer Screening rule is using the patient's biological birth sex information in its rule calculations. I need to update the source attribute information for this rule to explain that the sex data point is used to determine if the patient is male and should be screened for prostate cancer. This will help clinicians make informed decisions as to the efficacy and safety of the rule. | :* The OpenEMR internal CDR is missing source attribute information on how it's Prostate Cancer Screening rule is using the patient's biological birth sex information in its rule calculations. I need to update the source attribute information for this rule to explain that the sex data point is used to determine if the patient is male and should be screened for prostate cancer. This will help clinicians make informed decisions as to the efficacy and safety of the rule. | ||
| Line 123: | Line 123: | ||
::[[File:task1-1.png|600px|none|thumb|Enter 'Smith' in patient selector at top right and then click the search icon/button.]] | ::[[File:task1-1.png|600px|none|thumb|Enter 'Smith' in patient selector at top right and then click the search icon/button.]] | ||
::[[File:task1-2.png|600px|none|thumb|Click the 'Smith, Ed' patient.]] | ::[[File:task1-2.png|600px|none|thumb|Click the 'Smith, Ed' patient.]] | ||
::[[File:Task5_Step3_InfoIcon.png|600px|none|thumb|Under Clinical Reminders | ::[[File:Task5_Step3_InfoIcon.png|600px|none|thumb|Under Clinical Reminders, click the info icon Past Due question mark on the far right for 'Assessment: Prostate Cancer Screening']] | ||
::[[File:Task5_Step4_FindPatientAttribute.png|600px|none|thumb|Find Patient's Sex source attribute information]] | ::[[File:Task5_Step4_FindPatientAttribute.png|600px|none|thumb|Find Patient's Sex source attribute information]] | ||
::[[File:Task5_Step5_ClickEditButton.png|600px|none|thumb|Click the "Edit Rule Source Attributes" button]] | ::[[File:Task5_Step5_ClickEditButton.png|600px|none|thumb|Click the "Edit Rule Source Attributes" button]] | ||
| Line 131: | Line 131: | ||
::[[File:Task5_Step9_SaveInterval.png|600px|none|thumb|Click the save button to save the rule schedule]] | ::[[File:Task5_Step9_SaveInterval.png|600px|none|thumb|Click the save button to save the rule schedule]] | ||
==Task 2: Provide feedback on incorrect Decision Intervention | ==Task 2: Provide feedback on incorrect Decision Support Intervention rule usage.== | ||
* Test: | * Test: | ||
:* Provide rule feedback on incorrect application of Pap Smear rule for 'Ed Smith' due to incorrect biological sex. | :* Provide rule feedback on incorrect application of Pap Smear rule for 'Ed Smith' due to incorrect biological sex. | ||
| Line 145: | Line 145: | ||
::[[File:Task6_Step7.png|600px|none|thumb|Confirm 'Feedback submitted successfully' message]] | ::[[File:Task6_Step7.png|600px|none|thumb|Confirm 'Feedback submitted successfully' message]] | ||
==Task 3: View and update 3rd party Decision Intervention | ==Task 3: View and update 3rd party Decision Support Intervention source attribute information.== | ||
* Test: | * Test: | ||
:* Update 3rd party decision support intervention source attribute field information. | :* Update 3rd party decision support intervention source attribute field information. | ||
| Line 151: | Line 151: | ||
:* The Pain Management Summary DSI engine is missing source attribute information on what kinds of patients the 3rd Party DSI will target in its AI engine. In order to provide clinicians safety information on the target populations of this DSI, this attribute needs to be updated. | :* The Pain Management Summary DSI engine is missing source attribute information on what kinds of patients the 3rd Party DSI will target in its AI engine. In order to provide clinicians safety information on the target populations of this DSI, this attribute needs to be updated. | ||
* Specific Testing steps: | * Specific Testing steps: | ||
::[[File:task1-1.png|600px|none|thumb|Enter 'Smith' in patient selector at top right and then click the search icon/button.]] | |||
::[[File:task1-2.png|600px|none|thumb|Click the 'Smith, Ed' patient.]] | |||
::[[File:Task7_Step1.png|600px|none|thumb|Find and expand the SMART Enabled Apps on the patient's Medical Record Dashboard]] | ::[[File:Task7_Step1.png|600px|none|thumb|Find and expand the SMART Enabled Apps on the patient's Medical Record Dashboard]] | ||
::[[File:Task7_Step2.png|600px|none|thumb|Click on the DSI Source Information to view the source attributes of the application]] | ::[[File:Task7_Step2.png|600px|none|thumb|Click on the DSI Source Information to view the source attributes of the application]] | ||
Latest revision as of 16:29, 19 November 2024
Overview
- The first usability testing was completed by the 2022 Cohort of the Professional Certificate in Health Information Technology at Columbia University for the a1, a2, a5, a9, a14 certification criteria.
- A 2024 addendum to the usability study is being conducted by OpenEMR for the b11 certification criteria.
Usability Test Report
UCD Process
Criteria that tested
- a1: Computerized provider order entry (CPOE) – medications (2022 task 2) (completed in 2022 and hidden below)
- a2: CPOE – laboratory (2022 task 4) (completed in 2022 and hidden below)
- a5: Demographics (2022 task 1) (completed in 2022 and hidden below)
- a9: Clinical decision support (2022 task 1) (completed in 2022 and hidden below)
- a14: Implantable device list (2022 task 3) (completed in 2022 and hidden below)
- b11: Decision Support Intervention 2024 addendum (2024 task 1,2,3)
Research
- Actual rule:
- Example reports:
- https://content-main.ul.com/sites/g/files/qbfpbp306/files/2020-08/BlueEHR-2.0-SED-Report.pdf
- https://slicompliance.com/wp-content/uploads/2022/01/Prime-Clinical-EHR-Usability-Test-Report.pdf
- https://slicompliance.com/wp-content/uploads/2022/01/FreeChiro_18_SED_Report.pdf
- https://slicompliance.com/wp-content/uploads/2021/12/Strateq_EHR_UsabilityReport_08Dec2021.pdf
Usability official testing demos
- These are duplicate official testing demos that contain 1 patient (Ed Smith). Official testing demos completely reset daily at around 1:00 am pacific time; when official testing demos completely reset, they are rebuilt on top of most recent codebase. Official testing demos use private credentials (ie. public will not be able to access them) that are only known to the official testers.
Usability training demos
- The point of these training demos is to allow training by multiple users, which pick Ed Smith patient to run through the below training guides on. Training demos completely reset daily at around 1:00 am pacific time; when training demos completely reset, they are rebuilt on top of most recent codebase. Training demos use public credentials, which are username:admin password:Administrator1!
Usability testing scenario
- Ed Smith is a patient in the user's clinic. In this scenario, the user will 'update Prostate Cancer Screening rule to explain the rule's usage of patient's biological birth sex', 'provide rule feedback on incorrect application of Pap Smear rule for Ed Smith due to incorrect biological birth sex', and 'update 3rd party decision support intervention source attribute field information'.
- The following is the testing guide that will be used during testing by the users: Usability Testing Guide
- The task material below is for user training.
Task 1: View and update Decision Support Intervention source attribute information.
- Test:
- Update Prostate Cancer Screening rule to explain the rule's usage of patient's biological birth sex.
- Scenario:
- The OpenEMR internal CDR is missing source attribute information on how it's Prostate Cancer Screening rule is using the patient's biological birth sex information in its rule calculations. I need to update the source attribute information for this rule to explain that the sex data point is used to determine if the patient is male and should be screened for prostate cancer. This will help clinicians make informed decisions as to the efficacy and safety of the rule.
- Specific Testing steps:
Task 2: Provide feedback on incorrect Decision Support Intervention rule usage.
- Test:
- Provide rule feedback on incorrect application of Pap Smear rule for 'Ed Smith' due to incorrect biological sex.
- Scenario:
- 'Ed Smith' in the Clinical Decisions section of his patient dashboard is showing that he needs a pap smear exam. However, Ed's biological birth sex is male and he has no cervix. As a clinician I need to provide feedback to the CDR designer of this rule that it is improperly being applied to Ed and the rule needs to be fixed.
- Specific Testing steps:
Task 3: View and update 3rd party Decision Support Intervention source attribute information.
- Test:
- Update 3rd party decision support intervention source attribute field information.
- Scenario:
- The Pain Management Summary DSI engine is missing source attribute information on what kinds of patients the 3rd Party DSI will target in its AI engine. In order to provide clinicians safety information on the target populations of this DSI, this attribute needs to be updated.
- Specific Testing steps:
