HUB
Sign inSign up
charmhealth-mcp-server logo

mcp/charmhealth-mcp-server

Verified Publisher

By mcp

•Updated 5 months ago

An MCP server for CharmHealth EHR that allows LLMs and MCP clients to interact with patient recor...

Image
Machine learning & AI
0

10K+

mcp/charmhealth-mcp-server repository overview

⁠CharmHealth MCP Server

An MCP server for CharmHealth EHR that allows LLMs and MCP clients to interact with patient records, encounters, and practice information.

What is an MCP Server?⁠

⁠MCP Info

⁠Image Building Info

AttributeDetails
Dockerfilehttps://github.com/CharmHealth/charm-mcp-server/blob/dae9f695b9ba82026959574d58db7e941703f026/Dockerfile⁠
Commitdae9f695b9ba82026959574d58db7e941703f026
Docker Image built byDocker Inc.
Docker Scout Health ScoreDocker Scout Health Score
Verify SignatureCOSIGN_REPOSITORY=mcp/signatures cosign verify mcp/charmhealth-mcp-server --key https://raw.githubusercontent.com/docker/keyring/refs/heads/main/public/mcp/latest.pub
LicenceMIT License

⁠Available Tools (17)

Tools provided by this ServerShort Description
findPatientsFind patients.
getPracticeInfoGet practice information.
manageAppointmentsManage appointments.
manageEncounterManage encounters.
manageFaxSend faxes and check fax delivery status.
manageMessagesManage patient and provider messaging across SMS, WhatsApp, and secure messaging channels.
managePatientManage patients.
managePatientAllergiesManage patient allergies.
managePatientDiagnosesManage patient diagnoses.
managePatientDrugsManage patient drugs and supplements.
managePatientFilesManage patient files and documents.
managePatientLabsManage patient laboratory results.
managePatientNotesManage patient notes.
managePatientRecallsManage patient recalls.
managePatientVitalsManage patient vitals and vital signs.
manageTasksManage CharmHealth tasks.
reviewPatientHistoryReview patient history.

⁠Tools Details

⁠Tool: findPatients

Find patients.

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. 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.

ParametersTypeDescription
age_maxstring optional
age_minstring optional
blood_groupstring optional
category_idstring optional
citystring optional
countrystring optional
created_afterstring optional
created_beforestring optional
facility_idstring optional
genderstring optional
has_phr_accountstring optional
languagestring optional
limitstring optional
marital_statusstring optional
modified_afterstring optional
modified_beforestring optional
pagestring optional
postal_codestring optional
querystring optional
search_typestring optional
sort_bystring optional
sort_orderstring optional
statestring optional
statusstring optional

⁠Tool: getPracticeInfo

Get practice information.

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. - "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 - "templates": List all available SOAP templates (id, name, type) for the practice - "template_details": Full template schema (widgets + entries) for given template_ids (comma-separated)

When required parameters are missing, ask the user to provide the specific values rather than proceeding with defaults or auto-generated values.

ParametersTypeDescription
info_typestring optional
template_idsstring optional

⁠Tool: manageAppointments

Manage appointments.

Complete appointment lifecycle management - schedule new appointments, reschedule existing ones, cancel appointments, and list appointments with flexible filtering. Handles the full appointment workflow. 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; optionally filter by status/provider/mode)

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

List filters (applied after fetching all appointments in the date range):

  • status_filter: e.g., status_filter="Confirmed"
  • provider_filter: provider_id or provider_name substring (e.g., provider_filter="12345" or provider_filter="Smith")
  • mode_filter: e.g., mode_filter="Video Consult"
  • limit: e.g., limit=25

When required parameters are missing, ask the user to provide the specific values rather than proceeding with defaults or auto-generated values.

ParametersTypeDescription
actionstring
appointment_datestring optional
appointment_idstring optional
appointment_timestring optional
cancel_reasonstring optional
consent_formsstring optional
delete_typestring optional
duration_minutesstring optional
end_datestring optional
end_date_rangestring optional
facility_idstring optional
facility_idsstring optional
frequencystring optional
limitstring optional
member_idsstring optional
message_to_patientstring optional
modestring optional
mode_filterstring optional
patient_idstring optional
provider_double_bookingstring optional
provider_filterstring optional
provider_idstring optional
questionnairestring optional
reasonstring optional
receipt_idstring optional
repetitionstring optional
resource_double_bookingstring optional
resource_idstring optional
start_datestring optional
statusstring optional
status_filterstring optional
status_idsstring optional
visit_type_idstring optional
weekly_daysstring optional

⁠Tool: manageEncounter

Manage encounters.

Complete encounter workflow - create, review, and sign encounters with comprehensive clinical documentation. Essential for clinical workflow from initial documentation through final signature. 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.

ParametersTypeDescription
patient_idstring
actionstring optional
appointment_idstring optional
chief_complaintstring optional
encounter_datestring optional
encounter_idstring optional
encounter_modestring optional
end_datestring optional
entriesstring optional
facility_idstring optional
filter_bystring optional
pagestring optional
per_pagestring optional
provider_idstring optional
reasonstring optional
start_datestring optional
template_idsstring optional
visit_type_idstring optional

⁠Tool: manageFax

Send faxes and check fax delivery status.

Fax clinical documents (referrals, records, prior auth forms) to providers, facilities, pharmacies, and insurance companies. Check delivery status of sent faxes. Actions: - "send": Fax a document (requires recipient_fax_number, recipient_name, document_content_base64). document_content_base64 must be a base64-encoded PDF. Optionally include subject, remarks, and reference for the cover page. facility_id determines which facility's fax credentials and return number are used.
  • "status": Check fax delivery status (requires fax_id). Status values: QUEUED, SENT, FAILED, YET_TO_SEND.

Common fax use cases:

  • Referral letters to specialists
  • Medical records requests
  • Prior authorization forms to insurance
  • Prescription orders to pharmacies without e-prescribe
ParametersTypeDescription
actionstring
document_content_base64string optional
facility_idstring optional
fax_idstring optional
recipient_fax_numberstring optional
recipient_namestring optional
referencestring optional
remarksstring optional
subjectstring optional

⁠Tool: manageMessages

Manage patient and provider messaging across SMS, WhatsApp, and secure messaging channels.

Send messages to patients, read inbox messages, and retrieve conversation threads. Supports SMS (Twilio/Telnyx), WhatsApp Business, and secure portal messaging. Use this for patient communication, follow-ups, appointment confirmations, and responding to patient inquiries. Actions: - "send": Send a message to a patient (requires patient_id, content, and facility_id). Channel options: - "sms": Send via text message (patient must have TEXT_NOTIFY_ENABLED) - "whatsapp": Send via WhatsApp (patient must be opted in) - "secure": Send via secure portal message (requires subject) - "auto": Automatically select best available channel (default) facility_id is required for all channels. Use getPracticeInfo() to look up facility IDs. For WhatsApp templates, provide template_name and placeholder values. For secure messages to providers, use recipient_member_ids.
  • "list": Show recent secure portal messages from inbox. Filter by section: "FROM_PATIENTS" (inbox) or "TO_PATIENTS" (sent). Use facility_id to filter by facility. Note: SMS and WhatsApp conversations are not available via list — use action='get_thread' with a patient_id to retrieve those.

  • "get_thread": Get full conversation history with a specific patient (requires patient_id). Filter by thread_channel to see only SMS, WhatsApp, secure, or all channels.

Before sending clinical content, confirm with the provider. Routine messages (appointment reminders, general notifications) can be sent directly.

ParametersTypeDescription
actionstring
channelstring optional
contentstring optional
facility_idstring optional
message_typestring optional
pagestring optional
page_sizestring optional
patient_idstring optional
recipient_member_idsstring optional
sectionstring optional
subjectstring optional
template_body_placeholdersstring optional
template_header_placeholdersstring optional
template_namestring optional
thread_channelstring optional

⁠Tool: managePatient

Manage patients.

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. 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.

ParametersTypeDescription
actionstring
address_line1string optional
address_line2string optional
agestring optional
areastring optional
birth_orderstring optional
blood_groupstring optional
caregiversstring optional
categoriesstring optionalCategories: Pass as list like [{"category_id": "category_123"}]
cause_of_deathstring optional
citystring optional
countrystring optional
county_codestring optional
custom_field_1string optional
custom_field_2string optional
custom_field_3string optional
custom_field_4string optional
custom_field_5string optional
date_of_birthstring optional
deceasedstring optional
districtstring optional
dodstring optional
duplicate_checkstring optional
emailstring optional
email_notificationstring optional
emergency_contact_namestring optional
emergency_contact_phonestring optional
emergency_extnstring optional
employment_statusstring optional
ethnicitystring optional
facility_idsstring optional
first_namestring optional
genderstring optional
gender_identitystring optional
guarantorstring optional
home_phonestring optional
id_qualifiersstring optional
introductionstring optional
is_multiple_birthstring optional
languagestring optional
last_namestring optional
linked_patient_idstring optional
maiden_namestring optional
marital_statusstring optional
middle_namestring optional
mother_first_namestring optional
mother_last_namestring optional
nick_namestring optional
patient_idstring optional
payment_end_datestring optional
payment_sourcestring optional
payment_start_datestring optional
phonestring optional
post_boxstring optional
preferred_communicationstring optional
primary_phonestring optional
racestring optional
record_idstring optional
rep_first_namestring optional
rep_last_namestring optional
send_phr_invitestring optional
sexual_orientationstring optional
smoking_statusstring optional
source_namestring optional
source_valuestring optional
statestring optional
suffixstring optional
text_notificationstring optional
update_specific_detailsstring optional
voice_notificationstring optional
work_phonestring optional
work_phone_extnstring optional
zip_codestring optional

⁠Tool: managePatientAllergies

Manage patient allergies.

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. Actions: - "add": Document new allergy (requires allergen, allergy_type, severity, reactions, allergy_date) - "list": Show all patient allergies (optionally filter by severity/type) - "update": Modify existing allergy (requires record_id, allergen, allergy_type, severity, allergy_status — use action='list' first to get current values, then pass all required fields with your changes) - "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" Allergy types: "Medication", "Drug Substance", "Environmental", "Food", "Plant", "Animal", "Latex" Status values: "Active", "Inactive"

List filters:

  • severity_filter: e.g., severity_filter="Severe"
  • type_filter: e.g., type_filter="Drug"
  • 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.

ParametersTypeDescription
actionstring
patient_idstring
allergenstring optional
allergy_datestring optional
allergy_statusstring optional
allergy_typestring optional
commentsstring optional
limitstring optional
reactionsstring optional
record_idstring optional
severitystring optional
severity_filterstring optional
type_filterstring optional

⁠Tool: managePatientDiagnoses

Manage patient diagnoses.

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. 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.

ParametersTypeDescription
actionstring
patient_idstring
code_typestring optional
code_type_filterstring optional
commentsstring optional
diagnosis_codestring optional
diagnosis_namestring optional
diagnosis_orderstring optional
diagnosis_statusstring optional
encounter_idstring optional
from_datestring optional
limitstring optional
record_idstring optional
status_filterstring optional
to_datestring optional

⁠Tool: managePatientDrugs

Manage patient drugs and supplements.

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. 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). IMPORTANT: drug name and strength CANNOT be changed via update — use discontinue + add instead. Updatable fields: directions, dispense, refills, status. - "discontinue": Stop drug (requires record_id) - "list": Show all patient drugs by type (filter by substance_type, optionally filter by status)

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 List filters:

  • status_filter: e.g., status_filter="active"
  • limit: e.g., limit=25 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.

ParametersTypeDescription
actionstring
patient_idstring
check_allergiesstring optional
commentsstring optional
directionsstring optional
dosagestring optional
dosage_unitstring optional
dose_formstring optional
drug_namestring optional
encounter_idstring optional
end_date`st

[...]

Install from MCP:Hub

Tag summary

Content type

Image

Digest

sha256:23c0372dc…

Size

110.7 MB

Last updated

5 months ago

docker pull mcp/charmhealth-mcp-server

This week's pulls

Pulls:

49

Last week