DICOM/HL7/FHIR — Claude Code MCP server: install
Inspect DICOM tags and HL7v2 messages, map data to FHIR, or connect to PACS. Built for healthcare interoperability work.
claude mcp add dicom-hl7-mcp-server -e DICOM_HL7_LICENSE_KEY=<DICOM_HL7_LICENSE_KEY> -- uvx dicom-hl7-mcpWhat DICOM/HL7/FHIR Interoperability MCP Server does
Free reference tools look up DICOM tags, describe vendor-specific quirks, and turn HL7 v2.x messages into readable output. Licensed tools map DICOM fields to HL7v2 and HL7v2 to FHIR R4, validate messages, and create Mirth Connect channel configurations.
PACS features cover study searches, metadata retrieval, and image transfer through C-MOVE; DICOMweb is supported too. Premium features need a DICOM_HL7_LICENSE_KEY, and PACS access needs connection settings. PACS results contain PHI. C-MOVE starts disabled, and sending PHI to a cloud LLM depends on your organization’s policies.
What it helps with
- look up a DICOM tag by number or keyword
- read an HL7 v2.x message as structured text
- map HL7v2 fields to FHIR R4 resources
- generate a Mirth Connect channel configuration
- search PACS for a study and retrieve its metadata
Example prompts for the agent
- Look up DICOM tag
(0008,0050)and describe any vendor-specific details. - Parse this HL7 v2.x message and explain the PID segment fields.
- Map the fields in this HL7v2 message to FHIR R4 resources.
How to install DICOM/HL7/FHIR Interoperability MCP Server
Platform CLI
claude mcp add dicom-hl7-mcp-server -e DICOM_HL7_LICENSE_KEY=<DICOM_HL7_LICENSE_KEY> -- uvx dicom-hl7-mcpReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from dicom-hl7-mcp <command>
Platform CLI
codex mcp add dicomhl7fhir-interoperability-mcp-server --env DICOM_HL7_LICENSE_KEY=<DICOM_HL7_LICENSE_KEY> -- uvx dicom-hl7-mcpReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from dicom-hl7-mcp <command>
Config file
{
"mcpServers": {
"dicomhl7fhir-interoperability-mcp-server": {
"command": "uvx",
"args": [
"dicom-hl7-mcp"
],
"env": {
"DICOM_HL7_LICENSE_KEY": "<DICOM_HL7_LICENSE_KEY>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from dicom-hl7-mcp <command>
Config file
{
"servers": {
"dicomhl7fhir-interoperability-mcp-server": {
"type": "stdio",
"command": "uvx",
"args": [
"dicom-hl7-mcp"
],
"env": {
"DICOM_HL7_LICENSE_KEY": "<DICOM_HL7_LICENSE_KEY>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from dicom-hl7-mcp <command>
Platform CLI
gemini mcp add -e DICOM_HL7_LICENSE_KEY=<DICOM_HL7_LICENSE_KEY> dicomhl7fhir-interoperability-mcp-server uvx dicom-hl7-mcpReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from dicom-hl7-mcp <command>
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about DICOM/HL7/FHIR Interoperability MCP Server
How do I install DICOM/HL7/FHIR Interoperability MCP Server in Claude Code?
Run claude mcp add dicom-hl7-mcp-server -e DICOM_HL7_LICENSE_KEY=<DICOM_HL7_LICENSE_KEY> -- uvx dicom-hl7-mcp. This registers the server with uvx and passes its license key.
What does DICOM/HL7/FHIR Interoperability MCP Server do?
It provides tools for inspecting DICOM tags, parsing HL7v2 messages, mapping data to FHIR R4, and accessing PACS. Mapping, validation, and PACS features require a premium license.
What is required to connect to a PACS?
Traditional DICOM connections use PACS settings such as AE title, host, and port; DICOMweb connections use a base URL and may need authentication details. PACS features require a license key, and C-MOVE must be enabled with DICOM_HL7_PACS_ALLOW_RETRIEVE=true.
