Orthopedic APP Clinical Fellowship (Non-Accredited)

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. We need to parse the posting. Key info: - Title: Genesis Orthopedic APP Clinical Fellowship (not needed as heading) - Overview: description. - The Opportunity: description of responsibilities. - What You'll Build Competency in: list of duties (clinic, hospital, OR). This is responsibilities. - Who This is For: qualifications/requirements (graduated, BC/board-eligible, licensed in Illinois or getting there, coachable, comfortable with complexity, cares about patients). - The Structure: Duration, Schedule, Rotations, Locations, Completion (permanent role + salary increase). - Compensation & Benefits: Competitive salary during training year, Healthcare plan, Paid time off, CME allowance, Malpractice coverage, Structured mentorship and skills development curriculum, Guaranteed permanent APP role and salary increase upon completion. - About Genesis: description of organization (maybe not needed as a section? Could be About the role? Actually "About Genesis" could be "About the role"? But we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map. We need to avoid repeating job title as heading. No Job ID etc. We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to output only HTML fragment. We need to use

for section headings. Use

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

  for prose. We need to include sections only when posting has real specific content. Let's decide sections: - About the role: could include overview description: "The Genesis Orthopedic APP Clinical Fellowship is a 12-month, full-time, paid training year designed from scratch for new graduates who are serious about orthopedics..." That's about the role. - Responsibilities: list of duties: clinic, hospital, OR tasks. - Requirements / Qualifications: maybe combine? We have "Who This is For" includes graduation, BC/board-eligible, licensed in Illinois or getting there, coachable, comfortable with complexity, cares about patients. Could be Requirements. - Skills: maybe not explicitly listed; but we could infer aptitude, drive, willingness to be coached. Could be Skills. - Benefits: list from Compensation & Benefits. - Pay: mention competitive salary during training year, plus guaranteed permanent role and salary increase upon completion. Could be Pay. - Schedule: Monday–Friday with rotating weekend call coverage. We need to avoid filler like "commensurate with experience". Not present. We must not invent details. Let's extract specifics. About the role paragraph: "The Genesis Orthopedic APP Clinical Fellowship is a 12-month, full-time, paid training year designed from scratch for new graduates who are serious about orthopedics and ready to do the work to get there. No prior ortho experience required. What we need is the aptitude, the drive, and the willingness to be coached hard by people who know this specialty inside and out. By the end, you'll be ready to practice independently. And you'll already have the job." That's good. Responsibilities: The Opportunity paragraph plus What You'll Build Competency in list. Opportunity: "From day one, you're embedded across the full continuum of orthopedic care — clinic, hospital, and OR — with responsibility that grows as your competency does. You'll have structured mentorship from Genesis surgeons and senior APPs, progressive autonomy as you earn it, and a clear runway to a permanent role within the practice when the year is done. Twelve months. Real patients. Real procedures. Real orthopedics." What You'll Build Competency in: list bullet points: - Clinic - Independent orthopedic evaluations and treatment planning - Fracture and acute injury management - Post-op visits and wound care - Injections, splinting, casting, and in-office procedures - Imaging review and clinical decision-making - Hospital - Daily inpatient rounding - ED and floor consults - Orders, documentation, and discharge planning - Serving as the liaison between surgeons and hospital teams - Operating Room - Surgical first assist - Pre- and post-operative care coordination - Progressive OR responsibility as skills develop We can format as

  • with sub-items maybe nested
    . But requirement: use
    • for any list of duties/requirements/benefits. Could nest. We'll produce a flat list maybe with headings inside li? Simpler: each bullet as
    • . Could include sub-bullets as nested
      . Requirements/Qualifications: "Who This is For" paragraph: "You just graduated — or you're about to. You're BC or board-eligible. You're licensed in Illinois or getting there. And you've known for a while that orthopedics is where you want to be. You're coachable. This year will move fast and push hard. The APPs who get the most out of it are the ones who stay hungry, ask good questions, and don't confuse confidence with competence. You're comfortable with complexity. Clinic to hospital to OR, sometimes in the same day. Multiple sites, rotating schedules, real call coverage. If that sounds like a lot — it is. If it sounds like exactly what you've been waiting for — keep reading. You care about who you're treating. Genesis serves Medicaid patients, underinsured patients, and patients who had no real options before they found us. The clinical training here is exceptional. So is the reason it matters." We can extract requirements: graduated or about to graduate, BC or board-eligible, licensed in Illinois or getting there, coachable, comfortable with complexity, cares about underserved patients (maybe not a requirement but a value). We'll list as requirements. Skills: aptitude, drive, willingness to be coached hard, stay hungry, ask good questions, not confuse confidence with competence. Could be skills. But we might combine skills into Requirements section. However we have separate headings for Skills. Could create Skills section with those. Benefits: list from Compensation & Benefits: - Competitive salary during the training year - Healthcare plan - Paid time off - CME allowance - Malpractice coverage - Structured mentorship and skills development curriculum - Guaranteed permanent APP role and salary increase upon completion Also later Benefits section: "Competitive salary package with potential for pay escalation via performance/productivity bonus 401(k) 401(k) matching Continuing education funds Disability insurance Flexible schedule Health insurance License reimbursement Life insurance Paid time off Professional development opportunities" We need to preserve ALL substantive information; do not invent or summarize away detail. So we must include all those benefits. Thus Benefits section should include: - Competitive salary during the training year - Healthcare plan - Paid time off - CME allowance - Malpractice coverage - Structured mentorship and skills development curriculum - Guaranteed permanent APP role and salary increase upon completion - Competitive salary package with potential for pay escalation via performance/productivity bonus - 401(k) - 401(k) matching - Continuing education funds - Disability insurance - Flexible schedule - Health insurance - License reimbursement - Life insurance - Paid time off (duplicate? Already have) - Professional development opportunities We should avoid duplicate lines? The instruction: remove duplicated lines. So we need to deduplicate. Paid time off appears twice; we should include once. Also Competitive salary appears twice: "Competitive salary during the training year" and "Competitive salary package with potential for pay escalation via performance/productivity bonus". They are distinct; we keep both. Pay section: maybe we can include salary details. But we already have Benefits includes salary. However we have a separate Pay heading allowed. Could put salary info under Pay. But we must not duplicate. Let's decide: Use Pay for salary details, Benefits for other benefits. Pay: Competitive salary during the training year; Competitive salary package with potential for pay escalation via performance/productivity bonus; Guaranteed permanent APP role and salary increase upon completion (maybe that's more outcome). But we could keep that under Benefits. Schedule: Monday–Friday with rotating weekend call coverage (mentorship support on call). Also rotations across multiple sites. We could include Schedule section with that. Now About Genesis: description of organization. Could be About the role? But we already have About the role. Could add another section like About the organization but not in allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should fit content into those. About Genesis description could go under About the role (maybe as extra). Or we could omit if not fitting. But we must preserve ALL substantive information. So we need to include Genesis description somewhere. Could put under About the role as additional paragraph. Thus About the role will include overview + Genesis description. Now we need to avoid repeating job title as heading. Not using. Now produce HTML. Structure:

      About the role

      ...

      Responsibilities

      • ... (maybe group)
      ... We need to embed lists. Let's craft. About the role paragraph: "The Genesis Orthopedic APP Clinical Fellowship is a 12-month, full-time, paid training year designed from scratch for new graduates who are serious about orthopedics and ready to do the work to get there. No prior ortho experience required. What we need is the aptitude, the drive, and the willingness to be coached hard by people who know this specialty inside and out. By the end, you'll be ready to practice independently. And you'll already have the job. Genesis Orthopedics & Sports Medicine is a full-spectrum MSK platform — surgery, physical therapy, and everything in between — operating across 16 clinics throughout Chicagoland. We run clinical trials, serve Medicaid patients at scale, and have built a care delivery model that delivers the kind of orthopedic care that the most demanding patients want — and the most underserved patients can finally access. We're growing fast. We need APPs who are trained the Genesis way from day one." That's about the role. Responsibilities: combine Opportunity and What You'll Build Competency in. We could produce a paragraph then a list. Paragraph: "From day one, you're embedded across the full continuum of orthopedic care — clinic, hospital, and OR — with responsibility that grows as your competency does. You'll have structured mentorship from Genesis surgeons and senior APPs, progressive autonomy as you earn it, and a clear runway to a permanent role within the practice when the year is done. Twelve months. Real patients. Real procedures. Real orthopedics." Then list:
      • Clinic
        • Independent orthopedic evaluations and treatment planning
        • Fracture and acute injury management
        • Post-op visits and wound care
        • Injections, splinting, casting, and in-office procedures
        • Imaging review and clinical decision-making
      • Hospital
        • Daily inpatient rounding
        • ED and floor consults
        • Orders, documentation, and discharge planning
        • Serving as the liaison between surgeons and hospital teams
      • Operating Room
        • Surgical first assist
        • Pre- and post-operative care coordination
        • Progressive OR responsibility as skills develop
      Requirements: maybe heading Requirements (or Qualifications). We'll use Requirements. Paragraph: "You just graduated — or you're about to. You're BC or board-eligible. You're licensed in Illinois or getting there. You're coachable. You're comfortable with complexity, able to handle clinic