Local Contract PCU Float RN - $47-55 per hour

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 if posting has real specific content. Must not repeat job title as heading. Must not include Job ID as heading; can fold minor metadata into short

or drop it. Must preserve all substantive info; remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. We need to parse the posting. Content: "Medical Solutions is seeking a local contract nurse RN Float PCU - Progressive Care Unit Med Surg for a local contract nursing job in Columbus, Ohio." That's job description intro. "Job Description & RequirementsSpecialty: PCU - Progressive Care UnitDiscipline: RNDuration: 13 weeks36 hours per weekShift: 12 hours, daysEmployment Type: Local Contract" Then a marketing paragraph: "We’re seeking talented healthcare professionals whose adventure game is as strong as their clinical game. Those that want flexibility and high pay, we have the positions for you! Some of the industry-leading benefits enjoyed by Medical Solutions travel nurses and travel allied healthcare professionals include: Day One Medical, Dental, and Vision with low premiums Day One 401(k) with Company Contribution Personalized Compensation Packages Paid, Private, Fully Furnished, Pet-Friendly Housing Dedicated Recruiter and 24/7 Customer Care Line Per Diem Allowance and Paid Travel Licensure and Certification Reimbursement Free Liability Coverage Voluntary Benefits: Critical Illness, Hospital Indemnity, Accident, and Pet Insurance Equal Employment Opportunity And More! Estimated pay package based on bill rate at time job was posted. Bill rates can change frequently and without notice. Exact pay package may vary based on guaranteed hours, distance being traveled, and customizations available for travelers." Then "Medical Solutions Job ID #1189220L. Posted job title: Telemetry" Then "About Medical Solutions" paragraph (company description). Then "Benefits" list: Weekly pay, Holiday Pay, Guaranteed Hours, Continuing Education, 401k retirement plan, Pet insurance, Company provided housing options, Cancelation protection, Wellness and fitness programs, Mileage reimbursement, Referral bonus, Employee assistance programs, Medical benefits, Dental benefits, Vision benefits, Benefits start day 1, License and certification reimbursement, Life insurance, Discount program. We need to produce sections: maybe About the role (description), Responsibilities? Not given explicit responsibilities. Could infer from specialty: PCU Float RN duties? Not given. Should not invent. So we should only include sections where there is real specific content. We have details: Specialty, Discipline, Duration, Hours per week, Shift, Employment Type. That could go under "About the role" or "Job Details". Could treat as "About the role". Could also have "Requirements" maybe not explicit. There's no explicit list of requirements besides being RN, PCU experience? Not given. So we shouldn't create Requirements section if not specific. We have benefits list: many items. So we can have Benefits section with

• . We have pay info: "Estimated pay package based on bill rate at time job was posted. Bill rates can change frequently and without notice. Exact pay package may vary based on guaranteed hours, distance being traveled, and customizations available for travelers." That's vague; not a specific number or range. According to rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). This is vague but mentions variability. It's not a specific number. It's basically saying pay varies. That might be considered filler. Should we include Pay section? The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about pay package but not a concrete figure. It's still stating something about pay, albeit vague. However the rule about filler text: "never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")". The phrase "Exact pay package may vary based on..." includes "may vary". That's similar to "varies". So likely we should NOT include Pay section because it's not specific. Schedule: we have shift: 12 hours, days; 36 hours per week; duration 13 weeks. That's schedule info. Could include Schedule section with details: 12-hour day shifts, 36 hours per week, 13-week contract. That's specific. So we can include Schedule. About the role: we can include description of role: local contract nurse RN Float PCU - Progressive Care Unit Med Surg in Columbus, Ohio. Also specialty, discipline, duration, hours, shift, employment type. Could be in About the role. Responsibilities: not given; skip. Requirements: not given; skip. Qualifications: not given; skip. Skills: not given; skip. Benefits: we have list; include Benefits. We also have company description "About Medical Solutions". That could be under "About the company" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add About Medical Solutions as a heading; maybe we can fold that into About the role? But it's about the company, not the role. However rule: "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." It doesn't forbid other headings not in list? It says: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The e.g. suggests those are examples, but likely we should only use those headings. Safer to stick to those. Thus we can have About the role containing both role description and maybe company overview? Could include a brief note about Medical Solutions as employer within About the role? Might be okay. We must not include boilerplate like EEO, duplicated lines, application instructions. The posting includes "Equal Employment Opportunity And More!" which is boilerplate; we should drop that. Also "Medical Solutions Job ID #1189220L. Posted job title: Telemetry." That's minor metadata; we can drop or fold into short

  . Probably drop. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all substantive info: specialty, discipline, duration, hours, shift, employment type, location, benefits list, schedule details, maybe the marketing paragraph about flexibility and high pay? That's substantive? It's marketing fluff but still part of posting. Should we keep? It's not boilerplate; it's about flexibility and high pay. Could be considered part of role description. We'll keep it as prose. We need to output only HTML fragment. Structure:

  About the role

  Medical Solutions is seeking a local contract nurse RN Float PCU - Progressive Care Unit Med Surg for a local contract nursing job in Columbus, Ohio. Specialty: PCU - Progressive Care Unit. Discipline: RN. Duration: 13 weeks. 36 hours per week. Shift: 12 hours, days. Employment Type: Local Contract. We’re seeking talented healthcare professionals whose adventure game is as strong as their clinical game. Those that want flexibility and high pay, we have the positions for you!

  Then maybe

  Schedule

  12‑hour day shifts, 36 hours per week, 13‑week contract.

  Then

  Benefits

  • Weekly pay
  • Holiday Pay
  • Guaranteed Hours
  • Continuing Education
  • 401k retirement plan
  • Pet insurance
  • Company provided housing options
  • Cancelation protection
  • Wellness and fitness programs
  • Mileage reimbursement
  • Referral bonus
  • Employee assistance programs
  • Medical benefits
  • Dental benefits
  • Vision benefits
  • Benefits start day 1
  • License and certification reimbursement
  • Life insurance
  • Discount program
  We should also include the list of industry-leading benefits mentioned earlier: Day One Medical, Dental, Vision with low premiums, Day One 401(k) with Company Contribution, Personalized Compensation Packages, Paid, Private, Fully Furnished, Pet-Friendly Housing, Dedicated Recruiter and 24/7 Customer Care Line, Per Diem Allowance and Paid Travel, Licensure and Certification Reimbursement, Free Liability Coverage, Voluntary Benefits: Critical Illness, Hospital Indemnity, Accident, and Pet Insurance. Some of these overlap with benefits list but we need to preserve all substantive info; not duplicate but we can include them. The benefits list later includes many similar items; we should combine? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we combine, we might lose some specifics like "Day One Medical, Dental, and Vision with low premiums" vs "Medical benefits", "Dental benefits", "Vision benefits". The later list includes Medical benefits, Dental benefits, Vision benefits but not specifying Day One or low premiums. The earlier list includes Day One 401(k) with Company Contribution (later list includes 401k retirement plan). Personalized Compensation Packages (not in later list). Paid, Private, Fully Furnished, Pet-Friendly Housing (later list includes Company provided housing options). Dedicated Recruiter and 24/7 Customer Care Line (not in later list). Per Diem Allowance and Paid Travel (not in later list). Licensure and Certification Reimbursement (later list includes License and certification reimbursement). Free Liability Coverage (not in later list). Voluntary Benefits: Critical Illness, Hospital Indemnity, Accident, and Pet Insurance (later list includes Pet Insurance but not the others). So we need to include all these specifics. Thus Benefits section should include all items from both mentions, without duplication but preserving specifics. We can list them as separate
• items, ensuring we don't repeat same meaning but keep distinct. Let's compile unique items: - Day One Medical, Dental, and Vision with low premiums - Day One 401(k) with Company Contribution - Personalized Compensation Packages - Paid, Private, Fully Furnished, Pet-Friendly Housing - Dedicated Recruiter and 24/7 Customer Care Line - Per Diem Allowance and Paid Travel - Licensure and Certification Reimbursement - Free Liability Coverage - Voluntary Benefits: Critical Illness, Hospital Indemnity, Accident, and Pet Insurance - Weekly pay - Holiday Pay - Guaranteed Hours - Continuing Education - 401k retirement plan (maybe redundant with Day One 401(k) with Company Contribution; but we can keep both as they are slightly different; but to avoid duplication we could note Day One 401(k) with Company Contribution is the 401k plan. However the later list says "401k retirement plan". It's likely same. To preserve all detail, we could keep both but note they are similar; but duplication might be considered redundant but not invented. Safer to keep both? The instruction: do NOT summarize away detail. If we merge, we might lose detail about Day One and Company Contribution. So we should keep both as separate