Pathway coordination, at a glance.
A unified view of chronic condition progress, goals, escalations and next actions for each person.
Your workflows run themselves, and your own team can change them. Every workflow in HealthOS (an intake, a claim, a discharge, a monthly compliance cycle) is a pathway: an ordered set of stages, each made of drop-in widgets. You assemble them point-and-click in the admin console. No developers, no vendor tickets, no waiting on a release. This is what we mean by "configuration, not consultants."
Contact usA widget does one real thing and records the result against the person. It isn't a form field, it's a step in the job. Some widgets capture information; others reach out to a government system or move the person forward.
Group widgets into stages, order the stages, and you have a pathway, the whole journey for a referral or an episode, from first contact to admitted (or from admitted to claimed and reported). One pathway runs the lifecycle; a person can run several at once.
You don't start from a blank page. Pick from a growing toolbox of widgets, the same ones that power intake, claiming, clinical care and compliance across the platform.
Here's the whole build, in the admin console, by an operations lead, in an afternoon. No ticket to us.
Configuration this powerful needs governance, so pathways behave like code without being code. Published definitions are read-only; you edit a draft, preview it, then publish, and every publish is versioned and auditable.
The alternative to configuration is a consulting engagement every time a funding rule changes or a new program lands. Because pathways are configured, not coded, your team owns the change, and the platform adapts to Support at Home, AN-ACC, NDIS and private care without a release.
A unified view of chronic condition progress, goals, escalations and next actions for each person.
Older Australians rarely have one chronic condition. HealthOS pathways are designed for multimorbidity, a person can be on multiple concurrent pathways with shared goals and coordinated medication reviews across conditions.
Every pathway embeds prevention screening as a first-class design principle, not an afterthought. Risk factors are identified early, interventions triggered proactively, before conditions escalate.
Clinical threshold bands are sourced from Australian clinical guidelines and configurable per organisation. The longitudinal rules engine replays thresholds against incoming monitoring data, from paired devices, manual entry, or ingested clinical systems.
We will walk you through it on real data. Bring questions.