EPIC PB/PB CLAIMS SOLUTIONS ANALYST - MAINTENANCE

We need to output HTML fragment with sections: headings

for sections like 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, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Also must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes "Base Pay Overview" and "Salary Description" with salary range. So we can include Pay section with that info. Benefits: "We offer a comprehensive range of benefits. See our website for details: https://ochin.org/employment-openings". That's a statement about benefits but not specific details. The rule: 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. Benefits: they say "We offer a comprehensive range of benefits. See our website for details". That's vague but it's a statement that benefits exist. Is that considered filler? It's not specific details, but it's a statement that benefits are offered. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state that they offer benefits, albeit generic. Should we include Benefits section? It says "We offer a comprehensive range of benefits. See our website for details". That's not specific but it's a statement. The instruction: "Prefer a few substantive sections over many thin ones." Might be better to omit Benefits because it's not specific. However, they explicitly mention benefits and give a link. Could be considered substantive enough? The rule about filler: "never emit a heading followed by filler/placeholder text (e.g., 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The benefits statement is not exactly filler like that, but it's vague. I'd lean to include Benefits section with that sentence. Schedule: Not mentioned explicitly. There's no schedule info (like full-time, part-time). The job type is Full-time mentioned at top: "Job Type Full-time". That's schedule info. So we can include Schedule section with "Full-time". However, the rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Job Type Full-time, so we can include Schedule. Pay: we have salary range. Now sections: About the role (maybe from description). Responsibilities (Essential Duties). Requirements (including certification, experience, skills, etc). Qualifications maybe overlapping with Requirements; but we can combine? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose which to include based on content. We have About the role: description paragraph about OCHIN and mission. That's substantive. Responsibilities: Essential Duties list. Requirements: certification, experience, skills, etc. Qualifications maybe same as Requirements; but we could split: Requirements (certification/experience) and Qualifications (skills). However we might avoid duplication. Let's see content: Requirements section includes: Must have certification/proficiency in one of the following: Epic Resolute PB or PB Claims, certification or proficiency in both is highly desired. The ideal candidate will have at least 5 years of experience as an Epic Resolute PB/PB Claims Applications Analyst, with ideally a minimum of 3 years of experience in Epic PB module build. Strong communication skills – able to communicate with both application and technical team members, as well as end users. Consistently acts with integrity and accountability. Process and detail-oriented, with a strong focus on data-driven decision making. Proactive, self-motivated, and solution oriented. Prior to moving forward to the team interview, all candidates are required to complete a 50–60-minute competency assessment... That's more like process. Also Physical Requirements/Work Environment etc. That could be under Requirements or maybe separate but we can include under Requirements. Skills: maybe we can extract communication skills etc. But we already have them in Requirements. Could create Skills section for communication, problem-solving, etc. But to avoid thin sections, maybe combine. Qualifications: maybe we can include certification and experience as Qualifications. But we already have Requirements. To follow instruction, we can include sections: About the role, Responsibilities, Requirements, Pay, Benefits, Schedule. Possibly also Qualifications if we separate. But we must not create sections with filler. Let's draft:

About the role

MAKE A DIFFERENCE AT OCHIN OCHIN is a nonprofit leader in health care innovation and a trusted partner to a growing national provider network, providing the clinical insights and tailored technologies needed to expand patient access, grow and connect care teams, and improve the health of rural and underserved communities. We are hiring for a number of new positions to meet increasing demand. When you choose to join OCHIN, you have the opportunity to continuously grow your skills and do meaningful work to help fulfill our vision of good health and well-being for everyone. At OCHIN, we value the unique perspectives and experiences of every individual and work hard to maintain a culture rooted in our values. Founded in Oregon in 2000, OCHIN employs a growing virtual workforce of more than 1,200 skilled professionals, working remotely across 49 states. We offer a generous compensation package and are committed to supporting our employees’ entire well-being by fostering a healthy work-life balance and opportunity for professional advancement. We are curious, collaborative learners who strive to live our values every day. OCHIN is excited to support our continued national expansion and the increasing demand for our innovative tools and services by welcoming new talent to our growing team.

That's a lot but it's from description. Now Responsibilities: Essential Duties list. We need to convert each duty into

. The duties are sentences separated by periods. Let's extract: - Develop, document, and deploy solution functionality by building, testing, and maintaining features according to specifications and requirements, while ensuring clear documentation for usability and future reference. - Troubleshoot, diagnose and resolve complex technical issues using critical thinking and advanced technical skills to ensure optimal system performance and end-user satisfaction. - Collaborate across departments to support project implementations and address member maintenance issues. - Drive documentation and knowledge sharing by creating and optimizing technical documentation to support process improvement and alignment across cross-functional teams. - Skill development and competency growth in technical design, analysis, and system enhancements. - Other duties as assigned. We'll put each as

. Now Requirements: We'll list certification, experience, skills, etc. Also include Physical Requirements/Work Environment maybe as part of Requirements. But we could also create a separate section for Physical Requirements? Not in allowed headings list; but we could include under Requirements. Let's list: - Must have certification/proficiency in one of the following: Epic Resolute PB or PB Claims; certification or proficiency in both is highly desired. - At least 5 years of experience as an Epic Resolute PB/PB Claims Applications Analyst, with ideally a minimum of 3 years of experience in Epic PB module build. - Strong communication skills – able to communicate with both application and technical team members, as well as end users. - Consistently acts with integrity and accountability. - Process and detail-oriented, with a strong focus on data-driven decision making. - Proactive, self-motivated, and solution oriented. - Prior to moving forward to the team interview, all candidates are required to complete a 50–60-minute competency assessment. The assessment gives us insights into how your strengths, preferences, and work style align with the OCHIN's nine core competencies. It’s not about passing or failing—it’s about understanding fit and setting you up for success. - Physical Requirements/Work Environment: Required to live within 1 hour of Kirtland Ohio; Up to 25% Travel will be required to support OCHIN’s business requirements for Go-Live installations or training which may require travel by air, vehicle, or train; Constant interpersonal skills, teamwork, and customer service; Frequent creativity, mentoring, presentations/teaching; Occasional decision making and independent judgment or action; Reading, speaking, writing, and understanding English; While performing the duties of the job, the employee is regularly required to sit for long periods of time; stand and walk; use hands to finger, handle or feel; reach with hands and arms; This position requires a virtual home-office environment, working remotely and will require that all employees be on camera for all virtual meetings; The role routinely uses standard office equipment such as computers and mobile devices; 25% Travel may be required to support OCHIN’s business requirements for Go-Live installations or training which may require travel by air, vehicle, or train. - Work Location and Travel Requirements: OCHIN is a 100% remote organization with no physical corporate office location. Employees work remotely from home and many of our positions also support our member organizations on-site for new software installations. Nationwide travel is determined based on OCHIN business needs. Please inquire during the interview process about travel requirements for this position. - Work From Home Requirements: Ability to work independently and efficiently from a home office environment; High Speed Internet Service; It is a requirement that employees work in a distraction free workplace; Travel may be required nationally for on-site Go Live support based on business requirements for OCHIN; In alignment with OCHIN’s mission and commitment to protecting our workforce and the communities we serve, OCHIN strongly encourages all workforce members, especially those whose role involves travel and in-person engagement, to remain up to date on immunizations, including but not limited to COVID-19 and influenza vaccinations. - Work Authorization: Candidates must be legally authorized to work in the United States on a permanent basis at the time of application. This position is not eligible for employment visa sponsorship now or in the future. OCHIN does not provide sponsorship for employment-based visas or transfers of existing employment-based visas. That's a lot but it's all substantive. Now Pay: Salary range is $85,697 - $137,116. Also Base Pay Overview description. We'll include that. We could include Pay section with paragraph: "OCHIN uses broadened pay bands to support equitable and market-aligned compensation practices. The final offer will be based on a variety of factors, including relevant skills, certifications, education, experience, training, responsibilities, internal equity, and market data. Salary range is $85,697 - $137,116." Now Benefits: We have statement: "We offer a comprehensive range of benefits. See our website for details: https://ochin.org/employment-openings". We'll include that. Schedule: Job Type Full-time. Also maybe mention remote work? But schedule is Full-time. We'll include. Now we must not include duplicated lines. Ensure we don't repeat same info multiple times. We have some duplication: Travel mentioned multiple times. We'll try to consolidate. We need to output only HTML fragment, no /, no markdown fences. Let's craft. We'll start with

About the role

then

...

Then

Responsibilities

• ...
...

Then

Requirements

• ...
...

Then

Pay

...

Then

Benefits

...

Then

Schedule

Full-time

Check for any filler: Benefits statement is not filler but it's generic. Acceptable. Now ensure we didn't include Job Title heading. Good. Now ensure we didn't include any boilerplate like EEO etc. We removed