asky.design

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
MIS+ / Prototype interfaceHTML prototype
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.

Scope of this case

Desktop prototype with three routes: reception, patients and a new-patient form.

01

Keep the queue beside the work

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

02

Separate two visit outcomes

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

03

Put orientation before action

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

From the challenge
to the decision.

Design challengesChallenge
01

Keep the queue beside the work

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

02

Separate two visit outcomes

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

03

Put orientation before action

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

MIS+ / Prototype interfaceDemo data
01

Keep the queue beside the work

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.

Prototype interface: Keep the queue beside the work
Demo data
02

Separate two visit outcomes

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.

Prototype interface: Separate two visit outcomes
Demo data
03

Put orientation before action

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.

Prototype interface: Put orientation before action
Demo data

Fragments of the current 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

A restrained working palette

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

01#DCECB9
02#E2E8E3
03#F5F7F4
04#18332C
MIS+Prototype interface
Typography / hierarchy
Aa123

DM Sans

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

400500600700
12 / 13 / 14 px

To add: text roles and the complete type scale.

Components / states

Separate two visit outcomes

Components / states: Separate two visit outcomes
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.

1014
68

The decisions, in detail

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.

Read-only HTML previews of the prototype. Demo data; personal identifiers replaced.

Original size. Scroll the screen to explore the details.

Open prototype separately
MIS+ / Prototype interface

The next patient.
The same context.

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

Desktop prototype with three routes: reception, patients and a new-patient form.

Explore the scenario
Reading and action order

MIS+

Prototype interface

  1. 1
    Search for and select a demonstration patient
  2. 2
    Review history, the current visit and the allergy warning
  3. 3
    Complete the visit or separately mark it as missed
  4. 4
    Move to the first waiting patient

States with visible consequences. Selection changes patient context; completion and non-attendance advance the queue locally against six fixture patients. The diagram describes the case logic. Working transitions are limited by the current prototype.

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.

My role

Product design for the medical system and its interface structure.

Already documented

Desktop prototype with three routes: reception, patients and a new-patient form.

  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 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.

Routes: reception, patients and new patient
3

Artefact inventory

Demonstration patients in the queue
6

Artefact inventory

Queue-advancing actions: complete and missed
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

There is no backend medical storage. Inputs use default values without persistence; saved labels do not prove a write. A full electronic health record is not implemented. Without baseline measurements, speed or error reductions cannot be established.

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