PathogenTestForm: Composition + Stable Form Refactor (Part 1) #13852

Situation Description & Motivation

Refactor PathogenTestForm from a bridge-method / PoC section-slot approach into a clean
composition architecture where disease-specific fields are fully encapsulated in
DiseaseSectionLayout implementations.

Use cases

PathogenTestForm

High-Level Explanation

• One stable PathogenTestForm instance — never swapped by the controller
• Disease-specific fields fully encapsulated in DiseaseSectionLayout implementations
• Adding a new disease = one new class + one line in the factory — zero changes to PathogenTestForm or the controller
• No bridge methods — sections receive exactly what they need via FieldGroup + CustomLayout
• TubeFieldHandler eliminates the 4× duplicated tube listener pattern

Timeline

Sprint 1 (Phases 1–4) + Sprint 2 (Phases 5–7)

Tasks

• [Part 1 / Phase 1] PathogenTestForm: Clean up PoC code #13853
• [Part 1 / Phase 2] PathogenTestForm: Refactor DiseaseSectionLayout interface #13854
• [Part 1 / Phase 3] PathogenTestForm: Refactor TuberculosisDiseaseSectionLayout #13855
• [Part 1 / Phase 4] PathogenTestForm: Create remaining DiseaseSectionLayout classes #13856
• [Part 1 / Phase 5] PathogenTestForm: Remove bridge methods and update section lifecycle #13857
• [Part 1 / Phase 6] PathogenTestForm: Create TubeFieldHandler #13858
• [Part 1 / Phase 7] PathogenTestForm: Verification #13859

Alternatives

Risks

Additional Information