Director Data, AI & Enterprise Business Systems

We need to output HTML fragment with sections: About the role? Actually we need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We have: - About Us (company description) maybe not needed as heading? Could be "About the role"? The posting includes "Position Overview" which is about role. We can treat that as About the role. - Responsibilities: "Key Responsibilities" list. - Requirements: includes Minimum 7 years experience etc. Also "Technical Requirements:" list. - Qualifications: "Preferred Qualifications" list. - Skills: maybe not separate; but we could combine technical requirements as Skills? However we have separate sections: Requirements and Qualifications. Could also have Skills if we want but not needed. - Benefits: Not mentioned. No benefits details. So we should NOT include Benefits section. - Pay: Not mentioned. So no Pay. - Schedule: Work Schedule: 9:00 AM–5:00 PM EST, Work Arrangement: Hybrid. Also Work Environment includes hybrid arrangement. So we can include Schedule section with that info. Also we have "Work Environment" details: hybrid, expected onsite presence 2–3 days per week, etc. That could be part of Schedule or separate? Since we only have Schedule heading allowed, we can put schedule details there. We must not repeat job title as heading. The job title is "Director Data, AI & Enterprise Business Systems". Not to be used as heading. We must not include Job ID etc. We must remove boilerplate like cookie/navigation/legal/EEO etc. At end there is some weird script: check(event) ; career-website-detail-template-2 => apply(record.id,meta)" mousedown="lyte-button => check(event)" final-style... That's boilerplate; remove. We need to preserve all substantive information. Let's extract: About Us: description of InterScripts. Could be placed under a heading? Not among allowed headings. Could we put it as a

before sections? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use

for section headings (list). Probably we should only use those headings. The "About Us" could be considered "About the role"? But that's more about company. Maybe we can include a brief intro as a

before sections, not a heading. That's acceptable. Thus output:

InterScripts is a Information Technology business based in Chantilly, VA and established in 2017 providing technology and platform enabled services and solutions. Historically, we have enabled our customers to realize the most value from their technology and resources through our Managed Services, Archival Solution, EHR, ERP, Advisory, Virtual Care, Technology, Application Development, and Cybersecurity services. In addition, InterScripts has substantial experience in providing Technology and Platform Enabled solutions to commercial, public sector, and government entities. We are an ISO 27001, 9001 CMMI 3 and SOC 2 certified organization, signifying our ability to lower the risks for our clients’ application modernization efforts, custom development, support, operations, and MSP projects.

Then

About the role

with Position Overview paragraph. Then

Responsibilities

with

• each responsibility. Then

  Requirements

  with
  • each requirement (minimum years, leadership, hands-on background, etc.) plus maybe technical requirements as separate list? Could embed. Then

    Qualifications

    with Preferred Qualifications list. Then

    Schedule

    with details: Work Schedule: 9:00 AM–5:00 PM EST, Work Arrangement: Hybrid, Expected onsite presence 2–3 days per week, etc. Also mention travel may be required, no regular weekend/holiday work, ability to lift up to 20 pounds occasionally, ability to walk throughout hospital, etc. That's from Work Environment. We must not include filler like "commensurate with experience". Not present. Let's craft. Responsibilities list items (from Key Responsibilities): - Develop and communicate the strategic roadmap, annual goals, and objectives for data, AI, automation, analytics, and enterprise systems. - Build and champion an Analytics & Insights Center of Excellence. - Lead cross-functional prioritization across business, clinical, and IT stakeholders. - Establish and manage enterprise data governance, including data definitions, ownership, stewardship, retention, and data classification. - Govern the intake, review, documentation, monitoring, and retirement of AI and machine learning models used for clinical and operational decisions. - Partner with Information Security on access controls, minimum-necessary requirements, and third-party data sharing. - Direct data engineering, data platforms, data architecture, enterprise data warehousing, and data archiving. - Own data pipeline reliability, load schedules, source-system inventories, data flows, and downstream dependencies. - Lead clinical and business analytics, including reporting, dashboards, self-service analytics, advanced analytics, and data science. - Own the Epic Cogito environment, including Caboodle and Clarity, report certification, and analyst enablement. - Ensure consistent and accurate reporting across Finance, Quality, Operations, and other business functions. - Support regulatory, quality, and value-based care reporting requirements. - Lead application integration and interface operations, including new builds, upgrades, monitoring, and troubleshooting. - Establish integration standards covering HL7, FHIR, and APIs. - Develop and manage the organization's RPA program, including process intake, development, deployment, and production support. - Lead automated testing and regression testing for enterprise applications, including Epic and Workday release cycles. - Own the Workday ERP platform roadmap, release adoption, configuration governance, security model, reporting, Prism content, and data feeds. - Partner with Finance, Human Resources, and Supply Chain on Workday-related business processes. - Provide coaching, mentoring, and strategic direction to managers and individual contributors. - Build cross-training and succession plans to ensure operational continuity across enterprise platforms. - Lead cross-functional projects from initiation through delivery and maintain quality throughout the project lifecycle. - Serve as an escalation point for complex production issues and manage stakeholder expectations. - Oversee change management and release governance across the portfolio. - Manage budgets, vendors, contracts, licensing, renewals, and technology investments across data, analytics, AI, RPA, and Workday. Requirements list: - Minimum 7 years of experience in data, analytics, enterprise applications, IT, or healthcare. - Minimum 5 years of leadership experience managing cross-functional teams, including managers or team leads. - Strong hands-on background in data warehousing, analytics, and visualization. - Experience with data architecture and scalable self-service data and reporting solutions. - Experience owning at least one enterprise platform through its full lifecycle, from selection or upgrade through steady-state support. - Strong strategic leadership, communication, problem-solving, and stakeholder management skills. - Ability to work effectively with executive, clinical, operational, financial, and technical stakeholders. - Bachelor's degree in business, mathematics, statistics, computer science, health informatics, or a related field, or equivalent experience. - Master's degree in a related field is preferred. Technical Requirements list (maybe under Requirements as sublist? Could be separate

    Skills? But we can include as part of Requirements as a list). However instruction: Use

    • for any list of duties/requirements/benefits. So we can include technical requirements as list items under Requirements. Thus Requirements
      includes all those items plus technical ones. Technical Requirements: - Epic Cogito - Epic Caboodle - Epic Clarity - Enterprise data architecture and data warehousing - Business intelligence and enterprise analytics - Data governance and data management - Workday ERP - Workday Prism - HL7 / FHIR / APIs - Robotic Process Automation (RPA) - Automated and regression testing - AI/ML governance and monitoring - Cloud data platforms and consumption-based services - Data classification, retention, and enterprise data governance Qualifications (Preferred Qualifications) list: - Provider-side healthcare experience with Epic, Cogito, Caboodle, and Clarity. - Workday ERP ownership across Finance, HCM, or Supply Chain. - Interface engine and healthcare integration experience, including HL7 and FHIR. - Experience building or managing an RPA program. - Experience with AI or machine learning models in production, including monitoring and governance. - Familiarity with the NIST AI Risk Management Framework or comparable AI risk frameworks. - Experience with cloud data platforms and consumption-based cloud services. - Epic Cogito certification. - Workday certification. - CHDA, CPHIMS, or cloud data platform certification. Leadership & Engagement Expectations and Success Measures maybe could be included under Requirements or as separate sections? Not in allowed headings. Could be part of Requirements or maybe we can add a section "Expectations"? Not allowed. Better to incorporate into Requirements or maybe as part of Responsibilities? The Leadership & Engagement Expectations could be considered part of Requirements (skills). Success Measures maybe not needed. But we must preserve ALL substantive information. So we need to include that info somewhere. Could add a section "Expectations" but not allowed heading. Could add as a

      under Requirements or Responsibilities. The instruction: Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use

      for section headings (list). It might be okay to add other headings but they'd deviate from instruction. Safer to embed those details within existing sections as paragraphs or list items. Leadership & Engagement Expectations: - Lead and mentor multidisciplinary teams across data, analytics, AI, integration, RPA, testing, and enterprise applications. - Establish clear priorities and accountability across multiple technology functions. - Partner with clinical, operational, Finance, HR, Information Security, and executive leadership. - Drive continuous improvement, automation, data quality, and operational efficiency. - Maintain strong data confidentiality and comply with healthcare privacy and governance requirements. - Participate in change management, release governance, and enterprise technology planning. - Travel between office, hospital, and other locations may be required. Success Measures: - Business leaders being able to access trusted information without unnecessary reporting requests. - Consistent and reconciled measures across Finance, Quality, and Operations. - AI and predictive models having documented ownership, use cases, and monitoring. - Interface failures being identified through proactive monitoring. - RPA solutions delivering measurable efficiency and error reduction. - Workday releases being implemented on schedule with regression testing completed. - Effective budget, vendor, and technology management. - Strong team retention, development, and internal promotion. We could add these as list items under Requirements or maybe a separate section "Expectations". Since not in allowed headings, maybe we can add a

      Expectations

      but that deviates. However the instruction says "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive. It might be okay to add other headings as long as they are

      . But safer to stick to those. However we need to preserve all substantive info; we can embed them as list items under Requirements (makes sense as expectations/leadership). Or we could add a

      Leadership & Engagement

      but that is not in list. I'd rather embed. Thus Requirements list will be long, covering experience, education, technical, leadership expectations, success measures. But that may become messy. Perhaps better to add a section

      Expectations

      as it's substantive and not covered by other headings. The instruction didn't forbid; it just gave examples. I think it's acceptable. Similarly Success Measures