Skip to main content
About HealthOS

Built in Australia, for Australian NDIS, aged care, and allied health providers

HealthOS exists because Australian healthcare providers are paying three or four vendors for tools that should live on one record. We are building the platform we wished existed when we ran operations inside disability, aged care, and allied health organisations ourselves.

Why we built HealthOS

Most software in Australian disability, aged care, and allied health was designed for one funding stream and bolted on the others. The result is duplicate client records, three logins for the same person, audit prep weekends, and a procurement bill that grows faster than caseload.

HealthOS is the platform we wished existed: full depth on the program you run today, one person record when you add the next program, transparent per-program pricing, and AI features that respect Australian regulatory rules — pseudonymised by default, with clinical notes excluded from external services entirely.

We are Australian-owned, Australian-hosted, and accountable to Australian healthcare buyers — not a US platform with an AU sales office.

Company snapshot

HealthOS at a glance

The facts a procurement officer or quality manager checks before booking a call.

Founded

2025

Australian-incorporated; Sydney-based core team.

Programs covered

NDIS, aged care, allied health

Full depth per program — not a unified-care shortcut.

Data residency

Australia only

AWS ap-southeast-2 (Sydney) primary, ap-southeast-4 (Melbourne) disaster recovery. No customer data leaves Australian regions.

Security posture

Essential Eight ML2 controls

SOC 2 Type 1 audit scheduled Q4 2026; ISO 27001 alignment on the 2027 roadmap. Trust Pack available on request.

Customer stage

Foundation rollouts

First cohort of registered NDIS, aged care, and allied health providers onboarding through 2026; named case studies publishing from Q3 2026 once customers complete full audit and pay cycles on HealthOS.

Ownership

Australian-owned

Independently funded, no offshore parent.

How we work

Operator-first principles

The four commitments that shape every product decision.

Build with operators in the room

Every workflow in HealthOS is reviewed by people who have run NDIS, aged care, or allied health operations — claim coordinators, plan managers, Directors of Care, AHPRA-registered clinicians. Engineering decisions sit downstream of operator decisions, not the other way around.

Australian regulatory rules are first-class

PACE/PRODA transition, SIRS Priority 1 timelines, CHSP DEX quarters, AHPRA expiry, SCHADS Award 2010 — these are not configurations layered on a generic care platform. They are core schema and logic shipped with the product.

Compliance is the product, not the disclaimer

Every AI feature is labelled, pseudonymised before any external call, and held for human review before reaching a participant file or PRODA submission. Clinical note bodies, behaviour support plans, and counsellor notes never leave the Australian data boundary — and are excluded from external AI services entirely.

Honest about the stage we are at

We are in foundation rollouts. We do not publish customer logos we have not earned, we do not invent testimonials, and we do not claim certifications we have not yet completed. The Trust Pack states exactly where we are today and exactly when each upcoming audit lands.

What sets HealthOS apart

Three structural differences

One person record across programs

A client receiving NDIS, Home Care, and allied health appears once — not three times. Demographics, goals, cultural safety, and contact data update in one place; rostering and claims respect the same record.

Pay for what you run

Single-program organisations pay platform core plus that program only. Add programs as you grow; bundle discounts of 20% (two programs) or 45% (three) instead of penalties for breadth.

Australian-hosted, Australian-supported

Customer data lives in AWS Sydney with Melbourne disaster recovery. Sales, onboarding, and support all operate in Australian business hours — not a 14-hour follow-up loop with an offshore queue.

Want to know more before booking a call?

The Trust Pack covers security architecture, data residency, AI governance, audit posture, and migration patterns — the document procurement teams and Quality Managers need before approving a software change.