his-tools
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@his-toolsget a pre-visit brief for patient pid 4a9f: conditions, meds, and any drug interactions"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
his-mcp-agents
An MCP server for hospital information system (HIS) data, plus a supervisor/worker agent graph that writes a grounded pre-visit brief for a clinician.
Portfolio demo (Sept 2026). Mock FHIR-shaped data, runs fully offline, 8 tests. It shows the design decisions I would make when putting LLM agents next to an HIS — not a production system.
MCP (stdio) read-only, de-identified
LLM / agent ───────────────► his-tools server ───────────────────────► FHIR store
│ every call → audit.jsonl
│ writes = draft only; clinician confirms out-of-bandWhat it demonstrates
Concern | How it is handled |
PHI never reaches the model | Tools return a pseudonymous |
Auditability | Every tool call is appended to |
Human-in-the-loop writes | The agent can only call |
Grounding | The brief is built only from tool results and guideline chunks, each line carries |
Multi-agent routing | LangGraph: |
Cost / latency visibility | Every node appends |
Model-agnostic |
|
Related MCP server: FhirMCP
Run
pip install -r requirements.txt
pytest -q # 8 tests
python -m agents.graph # prints the brief + per-node trace
python -m his_mcp.server # MCP server over stdio (e.g. register in Claude Desktop)
LLM_BACKEND=ollama OLLAMA_MODEL=qwen2.5:7b python -m agents.graphTools exposed
list_patients · get_encounters · get_conditions · get_observations(abnormal_only) · get_medications · check_interactions(extra_drugs) · draft_medication_request
Limits (on purpose)
Mock data; the interaction table has three illustrative pairs and is not clinical knowledge.
BM25 over markdown stands in for a vector store; the retrieval interface is the same.
Guideline texts are short illustrative summaries I wrote, not clinical guidance.
This server cannot be deployed
Maintenance
Related MCP Connectors
Guardrailed FHIR access for AI agents: PHI redaction, audit trail, step-up auth, tenant isolation
Read patient-authorized EHR records: medications, labs, conditions, allergies. Consent-bounded.
Synthetic EHR: medications, labs, conditions, allergies, immunizations, FHIR R4. No API key.
HealthGuard - 12-tool health/medical AI safety MCP: PII redaction, HIPAA, GDPR Art.9.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables LLM-based agents to interact with FHIR healthcare data through natural language prompts, providing full CRUD operations on FHIR resources, document processing, and semantic search capabilities.13100MIT
- AlicenseNot gradedqualityBmaintenanceEnables LLMs to securely interact with FHIR healthcare servers and HL7 terminology services. Provides comprehensive healthcare data operations with built-in PHI protection, audit logging, and SMART on FHIR authentication.MIT

vClinic MCP Serverofficial
FlicenseNot gradedqualityDmaintenanceEnables AI agents to manage virtual clinic data including patients, visits, diagnoses, treatments, lab/radiology orders, and search medical literature and internal knowledge base.-- FlicenseNot gradedqualityBmaintenanceEnables LLMs to interact with clinical patient records using tools for document ingestion, structured conversion, patient profiling, record listing, search, and secure Q&A over patient documentation.-