Where does the encounter's audio go?
During a sales demo, almost every AI scribe produces a neat note from a calm conversation. What truly separates two tools is invisible in the text formatting: it comes down to what happens to the patient's and clinician's voices during and after the visit.
When Dr. Martin and the clinic coordinator of a fictional family medicine group (Saint-Laurent FMG) interview vendors ahead of a pilot, they hear three very different answers:
| Vendor's answer | What happens technically | Impact on your practice or FMG |
|---|---|---|
| 1. “Audio is kept for playback” | A full voice recording is stored inside your cloud account. | Creates an archive of intimate clinical recordings that must be secured, governed, and produced on access requests. |
| 2. “Audio is deleted after processing” | An audio file is written to cloud disk first, then removed by a cleanup job later. | Leaves a disk-persistence window you have to verify across storage buckets, logs, and backups. |
| 3. “Audio is never written to disk” | Voice is streamed and transcribed strictly in volatile memory (RAM), then discarded. | 0 seconds of stored audio on disk—neither during nor after the encounter. |
Ask for the exact written architecture rather than a generic “everything is encrypted.” In Silenoa, no audio file is ever written to disk (0 h stored audio).
How long is the note kept?
For a physician or nurse practitioner charting in MYLE, Omnimed, OSCAR, or Cristal-Net, the EMR is already the official medical record. When an external scribe keeps every generated note indefinitely in its own portal, your clinic quietly builds a second shadow patient chart outside the EMR.
That duplicate record creates two practical problems: it doubles the footprint of clinical data to protect, and it drifts out of sync whenever you edit a nuance inside your EMR right before signing.
To review this architecture alongside your privacy officer, read our white paper Transient draft: why your EMR stays the only chart.
Who signs?
Between a tool that forces four manual copy-pastes per visit and one that claims to finalize notes unattended, there is a clean medico-legal line: the tool fills the draft boxes, and the physician reviews and signs inside the EMR.
During a live vendor demo, ask to watch the handoff into a simulated EMR screen from start to finish without jump cuts:
- Targeted field injection: does the Chrome extension populate Subjective, Objective, Assessment, and Plan into the open EMR tab in 1 click?
- Hard stop before signing: is the extension strictly prevented from clicking “Sign” or “Save” on your behalf?
- Consent lock and traceability: does the microphone stay locked until informed verbal consent is ticked, and is a traceability footer added automatically?
The diagram below shows that exact split: automated field placement on the left, clinician review and signature on the right.
On the left, the tool fills the EMR boxes. On the right, the physician clicks “Sign”.
Where are the servers?
“Where are your servers?” is really three separate questions, because the web application, the database, and the AI inference endpoint do not always sit in the same jurisdiction.
- End-to-end Montréal residency: do application servers, the encrypted database, and AI processing all run in Montréal (
northamerica-northeast1, Québec / Canada)? - Zero AI training (Zero Data Retention): does the provider contractually guarantee that no transcript or clinical draft is retained by the model operator or used to train any AI model?
- Identifier stripping and anti-hallucination: are RAMQ and SIN numbers stripped automatically before synthesis, with strict instructions forbidding invented vitals or clinical facts?
- Law 25 / PIA documentation: can the vendor hand your privacy officer a concise technical brief listing data flows, roles, and subprocessors so you can review compliance with Law 25, Law 5, and college guidelines?
For larger FMGs and clinic groups with stricter governance rules, also ask whether a dedicated isolated Montréal database—or Bring Your Own Cloud (BYOC) deployment inside your own Google Cloud environment—is available. See our Security and hosting brief for the full technical summary.
The list to bring to your provider
Bring the single-page comparison table below to any vendor demo so your physicians and privacy officer evaluate every option against the same factual criteria:
| Question to ask in a demo | Answer that creates a grey zone | Expected answer (and how Silenoa works) |
|---|---|---|
| 1. What happens to encounter audio? | Archived in the account or written temporarily to cloud disk. | 0 s on disk: streamed and transcribed in volatile memory (RAM), then discarded immediately. |
| 2. How long is the note kept (EMR mode)? | Retained indefinitely inside the scribe's own portal. | Transient draft deleted upon confirmed transfer or after 48 h by default (30-day hard ceiling). |
| 3. How does the note enter our EMR? | Four manual copy-pastes, or unattended auto-save without review. | 1-click Chrome fill of S/O/A/P boxes; physician reviews and clicks Sign in the EMR. |
| 4. Where do the database AND AI run? | Database in Canada, but AI inference routed abroad. | Montréal (northamerica-northeast1) for application servers, encrypted database, and AI processing. |
| 5. Are AI models trained on our notes? | Opt-out or vague “service improvement” model retention. | Zero AI training (Zero Data Retention), auto RAMQ/SIN stripping, and no-invented-vitals rule. |
| 6. How is patient consent enforced? | Left entirely to memory with an unlocked microphone. | 15-second guided reminder locking the mic until ticked, 1-click exam pause, and auto footer. |
To watch the 1-click EMR transfer step by step without auto-signing, Open the guide: Fill your EMR in one click with the Chrome extension and review retention controls in Set how long drafts are kept.
Frequently asked questions
Why should an EMR-equipped physician avoid a scribe that stores permanent patient folders?
Because your certified EMR (MYLE, Omnimed, OSCAR, Cristal-Net) is already the legal chart. Keeping a permanent duplicate archive in a second system expands your privacy surface and falls out of sync whenever you edit a note inside your EMR before signing.
What if our private clinic does not use a physician EMR and needs signed longitudinal charts?
That is why Silenoa separates its two clinical modes: physicians with an EMR use Ephemeral Scribe mode, whereas allied health clinics in longitudinal care (psychologists, physiotherapists, chiropractors, osteopaths, OTs, SLPs) use Clinics mode with signed locked sessions, timestamped addenda, and an immutable audit log.
Can an FMG administrator enforce one draft-retention policy across every clinician in the group?
Yes. On Group deployments (5+ clinicians), workspace administrators can enforce a uniform draft-purge window (for instance 24 h or 48 h) across all seats.
Does this checklist replace review by our privacy officer or professional college?
No. This checklist gives you concrete technical questions to ask vendors; formal compliance assessment under Québec's Law 25, Law 5, and your professional college's guidelines should always be reviewed with your privacy officer or qualified counsel.