Skip to main content
Allied health

Running Medicare and NDIS allied health from one practice record

1 July 2026 · 6 min read

When physio, OT, or psychology serves both clinic appointments and NDIS-funded community visits — billing, credentials, and encrypted notes on one Australian system.

Two funding streams, one client

Allied health practices commonly see clients funded across more than one stream. A child seen for early intervention may have NDIS-funded sessions in the clinic and at home; an adult recovering from surgery may move from Medicare-funded chronic disease management items to NDIS supports after assessment.

When the practice runs Medicare in one system and NDIS in another, clinicians duplicate intake, consents, and clinical notes — and the back office reconciles two billing flows before reporting cash.

Billing rules differ in ways software should know

Medicare items have published fee schedules, eligibility rules (GP Mental Health Care Plan, Chronic Disease Management referrals), and HICAPS / online claiming flows. DVA items follow related but distinct schedules. NDIS-funded allied health uses the NDIS Price Guide, registration group, and plan budgets.

A practice system should keep these rules separate at the line-item level but unified at the client level — letting reception ask "which funder for today?" without rebuilding the file.

Credential and AHPRA tracking applies to both

Practitioners need current AHPRA registration regardless of who funds the service. NDIS-registered providers also need additional worker screening evidence for in-home community work. Tracking both in one HR module avoids the situation where a clinician is rostered onto an NDIS shift while their working with children check has lapsed.

Encrypted notes — without sending them to AI

Allied health session notes contain clinical detail that should be encrypted at rest and never sent to external AI APIs. Practices that want AI assistance for documentation can have it on structural metadata — appointment type, duration, goal alignment — without exposing the body of the note.

Persistent, encrypted clinical records support clinician handover and audit without compromising the privacy that clients and AHPRA expect.

Community visits sit on the same diary as the clinic

NDIS-funded therapy often happens in homes, schools, or community settings. A diary that mixes clinic appointments with travel-time-aware community visits — and shows the funder source on each block — is what schedulers actually need.

When the practice also has support workers from a disability arm visiting the same client, sharing one person record removes the awkward email handoff that the client experiences as "yet another form".

When a single system actually pays back

For a solo or small clinic with no NDIS work, a clinic-first product is fine. For practices with growing NDIS revenue, multi-funder community work, or affiliated disability or aged care services, consolidating onto one Australian-hosted record avoids the duplicate-entry tax and gives finance a single revenue view.

See HealthOS in your context

Run NDIS, aged care, or allied health with full depth per program — one person record when you need more than one stream.