asky.design

From totals to individual readings

Product design / asky

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 screens
Monitor mockup of the analytics screen: key metrics, a completion-versus-target chart and the assistant panel
Who it serves
Federal and regional analysts working in the compulsory health insurance system.
My role
Visual identity and analytics interface design.
Scope of this case
Three standalone desktop pages; the end-to-end journey is a proposed concept.

One question at three scales

Follow-up care monitoring connects programme oversight with individual observations. Analysts must distinguish plan completion, risk group composition and specific deviations: in the source system, an appointment missed against its due date was as much a basis for a signal as an out-of-range reading. A headline number supports an overview but cannot establish an individual signal’s basis.

The design task was to distribute these questions across levels of the interface. Analytics directs attention, the registry describes the group, and diaries expose a patient’s measurements as the curator’s view rather than a patient scenario. This structure proposes a traceable review process; linked navigation and retained filters are not implemented.

The case is based on a real public health insurance system (2023) covering both the professional contour and the insured person’s cabinet. The LensCare name, identity and demonstration data are changed for publication, and the screens remain a prototype. The patient side of the same system is shown in the HealthHub case.

Scope of this case

Three standalone desktop pages; the end-to-end journey is a proposed concept.

01

Establish scale before exceptions

Placing programme totals beside individual alerts can blur the distinction between overall performance and a specific case.

02

Make the group inspectable

An aggregate does not identify its members or show which patient attributes warrant closer inspection.

03

Expose the basis of a signal

Risk colour alone cannot explain the direction of change or connect it with a particular measurement.

From the challenge
to the decision.

Design challengesChallenge
01

Establish scale before exceptions

Placing programme totals beside individual alerts can blur the distinction between overall performance and a specific case.

02

Make the group inspectable

An aggregate does not identify its members or show which patient attributes warrant closer inspection.

03

Expose the basis of a signal

Risk colour alone cannot explain the direction of change or connect it with a particular measurement.

LensCare / Prototype interfaceDemo data
01

Establish scale before exceptions

The analytics page moves from KPIs to progress against targets, risk groups and observations needing attention. The sequence progressively narrows the review.

Trade-off

This hierarchy uses vertical space. Urgent observations may require scrolling, so their visibility needs testing in realistic analyst tasks.

Prototype interface: Establish scale before exceptions
Demo data
02

Make the group inspectable

The registry provides an insurance ID search, a filter panel and columns for age, ICD-10 codes, risk level and signals. These attributes structure the proposed narrowing step.

Trade-off

The table assumes desktop working space. Fully functioning filters and carrying context from analytics remain implementation work.

Prototype interface: Make the group inspectable
Demo data
03

Expose the basis of a signal

Risk cards compare previous and current states, repeating colour with an arrow and text, so risk-level dynamics read without a legend. Diaries show blood pressure, pulse and glucose with normal ranges and a deviations table.

Trade-off

The ranges and risk states belong to a demonstration. Calculation rules and medical interpretation require separate verification before real-world use.

Prototype interface: Expose the basis of a signal
Demo data

Fragments of the current Russian-language prototype. The original interface for an evidence-based before/after comparison has not been added.

To add: the original screen, date and comparison conditions.

A shared language.
Down to the details.

The palette, component fragments and CSS values from the current prototype. The full system specification and usage rules still need to be added.

Colour / semantics

An accent within dense data

Lime #CCFE49 identifies LensCare. Surfaces #EFECE6 and #E4E6E9 with dark #0F1316 underpin tables and analytical cards.

01#CCFE49
02#EFECE6
03#E4E6E9
04#0F1316
LensCarePrototype interface
Typography / hierarchy
Aa123

Inter → system-ui

The family declared in CSS. Missing fonts or glyphs use the system fallback.

400600700
12 / 14 / 32 / 42 px

To add: text roles and the complete type scale.

Components / states

Make the group inspectable

Components / states: Make the group inspectable
A fragment of the original prototype. Other states still need to be added.
Geometry / rhythm

Values from the layouts

Selected spacing and corner-radius values from CSS. These examples are not an approved token scale.

81218
1011

The decisions, in detail

Programme overviewExplore the screen
01

Programme overview

The top of the analytics page shows KPIs and progress against the target. Risk groups and observations continue below the preview window.

Inside the patient groupExplore the screen
02

Inside the patient group

Search and filters accompany patient rows with diagnoses, risks and signals.

The individual readingsExplore the screen
03

The individual readings

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.

Read-only HTML previews of the original Russian-language prototypes. Demo data; personal identifiers replaced. The previews use the original product name "ГИС ОМС" and the logo from the project identity.

Original size. Scroll the screen to explore the details.

Open prototype separately
LensCare / Prototype interface

From the overview
to the detail.

Targets accompany progress, ranges accompany readings, and attributes accompany patients. Each block keeps its reference in view.

Three standalone desktop pages; the end-to-end journey is a proposed concept.

Explore the scenario
Reading and action order

LensCare

Prototype interface

  1. 1
    Proposed journey: review headline indicators
  2. 2
    Compare progress with targets and inspect risk groups
  3. 3
    Narrow the group in the registry
  4. 4
    Examine individual readings in patient diaries

More than a colour code. Text and arrows repeat risk colours. This implemented choice still requires testing within a whole-system accessibility review. The diagram describes the case logic. Working transitions are limited by the current prototype.

How the project
is presented.

The challenge, decisions and prototype are documented. The process history, contributors and intermediate versions still need supporting material.

My role

Visual identity and analytics interface design.

Already documented

Three standalone desktop pages; the end-to-end journey is a proposed concept.

  1. 01

    Brief

    Scope documented

  2. 02

    Decisions

    Decisions and trade-offs documented

  3. 03

    Prototype

    Layouts available above

  4. 04

    Validation

    User testing remains a next step

What took shape.
Within the prototype.

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.

Standalone prototype pages
3

Artefact inventory

Types of readings in patient diaries
3

Artefact inventory

Risk states compared: previous and current
2

Artefact inventory

The numbers describe the prototype’s scope. User impact has not been measured.

To add: baseline, test method, sample and results.

Boundaries of the result

Data is explicitly mocked in the source. Many filter and export buttons only display notifications; the linked journey is not implemented. There is no baseline measurement, so faster analysis or better decisions cannot be established.

What to test next

01

Test scenario

In a future test, locate a target deviation and explain what needs attention.

What to observe

Record identification accuracy, search time and confusion between overall movement and individual signals.

02

Test scenario

Once pages are linked, trace a group signal to a patient entry.

What to observe

Check retained selection context, incorrect transitions and whether participants can name the signal’s basis.

03

Test scenario

Compare a risk change with readings in test diaries.

What to observe

Record interpretation of direction, ranges and deviations, including a version without colour cues.

Next case study

HealthHub

What matters today