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
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>
managePatientNotesManage patient notes. <usecase> Quick clinical note management for important patient information - add care notes, provider communications, and clinical observations that need to be highlighted across all patient interactions. </usecase> <instructions> Actions: - "add": Add new clinical note (requires notes content) - "list": Show all patient notes (optionally filter by date range) - "update": Modify existing note (requires record_id + notes content) - "delete": Remove note (requires record_id). Ask the user if they are sure they want to delete the note before proceeding. Use for: Important care instructions, provider alerts, patient preferences, social determinants Formal encounter notes should use manageEncounter() instead List filters: - from_date / to_date: e.g., from_date="2025-01-01", to_date="2025-12-31" - limit: e.g., limit=50 When required parameters are missing, ask the user to provide the specific values rather than proceeding with defaults or auto-generated values. </instructions>