Who can see a case, and what happens to what you add.
Written for clinicians and for the people whose job is to say no. We publish status, not promises: if something is not in place yet, this page says so.
Pilot stage · status as of September 2026 · updated as it changes
The care team sees the case. No one else does.
Access is decided by the case, not by a shared folder. Inviting someone to a case gives them that case — its discussion, evidence and recordings — and nothing else.
In place today — and planned.
- Case-level access
Only people invited to a case can open it — its discussion, evidence and recordings. Every clinical request checks case membership. Mextt administrators can open a case only to support you, and every such access is recorded.
- Removing someone ends their access
The case owner or a surgeon on the case can take someone off it; their access ends immediately and old invitation links stop working.
- Separation between organisations
One hospital’s cases are never visible to another. Verified with two-organisation testing.
- Signed-in media
Recordings and files are streamed only to signed-in members of the case’s care team; an anonymous request is refused.
- Roles
Surgeon, consultant, resident, coordinator, observer. Roles limit who can invite others; invitations expire.
- Audit trail
Who opened a recording, and who changed, shared or deleted what — with the person, time and address. Append-only.
- Deleting means deleting
Removing material deletes the stored file (every version), its copies and what was derived from it.
- AI labelled, clinicians never overwritten
AI drafts and suggestions are marked as AI until a clinician edits or confirms them. AI never overwrites a clinician’s edit.
- Notifications without patient details
A phone notification says only what happened (for example, that you were mentioned) and the case number — nothing about the patient.
- Encryption
All traffic uses TLS. Stored recordings and files are encrypted at rest by the storage provider; database backups are encrypted.
- Synthetic demonstrations
Every case, person and recording on this website and in demos is invented.
- Encryption of the application server’s disk caches and of transcript fields
- Enterprise single sign-on and directory integration
- India-region data residency (today: application servers in the EU, stored recordings and files in a US region)
- Consent tiers for teaching use, enforced in the product
- Configurable retention and data-subject-rights workflows
- Formal certifications and agreements (e.g. HIPAA BAA, SOC 2, ISO 27001) — none held today
We do not claim HIPAA compliance or any certification today. If your institution needs a specific agreement for a pilot, ask — we will tell you plainly what is possible.
Every service that touches case content, and what it receives.
| Service | Used for | What it receives |
|---|---|---|
| Deepgram | Speech-to-text | The audio of voice notes and dictations, and the sound track of uploaded operative recordings — to transcribe what was said. Zero retention: we opt out of Deepgram’s model-improvement programme on every request. |
| Anthropic (Claude) | AI drafting and questions | Text only, after identifiers are removed on our server: patient and clinician names, record numbers, dates and hospitals become placeholders. If removal cannot run, nothing is sent. |
| Oracle Cloud (OCI) | Storage | Recordings and files, stored in object storage (currently a US region) and served only through the application, to signed-in members of the care team. |
| LiveKit | Live calls | The audio of a “call the case team” session while it happens. |
| Browser push services | Notifications | A notification that says what happened and the case number — no patient details. |
Raw transcripts stay on our servers for the care team. AI output is stored with a record of where it came from and stays labelled until a clinician edits or confirms it.
Not a medical record
Mextt sits alongside your EHR and PACS. The formal record stays where it is.
Not an AI doctor
It organises and retrieves. Clinicians make, and remain responsible for, clinical decisions.
Not for real patients in demos
Everything you see on this site and in demonstrations is synthetic.
Security questions before a pilot?
Send your questionnaire. We answer with the architecture and the data flow as they are — in parallel with the pilot conversation.