MIS+ All projects

Keep the visit in context

Product design / asky

Moving between patients requires clarity about whose record is open and what happens when a visit ends. For MIS+, I focused the prototype on the queue, the selected patient’s context and explicit actions for moving forward.

Explore the screens
Prototype interfaceMIS+
Queue and selected patient
Demo dataMIS+ / Product design
Who it serves
Clinic staff working with the visit queue and patient records.
My role
Product design for the medical system and its interface structure.
Scope of this case
Desktop prototype with three routes: reception, patients and a new-patient form.

A focused slice of a system

The clinic-network PRD notes twenty old navigation icons, inconsistent filters and busy forms. These are unvalidated design observations. The prototype focuses on reception and patients.

The challenge is retaining context when the queue changes. Patient details, history, current visit and summary belong together, while completion and non-attendance need distinct actions despite both advancing the queue.

Scenario logic

  1. 01

    Search for and select a demonstration patient

  2. 02

    Review history, the current visit and the allergy warning

  3. 03

    Complete the visit or separately mark it as missed

  4. 04

    Move to the first waiting patient

What shapes the interface

01

Keep the queue beside the work

Switching between list and record can obscure whose history and visit are displayed.

Decision

The left-hand queue accompanies patient details, history, current visit and summary. Search and selection work with demonstration records.

Trade-off

The composition assumes desktop space. Long histories and larger queues still need usability testing.

02

Separate two visit outcomes

Completion and non-attendance change the queue but represent different events, requiring distinct actions.

Decision

Finish-and-next is separate from marking a missed visit. Both promote the first waiting patient.

Trade-off

Queue changes are local. Mistaken completion, reversal and consistency across workstations need further design before connecting real data.

03

Put orientation before action

Icon-only navigation demands memorisation, while allergy warnings can disappear among densely arranged fields.

Decision

The shell labels navigation and places an allergy strip above visit actions. New-patient entry has a separate route.

Trade-off

The strip does not establish comprehensive clinical warnings. Saved-state labels do not mean form data is persisted.

A shared visual language

The palette and principles represented in the prototype. A full component specification is not yet part of this case.

01 / Palette

A restrained working palette

Colours #DCECB9, #E2E8E3, #F5F7F4 and #18332C underpin MIS+’s queue, fields and summary.

#DCECB9
#E2E8E3
#F5F7F4
#18332C
02 / Principle

A shared application shell

Labelled navigation unifies three routes. Other labels do not establish functioning scheduling or finance modules.

03 / Principle

States with visible consequences

Selection changes patient context; completion and non-attendance advance the queue locally against six fixture patients.

The decisions, in detail

Read-only HTML previews of the original Russian-language prototypes. Demo data; personal identifiers replaced.

Queue and selected patientExplore the screen
01

Queue and selected patient

Patient context accompanies the queue; the allergy strip precedes visit actions.

The patient listExplore the screen
02

The patient list

Demonstration records appear within the shared shell and labelled navigation.

A new patient recordExplore the screen
03

A new patient record

A dedicated form route presents input structure without data persistence.

Designer-directed AI prototyping

The process material demonstrates AI use for structure, code, demo data and states. The designer owns priorities, clinical context and verification. This documents an approach to prototyping without a measured speed gain.

What took shape

The prototype implements three routes, patient search and selection, and local queue changes after completion or non-attendance. It brings visit context into a desktop composition and presents a new-record form.

3Routes: reception, patients and new patient
6Demonstration patients in the queue
2Queue-advancing actions: complete and missed

What to test next

01

Test scenario

In a future test, find a patient and identify whose history is open.

What to observe

Record selection errors, lost context and repeated identity checks against the queue.

02

Test scenario

Run separate completion and missed-visit scenarios on a test queue.

What to observe

Check action choice, understanding of the next patient and expectations of reversal.

03

Test scenario

Review the allergy warning and complete a test new-patient form.

What to observe

Record warning discovery, omitted fields and saving expectations; test persistence once storage exists.

Next case study

LensCare

From totals to individual readings

Original size. Scroll the screen to explore the details.

Open prototype separately ↗