Project Principal Federated Data Platform Architect Stealth Deployment

## About the Role As part of the Stealth Federated Research Platform, the selected Architect will design and compare two parallel architectural scenarios for federated healthcare data infrastructure. The objective is not only implementation, but a clear technical decision framework supporting long-term scalability, governance, and interoperability across multiple regions. ## Responsibilities ### Scenario 1 — Enterprise Healthcare Stack (InterSystems IRIS / Caché-based) This scenario builds on an enterprise-grade interoperability platform commonly used in healthcare environments. - IRIS for Health–based integration layer - Secure ingestion pipelines from hospital systems - Cloud-hosted deployment (Azure / GCP) - High-performance data processing using IRIS data engine - Integration with existing ETL and transformation tooling - Conversion into a Common Data Model (OMOP) ### Architecture Components - IRIS for Health instance (cloud or hybrid deployment) - Integrated message handling (FHIR/HL7 where applicable) - Controlled anonymization workflows - Research workspace environment - Federated query execution layer ### Expected Design Considerations - Data security boundaries between hospital and research environments - Performance of large-scale cohort queries - Governance and auditability - Vendor lock-in considerations vs operational efficiency ### Scenario 2 — Open Architecture Stack (PostgreSQL / Open Source Ecosystem) The alternative architecture explores a more open, modular infrastructure based on widely adopted open-source technologies. - PostgreSQL as primary analytical datastore - Modular data pipeline architecture - Cloud-native and hybrid-ready deployment - Fully containerized services ### Potential Components (Architect to Propose Final Stack) - PostgreSQL (primary storage layer) - Redis (or equivalent) for caching and orchestration - Workflow orchestration layer (e.g., Airflow or similar) - API-based federated query execution - Containerized ETL pipelines - OMOP CDM transformation tooling ### Expected Design Considerations - Federated analytics without centralizing identifiable data - Scalability across multiple hospital nodes - Infrastructure automation and reproducibility - Long-term extensibility and cost optimization ### Key Responsibility — Comparative Architecture Strategy The Architect will: - Design both IRIS-based and Open-Source-based federated architectures - Define advantages, trade-offs, and risks of each approach - Propose deployment models for: - Cloud-first environments - Hybrid / on-premise secure nodes - Define how both stacks support: - Stage 1 — Push Data Model - Stage 2 — Federated Pull Model The final deliverable should include a technology decision framework, not only diagrams. ### Deliverables Specific to Dual-Scenario Design - IRIS-based reference architecture - Open-source PostgreSQL-based reference architecture - Comparative analysis document: - Security model - Operational complexity - Scalability - Cost considerations - Governance model - Federated analytics workflow design for both stacks ## What we offer Apply Now