Clinicians

Drafting orders

Orders proposed from the conversation, why none of them are real until you confirm, and how to add the one the AI missed.

7 min · Clinicians · lesson v1

Orders in ChartVoyant get drafted while you talk, and then wait for you. The waiting is the point.

The banner that governs the whole tab

  1. At the top of the Orders tab, on every visit:

    All orders are DRAFTS. Medications, imaging, procedures, referrals, and labs never finalize automatically — clinician must Confirm, and nothing is transmitted in this prototype.

    Nothing on this screen has left the building.

    Screenshot pending capture

Each card carries a category pill — medication, imaging, lab, referral, procedure — the order itself, the rationale for suggesting it, and, where relevant, a safety list and a prior-authorization block.

Confirming

  1. Each card has Accept, Modify, Reject — and, uniquely for orders, Confirm.

    The status line under the card is the one to read:

    • ● Draft — not ordered
    • ✓ Confirmed draft (would route on clinician sign — not transmitted here)

    Once confirmed, the button reads Confirmed and is disabled. Rejecting disables it too.

    Screenshot pending capture

Adding what the assistant missed

  1. + Order something else opens Add a draft order the AI didn't suggest:

    • a category dropdown
    • Order name (e.g. Naproxen 500mg)
    • Detail (optional) — dose, instructions, indication

    Then Add draft order. It joins the list as a draft like any other, and needs the same Confirm.

    Screenshot pending capture

This matters more than it looks. The assistant drafts from what it heard; anything decided before the visit, or agreed after the transcript stopped, has to come from you.

Safety and prior authorization

Where a suggested order raises something, the card carries a safety list — each row naming the kind of concern and the message.

The prior-auth mini-block reads Prior auth: [determination] · [payer], plus a line like 3 criteria outstanding — see close-out for the full checklist.

The other orders panel

There is a second, fuller ordering surface in the patient's chart — not in the staged visit. It handles Lab, Imaging, Referral and Procedure with coded search, practice Favorites (shown as ★ [name]), point-of-care tests (+ UDS, + Pregnancy (hCG), + Flu A/B and so on), and an Urgency picker.

Two things there worth knowing now:

  • Orders start as DRAFT and need Sign — the tooltip is Sign to activate (clinician).
  • A point-of-care test you ordered but haven't logged shows Not yet recorded — click Record to enter who performed it. Somebody has to own having done the test.

What usually goes wrong

Accepting without confirming. An accepted order that was never confirmed still reads ● Draft — not ordered and will not happen.

Waiting for the assistant to suggest the obvious. If you have already decided, add it.

Reading the prior-auth block as a coverage decision. It is a checklist against generic criteria.

Ordering a point-of-care test and walking away. The record needs who performed it, when, and where.

Check yourself

No score, no account — just make sure you can answer these before you move on.

  1. You confirmed three orders during the exam. Have they been sent anywhere?

    Show the answer

    No. A confirmed order reads ✓ Confirmed draft (would route on clinician sign — not transmitted here). Confirming means you agree it should happen; routing happens at sign-off, and in this build nothing is transmitted at all.

  2. What's the practical difference between Accept and Confirm on an order card?

    Show the answer

    Accept is the generic "this suggestion is useful" action shared by every card type. Confirm is specific to orders and is the one that moves it from ● Draft — not ordered to a confirmed draft. An accepted but unconfirmed order is still nothing.

  3. An order card shows a prior-auth block reading 3 criteria outstanding. Does that mean the payer will refuse?

    Show the answer

    It means three criteria are unresolved in the checklist — and the checklist itself warns that the real payer policy is source-needed — not ingested in this prototype, with generic placeholders. It is a prompt to go and check the actual policy, not a prediction.