Orthopedic Surgery | Central Kansas

We need to output HTML fragment only, with sections for headings where there is real content. Use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the job description. We need to include sections only if posting has real specific content. We have: - Job title: Orthopedic Surgeon (not to be repeated as heading) - StartDate: ASAP (maybe schedule? but schedule not given) - Pay Rate: $600000.00 - $1500000.00 (Pay section) - Position Overview (maybe About the role) - Position Highlights (list) - Compensation & Benefits (list) - Community Highlights (maybe Benefits? Actually community highlights is location info, could be part of About the role or maybe a separate section? The allowed headings are limited: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Community Highlights could go under About the role or maybe Benefits? It's not exactly benefits but location/community. Probably we can put under About the role as prose. - Contact Information (should be removed as boilerplate? It's contact info for recruiter; we should remove application instructions and contact info. The instruction says remove application instructions. Contact info is likely part of application instructions, so drop it. - Job Benefits About the Company (some boilerplate about AMN Healthcare) - remove. - Foot And Ankle Orthopedic Surgery etc (list of keywords) - remove. Thus we need sections: About the role (position overview + highlights + community highlights maybe), Responsibilities (maybe not explicit), Requirements (maybe not explicit), Qualifications (maybe not explicit), Skills (maybe not explicit), Benefits (compensation & benefits list), Pay (pay rate), Schedule (maybe not explicit; we have flexible scheduling model based on physician preference, could be schedule info). So we can include Schedule section with that detail. We must not invent or summarize away detail; preserve all substantive information. Let's extract substantive content: Position Overview: "A physician-owned specialty surgical hospital in Central Kansas is seeking an Orthopedic Surgeon to join its highly integrated orthopedic platform and help establish and expand a dedicated Joint Care Center. This opportunity offers significant autonomy, substantial surgical volume, and a clear pathway to ownership within a physician-led organization." Position Highlights bullet points: - Existing orthopedic surgeons perform approximately 500–600+ surgeries annually each - OR utilization currently around 40%, providing significant capacity for growth - Cases currently scheduled approximately 6 weeks out - Patient population of 800,000+ people - Strong demand driven by a large Medicare population and aging patient base - Flexible scheduling model based on physician preference - Employed position with partnership and teaching opportunities - 21,000-square-foot physician-owned facility with attached rehabilitation center - Local hospital provides additional resources for cases requiring a higher level of care, including a Level III Trauma Center, MAKO robotic platform, and Stryker technology Compensation & Benefits bullet points: - Two-year income guarantee - Documented earning potential up to $1.5M - Sign on + Relocation bonus - Immediate ownership opportunity of up to 5% - Distribution income potential - 100% employer-paid health, dental, and vision coverage for physician and family - 30 days time off - Malpractice coverage Community Highlights bullet points: - Wichita metro and national airport 40 minutes away - Country Club ranked in Top 25 golf courses in the United States - Cosmosphere Space Museum & IMAX Theater - Sand Hills State Park - Fishing, hunting, camping, and outdoor recreation - Downtown with local restaurants, breweries, and boutique shopping - Strong youth sports and family recreation - Excellent public and private school options Pay Rate: $600000.00 - $1500000.00 StartDate: ASAP (maybe schedule? but we have flexible scheduling model; start date ASAP could be schedule? Probably we can put under Schedule: Start date ASAP, flexible scheduling model based on physician preference.) We need to avoid repeating job title as heading. We need to use

for section headings. We need to use

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

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove boilerplate etc. Thus we will produce sections: - About the role: includes Position Overview and maybe Community Highlights? But community highlights is location/community, could be part of About the role. However we might also create a separate section for Community Highlights? Not in allowed headings. So we incorporate into About the role as prose or list? The community highlights is a list; we could put as

  • under About the role? But About the role heading expects prose? The instruction: Use
    • for any list of duties/requirements/benefits, and

      for prose. So if we have a list under About the role, we should still use

      • . That's fine. Thus About the role could contain both prose (position overview) and lists (position highlights, community highlights). But we need to avoid mixing? It's okay to have multiple

        and

        under same heading. Responsibilities: Not explicitly listed; maybe we can infer from position highlights? But we should not invent. If no explicit responsibilities, we should not create Responsibilities section. Requirements: Not explicit; skip. Qualifications: Not explicit; skip. Skills: Not explicit; skip. Benefits: we have compensation & benefits list (including insurance, time off, malpractice, ownership, bonus, etc). That's benefits. Pay: we have pay rate. Schedule: we have flexible scheduling model based on physician preference and start date ASAP. So we can put schedule info. Thus sections: About the role, Benefits, Pay, Schedule. Check if any other sections like Responsibilities could be derived from position highlights (e.g., performing surgeries, establishing Joint Care Center). But those are more highlights/duties. However the instruction says to include a section ONLY when the posting has real, specific content for it. The posting does have duties: "help establish and expand a dedicated Joint Care Center", "perform surgeries". But those are in position highlights. Could be considered responsibilities. However we already used position highlights in About the role. Might be okay to not create Responsibilities. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must not include cookie/navigation/legal/EEO etc. We must not include application instructions (contact info). Thus final HTML:

        About the role

        A physician-owned specialty surgical hospital in Central Kansas is seeking an Orthopedic Surgeon to join its highly integrated orthopedic platform and help establish and expand a dedicated Joint Care Center. This opportunity offers significant autonomy, substantial surgical volume, and a clear pathway to ownership within a physician-led organization.

        Position Highlights

        ... but we cannot use heading not in allowed list. So we cannot add Position Highlights heading. Instead we can embed the list directly under About the role without a heading? But we need to convey that it's highlights. Could we just put a
        • list without a heading? The instruction: Use

          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. those). It might be okay to use other headings? Safer to stick to allowed headings only. So we should not add extra headings like Position Highlights. Instead we can incorporate the highlights as a list under About the role, maybe preceded by a

          describing that these are highlights. But we need to preserve all info; we can just put the list directly. Thus:

          About the role

          A physician-owned specialty surgical hospital in Central Kansas is seeking an Orthopedic Surgeon to join its highly integrated orthopedic platform and help establish and expand a dedicated Joint Care Center. This opportunity offers significant autonomy, substantial surgical volume, and a clear pathway to ownership within a physician-led organization.

          • Existing orthopedic surgeons perform approximately 500–600+ surgeries annually each
          • OR utilization currently around 40%, providing significant capacity for growth
          • Cases currently scheduled approximately 6 weeks out
          • Patient population of 800,000+ people
          • Strong demand driven by a large Medicare population and aging patient base
          • Flexible scheduling model based on physician preference
          • Employed position with partnership and teaching opportunities
          • 21,000-square-foot physician-owned facility with attached rehabilitation center
          • Local hospital provides additional resources for cases requiring a higher level of care, including a Level III Trauma Center, MAKO robotic platform, and Stryker technology

          Community highlights:

          • Wichita metro and national airport 40 minutes away
          • Country Club ranked in Top 25 golf courses in the United States
          • Cosmosphere Space Museum & IMAX Theater
          • Sand Hills State Park
          • Fishing, hunting, camping, and outdoor recreation
          • Downtown with local restaurants, breweries, and boutique shopping
          • Strong youth sports and family recreation
          • Excellent public and private school options
          Then Benefits:

          Benefits

          • Two-year income guarantee
          • Documented earning potential up to $1.5M
          • Sign on + Relocation bonus
          • Immediate ownership opportunity of up to 5%
          • Distribution income potential
          • 100% employer-paid health, dental, and vision coverage for physician and family
          • 30 days time off
          • Malpractice coverage
          Pay:

          Pay

          $600,000.00 - $1,500,000.00

          Schedule:

          Schedule

          Start date: ASAP. Flexible scheduling model based on physician preference.

          We need to ensure we didn't invent anything. All content is from posting. Check for any duplication: We have "Flexible scheduling model based on physician preference" appears both in About the role list and Schedule section. That's duplication; we should avoid repeating same content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It didn't say we cannot repeat, but better to avoid duplication. We could keep it only in Schedule section and remove from About the role list. However the list includes it as a highlight; we could keep it there and not duplicate in Schedule. But Schedule needs to convey start date and flexible scheduling. We could mention start date ASAP and note that scheduling is flexible (referring to the highlight). But we should not invent; we can say "Start date: ASAP. Flexible scheduling model based on physician preference (as noted in highlights)." That's still referencing the highlight but not duplicating the exact phrase? It's still the same phrase. Might be okay to duplicate; but better to avoid. We could move the flexible scheduling mention to Schedule and remove from About the role list. However then we lose that highlight from About the role. But we could keep it in About the role as a highlight and not duplicate in Schedule, but then Schedule would only have start date. But we need to convey schedule info; we could say "Start date: ASAP. (See flexible scheduling model under highlights.)" That's not