Capability status

This page is a capability register, not a live incident feed. For service availability and incidents, use status.refera.au.

• Available - enabled in the connected product.
• Setup checks required - built, but patient-data capture stays off until the named connection and service checks pass.
• Not in the connected product - evaluated design work that is not a licensed product route.
• Not yet available - not available to practices.
• Outside current product - not a Refera capability or release commitment.

The sequencing rule is simple: Refera claims a capability only when it is built, and claims patient-data capture only after its launch checks pass.

Capability register

Capability	State	Exact boundary
Public site and account setup	Available	A practice can create an account, prove its work mailbox, accept the exact terms and enter a guided empty workspace.
Connected console	Available	Inbox, practitioner worklists, Settings, Practice analytics and Cancellation Fill are available in the connected product. New workspaces open empty and patient-data capture remains off until connection checks pass.
Extended Growth, relationship, geography and standalone closure-ledger views	Not in the connected product	These are not routes in the licensed product, and since the 20 Aug 2026 homepage redesign the public website no longer previews a relationship map; it is not a live console view. Current Practice analytics is the available aggregate surface.
Microsoft 365 mailbox	Setup checks required	Choose the inbox and ask your Microsoft 365 admin to approve access. Refera then checks the chosen inbox, blocks another inbox and receives a test email with no patient information before new referrals start. Detail
Gmail, IMAP and fax-to-email	Setup checks required	Connector-specific checks and the complete source-document lifecycle must pass before patient referrals flow.
Secure upload and direct scanned-document capture	Not yet available	These direct capture routes are not enabled in the connected product. A scanner can still deliver to a verified email inbox. Detail
Patient referral data	Setup checks required	Practice, workspace and service checks must pass. Archive infrastructure is deployed; complete source write, readback, restore, export and tenant-isolation verification remains required. Detail
HealthLink	Setup checks required	Not connected. HealthLink’s written partner assessment, the applicable technical profile and conformance process, interface-specific synthetic testing, and a reviewed reversible cutover are required. Refera has no live SMD transport enabled and does not claim HealthLink conformance. Detail
Medical-Objects	Not yet available	It is the named secure-messaging rail after HealthLink and is not connected. Detail
Optional Microsoft 365 sending	Setup checks required	Separate Owner addendum, mailbox-scoped Application Mail.Send, positive and negative scope checks, and explicit staff approval for every send. Read-only capture never grants sending.
EMR write-back	Not yet available	It requires EMR vendor permission. Today, staff copy the ready-to-enter details into the EMR. Detail
Refera Intelligence	Not yet available	It is not sellable or active for referral data. Any future path remains administrative-only and must pass the Sydney Bedrock and patient-data readiness checks. Detail
AI clinical prioritisation	Outside current product	Refera does not prioritise referrals clinically. Any separate future proposal would need its own intended-purpose assessment and applicable TGA pathway before development, pilot use or supply. Product boundary
Formal certifications	Not yet available	Refera names a certification only after it is earned and links the evidence. Detail

Operational status

Account setup and the connected console are available. Patient-data capture stays off until the selected connector and service checks pass. Live availability and incidents are reported separately at status.refera.au.