Private beta · Australian clinics

The operating system for the modern clinic.

One connected platform for the whole practice — booking, the patient chart, prescribing, dispensing, payments, intake, documents and automation. Australian-hosted, private by default, and configured by your own team — not a developer.

Built by clinicians, for their own clinic.

app.patientos.com.au
The PatientOS Today dashboard — appointments, open tasks, overdue items and the day’s schedule for the whole clinic at a glance.
Australian-owned & operatedHosted in AustraliaPrivacy Act 1988 & the APPsBuilt by clinicians

01·The problem

A clinic runs on a drawer full of tools that don’t talk to each other.

Most practices don’t have one system. They have a stack — and the gaps between the parts are where the time, the money and the mistakes go.

01

Stitched together

Booking in one app, the record in another, dispensing, payments, letters and reminders all bolted on — none of it talking to each other.

02

Re-keyed and stale

The same patient typed into four systems. Lists that are out of date the moment you look away. The front desk always a step behind.

03

Frozen in place

Every change is a vendor request or a developer ticket. You wait weeks to alter a form, a price, or a reminder you should own.

02·One platform

Everything the clinic does, on one spine.

Every part of a practice resolves to a small set of composable primitives. PatientOS is built from them — so booking flows into the chart, the chart into prescribing, prescribing into dispensing, payment and the document, with nothing re-keyed in between.

  1. 1Booking
  2. 2Chart
  3. 3Prescribing
  4. 4Dispensing
  5. 5Payments
  6. 6Documents
  7. 7Tasks
  8. 8Automation

It’s one system, not an integration. Each capability is configuration of a maintained product — not net-new code, and not another subscription to reconcile.

03·What it does

The staff workspace, already built.

Built and working in private alpha. The screens below are the product as it stands today — ahead of our first clinics going live.

app.patientos.com.au
The PatientOS patient chart — demographics, appointments, scripts, documents and tasks for one patient in a single view.

The patient chart

Everything about a patient — appointments, scripts, documents, tasks — in one master-detail view.

app.patientos.com.au
The PatientOS dispensing queue — fills ready to dispense, with pickup and ship handled from one list.

Dispensing & fulfilment

Scripts become fills become dispenses — pickup and post, paid at the gate, from one queue.

Live

Booking that lands in a real slot

Book a practitioner × appointment type into a confirmed slot against live availability. Leave, capacity and recurring hours are respected automatically — no double-booking while a doctor is away.

Live

Intake that writes to the record

Branching question sets — pre-consult, eligibility, consent — whose answers bind straight onto the patient or appointment. No re-typing what the patient already told you.

Live

Script → fill → dispense → paid

The whole medication spine in one flow, with card capture authorised at the gate — pre-auth, 3DS and capture, gateway-agnostic. Pickup or post, handled from one queue.

Live

Letters that write themselves

Design a letterhead, drop in merge fields, and referrals, consent forms, clinical letters and invoices come out as finished, verifiable PDFs — generated, never hand-typed.

Live

One register, front counter to post

A staff point-of-sale with live catalogue, barcode scan and customer-attach at checkout — walk-ins and pickups handled right alongside online dispensing.

Live

Automations that just run

Reminders, no-show reschedules, repeat-due chases, limit tracking — clinic policy compiled to durable triggers and timers that fire without anyone remembering to.

04·Configure it yourself, safely

How your clinic runs is yours to own.

Most systems make you log a ticket and wait. PatientOS hands the whole system to your staff: appointment types, intake forms, care pathways, pricing, letterheads, roles — even which modules are switched on — all edited in-app by your own admins.

1
Describe it in plain English
“Remind no-shows after 24 hours.” “Flag a patient who has called three times.” No rules editor, no developer — just say what you want.
2
Review before it goes live
Every change stages into a draft first — see exactly what will change, side by side with what is live, and publish the whole set together when you are ready.
3
Promote it live
Happy with it? Publish. Configuration of a maintained product — owned by you, exportable in full, never locked in a black box.
AI assistant · Alpha
app.patientos.com.au
The PatientOS workflow editor with the Ask AI assistant drafting an automation from a plain-English request: when a controlled-substance script is dispensed, raise a pharmacist review due in 24 hours.

“When a controlled-substance script is dispensed, raise a high-priority pharmacist review due in 24 hours.” — and the assistant drafts the live workflow for you.

05·Australian & private

Your patients’ data stays in Australia.

PatientOS runs on Australian infrastructure, and patient data at rest stays in the country — handled under the Privacy Act 1988 and the Australian Privacy Principles. Privacy is the default, not an add-on, and not a setting you have to remember to switch on.

  • Hosted on Australian infrastructure — PHI at rest stays in-country (APP 8).
  • Built around how Australian primary care actually runs — not a US clinic translated.
  • Your configuration and your data are exportable in full, any time. No black box.
Australia rendered as a network of cyan data points, with Sydney and Melbourne lit and linked — patient data hosted in Australia across two regions.

Data residency, by default

Sydney · Australia · APP 8

06·Who’s building it

Built by the people who run the clinic.

PatientOS is built on PocketDoc’s own clinic by its two founders — a UK-trained GP and a senior engineer. Clinical judgement and the build, in the same room.

Dr James Ayres, Co-Founder and CEO of PocketDoc
Clinical leadership

Dr James Ayres

Co-Founder / CEO

A UK-trained GP based in Canberra, with experience across general practice, men’s health and chronic disease care.

Tim O’Connell, Co-Founder and engineer at PocketDoc
Product & engineering

Tim O’Connell

Co-Founder & engineer

Designs and builds PatientOS himself — decades spent helping teams make good technology decisions, now doing the same with AI, shaped by how a clinic actually runs day to day.

“PatientOS isn’t briefed out — it’s software I design and build myself. That’s why it holds together as one system, instead of a pile of features that don’t quite meet.”

— Tim O’Connell, Co-Founder & engineer

07·On the roadmap

Not a commitment — a direction.

PatientOS is under active development. These are the angles we’re planning to grow into — the national rails, connected prescribing, and more of the busywork handled for you.

Planned

Medicare, DVA & national rails

Claim, report and verify through PRODA — the immunisation register and My Health Record — without leaving the chart.

Planned

Electronic ordering & results

Send pathology and imaging requests electronically and have results land back on the patient’s timeline, not a paper tray.

Planned

Connected prescribing

eScripts, the active script list and real-time prescription monitoring, with interaction checking built into the prescribe step.

Planned

Build your website by describing it

Describe the page you want and it lays out a branded, bookable site wired straight into your live clinic. No agency, no separate CMS.

Planned

A voice assistant you can talk to

Ask what’s on today, pull a patient’s history, draft a task — answered out loud, with anything irreversible left for you to confirm.

Planned

A full public API

A complete, documented API over your whole clinic, so you — or anyone you choose — can build integrations on top of PatientOS.

08·Request access

Bring your clinic into the private beta.

We’re onboarding Australian clinics gradually and hands-on. Tell us a little about your practice and we’ll be in touch when a spot opens up.

  • Hands-on onboarding — we set up alongside you
  • No commitment — register your interest
  • Your data hosted in Australia from day one

By registering you agree to our privacy policy. We’ll only use your details to contact you about the PatientOS beta.