DirectJobHub
Jobs · Healthcare · South Carolina

Advanced Practice Provider (APP)

Lowcountry Oncology Associates · North Charleston, SC · 3 wk ago
HealthcareFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Preserve all substantive info. We need to parse the posting. Content: - Mission statement: "Lowcountry Oncology Associates mission is delivering high-quality and compassionate cancer care in our community, for our community and by oncologist who in live in our community." Might be considered part of About the practice? Could be included in About the role? Probably not needed as separate heading; but we can include in About the role or About the practice? There's no explicit "About the practice" heading but we could include under About the role? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule if content exists. We need to extract: About the role: The paragraph after "About The Role" includes description: "Lowcountry Oncology Associates is seeking a dedicated and compassionate Advanced Practice Provider to join our Hematology/Oncology team in Charleston, South Carolina. In this role, you will provide patient-centered care through evaluations, follow-up visits, and treatment planning in close collaboration with experienced physicians in the outpatient clinic setting. You will work in a supportive, team-oriented environment that values clinical excellence and strong patient relationships. As part of a private practice committed to comprehensive cancer care, you will play an important role in guiding patients through every stage of their treatment with professionalism and empathy." That's substantive. Responsibilities: Not explicitly listed but we could infer from description: evaluations, follow-up visits, treatment planning, collaborate with physicians, guide patients through treatment. Could be considered responsibilities. However we need to ensure we don't invent. The posting does not have a separate "Responsibilities" heading but we can create a Responsibilities section if we can pull duties from the description. The instruction: "Use
  • for any list of duties/requirements/benefits". If we don't have explicit list, we could still create a
      with items derived from the prose? Might be considered summarizing. Safer to only include sections where there is explicit list. The posting does not have bullet list of responsibilities. It has prose. We could still put prose in

      under Responsibilities? But the instruction says use

      for prose. So we could have a Responsibilities section with a

      containing the duties described. However we must not create a section if posting lacks real specific content for it. The posting does have description of role which could be considered responsibilities. It's specific enough. So we can include Responsibilities with a

      summarizing the duties (but we must not invent or summarize away detail). We can copy the sentences directly. Similarly Requirements: The posting includes "Ideal Candidate Experienced APPs preferred; New Grads encouraged to apply Hematology/Oncology experience as RN or APP preferred". Also "Board Certifications: NP-C/PA-C". Also "Occupation: Nurse Practitioner or Physician Assistant Specialty: Hematology/Oncology". Also "Employment: Full-Time | Mon-Fri Setting: Private Practice, Outpatient". Those could be requirements/qualifications. Qualifications: Could include board certifications, experience preferences. Skills: Not explicitly listed. Benefits: Under "Recruitment Package" we have bullet-like list: "Top-Tier Compensation – Highly competitive compensation structures Comprehensive Benefits – Medical, Dental, Vision, Disability, Life Retirement Plan – Secure your future, 401k match Work-Life Balance – Paid time off Professional Growth – CME days and reimbursement Community Care – Make a real difference by caring for patients in their local communities". That's benefits. Pay: Not explicitly stated; only "Top-Tier Compensation – Highly competitive compensation structures". That's vague; not a specific number. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. For Pay, we have only "Highly competitive compensation structures" which is vague but still mentions compensation. Is that considered stating Pay? It says "Top-Tier Compensation – Highly competitive compensation structures". That's a statement about compensation but not a specific figure. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state compensation, albeit vague. I'd argue we can include Pay section with that statement. However they also say "Prefer a few substantive sections over many thin ones." Might be better to combine Pay into Benefits? But they are separate headings. Since we have Benefits section already, we could include Pay as a subsection? But instruction says use those headings. We could include Pay with a

      stating "Highly competitive compensation structures". That's not invented. Schedule: The posting includes "Employment: Full-Time | Mon-Fri". That's schedule. So we can include Schedule section. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Possibly Skills if any; none. We must not repeat job title as heading. No Job ID. We must remove boilerplate: mission statement, "Why Join Us?" etc. Also "About Charleston, SC" maybe not needed as a heading; but it's substantive about location. Could be included under About the role or maybe as a separate section? Not in allowed headings. Could be included in About the role as extra paragraph. But we already have About the role; we could add a paragraph about Charleston. However the About the role section currently is about role description. Adding location might be okay but could be considered not strictly role. However we can keep it as part of About the role or maybe we could create a separate section like "Location" but not allowed. So we can incorporate location into About the role or maybe into Responsibilities? Better to add a paragraph after role description about Charleston. But we must preserve all substantive information. So we need to include Charleston description somewhere. Could add a separate section "About Charleston, SC" but not allowed heading. So we could add a

      under About the role after the role description. Similarly "About The Practice" and partnership with OneOncology etc. That's substantive. Could be included under About the role or maybe a separate section "About the practice". Not allowed heading but we could incorporate into About the role as well. However that may be too much mixing. But we need to preserve all info. We could add a section "About the practice" but not allowed heading; maybe we can treat it as part of About the role? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections; but we could also add other headings if needed? The instruction: "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive list. However later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could add other headings if needed, but better to stick to given ones to avoid extra. Thus we need to fit all substantive info into those sections. Let's map: - About the role: role description (including mission? maybe not). Could also include "Why Join Us?" values? That's about culture. Could be part of About the role. - Responsibilities: duties (evaluations, follow-up visits, treatment planning, collaborate with physicians, guide patients). - Requirements: maybe "Board Certifications: NP-C/PA-C", "Occupation: Nurse Practitioner or Physician Assistant Specialty: Hematology/Oncology", "Employment: Full-Time | Mon-Fri". Also "Ideal Candidate Experienced APPs preferred; New Grads encouraged to apply". Could be requirements. - Qualifications: maybe "Hematology/Oncology experience as RN or APP preferred". Also "Experienced APPs preferred; New Grads encouraged to apply". Could be qualifications. But there is overlap. We need to avoid duplication. Let's think: Requirements often are mandatory; Qualifications are preferred. The posting says "Board Certifications: NP-C/PA-C" (mandatory). "Occupation: Nurse Practitioner or Physician Assistant Specialty: Hematology/Oncology" (role). "Employment: Full-Time | Mon-Fri Setting: Private Practice, Outpatient" (schedule). "Ideal Candidate Experienced APPs preferred; New Grads encouraged to apply" (preference). "Hematology/Oncology experience as RN or APP preferred" (preference). So we can put mandatory in Requirements, preferred in Qualifications. Benefits: as listed. Pay: "Top-Tier Compensation – Highly competitive compensation structures". Could be a brief statement. Schedule: "Full-Time | Mon-Fri". Already maybe in Requirements but we can also put in Schedule. We must not duplicate content. Let's decide to put schedule in Schedule section only, and not repeat in Requirements. Thus Requirements: Board Certifications NP-C/PA-C, Occupation: Nurse Practitioner or Physician Assistant Specialty: Hematology/Oncology. Qualifications: Experienced APPs preferred; New Grads encouraged to apply; Hematology/Oncology experience as RN or APP preferred. Benefits: list items. Pay: Highly competitive compensation structures. Schedule: Full-Time, Mon-Fri. About the role: include role description, mission statement? The mission statement is about the organization; could be included in About the role or maybe we could add a short paragraph about mission. But we already have About the Practice section? Not allowed. Could incorporate mission into About the role as introductory sentence. Also include "Why Join Us? Our team values the work components of every member to create a culture of people helping people and making a difference in our lives and those we serve." That's culture; could be part of About the role. Also include Charleston description and practice description and OneOncology partnership. That's a lot; maybe we can put them in About the role as additional paragraphs. But we must avoid making the section too thin? It's okay. Thus About the role will contain multiple paragraphs: mission, why join us, role description, Charleston info, practice info, OneOncology partnership. We must ensure we don't include boilerplate like "If you would like to apply or learn more about this opportunity, please email your CV to ..." That's application instructions; remove. Also remove "Lowcountry Oncology Associates is proud to partner with OneOncology..." Actually that's substantive about partnership; we can keep. Now produce HTML:

      About the role

      ...

      Responsibilities

      • ...
        • ...

      Requirements

      • ...
        • ...

      Qualifications

      • ...
        • ...

      Benefits

      • ...
        • ...

      Pay

      Highly competitive compensation structures

      Schedule

      Full-Time, Monday–Friday

      We need to ensure we use correct punctuation: en dash? Use hyphen. Now extract exact phrasing to preserve. Mission: "Lowcountry Oncology Associates mission is delivering high-quality and compassionate cancer care in our community, for our community and by oncologist who in live in our community."

Similar jobs