The visit ends. The note is already written.
It listens to the encounter, drafts the note, and flags what has not been asked yet. The ninety minutes a day that go into documentation go back into seeing patients.
Start a pilot with one clinician
Two weeks, no charge · the encounter is not recorded · Windows
Ninety minutes a day, spent typing.
Two or three visits
That is what the documentation hour costs a practice, per clinician, per day.
The screen, not the patient
Notes taken during the encounter are taken instead of eye contact.
Notes from memory
Written up at the end of the day, they lose the detail that made them worth writing.
You can see exactly what the model receives.
Not a promise about data handling — the actual difference between what the clinician sees and what is sent.
Maria Ivanova, DOB 03/14/1978, member ID 1234567890123456.
Headache for three weeks, worse in the evening. BP 150/95, on enalapril 5 mg. Phone (415) 555-0143.
[PATIENT_1], DOB [DATE_OF_BIRTH], member ID [DOCUMENT].
Headache for three weeks, worse in the evening. BP 150/95, on enalapril 5 mg. Phone [PHONE].
Audio
Never leaves the machine, never written to disk. Recognition is local.
Identifiers
Name, date of birth, phone, email, document numbers and address are replaced before the text is sent.
Clinical content
Doses, vitals and symptom timing are deliberately untouched — without them the note is worthless.
Where it stops.
The boundary is not modesty. Software that recommends a clinical action is regulated as a device; documentation support is not. Staying on this side of the line is what lets a clinic start next week instead of next year.
It does
Structures what the patient said · flags what has not been asked · drafts the note · copies it to a file and the clipboard for your own system.
It does not
Suggest a diagnosis · propose treatment · name a dose · speak to the patient · make any decision the clinician has not reviewed and signed.
Three steps, and one button between patients.
Type the patient's name
That name is hidden in everything that leaves the machine, in every grammatical form. It is never written to the settings file.
See the visit
What has been said, and what has not been asked. The window stays quiet otherwise.
Save the note, start the next patient
The note is saved with the real names, on your machine, and copied to the clipboard. One button clears the transcript, the hidden names and the counters — nothing carries over.
$149 per clinician, per month.
The category runs $99–300. The comparison that matters is different: two visits a day per clinician cost more than this does in a month.
The pilot is two weeks at no charge, one clinician, no card. Payment afterwards is handled by Gumroad as merchant of record.
One clinician, two weeks.
Patient consent to being recorded is a required step of any pilot, and we will send the wording we use.
What clinics ask first.
Do we need patient consent?
Yes. It is a required step of the pilot and we provide the wording. The encounter is not recorded, but the patient is still told what is running.
Is this a medical device?
No. It documents the encounter and does not recommend clinical action. That distinction is the reason the scope is drawn where it is.
Where does patient data go?
Audio stays on the machine and is never saved. The text of the conversation goes to a language model with identifiers replaced first. The panels above show exactly what that looks like.
Is it HIPAA compliant?
We do not make that claim on a web page. What we can say precisely: audio never leaves the machine, identifiers are removed from the text before sending, and nothing is written to disk. A BAA and a formal review are part of the pilot conversation.
We already have an EHR.
The note lands in a file and on the clipboard, so it pastes anywhere. Direct integration is a later step, not a requirement.
Will the clinician have to learn software?
Ten minutes once. After that it is a name field and one button between patients.