Healthcare Data Tools

Browser-based tools for DICOM and HL7 medical data standards — no data leaves your browser.

Six single-page utilities for working with HL7 v2.x and DICOM — parsing messages, inspecting and editing imaging metadata, generating test data, and simulating modality worklists. No installs, no accounts, and nothing ever leaves your machine.

Tools

  • 🩻

    DICOM Viewer & Tag Morph

    Medical Imaging

    View DICOM images across all major storage SOP classes — CT, MR, US, XA, NM, PET, mammo, RT and more — with window/level, cine, and measurements. Morph tags inline or in batch and re-export valid DICOM.

    Launch →
  • 🏥

    DICOM Toolbox

    Medical Imaging

    Create, configure, and generate valid DICOM files from scratch, then read them back with the built-in tag browser. Ideal for testing implementations and building synthetic datasets.

    Launch →
  • 📋

    HL7 v2.x Parser

    Clinical Messaging

    Parse HL7 v2.x messages into a structured breakdown of segments, fields, components, and subcomponents — with highlighted and JSON views, plus FHIR resource support.

    Launch →
  • 🔄

    HL7 Diff Checker

    Data Validation

    Compare two HL7 messages side by side, down to the field level. Quickly spot what changed between an inbound message and its transformed counterpart.

    Launch →
  • 📡

    MWL Simulator

    Modality Worklist

    Simulate or query a DICOM Modality Worklist (C-FIND SCU) with a built-in dataset, or point it at a live DICOMweb endpoint. Includes a dcmdump-style view of the request and response.

    Launch →
  • 🔗

    DICOM → HL7 Order

    Workflow Integration

    Read tags from a DICOM file and generate an HL7 ORM^O01 radiology order, with a mapping table showing exactly which attribute produced each field.

    Launch →

About

Built for healthcare IT professionals, integration engineers, and students working with medical data standards — whether you're debugging an interface, testing a PACS implementation, or just learning how these formats fit together.

Every tool is a single self-contained HTML page with no build step and no dependencies. Parsing, rendering, and file generation all happen locally in JavaScript, which makes them safe to point at data that may contain PHI.

🔒 Client-side only — no data leaves your browser