fi-fhir
fi-fhir turns HL7v2, CSV, EDI X12, and CDA/CCDA feeds into semantic events that workflows validate, transform, and route, with FHIR R4 as one output. These three tools run its HL7v2 path for real: the production profile compiler, parser, and FHIR projection, compiled from Go to WebAssembly and running in your tab. The samples are synthetic, and nothing you paste leaves the page.
Kernel v0.1.0, 8.3 MB, loaded once and shared by the three tools. Source on GitHub
Each tool runs the same kernel call and shows a different side of the answer. The line under each description says what it runs.
Configure
Edit an example Source Profile in YAML, compile it with fi-fhir’s own profile compiler, and run a sample message through it to see what changes.
Status: fi-fhir’s profile compiler in WebAssembly, example profiles, no backend
Parse
Paste an HL7v2 message or pick a sample and see what the real parser returns: its segments, the semantic event, and every diagnostic with its path.
Status: fi-fhir’s HL7v2 parser in WebAssembly, synthetic samples, no backend
Map
Follow the same event into FHIR R4: the conditional transaction Bundle a fi-fhir destination would send, entry by entry, with copy and download.
Status: fi-fhir’s FHIR projection in WebAssembly, synthetic samples, no backend
55 synced docs pages in 6 sections, copied from the fi-fhir repo when this site was built.
What runs in your tab, which samples it ships with, and why nothing leaves the page.
A walk through these three tools and what each one shows.
Install, parse a first message, and follow the core flow.
How profiles drive parsing, normalization, and validation.
Parsing, linting, validation, and workflow commands.
What runs in production: ingress, durable acceptance, workflow routing, FHIR delivery.