HL7 Tools — Parser, Validator, FHIR R4 Converter

Name: HL7 Tools — Parser, Validator, FHIR R4 Converter
Author: easysolutions906

@easysolutions906

HL7 Tools — Parser, Validator, FHIR R4 Converter について

Parse, explain, validate, generate, diff, and convert HL7 v2 messages. Supports versions 2.3-2.8 with 600+ CARISTIX field definitions. Bidirectional HL7 v2 to FHIR R4 conversion. 9 tools.

#hl7 #fhir #healthcare #parser #interoperability #mcp

基本情報

カテゴリ

その他

トランスポート

stdio

公開者

easysolutions906

投稿者

easysolutions906

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "hl7": {
      "command": "npx",
      "args": [
        "-y",
        "@easysolutions906/hl7-tools"
      ]
    }
  }
}

ツール

Parse a raw HL7 v2 pipe-delimited message into structured JSON with named fields, data types, and descriptions. Supports versions 2.3 through 2.8.

Parse an HL7 v2 message and return a human-readable explanation of every segment, field name, data type, and value. Great for understanding unfamiliar messages.

Validate an HL7 v2 message: checks required segments for the message type, required fields, timestamp formats, and segment ordering. Returns issues with severity levels (error/warning/info).

Generate a sample HL7 v2 message with realistic but fake test data. Supported types: ADT^A01, ADT^A08, ADT^A04, ORM^O01, ORU^R01, SIU^S12, MDM^T02, DFT^P03, VXU^V04

Compare two HL7 v2 messages and return all differences: version, message type, segment additions/removals, and field-level changes with named fields.

Convert an HL7 v2 message to a FHIR R4 Bundle. Maps PID->Patient, PV1->Encounter, DG1->Condition, OBX->Observation, OBR->DiagnosticReport, AL1->AllergyIntolerance, IN1->Coverage, RXA->Immunization, ORC->ServiceRequest, MSH->MessageHeader.

Convert a FHIR R4 Bundle back to an HL7 v2 message. Maps Patient->PID, Encounter->PV1, Condition->DG1, Observation->OBX.

List all known HL7 v2 segments with their field counts. Use to discover available segments for a given version.

Look up a specific HL7 field definition by segment and field number. Returns the field name, data type, optionality, repetition, and description. Example: segment="PID", field=3 returns "Patient Identifier List".

概要

What is HL7 Tools — Parser, Validator, FHIR R4 Converter?

It is an MCP server and REST API for parsing, explaining, validating, generating, and diffing HL7 v2.x messages, as well as converting between HL7 v2 and FHIR R4 Bundles. It is designed for developers who need to handle HL7 healthcare data.

How to use HL7 Tools — Parser, Validator, FHIR R4 Converter?

Install with npm install, then run in HTTP mode on port 3200 using npm run dev or in stdio mode for MCP clients using npm start. The server provides nine MCP tools (e.g., hl7_parse, hl7_validate, hl7_to_fhir) and a full REST API for each operation.

Key features of HL7 Tools — Parser, Validator, FHIR R4 Converter

Parse raw HL7 v2 messages into JSON
Explain messages with human-readable field descriptions
Validate messages against 20+ message types
Generate realistic test messages for common types
Diff two HL7 messages field by field
Convert HL7 v2 to FHIR R4 and back
Look up segment/field definitions for versions 2.3–2.8

Use cases of HL7 Tools — Parser, Validator, FHIR R4 Converter

Parsing and inspecting incoming HL7 v2 messages from healthcare systems
Validating message structure and required fields before processing
Generating test messages for ADT, ORM, ORU, and other message types
Converting legacy HL7 v2 data to FHIR R4 for modern interoperability
Comparing two versions of an HL7 message to find differences

FAQ from HL7 Tools — Parser, Validator, FHIR R4 Converter

What HL7 versions does HL7 Tools — Parser, Validator, FHIR R4 Converter support?

It supports HL7 v2.x with full field definition lookup for versions 2.3 through 2.8.

What message types and segments are supported?

Validation covers 20+ message types, and 20 segments (e.g., MSH, PID, PV1, OBX) have complete field definitions.

Does HL7 Tools — Parser, Validator, FHIR R4 Converter provide a REST API?

Yes. In addition to MCP tools, it offers HTTP endpoints for all operations, running on port 3200.

How do I switch between HTTP and stdio modes?

Use npm run dev for HTTP mode and npm start for stdio mode (for MCP clients).

Does HL7 Tools — Parser, Validator, FHIR R4 Converter require any external dependencies?

It requires Node.js and npm for installation, but no other external services or authentication.

「その他」の他のコンテンツ

Unity MCP ✨

justinpbarnett

Unity MCP acts as a bridge between AI assistants and your Unity Editor. Give your LLM tools to manage assets, control scenes, edit scripts, and automate tasks within Unity.

12.2K