FHIR to OMOP FHIR IG, published by HL7 International / Biomedical Research and Regulation. This guide is not an authorized publication; it is the continuous build for version 2.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-omop-ig/ and changes regularly. See the Directory of published versions

• Narrative Content
• XML
• JSON
• TTL

ActorDefinition: Transformation Engine

Official URL: http://hl7.org/fhir/uv/omop/ActorDefinition/xfm				Version: 2.0.0-ballot	Highlight text changes?
Standards status: Trial-use				Maturity Level: 2	Computable Name: Transformation_Engine
Other Identifiers: OID:2.16.840.1.113883.4.642.40.77.12.5

The software component that reads FHIR resources from a Source System and produces records in an OMOP CDM v5.4 database. This is the actor that executes the ETL logic, whether through published FHIR StructureMaps, a custom ETL stack in SQL, dbt, Spark, or Python, or a hybrid of these. The Transformation Engine carries the largest number of conformance obligations in this guide, because it is where mapping decisions, code prioritization, type concept assignment, and status and intent filtering are enforced at runtime.

The Transformation Engine is distinguished from the ETL Implementer (A5) in that the Engine is the software and the Implementer is the organization that configures and runs it. A single Transformation Engine product, such as a commercial ETL tool, could be deployed by many Implementers, each producing their own Target OMOP Instances.