Revenue Cycle Process Improvement Analyst, Full Time- Days

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. Must not repeat job title. 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 remove "About Us" maybe? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The "About Us"About Us" paragraph is not boilerplate? It's about the organization, but could be considered not required? It's not a required section heading; we could include it under "About the role"? The job description includes a paragraph about being part of world-class academic healthcare system. That's like an intro. Could be placed under "About the role". Also there is "Compensation & Benefits Overview" which includes pay range statement but not actual numbers. It says "The pay range provided reflects the anticipated wage..." but no actual numbers given. Since we should not create Pay/Schedule/Benefits sections unless posting actually states them. It does mention compensation overview but no specific numbers; it's vague. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Since they didn't give actual numbers, we should not create Pay section. Benefits: they mention "Review the full complement of benefit options for eligible roles at Benefits - UChicago Medicine." That's a link but no specifics. So we should not create Benefits section unless specific benefits listed. So we omit Benefits and Pay and Schedule unless schedule given: they gave Shift: Days, Monday-Friday, Work Location: Flexible Remote (Will need to commit to being onsite when needed). That's schedule info. So we can include Schedule section with that info. Also Job Type/FTE: Full Time (1.0 FTE) could be part of Schedule or maybe a separate section? But we only have Schedule heading allowed. Could include schedule details there. Now we need sections: About the role (intro), Responsibilities (essential functions?), Requirements (maybe combine with Qualifications?), Qualifications (maybe separate), Skills (maybe list of skills). The posting has "Essential Functions" which is a list of qualifications repeated. Then "Required Qualifications" repeats same list. Then there is a list of skills after that. So we need to parse. We must not duplicate content. We need to preserve all substantive info, but avoid duplication. So we need to combine similar info. Let's extract substantive content: Intro: "Be a part of a world-class academic healthcare system, UChicago Medicine, as a Revenue Cycle Process Improvement Analyst. This position demands exceptional leadership, collaboration, and stakeholder engagement capabilities to effectively align cross-functional teams—including IT, clinical departments, and administrative units in addressing complex challenges. Leveraging advanced analytics, system optimization, and process improvement methodologies, the role will deliver measurable financial and operational outcomes. Operating with a high degree of autonomy, this role is accountable for identifying opportunities to improve hospital revenue cycle and collaborating with cross-functional teams to implement effective, sustainable solutions. The scope of this role encompasses the full continuum of the revenue cycle, from patient scheduling through final payment. The primary objective is to accelerate cash flow while minimizing errors and inefficiency." That's about the role. Essential Functions (list): - 3+ years of progressive experience in healthcare revenue cycle, preferably within a large or complex health system. - Bachelor’s degree preferred. - 2+ years of experience in process improvement, quality assurance, analytics, or a similar role - 2+ years of Epic experience required in a leadership or analyst role - Experience conducting root cause analysis required - Experience across key functions including billing, coding, claims management, denials, accounts receivable, and charge capture - Understanding of CPT, ICD-10, HCPCS coding standards, clearinghouses, and payer portals - Advanced proficiency with Excel and data analysis Required Qualifications (same list). So we can just present once as Requirements or Qualifications. Then after that there is a list of skills/attributes: - CRCR (Certified Revenue Cycle Representative) – required or must be obtained within 3–6 months - Project Management certification (PMP, CAPM) preferred - Epic Certification preferred - Optional: CPC, CPB, or CCS for coding/billing expertise - Strong analytical and critical thinking skills with the ability to break down complex problems - Experience with sampling techniques and data analysis to identify patterns and anomalies - Ability to develop, test, and validate hypotheses using both quantitative and qualitative methods - Excellent attention to detail and ability to identify subtle inconsistencies or trends - Strong organizational and documentation skills - Facilitation and presentation skills - Self-motivation with ability to work independently with minimal guidance and manage multiple priorities - Excellent written and verbal communication skills, including ability to positively interact with executives, physicians and staff at all levels - Microsoft Office proficiencies, especially fluent with PowerPoint, Excel, and Word - Ability to quickly learn proprietary data systems and sources Then Position Details: - Job Type/FTE: Full Time (1.0 FTE) - Shift: Days, Monday-Friday - Unit/Department: Revenue Cycle - Work Location: Flexible Remote (Will need to commit to being onsite when needed) - CBA Code: Non-union We can put Schedule section with Shift and Work Location maybe. Also Job Type/FTE could be included there. We should not include Unit/Department maybe as part of About the role? Could be included in About the role? But we can keep as a separate section? Not among allowed headings. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these. We have About the role (intro). Responsibilities: maybe we can list the core duties: aligning cross-functional teams, leveraging analytics, identifying opportunities, implementing solutions, scope full continuum, accelerate cash flow, minimize errors. That's from intro. Could be responsibilities. Requirements: maybe the experience/education list (3+ years, Bachelor's preferred, etc.) Could be Requirements. Qualifications: maybe certifications (CRCR required, PMP preferred, Epic Cert preferred, optional coding certs). Could be Qualifications. Skills: the list of soft/technical skills (analytical, attention to detail, organizational, facilitation, self-motivation, communication, MS Office, ability to learn proprietary systems). Could be Skills. Schedule: shift, work location, job type. We must not repeat same info across sections. Ensure we don't duplicate. Let's craft. About the role: include the intro paragraph about being part of world-class academic healthcare system, demands leadership, etc., scope, objective. Responsibilities: bullet list of duties: aligning cross-functional teams (IT, clinical, admin), leveraging advanced analytics, system optimization, process improvement methodologies to deliver measurable financial/operational outcomes, identifying opportunities to improve hospital revenue cycle, collaborating with cross-functional teams to implement effective sustainable solutions, scope full continuum of revenue cycle (patient scheduling to final payment), primary objective accelerate cash flow while minimizing errors and inefficiency. Requirements: bullet list: 3+ years progressive experience in healthcare revenue cycle preferably large/complex health system; Bachelor’s degree preferred; 2+ years experience in process improvement, quality assurance, analytics, or similar role; 2+ years Epic experience required in leadership/analyst role; experience conducting root cause analysis required; experience across key functions including billing, coding, claims management, denials, accounts receivable, charge capture; understanding of CPT, ICD-10, HCPCS coding standards, clearinghouses, payer portals; advanced proficiency with Excel and data analysis. Qualifications: bullet list: CRCR (Certified Revenue Cycle Representative) – required or must be obtained within 3–6 months; Project Management certification (PMP, CAPM) preferred; Epic Certification preferred; Optional: CPC, CPB, or CCS for coding/billing expertise. Skills: bullet list: Strong analytical and critical thinking skills with ability to break down complex problems; Experience with sampling techniques and data analysis to identify patterns and anomalies; Ability to develop, test, and validate hypotheses using both quantitative and qualitative methods; Excellent attention to detail and ability to identify subtle inconsistencies or trends; Strong organizational and documentation skills; Facilitation and presentation skills; Self-motivation with ability to work independently with minimal guidance and manage multiple priorities; Excellent written and verbal communication skills, including ability to positively interact with executives, physicians and staff at all levels; Microsoft Office proficiencies, especially fluent with PowerPoint, Excel, and Word; Ability to quickly learn proprietary data systems and sources. Schedule: bullet list: Job Type/FTE: Full Time (1.0 FTE); Shift: Days, Monday-Friday; Work Location: Flexible Remote (Will need to commit to being onsite when needed); CBA Code: Non-union (maybe include). Could also include Unit/Department: Revenue Cycle but that's maybe not schedule; but we could include as part of schedule? It's not schedule but we have no other heading. Could we add a separate section like "About the role" already includes unit? Not needed. Might be okay to include Unit/Department under Schedule as extra detail. Or we could omit it as not required. The instruction: preserve ALL substantive information. So we need to keep Unit/Department: Revenue Cycle and CBA Code: Non-union. Where to put? Could add a short paragraph under About the role? But that's about the role, not unit. Could add a separate section? Not allowed headings. Could we add a

after Schedule? The instruction: Output ONLY the HTML fragment. It didn't forbid extra paragraphs not under headings? It says use

for section headings,

• for any list,

  for prose. So we can have prose paragraphs outside of sections? Probably we should keep everything within sections. But we could add a

  under Schedule for extra info like Unit/Department and CBA Code. However Schedule heading expects list; we could still have a

  after the list within the same section? Might be okay but better to keep within

  • . We could add list items for Unit/Department and CBA Code under Schedule. Thus Schedule
    • Job Type/FTE: Full Time (1.0 FTE)
    • Shift: Days, Monday-Friday
    • Work Location: Flexible Remote (Will need to commit to being onsite when needed)
    • Unit/Department: Revenue Cycle
    • CBA Code: Non-union
    Now ensure no duplication: we didn't repeat the experience list elsewhere. We have Requirements list includes those. Qualifications list includes certifications. Skills list includes abilities. Good. We must not include Benefits, Pay sections because no specific info. Now produce HTML fragment: start with

    About the role

    then

    ...

    . Then

    Responsibilities

    ... etc. Make sure to not include any markdown fences. Let's craft the prose for About the role: combine the intro sentences into a paragraph. Paragraph: "Be a part of a world-class academic healthcare system, UChicago Medicine, as a Revenue Cycle Process Improvement Analyst. This position demands exceptional leadership, collaboration, and stakeholder engagement capabilities to effectively align cross‑functional teams—including IT, clinical departments, and administrative units—in addressing complex challenges. Leveraging advanced analytics, system optimization, and process improvement methodologies, the role will deliver measurable financial and operational outcomes. Operating with a high degree of autonomy, this role is accountable for identifying opportunities to improve hospital revenue cycle and collaborating with cross‑functional teams to implement effective, sustainable solutions. The scope of this role encompasses the full continuum of the revenue cycle, from patient scheduling through final payment. The primary objective is to accelerate cash flow while minimizing errors and inefficiency." Now Responsibilities list: we can bullet each duty. - Align cross‑functional teams (IT, clinical