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>
managePatientDiagnosesManage 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 status, code type, and/or date range) - "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" List filters: - status_filter: filter by diagnosis_status (e.g., status_filter="Active") - code_type_filter: filter by code_type (e.g., code_type_filter="ICD10") - from_date / to_date: best-effort date filtering (e.g., from_date="2025-01-01", to_date="2025-12-31") - limit: e.g., limit=25 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>