Patient Communication Agent
Patients get timely follow-ups while clinicians approve every clinical message.
A ready-to-build governance package for Healthcare. Your runtime enforces it; Agent Bob does not run the agent.
Purpose
You want patients to get reminders, care plan summaries and follow-up instructions on time. This agent drafts and sends those messages over encrypted channels. Any message with diagnosis or treatment language waits for clinician approval, and no PHI is kept between sessions.
It will
- Send patient messages only — no EHR write access
It won't
- Transmit PHI over unencrypted channel, send clinical advice without clinician approval
It asks a person first
- Escalate to care coordinator if patient responds with distress keywords
- Dual-approval required for any message containing diagnosis or treatment language
Tools
- Send email
- SMS / text messages
- Send email: Send email on your behalf.
- SMS / text messages: Send text messages to phone numbers.
✋ Every outbound action needs your approval
Budget defaults
- Per task
- $0.50
- Per month
- $40
- Actions a day
- 100
The runtime pauses the agent at a limit. You can change every number in the builder.
Memory and autonomy
No memory. Nothing is kept between runs.
Supervised: it prepares the work and a person approves it.
What you get
The 8-file governed package your runtime loads and enforces. On the paid tier the trust manifest is signed, so your runtime can verify nothing was changed after you approved it.
HANDOFF.mdWhat your runtime has to enforce, file by fileagent-blueprint.jsonThe agent's purpose, tools and settingspolicy.jsonHard limits: autonomy, budget, memory, tools, loop boundstrust-manifest.jsonThe integrity manifest your runtime can verifyrouting.rules.jsonWhich tools need approval before userun-report-template.jsonWhat every run reports backapproval-gates.mdThe moments that must pause for a persondeployment-checklist.mdWhat to check before it goes live
This is a governance specification, not a running agent. The rules in these files do not enforce themselves: your runtime has to implement them.
Start from this package
Bob pre-fills the builder with it and drafts the rest. You confirm every step.