A regional indicator needs a clear path to the observations behind it. For LensCare, I organised three levels of information: programme performance, patient groups and individual health readings.
Explore the screensChronic-care monitoring connects programme oversight with individual observations. Analysts must distinguish target progress, group composition and specific deviations. A headline number supports an overview but cannot establish an individual signal’s basis.
Analytics directs attention, the registry describes the group, and diaries expose individual measurements. This structure proposes a traceable review process; linked navigation and retained filters are not implemented.
Proposed journey: review headline indicators
Compare progress with targets and inspect risk groups
Narrow the group in the registry
Examine individual readings in patient diaries
Placing programme totals beside individual alerts can blur the distinction between overall performance and a specific case.
The analytics page moves from KPIs to progress against targets, risk groups and observations needing attention. The sequence progressively narrows the review.
This hierarchy uses vertical space. Urgent observations may require scrolling, so their visibility needs testing in realistic analyst tasks.
An aggregate does not identify its members or show which patient attributes warrant closer inspection.
The registry provides an insurance ID search, a filter panel and columns for age, diagnosis, risk and signals. These attributes structure the proposed narrowing step.
The table assumes desktop working space. Fully functioning filters and carrying context from analytics remain implementation work.
Risk colour alone cannot explain the direction of change or connect it with a particular measurement.
Risk cards compare previous and current states, repeating colour with an arrow and text. Diaries show blood pressure, pulse and glucose with normal ranges and a deviations table.
The ranges and risk states belong to a demonstration. Calculation rules and medical interpretation require separate verification before real-world use.
The palette and principles represented in the prototype. A full component specification is not yet part of this case.
Lime #CCFE49 identifies LensCare. Surfaces #EFECE6 and #E4E6E9 with dark #0F1316 underpin tables and analytical cards.
#CCFE49#EFECE6#E4E6E9#0F1316Targets accompany progress, ranges accompany readings, and attributes accompany patients. Each block keeps its reference in view.
Text and arrows repeat risk colours. This implemented choice still requires testing within a whole-system accessibility review.
Read-only HTML previews of the original Russian-language prototypes. Demo data; personal identifiers replaced. The previews use the LensCare name and logo from the project identity.
The top of the analytics page shows KPIs and progress against the target. Risk groups and observations continue below the preview window.
Search and filters accompany patient rows with diagnoses, risks and signals.
Summary readings and a blood pressure chart with normal ranges. The pulse chart begins at the bottom; glucose and the deviations table sit below the preview window.
The artefact contains an analytics overview, registry and patient diaries with a shared visual language. It presents three levels of detail and a conceptual route from aggregate information to individual readings.
In a future test, locate a target deviation and explain what needs attention.
Record identification accuracy, search time and confusion between overall movement and individual signals.
Once pages are linked, trace a group signal to a patient entry.
Check retained selection context, incorrect transitions and whether participants can name the signal’s basis.
Compare a risk change with readings in test diaries.
Record interpretation of direction, ranges and deviations, including a version without colour cues.
What matters today