HL7 Developer Toolkit

Features

Tools for reading and debugging HL7 v2

Preview means a basic version works in the current build. Planned means it is not built yet.

Message inspection Preview

Turn a wall of pipes into something you can read. The Inspector splits an HL7 v2 message into segments, fields, components and subcomponents using the delimiters declared in the MSH segment.

Try HL7 Inspector

Available in this build

  • Segment list with a field table for each segment
  • Component and subcomponent breakdown
  • Repeating fields shown as separate repetitions
  • Summary of message type, control ID and version from MSH

Planned

  • Escape sequence decoding
  • Version-specific field names
  • Multi-message files
  • Highlighting of unusual structure

Field navigation Preview

Read values by their HL7 address, such as PID-5.1 or OBX-5, instead of counting delimiters. Move between segments and see where each value sits.

Try HL7 Inspector

Available in this build

  • Field addresses such as PID-3 and PID-5.1
  • Repeated segments numbered in order, such as OBX 1 and OBX 2

Planned

  • Search by field address or value
  • Copy a field path
  • Field names and descriptions by HL7 version

Message comparison Planned

Compare two messages to see which fields differ, for example the message a source system sent and the message after a channel transformed it.

Available in this build

  • Not available yet

Planned

  • Field-level comparison of two messages
  • Ignore rules for values that always differ, such as timestamps and control IDs

Mirth Connect helper tools Planned

Helpers for developers who build and debug Mirth Connect channels. The documentation already explains how HL7 addresses relate to transformer references.

Available in this build

  • Reference notes in the documentation

Planned

  • Field-path references for transformers
  • Snippet generators for common mappings
  • Sample message builders for channel testing

How the tools are designed

Browser-first

In this phase, message parsing happens in your browser. Pasted text is not sent to the server.

Honest about scope

The tools do not claim certification, standards validation or regulatory compliance.

Built for troubleshooting

Each tool is designed around a question developers ask when an interface misbehaves.

What this is not. It is not a certified validator, an interface engine, or a tool for clinical decisions. It is a developer aid for reading and troubleshooting messages.

See the preview for yourself

Open the Inspector with a synthetic message, or read the HL7 v2 basics in the documentation.

Try HL7 Inspector Documentation