CharmHealth MCP Server

Find patients. <usecase> Find patients quickly using natural search terms or specific criteria. Handles everything from "find John Smith" to complex searches like "elderly diabetes patients in California". Essential first step for any patient-related task. </usecase> <instructions> Quick searches: Use search_type="name" with query="John Smith" for basic name searches Phone lookups: Use search_type="phone" with query="555-1234" (handles any format) Medical record: Use search_type="record_id" with query="MR123456" Complex searches: Use search_type="advanced" with multiple criteria: - Age ranges: age_min=65, age_max=80 for elderly patients - Location: state="CA", city="Los Angeles" for geographic filtering - Medical: blood_group="O+", language="Spanish" for clinical needs Always returns patient_id needed for other tools. Start here before any patient operations. When required parameters are missing, ask the user to provide the specific values rather than proceeding with defaults or auto-generated values. </instructions>

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>

Manage appointments. <usecase> Complete appointment lifecycle management - schedule new appointments, reschedule existing ones, cancel appointments, and list appointments with flexible filtering. Handles the full appointment workflow. </usecase> <instructions> Actions: - "schedule": Create new appointment (requires patient_id, provider_id, facility_id, appointment_date, appointment_time). Check the provider's availability with manageAppointments(action='list') and provider_id, and across all facilities for the provider before suggesting a time. - "reschedule": Change existing appointment time (requires appointment_id + new scheduling details) - "cancel": Cancel appointment (requires appointment_id + cancel_reason) - "list": Show appointments with filtering (requires start_date, end_date_range, facility_ids) Time format: Use 12-hour format like "09:30 AM" or "02:15 PM" For recurring: Set repetition to "Weekly" or "Daily" and provide frequency + end_date For double booking: Use provider_double_booking="allow" or resource_double_booking="allow" to override checks For cancellation: Use delete_type "Current" for single appointment or "Entire" for recurring series When required parameters are missing, ask the user to provide the specific values rather than proceeding with defaults or auto-generated values. </instructions>

Manage 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: - "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: - Requires: patient_id, provider_id, facility_id, encounter_date - Optional: appointment_id (to create from existing appointment), 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 Recommended workflow: 1. Create encounter: 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>

Manage patients. <usecase> Complete patient management with comprehensive demographic, social, and administrative data. Handles patient creation, updates, status changes, and complex relationships. Supports all CharmHealth patient data fields for complete EHR functionality. </usecase> <instructions> Actions: - "create": Add new patient (requires first_name, last_name, gender, date_of_birth OR age, facility_ids) - "update": Modify existing patient (requires patient_id + fields to change). - "activate": Reactivate deactivated patient (requires patient_id only) - "deactivate": Deactivate patient (requires patient_id only) Update Modes: - update_specific_details=True: Only updates the fields you provide, preserves all other existing data (RECOMMENDED, Default) - update_specific_details=False: Complete record update - must provide all fields or existing data will be lost Demographics: Supports comprehensive patient information including social history, family data Addresses: If any address field provided, country is required (defaults to US) Facilities: Pass as list of facility IDs like "facility_123,facility_456". Categories: Pass as list like [{"category_id": "category_123"}] Complex Relationships: - caregivers: [{"first_name": str, "last_name": str, "relationship": str, "contact": {...}, "address": {...}}] - guarantor: [{"first_name": str, "last_name": str, "relationship": str, "contact": {...}, "address": {...}}] - id_qualifiers: [{"id_qualifier": 1-8 or 99, "id_of_patient": "ID_value"}] When required parameters are missing, ask the user to provide the specific values rather than proceeding with defaults or auto-generated values. </instructions>

Manage patient allergies. <usecase> Critical allergy management with safety alerts - document patient allergies, update allergy information, and maintain allergy safety checks. Essential for safe prescribing and clinical decision-making. </usecase> <instructions> Actions: - "add": Document new allergy (requires allergen, allergy_type, severity, reactions, allergy_date) - "list": Show all patient allergies (requires only patient_id) - "update": Modify existing allergy (requires record_id + fields to change) - "delete": Remove allergy record (requires record_id) Safety critical: Always check allergies before prescribing medications. Common allergens: "Penicillin", "Latex", "Shellfish", "Nuts", "Contrast dye" Severity levels: "Mild", "Moderate", "Severe", "Life-threatening" When required parameters are missing, ask the user to provide the specific values rather than proceeding with defaults or auto-generated values. </instructions>

Manage patient diagnoses. <usecase> Complete diagnosis management for patient problem lists - add new diagnoses, update existing conditions, and maintain accurate medical problem lists. Essential for clinical reasoning and care planning. </usecase> <instructions> Actions: - "add": Add new diagnosis (requires diagnosis_name, diagnosis_code, code_type) - "list": Show all patient diagnoses (optionally filter by encounter_id) - "update": Modify existing diagnosis (requires record_id + fields to change) - "delete": Remove diagnosis (requires record_id). Ask the user if they are sure they want to delete the diagnosis before proceeding. Code types: "ICD10", "SNOMED" Status options: "Active", "Inactive", "Resolved" Use encounter_id to link diagnosis to specific visit for billing and documentation When required parameters are missing, ask the user to provide the specific values rather than proceeding with defaults or auto-generated values. </instructions>

Manage patient drugs and supplements. <usecase> Unified drug management for medications, supplements, and vitamins - prescribe medications, document supplements, manage drug interactions. Includes automatic allergy checking and comprehensive drug safety workflow for optimal patient care. </usecase> <instructions> Actions: - "add": Prescribe new drug (requires drug_name, directions for medications; drug_name, dosage for supplements) - "update": Modify existing prescription (requires record_id + fields to change) - "discontinue": Stop drug (requires record_id) - "list": Show all patient drugs by type (optionally filter by substance_type) Substance Types: - "medication": Prescription drugs (requires directions, refills) - "supplement": OTC supplements/vitamins (requires dosage as integer) - "vitamin": Specific vitamins (requires dosage as integer) Safety: Automatically checks allergies before prescribing unless check_allergies=False For medications: Use clear directions like "Take 1 tablet by mouth twice daily with food" For supplements: Provide dosage as integer (e.g., 5) and use strength for units (e.g., "500mg") When required parameters are missing, ask the user to provide the specific values rather than proceeding with defaults or auto-generated values. </instructions>

Manage patient files and documents. <usecase> Patient file and document management - upload patient photos, manage identity documents, and send PHR (Personal Health Record) invitations. Handles the complete patient file workflow. </usecase> <instructions> Actions: - "upload_photo": Upload patient photo (requires photo_file path) - "delete_photo": Remove patient photo (requires only patient_id) - "upload_id": Upload identity document (requires id_file, id_qualifier) - "send_phr_invite": Send PHR portal invitation (requires email) ID Qualifiers: military_id, state_issued_id, drivers_license_id, passport_id, social_security_number, etc. File paths should be absolute paths to image/PDF files on the system. When required parameters are missing, ask the user to provide the specific values rather than proceeding with defaults or auto-generated values. </instructions>

Manage patient laboratory results. <usecase> Complete laboratory results management - list lab results, get detailed reports, and add new lab results. Handles the full lab workflow for clinical decision-making. </usecase> <instructions> Actions: - "list": Show lab results with filtering (optionally filter by patient_id, reviewer_id, status) - "get_details": Get detailed lab report (requires group_id OR lab_order_id) - "add_result": Add new lab results (requires patient_id + result_details) For detailed results: Use group_id for result groups or lab_order_id for specific orders For adding results: Provide structured result_details with tests, parameters, and values Status codes: 0 for pending, 2 for final results When required parameters are missing, ask the user to provide the specific values rather than proceeding with defaults or auto-generated values. </instructions>