The patient is ready to leave. The summary is not
Everything the discharge summary needs is already in the record: admission notes, ward rounds, lab results, the medication chart, the follow-ups ordered on the last day. What costs the afternoon is a clinician assembling it by hand across six screens. Blue Mesh drafts the summary from the record itself, every line cited back to the entry it came from, and holds it for the discharging physician to verify and sign.
What a discharge summary actually costs
The document is short. The assembly is not, and the record it draws on was written by a dozen hands across a whole admission.
The six-system assembly job
One summary means admission notes in one screen, labs in another, the medication chart in a third. The clinician is not composing, but hunting.
- 01.01Half a dozen screens open to produce one document
- 01.02The medication list reconciled by eye
- 01.03Whatever was filed unusually, found late or not at all
The bed blocked by paperwork
A patient can be medically ready in the morning and still in the bed mid-afternoon because the summary sits in a queue behind ward rounds.
- 02.01Discharge decided at nine, executed much later
- 02.02Summaries queued behind everything clinical
- 02.03Bed flow set by the speed of a document
What primary care never hears
A summary written under pressure carries what its author found in the hunt. The dose that changed on day three is exactly the detail that slips.
- 03.01Medication changes that never reach the summary
- 03.02Follow-ups that exist only in a ward note
- 03.03A handover the receiving doctor cannot audit
From scattered record to signed summary
Retrieval-augmented drafting over your own EHR, with a citation on every line and a physician holding the gate.
The workflow reads the admission from your EHR: diagnoses, procedures, the medication chart with what changed and when, doctor notes, and the follow-ups already ordered. Retrieval is grounded in the indexed record, and every fact it pulls carries a citation back to the entry it came from.
A structured summary is drafted in your format, section by section. Where the record is silent, the draft says so instead of improvising: a gap is flagged for the physician to resolve, not papered over with plausible prose.
The draft stops at the discharging physician, and the citations are what make the check fast: verifying a medication change is one look at the source entry, not a dive through the chart. Sign it, amend it, or send it back.
Draft, edits, sign-off, and dispatch to primary care are all logged. When anyone asks what the summary said, what it was based on, and who approved it, the answer is a record, not a recollection.
Benefits that follow from the mechanism
The physician's job becomes verification
Assembling a summary and checking one are different afternoons. With retrieval doing the hunt and citations pointing at every source, the clinical time goes into the judgment call, which is the only part that needed a clinician.
A handover the receiving doctor can audit
A summary drawn from the record rather than from memory, with gaps flagged instead of guessed, gives primary care something it can interrogate. The citation trail answers the follow-up question before the phone call.
Patient records stay where they live
The workflow reads the record in place, inside the environment you deploy it in: private cloud, on premises, or fully air-gapped. Access is role-based, nothing is siphoned out to be processed, and every retrieval and edit is logged.
The boundary: the record is the ceiling
A draft can only carry what someone entered, and a wrong entry produces a well-cited wrong line. That is exactly why the sign-off gate exists and why the citations point at sources rather than asking for trust: the physician decides, the system drafts.
- Enterprise RAG The retrieval engine underneath this page, Privy AI: grounded answers from your own records with the source cited in every reply.
- Clinical Note Automation Upstream of the summary: the consultation transcribed and structured into the note this page later draws on.
- Trust and security Patient records are why this question comes before the demo: the three deployment modes, and the audit trail on every decision.
Watch a summary assemble itself
In one session we will point the workflow at sample records and walk the whole path: retrieval with citations, the drafted summary, the sign-off step, and the log entry it leaves behind.