Run the practice. Not your colleagues' consults.
A practice administrator needs to know who is set up, what the practice's defaults are, and that the promises hold. None of that requires reading a clinical note. Akoua's organisation console is built around that line — and it draws it in the product, not in a policy document.
An invitation is a credential, and it behaves like one.
Give an address and the invite is bound to it — nobody else can redeem it, even holding the link. Leave it blank to hand a code over in person instead.
The code is displayed when it is generated and only its hash is stored. Losing it means issuing another — it can never be read back out of the system, by anyone.
Revoking stops the link immediately. The invite is kept rather than deleted, so who issued it, who revoked it and why all stay legible afterwards.
You can administer a practice without reading its consults.
Administration and clinical content are different permissions, and the console keeps them apart. Where an administrator genuinely needs to open content, the act is recorded and the clinician can see it — so the boundary is observable by the person it protects, not just asserted to them.
Who recorded, when, how long, which mode, whether a note was confirmed and whether audio is still retained. Not a word of the consult itself.
Reading clinical content writes an audit entry naming who read it. The clinician sees that entry. There is no quiet look.
Commercial access is granted separately from day-to-day administration, so running the roster does not hand someone the invoices.
Decide once, for everyone, and say what is locked.
Processing modes, consent, retention, shared templates and your letterhead are set for the practice rather than negotiated per clinician. Where the platform holds a setting above you, the console marks it as locked instead of pretending it is yours to change.
Audio is deleted by default — kept encrypted only while you review and deleted the moment you confirm the note; a practice can instead set immediate deletion or a short fixed retention window, and every mode sits under a hard 7-day ceiling. On AU Sovereign, everything stays in Australia: transcription and note drafting run on vetted Australian services over private links inside Akoua’s cloud — disclosed on every note, under the consent your organisation gives for that processing. Ordinary consent to record is a separate authority, given for each consultation. Who’s speaking is recognised only on Akoua’s own infrastructure, and nothing is processed outside Australia without a separate, explicit request for that specific session. Clinical data is never used to train models.
Share note and letter templates across the practice and set the default one. Your address, letterhead and logo live with your letters, so what a patient receives looks like it came from you.
Compliance you can read, rather than assurances you're given.
Every row on the compliance page is a live read of the running system — encryption at rest, consent captured before recording, the append-only guard on the audit trail, retention and deletion evidence. Not a checklist someone ticked. Where a check cannot be answered right now, it says so instead of passing.
Filter by the question you're actually asking — who read clinical content, who changed our policy, who signed in, what was exported — rather than by an action name you'd have to know. Export it as CSV; the export is itself recorded.
One month at a time: recorded consults, recorded minutes, consent capture and confirmed notes, per clinician and in total. Counts only — every number traces back to the sessions list. Exports as CSV.
We say “integrated” only when it actually is.
Cliniko, yes — Australian practices can connect it today, choosing the appointment and patient each time, with nothing written back until you confirm. Nookal is currently disabled ahead of its activation approvals. Everything else still exports as clean text and PDF you paste or attach: Best Practice, Medical Director, HealthLink, Medical Objects and My Health Record are on the roadmap, and we’ll say “integrated” only when it actually is.
Per seat, one billing cycle for the practice.
Seats are a purchased quantity, not a headcount that creeps — the console shows how many are occupied against how many you bought. Pricing, tax treatment and annual terms are on the pricing page.