Skip to content

Instantly share code, notes, and snippets.

@anuar2k

anuar2k/patient-registration-experience.md

Last active November 3, 2018 01:17
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save anuar2k/8b4ea5be3b0e5cde5db73c138561d630 to your computer and use it in GitHub Desktop.
Save anuar2k/8b4ea5be3b0e5cde5db73c138561d630 to your computer and use it in GitHub Desktop.
Download ZIP
Register a patient on the demo system - report
Raw
patient-registration-experience.md

I have successfully registered a patient using OpenMRS RefApp demo (version available as of 02 Nov, 2018) using:

  • new UI (Available under Register a patient)
  • legacy UI (Available under System Administration > Advanced Administration > Find/Create Patient)

I have found some flaws and incosistencies in the design of the new wizard.

The process itself is very simple and it's possible to register a patient without any knowledge about the whole system nor reading any guides, but not without any problems, because it's a bit unintuitive.

I've focused on documenting issues I found using screenshots rather than the process itself.

So what are the design flaws?

  • The new wizard doesn't allow to register a patient without an adress, while old one does (and the fix is to put a random char into any of address fields). There will be probably a lot of situations when we'd like to register a patient without the address. If the server does not valitade it, why the UI should bother? It's perfectly fine to do so using legacy UI.
  • Tabs of the new wizard lack the pointing finger cursor, moreover it's also possible to select text on their labels / caret cursor is displayed: https://imgur.com/a/MhqeREX
  • It doesn't really make sense why the user has to switch between the tabs in the strict order when entering the data. It's not very clear for me why I can't enter adress data without selecting the gender first (these fields do not rely on each other at all, so why force the user to do it all in a strict order - legacy UI does not restrict the user, because all fields are displayed at one time).
  • Birthdate and address fields lack the "required" marker.
  • The function to add a relationship also doesn't work as expected. One issue with this part of the wizard is described in RA-1539 issue, but another problems are:
    • The user isn't really informed that it is only possible to make a relationship with a relative, which is available in the database. Entering a name, which is not found in the DB doesn't cause an error at all. The user is allowed to go to the summary and the name of unavailable relative is displayed properly.
    • It's not really clear that "Person Name" field is a search field, which causes a list pop up. It rather should be named e.g. "Find a relative".
    • When there is more than one person available in the database with the same name, the user doesn't know which person is selected. It could be solved with displaying the ID of the relative, both in the search results list and in the summary: https://imgur.com/a/XeUyLqD
  • Actually, why use tabs at all? Computer screens have a much larger surface that each of these tabs use. It's easier to simply use the scroll of the mouse. It would be easier to review the data displayed at one time, instead of switching between the tabs.

In general, the new wizard is "just okay". In some terms it's a really huge downgrade compared to the legacy UI.

@ykarim
Copy link

ykarim commented Nov 3, 2018

Just a heads up, birthdate and address aren't required as not everyone may have an exact address or remember their birthdate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment