HealthBridge MCP
Enables cross-hospital patient safety intelligence by detecting drug interactions, allergy conflicts, duplicate procedures, and medicine stock routing across multiple healthcare facilities.
README
๐ HealthBridge MCP System
Cross-hospital patient safety intelligence powered by Model Context Protocol (MCP).
๐ Overview
HealthBridge is an intelligent healthcare orchestration system that exposes Model Context Protocol (MCP) tools and resources to detect patient safety issues across a distributed, multi-hospital network. By unifying patient histories, HealthBridge acts as a singular intelligence layer preventing drug interactions, allergy conflicts, and duplicated procedures when patients move between different healthcare facilities.
โจ Key Highlights
- Universal Patient Timeline: A centralized
healthbridge://patients/{patient_id}MCP resource that aggregates visits, diagnoses, and prescriptions. - Cross-Hospital Safety: Proactively detects buried drug conflicts and missed allergies from previous hospital visits.
- Intelligent Stock Routing: Checks medicine availability across facilities and automatically reroutes prescriptions or requests replenishments.
- Context-Aware Scheduling: Evaluates diagnosis severity to assign appropriate urgency tiers for follow-up appointments.
๐จ Problem Statement
Healthcare data is heavily siloed. When a patient visits multiple hospitals, clinics, or pharmacies, their medical history becomes fragmented. This fragmentation leads to:
- Adverse Drug Events (ADEs): Prescribing medications that interact dangerously with drugs prescribed at a different facility.
- Missed Allergies: Prescribing drugs a patient is allergic to because the allergy was recorded in another hospital's system.
- Resource Inefficiency: Ordering expensive duplicate tests (e.g., Lipid Panels, MRIs) simply because the previous results are inaccessible.
- Inventory Shortages: Pharmacies running out of stock without an automated fallback mechanism to nearby clinics.
๐ก Our Solution
HealthBridge bridges these silos using the Model Context Protocol (MCP). Instead of relying on a centralized database that hospitals are reluctant to adopt, HealthBridge provides AI-driven agents with the tools to securely query cross-hospital histories, perform safety checks, and orchestrate inventory.
By exposing specialized MCP tools, HealthBridge empowers AI assistants to act as a universal safety net for healthcare providers.
๐ Workflow
The typical workflow involves an AI agent utilizing HealthBridge tools during a patient encounter:
sequenceDiagram
participant Doctor as Doctor (via AI Assistant)
participant Agent as AI Agent
participant HB as HealthBridge MCP
Doctor->>Agent: "Prescribe Aspirin 100mg to PAT-001 at HOSP-B"
rect rgb(30, 30, 30)
Note over Agent,HB: 1. Safety Check Phase
Agent->>HB: Call cross_hospital_safety_check(PAT-001, Aspirin)
HB-->>Agent: โ ๏ธ HIGH RISK: Warfarin conflict (from HOSP-A)
end
Agent-->>Doctor: Warn about interaction. Doctor changes to safe alternative.
rect rgb(30, 30, 30)
Note over Agent,HB: 2. Inventory Phase
Agent->>HB: Call medicine_availability_check(HOSP-B, SafeDrug)
HB-->>Agent: ๐ Rerouted to HOSP-C (In Stock)
end
rect rgb(30, 30, 30)
Note over Agent,HB: 3. Logging & Follow-up Phase
Agent->>HB: Call log_patient_visit(...)
HB-->>Agent: Visit logged to global history
Agent->>HB: Call followup_scheduler(PAT-001, severity)
HB-->>Agent: ๐ข Routine follow-up scheduled (30 days)
end
Agent-->>Doctor: Prescription rerouted and visit logged successfully.
๐๏ธ Architecture
HealthBridge operates via an MCP server interacting with a static data layer, presenting a unified interface for AI clients and a visual widget.
graph TD
Client[AI Client / Claude Desktop] -->|MCP Protocol| Server[HealthBridge FastMCP Server]
Widget[Browser Widget] -->|HTTP/SSE| Server
subgraph HealthBridge Core
Server --> T1[log_patient_visit]
Server --> T2[cross_hospital_safety_check]
Server --> T3[medicine_availability_check]
Server --> T4[followup_scheduler]
Server --> R1[(Resource: patient_history)]
end
subgraph Data Layer
T1 -.-> D1[patients.json]
R1 -.-> D1
T2 -.-> D2[drug_interactions.json]
T3 -.-> D3[facility_stock.json]
T2 -.-> D1
end
classDef tools fill:#2a4d69,stroke:#4b86b4,stroke-width:2px;
classDef data fill:#1f2833,stroke:#66fcf1,stroke-width:2px;
class T1,T2,T3,T4 tools;
class D1,D2,D3 data;
๐ ๏ธ MCP Tools & Resources
Tools
| Tool Name | Description |
|---|---|
log_patient_visit |
Records a new encounter into the shared patient history. |
cross_hospital_safety_check |
Detects drug interactions, allergy conflicts, and duplicate tests across all past visits. |
medicine_availability_check |
Checks stock, reroutes to nearby facilities if empty, or requests replenishment. |
followup_scheduler |
Assigns follow-up urgency tier with contextual escalation. |
Resources
healthbridge://patients/{patient_id}: Provides the full, cross-hospital timeline and aggregated allergy lists for a specific patient.
๐ Quick Start
1. Install Dependencies
pip install -r requirements.txt
2. Run the MCP Server
# stdio mode (for standard MCP clients)
python server.py
# HTTP/SSE mode (for browser widget live wiring)
python server.py --http
3. Open the Dashboard Widget
The frontend widget allows you to visualize the timeline and tool orchestration.
start widget/index.html
(Ensure CONFIG.USE_MCP_API = true in app.js if running alongside the HTTP server)
4. Run Tests
Validate the system logic with the pytest suite:
python -m pytest tests/ -v
๐งช Demo Scenarios
HealthBridge comes with planted data (data/patients.json) to test various edge cases:
| Scenario | Patient | Trigger | Expected Outcome |
|---|---|---|---|
| Buried Conflict | PAT-001 (Anil) | Prescribe aspirin |
โ ๏ธ Detects warfarin interaction from HOSP-A |
| Duplicate Test | PAT-003 (Priya) | View history | ๐ Identifies Lipid Panel at 2 hospitals within 8 days |
| Missed Allergy | PAT-005 (Ravi) | Prescribe amoxicillin |
๐จ Flags penicillin cross-reactivity from 2024 |
| Stock Reroute | Any at HOSP-B | Prescribe metformin |
๐ Reroutes to HOSP-C (Green Valley Clinic) |
| Out of Stock | Any | Prescribe atorvastatin |
๐ด Out of Stock โ Replenishment Requested |
| Urgent Care | PAT-007 (Meena) | severe AMI diagnosis |
๐ด Urgent Follow-up โ 3 days, doctor notified |
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.