For most meeting software built to answer that question, the honest answer is a server somewhere the patient never chose and the practice doesn't operate — transcribed and summarised there, then handed back as text sometime after the visit ends. For a clinical conversation, that detour is the part worth questioning, not the recording itself.
What a general-purpose notetaker asks a practice to accept
Otter and Fireflies both join a call as a named participant to capture it, and both transcribe and summarise on infrastructure the vendor operates rather than the machine running the visit. Granola skips the participant but is still a cloud subscription end to end. Neither answers the question that actually matters for a clinical recording, which isn't whether something joined the call but where the audio went once it was captured.
Both sides of the visit, recorded on the machine running it
Coii AudioNotes records the microphone and, separately, the system audio the Mac is playing during a video visit — two tracks, captured and transcribed entirely on that same machine. Nothing about the visit is sent anywhere to produce the recording, the transcript or the summary.
A summary written where the visit happened
A language model bundled inside the app turns the transcript into a short recap — something decided, something to follow up on, a question still open — right after the visit ends. It's a general summary, not a note built to a specific clinical format, and it's written on the Mac rather than sent off to be generated somewhere else.
Decisions
- Continue the current medication through the next check-in
Actions
- Schedule bloodwork before the following visit
Open questions
- Has the reported side effect changed since the dosage adjustment?
What this page is careful not to claim
It does not claim a HIPAA or any other compliance certification. What's actually true, and the thing worth relying on instead, is the behaviour: the recording, transcript and summary are all produced on the Mac and nothing is uploaded to produce them. Whether that satisfies a specific practice's compliance obligations is a question for that practice's own compliance officer, not this page — and it is not a clinical documentation tool, so it makes no claim about note formats, coding, or anything a billing review would need to check against a specific standard.
What it deliberately doesn't do
There is no EHR integration, no e-prescribing connection, and no clinical note template — no SOAP note, no structured history and physical. The summary is general, and turning it into documentation that fits a practice's specific format and coding requirements remains a separate step. There is no shared workspace a colleague can browse without being sent the recording directly; each one lives on the Mac that made it, across up to three machines on one licence. And it runs on macOS only, with no Windows, iOS or Android version, so a practice with staff on mixed platforms won't get the same tool across everyone from this one alone.
What actually changes about the visit
Nothing about the visit itself changes — same call, same platform, same conversation. What changes is what happens to the recording afterward: instead of a transcript produced on a vendor's server, there's a transcript and a short recap on the same Mac that ran the call, kept there rather than passed through a third party to get written up.
Who this genuinely isn't built for
A larger practice already running structured clinical documentation through an EHR, with notes required to fit a specific coding and billing format, has a real requirement this tool doesn't attempt to meet — the summary here is general, not built to any clinical standard. This is written for the version of practice where the recording's job is helping a clinician remember a visit accurately, not replacing the documentation a practice's own systems already require.
Setting it up is smaller than the decision to switch
The first launch asks for two macOS permissions — microphone access and permission to record system audio, for the video-call side of a telehealth visit — the same prompt any Mac app requesting audio capture triggers, and that's the whole of it. No account to register, no workspace to configure, nothing to connect before the first visit can be recorded. The larger part of introducing recording into a practice is usually the practice's own decision about which visits it applies to and how that's communicated to a patient, not the software itself.
Recording is a decision made visit by visit
Nothing here records automatically the way a bot logs into a scheduled call on its own. Recording is started deliberately for a specific visit, which means a practice that wants some visits recorded and others not gets that by choosing not to start it for the ones it doesn't, rather than configuring an exception into a system that would otherwise record everything by default.
Why a transcript is worth having alongside notes taken live
Notes written during a visit capture what a clinician judged worth writing down in the moment, which isn't always the exact wording a patient used to describe a symptom, a timeline, or a change since the last visit. A transcript sitting alongside those notes gives a chance to check the two against each other afterward — useful specifically on the visits where a precise phrase, a reported date, or a detail that seemed minor during the conversation turns out to matter more once the note is actually being written up.
What a full patient panel makes visible over time
A single visit's recap is useful that same day; an archive of them becomes useful in a different way over the course of ongoing care, when what actually matters is whether a symptom reported six visits ago has recurred, or whether a specific instruction was given the way the clinician remembers giving it. Reconstructing that from memory across an entire panel isn't realistic much past a handful of patients; a transcript sitting on the clinician's own Mac, searchable by keyword, turns it into something that can actually be checked rather than guessed at.
What actually changes across a full day of visits
The visit itself runs exactly as it always has — same questions, same exam, same conversation. What changes is what happens in the minutes after each one: instead of writing a note from memory while trying to stay on schedule for the next patient, there's already a transcript and a short recap on the Mac, ready to turn into the actual chart note whenever there's time to do it properly rather than rushed between visits.
The trust question underneath a telehealth visit
A patient who agrees to a telehealth visit being recorded is trusting that it goes somewhere specific and limited, even without asking exactly where. A cloud vendor's privacy policy can describe that in detail, but it's a document almost nobody reads closely before a video call starts. Recording, transcribing and summarising on the same Mac running the visit sidesteps the question rather than needing a reassuring answer to it — there's no vendor's server in the chain at all, and nothing about the visit exists anywhere the clinician's own Mac isn't.
Who this genuinely isn't built for, said a second way
A solo practitioner or a small practice where the clinician handling the visit is also the one who needs the record of it is exactly who this is built for. A larger practice or hospital system with shared clinical documentation, structured EHR workflows and coding requirements that span a whole care team has a real reason to stay with tools built around that infrastructure — not because a single visit is handled worse here, but because the value of an EHR comes specifically from the structure and sharing this tool deliberately doesn't attempt to replace.
The first weeks after introducing it
The first few visits after starting to record tend to feel slightly different for one specific reason — remembering to press record before the video call begins, rather than it happening on its own. That adjustment fades within a couple of weeks, and what replaces it is a transcript and a short recap waiting on the Mac after each visit, without anything joining the call or appearing on the patient's screen to explain.
A telehealth day, before and after
A morning of back-to-back telehealth visits used to mean either typing notes mid-conversation, which pulls attention away from the patient on screen, or writing everything up afterward from memory once the last visit of the block finally ends — by which point the second visit's details have usually started blending into the fifth's. With the recording, transcript and recap produced automatically per visit, the write-up step shrinks to reading back a short summary rather than reconstructing the whole conversation from scratch.
What a patient remembers about the visit
A patient rarely remembers the exact clinical language used, but they do remember whether the clinician seemed present or distracted by typing during a video visit. Recording instead of transcribing live keeps the clinician's attention on the screen and the patient rather than on a notes window, which matters as much for the visit itself as it does for the accuracy of the eventual chart note.
Who this is written for, plainly
Not a hospital system standardising documentation across hundreds of clinicians — that's an EHR procurement decision, not a single app's job. This is written for the solo practitioner or small practice whose telehealth visits currently get either typed up live, at the cost of eye contact with the patient on screen, or reconstructed from memory between one visit and the next, and who wants a transcript worth trusting without a recording that has to leave the Mac to produce it.
What it costs, what it runs on
Coii AudioNotes is $19, paid once, for three of a clinician's own Macs, with a 30-day trial needing no card and no account, and every feature unlocked from the first launch rather than gated behind a tier a small practice would have to justify upgrading into. It runs on macOS 13 Ventura or later, Apple Silicon or Intel. Against Otter's or Fireflies' monthly subscriptions, or Granola's $14-a-month Business tier, the $19 is paid once rather than every month for as long as the practice keeps recording. Full comparisons here and here. A wider round-up of meeting notes apps for regulated work covers clinical practice alongside the other professions with the same requirement, and meeting apps that don't train on your data covers a closely related question a compliance review usually asks next, and is worth reading alongside this one before a practice settles on any single tool for recording clinical conversations. The broader case for a Mac-native meeting notes app, what an AI notetaker without the bot changes, a round-up of private meeting recorders, and what happens when a visit runs somewhere without a reliable connection, covered in offline transcription for Mac, all cover ground this page doesn't repeat, and each is worth a look before settling on a single tool for recording clinical conversations.