Desgin and plan user configurable register view

[rowo]

Here's an approach for discussion:

We have three main registers available that patients/cases can move through, presumptive, positive and in-treatment. Within those, there are a few configurable parts shown below.

A potential list of columns is:

• Patient info (1 layout for now - name, id, age, sex)
• First encountered date
• Time since first encounter
• Initial results (editable/active until treatment starts, then becomes “baseline results” perhaps or keeps same name)
• Latest results
• Results during treatment (the idea here is a special minimal comparison view in one column rather than taking up two columns)
• Diagnosis date
• Treatment start date
• Treatment Regimen
• Treatment History (not sure if this is useful)
• Risks (via optional risk form, maybe attach to flags)
• Last seen (last service/data entered for patient)
• Notes (via optional notes form)
• Button, single (define label and form)
• Button, drop down (define list of labels and forms)
• Button, schedule (define label, form, schedule)

@maimoonak @alihabib I'm curious about the approach — it can either be some sort of pre-defined list like the above, or very open where a user can assign a column to any field in a the form (like having a yes/no column for "Does this person eat pizza?")

[alihabib]

In my opinion allowing a closed list of what we think will be the typical things to ad/remove might be the way to go.

Given that we are allowing users to change forms though, it could potentially cause a situation where someone someone has added something to one of the forms that they think is vital to have showing up in the register. I think this would be an edge case if we get the list right to start with however.

[rowo]

@alihabib @kwasim Cool, I'm okay with that approach.

I had a few questions on a few of the columns:

• Results
• Results comparison or baseline-now delta
• Treatment regimen

We could just have an unordered list for any of the above, same as what's fed from the forms, but I was wondering if we should make it more visual and easier to read given these will be in most registers and is an opportunity to differentiate — like the red plusses that were in the early mockups. Any ideas for these columns or other special columns that would be good for TB?

[alihabib]

The pluses still work really well for test results for smear and culture but perhaps a change in colour would be needed if we use colours for progress (see below)

For GeneXpert the results are different (e.g. MTB +ve, -ve or error and RIF +ve,-ve,indeterminate). If there was a way to visually differentiate those types of results from smear and culture that would be nice. I've not seen this done anywhere in the TB world so not really sure what it would need to look like

For the results comparison, red to indicate declining progress or green/blue to indicate improvement would be nice but we also don't want to overwhelm the user with colours.

For regimen the standard way to show it us to use the short names for the drugs.

[rowo]

For these registers:

• https://projects.invisionapp.com/d/main#/console/11807727/249241050/preview
• https://projects.invisionapp.com/d/main#/console/11807727/249241052/preview
• https://projects.invisionapp.com/d/main#/console/11807727/249241054/preview

What're predetermined in registers:

• Choice of register i.e. presumptive, positive, in-treatment
• Colors and visual styling
• Existence of top bar (with the filter, advanced search buttons), and search bar
• Patient info column and "transition buttons" (diagnose, start treatment, followup)

What's configurable in registers:

• Whether the "transition buttons" are on schedules
• Labels for register, columns, buttons
• Which other columns show up
• If the add button appears (to be determined)
• Results categories come from forms