Epic Analyst IV – Ambulatory & Care Link (EpicCare)

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate. We need to parse the job posting. Content: POSITION SUMMARY: description of role. Primary Accountabilities: list of duties. Work Experience MINIMUM QUALIFICATIONS: Education, Work Experience, Licensure, Certification, Work Experience In Lieu of Education, Skills/Knowledge/Abilities. Preferred Qualifications: Education, Work Experience, Certification, Prefer candidates who are Epic Build accredited..., Prefer candidates with Epic Care Link experience... Physical Requirements: description. Benefits: only heading "Benefits" then a paragraph about Health First diversity etc. Schedule: "Schedule : Full-Time Shift Times : 800am_500pm Paygrade : PG-PG-PG-PG-PG-PG-PG-PG-PG-PG-PG-PG-EP4" We need sections: About the role (position summary). Responsibilities (primary accountabilities). Requirements (maybe minimum qualifications?). Qualifications (preferred qualifications?). Skills (skills/knowledge/abilities). Benefits (the paragraph). Pay (paygrade). Schedule (schedule and shift times). Physical Requirements maybe could be part of Requirements? But we have no heading for Physical Requirements in list; we could include under Requirements or maybe as separate but not in allowed headings list. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we should only use those headings if content exists. We could also include other headings if needed? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we need to map content to those sections. Thus: - About the role: position summary paragraph. - Responsibilities: primary accountabilities (list). - Requirements: minimum qualifications (education, work experience, licensure, certification, work experience in lieu of education). Could also include physical requirements? Might be part of Requirements. - Qualifications: preferred qualifications (education, work experience, certification, preferences). - Skills: skills/knowledge/abilities (proficient in MS Office, project management, Epic modules, leadership, problem solving, etc.) - Benefits: the paragraph about Health First diversity etc. - Pay: paygrade line. - Schedule: schedule line (Full-Time Shift Times: 800am_500pm). We must not include placeholder text like "commensurate with experience". Not present. We must preserve all substantive info; do not invent or summarize away detail. So we need to keep details exactly as given, but we can format as lists. We must not repeat job title as heading. Not include Job ID etc. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. There's none obvious besides maybe the benefits paragraph includes diversity statement; that's substantive. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

The Epic Applications Analyst IV is an expert responsible for leading system-wide Epic Electronic Medical Record (EHR) initiatives, driving strategic alignment, and serving as a trusted advisor to executive leadership. The Epic Applications Analyst IV oversees large-scale implementations, optimizations, and integrations while ensuring compliance with healthcare regulations. The Epic Applications Analyst IV mentors analysts, leads cross-functional collaboration, and acts as a key liaison with Epic Systems and external vendors to deliver scalable, innovative solutions that enhance care delivery and operational efficiency.

Responsibilities

• Oversees large-scale Epic EHR implementations, and system upgrades, ensuring deliverables are met in an efficient and timely manner, adherence to proposed budget, and alignment with Health First’s goals.
• Leads teams in system-wide Epic optimization and integration projects, delivering seamless system performance and end-user implementation.
• Collaborates with leadership to advise, coach, and support the development of Epic Applications Analysts, and project team leads, contributing expertise and sponsoring best practices across the team.
• Partners with executive leadership and applicable stakeholders to align strategies with Health First’s objectives and goals, while delivering advisement on system capabilities and continuous planning long-term.
• Ensures full compliance with Healthcare regulations and standards such as: Health Insurance Portability and Accountability Act (HIPAA), The Joint Commission (TJC), internal IT governance and Health First policies and procedures.
• Acts as point of contact and liaison between the Integrated Delivery Network (IDN), Epic Applications, and vendors to manage escalations, enhancement requests, and organize technical support to all applicable stakeholders.
• Provides thoughtful and strategic leadership in system, Epic planning, and data integration to support innovation and growth for Health First’s EHR system.

Requirements

Education: Bachelor’s degree in Information Technology, Healthcare or Business Administration, or relevant field.

Work Experience: Six (6) years of experience with an EHR, including leading projects.

Licensure: None

Certification: Accreditation(s) in multiple specialties prior to start date and maintained.

Work Experience In Lieu of Education: Eight (8) years of experience with an EHR, including leading projects.

Alternatively could combine into a list. But we need to preserve all info. Could use

• for each bullet. The instruction: Use
  • for any list of duties/requirements/benefits. So for Requirements we should use a list. Let's do:

    Requirements

    • Education: Bachelor’s degree in Information Technology, Healthcare or Business Administration, or relevant field.
    • Work Experience: Six (6) years of experience with an EHR, including leading projects.
    • Licensure: None
    • Certification: Accreditation(s) in multiple specialties prior to start date and maintained.
    • Work Experience In Lieu of Education: Eight (8) years of experience with an EHR, including leading projects.
    Similarly for Qualifications (preferred):

    Qualifications

    • Education: Bachelor’s degree in Information Technology, Healthcare or Business Administration, or relevant field.
    • Work Experience: Six (6) years of experience with Epic EHR, including leading projects.
    • Certification: Project Management Professional (PMP). Certified Scrum Master (CSM). Certified Healthcare Technology Specialist (CHTS). Certified Professional in Healthcare Information and Management Systems (CPHIMS).
    • Prefer candidates who are Epic Build accredited or certified, with a strong emphasis on hands-on Build experience.
    • Prefer candidates with Epic Care Link experience, including Build, configuration, optimization, and support of provider access and interoperability workflows.
    Skills:

    Skills

    • Proficient in Microsoft Office – Outlook, Word, Excel, PowerPoint.
    • Proven ability in managing large-scale and cross-functional projects.
    • Expert-level knowledge of multiple Epic modules.
    • Advanced skills in leadership and mentoring.
    • Excellent skills in problem solving and decision making.
    • Strong project management and organizational skills.
    • In-depth knowledge and understanding of Healthcare regulations and IT governance and compliance.
    Benefits:

    Benefits

    At Health First, diversity and inclusion are essential for our continued growth and evolution. Working together, we strive to build and nurture a culture that recognizes, encourages, and respects the diverse voices of our associates. We know through experience that different ideas, perspectives, and backgrounds create a stronger and more collaborative work environment that delivers better results. As an organization, it fuels our innovation and connects us closer to our associates, customers, and the communities we serve.

    Pay:

    Pay

    Paygrade : PG-PG-PG-PG-PG-PG-PG-PG-PG-PG-PG-PG-EP4

    Schedule:

    Schedule

    Schedule : Full-Time Shift Times : 800am_500pm

    We need to ensure we didn't miss any substantive info: Physical Requirements not included anywhere; but we have no heading for it. Should we include it under Requirements? The instruction says use those headings e.g., but we could add a section for Physical Requirements if we want, but it's not in the list. The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are examples; we could still use other headings if needed, but better to stick to those. However, we must preserve ALL substantive information. If we omit Physical Requirements, we lose info. So we need to include it somewhere. Perhaps we can include Physical Requirements under Requirements as a list item. That would preserve it. Let's add a list item under Requirements: "Physical Requirements: Majority of time involves sitting or standing; occasional walking, bending, and stooping. Long periods of computer time or at workstation. Light work that may include lifting or moving objects up to 20 pounds with or without assistance." Also include other details: "May be exposed to inside environments with varied temperatures, air quality, lighting and/or low to moderate noise. Communicating with others to exchange information. Visual acuity and hand-eye coordination to perform tasks. Workspace may vary from open to confined. May require travel to various facilities within and beyond county perimeter; may require use of personal vehicle." We should include all that. Thus Requirements list will have many items. Let's compile Requirements list items: - Education: Bachelor’s degree in Information Technology, Healthcare or Business Administration, or relevant field. - Work Experience: Six (6) years of experience with an EHR, including leading projects. - Licensure: None - Certification: Accreditation(s) in multiple specialties prior to start date and maintained. - Work Experience In Lieu of Education: Eight (8) years of experience with an EHR, including leading projects. - Physical Requirements: Majority of time involves sitting or standing; occasional walking, bending, and stooping. Long periods of computer time or at workstation. Light work that may include lifting or moving objects up to 20 pounds with or without assistance. - Environmental: May be exposed to inside environments with varied temperatures, air quality, lighting and/or low to moderate noise. - Communication: Communicating with others to exchange information. - Visual: Visual acuity and hand-eye coordination to perform tasks. - Workspace: Workspace may vary from open to confined. - Travel: May require travel to various facilities within and beyond county perimeter; may require use of personal vehicle. We could combine some. Now ensure we didn't duplicate any content. The original also had "Note HR Title: Epic Applications Analyst IV External Marketing Title: Epic Analyst IV – Ambulatory & Care Link (EpicCare)" - that's metadata; we should drop it per instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. This is minor metadata; we can drop it. Also "Benefits ABOUT HEALTH FIRST" heading: we already captured benefits paragraph. Now check for any other substantive info: The "Schedule : Full-Time