Healthcare User Acceptance Testing

A recent XBOSoft blog reader wrote in and asked about Healthcare User Acceptance Testing for a healthcare patient portal.

 

Simply stated, any user acceptance testing would comprise of testing from an end user point of view to determine if you “ACCEPT” the software or not. Usually, acceptance is done by or on behalf of an end user or end customer for whom you are developing software. Sometimes, a development organization may ask a small group of users who have deep domain knowledge to do acceptance testing as well. In any case, it should be done from the end user point of view for stories or use cases that they would execute frequently.

 

If you want to do a User Acceptance Testing (UAT) for a patient portal, what would be the top scenarios that a user would do on the portal. Some user stories that we have run across in our experience in healthcare user acceptance testing include:

  1. Notification to patient – A patient receives notification through either their email or the mobile app that they have a message, results or other information regarding their account.
  2. Look up test results – A patient goes into the portal and checks their mail or looks at recent test results. This could include results from the lab or other tests, or just an email from their doctor.
  3. API for test results – Although not from a patient point of view, data from various systems needs to get into the portal for the patient to access. This could include x-rays, blood test results, electrocardiograms and any other information captured.
  4. Input or update billing information – A patient must enter or update their credit card or bank account information for automatic payment.
  5. Correspondence – Simple messaging back and forth between the doctor or nurse and the patient with records kept for a predetermined amount of time.
  6. Make an appointment – A patient needs to make an appointment with a variety of specialists or their primary care doctor. Sometimes they can make an appointment directly or perhaps need a referral from their primary care physician.
  7. Cancel or edit an appointment – Patients often need to cancel or edit and reschedule an appointment. The doctors must be notified if this interferes with the normal care process.
  8. Fill or check a prescription – A doctor must first input the prescription for the patient, and then the patient can pick up or submit to outside pharmacy.
  9. Inputting vitals – Information such as temperature, blood pressure, glucose levels etc. are input by a technician either manually or through automatic interface via the equipment used.

Going through typical scenarios such as those listed above would constitute the Healthcare User Acceptance Testing for a patient portal. Special attention is needed when considering the end user. Sometimes it is the doctor, nurse or patient. Each has different usage patterns. These are by no means exhaustive, but as you can see, there are many variations as well as negative patterns that need to be tested as well.

 

Contact Us with any questions or to discuss your next project.

Leave a Reply

Show Buttons
Hide Buttons