Work02 / 06Healthcare2025Sample
Care Journey
A patient app and clinician portal that connect booking, treatment and recovery in one journey.
SampleIllustrative case study with placeholder figures — replace it with your own project.
- Client
- Private healthcare network
- Industry
- Healthcare
- Year
- 2025
- Platforms
- iOS
- Android
- Clinician web portal
- Engagement
- 7 months(placeholder) · discovery to app store
- 5(placeholder) · people on the team
The problem
Patients were managing their own care with a phone and a pile of paper.
Booking meant calling during office hours. Prescriptions were printed, follow-ups were letters, and clinicians had no view of how patients were doing between visits.
The network wanted one place where a patient could book, be treated and recover — without adding work for clinicians who were already at capacity.
- clinics in the network
- 12(placeholder)
- clinics in the network
- separate booking systems
- 3(placeholder)
- separate booking systems
The app
Book. Treat. Recover.
Every screen does one job. The journey continues from the booking to the pharmacy to the daily check-ins, so patients always know what happens next.
Booking in three taps
Instant confirmation
Prescriptions to any pharmacy
Tracked to pickup
Recovery, day by day
Our approach
Designed with patients and clinicians in the room.
Strategy
Follow the patient, not the org chart
We mapped patient journeys across the network's clinics and found the hand-offs where people got lost — between booking and the visit, and between the visit and the pharmacy.
UX & UI
Accessible before it's beautiful
Large touch targets, plain language and full screen-reader support were requirements from the first prototype, tested with older patients and people using assistive technology.
Engineering
Health records stay where they belong
The app never becomes a second record system. It reads and writes through a FHIR integration layer, so the clinical record stays authoritative.
Architecture
A thin app on top of the clinical record
Scheduling, prescriptions and messaging run as small services. Clinical data is read from and written back to the existing record system through a single, audited integration layer.
One audited door
Every read and write of clinical data passes through one integration layer with a full audit log.
Offline-tolerant
Dose check-ins and symptom logs queue on the device and sync when a connection returns.
Privacy by design
Minimal data on the device, encrypted storage and short-lived tokens for every session.
In detail
Three moments that used to need a phone call
Booking
Real availability across clinics, video or in person, confirmed instantly with reminders.
Prescriptions
Sent to a pharmacy of the patient's choice and tracked until it's ready to collect.
Recovery
Dose reminders and a 10-second daily check-in that clinicians can see between visits.
In their words
“Client quote goes here: what changed for patients and clinicians after launch.”(placeholder)
Outcome
Less time on the phone, more time on care.
Patients book, collect prescriptions and report progress in the app. Front-desk teams spend less time on the phone, and clinicians see how patients are doing before the next visit.
- phone bookings
- −60%(placeholder)
- phone bookings
- average app store rating
- 4.8(placeholder)
- average app store rating
- WCAG 2.2 conformance
- AA(placeholder)
- WCAG 2.2 conformance
Technology
- Experience
- WCAG 2.2
- Applications
- React Native
- TypeScript
- NestJS
- Data
- PostgreSQL
- Infrastructure
- Azure
