Import your data
Pull everything from your current system with an API key, or bring patients, contacts and appointments across from a spreadsheet with the guided column mapper.
Resources
Everything you need to get running.
Guides to set up your practice, developer docs for the open API, and a straight line to the team when you need a hand.
Help centre
Answers, the overview, and the team.
New to AspireOS? The Help Centre answers the how-to questions section by section, the product overview walks through how the pieces fit together, and the team is one message away.
Help Centre
Short, practical answers: setting up, the calendar, notes, invoicing, the portal, your team and AspireAi.
Product overview
A guided tour of AspireOS — the capabilities, how they connect, and what a day on it looks like.
Ask the team
Have a question we haven’t answered? Get in touch and we’ll help you out.
Install the app
Put AspireOS on your phone straight from the browser — full screen, no app store.
Blog
Plain-English pieces on running a clinic or home-visit practice: NDIS invoices, travel time, credentials and AI.
Start a free trial
Your own practice, with sample data to click through if you want it. 16-day free trial, no card needed.
Blog
Notes from running a practice.
Plain-English pieces on running a clinic or home-visit practice: NDIS invoices, travel time, credentials and AI. Every post.
SOAP notes for occupational therapy, with examples
How to write SOAP notes for occupational therapy: functional goals, home environment observations, NDIS goal links and a worked example to adapt.
Read the post →Practice software for mobile and NDIS-heavy practices
Weighing your options? What a mobile or NDIS-heavy allied health practice should test in any practice management system before switching.
Read the post →AHPRA registration renewal: a checklist for practice owners
A practice owner's checklist for AHPRA registration renewal: the deadline, CPD, insurance and recency declarations, register checks and what to keep.
Read the post →DVA allied health treatment cycles explained
How DVA allied health treatment cycles work for physios, OTs and other providers: referrals, cycle length, end-of-cycle reports and card types.
Read the post →A physiotherapy cancellation policy that is fair and enforceable
How to write a physiotherapy cancellation policy patients accept: notice window, fee, exceptions, funder rules and template wording to adapt.
Read the post →Home visit physiotherapy: pricing, travel and scheduling
How to price home visit physiotherapy, handle travel under each funder, build routes by suburb and run visits that work well for older patients.
Read the post →Moving your data across
Bring your whole practice across in a morning.
AspireOS reads your current system directly, so most of the move is one button. Here is the whole of it.
- Pull everything with your API key. In your current system, copy your API key (usually under its integrations or API settings). In AspireOS, open Settings → Import, paste it and press Pull. Your patients, staff, contacts, visit history, invoices, funding episodes, price list and waitlist come across in one go, with their original dates and times. The key is used once and never stored.
- Bring your progress notes. Clinical notes aren’t offered through the API, but your current system’s own export does: in its export settings, tick Progress notes, widen the date range to cover your whole history, include archived patients, and download the file. Drop it on the Clinical notes import in AspireOS. Notes arrive locked, with their author, each dated by its visit, and you get a count per patient to check against your current system.
- Check, then switch. Re-running the pull is safe — only new records land — so you can pull again on the day you switch. Still working in your current system for a while? The sync card keeps pulling on a schedule and shows you anything the two systems disagree about.
Coming from a spreadsheet instead? The same Settings → Import takes a CSV: headers are matched for you, and dates and funding labels are tidied as they come in.
Guides & templates
Set up once, run for years.
Short, practical guides for the things you’ll do in your first week.
Set up your fee schedule
Model your items, funding and travel rules so invoices price themselves from day one.
Working with AspireAi
How the confirm-before-act model works, the action cards it answers with, and the tasks AspireAi can take off your plate.
Letter & report templates
Starting points for referrer updates and discharge summaries you can adapt to your practice.
API docs
A real open API.
Authenticate with a scoped API key. Keys are issued in Settings under AspireOS, in the Developer group — set up once and then left alone, rather than sitting between the settings you use weekly. Reach it from the Developer tools card, by searching settings for api key, or straight at /settings?tab=developers, which still resolves. A key is shown once and stored hashed, and carries read and write scopes. The base path is /api/v1, and the same pricing, EPC counting and webhook fan-out fire exactly as they do in-app.
GET /api/v1/ping read
Key check — echoes the authenticated practice.
GET /api/v1/patients read
List patients (filter by status, limit).
GET /api/v1/appointments read
List appointments (from / to / status).
GET /api/v1/invoices read
List invoices (filter by status).
POST /api/v1/appointments write
Book an appointment — prices it and fires webhooks.
POST /api/v1/intake write
Land an enquiry on the waitlist.
Webhooks
Subscribe a URL to domain events and AspireOS POSTs you signed JSON as they happen. Each body is { event, at, practice, data }, carrying an X-AspireOS-Signature header (HMAC-SHA256 of the raw body) so you can verify it before trusting the payload. Every attempt lands in an immutable delivery log. Events:
patient.created appointment.created appointment.completed invoice.paid intake.received leave.requestedCommunity
Built with practitioners, not just for them.
AspireOS grows out of real practice — features come from the clinicians who use it every day. Have an idea, a rough edge, or a workflow we should support? We want to hear it.