Analysis User Interface

The cohort builder is very useful and intuitive for some purposes. But since it's the only tool we have for getting sets of patients, it ends up being used for other purposes as well, and as a result many users don't really like it.

A pretty common case is that of a data officer who wants to quickly select a group of patients, and run a report on that group. They will generally not be doing complicated boolean expressions based on individual subqueries. They want to do something more like "print the consult sheets for Rwinkwavu Group 3".

Here's a mockup of how the UI might look.

This can easily be programmed in a way that makes it completely configurable by a site's administrator:

• Each check box represents applying a pre-generated saved cohort definition

• All checked boxes within a fieldset would be OR'd together

• All fieldsets would be AND'd together.

• I.e. checking Rwinkwavu, Kirehe, and Male means "(Rwinkwavu OR Kirehe) AND Male".

• You can imagine configuring this via a spec like this:

Where:

• Demographics, HIV Program, etc are enduser-defined strings and can be anything (just box labels)

• Location, Sex, Age, ARV Treatment Group are also enduser-defined strings and can be anything (just box labels)

• Rwinkwavu, Kirehe, Mulindi, Female, Male, Adult, Child, 0-5, 5-15, Group 1, Group 2, Group 3, Group 4 are all names of Cohort objects?

I used Balsamiq for the mockup. Here's how: