The event the parser builds is projected into FHIR R4 the way a fi-fhir fhir destination does it: one conditional transaction Bundle per event, each resource with the request that creates it or matches an existing one. Event types without a FHIR projection say so instead of showing a Bundle.
Loading the fi-fhir kernel (fi-fhir.wasm, 8.3 MB) into a worker in your browser…
0 of 1,048,576 bytes (the kernel's 1 MiB cap)
No result yet: the kernel is loading.
The pipeline opens on the parser's segments for the same message.