Clinical AI Solutions · Integrations

We meet each system the way it actually works

Australian health runs on a small number of systems, and every one of them takes a write differently. We connect to each the way its vendor permits — through the gateway where a gateway is mandated — and we say plainly which connections are live.

No second copy of your record Your credentials, your consent
What we connect to

Six kinds of system, one way in

Ask and we will tell you exactly what we support for the systems you run.

Hospital records

Public & private health services

  • Reads and writes through your existing integration layer
  • Standard clinical interfaces where the vendor offers them
  • Message-based interfaces where it does not

Practice software

General practice

  • Through each vendor’s permitted path, including mandated gateways
  • Documents delivered the way the system can receive them
  • Recalls reconciled with the list already in your system

Booking platforms

The front door you already pay for

  • We work the cancellations, waitlists and recalls it does not reach
  • Patient-facing messages go through it, not around it
  • We do not compete with it

Labs, imaging & pharmacy

Results and medicines

  • Results read in context, including the unacknowledged ones
  • Medication lists with the change and the reason beside it
  • Codes checked against the current Australian list

National rails

Government and payer

  • Medicare, the Healthcare Identifiers Service, My Health Record
  • Held in a separate credential perimeter from everything else
  • Under your own registrations — we never automate a portal

Secure messaging

Clinician to clinician

  • Letters and referrals delivered into the inbox a clinician uses
  • Delivery reported as delivered, not as filed
  • Nothing sent that a person has not approved
How a connection is made

Four steps, and the clinic owns all of them

1 · The clinic authorises

On a consent screen that names who is asking, for what, and for how long.

2 · Credentials are held once

In one vault, under your own registrations. Nobody pastes a password into a product.

3 · The connection is tested

A live check before anyone relies on it, with a plain-language result if it fails.

4 · Revocation is normal

Revoke from inside your own software; cached data for that connection is purged.

Where this is today

Integration work is in build. The first connections are the major hospital records and the main general-practice systems, reached the way each vendor permits. We will tell you which are in production and which are in sandbox before you commit to anything — and if your systems cannot support a capability, we will say so on the first call rather than after you have signed.

Ask about your systems

Tell us what you run, and we will tell you what is possible

A short call, before a demonstration: which of your systems we can read from, which we can write to, and what that means for each agent.