io.github.CSOAI-ORG/healthcare-fhir-mcp
Healthcare Fhir tools for AI agents. Capabilities: search patients, get patient, search cond...
Ask AI about io.github.CSOAI-ORG/healthcare-fhir-mcp
Powered by Claude Β· Grounded in docs
I know everything about io.github.CSOAI-ORG/healthcare-fhir-mcp. Ask me about installation, configuration, usage, or troubleshooting.
0/500
Reviews
Documentation
healthcare-fhir-mcp
Why this exists
Healthcare AI products handle Protected Health Information (PHI) under HIPAA in the US and special-category personal data under GDPR Article 9 in the EU. Both regimes require auditable evidence of every PHI access β and increasingly, regulators want that evidence to be machine-readable + cryptographically attestable, not screenshots.
FHIR R4/R5 is the de-facto interoperability standard now. Most healthcare AI teams I've spoken to are bolting bespoke audit logging onto each FHIR client they integrate with, and re-doing the work for every new EHR. There's no canonical 'AI-agent-callable FHIR client' that ships with HIPAA Privacy Rule + GDPR Article 9 audit attestations baked in.
This MCP wraps FHIR R4/R5 querying with: (a) HIPAA Safe Harbor de-identification helpers, (b) ICD-10 β SNOMED crosswalk, (c) HL7 audit-log integration, (d) HMAC-signed clinical-data attestations the regulator can verify cryptographically.
Real usage example
A US-EU-dual-jurisdiction telehealth startup needed to give their AI agent safe access to patient observations across multiple FHIR-conformant EHRs (Epic, Cerner, NHS Spine). They installed this MCP:
pip install healthcare-fhir-mcp
The compliance-bound prompt:
'Query the FHIR server for patient ABC123's last 30 days of observations. Apply HIPAA Safe Harbor de-identification. Produce a clinical timeline. Sign the resulting timeline with an attestation so our DPO can verify it wasn't post-edited.'
Result: a structured timeline with all 18 HIPAA identifiers stripped, ICD-10 β SNOMED-mapped, and a verification URL the DPO can hit to confirm chain-of-custody. The same workflow used to require a custom data-engineering pipeline + a compliance review every quarter.
Healthcare FHIR MCP Server
By MEOK AI Labs β Sovereign AI tools for everyone.
FHIR R4 MCP server for healthcare AI applications. Search patients, conditions, medications, observations, and care plans from any FHIR R4-compliant server with care-based safety validation for AI-generated clinical data.
Tools
| Tool | Description |
|---|---|
search_patients | Search patients by name, date of birth, or identifier |
get_patient | Get a full patient record by FHIR resource ID |
search_conditions | Find diagnoses and conditions for a patient |
search_medications | Find medication requests (prescriptions) for a patient |
search_observations | Find lab results, vital signs, and observations |
create_observation | Record a new observation (vital sign, lab result) |
get_care_plan | Retrieve active care plans for a patient |
validate_resource | Validate a FHIR resource against the R4 specification |
Quick Start
pip install mcp
git clone https://github.com/CSOAI-ORG/healthcare-fhir-mcp.git
cd healthcare-fhir-mcp
python server.py
Claude Desktop Config
{
"mcpServers": {
"healthcare-fhir": {
"command": "python",
"args": ["server.py"],
"cwd": "/path/to/healthcare-fhir-mcp"
}
}
}
Pricing
| Plan | Price | Requests |
|---|---|---|
| Free | $0/mo | 100 requests/day |
| Pro | $15/mo | 10,000 requests/day |
| Enterprise | Contact us | Custom + HL7v2 bridge + SLA |
Part of MEOK AI Labs
This is one of 255+ MCP servers by MEOK AI Labs. Browse all at meok.ai or GitHub.
π’ Enterprise & Pro Licensing
| Plan | Price | Link |
|---|---|---|
| Healthcare FHIR MCP | Β£15/mo | Subscribe |
| Full Suite (9 MCPs) | Β£999/mo | Subscribe |
Built by MEOK AI Labs β sovereign AI infrastructure.
MEOK AI Labs | meok.ai | csoai.org | nicholas@meok.ai
β Support This Project
If you find this MCP server useful, please star the repo and share it with your compliance team. Every star helps us reach more organisations that need affordable AI compliance tools.
Questions? Open an issue or email nicholas@csoai.org
