Director, Integrations and Automation

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes description (About the role) – we can put that in

About the role

with paragraphs. Responsibilities: list of duties – we have many bullet-like sentences. We'll create

• for each duty. Requirements: maybe "Minimum Job Qualifications" includes education and experience. Could be Requirements. Qualifications: maybe "Knowledge, Skills And Abilities" and "Minimum Job Qualifications". But we need to avoid duplication. We can treat "Knowledge, Skills And Abilities" as Skills section. "Minimum Job Qualifications" as Requirements/Qualifications. The instruction: Use headings for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content accordingly. We have Pay: salary range $193,000 - $208,600. So we include Pay section. Schedule: not mentioned, so omit. Benefits: not mentioned explicitly; there is mention of inclusive environment but not benefits. So omit Benefits. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay. We need to ensure we don't repeat job title as heading. We need to preserve all substantive information; not invent. We need to remove boilerplate like EEO, equal opportunity, etc. Also remove "Supervisory Responsibilities", "Patient Contact", "License/Certification/Registration Required None required". Also remove "At Dana-Farber Cancer Institute, we work every day..." maybe that's part of About the role? It's about mission; could be included in About the role. But we need to preserve all substantive information; we can include that as part of About the role paragraph. We need to avoid duplication: there are repeated sentences like "Supervises staff. Hires, develops, and manages staff..." appears twice? Actually appears in Responsibilities and later again. We'll deduplicate. We'll craft HTML. Let's extract About the role: first paragraph(s) before "Primary Duties And Responsibilities". That includes: "The Director of Integrations and Automation provides strategic technical leadership for Dana-Farber Cancer Institute and is responsible for architecting, building, and maintaining the organization’s enterprise interoperability ecosystem. This role is responsible for defining and executing the organization’s integration strategy to enable seamless, secure, and scalable data exchanges across clinical, research, operational, and business platforms. The Director drives the design, implementation, execution, and ongoing optimization of enterprise integration capabilities spanning interface engines, API management, modern automation workflows, AI solutions, event-driven architectures, and data movement platforms that connect critical systems. The Director translates organizational strategy, regulatory requirements, and clinical priorities into an enterprise interoperability roadmap that aligns strategic vision with technical execution to deliver reliable interoperability solutions that support patient care, research innovation, operational excellence, and long-term institutional growth. Located in Boston and the surrounding communities, Dana-Farber Cancer Institute is a leader in life changing breakthroughs in cancer research and patient care. We are united in our mission of conquering cancer, HIV/AIDS, and related diseases. We strive to create an inclusive, diverse, and equitable environment where we provide compassionate and comprehensive care to patients of all backgrounds, and design programs to promote public health particularly among high-risk and underserved populations. We conduct groundbreaking research that advances treatment, we educate tomorrow's physician/researchers, and we work with amazing partners, including other Harvard Medical School-affiliated hospitals." We'll put that in

  . Responsibilities: list items from "Primary Duties And Responsibilities" onward until "Knowledge, Skills And Abilities". We'll extract each bullet-like sentence. Let's list them: - Develop and maintain Dana-Farber Cancer Institute’s enterprise integration and automation strategy, standards, governance framework, and multi-year roadmap. - Establish enterprise standards and best practices for interoperability, API management, automation, data exchange, and integration lifecycle management. - Establish governance frameworks for AI-related data exchange, ensuring alignment with organizational policies, ethical standards, and regulatory requirements. - Partner with executive leadership to identify opportunities for innovation, automation, operational efficiency, and digital transformation. - Develop and manage operating and capital budgets for integration and automation platforms, services, and strategic initiatives. - Manage vendor relationships, software licensing, consulting engagements, statements of work, and technology contracts. - Identify opportunities to eliminate operational friction by designing end-to-end automation strategies, optimizing business processes, and reducing manual technical debt. - Direct and mentor a high-performing team of integration engineers, technical analysts, and project managers. - Foster a culture of technical excellence, continuous learning, and modern engineering practices. - Oversee the design, implementation, support, and optimization of enterprise integrations leveraging HL7, FHIR, SMART on FHIR, C-CDA, X12, RESTful APIs, JSON/XML payloads, APIs, event streaming, ETL/ELT pipelines, file-based integrations, and Epic interoperability technologies, including Bridges, Interconnect, FHIR, Aura, and emerging API frameworks. - Manage a team overseeing diverse data transmissions, including real-time API connections, modern event-driven architectures, and legacy data streams. - Establish robust data security, governance protocols, and monitoring standards for all interfaces and data transmissions, ensuring adherence to healthcare data privacy regulations (HIPAA), HITECH, the 21st Century Cures Act, CMS interoperability requirements, TEFCA, organizational security policies, applicable federal and state regulations, and industry best practices. - Maintain robust monitoring, auditing, disaster recovery, and business continuity capabilities across the integration ecosystem. - Supervises staff. Hires, develops, and manages staff to achieve organizational goals. Sets clear expectations, delivers feedback, and monitors performance for quality, efficiency, and compliance with policies and procedures. - Mentors staff, fosters career growth, and cultivates a positive and productive work environment. Note: "Supervises staff..." appears also later but we can keep one. Now Requirements: from "Minimum Job Qualifications" section. Content: - Bachelor's degree in Computer Science, Management of Information Systems, Healthcare Informatics or a related field required. - Bachelor's degree in Business Administration or a related field preferred. - 8+ years of progressive experience in healthcare information technology, interoperability, integration engineering, automation, or software development required. - 10+ years 3+ years of progressive leadership experience, including management or architectural leadership over enterprise integration teams required. (This seems garbled: "10+ years 3+ years". Likely they meant 10+ years experience, 3+ years leadership. We'll keep as is but maybe we should preserve exactly: "10+ years 3+ years of progressive leadership experience, including management or architectural leadership over enterprise integration teams required." We'll keep. - Direct experience establishing and governing HL7 and FHIR architectures, including SMART on FHIR required. - Experience implementing API-first, event-driven, and hybrid IPaaS architectures required. - Experience leading large-scale clinical, research, and operational integration programs required. - Proven track record of moving an organization from legacy, point-to-point interface strategies to modern, API-first, event-driven architectures or hybrid iPaaS (Integration Platform as a Service) models. - Strong knowledge of solutions such as MuleSoft Anypoint, Boomi, and Microsoft Azure Integration Services preferred. - Experience managing the technical debt of legacy environments while systematically scaling modern interoperability pipelines. - Must possess a deep operational understanding of how data flows across the clinical and financial ecosystem preferred. - Multi-year experience directing or architecting solutions on major enterprise interface engines (e.g., Lyniate/Rhapsody/Corepoint, Mirth Connect, Infor Cloverleaf, or InterSystems Health Connect/IRIS) preferred. - Experience leading large-scale data mapping, translation, and semantic normalization initiatives across disparate ancillary systems (Labs, Radiology, Pharmacy), FHIR (Fast Healthcare Interoperability Resources) & Modern APIs preferred. - License/Certification/Registration Required None required - HL7, FHIR & Epic Bridges preferred. We'll include these as

  • . Now Skills: from "Knowledge, Skills And Abilities". Content: - Hands-on leadership experience managing ecosystems that heavily feature Epic (or similar EHRs), Snowflake (Data Cloud), and Salesforce. - Understanding of AI and generative AI, machine learning, and advanced analytics concepts and the data integration patterns required to operationalize AI solutions. - Strong familiarity with healthcare interoperability standards (HL7 v2/v3, X12, JSON, FHIR, SMART on FHIR, C-CDA, USCDI). - Solid grasp of data warehousing concepts, cloud data architecture (Snowflake preferred), and CRM data flows. - Knowledge of automation technologies, including UiPath, Microsoft Power Automate, and workflow orchestration platforms. - Excellent communication and storytelling skills, with the ability to explain complex technical integration concepts to non-technical executive stakeholders. We'll put these as
    • . Pay: we have salary range: $193,000.00 - $208,600.00. We'll put in

      . Now we need to output only HTML fragment, no /. Use

      for each section heading. We'll order sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay. But we have both Requirements and Qualifications; we need to decide what goes where. The posting has "Minimum Job Qualifications" (education/experience) and "Knowledge, Skills And Abilities". We could treat "Minimum Job Qualifications" as Requirements, and "Knowledge, Skills And Abilities" as Skills. Qualifications maybe we could omit or combine? The instruction says use headings for those sections if they have real specific content. We have both Requirements and Qualifications; we could put Requirements for education/experience, Qualifications for maybe "License/Certification/Registration Required None required" and "HL7, FHIR & Epic Bridges preferred." But that seems thin. Better to treat Requirements as the education/experience, Qualifications as the knowledge/skills? But we already have Skills heading. Hmm. We could map: Requirements = Minimum Job Qualifications (education/experience). Qualifications = Knowledge, Skills And Abilities (but we also have Skills heading). Actually we have both Skills and Qualifications headings available. The posting has "Knowledge, Skills And Abilities". That could go under Skills. Then we could have Qualifications for something else like "License/Certification/Registration Required None required" and "HL7, FHIR & Epic Bridges preferred." but those are not really qualifications; they are preferences. Could combine them into Qualifications as a list. Alternatively, we could omit Qualifications section if no substantive content beyond what's covered elsewhere. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So if we don't have distinct content for Qualifications, we should omit it. Thus we will have sections: About the role, Responsibilities, Requirements, Skills, Pay. We'll put Knowledge, Skills And Abilities under Skills. Now we need to ensure we don't duplicate content. We'll not include the "License/Certification/Registration Required None required" and "HL7, FHIR & Epic Bridges preferred." maybe we could include them under Requirements as additional items? They are under Minimum Job Qualifications section after the list; they are part of qualifications. We'll include them as list items under Requirements. Thus Requirements list will include education, experience, leadership, direct experience, etc., plus the license/cert line and HL7/FHIR/Epic Bridges preferred. Now we need to ensure we preserve all substantive information. Let's verify we didn't miss any important bits. From the posting after "Minimum Job Qualifications" there is also "Supervisory Responsibilities Team of 10+ FTE's Project Specialists/Sr Project Specialists, Software Engineers and Integration/Engineer Consultants Patient Contact None".