MOCKUP: patient tabs

[mapsam]

Show mockups of tab navigation within a patient

[mapsam]

Recreated the tab look, and also thinking about how they work on mobile... what if we removed the tabs entirely and made a dropdown navigation?

desktop

mobile

[mapsam]

With the above gif we now have a reset for dropdown menus that removes the border radius. Since using -webkit-appearance: none; removes the arrows, the rest includes an arrow icon as a background image to bring it back to appearing like a dropdown.

[mapsam]

Tabs wiki: https://github.com/codeforamerica/rva-screening-ui-prototypes/wiki/Tabs

[bengolder]

I think tabs are not the way to go, because they are visually subordinate to everything else on the page and as a result some people missed 'Share Patient' as an option in testing until it was pointed out to them.

[mapsam]

What about styling them a bit more strongly? I really like how tabs show you navigation and context at the same time, rather than having big buttons all over the place. I'll work on some other ideas.

[mapsam]

We should also figure out what the priorities will be on these pages. What should be the most important thing to do on this page?

Seems we have actions and we have views of information.

Actions:

• refer patient
• screen patient
• print (seems best to just have this download a PDF in the page)

Views:

• details
• visit history / share history

[bengolder]

We shouldn't have tabs. Instead we should focus around workflows and actions. For any page, we should be able to quickly state who is using that page and for what action.

This workflow is based on the last round of user testing. These are the steps that navigators tried to do with our app, but had trouble completing:

Here is a set of pages that addresses that workflow:

[bengolder]

I would propose that we separate Patient Details into a few different pages, focused more around the different workflows that were revealed in usability testing.

We should have Patient Overview page that summarizes the patient's most important info, with huge obvious buttons that lead to the most important actions.

[bengolder]

The questions should be part of a referral process. So if a navigator clicks on "Make a referral", they would arrive at a page that lets them select the services they are interested in:

Then, knowing the services they are interested in, we would lead them to a set of questions for those services:

[bengolder]

Upon completed the questions and hitting a big button at the bottom that says "See Eligibility Results", The navigator would then be presented with eligibility results:

[bengolder]

And then they could click into each service to send the patient's application to that particular service. When they do so, they also see the details about the service.