Epic Applications Systems Specialist, Radiant

We need to output HTML fragment with sections only if real content. Remove boilerplate, navigation, EEO, etc. Keep substantive info: Exemption Status, Hiring Range, Schedule Details, maybe signing bonus note, "Everyone Is a Caregiver" paragraph, responsibilities (I. Major Responsibilities with subpoints), Qualifications (II. Position Qualifications with Required, Preferred, Experience/Skills). Also maybe note about signing bonus. Also maybe note about cost center? Probably not needed as minor metadata; we can fold into short p or drop. The instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. So cost center maybe minor metadata; we can include in a short p if we want but better drop. The hiring range and schedule details are substantive; we need Pay and Schedule sections if posting actually states them. Yes we have Hiring Range and Schedule Details. So we should create

Pay

with the hiring range info. Also maybe note about signing bonus? Could be part of Benefits? Not exactly benefits; but we could include in a

under Pay or a separate Benefits? The instruction: include a section ONLY when posting has real, specific content for it. Benefits section only if posting actually states benefits. There's mention of signing bonus maybe but not detailed benefits. Could include a short

about signing bonus under Pay or maybe a Benefits section? Safer to not create Benefits unless explicit benefits listed. So we can put signing bonus note in a

under Pay or maybe under a general description. We also have "Exemption Status: Exempt". Could be part of Pay or maybe a short p. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include those that have content. Likely we will have About the role (maybe the introductory paragraph about Everyone Is a Caregiver and mission). Responsibilities (the major responsibilities). Qualifications (the Position Qualifications). Pay (hiring range). Schedule (schedule details). Possibly Skills? Could be covered under Qualifications/Experience/Skills. But we could create a Skills section if we want to list skills from Experience/Skills. However instruction: Prefer a few substantive sections over many thin ones. So we could combine Qualifications and Skills into one Qualifications section. But they said use headings like Qualifications, Skills. We could have Qualifications (education/certifications) and Skills (experience/skills). But we can also just have Qualifications covering both. Safer to follow instruction: include a section only when posting has real, specific content for it. If we split, we need to ensure each has content. We have content for both: Qualifications (education, certifications) and Skills (experience, skills). So we can make two sections. Thus sections: About the role (intro paragraph), Responsibilities, Qualifications, Skills, Pay, Schedule. We must not repeat job title as heading. No markdown. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the bullet points etc. Use

• for any list of duties/requirements/benefits. For prose use

  . We need to extract the responsibilities list: It's under "I. Major Responsibilities:" with subheadings like Leadership and Expertise: Critical Incident Management, Knowledge Sharing, Knowledge Advancement, Project Coordination, Mentorship And Coverage, Project And Leadership, Technical Troubleshooting And Support, Adaptability. Each has multiple sentences. We need to preserve all detail. We could treat each bullet as a

• containing the sentences. Might be long but okay. Similarly for Qualifications: "II. Position Qualifications:" with Required, Preferred, Experience/Skills. We'll need to parse. Let's extract text. First, intro: After the boilerplate lines, we have: "Everyone Is a Caregiver At UMass Memorial Health, everyone is a caregiver – regardless of their title or responsibilities. Exceptional patient care, academic excellence and leading-edge research make UMass Memorial the premier health system of Central Massachusetts, and a place where we can help you build the career you deserve. We are more than 20,000 employees, working together as one health system in a relentless pursuit of healing for our patients, community and each other. And everyone, in their own unique way, plays an important part, every day." That's prose. Then "Acts independently to lead multiple projects and assignments facilitating and improving clinical or business information system’s technical solutions and tools." This seems like a summary statement before responsibilities. Could be part of About the role or Responsibilities. Probably part of About the role (general description). We'll include it in About the role paragraph. Then "I. Major Responsibilities:" then sub-sections. We need to capture each bullet. Let's copy the responsibilities text exactly as given: "Leadership and Expertise: Critical Incident Management: Serves as a key member of the team, taking on challenging projects and critical incidents. Provides expert guidance during high-impact situations. Knowledge Sharing: Embraces unknown issues as learning opportunities and proactively shares discovered knowledge with the team. Engages with vendors and systems, even with limited prior experience, to expand understanding and solve complex problems. Knowledge Advancement: Continuously advances knowledge of current products, including obtaining application certifications and staying updated on system configurations and emerging technology and industry trends. Actively participates in professional development programs defined by department. Project Coordination: Project Leadership: Regularly leads projects with appropriate input. Takes responsibility for project outcomes and manages tasks effectively. Project Estimation: Assists in estimating the hours required for upcoming projects to facilitate accurate planning and resource allocation. Workflow Optimization: Recommends and implements workflow modifications. Collaborates with key vendors to discuss and apply standard solutions. Leverages knowledge of user experience design principles during system workflow reviews and/or optimization initiatives. Applies lean belt methodology, which focuses on improving efficiency and reducing waste in processes. Directs the configuration of application features and security settings and creation of support documentation, including test scripts and workflow diagrams. Mentorship And Coverage: Acts as the primary advisor to other team members, department colleagues, and organizational staff. Seeks out and offers support to new staff members and helps them integrate into the team. Constantly innovates and assists others in achieving their ideas. Covers managerial responsibilities in leader’s absence, including handling urgent issues and maintaining team operations. Project And Leadership: Proactively identifies barriers to completing work and escalates issues with proposed solutions. Leads meetings, develops agendas, assumes accountability for assigned follow-ups and practice closed loop communication. Participates as workstream lead on cross-functional projects, ensures tasks are completed within scope and project management guidelines. Runs optimization requests/projects, including scheduling meetings, identifying timelines, and allocating resources. Requests new assignments or participates in stretch goals, coverage opportunities, and additional responsibilities, such as leading new initiatives, completing market analysis or participating in kaizen efforts. Drives projects from conception to completion with minimal oversight and establishes strong working relationships with operational staff as a subject matter expert. Works with vendors to establish short-term product roadmaps. Reviews roadmaps with department manager and key stakeholders. Technical Troubleshooting And Support: Investigates and resolves application and system configuration. Develops and implements appropriate system fixes based on thorough analysis. Works closely with third-party vendors to ensure proper installation and configuration of vendor software. Troubleshoots issues related to server configurations, system services, and interface jobs to drive effective issue resolution. Adaptability: Leverages high adaptability to accomplish dynamic responsibilities and evolving project requirements. Must be able to work off hours as needed and participate in an on-call rotation." We need to keep that detail. Now Qualifications: "II. Position Qualifications: Required: Bachelor's degree in Computer Science or related field, or equivalent work experience. Epic Application certification(s); if additional certifications required for a specific role/team, ability to achieve, as required by department. Lean Green Belt certification or ability to achieve, as required by department. Preferred: Project Management certification (PMP/CAPM). Experience/Skills: Required: 7 years experience with enterprise platforms (EHRs/ITSM/ERPs). Team player with strong problem solving, time management and decision-making skills, ability to maintain a positive attitude, solution focused even in challenging situations. Able to act independently with minimal oversight. Able to advise less experienced team members. Able to effectively communicate to staff at all levels of the organization. Preferred: Healthcare experience. Unless certification, licensure or registration is required, an equivalent combination of education and experience which provides proficiency in the areas of responsibility listed in this description may be substituted for the above requirements. Radiant certification required; Decision Tree expertise preferred; other Epic certifications like Cupid, Stork, Lumens would be valuable also for the role" We need to keep all that. Now Pay and Schedule: "Exemption Status: Exempt Hiring Range: $83,116.80 - $149,593.60 (based on a full time schedule of 40 hours per week). Please note that the final offer will vary based on scheduled hours. Compensation for part-time or reduced schedules will be prorated based on scheduled weekly hours, experience, skills, qualifications, and internal equity considerations. Schedule Details: Monday through Friday Scheduled Hours: 8am - 4:30pm Shift: 1 - Day Shift, 8 Hours (United States of America) Hours: 40 Cost Center: 99940 - 5963 Integration & Large Ancillaries This position may have a signing bonus available a member of the Recruitment Team will confirm eligibility during the interview process." We need Pay section: include Exemption Status, Hiring Range, note about final offer varying, prorated compensation, signing bonus note. Schedule section: Monday through Friday, Scheduled Hours 8am-4:30pm, Shift: Day Shift 8 Hours, Hours: 40. Possibly also mention United States of America but that's location; we can keep. We should not include Cost Center as heading; maybe drop or include in a short p under Schedule? It's minor metadata; we could drop. Now we need to output HTML fragment with sections. Structure:

  About the role

  Everyone Is a Caregiver ...

  Maybe combine the "Acts independently..." sentence into same paragraph. Then

  Responsibilities

  • Leadership and Expertise:
    ...? Actually we need to keep the subheadings inside li? Could just put the whole text as li. But we have multiple subheadings; we could nest ul inside li for each major category. However instruction: Use
    • for any list of duties/requirements/benefits. It doesn't forbid nested lists. We can do nested lists for clarity. Thus:
      • Leadership and Expertise
        • Critical Incident Management: Serves as a key member of the team, taking on challenging projects and critical incidents. Provides expert guidance during high-impact situations.
        • Knowledge Sharing: Embraces unknown issues as learning opportunities and proactively shares discovered knowledge with the team. Engages with vendors and systems, even with limited prior experience, to expand understanding and solve complex problems.
        • Knowledge Advancement: Continuously advances knowledge of current products, including obtaining application certifications and staying updated on system configurations and emerging technology and industry trends. Actively participates in professional development programs defined by department.
      • Project Coordination
        • Project Leadership: Regularly leads projects with appropriate input. Takes responsibility for project outcomes and manages tasks effectively.
        • Project Estimation: Assists in estimating the hours required for upcoming projects to facilitate accurate planning and resource allocation.
        • Workflow Optimization: Recommends and implements workflow modifications. Collaborates with key vendors to discuss and apply standard solutions. Leverages knowledge of user experience design principles during system workflow reviews and/or optimization initiatives. Applies lean belt methodology, which focuses on improving efficiency