EPIC CERTIFIED CLINDOC/STORK ANALYST

We need to output HTML fragment with sections: About the role? Actually we have description paragraphs about OCHIN. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We have: - Description: includes mission, etc. Could be "About the role" or maybe "About OCHIN". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading with prose describing role and organization. - Responsibilities: we have "Essential Duties" list. So we can have

Responsibilities

with

• items. - Requirements: we have "Requirements Qualifications" section. Might combine Requirements and Qualifications? The instruction says separate headings possible. We have both Requirements and Qualifications content. We can have

  Requirements

  with list of requirements (experience, education, etc.) and

  Qualifications

  with list of qualifications (certifications, etc.) Or we could combine but better separate if content distinct. - Skills: maybe not explicit separate list; we have "Intermediate proficiency in Microsoft Excel" and maybe other skills implied. Could include under Skills. - Benefits: we have "We offer a comprehensive range of benefits. See our website for details: ..." Not specific benefits listed, just generic. According to rule: do NOT create Benefits section unless posting actually states them. It states "We offer a comprehensive range of benefits." but not specific. Is that enough? It says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "We offer a comprehensive range of benefits." is vague but still states benefits exist. Might be considered filler? Probably not specific enough. Safer to omit Benefits section. - Pay: we have "Base Pay Overview" and salary range Min- $85,697.00 to $137,116.00. That's specific. So include Pay section. - Schedule: we have work location and travel requirements: remote, travel up to 25%, etc. That's schedule-ish. Could include Schedule section with remote and travel details. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, etc. Also remove "Equal Opportunity Employer..." etc. Also remove "Work Location and Travel Requirements" maybe we keep as Schedule. We need to preserve all substantive information. Let's extract content. About the role: combine description paragraphs about OCHIN and position overview. Paragraphs: "MAKE A DIFFERENCE AT OCHIN OCHIN is a rapidly growing national nonprofit health IT organization with two decades of experience transforming health care delivery to drive health equity. 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 mission. OCHIN provides leading-edge technology, data analytics, research, and support services to more than 1000 community health care sites, reaching nearly 6 million patients nationally. We believe that every individual, no matter their race, ethnicity, background, or zip code, should have fair opportunity to achieve their full health potential. Our work addresses differences in health that are systemic, avoidable, and unjust. We partner, learn, innovate, and advocate, in order to close the gap in health for individuals and communities negatively impacted by racism or other structural inequities. At OCHIN, we value the unique perspectives and experiences of every individual and work hard to maintain a culture of belonging. Founded in Oregon in 2000, OCHIN employs a growing virtual workforce of more than 1,00 diverse 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 equitable opportunity for professional advancement. We are curious, collaborative learners who strive to live our values everyday: Learning, Heart, Belonging, and Impact. 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." Then Position Overview paragraph: "The Epic ClinDoc Application Analyst supports the mission of OCHIN by configuring and supporting clinical applications within the Epic electronic health record (EHR) software for our Acute Care member clinics. This role consults with members to provide solutions that offer accurate, secure, and efficient patient care and provider workflows, medical and billing information for patients providers and clinics, and usage of Epic front desk application and related ancillary services, with a focus on quality outcomes for our member organizations." We can combine into About the role. Responsibilities: list of Essential Duties. Let's extract each bullet (they are sentences separated by periods). We'll create
  • for each duty. List: - Perform routine build and configuration in Epic and related products - Act as Level 2 technical support for many ancillary integrated products. This entails: - Collecting and resolving issues - Coordinating with Help Desk on JIRA resolution - Helping the product owner to put together agendas for vendor calls - Representing OCHIN on vendor calls from a technical perspective - Operate alongside the Member Care Team framework, being a key contributor to the overall goals of the team support model - Serve as internal advisor to other analyst as the lead working sessions with OCHIN members to resolve advanced and complex integration work orders and support issues - Discuss and provide workflow solutions and ensure understanding of the system through hands on training - Document build specifications, team processes and complex clinic workflows - QA complex builds, Service Update (SU) modifications, and other work orders - Collaborate with members from other OCHIN teams to address integration issues - Provide elbow support to clinic staff during Go-Lives and Mock clinics as needed - Lead trainings and workgroups for members - Mentor, coach, and train less experienced analysts - Develop and share workflow best practices - Travel to support new member off-site Go Live software installations as needed. - Provide support to inpatient clinic staff with the potential need for after-hours - Assist Project Managers in identifying system capabilities - Build, design, test and document functionality of new system features - Provide process improvements within your application or team - Provide support to inpatient clinic staff with the potential need for after-hours/ on-call support - Other duties as assigned Note some duplicates: "Provide support to inpatient clinic staff with the potential need for after-hours" appears twice (once alone, once with on-call). We'll keep both as they appear; but could deduplicate? Instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Duplicates are part of posting; we should keep them? Might be okay to keep both but could be considered duplication. Safer to keep as is. Requirements: list: - Epic Certification in ClinDoc and Stork is required, as well as build experience. - Minimum of 3 years of experience in similar or relevant role - The ideal candidate will have 3-5 years of experience as an Epic Applications Analyst, with a minimum of 2 years of build experience. - Experience with full-cycle implementation build is highly desired. - Work history in Healthcare IT is required - Bachelor’s Degree preferred or a combination of college education and 5-7 years of relevant experience - Intermediate proficiency in Microsoft Excel - COVID-19 Vaccination Requirement: To keep our colleagues, members, and communities safe, OCHIN requires all employees—including remote employees, contractors, interns, and new hires—to be vaccinated with a COVID-19 vaccine, as supported by state and federal public health officials, as a condition of employment. All new hires are required to provide proof of full vaccination or receive approval for a medical or religious exemption before their hire date. We could put vaccination under Requirements or separate? It's a requirement. We'll include under Requirements. Qualifications: maybe overlapping with Requirements. But we have "Requirements Qualifications" heading. Could treat everything after that as Qualifications. But we already used Requirements. To avoid duplication, we could treat the list as Qualifications and not have separate Requirements. However the instruction allows both headings if content distinct. We have content that could be split: Requirements (experience, education, vaccination) and Qualifications (certification, build experience). But the posting lumps them together. Safer to have one section: Requirements (or Qualifications). Which heading to use? The list includes both requirements and qualifications. The instruction examples include both. We could create

    Requirements

    and put all items there. Or we could create

    Qualifications

    and put certification etc. But we need to capture all. Let's do

    Requirements

    with the list (including certification, experience, education, vaccination, Excel). Then we could omit Qualifications section to avoid duplication. Skills: we have "Intermediate proficiency in Microsoft Excel" which is a skill; could be under Skills. But we already put under Requirements. Might be better to move Excel to Skills section. Let's create Skills section with that. Pay: we have salary range. Schedule: we have remote work, travel up to 25%, work from home requirements: ability to work independently, high speed internet, distraction free workplace. Also mention "This position is 100% remote." and "Work from home requirements are: 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 required up to 25% nationally for on-site Go Live support based on business requirements for OCHIN". We'll put that under Schedule. We must not include boilerplate like EEO, etc. Also remove "See our website for details: https://ochin.org/employment-openings" (benefits link). Since we omitted Benefits, we can drop that line. Also remove "Base Pay Overview ..." we keep salary range. Now produce HTML fragment. Structure:

    About the role

    ... (combined paragraphs)

    Responsibilities

    • ...
    ...

    Requirements

    • Epic Certification in ClinDoc and Stork is required, as well as build experience.
    • Minimum of 3 years of experience in similar or relevant role
    • The ideal candidate will have 3-5 years of experience as an Epic Applications Analyst, with a minimum of 2 years of build experience.
    • Experience with full-cycle implementation build is highly desired.
    • Work history in Healthcare IT is required
    • Bachelor’s Degree preferred or a combination of college education and 5-7 years of relevant experience
    • COVID-19 Vaccination Requirement: To keep our colleagues, members, and communities safe, OCHIN requires all employees—including remote employees, contractors, interns, and new hires—to be vaccinated with a COVID-19 vaccine, as supported by state and federal public health officials, as a condition of employment. All new hires are required to provide proof of full vaccination or receive approval for a medical or religious exemption before their hire date.

    Skills

    • Intermediate proficiency in Microsoft Excel

    Pay

    Salary range: $85,697.00 to $137,116.00

    Schedule

    This position is 100% remote. Work from home requirements: ability to work independently and efficiently from a