Epic Senior Analyst, Cadence

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate like current employees note, tip sheet, EEO, etc. Also remove application instructions. Keep substantive info. Let's parse content: - Intro: "The University of Miami Health System (“UHealth”) IT Department has an exciting opportunity for a full-time Epic Senior Analyst, Cadence." That's about the role. - Then description: "The Epic Senior Analyst, Cadence initiates the implementation, builds, and modifies complex applications, and collaborates with key stakeholders, end-users, and application team members to optimize the application’s configuration, function, and access. The incumbent supports junior staff members in day-to-day operations and resolving application issues." - Then "Core Responsibilities:" list. - Then "Department Specific Functions:" list. - Then "Duties And Responsibilities As a Epic Senior Analyst – Cadence, you will:" list. - Then note: "This list of duties and responsibilities is not intended to be all-inclusive..." - Then "MINIMUM QUALIFICATIONS:" list. - Then after that: "Any appropriate combination of relevant education, experience and/or certifications may be considered." - Then benefits: "The University of Miami offers competitive salaries and a comprehensive benefits package including medical, dental, tuition remission and more." - Then description of UHealth. - Then "Job Status: Full time Employee Type: Staff" We need sections: About the role (intro). Responsibilities (core responsibilities + department specific + duties). Requirements (maybe minimum qualifications). Qualifications (maybe same as requirements? but we can combine). Skills (maybe list of skills from qualifications: Learning Agility, Teamwork, Technical Proficiency, Communication, etc). Benefits (the benefits sentence). Pay (not given specific salary, only "competitive salaries" - that is vague but maybe we can include as Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It states "competitive salaries" which is a statement about pay, albeit not specific. Is that enough? It says "competitive salaries" - that is a statement about pay. I'd consider that as pay info, albeit not specific. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. "competitive salaries" is not filler like "commensurate with experience"? It's somewhat vague but still a statement. I'd include Pay section with that sentence. Schedule: Not mentioned besides full-time. No schedule details. So we should not create Schedule section. Benefits: we have "competitive salaries and a comprehensive benefits package including medical, dental, tuition remission and more." That's benefits info. So Benefits section. Now we need to avoid duplication. We'll gather responsibilities: combine core responsibilities, department specific functions, duties and responsibilities. Many are repetitive. We need to preserve all substantive information but avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove duplicated lines. So we should deduplicate similar bullet points. Let's extract bullet points: From Core Responsibilities: - Collaborates with key stakeholders, end-users, and application team members to optimize the application’s configuration, function, and access. - Serves as a primary support contact for application end‐users. - Initiates the design, development, implementation, and maintenance of the application. - Initiates all phases of testing and the documentation of workflow design. - Performs the analysis of information technology in clinical work processes and validates the impacts to the workflow. - Initiates the identification of issues and guides the work to resolve them. - Supports junior staff members in the evaluation and resolution of service tickets, identification and implementation of application changes, retrieval of requested data, and execution of day-to-day operations. - Collaborates with trainers on application changes and new features to develop documentation and training strategies. From Department Specific Functions: - Providing oversight and leadership to Associate Epic Analysts and Epic Analysts on the team - Initiating the implementation, build, and modification of the application - Collaborating with key stakeholders, end-users, and application team members to optimize the application’s configuration, function, and access - Supporting junior staff members in day-to-day operations and resolving application issues From Duties And Responsibilities: - Serve as a primary support contact for application end‐users - Initiate the design, development, implementation, and maintenance of the application - Initiate all phases of testing and the documentation of workflow design - Perform the analysis of new releases and validate the impacts to the workflow - Initiate the identification of issues and guide the work to resolve them - Support junior staff members in the evaluation and resolution of service tickets, identification and implementation of application changes, retrieval of requested data, and execution of day-to-day operations - Collaborate with trainers on application changes and new features to develop documentation and training strategies - Work with stakeholders, business community, and end users to ensure the application meets UHealth's business/clinical needs - Mentor and transfer knowledge to Junior staff members - Take the lead in team application projects as assigned by Senior Manager - Participate in on-call rotations and support - Maintain regular communication with team members, including participating in weekly project team meetings - Review the status of projects and issues on an ongoing basis with leadership - Become knowledgeable about UHealth’s policies, procedures, and business operations Also note: "This list of duties and responsibilities is not intended to be all-inclusive and may be expanded to include other duties or responsibilities as necessary." That's a note; we could include as a sentence. Now deduplicate: Many repeats. Let's create a consolidated list of unique responsibilities: 1. Collaborates with key stakeholders, end-users, and application team members to optimize the application’s configuration, function, and access. 2. Serves as a primary support contact for application end‑users. 3. Initiates the design, development, implementation, and maintenance of the application. 4. Initiates all phases of testing and the documentation of workflow design. 5. Performs the analysis of information technology in clinical work processes and validates the impacts to the workflow. 6. Initiates the identification of issues and guides the work to resolve them. 7. Supports junior staff members in the evaluation and resolution of service tickets, identification and implementation of application changes, retrieval of requested data, and execution of day-to-day operations. 8. Collaborates with trainers on application changes and new features to develop documentation and training strategies. 9. Provides oversight and leadership to Associate Epic Analysts and Epic Analysts on the team. 10. Works with stakeholders, business community, and end users to ensure the application meets UHealth's business/clinical needs. 11. Mentors and transfers knowledge to junior staff members. 12. Takes the lead in team application projects as assigned by Senior Manager. 13. Participates in on-call rotations and support. 14. Maintains regular communication with team members, including participating in weekly project team meetings. 15. Reviews the status of projects and issues on an ongoing basis with leadership. 16. Becomes knowledgeable about UHealth’s policies, procedures, and business operations. 17. Performs analysis of new releases and validates impacts to workflow (similar to #5 but specific to new releases; we can keep as separate or merge? It's slightly different: analysis of new releases vs analysis of IT in clinical work processes. Keep both.) 18. Note: This list is not all-inclusive and may be expanded. Now Minimum Qualifications: - Bachelor’s Degree - Minimum of 5 years of experience, preferably in healthcare or healthcare-related organization - 3-5 years of Epic build experience - Understanding of scheduling and payer authorization, including nuances of provider schedules, scheduling practices for certain types of visits, and how these practices relate to the medical record flow for appointments preferred - Knowledge of areas that integrate with Cadence, including check‑in, registration, benefits, referrals, PCP assignment, and orders preferred - Previous operational, project management, and organizational skills - Epic Cadence/Referrals Certification - Ability to work evenings, nights, and weekends as necessary. - Learning Agility: Ability to learn new procedures, technologies, and protocols, and adapt to changing priorities and work demands. - Teamwork: Ability to work collaboratively with others and contribute to a team environment. - Technical Proficiency: Skilled in using office software, technology, and relevant computer applications. - Communication: Strong and clear written and verbal communication skills for interacting with colleagues and stakeholders. - Works with stakeholders, the business community, and end users to ensure the application meets UHealth's business/clinical needs. (duplicate) - Participates in on-call rotations and support and attend and participates in, applicable committees. - Maintains regular communication with team members, including participating in weekly project team meetings. - Reviews the status of projects and issues on an ongoing basis with leadership. - Remains knowledgeable about UHealth’s policies, procedures, and business operations. - Adheres to University and unit-level policies and procedures and safeguards University assets. - Any appropriate combination of relevant education, experience and/or certifications may be considered. We need to separate into Requirements, Qualifications, Skills. The instruction: Use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. Typically: About the role = intro paragraph. Responsibilities = list of duties. Requirements = minimum qualifications (education, experience). Qualifications = certifications, preferred knowledge. Skills = soft skills like learning agility, teamwork, technical proficiency, communication. But we must not invent sections if content is thin. We'll allocate: - About the role: intro paragraph(s) about the opportunity and role description. - Responsibilities: consolidated list as above. - Requirements: Bachelor’s Degree, Minimum of 5 years of experience preferably in healthcare, 3-5 years of Epic build experience. Possibly also "Epic Cadence/Referrals Certification" could be qualification. - Qualifications: Understanding of scheduling and payer authorization preferred, Knowledge of areas that integrate with Cadence preferred, Previous operational, project management, and organizational skills, Ability to work evenings, nights, and weekends as necessary, Any appropriate combination of relevant education, experience and/or certifications may be considered. - Skills: Learning Agility, Teamwork, Technical Proficiency, Communication, Works with stakeholders... (maybe duplicate), Participates in on-call rotations..., Maintains regular communication..., Reviews status..., Remains knowledgeable..., Adheres to policies... But many of those are also responsibilities. Might be overlapping. However we must preserve all substantive info; we can keep them in Skills if they are skill statements. But we need to avoid duplication across sections. The instruction: Remove duplicated lines. So we should not repeat same bullet in multiple sections. We'll need to decide where each piece belongs uniquely. Let's list all unique statements from the posting (excluding intro and benefits/pay). We'll categorize. Statements list: 1. Bachelor’s Degree 2. Minimum of 5 years of experience, preferably in healthcare or healthcare-related organization 3. 3-5 years of Epic build experience 4. Understanding of scheduling and payer authorization, including nuances of provider schedules, scheduling practices for certain types of visits, and how these practices relate to the medical record flow for appointments preferred 5. Knowledge of areas that integrate with Cadence, including check‑in, registration, benefits, referrals, PCP assignment, and orders preferred 6. Previous operational, project management, and organizational skills 7. Epic Cadence/Referrals Certification 8. Ability to work evenings, nights, and weekends as necessary. 9. Learning Agility: Ability to learn new procedures, technologies, and protocols, and adapt to changing priorities and work demands. 10. Teamwork: Ability to work collaboratively with others and contribute to a team environment. 11. Technical Proficiency: Skilled in using office software, technology, and relevant computer applications. 12. Communication: Strong and clear