Listed from the MCP registry; nobody on Odel publishes it.

MCP server: One MCP server.

HL7 FHIR Bridge

@csoai-orgMCP server · External

HL7 v2 / FHIR healthcare bridge — parse, map, validate, govern PHI (HIPAA/MDR).

Data privacyv0.1.2Python
Freeno charge per call

Runs on your machine from its package; the steps are below.

What it does

  1. Reads
  2. Writes
  3. High impact

At most: only reads or looks up information.

What it costs

Free

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

PyPIhl7-fhir-bridge-mcpv0.1.1

Run

uvx hl7-fhir-bridge-mcp

MCP client config

{
  "mcpServers": {
    "hl7-fhir-bridge": {
      "command": "uvx",
      "args": [
        "hl7-fhir-bridge-mcp"
      ]
    }
  }
}
README1 min read

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.

Tools

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

Run

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

Similar modules

Browse Data privacy