← All work
Scenarios and client names in this case study are constructed to illustrate our working patterns. The approach, stack, and outputs are accurate representations of services we deliver.
Brief
47 independent clinics across 3 provinces, each running different systems. Some Excel. Some legacy software from 2015 that couldn't update Windows. The challenge wasn't technical — it was political: how do you migrate a workflow without making doctors and nurses feel they've lost control?
Approach
- 01
Pilot 3 clinics
Month 1–3 only 3 clinics participated. Daily feedback drove iteration.
- 02
Native BPJS integration
Clinics no longer needed to re-submit to V-Claim — the system did it automatically.
- 03
Offline mode for power outages
Rural clinics still face outages; the system keeps running and syncs when power returns.
Outcomes
47
active clinics (3 provinces)
18 → 4 min
average check-in time
99.94%
uptime since go-live
Native
BPJS integration from day one
Product Showcase
See the product deeper — features, flows, and an interactive demo.
Notes from the studio
We were reminded that clinic software isn't about "faster." Sometimes what's needed is "more reliable when the day gets heavy." That's what we defend on every release.
Up next
Have a project in mind?
Initial discovery call — no cost, no commitment.