Everything a practice does between the appointments
13 capabilities, one operational layer. First, one patient's record moving through all of it. Then every capability, in detail.
One patient, start to finish
Follow one record through a practice — what arrives, what is added, and what MedOS does on its own along the way.
01 / 07
A referral arrives
By e-fax, email, secure messaging or upload, it lands in one queue, is classified as a referral, and is matched to the patient — or the record is created from it when they are new, with duplicate detection at the door. Where a practice has an OCR provider, scans are read on the way in. Reception can create the patient directly, and other systems can through the API.
Priya Nair
MRN 004821 · DOB 12 Mar 1961
- Source
- E-fax · classified as a referral
- Patient
- New record · no duplicate found
- Referrer
- Dr A. Grant · provider number attached
- 01
A referral arrives
By e-fax, email, secure messaging or upload, it lands in one queue, is classified as a referral, and is matched to the patient — or the record is created from it when they are new, with duplicate detection at the door. Where a practice has an OCR provider, scans are read on the way in. Reception can create the patient directly, and other systems can through the API.
- Source
- E-fax · classified as a referral
- Patient
- New record · no duplicate found
- Referrer
- Dr A. Grant · provider number attached
- 02
The appointment is booked
Choosing the category sets the length. The calendar checks the room, the device and the clinician before it accepts. The intake form and a payment request go to the patient as a secure link, and the answers land on the record.
- Booking
- Echocardiogram · Thu 14 May, 9:40 · Room 2
- Intake form
- Sent by SMS · completed
- Payment request
- Paid
- 03
The procedure happens
The procedure is its own record under the patient, carrying the fields this practice defined. The clinician's note is permissioned separately from admin notes, and a dictation from the app attaches to it. If something is prescribed, the script is checked against the PBS and the legal particulars as it is written.
- Procedure
- Echocardiogram · Dr Tan · Echo 1
- Clinical note
- Dictated on the app · attached
- Prescription
- 1 item · PBS · particulars checked
- 04
Data comes back, rules run
The report is confirmed. A pathology result arrives in the Inbox, is typed, and is filed against the procedure. A rule the practice wrote — when the report is confirmed, only if there is a referrer, then mark it ready and tell the letters team — runs on its own. The letter is signed and delivered through Medical Objects.
- Result
- Pathology · filed to the procedure
- Rule ran
- Report confirmed → ready to send
- Letter
- Signed · sent via Medical Objects
- 05
It gets paid
Eligibility was checked before the visit. The item numbers and the billing rule were already on the procedure, so the claim is validated and lodged from it, the remittance comes back against it, and whatever the claim did not cover becomes an invoice with a payment link.
- Eligibility
- Verified before the visit
- Claim
- Lodged · remittance received
- Invoice
- Gap · paid
- 06
The patient is asked
A follow-up survey goes out by email, and the answers come back to the practice — so what patients say sits beside what was done.
- Survey
- Sent by email · answered
- 07
The episode closes
The procedure is marked complete. Every step above is in the activity log with the person who made it, every document is filed by type, and reporting already has the numbers. No export, no reconciliation, nothing typed twice.
- Status
- Complete
- Activity log
- 23 events, each attributed
- Reporting
- Counted the moment it closed
The clinical day
The records and the schedule the practice works from.
Patient records
One record that holds the whole story
Everything about a person sits in one place — demographics, insurers, alerts, documents and every procedure they have had. The record carries the fields your practice actually uses, not the fields someone else decided you need.
Scheduling
A calendar that understands a clinic
Day, week and month views that regroup between clinicians and locations with one toggle. It knows about rooms, devices, buffers, blocked time and opening hours — so the bookings it accepts are bookings you can actually deliver.
The MedOS app
The clinic, in a pocket
The work that happens away from a desk — between rooms, at the bedside, across sites — on a phone, against the same records as everything else.
Correspondence and prescribing
What comes in, what goes out, and what is prescribed.
Inbound correspondence
Every referral and result in one queue
Documents arrive from several places and are worked in one. Each one is triaged, matched to a patient, filed against the right procedure, and logged — so nothing sits in a mailbox someone forgot to check.
Letters and referrals
Correspondence that leaves properly signed
Write from templates on your own letterhead, sign with the signature held on the doctor's profile, and send. A signed letter cannot be quietly edited — corrections are their own document, which is what makes the record trustworthy.
Prescribing
Prescriptions that hold up to the rules
A prescribing module built on the national drug data, with the legal particulars checked as you write. It knows PBS quantities and repeats, authority levels, active-ingredient prescribing and Schedule 8 — and it warns rather than silently deciding anything a prescriber should judge.
Electronic prescriptions
Built to the conformance profile, ready to switch on
The electronic prescription path is built into the prescribing module and waiting on the approvals every vendor has to complete. The record structure, the medicine coding and the lifecycle are already in place, so enabling it is a connection rather than a rebuild.
Built, pending approvals
The business
Getting paid, and knowing where the practice stands.
Billing and claiming
From the procedure to the money, without re-entry
The procedure already knows the item numbers, the insurer and the fee, so the claim and the invoice come from it rather than from someone retyping it. Eligibility is checked before the service, not after the rejection.
Forms and documents
Paperwork that fills itself in
Design the forms your practice sends, deliver them by email or text, and have what the patient enters arrive on the record instead of in someone's inbox to be retyped.
Reporting
The numbers, without the export
Operational and financial reporting across patients, procedures, invoices and claims, so the questions a practice asks every week have an answer that is already current.
The platform
How MedOS bends to your practice and connects to the rest.
Automation
The admin between the care, done for you
A rule reads: when something happens, only if certain things are true, then do these things. That is the whole model. No scripting, no deployment, and a dry run against a real record before anything goes live.
Integrations
Made to sit alongside what you already run
MedOS is the operational layer, not a replacement for your clinical systems. It connects to what is already in place and makes those systems more useful rather than asking you to retire them.
Enabled per practiceConfiguration
Shaped to your practice, without a developer
The parts of a healthcare business that differ between practices — fields, statuses, roles, services, devices — are configuration rather than code. That is why MedOS fits a pathology network and a physio clinic without becoming two products.
Ready to make healthcare run better?
MedOS helps healthcare organisations connect fragmented operations, reduce manual admin, improve visibility and deliver a smoother patient journey.