Built for critical infrastructure. Handles encoding nightmares, line ending chaos, and ACK processing that actually works. 100% offline. GDPR & HIPAA compliant. Zero compromises.
We analyzed hundreds of forum posts from frustrated integration engineers. Here's what breaks every other converter—and how we fixed it.
Most HL7 converters fail on edge cases. We handle the encoding nightmares, malformed messages, and vendor-specific quirks that break other tools.
Automatically detects and converts from Windows-1250, Windows-1252, ISO-8859-1, ISO-8859-2, Windows-1251, and UTF-8. No more replacement characters (�) in Polish, Czech, or Cyrillic patient names.
HL7 v2 standard specifies CR (\r) as segment separator. But real-world files come with CRLF (Windows), LF (Unix), or mixed. We automatically normalize everything to CR before parsing.
Most tools ignore ACK messages or dump them as JSON. We parse MSA and ERR segments, map acknowledgment codes (AA, AE, AR, CA, CE, CR) to FHIR OperationOutcome severity levels, and extract detailed error information.
Real HL7 files have stray spaces, missing MSH-2 encoding characters, and inconsistent formatting. Our validator auto-fixes common issues before parsing, reducing validation errors by 80%.
In healthcare IT, "cloud-based" is often a liability. Here's why offline processing isn't just convenient—it's mandatory for secure, compliant environments worldwide.
PHI never leaves your network. No uploads, no APIs, no third-party servers. Ideal for BAAs and audits.
Runs in air-gapped facilities. Single self-contained executable with zero external dependencies.
Built on NHapi and official FHIR.NET libraries. Transparent parsing, no black boxes.
Your HL7 data is your IP. Nothing is logged, transmitted, or observed—ever. Supports NIS2 cybersecurity requirements for EU healthcare essential entities.
Choose the interface that fits your workflow. Same conversion engine, same validation logic, different entry points.
Scriptable command-line interface for batch processing and automation. Integrates into build pipelines, cron jobs, or PowerShell scripts.
Beautiful WinUI 3 desktop app with embedded React interface and Monaco Editor. Perfect for testing, debugging, and one-off conversions.
Local REST API with OpenAPI/Swagger documentation. Embed into your applications or build custom workflows. No external network calls.
Watch how the converter handles encoding detection, malformed messages, and ACK processing in real-world scenarios.
Powered by NHapi and FHIR.NET—the same libraries used by Epic, Cerner, and Allscripts integrations.
Practical answers for healthcare engineers running the HL7 Converter in real environments.
The converter supports three execution modes, all powered by the same conversion engine:
The mode is selected automatically based on how the application is launched.
Simply launch the application normally (double-click or run without arguments).
The UI allows you to select HL7 files and convert them interactively. All conversions use the same engine as CLI and API modes.
In CLI mode, the first argument determines what is converted. You can pass either:
Examples:
hl7converter.exe "C:\HL7\msg.hl7"
hl7converter.exe "C:\HL7Messages"
When a directory is provided, all files in that directory are processed sequentially.
The output directory is determined as follows:
hl7converter.exe "C:\HL7\msg.hl7" "D:\FHIR\Output"
Output files are named using the original input filename plus a high-resolution timestamp to prevent overwriting.
Format:
<original_filename>_yyyyMMdd_HHmmss_fff.json
Example:
ADT_A01_20251214_132206_143.json
This guarantees unique filenames even when converting many files rapidly.
Start the application with the api flag:
hl7converter.exe api
This launches a local REST API and exposes Swagger UI at:
http://localhost:5000/swagger
To use a custom URL:
hl7converter.exe api --urls http://127.0.0.1:8080
Swagger will then be available at:
http://localhost:8080/swagger
No. The converter is 100% offline.
No cloud calls, no telemetry, and no external dependencies. All HL7 data remains on your machine.
HL7 v2.3, v2.4, v2.5, and v2.5.1 are supported.
Older versions are automatically normalized to v2.5 to prevent compatibility failures.
Yes. HL7 ACK messages are fully parsed.
MSA and ERR segments are mapped to structured FHIR OperationOutcome resources with correct severity levels.
Z-segments are non-standard, locally defined HL7 extensions.
Because their meaning varies by organization, the converter does not guess. Instead:
HL7 v2 is a decades-old, highly flexible standard with massive real-world variation. Optional fields, malformed delimiters, and vendor-specific quirks are common.
Most converters assume perfect HL7. This tool is built for what actually exists in production.
The converter automatically fixes common issues where safe, and emits explicit warnings when interpretation is uncertain.
It never crashes mid-conversion and never silently drops data.
Many HL7 feeds fail to escape reserved characters correctly, causing naive parsers to break.
This converter correctly processes HL7 escape sequences and safely serializes output using official FHIR JSON libraries.
Yes. The converter produces clean FHIR R4 transaction bundles suitable for ingestion, testing, and validation.
Healthcare integration engineers, platform teams, and vendors who need reliable HL7 processing without heavy infrastructure.
Yes. The converter is designed to support EU regulatory compliance:
GDPR: Because all processing happens locally with zero data transmission, there are no GDPR data processing obligations. PHI never leaves your infrastructure, ensuring full compliance with data minimization and data residency requirements.
NIS2 Directive: Hospitals and healthcare providers are classified as "essential entities" under NIS2. The offline-first architecture eliminates external network dependencies, supporting your cybersecurity risk management obligations.
Medical Device Regulation (MDR): This tool is a data conversion utility for IT infrastructure, not a medical device. It does not provide clinical decision support, diagnostics, or treatment recommendations, and therefore falls outside MDR scope.
Yes. The converter automatically detects and handles Windows-1250 (Polish, Czech, Slovak, Hungarian), Windows-1251 (Cyrillic), ISO-8859-1, ISO-8859-2, and UTF-8 encodings.
Patient names with diacritics (ą, ć, ę, ł, ń, ó, ś, ź, ż, č, ř, ů, etc.) are correctly converted without replacement characters (�).
Absolutely. The converter is a single self-contained executable with zero external dependencies.
It runs entirely offline in isolated networks, secure facilities, and environments with strict network segmentation requirements common in EU healthcare infrastructure.
Join healthcare integration engineers who've eliminated encoding headaches, cloud dependencies, and vendor lock-in.
Download from Windows Store