What problem does On-Care solve?
Specialist care across APAC is fragmented across incompatible systems, one specialty and one jurisdiction at a time.
How does On-Care solve it?
One platform standardizes records, scheduling and billing per specialty, modelling each market as configuration rather than a fork.
Where is On-Care now?
In active build, first markets onboarding. Founder-CPO Anthony Chevalier.
On-Care standardizes the operational spine of specialist care so a clinic runs the same way in every market it enters, across 22 specialties and 9 APAC markets.
What does On-Care standardize?
Records, scheduling and billing are held in one platform per specialty, so a clinic does not stitch together incompatible systems to run a single patient journey across 22 specialties.
How does On-Care handle nine markets?
Each APAC jurisdiction carries its own rules for records and billing, so the platform models the market as configuration rather than a fork, which keeps one codebase serving every region it enters.
How is the build made to hold?
The product is built as an industrial production chain. 90+ primary-research documents on per-country regulation, patient pathways and clinical workflows feed 22 complete Service Blueprints and 3700 structured feature specs. Every drift becomes an automated check, every check becomes a script, and the system hardens with each cycle rather than drifting across 22 specialties by 9 markets.
- Who is On-Care for?
- Specialist clinics and networks operating across multiple APAC jurisdictions.
- How is On-Care built?
- As an industrial production chain: 90+ primary-research documents and 22 complete Service Blueprints feed 3700 structured feature specs, with quality gates and automation scripts that harden the system each cycle.