Travel Operating Room Registered Nurse - $2,225 per week

We need to produce HTML fragment with sections for headings: 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 etc. Must remove boilerplate. Must preserve all substantive info. We need to parse the posting. Key info: - Specialty: OR - Operating Room - Discipline: RN - Start Date: 10/26/2026 - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, nights - Employment Type: Travel - Job Summary: Operating Room (OR) Registered Nurse (RN) - Seasonal Travel assignment in a large trauma and neuro surgical unit. This position involves working in a high-acuity environment with advanced equipment such as DaVinci Robotics and experience in vascular/hybrid OR procedures. The shift is scheduled for nights, with a 12-hour shift pattern from 7:00 PM to 7:00 AM, requiring a minimum of 36 hours per week. - Job Details: Schedule: Nights, 12-hour shifts, with a minimum of 36 hours per week - Required Qualifications: Valid RN license, a minimum of 1 year current acute care OR RN experience, BLS and ACLS certifications, located within the United States, and at least 1 year of relevant experience - Preferred Qualifications: Robotics experience, prior Meditech experience, travel experience to large trauma OR facilities, and familiarity with vascular/hybrid procedures - Additional Information: This assignment is located in a high-capacity surgical unit with 284 beds and an experienced team of 55 staff members, including charge RNs and trauma RNs. On-call responsibilities are from 5:00 PM to 11:00 PM, Monday through Friday, with no overnight on-call required. Scrubs are provided. The unit utilizes electronic medical records through Meditech / CPN and typically performs trauma, neuro, and vascular procedures. Staff are self-motivated, positive, and team-oriented. - Benefits: Private housing or generous housing allowance; Comprehensive health insurance with prescription coverage; Dependent health insurance with prescription coverage; Competitive salaries; Referral bonuses; Travel reimbursement; 401(k) retirement plan; Direct deposit/free checking; Unlimited free CE credits. - Pay package: based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. - Posted Date: 2026-09-22 (maybe not needed) - About Cross Country Nurses paragraph (maybe not needed as it's boilerplate? It's about the company, could be considered "About the role"? Actually "About the role" is a section heading we can use for description of role. The "About Cross Country Nurses" is company description, maybe we can include under "About the role"? But we should not include boilerplate. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Cross Country Nurses" is not exactly boilerplate but could be considered promotional. Might be okay to keep as part of "About the role"? However they said "Prefer a few substantive sections over many thin ones." We could combine role description and company info under "About the role". But we need to ensure we don't include filler. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for: - About the role: Could include job summary and additional info about unit (size, staff, equipment, procedures). That's substantive. - Responsibilities: Not explicitly listed but implied: working in OR, high-acuity, DaVinci Robotics, vascular/hybrid procedures, on-call responsibilities, etc. Could extract responsibilities from job summary and additional info. Might be okay to create a Responsibilities section with bullet list. - Requirements: Required Qualifications list. - Qualifications: Could be Preferred Qualifications? Or we could treat Required Qualifications as Requirements, and Preferred Qualifications as Qualifications (or Skills). The instruction: Use headings exactly as given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - Requirements: Valid RN license, minimum 1 year current acute care OR RN experience, BLS and ACLS certifications, located within US, at least 1 year of relevant experience (some duplication). We'll list. - Qualifications: Could be Preferred Qualifications: Robotics experience, prior Meditech experience, travel experience to large trauma OR facilities, familiarity with vascular/hybrid procedures. - Skills: Could be skills like DaVinci Robotics, Meditech, vascular/hybrid OR procedures, trauma/neuro, etc. But we already have similar in Qualifications. Might combine or separate. Since we have both, we could put skills as technical skills: DaVinci Robotics, Meditech/CPN EMR, vascular/hybrid procedures, trauma/neuro OR, etc. But we need to avoid duplication. Perhaps we put skills as "DaVinci Robotics, Meditech EMR, vascular/hybrid OR procedures, trauma/neuro OR". However the posting already mentions those under Preferred Qualifications and Additional Information. We'll decide. - Benefits: list as given. - Pay: mention pay package based on 12 hour shifts and 36 hours per week, tax-free stipend amount to be determined. This is somewhat vague but it's specific enough? It says "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." That's not a specific number, but it's still content. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here "tax-free stipend amount to be determined" is TBD-like. Might be considered placeholder. Should we omit Pay section? The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay package based on shifts and hours, but stipend TBD. Might be considered not specific enough. However they said "Prefer a few substantive sections over many thin ones." If we omit Pay, we might lose some info. But we could include Pay with the info we have, but it's somewhat vague. The instruction 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 maybe we should omit Pay section to avoid filler. However we could still include the part about "based on 12 hour shifts and 36.0 hours per week" which is concrete. But the heading would be Pay, and the content would be that sentence. It's not exactly filler but it's not a specific amount. I'd lean to include Pay section with that sentence, as it's still substantive about how pay is calculated. The instruction about filler is about headings with filler like "commensurate with experience". This is not exactly that; it's a description of how pay is structured. I'd include. - Schedule: we have schedule: Nights, 12-hour shifts, minimum 36 hours per week. Also shift details: 7:00 PM to 7:00 AM. On-call responsibilities 5-11 PM Mon-Fri. So we have specific schedule info. So include Schedule section. Now we need to output HTML fragment with

for each section heading, then content: either

for prose or

• for lists. We must not include job title heading. Must not include Job ID etc. We must remove duplicated lines. Ensure we preserve all substantive info. Let's draft sections: About the role: Could combine job summary and additional info about unit. Prose: "Operating Room (OR) Registered Nurse (RN) - Seasonal Travel assignment in a large trauma and neuro surgical unit. This position involves working in a high-acuity environment with advanced equipment such as DaVinci Robotics and experience in vascular/hybrid OR procedures. The assignment is located in a high-capacity surgical unit with 284 beds and an experienced team of 55 staff members, including charge RNs and trauma RNs. The unit utilizes electronic medical records through Meditech/CPN and typically performs trauma, neuro, and vascular procedures. Staff are self-motivated, positive, and team-oriented." That seems good. Responsibilities: Could list bullet points: Provide perioperative nursing care in OR; Manage high-acuity patients; Operate DaVinci Robotics; Assist with vascular/hybrid procedures; Follow night shift schedule (7:00 PM–7:00 AM, 12-hour shifts); Participate in on-call responsibilities (5:00 PM–11:00 PM, Monday–Friday); Ensure compliance with BLS/ACLS standards; Maintain sterile field and patient safety; Collaborate with surgical team; Document care using Meditech/CPN EMR. We need to ensure we don't invent info not in posting. The posting mentions: "working in a high-acuity environment with advanced equipment such as DaVinci Robotics and experience in vascular/hybrid OR procedures." "shift is scheduled for nights, with a 12-hour shift pattern from 7:00 PM to 7:00 AM". "On-call responsibilities are from 5:00 PM to 11:00 PM, Monday through Friday, with no overnight on-call required." "Scrubs are provided." "The unit utilizes electronic medical records through Meditech / CPN". So we can derive responsibilities accordingly. We'll keep bullets faithful. Requirements: list bullet points: Valid RN license; Minimum 1 year current acute care OR RN experience; BLS certification; ACLS certification; Located within the United States; At least 1 year of relevant experience (maybe duplicate). We'll combine. Qualifications (Preferred): Robotics experience; Prior Meditech experience; Travel experience to large trauma OR facilities; Familiarity with vascular/hybrid procedures. Skills: Could list technical skills: DaVinci Robotics operation; Meditech/CPN EMR; Vascular/hybrid OR procedures; Trauma/neuro OR care; 12-hour night shift adaptability; On-call management. But some overlap with qualifications. Might be okay to have Skills as "DaVinci Robotics, Meditech EMR, vascular/hybrid OR procedures, trauma/neuro OR care". However we risk duplication. Perhaps we can omit Skills section if content too thin. But we have some skills. The instruction: Prefer a few substantive sections over many thin ones. If Skills is thin, maybe combine into Qualifications. But we already have Qualifications for preferred. Could we treat Qualifications as both required and preferred? But we already have Requirements separate. Could we merge Qualifications and Skills? The headings are prescribed; we must use them if we have content. If we think Skills is not substantive enough, we could omit it. Let's see: we have DaVinci Robotics, Meditech, vascular/hybrid, trauma/neuro. That's four items, could be a list. That's substantive enough. Thus we will include Skills section with bullet list. Benefits: list bullet points as given. Pay: Provide sentence: "Pay package is based on 12‑hour shifts and 36.0 hours per week (subject to confirmation) with a tax‑free stipend amount to be determined." Schedule: Provide bullet or prose: "Night shift: 12‑hour shifts from 7:00 PM to 7:00 AM, minimum 36 hours per week; On‑call responsibilities: 5: