Clinical records clinicians actually defend
Seven disconnected record systems unified behind one FHIR-backed service, with chart loads down from forty seconds to just over one.
- Year
- 2025
- Duration
- 8 months
- Team
- 5 engineers, 2 designers
- Sector
- Healthcare
The problem
Seven disconnected record systems, forty-second chart loads, and a clinical workforce that had quietly routed around the software with paper and group chats. Audit coverage was partial and nobody could say by how much.
What we did
A single FHIR-backed record service consolidated the seven sources, with an edge-rendered chart UI designed alongside the ward staff who use it. Every read and write emits an audit event, so coverage is a property of the system rather than a policy.
Where it landed
Thirty-one thousand daily users on one record, chart loads at 1.2 seconds, and complete audit coverage that satisfies HIPAA without adding a step to clinical work.
“They argued with us — politely, with benchmarks — about half of what we asked for. The system is better for every one of those arguments.”
Dr. Samuel Okafor
Clinical Director, Halcyon Health
Tell us what is breaking.
Send the problem, not a polished brief. A principal engineer reads every enquiry and replies within two working days with a real technical opinion.
- Reply from an engineer, not a salesperson
- Fixed scope and price before any build starts
- Your code, your cloud, your repo — from day one