An MCP server for CharmHealth EHR that allows LLMs and MCP clients to interact with patient records, encounters, and practice information.
162
14 Tools
Version 4.43 or later needs to be installed to add the server automatically
Tools
Name | Description |
---|---|
manageEncounter | 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> |
managePatientDrugs | 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> |
Manual installation
You can install the MCP server using:
Installation for