A real parser — delimiters read from MSH-1 and MSH-2 rather than assumed, MSH indices reconstructed, repetitions and subcomponents decomposed properly. It shows the mapping decision for every field, the FHIR Bundle it produces, and the places it deliberately refuses to guess.
Paste a message or load a sample. Everything is parsed and mapped in your browser — no upload, no storage, no network call.
Load a sample and hit parse. Free gives you the full parser, the FHIR Bundle, the mapping table and every finding — the whole tool, not a teaser.
The segments you actually meet, what each field carries, and where it lands in FHIR. Click a segment to expand.
| Type | Name | What it means | Usual segments |
|---|
The parser and mappings are free. What costs money is knowing which of these decisions will page you at 3am — the failure modes you only learn by shipping interfaces in hospitals.
An interface moving GxP or patient data is a computerised system, and needs the same qualification evidence as any other. This is the part generic integration guidance omits — and the part an auditor asks about first.
Messages that naive parsers handle wrongly, each paired with the behaviour a correct implementation must show. Three are loaded in the explorer free — try them. The full pack with expected behaviours is a regression suite you can run against your own engine or a vendor's.
Most v2-to-FHIR programmes fail the same way, and it is rarely technical. The playbook covers the sequencing, the measurement that decides your timeline, and the risk that derails each phase.
No. There is no backend. Parsing, mapping and export all happen in your browser — you can disconnect from the network and it still works. That said, paste de-identified or synthetic messages: good habits around PHI shouldn't depend on trusting a web page.
No, and please don't. It doesn't validate against FHIR profiles, doesn't do terminology translation against a real code-system server, doesn't persist or transmit anything, and has no error handling or retry semantics. It's a tool for understanding mappings and writing specifications, which is a different job.
One defensible reading of the standard, chosen to be explicit about ambiguity rather than confident about guesses. Where a value has no clean FHIR equivalent, the tool says so instead of inventing one. Your trading partner's conformance profile always overrides a general-purpose default.
The parser is version-agnostic because it reads delimiters and structure from the message itself. The field reference targets the 2.3.1 through 2.5.1 range, which is what the overwhelming majority of production interfaces still run.
Enter it here — it unlocks the field guide and inline notes on this device.
Enter your license code (from your receipt). It unlocks the production failure-mode guide, per-field integration notes inline in the explorer, the mapping-spec export and the AI review prompt.
No code yet? See pricing →