tool4.dev

Data / LOCAL TOOL

HL7 v2 Capture Inspector

Inspect, filter, and correlate HL7 v2 messages and acknowledgments locally in your browser.

Runs locally — input is never uploaded
Drop or paste an HL7 v2 capture · max 100 MiB
Match
Sending application
Message type
Acknowledgment
MessagesReady when you are

WHAT IT DOES

Follow an HL7 conversation without sending patient data anywhere.

Drop a raw HL7 v2 capture to separate its messages, inspect routing and message metadata, filter a large exchange, and open any row down to its non-empty fields. Acknowledgments are correlated by the original message control ID in MSA-2, with reversed sender and receiver endpoints used to disambiguate repeated IDs. Sender and receiver remain explicit and searchable without guessing which endpoint is local.

Why use it?

Use it to locate messages and their acknowledgments in a capture when a single long text file makes routing and missing replies difficult to follow.

How to use this tool

  1. Load or paste the raw HL7 v2 capture and inspect its message inventory.
  2. Filter by type, control ID, sender, receiver, or acknowledgment state, then open a message to review its fields.
  3. Check MSH-10 on the original against MSA-2 on its acknowledgment. Correlation is a diagnostic aid, not proof that a clinical workflow completed.
  4. Use synthetic or appropriately authorized data. The tool reads captured text; it does not contact an interface engine or validate a clinical implementation profile.

Details and limitations

  • Message boundaries are read from MSH segments and common MLLP framing bytes; text before the first MSH is ignored and reported rather than treated as clinical content.
  • Filters cover message type, acknowledgment state, control ID, sender, receiver, and free-text message content without creating one page element for every message in an unbounded capture.
  • Each message row opens into named segments and separately copyable non-empty fields, repetitions, components, and subcomponents. Their standard positions and practical names remain available on hover.
  • ACK messages are linked through MSA-2 to the original MSH-10 control ID. AA and CA are shown as accepted outcomes, while AE, AR, CE, and CR remain visible as errors or rejections.
  • The parser reports the encoding characters declared by MSH and uses the message's own field separator instead of assuming a pipe for every capture.

COMMON QUESTIONS

HL7 v2 Inspector questions

Does the inspector upload HL7 messages or patient data?
No. Pasted and dropped captures are read by browser-side code only. The server receives neither the source messages nor the filters you apply to them.
How are ACK messages connected to their originals?
The inspector matches MSA-2 in the acknowledgment to MSH-10 in an earlier non-ACK message. Reversed sending and receiving endpoints are preferred when the same control ID occurs more than once.
Can I filter by sender or receiver?
Yes. Both search fields inspect the complete raw message, including MSH sending and receiving applications and facilities. Combine two endpoint terms with AND or OR when narrowing a capture.
Which HL7 versions can it read?
The inspector reads the common delimited structure used across HL7 v2 releases and reports the version declared in MSH-12. Field labels are a practical reference for common segments, not full conformance validation against a version-specific implementation guide.