Sr Application Analyst

We need to output HTML fragment with sections: About the role? The posting includes a summary line: "Candidates must have a primary address located within the state of Michigan or willing to move to Michigan to be considered." Then job title line: "Sr Analyst - Epic Release & Systems Administrator". Then description paragraphs. Then "Responsibilities" with subsections. Then "Other Duties And Responsibilities". Then "Certifications and Licensures". Then "Required Education". Then "Other Information" with subheadings: Experience, Training And Skills; Technical Knowledge And Skills; Leadership And Communication Skills; Core Competencies; Physical/Mental Requirements And Typical Working Conditions. We need to use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should only include sections that have real specific content. So we need to map content to these headings. We have: - About the role: could be the summary paragraph after title? The description about managing Epic software releases etc. That's a prose description. So we can have

About the role

then

...

. - Responsibilities: we have a big list of duties. Use

• for each duty. The responsibilities section includes subcategories with percentages. We can flatten into list items preserving details. Must not lose info. Could keep subheadings? But we only allowed

  for section headings; we could still have

  ? Not allowed? The instruction says use

  for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we can just use

  for main sections and use

  or

  • inside. We can keep subheadings as bold text within

    maybe, but better to keep as inside

  • . We'll preserve content. - Requirements / Qualifications: we have Certifications and Licensures, Required Education, Other Information (Experience, Training And Skills etc). Could combine into Requirements section? But we have separate headings possible: Requirements, Qualifications, Skills. We need to decide based on content. We have: - Certifications and Licensures: Preferred Epic certification, ITIL certification, experience supporting Epic etc. - Required Education: Associates Degree or Bachelors in IT, business, or healthcare field with four (4) or more years of work-related experiences providing advanced application system support. - Other Information: includes Experience, Training And Skills; Technical Knowledge And Skills; Leadership And Communication Skills; Core Competencies; Physical/Mental Requirements And Typical Working Conditions. Thus we could have sections: Requirements (covering Certifications and Licensures, Required Education), Qualifications (maybe experience), Skills (technical knowledge, leadership, core competencies). But we need to avoid thin sections. Perhaps combine into one "Requirements" section with subpoints. But instruction: Prefer a few substantive sections over many thin ones. So maybe we have: About the role, Responsibilities, Requirements (including education, certifications, experience, skills, physical requirements). That's it. We must not include Benefits, Pay, Schedule unless present. Not present. We must not repeat job title as heading. We must not include Job ID etc. We must remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We must preserve all substantive information. Thus produce:

    About the role

    ... (summary paragraph about managing Epic software releases etc.)

    Responsibilities

    • ... each duty ...
    ...

    Requirements

    • ... education ...
    • ... certifications ...
    • ... experience ...
    • ... technical knowledge ...
    • ... leadership and communication ...
    • ... core competencies ...
    • ... physical/mental requirements ...
    But we need to ensure we don't lose details like percentages etc. We'll embed them in list items. Let's extract the About the role paragraph: The text after title: "The Epic Release & Systems Administrator is responsible for managing Epic software releases and administering key Epic management tools and processes. This position serves as the primary owner of Epic quarterly release planning and execution, Data Courier governance, Epic UserWeb administration, Nova administration, and Epic environment coordination. The role acts as the central liaison between Epic representatives, application analysts, technical teams, leadership, training resources, and operational stakeholders to ensure successful implementation of Epic releases, effective migration of Epic content, stable system environments, and ongoing compliance with Epic governance processes. This position provides operational leadership for Epic release activities and serves as the organization's primary coordinator for Epic administration, environment maintenance, and system-wide Epic initiatives." We'll put that in

    . Now Responsibilities: We have subsections with percentages. We'll create list items for each bullet under each subsection. Let's extract each bullet: Epic Release Management (35%) - Serve as the primary project manager for Epic quarterly releases, updates, and major Epic initiatives. - Develop and maintain release schedules, milestones, and implementation timelines. - Facilitate bi-weekly Epic Release Workgroup meetings. - Coordinate review, installation, build, testing, training preparation, and deployment activities. - Track release-related tasks, dependencies, risks, and issues. - Collaborate with application analysts, technical teams, training staff, operational leaders, and Epic representatives to ensure release readiness. - Coordinate go-live planning, support activities, and downtime procedures. - Monitor release progress and communicate status updates to leadership and stakeholders. - Coordinate end-user communications related to Epic upgrades and releases. - Ensure timely completion of release deliverables and action items. Data Migration (Data Courier Administration) (20%) - Facilitate monthly Data Migration Workgroup meetings. - Administer Epic Data Courier migration activities. - Coordinate migration planning and movement of Epic records and configurations between environments. - Maintain migration controls including locking and unlocking items and management of direct-edit workflows. - Troubleshoot Data Courier-related issues and coordinate resolutions. - Create and maintain migration-related interfaces and supporting processes. - Develop and maintain migration standards, procedures, and documentation. - Ensure adherence to established change control and migration governance processes. Technical and Epic Coordination (15%) - Serve as the primary liaison between Epic, Epic Technical Coordinators, application teams, technical services teams, and IT leadership. - Facilitate recurring meetings related to Epic releases, package installations, environment changes, and technical issues. - Coordinate activities among application, infrastructure, network, security, and support teams. - Escalate and track Epic-related issues through resolution. - Support collaboration and communication between internal stakeholders and Epic representatives. - Participate in planning and coordination of Epic-related operational and strategic initiatives. Epic Environment Management (10%) - Coordinate package loads, software updates, upgrades, and maintenance activities across Epic environments. - Coordinate environment refreshes and testing readiness activities. - Monitor Epic Security and Privacy Risk Escalation (SPRE) bulletins and coordinate required actions. - Troubleshoot and coordinate resolution of environment-related issues. - Maintain awareness of environment stability, availability, and readiness. - Communicate environment changes and impacts to stakeholders. Nova Administration (10%) - Serve as Epic Nova Administrator. - Create and maintain projects within Nova. - Manage project assignments, work queues, notes, tracking activities, and reporting. - Maintain Nova roles, teams, assignment rules, and user access. - Support process improvement and standardization of Nova workflows. Epic UserWeb Administration (10%) - Serve as Epic UserWeb Administrator. - Manage UserWeb accounts, permissions, access requests, and user groups. - Administer App Orchard access requests and activities. - Manage Sherlock access requests and approvals. - Maintain Epic administrative records and documentation. - Ensure compliance with Epic access management requirements. Other Duties And Responsibilities (a long paragraph). We need to break into list items for each sentence? The instruction: Use

    • for any list of duties/requirements/benefits. So we should convert that paragraph into list items. It's a long prose with many sentences separated by periods. We'll split into separate items per sentence or clause. Let's extract sentences: - Exhibit a commitment to exceptional customer service while providing Go-Live or Daily end user support and training of Applications. - Serves as an owner of IT and Operations workflows by following standard Change Management processes, using analytical decision-making, and understanding all technical, clinical, and financial impacts. - Proactively predicts and presents operational needs for system changes, collaborates closely with operational partners to align IT improvements with business and clinical goals. - Builds trusted relationships with operational leaders and staff by providing consistent follow-up on changes, issues, and upgrades, ensuring transparency and accountability within IT. - Maintains expertise as subject matter expert to one or more applications and integrated areas, with strong knowledge of all third-party applications. - Utilize knowledge of all application integrations and transition points between primary application and third-party applications to troubleshoot and provide support. - Drives informed decisions on system upgrades and enhancements by leading conceptualization, creation, testing, and upkeep of system improvements. - Deliver prompt, efficient, and effective customer assistance by skillfully addressing reported concerns until they are successfully resolved by bringing all necessary parties together and delegating tasks to ensure success. - Effectively communicates technical components in terms of clinical, financial, and business outcomes, presenting information in a succinct and easy to understand way. - Facilitate and lead meetings, manage priorities, resolve conflicts, maintain a comprehensive issues list, and maintain project tasks within specified timelines. - Leads applications teams in coordinating the design, build, testing, training, and troubleshooting of applications. - Supports all staff in efforts to resolve critical issues and meet deadlines. - Regularly analyze performance metrics and implement optimizations to enhance efficiency and reliability. - Shares IT metrics and developments with leaders and frontline staff routinely. - Effectively collaborates cross functionally with all teams, understanding both IT and operational impacts of decisions. - Manage medium to large-size requests from inception to completion. - Develop and manage plans and timelines, coordinate resources within IT, and ensure that requests are delivered within scope and on time. - Actively participate in strategic planning for the application system and develop implementation plans for new system functionality. - Works collaboratively with other members of the IT team and end users to develop and implement these plans. - Participates in an on-call support rotation to address organizational urgent needs. - Travel between MyMichigan Locations may be required to support applications and go-live implementations. - Acts as a mentor and subject matter expert, sharing knowledge and best practices with team members. - Facilitate knowledge sharing sessions, training programs, and documentation repositories to promote continuous learning and skill development. - Embrace the technological orientation of MyMichigan Health by showcasing competency in Microsoft Windows. - Upon hiring, complete a Computer Skills Assessment via the learning management system. - Depending on assessment outcomes, engage in further learning opportunities provided by MyMichigan Health. Now Certifications and Licensures: "Preferred Epic certification, accreditation, proficiency, or demonstrated Epic administration experience. ITIL certification or related healthcare IT certification. Experience supporting Epic, Infor Lawson, OnBase, or other enterprise healthcare applications." We'll make list items. Required Education: "Associates Degree or Bachelors in IT, business, or healthcare field with four (4) or more years of work-related experiences providing advanced application system support." Other Information sections: Experience, Training And Skills: - Five (5) or more years of experience supporting healthcare information technology systems, enterprise software platforms, or electronic medical record systems. - Experience coordinating software releases, upgrades, system implementations, or operational technology initiatives. - Experience working with technical teams, application teams, vendors, and organizational leadership. - Experience facilitating meetings, coordinating workgroups, and managing operational activities across multiple teams. - Experience developing communications, tracking deliverables, and coordinating issue resolution activities. Technical Knowledge And Skills: - Working knowledge of Epic systems, release processes, and environment management practices. - Experience with Epic Data Courier