Summary
Healthcare ETL is predominantly orchestrated through Airflow, and the v2.5/3.0 KPI targets broad ecosystem integration (§8.5). No task provides an Airflow operator. A thin OpenMedDeidentifyOperator wrapping the existing dataset-redaction runner (OM-055) lets data engineers drop OpenMed redaction into a DAG as a first-class task, with provider packaging kept optional.
Scope
Acceptance criteria
Out of scope
- Publishing an apache-airflow-providers-openmed package.
- Structured k-anonymity transforms (OM-044).
- Streaming/sensor operators.
Files
- openmed/interop/airflow_operator.py
- pyproject.toml
- tests/unit/interop/test_airflow_operator.py
Task: OM-154 · Milestone: Backlog · Priority: P3 · Size: S
Depends on: — · Blocks: —
Roadmap: §8.5 Ecosystem KPI (data-ecosystem integrations); OM-055 runner
Spec: PLANS/V2/EXECUTION/tasks/OM-154.md
Summary
Healthcare ETL is predominantly orchestrated through Airflow, and the v2.5/3.0 KPI targets broad ecosystem integration (§8.5). No task provides an Airflow operator. A thin OpenMedDeidentifyOperator wrapping the existing dataset-redaction runner (OM-055) lets data engineers drop OpenMed redaction into a DAG as a first-class task, with provider packaging kept optional.
Scope
Acceptance criteria
Out of scope
Files
Task: OM-154 · Milestone: Backlog · Priority: P3 · Size: S
Depends on: — · Blocks: —
Roadmap: §8.5 Ecosystem KPI (data-ecosystem integrations); OM-055 runner
Spec: PLANS/V2/EXECUTION/tasks/OM-154.md