Listed from the MCP registry; nobody on Odel publishes it.
Deprecated. Deprecated by the publisher: Superseded by ai.councilof/gspc (remote https://councilof.ai/mcp). Kept visible; not deleted.
HL7 v2 / FHIR healthcare bridge — parse, map, validate, govern PHI (HIPAA/MDR).
Runs on your machine from its package; the steps are below.
At most: only reads or looks up information.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
uvx hl7-fhir-bridge-mcp
MCP client config
{
"mcpServers": {
"hl7-fhir-bridge": {
"command": "uvx",
"args": [
"hl7-fhir-bridge-mcp"
]
}
}
}mcp-name: io.github.CSOAI-ORG/hl7-fhir-bridge-mcp
Part of the CSOAI Layer-0 legacy-bridge family (sibling of cobol-bridge-mcp). Bridges healthcare legacy messaging (HL7 v2 pipe-delimited) and modern FHIR to ONE OS / CSOAI, and governs PHI.
parse_hl7v2(message) — message type + key patient fields from a pipe-delimited HL7 v2 message.hl7_to_fhir(message) — map HL7 v2 → a minimal FHIR R4 message Bundle (Patient + MessageHeader).validate_fhir(resource_json) — well-formed JSON + resourceType + basic shape.govern_phi(message_or_fhir) — detect PHI, surface HIPAA/MDR/GDPR-Art.9 risk + data-minimisation advice; attestable on the CSOAI ledger.pip install -e .
python server.py # stdio MCP server
The win: legacy HL7 / FHIR clinical data → CSOAI PHI governance/attestation → ONE OS. Pairs with hipaa-compliance-mcp + healthcare-ai-governance-mcp + eu-ai-act-compliance-mcp (Annex I medical devices).