For Australian medical practices
The front door for your inbound referrals
Clera is the front door for your practice's inbound referrals - specialist, GP or allied health. Every referral, however it arrives, lands in one queue, captured and sealed the moment it reaches the door, then drafted for your staff to approve. Nothing re-typed. Nothing lost.
- Administrative process-state only - performs no clinical triage
- Draft-first - nothing sent without human approval
- Australian data residency
- Synthetic demo - no real patient data
The problem
Referrals arrive everywhere except in one place
In Australia, a Medicare-rebated specialist visit needs a GP referral, typically valid for 12 months - so referrals are the growth pipe. Specialist, GP and allied-health practices alike take them in as a fragmented mix of email, HealthLink, fax and paper, then type them in by hand.
Four channels, no queue
Email to the practice address, HealthLink secure messages, fax and paper all land in different places. Industry estimates put fax use at 80 to 90 per cent of Australian healthcare organisations (PwC and industry estimates), so the mix is not going away soon.
Typed in by hand
No PMS auto-captures fax, email or paper referrals - they are scanned and re-keyed by hand, everywhere. That manual pile is slow, easy to lose, and invisible to any report that only reads what was already typed into the system.
New patients fall outside the rails
A new-patient referral is never auto-filed by any PMS - there is no existing record to match it to, even on electronic rails. On Best Practice it sits unallocated in Incoming Reports; on Zedmed, against a blank patient in the Results Inbox; on Genie and Gentu, as an unlinked patient.
The workers
A few focused workers, one front door
Clera is not a chatbot bolted to your inbox. It is a small set of focused workers, each with one administrative job, working the front door together. Each prepares the next step and hands it to a person.
Capture
Brings every referral into one queue- A dedicated referrals mailbox, a fax-to-email number and drag-and-drop upload
- Secure messages too - a HealthLink HL7 v2 adapter, built; secure messaging goes live once practice registration and Clera's own accreditation clear
- The original document is kept intact - nothing is silently dropped
Surface
Reads the admin, quotes the rest- Extracts the administrative fields and makes the text searchable
- Urgency is only ever the referrer's own words, quoted and attributed
- Arrival-ordered, never ranked - attachments are noted, not interpreted
Draft
Prepares the next administrative step- Drafts an acknowledgement to the referring practice, or a missing-information request
- Lays out a ready-to-enter card for your PMS, field by field
- Nothing sends without a person approving it, and every approval is sealed
Grow
Counts what actually arrived- A live map of where referrals come from, built from what reached the door
- Loyal, lapsed and never-referred practices - the space a PMS report cannot see
- Business intelligence about the practice, never clinical decisions about patients
Chain of custody - nothing lost at the front door
Four demo events for one referral, hash-chained with SHA-256 in your browser right now. Verify the chain, then tamper with one event and verify again - the break shows at the exact event.
This is a live demonstration of the same verification that runs in the product.
Works with the rails you already use
Built to speak the Australian rails
Clera stands where referrals arrive and speaks the messaging systems Australian practices already run on. It sits beside your practice management system - it does not replace it, and it starts on the channels a practice already controls.
Referral channels
Works alongside any PMS
What is honest here. The mailbox, fax and upload channels work from day one. The HealthLink adapter is built and ready; going live on secure messaging needs practice-level registration (about 4 to 5 business days) and Clera's own accreditation before real data flows. PMS compatibility is a property of the design, not a per-vendor integration - Clera relays into the same inbound channel every PMS already collects, so no vendor has to say yes. These are the rails Clera is built to speak, not a claim of live customers - Clera is a pre-launch concept running on synthetic data.
How Clera compares
A front-door agent, not a board you feed
Other tools touch referrals, but they sit in a different place. A tracker waits for you to type referrals in. An enterprise system waits for the GP to submit them electronically. A connected-care network waits for the GP to sign up and refer through the vendor's own portal. A PMS report only ever sees what was already entered. Clera stands at the door and captures what arrives - however it arrives - and it works for a single practice on its own, with no two-sided network to build and no GP asked to change how they refer.
Clera
The front-door agent
How referrals get in: captured automatically the moment they arrive - fax, email and upload from day one, HealthLink secure messaging once registration clears.
- Sits on the inbound stream - no manual entry, no drop-in, no paid add-on to read a document
- Works beside any PMS with no vendor permission, and seals every referral in a chain of custody
- Drafts an acknowledgement back to the referring GP, and sees the never-referred practices
- Administrative only - urgency stays the referrer's own quoted words
A referral tracker
A board you feed
How referrals get in: added or uploaded by hand - automatic reading is often a paid add-on.
- A drag-and-drop board to move a referral from received to booked
- Only ever knows the referrals someone remembered to enter
- No secure-messaging capture, and no view of who never referred
An enterprise or network platform
An integration project
How referrals get in: the referring GP submits electronically - into a deep systems integration, or through the vendor's own portal.
- Built around a PAS or EMR integration, or a cloud portal - typically a hospital-scale project
- Whether it is an integration or the vendor's portal, the referrer has to change how they send - fax, email and paper stay outside it
- Scoped to electronic referrals, not the mixed inbound reality of a private practice
A PMS analytics report
A report on what was typed in
How referrals get in: it doesn't capture - it reports on what staff already entered in the PMS.
- Dashboards over data already inside the practice management system
- Blind to anything that never got entered - the front door is invisible to it
- No capture, no drafting, and no chain of custody
This is a category comparison, not a claim about any one product. Clera is a pre-launch concept running on synthetic data. The point is the shape of the approach: a front door that captures automatically, versus a board you feed by hand, a project you integrate, or a report that only sees what was typed in. And where some tools add clinical triage, Clera deliberately does not - it stays administrative, keeps the queue in arrival order, and shows urgency only as the referrer's own quoted words.
Growth intelligence
See the referral base you actually have
Because Clera stands at the door, it counts every referral that arrives - not just the ones that were typed into the PMS. The same data layer that runs the queue answers the questions a practice owner actually asks.
Where referrals come from
Every referral counted at the door: which practice, which referrer, which channel, which suburb. A live map of the referral base, built from what actually arrived.
Loyal, lapsed, never-referred
Which nearby practices refer regularly, which have gone quiet, and which have never referred at all - the negative space a PMS-derived report cannot see, because it only knows what was entered.
Service mix
What kinds of work are being requested and how the mix moves over time, so the practice can plan capacity and see changes early.
The referrer loop
Close the loop with the referring GP
The enterprise systems built for hospitals lead with secure messaging and auto-acknowledgements. Clera brings that to a private practice's front door - draft-first, and only ever back to the referring practice. It is the difference between a referral that vanishes into a queue and one the GP knows landed.
Acknowledge receipt
The moment a referral lands, Clera drafts an acknowledgement to the referring practice - ready for staff to approve and send from the practice's own mailbox or secure messaging. The GP knows it arrived.
Chase what's missing
When a Medicare number or a date of birth is missing, Clera drafts the request back to the referring practice - never to the patient - so the gap is closed before the appointment, not at the front desk.
Administrative status, sealed
Received, acknowledged, filed - each step is a sealed event in the chain of custody. It is administrative status, never a clinical update, and it goes to the referrer, never the patient.
Works with your PMS
Alongside any PMS, including cloud
Clera does not replace your practice management system and does not need its permission to start. It sits beside the PMS, at the point where referrals arrive - before anything is entered.
No PMS permission needed
Capture runs on things the practice already controls.
- A dedicated referrals mailbox (Microsoft 365, Gmail or IMAP)
- Fax-to-email through Australian providers
- Drag-and-drop upload for paper and scans
- Works beside every PMS, including cloud-native ones
Ready-to-enter cards
Clera does not write into your PMS. Instead, staff get a ready-to-enter card for each referral.
- Clean, checked fields laid out to match data entry
- One-click copy, field by field
- The original document always attached
- Write-back is a later step that needs PMS vendor permission - we say so plainly
HealthLink adapter ready
HealthLink is the dominant GP eReferral rail, and Clera is built for it.
- An HL7 v2 REF adapter, built
- Going live needs practice registration (about 4 to 5 business days) and Clera's own accreditation before real data flows
- Mailbox, fax and upload capture work from day one either way
Your own secure instance
Cloud-managed, and yours alone
Clera is designed to run as managed cloud, with each practice given its own isolated instance - not a shared database with other practices' referrals in it. You run it from the desks you already have, signing in with the accounts you already use.
A private instance per practice
Clera is designed to give each practice its own isolated, Australian-hosted instance - single-tenant by design, cloud-managed and kept current for you, so your data is kept separate from other practices'.
Sign in with what you have
Designed for single sign-on with your existing Microsoft 365 or Google accounts, with multi-factor authentication - so staff log in the way they already do, and access follows the people who join or leave.
Every mailbox and site
Multiple referral mailboxes, several fax numbers and more than one location all feed the same queue - so a group with several sites or intake addresses sees one front door, not many.
Going live
From first connection to a sealed front door in week one
No rip-and-replace and no year-long project. Connect the channels the practice already controls, watch Clera work in the background, then switch the front door over when you are ready.
Connect the channels
Point a referrals mailbox and a fax-to-email number at Clera, and drop scans straight in. Minutes of setup, not an IT project.
Run in shadow mode
Clera captures and drafts beside your current process, so you can see it working before anything changes.
Verify the drafts
Read what Clera prepares, edit anything, approve what is right. Editing before approving is expected, not an exception.
Switch the front door
Every referral captured in one queue and sealed from the first fax. Add HealthLink secure messaging once registration clears.
The setup planner asks eight questions and builds your tailored timeline - IT request, go-live gates and all - in your browser in a few minutes. No sign-up, nothing sent anywhere.
The closure ledger
The closure ledger, quietly in the background
Most of Clera is about what arrives. The closure ledger watches what leaves.
For every billed specimen, the ledger expects a result, a review and a notification, and resolves each one to a single state, provable from the practice's own records. It is deliberately biased to UNKNOWN: when the evidence is incomplete it says so, rather than assuming the loop was closed.
This is a background assurance feature, not the product. It tracks whether the administrative loop closed - never what a result means. Administrative process-state only - Clera performs no clinical triage.
Where the evidence comes from. The ledger reads only the practice's own records - either a billing report the practice exports itself, or the pathology results that already arrive on Clera's inbound stream. It needs no live PMS integration and no vendor permission. Capture, surfacing, drafting and growth need no billing data at all.
Pricing
Pricing, plainly
The practice manager's first question, answered before the call.
- Setup and the initial capture scan are credited to your first month.
- A flat monthly fee - never a percentage of your billings.
- No lock-in: your data, including the sealed ledger, exports in full on exit at no charge.
Why practices stay
Honest limits
What Clera does not do, and where it can be wrong
Software at the front door of a medical practice should be plain about its failure modes. These are ours.
See it live
Walk the front door on synthetic data
The live demo is the full product surface running on synthetic referrals - no sign-up, nothing sent anywhere.
Wondering what setup looks like for your practice? The setup planner asks eight questions and builds your tailored plan - timeline, IT request and go-live gates - entirely in your browser.
The demo opens on Today. From there: Inbox is the one queue, Growth the referral intelligence, Practice the referrer book, Ledger the closure ledger, and Onboard the setup checklist.