Intelligent symptom triage, appointment routing, and medication Q&A chatbot for healthcare platforms
The Healthcare Diagnostic AI Agent framework is the definitive AI prompt system for health systems, telehealth platforms, and digital health startups building patient-facing AI agents. Healthcare chatbots fail in two ways: they either give dangerously overconfident medical advice, or they are so hedged they provide zero value. This framework solves both failure modes with a precision-engineered architecture: a structured symptom intake that produces an urgency score (not a diagnosis), hard-coded emergency escalation that no LLM response can override, medication Q&A with drug interaction checking and explicit scope boundaries, and HIPAA-aware conversation patterns that keep PHI out of logs. Every prompt is reviewed against the principle that the agent's job is to route patients to the right care faster — not to replace clinical judgment.
Full Access Unlocked
All 58 prompts · All 7 modules
"The emergency escalation protocol architecture — hard-coded keyword detection that fires before the ..."
Chief Medical Officer · Regional telehealth platform, 200K patients
Need expert implementation?
Hire an OrchestratorConnect with a certified Prompt.Doctor Orchestrator to deploy this framework for you.
No coding required. You will use ChatGPT or Claude as your AI tool. Follow these steps in order — do not skip ahead.
Purchase & download the framework
Click the buy button on this page. After checkout, go to the and hit Download .zip. Unzip it — you'll get a .md file (the full framework) and a .pdf (easy to read reference). Keep both open.
Open your project — new or existing
This dashboard is designed to integrate into any existing project or be built as a standalone app. If you already have a site in Airo (or Cursor, Bolt, etc.), open that project. If you're starting fresh, create a new project. The Orchestrator Prompt handles both cases — it scans what's already there and adds only what's missing.
Paste the Orchestrator Prompt into your builder's chat
Open the on this page. Copy the Orchestrator Prompt and paste it into your AI builder's chat. It will scaffold the full admin system — secure login, email marketing module, booking engine, and CMS — on top of your existing codebase. This takes 2–5 minutes.
Add your API keys as secrets
Critical — Novice UsersIn your builder, go to Settings → Secrets and add the keys your app needs. For this framework: STRIPE_SECRET_KEY (for booking payments — get it from your Stripe dashboard), ANTHROPIC_API_KEY (for AI-assisted content — get it from console.anthropic.com), and DATABASE_URL (your MySQL connection string). No key is needed for the admin login, CMS, or email modules — those run on your existing infrastructure.
Don't have a MySQL server?
You can purchase a shared hosting plan with cPanel and MySQL at host.esgwon.dev. Once your account is set up, follow the step-by-step guide to create your database and connect it to your AI website builder.
How to set up cPanel MySQL & connect to your AI website →Need help with Stripe?
Get your STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY from your Stripe dashboard. The guide covers test keys, webhook setup, and going live.
Need help with Anthropic?
Get your ANTHROPIC_API_KEY from console.anthropic.com. The guide covers model selection, cost management, and troubleshooting.
Prompting Airo after setup — always name the file
When asking Airo to add tables, columns, or features to the admin dashboard, always include src/server/lib/admin-db.ts in your prompt. Without it, Airo may target the wrong database. Example: "Add a bookings table in the admin database (src/server/lib/admin-db.ts) — do not touch any other database connection in this project."
Run the framework prompts inside your live app
Your app is now running in the builder's preview panel. Open the on this page, copy each prompt one at a time, and paste it into your builder's chat. Replace every [BRACKET] with your real data before sending. Work through the stages in order — each stage output feeds the next.
Test end-to-end, then publish or hand off to your client
Walk through the admin as a real user: log in, create a booking, send a test email campaign, update a CMS image, and run the Safe-to-Publish gate. Once everything passes, click Publish in your builder. Because this is a white-label dashboard, your client accesses it at /admin on their own domain — no Prompt.Doctor branding, no third-party login required.
7 modules · 58 prompts · 7 workflow stages
Symptom Intake & Triage Engine
Structured symptom collection (onset, severity 1–10, location, duration, associated symptoms), urgency scoring rubric, red-flag symptom detection, and triage decision tree
12 promptsEmergency Escalation Protocol
Hard-coded emergency keyword detection (chest pain, stroke symptoms, suicidal ideation), immediate 911/ER redirect message, bypass of all LLM generation for flagged inputs, and crisis resource injection
8 promptsAppointment Routing
Symptom-to-specialty mapping table, insurance verification prompt, provider availability surfacing, appointment slot confirmation, and calendar invite generation
10 promptsMedication Q&A
Drug name normalization (brand → generic), dosage guidance with weight/age parameters, drug-drug interaction lookup, side-effect explanation, and refill reminder logic
10 promptsMedical History Context
Persistent patient context schema (conditions, allergies, current medications, last visit), context injection into every triage prompt, and context update on new disclosures
8 promptsHIPAA-Aware Architecture
PHI detection and redaction before logging, consent capture conversation flow, audit trail event schema, data retention policy prompts, and BAA-ready response disclaimers
6 promptsMultilingual Triage
Language auto-detection from first user message, Spanish/Mandarin/French triage prompt variants, medical terminology localization, and escalation messages in detected language
4 promptsWrite a production-ready system prompt for a healthcare symptom triage AI agent for [CLINIC/HEALTH SYSTEM NAME]. The agent helps patients understand their symptoms and determine appropriate care level. Requirements: 1) Role: a clinical triage assistant — NOT a doctor, cannot diagnose, cannot prescribe, 2) Emergency detection: ALWAYS check for emergency symptoms first (chest pain, difficulty breathing, stroke symptoms, severe bleeding, suicidal ideation) — immediately direct to 911 or ER, 3) Symptom collection: ask about symptom onset, severity (1-10), duration, associated symptoms, relevant medical history, 4) Care level recommendation: self-care at home / urgent care / ER / call 911 — with specific reasoning, 5) Escalation: offer to connect with a nurse or schedule an appointment, 6) Prohibited: never diagnose, never recommend specific medications, never minimize serious symptoms, 7) Tone: calm, empathetic, clear. Include 3 few-shot examples: mild symptom, moderate symptom, emergency symptom.
Build a Node.js TypeScript HIPAA-compliant conversation logging system for a healthcare AI chatbot. Requirements: 1) PHI detection: before logging any message, scan for PHI using regex patterns for: SSN, date of birth, phone numbers, email addresses, medical record numbers, full names (first + last), 2) PHI redaction: replace detected PHI with [REDACTED_TYPE] placeholders before storing, 3) Audit log schema: { sessionId, timestamp, role (user/assistant), messageHash (SHA-256 of original), redactedContent, phiTypesDetected[], agentAction, agentReasoning }, 4) Storage: encrypted at rest — use AES-256 encryption before writing to database, 5) Retention: auto-delete logs after 7 years (HIPAA minimum), 6) Access log: log every time a conversation record is accessed (who, when, why), 7) TypeScript with full type safety. Include the PHI regex patterns and encryption utilities.
Build a conversational appointment booking flow for a healthcare AI agent. The agent should: 1) Collect: patient name, date of birth (for identity verification), reason for visit (free text), preferred provider (if any), preferred date/time range, 2) Check availability: call GET /api/appointments/availability?providerId=X&date=Y to get open slots, 3) Present options: show 3 available slots in a natural conversational format ("I have Tuesday at 2pm with Dr. Smith, or Wednesday at 10am with Dr. Jones — which works better?"), 4) Confirm: summarize the appointment details and ask for confirmation, 5) Book: call POST /api/appointments/book with collected data, 6) Send confirmation: trigger email confirmation with calendar invite (.ics file), 7) Handle edge cases: no availability (offer waitlist), patient cancels mid-flow (save partial data), provider not available (suggest alternatives). Write as a TypeScript state machine with explicit states and transitions.
system
26 prompts
workflow
14 prompts
prompts
10 prompts
templates
8 prompts
"The emergency escalation protocol architecture — hard-coded keyword detection that fires before the LLM ever generates a response — is the only correct way to build this. Every other healthcare chatbot framework we evaluated let the LLM handle emergency routing. That's a liability. This framework gets it right."
Chief Medical Officer
Regional telehealth platform, 200K patients
"The symptom intake → urgency scoring → specialty routing pipeline reduced our patient intake time by 60% and increased appointment completion rates by 34%. The HIPAA-aware logging patterns saved us 3 months of compliance work."
VP of Product
Digital health startup, Series B
All 58 prompts across 7 modules are unlocked for your account.
Lifetime access