Patient Access Center Supervisor

We need to output HTML fragment with sections: maybe "Why Join Us?" as a heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: 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") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We have content: "Why Join Us?" bullet points (list). Then "Job Description Pay Range: $62,500-$78,000". Then "Scope Providers leadership and oversight...". Then responsibilities broken into categories: Operational Management, Staff Leadership, Performance and Quality Management, Strategic Planning and Process Improvement, Patient Experience and Service Recovery, Compliance and Regulatory Oversight. Then Minimum Qualifications (list). Then Knowledge, Skills, And Abilities (list). Then Physical Demands (list). Also there is "Pay Range" given. So we should include a Pay section with that range. Also maybe Benefits? Not provided. Schedule? Not provided. So we should not create Benefits or Schedule sections. We need to decide sections: maybe "Why Join Us?" as a heading? Not in the list but could be considered a section. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Probably we should use those standard headings where applicable. "Why Join Us?" could be considered "About the role" or maybe we can just treat it as a

  or

  "Why Join Us?" but they said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we can follow that pattern: maybe we can use

  Why Join Us?

  . That seems okay. Then we have Pay Range: we can make a Pay section with

  Pay

  and

  $62,500-$78,000

  . Then Responsibilities: we have multiple subcategories. Could combine into one Responsibilities section with nested lists? The instruction: Use
  • for any list of duties/requirements/benefits. So we can have a

    Responsibilities

    then a
    with each duty as
    • . But we have categories; we could either list each bullet as separate
    • preserving the category headings inside the
    • maybe as bold? But we cannot add extra formatting beyond HTML? We could embed inside
    • . That's okay. Or we could make subheadings inside the list? Probably better to keep categories as

      inside Responsibilities? But instruction only mentions

      for section headings. It didn't forbid other heading levels, but to be safe we can keep categories as within

      . Or we could make separate sections for each category (Operational Management, Staff Leadership, etc.) but that would be many thin sections; they said prefer a few substantive sections over many thin ones. So better to combine into one Responsibilities section with a list that includes the category headings as part of the list items. Similarly for Minimum Qualifications: we can have

      Minimum Qualifications

      with a

      . Knowledge, Skills, And Abilities:

      Knowledge, Skills, and Abilities

      with
      . Physical Demands: maybe we can include under Requirements? But there is no specific section for Physical Demands in the examples. Could treat as part of Requirements or Qualifications. But we have a separate section for Physical Demands; we could make a

      Physical Demands

      with
      . That seems okay. We must not include boilerplate like EEO etc. Not present. We must preserve all substantive information. So we need to include all bullet points. Let's extract the "Why Join Us?" bullet points: - Be part of a practice at the forefront of cutting-edge cancer care and advanced treatments - Access opportunities for professional growth and continuing education. - Work alongside a collaborative and compassionate team of experts dedicated to making a difference. - Enjoy the convenience of multiple locations throughout the Capital Region. - Contribute to groundbreaking clinical trials that shape the future of oncology care. - Discover your career potential with a practice dedicated to excellence and innovation. We'll put those in a
      under

      Why Join Us?

      . Pay Range: $62,500-$78,000. Scope: "Providers leadership and oversight of Patient Access Center operations supporting patient access services across multiple oncology practice locations." That's a prose sentence; we can include as

      under maybe a "Scope" heading? Not in list but we could incorporate into Responsibilities or a brief overview. Since they said use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). "Scope" could be considered part of About the role. But we already have Why Join Us. Maybe we can treat the scope as part of Responsibilities overview. But we need to preserve it. Could add a

      after Why Join Us before Responsibilities: "Scope: Provides leadership and oversight of Patient Access Center operations supporting patient access services across multiple oncology practice locations." That seems fine. Now Responsibilities categories and bullet points: Operational Management: - Direct and oversee daily Patient Access Center operations, including workload distribution, staffing coverage, workflow management, and achievement of departmental service and quality goals. - Monitor call volumes, queue activity, operational trends, and patient access workflows to support efficient service delivery. - Identify operational challenges and implement solutions to improve productivity, service levels, and workflow effectiveness. Staff Leadership: - Recruit, hire, onboard, train, and develop Patient Access Center Staff. - Conduct performance evaluations, coaching sessions, corrective action, and employee development activities. - Manage staffing plans, scheduling, attendance, and employee engagement initiatives. - Facilitate team communication, departmental meetings, and dissemination of operational, workflow, and organizational updates. Performance and Quality Management: - Develop, monitor, analyze, and communicate departmental performance indicators including service levels, productivity, quality measures, first-call resolution, patient experience, and other operational metrics. - Conduct quality reviews and audits, identify performance trends, and implement coaching, training, or corrective action plans when necessary to ensure compliance with established standards. - Develop and maintain operational reports and communicate departmental performance results, priorities, and improvements to leadership. Strategic Planning and Process Improvement: - Develop, implement, and maintain departmental workflows, policies, procedures and service standards. - Lead process improvement initiatives and support technology implementation and optimization efforts that enhance patient access operations. - Collaborate with clinical, operational, and administrative leaders to support organizational access initiatives and growth strategies. Patient Experience and Service Recovery: - Oversee resolution of complex patient, caregiver, provider, and service-related concerns including service recovery efforts and escalated patient access issues. - Promote a culture of compassionate, patient-centered customer service and continuous improvement. Compliance and Regulatory Oversight: - Ensure compliance with HIPAA, regulatory requirements, organizational policies, and established workflows. - Maintain departmental policies, competency programs, quality standards, and staff compliance with required training and certifications. - Supports and adheres to the New York Oncology Hematology Compliance Program, to include the Code of Ethics and Business Standards. We'll put all these as

      items, maybe with the category headings as inside each

      or we could separate categories with

      but that might be many sections. To keep few sections, we can embed categories as within

      . Eg:

      Operational Management: Direct and oversee ...

      . That preserves the info. Minimum Qualifications: - Associates Degree required. - Bachelor’s Degree in Healthcare Administration, Business Administration, or related field preferred. - Five years healthcare patient access, scheduling, or healthcare contact center experience. - Two years supervisory or leadership experience preferred. - Oncology experience strongly preferred. Knowledge, Skills, And Abilities: - Knowledge of healthcare contact center operations - Strong leadership and employee development skills - Workforce management experience - Data analysis and performance management skills - Change management and process improvement capabilities Physical Demands: - Requires sitting for long periods of time. - Some bending and stretching required. - Adequate finger dexterity and feeling to perform keyboarding and substantial repetitive motions involving the wrists, hands and/or fingers. - Requires vision and hearing corrected to normal range. - Must be able to view computer screen and printed material accurately. - Occasionally lifts and carries items weighing up to 40 lbs. - Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions. (This is a sentence; we can include as

      .) We need to ensure we don't include boilerplate like "Reasonable accommodations may be made..." It's part of Physical Demands; it's substantive, keep. Now output HTML fragment: no or . Just the sections. We'll order: Why Join Us?, Scope (maybe as a

      ), Pay, Responsibilities, Minimum Qualifications, Knowledge, Skills, and Abilities, Physical Demands. Check for any duplicated lines: none. Make sure not to include any filler like "commensurate with experience". Not present. Now craft HTML. We'll use

      for each section heading. Inside sections, use

      • for lists,

        for prose. For Why Join Us:

        Why Join Us?

        ...
        Pay:

        Pay

        $62,500-$78,000

        Scope: maybe

        Scope

        Provides leadership and oversight of Patient Access Center operations supporting patient access services across multiple oncology practice locations.

        But Scope is not in the list of headings examples but it's okay. Could also incorporate into Responsibilities overview. But we have a separate Responsibilities section; we could put scope as a

        before the Responsibilities list. However the instruction: "include a section ONLY when the posting has real, specific content for it". Scope is specific content, so we can make a section. But they gave examples of section headings; Scope is not listed but we can still use

        Scope

        . It's not prohibited. Alternatively we could avoid extra section and put scope as a

        under Why Join Us? or Responsibilities. But to keep few sections, maybe we incorporate scope into Responsibilities as an introductory

        before the list. That would keep sections fewer. Let's do that: Under Responsibilities, first a

        scope, then

        of duties. Thus sections: Why Join Us?, Pay, Responsibilities (with scope paragraph then list), Minimum Qualifications, Knowledge, Skills, and Abilities, Physical Demands. Now craft. Responsibilities:

        Responsibilities

        Provides leadership and oversight of Patient Access Center operations supporting patient access services across