Trust overview

Who this page is for: the practice manager doing diligence, and whoever they forward it to.

Refera handles health information for practices, so the standard is simple: every promise maps to an enforced control, every legal claim maps to an Australian statute, and every stage of maturity - certification included - is stated with its real status. Real-data processing, including AI-assisted extraction, requires the practice’s agreement and activation. This overview is not an executed data processing agreement.

The six promises

Promise	The enforced property
Australian data residency	The licensed portal, API and stored platform copies remain in AWS Sydney. Where a practice’s agreement and activation enable AI-assisted administrative extraction, Amazon Bedrock receives recovered referral text, never images, through its Sydney runtime endpoint and Australian inference profiles (au.*), with inference in Sydney and Melbourne. Detail
No clinical triage	Administrative process-state only - the extraction schema has no field a clinical judgement could occupy. Detail
Draft-first, always	A named staff member approves correspondence to patients or referrers and reviews information before entering it into the practice’s clinical record. Agreed and activated administrative extraction can run automatically; it does not send correspondence or make clinical decisions. Detail
No independent patient contact	No patient account or patient-facing Refera portal exists. Cancellation Fill prepares generic appointment copy only; staff approve, use the practice’s normal channel and record the outcome.
Export freedom	Structured tenant data and available sealed events export free. Object-Locked source-archive storage is deployed in AWS Sydney; complete source retention, retrieval and export remain unavailable until the lifecycle is proven end to end. Detail
Sealed audit trail	Every event is hash-chained with a server-held HMAC key. The export is not independently verifiable without the service-held key, and Refera does not claim a deployed write-once anchor. Detail

The deeper pages

• What Refera does and doesn’t do with your data - the short, exact answer.
• Handling health information: what your practice must do - APPs 1, 3, 5 and 6 in plain English.
• Security, breaches and the NDB scheme - APPs 10 to 13 and what happens if something goes wrong.
• No clinical triage - the position in plain language.
• Clinical prioritisation and regulation - Refera’s administrative boundary and the separate regulated-product pathway.
• Privacy and the APPs - all thirteen principles, each tied to a control.
• Data residency - what the AU-only commitment means precisely.
• Security posture - the architecture, the access model and the certification ladder.
• Sub-processors - the complete, deliberately short list.
• Breaches and state law - state health-records law, My Health Record, breach response.