hl7v2-to-fhir-pipeline

To map HL7v2 messages to FHIR format, use a pipeline orchestration approach that manages example collection, requirements generation, design, and iterative implementation for ADT/ORU/BAR workflows while enforcing de-identification and commit discipline.

De-identifying HL7v2 examples before FHIR conversion is enforced automatically by the orchestration pipeline. It requires strict de-identification of example messages during collection and supports automated example generation to maintain data safety throughout the mapping process.

The best way to manage HL7v2 to FHIR converter development tickets is using a ticket-driven workflow that creates directories for examples, runs spec exploration, and enforces a stepwise pipeline with sub-agent handoffs and commit-every-step discipline.

Yes, you can use sub-agents for HL7v2 to FHIR mapping requirements and design. The orchestration layer spawns sub-agents for requirements, exploration, design, planning, implementation, and review, utilizing NEED_USER_INPUT semantics and strict resume behavior.

Yes, the HL7v2 to FHIR pipeline supports automated example generation when needed. It enforces de-identification of collected example messages and mandates strict resume behavior for sub-agents during the iterative implementation process.

Limitations of orchestrating HL7v2 to FHIR message converters include strict dependency on sub-agent resume behavior and NEED_USER_INPUT semantics, requiring commit-every-step discipline and manual placement of example messages into specific ticket directories to function correctly.