A patient needs care
Scheduling, patient access and team coordination create one shared operational context.
Practice management infrastructure / Australia
Practice management infrastructure for Australian healthcare.
From intake to follow-up, one governed platform.
OrionCloud connects the clinical day across teams, portals and workflows while keeping clinicians in control of consequential actions.
Current multi-tenant coreCurrent hosted portalsCurrent governed workflow spinePilot gate migration and trust surfacesExternal gate production rails
01 Care infrastructure
The platform follows the work, not the org chart.
A connected operating path from the first patient signal to the work that follows a consultation.
The consultation starts
Clinical context, structured documentation and scribe-assisted drafts stay in one reviewable workspace.
Next actions are prepared
Workflow rules can propose correspondence, recalls, tasks and billing preparation without silently finalising them.
The team closes the loop
Staff-visible queues, evidence and patient access keep responsibility clear after the consult.
02 Product evidence
Operational views built for the people doing the work.
Inspect the working surfaces directly. These captures use synthetic demonstration data.
03 Readiness
Capability is labelled before it is sold.
Current product foundations, pilot evidence and external dependencies are deliberately separated.
Platform capability
Working foundation
Practice, patient and administration surfaces sit over a multi-tenant clinical core with workflow and audit foundations.
- Hosted practice, admin and patient portals
- Scheduling, encounters and clinical documentation
- Human-reviewed AI and workflow proposals
- Billing preparation and operational work surfaces
Operational proof
First reference deployment
Migration, reliability, support and transparent integration states are part of the pilot path, not details deferred until go-live.
- Repeatable end-to-end clinical journey
- Verified migration and cutover process
- Support, incident and release operations
- One paid production reference deployment
External dependencies
Certification and contracts
Production claiming, regulated connectors and partner-facing API contracts open only after their evidence and operability gates.
- Provider-real claiming and payment rails
- Identity and national record conformance
- Messaging and prescribing connectors
- Stable public contracts and partner operations
04 Distribution
Operate directly. Distribute when the model is proven.
One hosted clinical platform, with the commercial and technical boundary made explicit.
Hosted platform
Practices and healthcare organisations
Use OrionCloud's existing portals, configured and branded for your operating model.
- Practice and patient experiences
- Specialty workflow configuration
- Migration and implementation discovery
Qualified pathway
Distribution partners
Build a specialty channel with OrionCloud after commercial fit and production evidence are established.
- Phase one: branded hosted portals
- Future: stable public contracts and events
- No customer forks or internal API access
Public API is not offered as a phase-one capability.
05 Questions
Clear answers before a commercial conversation.
Who is OrionCloud for?
OrionCloud is being developed for Australian practices, healthcare organisations and qualified distribution partners that need one governed platform across practice operations, clinical work and patient access.
Is OrionCloud in production today?
OrionCloud is a late-pilot platform. The core product surfaces are substantially implemented, while the next commercial gate is a paid reference deployment that proves migration, reliability and support in real operations.
Are Medicare and other external integrations live?
External claiming, payment, identity, messaging and prescribing rails are not presented as production-connected by default. Their real, simulated, connector-dependent or certification-blocked status is confirmed during discovery and implementation.
Does the AI take clinical or operational action by itself?
No. AI-assisted documentation and workflow outputs are designed as reviewable proposals. Clinicians and authorised staff remain responsible for approving consequential actions.
Can a partner build directly on a public OrionCloud API?
Not in phase one. Qualified partners start with OrionCloud's hosted portals configured for their brand and operating model. A stable public API and event contract is a later, separately gated distribution tier.
06 Book a demo
Bring the real workflow.
We will show the relevant platform journey and name the gaps, dependencies and next decision plainly.
hello@orioncloud.com.au