All use cases

Prevent / Care

Pre-visit intake summary and SOAP-note copilot

Your clinician walks into a GLP-1 visit and the patient's story is already on one page — history, current dose, side-effect log, latest labs — and walks out with the note drafted, ready to sign.

Close the loopSystem triggerTime-based triggerIn-appGLP-1 & PeptidesHealth & Telehealth

What it does

Every GLP-1 visit is bracketed by documentation work that eats the clinician's time: before, they piece together the patient's history, current dose, side-effect log, and recent labs from scattered places; after, they write the clinical note from memory. That double overhead is minutes lost on each visit, multiplied across a full panel, and it is the easiest throughput to win back. The agent bookends the visit — it auto-generates the pre-visit intake summary so the clinician arrives with the picture synthesized, and drafts the post-visit clinical note in SOAP structure, ready for signature. The clinician reviews and signs; the agent never makes the clinical call or the documentation final on its own.

How it works

  1. 1
    Trigger. a GLP-1 visit is scheduled (pre-visit summary) and later marked complete or its transcript posted (note draft); the agent assembles each artifact at its moment.
  2. 2
    Decision. for the summary, the agent synthesizes history, current medication and dose stage, the side-effect log, and the latest labs into a one-page brief; for the note, it structures the visit's record into a SOAP draft, citing the source behind each clinical line.
  3. 3
    Action. the pre-visit summary lands in the clinician's tool ahead of the appointment; after the visit the SOAP draft appears for review, edit, or signature, with anything uncertain marked as a question rather than asserted.
  4. 4
    Follow-through. the signed note writes back to the patient record and feeds the next pre-visit summary; clinician edits are kept as a quality signal; nothing becomes part of the record until the clinician signs.
Example
Agent (pre-visit summary)Ahead of today's visit: on the medication a few months, last titration a few weeks ago, side-effect log shows nausea that has eased, and the latest labs are in and within range. *Each line sourced to the record.*
ClinicianGood — after the visit, draft the note and carry the nausea trend forward.
AgentWill do. The SOAP draft will be ready for your signature with the nausea trend noted; nothing enters the record until you sign.

Configuration

How the agent is wired for this use case.

Triggera visit_scheduled event from the scheduling system (pre-visit summary) and a visit_complete event or posted transcript (SOAP-note draft)
Tools & actions
  • Clinical/EHR system · read history, current medication and dose stage, side-effect log, and labs to build the pre-visit summary
  • Lab system · pull the latest results and flag values against protocol ranges for the summary
  • Clinical/EHR system · present the one-page pre-visit summary in the clinician's tool ahead of the appointment
  • Clinical/EHR system · draft the post-visit note in SOAP structure for clinician review and signature, sourcing each clinical line
  • Clinical/EHR system · write the signed note back to the patient record so the next summary starts from it
Autonomysummary synthesis and note drafting run unattended; the clinician reviews and signs every note — clinical = synthesize and draft, never diagnose or advise a dose; uncertain content is posed as a question, and nothing enters the record without signature
Channelsin-app
Escalationthe clinician signs every note; a flagged lab value or any safety signal in the summary is raised to the clinician, and no documentation becomes final without clinician sign-off

What you need

The inputs this use case runs on. Your channels stay yours; the agent supplies the judgment.

Signals

visit_scheduled and visit_complete events; posted visit transcripts or notes; lab-result-ready events

Data

patient history, current medication and dose stage, side-effect log, and lab results; the clinic's SOAP note template and protocol ranges; consent to use the record for documentation

Guardrails

clinician signature required before any note enters the record; source attribution on every clinical line; clinical = synthesize and draft, never advise a dose; a full audit log of summaries, drafts, edits, and signatures

Metrics it moves

  • clinician-hours-savedup, as pre-visit assembly and note writing collapse into review-and-sign, freeing minutes on every visit
  • time-to-resolutiondown, because the note is drafted at the close of the visit instead of written later from memory
  • csatup, since the clinician arrives prepared and the visit stays on care, not on screen-reading

Related use cases

Prevent / Care

Clinician copilot — approve instead of writing

drafts the patient reply; this drafts the visit summary and note instead

Prevent / Care

Clinician copilot — approve/decline decision packet

a yes/no start decision rather than a visit-documentation bundle

Prevent / Care

Doctor copilot — pre-drafted clinical reply with citations

the same sourcing discipline applied to async replies

See it on your own customer journey

Bring one drop-off, one churn cliff, or one silent segment. We will show you what a proactive agent with memory and judgment does with it.

Book a demo