Safety-enhanced design (MU3))

Overview

This usability testing was completed by the 2022 Cohort of the Professional Certificate in Health Information Technology at Columbia University.

An 2024 addendum to the usability study is being conducted by OpenEMR for the b11 certification criteria

Usability Test Report

OpenEMR Usability Test Report

UCD Process

NIST 7741

Criteria that tested

• a1: Computerized provider order entry (CPOE) – medications (task 2)
• a2: CPOE – laboratory (task 4)
• a5: Demographics (task 1)
• a9: Clinical decision support (task 1)
• a14: Implantable device list (task 3)
• b11: Decision Intervention Support 2024 addendum (task 5,6,7)

Research

Actual rule:

• https://www.healthit.gov/test-method/safety-enhanced-design

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.

• Testing Demo 1
• Testing Demo 2
• Testing Demo 3
• Testing Demo 4
• Testing Demo 5
• PHP Log

Usability training demos

• The point of these training demos is to allow training by multiple users, which pick a Ed* Smith* patient to run through the below training guides on.
• These are duplicate training demos that contain 9 patients (named Ed1 Smith1...Ed9 Smith9 each with one encounter) with one lab option (PSA) and with ICD10 code set installed and one provider (the admin user with name of Frank Johnson). 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!

• Training Demo 1
• Training Demo 2
• Training Demo 3
• Training Demo 4
• Training Demo 5
• PHP Log

Usability testing scenario

• Ed Smith is a patient in the user's clinic. In this scenario, the user will modify this patient's demographics, enter in a medication order for this patient, add a implantable device for this patient, and order a lab for this patient.

• 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: Enter and modify demographics.

• Test:

• Edit demographics for 'Ed Smith'

• Gender Identity choose 'Identifies as Male'
• Sexual Orientation choose 'Straight or Heterosexual'
• DOB change to '1968-12-30'

• After saving above demographic changes, clinical decision support will display window with new due reminders based off age (including Colon Cancer Screening).

• Specific testing steps:

Enter 'Smith' in patient selector at top right and then click the search icon/button.

Click the 'Smith, Ed' patient.

Click the edit icon/button for Demographics.

Gender Identity set 'Identifies as Male'. Sexual Orientation set 'Straight or Heterosexual'. DOB change to '1968-12-30'. Then click 'Save'.

Click 'OK'.

Task 2: Enter in medication order.

• Test:

• Add prescription for 'Ed Smith'

• Lipitor 20mg tabs Per Oris q.d. with quantity of 30

• Specific testing steps:

Scroll to bottom of patient summary screen and click the edit icon/button for Prescriptions.

Click 'Add'

Enter 'Lipitor' in the textbox and then select the Lipitor entry.

Enter Quantity 30. Enter Medicine Units 20 mg. Enter Directions 1 in tablet Per Oris q.d. Then click 'Save'.

Click 'Quit'.

Task 3: Add a implantable device.

• Test:

• Add Implantable Device for 'Ed Smith'

• UDI is (01)00889095205923(11)141231(17)150707(10)A213B1(21)1234

• Specific testing steps:

Click 'Issues' at top of patient summary screen.

Click 'Add' at Medical Devices.

Paste following into UDI textbox: (01)00889095205923(11)141231(17)150707(10)A213B1(21)1234
Then click 'Process UDI'.

This is what screen looks like after clicking 'Process UDI'.

Then scroll down and click 'Save'.

Task 4: Order a lab.

• Test:

• Order lab for 'Ed Smith'

• PSA

• Specific testing steps:

Click 'Visit Past Encounters' at top of screen.

Click '2022-01-18 Office Visit' from dropdown.

In encounter menu, click 'Administrative', then click 'Procedure Order'.

Click Procedure Test textbox.

Enter 'PSA' and click 'Search'.

Click 'psa_level_order'.

Click 'Save'.

Task 5: View and update Decision Intervention Support source attribute information.

• Test:

• Update Prostate Cancer Screening rule to explain the rule's usage of patient's biologic patient's 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:

Enter 'Smith' in patient selector at top right and then click the search icon/button.

Click the 'Smith, Ed' patient.

Under Clinical Reminders Click info icon for 'Assessment: Prostate Cancer Screening'

Find Patient's Sex source attribute information

Click the "Edit Rule Source Attributes" button

Find the Patient's Sex source attribute to edit

Enter in the 'Rule Usage of Patient's Sex' the message 'This rule uses birth sex to determine if the patient should be screened for prostate cancer'

Click the save button to save the rule

Click the save button to save the rule schedule

Task 6: Provide feedback on incorrect Decision Intervention Support 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:

Enter 'Smith' in patient selector at top right and then click the search icon/button.

Click the 'Smith, Ed' patient.

Click info icon for 'Examination: Pap Smear'

Scroll down to Feedback

Enter 'Rule should not have flagged Ed Smith for pap smear as Ed's birth sex is male'

Click the 'Submit Feedback' button

Confirm 'Feedback submitted successfully' message

Task 7: View and update 3rd party Decision Intervention Support 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:

Find and expand the SMART Enabled Apps on the patient's Medical Record Dashboard

Click on the DSI Source Information to view the source attributes of the application

Find the source attribute for "Intended patient population(s) for the intervention`s use"

Find and click the 'Edit' button

Find the source attribute "Intended patient population(s) for the intervention`s use"

Update the source attribute to be "All patients who have had some form of chronic pain condition or diagnosis"

Find and click the 'Save' button

Verify you see the 'Save successful' message