Senior Interoperability & Integration Analyst

• Global Impact: Drive state-of-the-art digital health platforms affecting millions of patients worldwide.
• Culture of Innovation: Work with cutting-edge open standards (FHIR R4/R5, DICOMweb, SNOMED CT) in a collaborative, agile ecosystem.
• Flexibility & Balance: Hybrid work environment, flexible hours, and continuous professional development programs.

B. Braun Medical, S.A. U. | Aitana Altuna

• HL7 FHIR (Expert): FHIR R4/R5, StructureDefinition, ValueSets, SearchParameters, Implementation Guides.
• HL7 v2.x (Advanced): ADT, ORM, ORU, DFT, MDM messaging structures & workflow semantics.
• DICOM & DICOMweb (Advanced): WADO-RS, STOW-RS, QIDO-RS, DICOM IODs, DICOM SR.
• Hospital Systems: In-depth functional knowledge of HIS, EMR/EHR, RIS, PACS, VNA, LIS.
• Clinical Workflows: Admissions, order entry, diagnostic reporting, medication management, clinical documentation.
• IHE Integration Profiles: Practical knowledge of IHE PAM, PIX/PDQ, XDS, SWF, XDW.
• Standard Vocabularies: Hands-on experience with SNOMED CT, LOINC, ICD-10/11, RxNorm, UCUM.
• Semantic Mapping: ConceptMap authoring and local code set harmonization.
• Data Modeling: Conceptual & logical data modeling, JSON/XML schemas, OpenAPI specifications.
• Governance & Security: EMPI/MPI strategies, data quality, HIPAA/GDPR health data privacy rules.
• Professional Experience: Minimum 5+ years of experience in healthcare data architecture, clinical informatics, or healthcare IT interoperability within hospitals, HealthTech vendors, or healthcare consulting.
• Educational Background: Bachelor's or Master's degree in Biomedical Engineering, Health Informatics, Computer Science, or equivalent field.
• Language Proficiency: Fluent in English (C1/B2+ level) required for international standards committees and global platform collaboration.
• Communication Skills: Strong capability to articulate complex clinical workflows into structured data specifications understandable by engineering teams.

Key Distinction from Software Engineering Role:
This position focuses on clinical data architecture, domain modeling, semantic governance, and healthcare process interoperability. It does NOT require hands-on software coding or backend microservice implementation. The Architect defines the 'what' and 'how' of clinical data standards so software engineering teams can build high-performance, compliant platform services.

The person shall have a fundamental understanding of required technologies to work with FHIR and in integration scenarios.

At B. Braun, we protect and improve the health of people around the world. As a global leader in medical technology, pharmaceutical products, and healthcare services, we actively drive digital transformation in acute and outpatient care ('Sharing Expertise'). Our Global Digital Department builds the Digital Foundation Platform-a vendor-neutral, highly scalable healthcare ecosystem designed to seamlessly connect medical devices, hospital information systems, and clinical workflows.

We are seeking an experienced Healthcare Data & Interoperability Solutions Data Architect to lead the functional definition, domain modeling, and semantic governance of clinical data across our Digital Foundation Platform. This role focuses on two core foundation platform components: the Patient Data Service and the Media Service.

Unlike a traditional software engineering role, this position does not require hands-on microservice backend programming. Instead, it demands deep domain expertise in healthcare operational workflows within hospitals and healthcare centers, combined with expert-level mastery of international healthcare data standards (HL7 FHIR, HL7 v2, DICOM/DICOMweb, and clinical terminologies). The Data Architect serves as the vital bridge between clinical end-users, hospital IT stakeholders, and software engineering teams, ensuring that platform data models are semantically consistent, standards-compliant, and optimized for real-world care delivery.

A. Patient Data Service - Clinical Data Modeling & FHIR Governance

• FHIR Profile Definition & Governance: Design, author, and govern HL7 FHIR profiles (StructureDefinitions), extensions, ValueSets, ConceptMaps, and Implementation Guides tailored to platform requirements.
• Clinical Domain Mapping: Model and map complex clinical data entities (patient demographics, encounters, observations, conditions, procedures, allergies, care plans) from hospital source systems (HIS/EMR) to standardized platform resources.
• Clinical Terminology Integration: Establish semantic normalization and coding strategies utilizing international clinical vocabularies (SNOMED CT, LOINC, ICD-10/11, RxNorm, UCUM).

B. Media Service - Medical Imaging & Multimedia Data Strategy

• Metadata Strategy for Imaging & Media: Define metadata schemas and data models for medical imaging (DICOM, DICOMweb) and non-DICOM biomedical content (surgical videos, clinical photos, PDF/A documents).
• Radiology & Workflow Alignment: Integrate image acquisition and archiving workflows (PACS, VNA, RIS) with platform services using DICOMweb (WADO-RS, STOW-RS, QIDO-RS) and relevant IHE profiles (e.g., RAD-68, XDS-I.b).
• Image-to-EMR Linking: Establish semantic references between imaging studies/reports and patient EMR records using FHIR resources (ImagingStudy, DiagnosticReport, Media, DocumentReference).
• Clinical Process Translation: Analyze real-world clinical and operational workflows in hospital departments (admissions, scheduling, orders, lab, operating room, emergency) and translate them into formal interoperability specifications.
• Legacy System Mapping: Specify transformation rules and semantic mappings between legacy formats (HL7 v2 ADT/ORM/ORU, CDA) and native FHIR/DICOM models.
• IHE Framework Architecture: Define integration architectures based on IHE (Integrating the Healthcare Enterprise) profiles (e.g., IHE PAM, PIX/PDQ, XDS.b/XCA, SWF).
• Data Quality & Master Patient Index: Establish data validation rules, Master Patient Index (MPI/EMRI) strategies, deduplication mechanisms, and data integrity policies.
• Implementation Validation: Audit and validate that software engineering implementations strictly adhere to specified data models and standards.
• Cross-Functional Collaboration: Act as the primary technical liaison between hospital clinical IT experts, Product Owners, and backend software engineering teams.