Local Contract OR RN - $42-50 per hour

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

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

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID as heading. Preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text like "commensurate with experience", "not specified", etc. Never create Pay/Schedule/Benefits sections unless posting actually states them. We need to parse the posting. Content: - Medical Solutions is seeking a local contract nurse RN OR - Operating Room for a local contract nursing job in Indianapolis, Indiana. - Job Description & Requirements Specialty: OR - Operating Room Discipline: RN Duration: 13 weeks 40 hours per week Shift: 10 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!" - 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. - Medical Solutions Job ID #1180215L. Posted job title: OR (Operating Room) - About Medical Solutions paragraph (multiple sentences). We need to preserve substantive info but remove boilerplate? The "About Medical Solutions" is descriptive about company; it's not boilerplate like EEO. It's okay to keep. - Benefits section: list of 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). This is a list. We need to decide sections. Potential sections: About the role (maybe description), Responsibilities (maybe not explicit), Requirements (maybe specialty, discipline, duration, hours, shift, employment type), Qualifications (maybe not explicit), Skills (maybe not explicit), Benefits (we have benefits list), Pay (we have estimated pay package info but it's vague: "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." This is not a specific number; it's generic. According to rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state something about pay but it's vague. Is that considered filler? It says "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 not a specific number; it's basically saying pay varies. This could be considered filler. The rule says never emit a heading followed by filler/placeholder text. So we should not create a Pay section if it's just vague. However, we could include the statement as prose under another section like "About the role" or "Details". But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to include only those sections that have substantive content. We have substantive content for: About the role (maybe the description about seeking professionals, adventure game, flexibility, high pay). Also we have details about the job: Specialty, Discipline, Duration, Hours, Shift, Employment Type. That could go under Requirements or Qualifications. We have Benefits list (substantive). We have Schedule? The posting includes Shift: 10 hours, days; 40 hours per week. That's schedule info. So we could create a Schedule section with that info. However, we need to check if schedule is substantive: yes, they give shift length and days. So we can include Schedule. Pay: we have vague statement; maybe we should not create Pay section. Instead we could incorporate that statement into About the role or Requirements as prose. But the rule says: "Prefer a few substantive sections over many thin ones." So we could combine. We need to output HTML fragment only. We must not repeat job title as heading. So no

  OR (Operating Room)

  . We must not put Job ID as heading. We need to remove duplicated lines, boilerplate like EEO, etc. The posting includes "Equal Employment Opportunity" inside benefits list; that is boilerplate; we should remove it. Also "And More!" is filler; maybe remove. We need to preserve all substantive information. So we keep the benefits list but remove EEO line. We need to format benefits as
  • . Similarly, we need to format responsibilities/requirements as list if applicable. Let's extract substantive content: - Location: Indianapolis, Indiana (maybe part of About the role). Not a heading but we can include in prose. - Job type: Local contract nurse RN OR - Operating Room. - Duration: 13 weeks. - Hours: 40 hours per week. - Shift: 10 hours, days. - Employment Type: Local Contract. - Specialty: OR - Operating Room. - Discipline: RN. - Adventure game line: "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!" This is marketing fluff but substantive? It's about flexibility and high pay. Could be included in About the role. - Benefits list (as above) with 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 (Remove Equal Employment Opportunity) And More! (remove as filler) Also later Benefits section 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 merge duplicate items (some appear in both lists). We should preserve all substantive info but avoid duplication. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't explicitly forbid deduplication, but we should not lose info. If we combine duplicates, we still preserve the info (just not repeated). That's likely acceptable. We need to decide sections. Potential sections: - About the role: includes location, job title (maybe not as heading), description about adventure game, flexibility, high pay, maybe also the specialty/discipline? But we might put specialty/discipline under Requirements. - Requirements: includes Specialty, Discipline, Duration, Hours, Shift, Employment Type. - Benefits: combine both benefit lists. - Schedule: maybe we already have shift/hours under Requirements; but we could also have Schedule section with shift and hours. However, we might avoid duplication. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine shift/hours into Requirements or About the role. But we have a specific Schedule heading allowed; we could use it if we have schedule specifics. The posting gives shift: 10 hours, days; 40 hours per week. That's schedule. So we could have a Schedule section with that info. - Pay: we have vague statement; maybe we incorporate into About the role as a sentence: "Estimated pay package based on bill rate at time job was posted; exact pay may vary." But that's somewhat filler. However, it's still substantive info that pay is variable. It's not a specific number but it's info. The rule says never emit a heading followed by filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". The phrase "Exact pay package may vary based on guaranteed hours, distance being traveled, and customizations available for travelers." includes "varies". That's placeholder-ish. So better to avoid a Pay section. Instead we could include that sentence in About the role or Requirements as prose, but it's still containing the word "varies". The rule is about headings followed by filler text; if we put it in a paragraph under a heading that has other substantive content, it's okay. So we can include that sentence in About the role. Thus sections: - About the role (paragraph with location, adventure game line, flexibility/high pay, pay variability statement). - Requirements (list: Specialty, Discipline, Duration, Hours per week, Shift, Employment Type). - Benefits (list of benefits). - Schedule (maybe we already included shift/hours in Requirements; but we could keep Schedule separate with shift and hours. However that would duplicate info. To avoid duplication, we could put shift/hours only in Schedule and not in Requirements. But Requirements also needs duration etc. Let's think: Requirements could contain Specialty, Discipline, Duration, Employment Type. Schedule could contain Hours per week and Shift. That splits logically. That seems okay and avoids duplication. Thus: - Requirements: Specialty: OR - Operating Room; Discipline: RN; Duration: 13 weeks; Employment Type: Local Contract. - Schedule: Hours per week: 40 hours; Shift: 10 hours, days. - Benefits: combined list. - About the role: location, adventure game line, flexibility/high pay, pay variability statement. We need to ensure we don't repeat job title as heading. So About the role heading is fine. We need to output HTML fragment: use

    for each section heading. Use

    • for lists. Use

      for prose. We need to ensure we don't include any markdown fences. Let's craft. About the role paragraph: "Medical Solutions is seeking a local contract nurse RN - Operating Room for a local contract nursing job in Indianapolis, Indiana. 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! Estimated pay package based on bill rate at time job was posted; bill rates can change frequently and