Concept · synthetic data

For Australian specialist practices

The front door for your inbound referrals

US intake vendors report referral handling falling from about 15 minutes to under 2 per referral once capture is automated (vendor-reported). Clera is the front door for a specialist practice's inbound referrals: every referral - secure message, email or fax - lands in one queue, captured, searchable, and acted on draft-first by your staff.

  • Administrative process-state only - performs no clinical triage
  • Draft-first - nothing sent without human approval
  • Australian data residency
  • Synthetic demo - no real patient data
However it arrives, it lands in the same queue Email HealthLink Fax Paper, scanned or uploaded

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. Referrals are the practice's growth pipe - and they arrive as a fragmented mix of email, HealthLink, fax and paper, then get typed 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 manually, everywhere. US intake vendors report per-referral handling falling from around 15 minutes to under 2 (vendor-reported, Medsender); one estimate puts manual intake near US$47,000 a year per clinic (ReferralMD).

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 person a referral is about is exactly the person your PMS does not know yet. That is why the front door matters: the highest-value document in the practice is the one most likely to be handled by hand.

What Clera does

Capture, one queue, verbatim surfacing, draft-first action

Clera stands at the front door. It captures what arrives, keeps it in one place, shows the referrer's own words, and drafts the admin work for your staff to approve. Every step is recorded in a sealed chain of custody.

1

Capture

A dedicated referrals mailbox, a fax-to-email number and drag-and-drop upload. Everything inbound is captured with the original document kept intact.

2

One queue

Every referral in a single queue, whatever the channel. Text is extracted and searchable; channel, age and attachments are visible at a glance.

3

Verbatim surfacing

Urgency is only ever the referrer's own stated words, quoted and attributed - never a Clera judgement.

referrer wrote: “please see urgently”
4

Draft-first actions

Acknowledge the referrer, route to the right list, chase missing information, and a ready-to-enter card for your PMS. Nothing sends without a person approving it.

5

Sealed chain of custody

Every event - received, captured, approved, filed - is hash-chained the moment it is recorded. Nothing can be backdated or quietly edited.

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.

01 · referral received · fax via fax-to-emailseal …
02 · captured · text extracted, original attachedseal …
03 · acknowledgement approved · staff sign-off recordedseal …
04 · filed · ready-to-enter card completedseal …

This is a live demonstration of the same verification that runs in the product.

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.

Business intelligence about the practice, never clinical decisions about patients. For an established practice this is capture integrity and service mix; for a new practice it is how the referral base gets built.

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 and ready
  • Registration is practice-level and takes about 4 to 5 business days
  • Mailbox, fax and upload capture work from day one either way
Analytics that reads from your PMS can only see what was typed into it. The front door sees everything that arrives - including what never made it in.

The safety net

The closure ledger, quietly in the background

Most of Clera is about what arrives. The closure ledger watches what leaves.

billed specimen → result → review → notification

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.

ClosedResult on file, review evidenced, notification recorded.
OpenSomething is still outstanding. It stays on the list until it is not.
UnknownThe records do not prove closure either way. Flagged for a person - never assumed closed.

Pricing

Pricing, plainly

The practice manager's first question, answered before the call.

Single practice
A$1,500 to A$3,000
per month
Multi-practice groups
A$3,000 to A$5,000
per month
  • 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

A sealed history that accumulates Every month of chain-of-custody is audit evidence that cannot be recreated after the fact. It only builds here.
Intelligence that deepens Loyal, lapsed and never-referred views sharpen with every month of referrals counted at the door.
Export freedom, always Everything exports in full, free, whenever you choose - so staying is a decision, never a trap.

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.

Text extraction misreads things. Faxes are grainy and handwriting is hard. Extracted fields are always shown beside the source, and the original document is always attached - it is the record, not our reading of it.
Some documents will not parse. When capture cannot make sense of a document, it stays in the queue marked needs review. It is never silently dropped and never silently guessed at.
Drafts can be wrong. That is why nothing is sent without a person approving it, and every approval is logged in the sealed chain. Editing a draft before approving is expected, not an exception.
Clera reads process, not meaning. It performs no clinical triage: it does not compute, infer, rank or flag clinical urgency, acuity or diagnosis. Urgency appears only as the referrer's own quoted words. Attachments are noted, not interpreted.
UNKNOWN is an answer. In the safety net, when the records do not prove closure, Clera says UNKNOWN and flags it for a person. It refuses to guess.
Synthetic data only, for now. Everything shown here and in the demo runs on synthetic data. Before any real patient data: privacy compliance, data processing agreements with practices, insurance, and regulatory counsel sign-off. Clera never contacts patients.

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.

About the technology. The demo runs entirely on synthetic data in your browser. Every event is recorded in a hash-chained log sealed with SHA-256 - the same verification you can run in the chain-of-custody demo on this page. The product is designed for Australian data residency, with a draft-first action pipeline: Clera prepares, a person approves.