Add your HL7 file
Drop one or more .hl7 files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
HL7 to JSON
Converting a .hl7 font to .json repackages the same glyphs and metrics for a different delivery target. Free, private, and validated — the file never leaves your browser.
Private for supported formats — processed in your browser
Runs on your deviceConvert supported files
Drop HL7 files here
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.About converting HL7 version 2 message to JSON data
Converting a .hl7 font to .json repackages the same glyphs and metrics for a different delivery target. An .hl7 file holds one or more HL7 version 2 messages: pipe-delimited healthcare interchange records made of segments — MSH for the header, PID for the patient, PV1 for the visit — each split into fields, components and subcomponents by a delimiter hierarchy declared in the message itself.
A .json file holds JavaScript Object Notation: nested objects, arrays, strings, numbers, booleans, and null written in a strict text syntax. It is the default data language of the web — most APIs speak nothing else. For this route the practical draw is parsers ship in the standard library of essentially every language and readable by humans and machines alike — balanced against no comments — a perpetual annoyance for configuration files, which is worth knowing before you commit a large batch.
Why convert HL7 to JSON?
The practical trigger for this conversion is usually a mismatch: with .hl7, extremely terse; a message is unreadable without a segment reference to hand. Switching to .json buys you parsers ship in the standard library of essentially every language, which is why it is the better fit for rEST and HTTP API request and response payloads. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
HL7 vs JSON at a glance
| Aspect | HL7 version 2 message (.hl7) | JSON data (.json) |
|---|---|---|
| Format type | Text-based — characters and structure, so there is no visual quality loss | Text-based — characters and structure, so there is no visual quality loss |
| How it stores data | segments are separated by CARRIAGE RETURNS, not newlines. This is the standard, not a Windows artefact, and readers that split on \n mis-parse real messages | exactly six value types; no dates, no comments, no trailing commas — the strictness is deliberate |
| Strongest at | inspecting hospital interface traffic during integration work | rEST and HTTP API request and response payloads |
| Weak spot | extremely terse; a message is unreadable without a segment reference to hand | no comments — a perpetual annoyance for configuration files |
Pick JSON as the output
Select .json in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if JSON is selectable, the route is real and validated.
Convert on your device
Press Convert. The font tables are parsed and rewritten locally with fonteditor-core; glyph outlines, hinting, and kerning survive the trip.
Verify and download
Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid JSON file. Outputs keep the original filename with the .json extension.
HL7 to JSON questions, answered
Will converting HL7 to JSON lose quality?
There is no visual quality to lose — hl7 is text-oriented and json is text-oriented, so the question is structural fidelity. Text, ordering, and basic structure are preserved; complex layout, embedded objects, and styling beyond the target's model are simplified.
Is it private to convert HL7 files here?
Yes — the .hl7 file is processed inside your browser tab and never uploaded. The font tables are parsed and rewritten locally with fonteditor-core; glyph outlines, hinting, and kerning survive the trip. Close the tab and the file is gone from memory.
Where will the JSON file work?
Browsers parse it natively through JSON.parse, every mainstream language bundles support, and most editors validate and highlight it out of the box. Viewing a raw .json file is possible in any text editor or browser tab.
Will the JSON file be bigger or smaller than my HL7?
It depends on the content: exactly six value types; no dates, no comments, no trailing commas — the strictness is deliberate. Convert one representative file first and compare before batch-processing a large set.
What happens to the metadata in my HL7 file?
In .hl7, the MSH header — sending and receiving applications, timestamp, message type, control ID — is preserved in the JSON output. Re-encoding through the browser pipeline does not carry embedded metadata into the output, which doubles as a privacy scrub — check the exported file if you specifically need tags preserved.