FHIR Mapping
FHIR R4 resource coverage and the boundary between core mapping and customer customization.
FireSonic converts supported HL7 v2 messages into FHIR R4 resources and assembles them into transaction Bundles suitable for downstream FHIR systems.
Generated resources
| FHIR Resource | Typical HL7 Source |
|---|---|
| Patient | PID / PD1 |
| Encounter | PV1 / PV2 |
| Practitioner | ROL / XCN provider fields |
| Organization | MSH / PV1 |
| RelatedPerson | NK1 |
| Coverage | IN1 / IN2 |
| AllergyIntolerance | AL1 / IAM |
| Condition | DG1 |
| Procedure | PR1 |
| Observation | OBX |
| DiagnosticReport | OBR |
| ServiceRequest | ORM / ORC / OBR |
| Specimen | SPM |
| Appointment | SCH / AIS / AIP / AIL / AIG |
| Immunization | RXA / RXR |
| MedicationRequest | RXO / ORC |
| MedicationAdministration | RXA |
| ChargeItem | FT1 |
| DocumentReference | ORU attachments/documents |
| MessageHeader | MSH |
Transaction Bundle behavior
Bundle construction preserves relationships between generated resources and supports conditional create/update and idempotent delivery patterns where appropriate.
Customization boundary
Core mapping is deterministic Java-based interoperability logic. Site-specific normalization, enrichment, terminology reconciliation, or workflow-specific patching should be implemented with the SDK rather than modifying the mapper.