Healthcare / Clinical Documentation Live
Clinical Document Summary
Summarise a discharge summary, consultation note, or referral letter, and emit the problems, medications, and follow-up actions as a structured FHIR bundle alongside the readable version.
- Run on demand
- ~6 credits per run
- v1.0.0
What does Clinical Document Summary do?
Clinical Document Summary is a production AI agent in the healthcare section of the Leverge agent store, built for the clinical documentation process. Summarise a discharge summary, consultation note, or referral letter, and emit the problems, medications, and follow-up actions as a structured FHIR bundle alongside the readable version. It runs on demand, works through 4 steps and returns 7 outputs, including encounter.
What it needs
-
Clinical document
A discharge summary, clinic letter, or consultation note. Text is extracted before anything is sent to the model.
-
Summary settings
What it does
- Extracting the document text
- Reading the record
- Writing the summary
- Mapping to FHIR R4
What you get back
- Encounter
- Summary
- Problems and diagnoses
- Medications
- Follow-up actions
- Needs attention
- FHIR R4 bundle
After each run it asks: “Would you hand this summary to a colleague?”
When it runs
Run on demand
Oversight
Runs under scoped, least-privilege credentials with every action written to an audit log. Anything that moves money, alters a contract or reaches a customer requires human approval before it executes.
Clinical Documentation
Other agents in clinical documentation
Clinical documentation, referrals and patient communication
-
Patient Message Triage
Triage an inbound patient message against the practice's own policy, look up the record, and draft either an administrative reply or a clinical escalation. Every reply waits for a human.
-
Referral Intake Review
Check an incoming referral letter against the receiving service's acceptance criteria, extract the clinical detail, and say plainly whether it can be booked or what is missing before it can.
Next Step
Deploy Clinical Document Summary, or adapt it
It runs as-is against the inputs above. Most deployments diverge — a different source system, a different tolerance, a different approval path. A 30-minute technical call establishes which.