How it works  /  Patient intake  ·  step 1 of 7
Patient intake

The visit starts with the history already gathered

A token-gated link, no login and no portal. The patient answers the questions a coder will need months later, while they still remember the answers.

What this changes for you

You stop chasing history that nobody wrote down

The answers that decide medical necessity — how long, what was tried, how long the last injection lasted — arrive before the visit instead of being reconstructed months later by someone who was not there.

The patient remembers what the doctor cannot

How long it has hurt, what was tried, how long the last injection lasted. These are the facts that decide medical necessity, and the person who knows them is not in the room when the note is written.

It is a source, never a prediction

No codes are picked here. A patient saying “knee” does not choose a procedure. What the intake gives you is evidence to check the note against — and requirements tied to a CPT stay note-only, because the payer asks for the physician's record.

Nothing is stored that was not said

Every fact carries the patient's own words, and is dropped if those words are not really in the transcript.

Try it on your own words

Answer as a patient and see what we would hold. Leave it empty to run the sample case. Use made-up details — this is a public page, so do not paste real patient information.

What the engine returned

gemini_vertex_client.generate_content
Body part knee · right
Already tried physical therapy, naproxen
Codes assigned none — this is an information source

cached run · 8.2s — press Run this engine for your own text

Next: Front desk →