There is now an attached diagram depicting the flow of the program for this spring

Sprint 4 Focus

The main idea focus for sprint 4 will be to get the application prepared for a usability study. This will require minor changes to certain defaults upon login and a slight rework of the patient session views.

There are two equal priorities:

1. The 5-second prescription - The theme of ticket #369 will carry on in this sprint. There are some elements of that ticket that haven't been completed yet, and some new ideas on streamlining this process may arise. The general rule here is to improve the prescription writing portion as much as possible
2. To rework the application to set it up for a usability study. This is a bit of a change of focus, but doesn't require a lot of substantial change to the codebase. It will mostly be reworking some defaults and some changes to the patient/SBADM editor views.

Reworking the Interface for Usabiltiy Studies

The basic workflow as it exists now is something like this...

1. User logs in
2. User searches for patient
3. User selects patient
4. User is free to add/edit prescriptions, allergies, etc...

For the usability study, this will not change much. Here is the general idea...

1. User logs in
2. At this point, there exists a single patient to choose. This step requires a little work, as that patient must be "new" every time someone logs in. This step could be avoided for the sake of the study, but seeing as how the patient search/selection already works, a small rework should be easier than overhauling it to work around this step.
   • A sticking point here is, "What happens if the user tries to search for a patient?"
   • Also, what about the creating new user/patient buttons. Presuemably, those should be hidden from the user.
3. User selects patient
4. User is presented with the same layout as before except for the main view. That area will be the focus of this rework. Initially it will present the user with a prescription for the user to enter. It will contain two buttons.
   • Choice "A" will be selected if the user understands the prescription they are to enter. When this option is selected, a new tab is opened over the top of the "main" view, presenting the standard prescription editor. The prescription to be entered will then be displayed in the notification panel for reference. Upon submitting the prescription, the tab closes, revealing the main tab again, with a new prescription to enter and the process repeats itself.
   • Choice "B" will be selected if the user does not understand/like/etc the suggested prescription and a new one is offered in the same view. The process then repeats.

Working Points

By my count there are 4 immediate working points concerning this track.

1. A separated database is required for this testing. This will be a safe production-type environment.
2. Setting up the new patient and dealing with patient selection.
3. Creating the "prescription suggestion" view and building the workflow cycle that appears in (4) above.
4. Continuing to push for improvements in the "5-second prescription" story.

There should be quite a few tickets that come out of this. Items 1-3 can be turned into individual stories, but smaller tickets will likely emerge from each of them.