Advanced Practice Provider - NP/PA

We need to output HTML fragment with sections: About the role? The posting includes a paragraph about CVS Health mission, then "This is a full-time, full-time, float provider role Anderson, SC covering clinics within a 50 mile radius. This provider will work every other weekend and 30-40 hours/week." That could be "About the role" or "Position Summary". Then there is a "Position Summary" heading in the text. Then "What Our Providers Enjoy" (benefits). Then "In This Role, You Will" (responsibilities). Then "Required Qualifications" (with subparts for NPs and PAs). Then "Education Requirements". Then "Preferred Qualifications". Then "Pay Range". Then "Great Benefits For Great People" (benefits). Also there is schedule info: "full-time, float provider role ... work every other weekend and 30-40 hours/week." That's schedule. We must not repeat job title as heading. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have content for: - About the role: mission statement, location, schedule? Could be. - Responsibilities: "In This Role, You Will" list. - Requirements: maybe combine Required Qualifications and Education Requirements? The spec says use headings: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: - Requirements: maybe Required Qualifications (NPs/PAs) and Education Requirements. - Qualifications: maybe Preferred Qualifications. - Skills: maybe not explicit; could be omitted if no specific skill list. - Benefits: "What Our Providers Enjoy" and "Great Benefits For Great People". Could combine. - Pay: Pay Range. - Schedule: mention full-time, every other weekend, 30-40 hrs/week. We must not create sections with filler like "commensurate with experience". Ensure we have real content. We need to use

• for any list of duties/requirements/benefits. Use

  for prose. We must strip boilerplate: cookie/navigation/legal/EEO etc. At end there is "Qualified applicants with arrest or conviction records will be considered..." that's EEO; remove. Also "We anticipate the application window..." remove. Also "Our people fuel our future..." maybe part of benefits? It's generic; could be considered boilerplate; but it's about culture; maybe keep as part of About the role? It's not specific to role; but it's not boilerplate like EEO. Might keep as part of About the role. We need to preserve all substantive information. So we need to include mission statement, location, schedule, position summary, what providers enjoy, responsibilities, required qualifications (NPs and PAs), education requirements, preferred qualifications, pay range, benefits. We must not repeat job title as heading. No Job ID. We'll output HTML fragment. Structure:

  About the role

  We’re building a world of health around every individual — shaping a more connected, convenient and compassionate health experience. At CVS Health®, you’ll be surrounded by passionate colleagues who care deeply, innovate with purpose, hold ourselves accountable and prioritize safety and quality in everything we do. Join us and be part of something bigger – helping to simplify health care one person, one family and one community at a time. This is a full-time, float provider role in Anderson, SC covering clinics within a 50‑mile radius. The provider will work every other weekend and 30‑40 hours per week.

  Position Summary

  maybe we can treat as About the role? But spec says use headings like About the role, Responsibilities, etc. Position Summary could be considered About the role. We already have About the role. Could rename that section to About the role and include position summary there. Or we could have both About the role and Position Summary but spec only lists certain headings; but we can still use other headings? The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, not exclusive. But they say "Prefer a few substantive sections over many thin ones." So we can use those headings; we can also use others if needed but better to stick to those. Thus we need to map content to those headings. Let's decide: - About the role: mission, location, schedule, maybe position summary. - Responsibilities: "In This Role, You Will" list. - Requirements: Required Qualifications (NPs/PAs) + Education Requirements? Could be. - Qualifications: Preferred Qualifications. - Skills: maybe not needed; we could omit if no specific skill list. - Benefits: "What Our Providers Enjoy" + "Great Benefits For Great People". - Pay: Pay Range. - Schedule: maybe we already included schedule in About the role; but we could also have separate Schedule section with details: full-time, every other weekend, 30-40 hrs/week. However we already included schedule in About the role; but we could still have Schedule section with that detail; but that would duplicate. Better to put schedule in About the role and not create separate Schedule section if we already covered. But spec says include a section ONLY when posting has real, specific content for it. So we can include Schedule if we have specific content not already covered elsewhere. Since we placed schedule in About the role, we could still have Schedule section but that would be duplicate; better to not duplicate. So we can omit Schedule section and keep schedule in About the role. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We need to ensure we use

  • for any list. Let's extract lists: Responsibilities list: - Deliver evidence‑based primary and family care, including assessment, diagnosis, treatment, and management of acute and chronic conditions - Provide both in-person and virtual visits (from the clinic) to support positive patient health outcomes - Perform diagnostic testing, preventive counseling, treatment of injuries and illnesses, and coordination of care with other healthcare professionals - Engage patients in wellness services, chronic disease management, and preventive health screenings - Complete essential clinic operations including inventory management, clinic opening/closing, patient follow‑up, insurance verification, and payment collection - Support a safe and efficient care environment through routine examinations and timely patient appointment management That's a list. Required Qualifications: two subcategories: For Nurse Practitioners (NPs) and For Physician Associates (PAs). Each has bullet points. We could make a
    with
    • for each bullet, maybe grouping. But we need to preserve all info. We'll list them. Education Requirements: separate list for NPs and PAs. Preferred Qualifications: list. Benefits: "What Our Providers Enjoy" list (autonomy, flexible scheduling, tools, etc.) plus "Great Benefits For Great People" list (medical, dental, vision, PTO, retirement, wellness programs). We'll combine. Pay: just a paragraph. Now we need to avoid boilerplate: remove lines like "Our people fuel our future..." maybe keep as part of About the role? It's generic but not boilerplate; but we can keep. Also remove "Qualified applicants with arrest or conviction records will be considered..." and "We anticipate the application window..." etc. Now craft HTML. We'll start with

      About the role

      then

      ... mission ... location schedule ...

      Then

      Responsibilities

      then
      • ... each responsibility
      Then

      Requirements

      then maybe

      Nurse Practitioners (NPs)

      but we cannot use

      ? Not prohibited but spec only mentions h3 for section headings. Using h4 might be okay but better to keep within h3 sections only. Could embed headings as inside

      ? But we need to preserve structure. Could use

      with
      • that contain subheadings as . That's acceptable. Thus under Requirements we can have:
        • Nurse Practitioners (NPs)
          • One year of NP experience preferred; qualified new graduates may be considered
          • Active, unrestricted Family Nurse Practitioner (FNP) license in good standing
          • Ability to provide holistic, evidence‑based care including counseling related to pregnancy prevention, STI prevention, and safer sex practices
          • Ability to order/administer vaccines and injections (COVID‑19, influenza, TB testing, Depo‑Provera, etc.)
          • DOT certification exam completed within 30 days of employment
          • Bilingual proficiency may be required depending on market needs
          • Active Basic Life Support (BLS) certification
          • Ability to pass a respirator FIT test
          • Physical presence at assigned clinic required
          • Must be able to obtain and maintain multi‑state licensure, based on business needs
          • Physical Requirements: Ability to perform duties involving prolonged standing, walking, bending, and reaching; Ability to perform Basic Life Support
        • Physician Associates (PAs)
          • 2 years of PA experience preferred
          • Master of Science in Physician Assistant/Associate Studies, or health‑related master’s degree plus Bachelor of Science in PA Studies
          • Current NCCPA certification
          • Active, unrestricted state PA/Physician Associate license (or eligibility to obtain upon hire)
          • Ability to provide holistic, evidence‑based care including counseling related to pregnancy prevention, STI prevention, and safer sex practices
          • DOT certification exam completed within 30 days of employment
          • Active BLS certification
          • Ability to pass a respirator FIT test
          • Physical presence at assigned clinic required
          • Must be able to obtain and maintain multi‑state licensure, based on business needs
          • Physical Requirements: Ability to perform duties involving prolonged standing, walking, bending, and reaching; Ability to perform Basic Life Support
        Then Education Requirements: Could be under Requirements as well, but we already used Requirements for qualifications. Maybe we need separate Education Requirements section? But spec only lists Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Could put Education under Requirements as well. But we already used Requirements for qualifications; we could combine qualifications and education under Requirements. However we also have a Qualifications section for Preferred Qualifications. So we can put Required Qualifications + Education under Requirements. That's okay. Thus under Requirements we will include both the NP/PA required qualifications and education requirements. Education Requirements list: - Nurse Practitioners: Master’s degree from an accredited Family Nurse Practitioner program; Current national board certification (AANP or ANCC); Active, unrestricted state APRN license. - Physician Associates: Master of Science in Physician Assistant/Associate Studies OR health‑related master’s degree plus Bachelor of Science in PA Studies; Current NCCPA certification; Active, unrestricted state PA license. We'll add as
      • Education Requirements ...
      maybe. Then Qualifications section for Preferred Qualifications:
      • Experience with the EPIC electronic health record
      • Prior MinuteClinic precepting rotation (if less than one year of provider experience; preferred but not required)
      • Experience conducting patient assessments and exercising sound clinical decision‑making in a virtual care environment
      • Familiarity with digital health tools and virtual communication technologies
      Benefits section: combine "What Our Providers Enjoy" and "Great