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.
- Practice agreement and activation required - built, and used only for a practice whose agreement and activation enable it.
- 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
Section titled “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 and Practice analytics are available in the connected product. New workspaces open empty and patient-data capture remains off until connection checks pass. |
| Cancellation Fill | Setup checks required | The connected route and fail-closed approval gate exist. Real-patient use remains off until its separate privacy, legal and practice-operational approval is recorded. Detail |
| 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 proves it can read the chosen inbox and that its access stops there before new referrals start. No setup email needs to arrive. Detail |
| Gmail and other inbox providers | Not yet available | Refera cannot connect or configure these services today. Request access to record the connection your practice needs. |
| Fax-to-email | Setup checks required | A fax-to-email provider may deliver PDFs to the verified Microsoft 365 inbox. The mailbox and source-document checks must pass before patient referrals flow. Detail |
| 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 | Not yet available | Refera cannot connect or configure HealthLink today. Written partner assessment, the applicable technical profile and conformance process, interface-specific synthetic testing, and a reviewed reversible cutover remain required. Refera has no live SMD transport enabled and does not claim HealthLink conformance. Request access |
| Medical-Objects | Not yet available | It is the named secure-messaging rail after HealthLink and is not connected. Detail |
| Outlook draft creation and sending | Not yet available | Refera currently provides copy-ready text only. It does not create Outlook drafts or send email. Any future option requires separate mailbox-scoped approval and a named person approving every send. Read-only capture never grants writing or sending. |
| EMR write-back | Not yet available | It requires EMR vendor permission. Today, staff copy the ready-to-enter details into the EMR. Detail |
| AI-assisted administrative extraction | Practice agreement and activation required | Recovered referral text only, never images. Rules run first; below the confidence threshold, Amazon Bedrock uses Haiku 4.5 and at most one Sonnet 4.6 attempt for an invalid result or unresolved core fields. Sydney runtime entry; Australian inference profiles (au.*) in Sydney and Melbourne. Administrative fields only; no clinical triage. Detail |
| Refera Intelligence | Not yet available | Planned add-on. Enabling administrative extraction does not enable that add-on. Any future Intelligence service requires its own agreement, activation and Australian processing, privacy and feature-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
Section titled “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.
Administrative process-state only - Refera performs no clinical triage.
Examples are fictional and contain no patient information. Practice staff approve every external action. Refera never auto-sends or independently contacts patients.
Refera homeRequest practice accessOpen ReferaPrivacyTerms
[email protected]Product and setup support. The line uses an AI assistant; for a person, use the contact form or email.