Local Contract Surgery RN - $56 per hour

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID as heading; can fold into short p. Remove boilerplate. We need to parse the posting. Content: - Stability Healthcare is seeking a local contract nurse RN OR - Operating Room for a local contract nursing job in Peoria, Illinois. - Job Description & Requirements Specialty: OR - Operating Room Discipline: RN Start Date: 10/12/2026 Duration: 13 weeks 36 hours per week Shift: 12 hours Employment Type: Local Contract - Stability Healthcare is looking for a OR RN contract position in Peoria, IL. Also known as perioperative nurses, operating room (OR) nurses provide care for patients before, during, and after surgical procedures. Perioperative nurses work in every type of healthcare facility. - Benefits list: *$600 travel bonus *Day 1 health insurance with United Healthcare *PTO plan -- start accruing on day 1, use during contract or cash out at the end! *Guaranteed stipend if facility calls you off *Extra hour bonus -- earn an additional hourly bonus for working over your weekly contracted hours - Stability Healthcare Job ID #L-881045. Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. - Posted job title: OR - About Stability Healthcare: description. - Benefits section again: Guaranteed Hours Benefits start day 1 (maybe duplicate). We need to produce sections: About the role (maybe description of role), Responsibilities (maybe duties), Requirements (maybe qualifications), Qualifications (maybe discipline, specialty), Skills (maybe not given), Benefits (list), Pay (maybe mention pay package based on 12 hour shifts, tax-free stipend amount to be determined - but we should not include Pay section if content is vague like "tax-free stipend amount to be determined" - that is not specific. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Pay package based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. That's somewhat vague but includes specifics: based on 12 hour shifts and 36 hours per week. However "tax-free stipend amount to be determined" is placeholder. Might still be okay to include Pay section with the known specifics? The rule says: never emit a heading followed by filler/placeholder text. If we include Pay section, we must ensure the content is not just filler. We have some specifics: based on 12 hour shifts and 36.0 hours per week (subject to confirmation). That's somewhat specific but still includes "subject to confirmation". Might be okay. However we also have Schedule section: we have shift: 12 hours, 36 hours per week, duration 13 weeks, start date. That is specific. So we can include Schedule. We need to avoid duplication. Let's extract substantive info: About the role: The description of OR RN duties: "perioperative nurses, operating room (OR) nurses provide care for patients before, during, and after surgical procedures. Perioperative nurses work in every type of healthcare facility." Also maybe "Stability Healthcare is looking for a OR RN contract position in Peoria, IL." That's about role. Responsibilities: Could be the same as above? Might be redundant. But we can separate: Responsibilities: provide care for patients before, during, and after surgical procedures. Requirements: Specialty: OR - Operating Room; Discipline: RN; maybe also local contract? Not sure. Qualifications: Could be same as Requirements. Might combine. Skills: Not given. Benefits: list as above. Pay: Pay package based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. Might be considered vague but we have some specifics. Could include. Schedule: Start Date: 10/12/2026; Duration: 13 weeks; 36 hours per week; Shift: 12 hours; Employment Type: Local Contract. We also have Guaranteed Hours Benefits start day 1 (maybe part of Benefits). Already have benefits. We need to output only HTML fragment, no extra. Let's craft sections:

About the role

Stability Healthcare is seeking a local contract RN for an Operating Room (OR) position in Peoria, Illinois. OR nurses, also known as perioperative nurses, provide care for patients before, during, and after surgical procedures and work in every type of healthcare facility.

Responsibilities

• Provide preoperative, intraoperative, and postoperative patient care.
• Assist surgical team and maintain sterile field.
• Monitor patient status and respond to changes during procedures.

But we must not invent details. The posting only says they provide care before, during, after surgical procedures. We cannot add "assist surgical team" etc if not in text. Must preserve ALL substantive information; do NOT invent or summarize away detail. So we can only list what is given: "provide care for patients before, during, and after surgical procedures." That's it. Could be a single bullet. Thus Responsibilities:

• Provide care for patients before, during, and after surgical procedures.

Requirements: Specialty: OR - Operating Room; Discipline: RN. Could be list. Qualifications: maybe same as Requirements? Might be redundant. Better to have Requirements include specialty and discipline; Qualifications maybe start date? Not sure. The posting includes Start Date, Duration, hours, shift, employment type. Those could be under Schedule. Requirements could be specialty and discipline. Qualifications could be maybe none else. But we should not create thin sections. Let's think: The posting has "Job Description & Requirements" with Specialty, Discipline, Start Date, Duration, 36 hours per week, Shift, Employment Type. So we could treat Requirements as Specialty and Discipline. Schedule as Start Date, Duration, Hours, Shift, Employment Type. Qualifications maybe not present. Skills not present. Thus sections: About the role (description) Responsibilities (duties) Requirements (Specialty, Discipline) Schedule (Start Date, Duration, Hours, Shift, Employment Type) Benefits (list) Pay (based on 12 hour shifts and 36.0 hours per week, tax-free stipend amount to be determined) - maybe include but note it's subject to confirmation. We must not include placeholder text like "tax-free stipend amount to be determined" - that is somewhat placeholder but still conveys that stipend amount is to be determined. Might be considered filler. The rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "tax-free stipend amount to be determined" is similar to TBD. So better to omit Pay section entirely, as it's not specific enough. The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Pay package based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. That's stating something, albeit vague. But the rule about filler applies to headings followed by filler text. If we include Pay section, we must ensure content is not just filler. The content includes "based on 12 hour shifts and 36.0 hours per week (subject to confirmation)" which is somewhat specific, but also includes "tax-free stipend amount to be determined" which is filler. Might be risky. Safer to omit Pay section. Schedule: we have specific start date, duration, hours per week, shift, employment type. That's substantive. Benefits: we have concrete list. Thus final HTML:

About the role

Stability Healthcare is seeking a local contract RN for an Operating Room (OR) position in Peoria, Illinois. OR nurses, also known as perioperative nurses, provide care for patients before, during, and after surgical procedures and work in every type of healthcare facility.

Responsibilities

• Provide care for patients before, during, and after surgical procedures.

Requirements

• Specialty: OR - Operating Room
• Discipline: RN

Schedule

• Start Date: October 12, 2026
• Duration: 13 weeks
• Hours per week: 36 hours
• Shift: 12 hours
• Employment Type: Local Contract

Benefits

• $600 travel bonus
• Day 1 health insurance with United Healthcare
• PTO plan – start accruing on day 1, use during contract or cash out at the end
• Guaranteed stipend if facility calls you off
• Extra hour bonus – earn an additional hourly bonus for working over your weekly contracted hours

We must not include any extra text like navigation. Ensure no markdown fences. Output only HTML. Check for any boilerplate: we removed Job ID, posted job title, About Stability Healthcare description (we used some but not the whole). The About Stability Healthcare paragraph is generic marketing; we might have included some of it in About the role? We used a sentence about OR nurses; we didn't include the agency description. That's okay; we preserved substantive info about the role. The agency description is boilerplate? It's about the company, not the role. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description might be considered boilerplate? Not sure. It's not strictly boilerplate but could be considered fluff. However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The company description is substantive? It's about the agency, not the job. Might be considered not required. The instruction says remove duplicated lines, but not to remove company info unless it's boilerplate. It's not explicitly listed as boilerplate to remove, but it's not about the job. The user likely expects only job-related sections. The example earlier: they'd include About the role (role description) not company description. So we can omit the Stability Healthcare description. Thus final output as above. Check for any missing specifics: The posting also mentions "Guaranteed HoursBenefits start day 1" which is similar to benefits. We have benefits list includes day 1 health insurance, PTO, etc. Guaranteed Hours maybe separate but we can incorporate into Benefits? Not needed. We have not included "Guaranteed Hours" as a benefit; but we have "Guaranteed stipend if facility calls you off" which is similar. The phrase "Guaranteed HoursBenefits start day 1" maybe means guaranteed hours benefit starts day 1. Could add as benefit: "Guaranteed hours benefit starts day 1". But we already have day 1 health insurance. Might be redundant. However we should preserve all substantive information. The phrase "Guaranteed HoursBenefits start day 1" appears after Benefits heading in the posting: "BenefitsGuaranteedHoursBenefits start day