Hl7 Fhir Bridge Mcp

io.github.CSOAI-ORGPublished by GitHub account CSOAI-ORGv0.1.2Updated Oct 30, 2026

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

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Local stdio MCP server that parses HL7 v2 messages, maps them to minimal FHIR R4 bundles, validates FHIR resources, and flags PHI risk.

What you can do
  • Parse pipe-delimited HL7 v2 messages for message type and key patient fields
  • Map HL7 v2 messages into a minimal FHIR R4 Bundle with Patient and MessageHeader
  • Validate FHIR resource JSON for well-formedness, resourceType and basic shape
  • Detect PHI and surface HIPAA, MDR and GDPR Article 9 risk with data-minimisation advice
When to use it
Useful when working with legacy healthcare messaging and you want an assistant to inspect HL7 v2 messages, convert them toward FHIR R4, sanity-check FHIR JSON, or review clinical data for PHI exposure before sharing it.
Requirements
Runs as a local Python process over stdio; install the hl7-fhir-bridge-mcp package from PyPI (or the source tree) and start the server with python. No authentication, environment variables or headers are declared.
Before you install
The server handles PHI, so messages and resources you pass to it go to the local model context; the governance tool reports risk and data-minimisation advice and mentions attestation on a CSOAI ledger, which may record data outside your machine. Validation is described as basic shape checking, not full conformance, so do not rely on it as a compliance guarantee.

Installation

In SourceWeft

  1. Open Hl7 Fhir Bridge Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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

Source: README.md at commit 10cc185

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.