Keep the systems you run. We connect them to one record.

HealthOS runs in your own cloud account in Australia, sits behind your identity provider, and connects the systems you already have to one care record.

What it connects

Government

Aged Care Web Services, the HI Service and GPMS, over PRODA and NASH certificates. Eclipse is in Notice of Integration testing with Services Australia.

Clinical systems

HL7 v2 in, a FHIR R4 and AU Core API out, with SMART on FHIR for apps.

Your data

CSV, SQL, SFTP and staging tables from the databases you already run.

In the field

A worker app that installs from the browser, works offline and syncs when back in range.

What changes for IT

Hosting, identity and integration you control

Your cloud, your keys

Each customer gets a single-tenant deployment in their own cloud account, onshore in Australia, with no co-tenancy. Data is encrypted at rest and in transit, sensitive fields are encrypted again, and the keys sit in your own key vault.

Sign-in through your identity provider, with MFA for admins
Row-level security on every query
Daily backups with point-in-time recovery

Integration without a consulting project

Build flows visually from source to transform to destination. Transforms can be written in Python and go through an approval step. Flows run on a schedule or a webhook, with connectors for SFTP, HTTP, document libraries, databases and object storage.

A rostering connector in the admin portal: healthy, with its ingress pipeline into the canonical data model, the filters either side and its recent activity.

Matching people you can trust

Records are matched on Medicare, IHI, MRN and DVA numbers first, then on name and date of birth, with a confidence score and a review queue for anything uncertain. Write-back to source systems is two-way and loop-safe, and a parallel-run mode lets you migrate in stages.

Hospitals

Hospital feeds, and the paper that’s left

HL7 v2 messages from a hospital’s existing systems are routed to the right facility by its receiving facility code, so one connection can serve several hospitals. Multifunction devices scan to a share HealthOS reads, and each scan is filed to the episode or encounter number in its filename, or held in a scan inbox for someone to file.

Set up an organisation in an afternoon

A guided assistant sets up your organisation, its sites and its structure. Roles and permissions follow the structure, so access matches who people work for.

The onboarding assistant setting up a new organisation.

AI in your own tenancy

Choose the language model you want, run it in your own tenancy, and records are de-identified before any model sees them. We follow the Australian Privacy Principles and the Essential Eight. We are building toward ISO 27001 and are not certified yet.

On YouTube

See it in action

All videos

Integration: connectors and the integration topology

Elsewhere in the care circle

In the boardroomNumbers you can trace back to the care. In the back officeClaims built from care already recorded. On the audit trailQuality reporting from the care record, kept for seven years.

Bring your architect

We’ll go through hosting, identity and the integration map with your team.