Case study · SiDLY Healthcare · in progress
Redesigning the ERP that runs public telecare
Municipalities, public institutions and care providers use the SiDLY ERP to order telecare bands, assign them to residents, keep consent documents in order and renew contracts. I am leading its redesign.
The challenge
Routine tasks where mistakes are easy to make and hard to notice, for very different clients.
What I did
Research with municipal and foreign clients, then a clickable React/TypeScript prototype.
Signature move
An undo instead of a confirm for anything reversible.
The interface is unreleased and confidential, so this case study describes the process and decisions without screens. I am happy to walk through the prototype in an interview.
The problem
Most of the work in the ERP is routine: activating a batch of bands, swapping a broken one, attaching a signed consent form. Mistakes in these tasks are easy to make and hard to notice. A band can be activated for the wrong client, or keep sending data under a person who no longer wears it.
The system also serves two very different clients. A Polish municipality works in złoty, uploads documents from its social-welfare office and tracks coverage of its residents aged 60+. An export client sells across borders, invoices in euro and needs dialling codes per country.
How I worked
Weekly project meetings with stakeholders, plus research with municipal and foreign clients about how they order, assign and renew devices.
I built the redesign as a clickable prototype in React and TypeScript with realistic test data, so whole flows can be tested instead of static mockups.
Where the decisions sit
The life of an order and its bands, simplified. Numbers match the decisions below.
Key design decisions
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.
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.
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.
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.
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.
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.