KatarzynaStępień

One record, three people

Three apps around one care visit. I lead UX/UI across mobile and web.

Download on theApp Store Get it onGoogle Play

Lead UX/UI / Web + mobile / React prototype / Medical device, MDR IIa

A visit belongs to all three

The screens

Mobile screens shown in English for this page; the product ships in Polish. All names and data are test data.

1. A visit starts with a scan

   The carer starts and ends each visit by scanning the resident's NFC tag with their phone. Work time is recorded as it happened, not as it was planned, and carers' hours are settled from it.

2. The care card has a lifetime

   Before a visit the care card is the plan. During the visit the carer fills it in. After the visit it becomes the record that the resident and the office read, so it is locked as it was when the visit ended.

3. The resident's home screen answers three questions

   Am I all right, what do I need to do today, and when is someone coming? Large text, large touch targets, few words, and SOS always on top.

4. Urgent first, then the day

   The manager's dashboard opens with what needs a reaction, then today's visits in the field, the week ahead and equipment. Each block leads to the screen where that issue gets solved.

5. Recurring visits stay ordinary visits

   A series is a set of normal visits that share a tag, so any single one can be moved or cancelled without breaking the rest.

6. Prototype in code, not in frames

   The flows are built as a clickable React/TypeScript prototype with realistic test data, so managers and carers test whole visits instead of single screens.

Redesigning the ERP that runs public telecare

The platform municipalities and care providers use to order telecare bands, assign them and keep consent in order. I lead its redesign.

Where the decisions sit

The life of an order and its bands, simplified. Numbers match the decisions below.

1. Confirm only what is expensive

   Asking twice for everything trains people to click through. A confirmation now appears only for a new paid year or a change to many devices at once. A single suspend or resume is reversible, so it gets an undo instead.

2. Read the file back before acting on it

   Bulk activation comes in as a spreadsheet, with columns in a different order every time. Rows are matched on the device number, and nothing runs until each line has been shown back with what it will do. The template you download is the file you can upload.

3. Keep a rule where it matters

   Health data needs signed consent, but the clerk entering a resident rarely has the scan at hand. Blocking the form only taught people to upload placeholder files. Now the resident can be saved, is flagged "no consent" everywhere, and cannot receive a band until the scan arrives.

4. Every number opens its list

   Each count on the dashboard opens exactly the devices it counts, and each bar in the renewals chart renews what it shows. Nothing on the dashboard sends you hunting elsewhere.

5. Show what an action will touch

   With a mixed selection, each action states how many of the selected devices it would change and switches off at zero. The selection bar used to be the one dark element on the screen, which made ticking three rows feel like a warning. It is now calm, with one obvious next step.

6. Never rely on colour alone

   Every status carries an icon and a label as well as a colour, because green and amber are hard to tell apart for colour-blind users.

HealthPlatform: a health summary from a medical wearable

Wristband data and medical documents in; a readable health summary and recommendations out.

The code is private; happy to show it in an interview.

UX friction detection, in real time

Rage clicks, abandoned sessions and stuck screens, flagged as they happen.