BESTMED  /  Aged & home care  /  Enterprise platform

Four products, one medication record.

BESTMED runs medication management across Australian aged care: facilities, pharmacies, prescribing doctors and in-home care. I designed one of its products from a blank page, the layer that connects all four, and rebuilt the prescribing record for the phone doctors were already using it on.

Product
BESTMED Platform
Platform
Web, iOS & Android
Role
Sole UX/UI designer
Ecosystem
4 connected products
Constraint
Safety & compliance
01
The problem

One record, four very different jobs.

BESTMED is medication-management software used across Australian aged care, and it isn't one product with one interface. A facility manager needs oversight and compliance visibility. A doctor needs to prescribe correctly, often from a phone between rooms. A pharmacist needs to dispense against a record they trust.

A carer working alone in someone's home needs the interface to be right the first time, because there usually isn't a second look before the moment has passed. Four surfaces, one underlying record, and very different constraints on each.

02
Homecare
The solution

The compliant path is the fastest path.

A carer's day becomes a visit queue with shift progress on it, and every medication step carries the checks legislation requires: allergies pinned above the action rather than buried in a profile, similar-name warnings before a dose is given, and dual-signature sign-off that makes each administration auditable. The obligations are unchanged. What changed is that meeting them is now the shortest route through the screen rather than a detour off it.

Wireframe  /  Layout only, not the real interface
Homecare: today's round
Today's round
The day's visit queue, status chips and shift progress at a glance.
Homecare: safe administration
Safe administration
Allergy warning pinned, every dose visible, one action to record it.
Homecare: insulin sliding scale
Clinical depth
Insulin sliding scale: BGL entered first, dose calculated, out-of-range flagged.
03
Homecare
AI alongside the carer

An assistant that plans, and knows what to hand back.

The assistant sequences the round into a workable route, surfaces what is overdue or due soon, prompts reorders before a medication runs out, and drafts the shift handover for the outgoing carer to review. Two rules hold it in place: every answer is grounded in the round's own data and says so on the reply, and a consent framework decides what it may do unasked. Routing and reordering it proposes; anything clinical it hands back to a person.

Wireframe  /  Layout only, not the real interface
Homecare: AI assistant ready
Assistant, ready
One hero action, suggested questions, and a free-text field, reachable from any screen.
Homecare: AI assistant answering
Assistant, answering
An answer grounded in today's round, with a provenance note to verify before acting.
Homecare: drafted shift handover
Drafted handover
Per-participant summaries and an overall note, drafted for the outgoing carer to review.
04
Care team

One conversation, four products, three organisations.

Facility staff, doctors and pharmacists all needed to discuss the same resident, and the only tool for it was Doctors Book: built for an era when prescribers visited in person and left notes for their next round. A subject line, no reply, no attachments, no search, so finding a finished item meant clicking back through history a day at a time. To Pharmacy there was no channel at all, so facilities phoned. Some pharmacies staffed five to six people whose main job was answering those calls.

I designed Care Team from a blank page, not as a standalone product but as a capability inside the BESTMED ecosystem: one messaging and document-sharing layer built natively into all four products, linking doctors, facilities and pharmacists, so a conversation started from any one of them looks and behaves the same everywhere else. Messages are open to everyone on a resident's care team. Documents are different, allocated to named recipients rather than broadcast, since a document is more often a discrete clinical artefact than a conversational update.

Wireframe  /  Desktop, layout only
Threads, desktop
Starting a new conversation
Desktop 01
Care Team: starting a new conversation
Subject and recipient required, resident optional, so the thread can be about a person or a broader operational matter.
Open and closed threads
Desktop 02
Care Team: open and closed threads
Every conversation tied to a resident, filterable by status and searchable, so nothing has to be hunted down day by day.
Full thread, with attachments
Desktop 03
Care Team: full thread with attachments
A pharmacist sharing a document inline, doctor and facility both in the same conversation.
Wireframe  /  Mobile, layout only
Care Team: new message, mobile
New message. Same fields as desktop.
Care Team: thread list, mobile
Thread list. Same status model as desktop.
Care Team: full thread, mobile
Full thread. Attachments open the same way.
05
BestDoctor
Prescribing on mobile

A record built for a desk, used on a phone.

Homecare started from a blank page. The Doctor Portal did not: it is an established clinical system, and doctors were opening it on their phones out of necessity rather than fit. The medication record was a desktop-width table with cursor-sized controls, so changing one medication meant scrolling sideways to read the row and zooming in to hit a checkbox.

The redesign removes no field the clinical workflow requires and rebuilds the layout for the screen in hand: a single column, sections separated so one part of the record can be edited without travelling through the rest, and targets sized for a thumb.

The medication record  /  Before and after
Doctor Portal medication record before the redesign
Before. Desktop table, unresponsive on mobile.
Doctor Portal medication record after the redesign
After. Rebuilt for the screen it's used on.

The edit flow had the same fault one level down. Every field, dropdown and checkbox rendered open at once and shrunk to fit a screen the form was never drawn for, so a doctor scrolled a long page hunting the one thing they came to change.

The redesign collapses the record into six clearly labelled sections: Start & End Dates, Route & Indication, Dose & Directions, Prescription Options, Administration Options, Frequency & Dose Times. A doctor sees the whole shape of what is editable in one glance, then opens only the section they came for.

The edit flow  /  Before and after
Medication edit flow before the redesign
Before. Every field open, nothing to scan.
Medication edit flow after the redesign
After. Six sections, one glance, no hunting.
06
Outcome

One platform, four products, and the judgement calls that connect them.

One product drawn from a blank page, Homecare. One capability drawn from a blank page inside the ecosystem, Care Team. One established clinical system rationalised without breaking what already worked, prescribing on mobile. Across all three the same question decided the design: what the system can safely do on its own, and what it should still put in front of a person.

01
Homecare designed end to end, and Care Team designed end to end as a capability inside the ecosystem.
02
An established clinical system rationalised for the screen it is actually used on: prescribing on mobile. Facility ordering was rationalised the same way, in its own case study.
03
A consent framework governing what the Homecare AI assistant can do without asking.
04
One messaging and document capability, consistent across three organisations.
05
Compliant with medication legislation and audit requirements throughout.