Contribute
Sign in
CharmHealth

CharmHealth

An MCP server for CharmHealth EHR that allows LLMs and MCP clients to interact with patient records, encounters, and practice information.

10K+pulls17 ToolsPackaged byDocker, with additional security features including SBOMs, provenance, signing, and multi-arch supportRequires Secrets

Tools

NameDescription
getPracticeInfoGet practice information. <usecase> Get essential practice information needed for other operations - available facilities, providers, vital signs templates, etc. Use this to understand practice setup and get IDs for other tools. </usecase> <instructions> - "facilities": List all practice locations with IDs needed for scheduling - "providers": List all providers with IDs needed for appointments and encounters - "vitals": Available vital sign templates for documentation - "overview": Summary of practice setup with key counts and recent activity - "templates": List all available SOAP templates (id, name, type) for the practice - "template_details": Full template schema (widgets + entries) for given template_ids (comma-separated) When required parameters are missing, ask the user to provide the specific values rather than proceeding with defaults or auto-generated values. </instructions>
manageEncounterManage encounters. <usecase> Complete encounter workflow - create, review, and sign encounters with comprehensive clinical documentation. Essential for clinical workflow from initial documentation through final signature. </usecase> <instructions> Actions: - "list": List encounters for a patient (requires patient_id; optionally filter by filter_by, start_date, end_date, per_page, page) - "create": Create new encounter and document clinical findings (default) - "review": Display complete encounter details for review before signing - "sign": Electronically sign encounter after review and confirmation - "unlock": Unlock a previously signed encounter to allow modifications For creating encounters (two paths): - From appointment: patient_id + appointment_id (provider/facility/date come from the appointment) - From scratch: patient_id + provider_id + facility_id + encounter_date - Optional: visit_type_id, encounter_mode, chief_complaint For reviewing encounters: - Requires: patient_id, encounter_id - Shows comprehensive encounter details including vitals, diagnoses, medications, notes For signing encounters: - Requires: patient_id, encounter_id - Only use after reviewing and confirming all information is accurate For unlocking encounters: - Requires: patient_id, encounter_id, reason - Used to unlock signed encounters when modifications are needed - Must provide a valid reason for unlocking the encounter For updating encounters with template data: - action="update" with chief_complaint always saved as narrative fallback - template_ids: comma-separated IDs of templates to attach to the encounter - entries: JSON array string of populated template entries, e.g. '[{"entry_id":"123","answer":"text"}]' - Templates are attached first, then entries + chief_complaints saved together - entry_id values must come from getPracticeInfo(info_type='template_details') — hallucinated IDs are dropped client-side Recommended workflow: 1. Create encounter: manageEncounter(patient_id, appointment_id, action="create") — or without appointment: manageEncounter(patient_id, provider_id, facility_id, encounter_date, action="create") 2. Add clinical data using managePatientVitals(), managePatientDrugs(), managePatientDiagnoses() 3. Review before signing: manageEncounter(patient_id, encounter_id, action="review") 4. Sign to finalize: manageEncounter(patient_id, encounter_id, action="sign") 5. If modifications needed: manageEncounter(patient_id, encounter_id, reason="reason for changes", action="unlock") When required parameters are missing, ask the user to provide the specific values rather than proceeding with defaults or auto-generated values. </instructions>
manageMessagesManage patient and provider messaging across SMS, WhatsApp, and secure messaging channels. <usecase> Send messages to patients, read inbox messages, and retrieve conversation threads. Supports SMS (Twilio/Telnyx), WhatsApp Business, and secure portal messaging. Use this for patient communication, follow-ups, appointment confirmations, and responding to patient inquiries. </usecase> <instructions> Actions: - "send": Send a message to a patient (requires patient_id, content, and facility_id). Channel options: - "sms": Send via text message (patient must have TEXT_NOTIFY_ENABLED) - "whatsapp": Send via WhatsApp (patient must be opted in) - "secure": Send via secure portal message (requires subject) - "auto": Automatically select best available channel (default) facility_id is required for all channels. Use getPracticeInfo() to look up facility IDs. For WhatsApp templates, provide template_name and placeholder values. For secure messages to providers, use recipient_member_ids. - "list": Show recent secure portal messages from inbox. Filter by section: "FROM_PATIENTS" (inbox) or "TO_PATIENTS" (sent). Use facility_id to filter by facility. Note: SMS and WhatsApp conversations are not available via list — use action='get_thread' with a patient_id to retrieve those. - "get_thread": Get full conversation history with a specific patient (requires patient_id). Filter by thread_channel to see only SMS, WhatsApp, secure, or all channels. Before sending clinical content, confirm with the provider. Routine messages (appointment reminders, general notifications) can be sent directly. </instructions>
managePatientRecallsManage patient recalls. <usecase> Patient recall and follow-up management - schedule preventive care reminders, follow-up appointments, and care plan reminders. Ensures patients receive timely care according to clinical guidelines. </usecase> <instructions> Actions: - "add": Schedule new recall (requires recall_type, notes, provider_id, facility_id) - "list": Show all patient recalls (optionally filter by type/date range) - "update": Modify existing recall (requires record_id, recall_type, notes — use action='list' first to get current values, then pass all required fields with your changes) - "delete": Remove recall (requires record_id). Ask the user if they are sure they want to delete the recall before proceeding. recall_type is a free-form string set by the practice (e.g. "Office Visit", "Follow-up", "Imaging", "Annual Physical"). Do not invent verbose names — use short descriptive terms. Scheduling: PREFER recall_date (ISO date string, e.g. "2026-07-10"). If using recall_time/recall_timeunit instead, recall_period is also REQUIRED (e.g. recall_time=3, recall_timeunit="Months", recall_period="after") — omitting recall_period causes a server error. Reminder timing: email_reminder_before/text_reminder_before in days (e.g., 7 for one week) Use getPracticeInfo() to get valid provider_id and facility_id values List filters: - type_filter: e.g., type_filter="Annual Physical" - from_date / to_date: e.g., from_date="2025-01-01", to_date="2025-12-31" (compares against recall_date when available) - limit: e.g., limit=25 When required parameters are missing, ask the user to provide the specific values rather than proceeding with defaults or auto-generated values. </instructions>
managePatientVitalsManage patient vitals and vital signs. <usecase> Complete patient vital signs management - record vitals during encounters, review vital trends, update incorrect readings, and track patient health metrics over time. Essential for clinical monitoring. </usecase> <instructions> Actions: - "add": Record new vitals (requires patient_id + vitals dict OR individual vital fields, plus encounter_id OR entry_date; defaults to today if neither provided). Check available vitals with getPracticeInfo(info_type='vitals') first to ensure all vital names and units are correct. - "list": Show patient vital history (optionally filter by vital name and/or date range) - "update": Modify existing vital record (requires record_id + fields to change) - "delete": Remove incorrect vital record (requires record_id) Vitals Format: - As dict: keys are EXACT CharmHealth vital names, values are "value unit" strings. Example: {"Systolic BP": "120 mmHg", "Diastolic BP": "80 mmHg", "Weight": "150 lbs", "Temp": "98 F"} - Individual: vital_name="Systolic BP", vital_value="120", vital_unit="mmHg" IMPORTANT: vital_name must be the exact CharmHealth API name. NEVER include units inside the name. Correct: "Systolic BP" | Wrong: "Systolic BP (mmHg)" or "Blood Pressure" Known names: Weight, Height, BMI, Temp, Systolic BP, Diastolic BP, Pulse Rate, Pulse Pattern, Pulse Volume, Vision Call getPracticeInfo(info_type='vitals') to get the full list of valid names and units for this practice. List filters: - vital_name_filter: e.g., vital_name_filter="Blood Pressure" (matches case-insensitively, substring ok) - from_date / to_date: e.g., from_date="2025-01-01", to_date="2025-12-31" - limit: e.g., limit=20 When required parameters are missing, ask the user to provide the specific values rather than proceeding with defaults or auto-generated values. </instructions>
manageTasksManage CharmHealth tasks. <usecase> Task management with task creation, updating, and listing. </usecase> <instructions> Actions: - "add": Create new task (requires task, owner_id (look up members using getPracticeInfo()), priority (0-Low, 1-Medium, 2-High, 3-Critical), status (Pending, In-progress, Completed), comments, due_date, reminder_options, tasklist. optional: patient_id if task is related to a patient) - "update": Modify existing task (requires task_id, task, owner_id, priority, status, tasklist — use manageTasks(action='list') first to get current values, then pass all required fields with your changes) - "list": Show tasks with filtering (supports view/date range/pagination plus client-side filters) - "change_status": Change the status of a task (requires task_id (use manageTasks(action='list') to get task_id) + new_status (Pending, In-progress, Completed)) When required parameters are missing, ask the user to provide the specific values rather than proceeding with defaults or auto-generated values. List filters: - status_filter: filter by status (e.g., status_filter="Pending") - priority_filter: "0"-"3" or "Low"/"Medium"/"High"/"Critical" - owner_filter: filter by owner_id - limit: max tasks to return (applied after filtering) Examples: - manageTasks(action="list", view="MyTasks", status_filter="In-progress", limit=20) - manageTasks(action="list", view="All", priority_filter="High", owner_filter="12345") </instructions>