For providers

You keep the laptop. You keep the signature.

Most of what an ambient scribe changes should be invisible. Here is the honest version of what is different, what is not, and what it costs you in the room.

What changes

You press record at the start of the visit and stop at the end. After clinic, instead of writing notes, you read them.

What does not

Your EHR, your templates, your dot phrases, your exam defaults, your time statements, and the fact that you are the only one who signs.

The note sounds like you, because it is configured to

A drafted note that reads like a different clinician is a note you rewrite, which is worse than no draft at all. Style belongs to the clinician, so it lives in a preferences record you edit yourself — paragraph length, default return intervals, standing wording you always include — not in something an engineer has to change for you.

What preferences deliberately cannot change is the clinical and billing logic: how coding is derived, how a preventive visit is separated from a problem visit, and the rule that every statement in the note has to be traceable to something said in the room. Those are the same for everyone, on purpose.

The billing call, argued rather than asserted

The fuzziest recurring decision in a gynecology practice is whether a well-woman visit that turned into a real problem discussion is one service or two. SimaNotes makes that call explicitly and shows its work: which components fell under the preventive service, what problem work was separately identifiable, and — the part most tools omit — what was considered and deliberately not billed separately.

That last block stays in the signed note. A year later, the note explains its own coding to whoever is reading it, including you.

Things it will not do, and will not learn to

  • Invent findings. If an exam element was not performed or stated, it does not appear.
  • Fill in a code you did not earn. Where the billable code depends on something SimaNotes cannot see — a patient’s age band, new versus established — it says so instead of guessing. A placeholder you have to resolve is safer than a real code that happens to be wrong.
  • Sign, submit, or send anything.
  • Record without the patient knowing.

When it is down

It will be, at some point. The answer is the one you already have: document the way you did before. SimaNotes is a drafting aid on top of a workflow that stands on its own — practices we work with get a one-page downtime procedure, on paper, at the laptop, because a procedure nobody can find during an outage is a procedure that does not exist.

Ask a question