Interaction Design¶

After defining the structure of the program–arranging it into stages, attributes, and data elements–you have a “workable” prototype that allows users to enter individual level data and produce routine data reports.

In practice, real people will be entering individual level data. They will often have pressures on their time to enter many data points for many patients in the same day. They will sometimes make errors and enter invalid or inconsistent data.

Smart interaction design improves the user experience, which can help with improving data quality and facilitating intuitive data entry workflows. These are not just aesthetic considerations, but key tools for supporting data entry personnel by making their jobs easier and more efficient. And as described above, program rules can also be used to support the design of program stage structures required for data entry workflow and analytics outputs.

Tracker Features To Streamline User Experience¶

In DHIS2, strong interaction design can be configured through the following features, which support an end user to efficiently and effectively search for the correct TEI, navigate to the correct stage and event, then enter valid data element values.

Work In Progress

While full exploration of interaction design and Tracker capabilities is out of scope for this guide, configuration instructions are presented elsewhere in the documentation. See links below.

• TEI Searches
  • Patient Rosters (Working Lists)in Capture and Tracker Capture
  • Patient Listings (Line Lists)
  • Which TEI are searchable, how long they need to be open
  • Trade-off between search flexibility and performance
  • “Search org units” and accessibility
  • Tracker search optimization (trigram indexing)
• Program and Program Stage Settings
  • Expiry days and completed event expiry days
• Program Rules
  • Skip logic (show/hides)
  • Assign
  • Warning boxes
  • Error boxes
  • Priorities of rules to create a cascading logic
  • “Select multiple” data elements – Yes Only data elements within the same section with program rules overlaid so only one can be entered. Example: Key Population selection in HIV Case Surveillance
  • Differences of Android and Web program rule evaluation
• TEI Dashboard layout
  • Widget layout
  • Feedback and Top Bar dynamic updates through program rules
  • “Live” program indicators
  • Android Settings app
• Visual Configuration
  • Icons and colours on data elements (Android)
• Tracker Data Entry Modes
  • Timeline and tabular data entry
• Other Tracker features to support intuitive workflows
  • Program Notifications (SMS alerts, emails, or DHIS2 messages)
  • User Assignment
  • Relationships

During the testing phase of the project, you should consult with beta testers on their experience of using the tracker program prototype, to understand how these features can be best utilised to support their workflows.