Enterprise Epic Architect

We need to output HTML fragment with sections only when content present. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The posting includes Position Summary (maybe About the role), Key Responsibilities, Requirements (Education, Experience, Certifications, Technical Skills, Soft Skills), Preferred Qualifications, Working Conditions, Physical Requirements. We need to map to headings: About the role (position summary), Responsibilities (Key Responsibilities), Requirements (Education, Experience, Certifications maybe), Qualifications (Preferred Qualifications), Skills (Technical Skills and Soft Skills maybe combined), Benefits (none), Pay (none), Schedule (Working Conditions maybe? Actually schedule is about hybrid, occasional after-hours). The instructions: include a section ONLY when posting has real, specific content for it. So we need to include sections for About the role, Responsibilities, Requirements, Qualifications, Skills, maybe Working Conditions as Schedule? But schedule heading is for schedule info; we have hybrid and occasional after-hours. That could go under Schedule. Benefits: none, so omit. Pay: none, omit. We must not repeat job title as heading. Use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. We need to output only HTML fragment. Let's structure:

  About the role

  then

  with position summary text. Then

  Responsibilities

  then maybe break into sub-sections? But we can just list responsibilities as
  • each bullet. The responsibilities are many paragraphs grouped under headings like Enterprise Architecture and Data Strategy, Epic Cogito Stack Ownership, etc. We need to preserve all detail; we can keep each bullet as a responsibility statement. Could also keep subheadings inside

    but instructions only say use

    for section headings; subheadings not required. We could keep them as

    bold? But better to keep as

    with the full sentence. We need to extract each responsibility bullet from the text. Let's parse responsibilities section: "Enterprise Architecture and Data Strategy Design and maintain the enterprise architecture for Epic's Cogito analytics suite, including Clarity, Caboodle, Cogito Cloud, and associated reporting and analytics tools. Define data architecture standards, governance policies, and best practices for extraction, transformation, and consumption of Epic clinical and operational data. Serve as the primary technical authority on Epic data models, schema design, and downstream data integration strategy. Develop and maintain the enterprise roadmap for Epic analytics capabilities, including migration and optimization strategy for Cogito Cloud, in alignment with organizational priorities." "Epic Cogito Stack Ownership Architect and optimize Clarity, Caboodle, and Cogito Cloud data warehouse structures to support enterprise reporting, self-service analytics, and advanced data science initiatives. Provide architectural oversight for Reporting Workbench, Radar dashboards, SlicerDicer, and Business Objects universes to ensure consistency, performance, and scalability. Lead technical evaluation and adoption of new Epic analytics capabilities, including Epic Cosmos and Epic Agent Factory. Ensure Epic analytics environments are properly tuned, monitored, and maintained for performance and reliability." "Epic Cosmos and Agent Factory Enablement Lead enterprise strategy for leveraging Epic Cosmos multi-organization data to support benchmarking, research, and predictive analytics initiatives. Architect and govern the deployment of Epic Agent Factory based AI agents and automation solutions across clinical and operational workflows. Partner with clinical, operational, and data science stakeholders to identify high value use cases for Cosmos data and Agent Factory automation. Ensure appropriate governance, validation, and monitoring frameworks are in place for AI agents and Cosmos derived insights." "Predictive Modeling and Advanced Analytics Architect the data foundation required to support predictive modeling initiatives, including feature engineering pipelines sourced from Clarity, Caboodle, and Cosmos. Partner with data science and clinical informatics teams to operationalize predictive models within Epic workflows (e.g., risk scores, care gap alerts, deterioration indices). Ensure predictive model outputs are properly integrated, validated, and monitored within Epic and downstream reporting environments. Guide model governance practices including performance monitoring, drift detection, and revalidation cadence in partnership with data science teams." "Epic Gold Stars and Honor Roll Analytics Analyze current state reporting and analytics utilization against Gold Stars and Honor Roll benchmarks to identify capability gaps and prioritize remediation. Partner with analytics team members and report developers to optimize dashboard design, self-service adoption, and reporting standardization in support of program criteria. Track, document, and present analytics maturity progress and program metrics to executive leadership and Epic program representatives. Use Gold Stars and Honor Roll participation as a benchmark to continuously elevate enterprise analytics quality, governance, and adoption standards." "Data Governance and Security Establish and enforce data governance standards for Epic sourced data across the enterprise, ensuring compliance with HIPAA and organizational security policies. Partner with compliance, privacy, and security teams to ensure appropriate access controls, auditing, and data stewardship practices are in place. Define and maintain data lineage, metadata management, and documentation standards for enterprise Epic data assets, including Cosmos and Agent Factory outputs." "Cross-Platform Integration Architect integration strategies connecting Epic Cogito data, Cosmos, and Agent Factory outputs with enterprise platforms including Microsoft Fabric, Power BI, Azure, and other enterprise data warehouse or lakehouse environments. Collaborate with enterprise data teams to ensure Epic data is efficiently and securely made available for downstream reporting, analytics, and AI/ML use cases. Support integration of Epic data with emerging AI and automation initiatives, including data agents, AI Foundry, and Cosmos based solutions." "Technical Leadership and Governance Serve as a subject matter expert and mentor for Epic analytics developers, BI developers, and analytics engineers. Lead architectural design reviews and provide technical guidance on enterprise reporting, analytics, and predictive modeling projects. Partner with Epic application teams (Clinical, Revenue Cycle, Ambulatory, etc.) to ensure architectural alignment across the enterprise Epic ecosystem. Represent Data Analytics in enterprise architecture review boards, IT governance committees, and Epic upgrade planning sessions." "Strategic Partnership Act as a strategic advisor to executive leadership on the capabilities, limitations, and opportunities within the Epic Cogito analytics platform, Cosmos, and Agent Factory. Partner with vendor relationships (Epic, Microsoft, and other analytics platform partners) to stay ahead of platform capabilities and roadmap changes. Support organizational AI and analytics strategy by ensuring the Epic data foundation is architected to support current and future advanced analytics, predictive modeling, and AI initiatives." We'll list each bullet as

    . Now Requirements: includes Education, Experience, Certifications, Technical Skills, Soft Skills. We can combine into one Requirements section with sub-bullets? Could separate into subheadings but only

    allowed for section headings; we could still use

    for prose and

    • for lists. We'll create

      Requirements

      then maybe

      Education: ...

      etc. But better to use
      • for each requirement item. However some items are paragraphs like Education: "Bachelor's degree in Computer Science, Information Systems, Health Informatics, or a related field required. Master's degree preferred." That's two sentences; we can keep as one
      • . Experience: multiple bullet points. We'll break each line as
      • . Certifications: list. Technical Skills: list. Soft Skills: list. We'll keep them as separate
        maybe under Requirements? But instructions: Use
        • for any list of duties/requirements/benefits. So we can have multiple lists. We'll output:

          Requirements

          • Bachelor's degree in Computer Science, Information Systems, Health Informatics, or a related field required. Master's degree preferred.
          • Minimum 7 to 10 years of experience in healthcare data analytics, data architecture, or Epic application development.
          • Minimum 5 years of direct experience working with Epic's Cogito analytics suite (Clarity, Caboodle, Cogito Cloud, Reporting Workbench, SlicerDicer, Radar).
          • Direct experience with Epic Cosmos and Epic Agent Factory strongly preferred.
          • Experience supporting or architecting predictive modeling initiatives within a healthcare data environment.
          • Demonstrated experience architecting enterprise scale data warehouse or lakehouse solutions in a healthcare environment.
          • Experience with Epic data model structures and healthcare data standards (HL7, FHIR).
          • Prior experience leading or contributing to Epic Gold Stars and/or Honor Roll analytics submissions strongly preferred.
          • Epic Cogito certification(s) required (Clarity and/or Caboodle Data Model Certification).
          • Additional Epic certifications (Reporting Workbench, Business Objects, Radar) strongly preferred.
          • Epic Cosmos and/or Agent Factory credentialing preferred as available.
          Then maybe separate Technical Skills and Soft Skills as separate sections? Could be under Skills heading. The instruction: Use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have a Skills section. We'll put Technical Skills and Soft Skills under Skills heading, maybe as two

          lists or combine. We'll do:

          Skills

          • Deep expertise in SQL and relational database design.
          • Strong understanding of dimensional data modeling and enterprise data warehouse architecture.
          • Experience with Microsoft Fabric, Azure Synapse, Power BI, or equivalent enterprise BI and cloud data platforms.
          • Familiarity with predictive modeling concepts, feature engineering, and model validation practices.
          • Working knowledge of Python, data pipeline tools, and modern data engineering practices a plus.
          • Strong understanding of HIPAA compliance and healthcare data governance requirements.
          • Excellent communication skills with the ability to translate complex technical concepts for executive and non-technical audiences.
          • Strong leadership and mentorship capabilities.
          • Proven ability to manage competing priorities across multiple stakeholders and departments.
          • Strategic thinker with strong problem solving and analytical skills.
          • Analytical and metrics driven approach to tracking and improving reporting maturity benchmarks.
          Now Qualifications: Preferred Qualifications section. We'll use

          Qualifications

          and list. Preferred Qualifications bullet list: - Experience in a multi-hospital or health system enterprise environment. - Prior experience leading enterprise architecture governance boards or technical steering committees. - Experience supporting AI/ML or predictive modeling initiatives built on top of Epic data. - Familiarity with Epic's Cosmos multi-organization data platform and Agent Factory automation framework. - Direct prior experience achieving Epic Gold Stars or Honor Roll analytics recognition at a health system. Now Schedule: Working Conditions and Physical Requirements. We'll combine under Schedule heading? Actually schedule heading is for schedule info; we have hybrid with periodic onsite presence required, occasional after-hours support may be required. Physical requirements separate but could be under Schedule as well? Might be better to have Schedule for hybrid/after-hours, and maybe Physical Requirements could be omitted? But we have content for physical requirements; there is no specific heading for Physical Requirements in allowed list, but we could put under Schedule or maybe under Qualifications? Better to create a Schedule section with hybrid/after-hours, and maybe add a note about physical requirements as a

          under Schedule? The instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can have Schedule with hybrid/after-hours and physical requirements as part of that section. Thus:

          Schedule

          • Hybrid with periodic onsite presence required for architecture reviews, governance meetings, and stakeholder collaboration.
          • Occasional after-hours support may be required for critical system upgrades or maintenance windows.
          • Ability to sit for extended periods while