CharmHealth MCP Server
An MCP server for CharmHealth EHR that allows LLMs and MCP clients to interact with patient records, encounters, and practice information.
154
14 Tools
Signed
Built by Docker
Requires Secrets
Add to Docker Desktop
Version 4.43 or later needs to be installed to add the server automatically
Tools
| Name | Description |
|---|---|
getPracticeInfo | Get 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 When required parameters are missing, ask the user to provide the specific values rather than proceeding with defaults or auto-generated values. </instructions> |
managePatientRecalls | Manage 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 (requires only patient_id) - "update": Modify existing recall (requires record_id + fields to change) - "delete": Remove recall (requires record_id). Ask the user if they are sure they want to delete the recall before proceeding. Common recall types: "Annual Physical", "Mammogram", "Colonoscopy", "Lab Follow-up", "Medication Review" 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 When required parameters are missing, ask the user to provide the specific values rather than proceeding with defaults or auto-generated values. </instructions> |
managePatientVitals | Manage 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 + encounter_id + vitals dict OR individual vital fields). 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 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: {"Weight": "70 kg", "BP": "120/80 mmHg", "Pulse": "72 bpm", "Temperature": "98.6 F"} - Individual: vital_name="Weight", vital_value="70", vital_unit="kg" Common Vitals: Weight, Height, Blood Pressure (BP), Pulse Rate, Temperature, Respiratory Rate, Oxygen Saturation Use getPracticeInfo(info_type='vitals') to see available vital types and proper naming When required parameters are missing, ask the user to provide the specific values rather than proceeding with defaults or auto-generated values. </instructions> |
Manual installation
You can install the MCP server using:
Installation for