StethoNote

  Pilot starting specialty-tuned, podiatry first

The note is written by the time the visit ends.

One tap starts the recording, with the patient's consent captured as its own deliberate act. StethoNote listens, transcribes, and drafts the clinical note with suggested codes. You read every word, change what you want, and sign. Nothing enters the chart unread.

  • 1 tap to start in the room
  • Minutes from visit end to draft
  • 0 notes filed without a physician

A clinic morning, documented as it happens

From the room to the record

01 / RECORD

Tap once. See the dot.

The phone stays in your pocket or on the counter. Consent is a deliberate, timestamped confirmation before the microphone opens. Not a checkbox buried in intake paperwork.

02 / DRAFT

The visit becomes a note.

A medical-tuned speech model separates who said what. The draft comes back structured: a full SOAP note, an E/M level reasoned from medical decision-making under the 2021 rules, and ICD-10 suggestions tied to the words that support them.

03 / SIGN

You stay the author.

Read it, fix it, sign it. A minute or two, not the fifteen you'd have spent typing. What the model proposed and what you signed are kept separately, for as long as the note is kept.

Tuned to one specialty at a time, on purpose.

General-purpose scribes translate every specialty equally, which is to say none of them well. StethoNote learns one specialty deeply — its vocabulary, its visit shapes, its codes — before opening the next. It started inside a working podiatry practice: nail care, plantar fasciitis, diabetic foot checks, injections.

Podiatry first Family medicine next Dermatology next Orthopedics next ENT next Urgent care next

The signed note is yours. It's formatted to paste cleanly into the EHR you already use, and direct integrations are on the roadmap.

The economics matter too. Enterprise scribe tools price for hospital systems. A three-provider practice shouldn't pay hospital-system rates — StethoNote is a flat monthly rate, not per-note metering.

How patient information is handled

A BAA before the first recording We store audio, transcripts, and notes in our own AWS account, in US regions, on HIPAA-eligible services. AWS runs the Claude model on Amazon Bedrock; AssemblyAI transcribes. We sign a Business Associate Agreement with every practice before any patient audio is recorded, and both subcontractors sign one with us first.
Encrypted, then deleted The app and dashboard reach our servers over HTTPS. Audio and notes are encrypted at rest with managed keys. The phone deletes each recording once its upload is confirmed. When the physician signs, we delete the recording and transcript from our servers; database backups roll off after their 7-day window, within about 9 days. Recordings of unsigned visits expire after 90 days. The signed note is the record.
An audit trail for every action Each phone is enrolled with a one-time code to a member of the practice. The audit trail answers who did what, on which device, and when. Every clinician gets a personal dashboard login before the first patient visit.
The physician stays accountable Nothing is filed automatically. The model's suggestion and the physician's signed version are stored side by side, so the two can be compared and audited for as long as the note is kept.