Travel Labor and Delivery Registered Nurse - $2,599 per week

We need to output HTML fragment with sections: h3 headings for sections present. Must not repeat job title as heading. Must not include Job ID or requisition numbers as headings; can fold minor metadata into short p or drop it. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Must preserve all substantive information. Must not invent or summarize away detail. Must include a section only when posting has real specific content for it. Must not emit heading followed by filler/placeholder text like "commensurate with experience", "not specified", etc. Must not create Pay/Schedule/Benefits sections unless posting actually states them. However the posting does have benefits listed (list of benefits). It also mentions pay: "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." Also "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." So we have some pay info but not exact numbers. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits (list). It does mention pay package but not specific amount; still it's about pay. Should we include a Pay section? The posting includes "Estimated pay package based on bill rate..." and "Pay package is based on 12 hour shifts and 36.0 hours per week...". That's substantive info about pay (though not exact numbers). The instruction says: 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. It does state pay package details (though variable). So we can include a Pay section with the given info. Similarly Schedule: they gave shift: 12 hours, nights; 36 hours per week; duration 13 weeks. That's schedule info. So we can include Schedule section. Benefits: they list many benefits. So include Benefits section. Also we need sections like About the role, Responsibilities, Requirements, Qualifications, Skills. The posting includes: "Specialty: Labor and Delivery Discipline: RN Duration: 13 weeks 36 hours per week Shift: 12 hours, nights Employment Type: Travel". Also description: "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!" That's more about role. Also location info: Blair, Nebraska, near Omaha. Also description of hospital: Memorial Community Hospital & Health System. Also "If interested please contact Medical Solutions at Medical Solutions Job ID #1180850." That's application instruction; we should drop application instructions. Also "Posted job title: L&D (Labor and Delivery)" maybe not needed as heading. We need to preserve all substantive information; not invent or summarize away detail. So we need to include details like location, hospital name, address, etc. Also the benefits list. We need to use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. We should not repeat the job title as a heading. So no heading for "Labor and Delivery RN". We'll have sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule as appropriate. We need to decide which sections have content. About the role: we can include description of the role, adventure game, flexibility, high pay, location, hospital details, etc. Responsibilities: maybe not explicitly listed; the posting does not list specific duties. So we should not create Responsibilities section if no real specific content. Similarly Requirements, Qualifications, Skills: not explicitly listed besides specialty RN, L&D. Could we treat "Specialty: Labor and Delivery Discipline: RN" as qualifications? Possibly but it's minimal. The instruction: prefer a few substantive sections over many thin ones. So we might combine qualifications into About the role or maybe a Requirements section if we have something. But we have "Specialty: Labor and Delivery Discipline: RN". That's a requirement. Could be placed under Requirements. However we need to avoid thin sections. Maybe we can include a Requirements section with that bullet. But also we have "Duration: 13 weeks", "36 hours per week", "Shift: 12 hours, nights", "Employment Type: Travel". Those are more schedule/employment type. We could have sections: About the role (description), Benefits (list), Pay (info), Schedule (info). Possibly also Requirements (specialty). But we need to see if we can avoid too many sections. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements into About the role? But About the role already has prose; we could add a bullet list for requirements? But they said use

  • for any list of duties/requirements/benefits. So if we have a list of requirements, we can put under a heading Requirements. But if we only have one item, it's still a list. Could be okay but might be thin. However we could incorporate that into About the role as a sentence: "The position requires an RN with Labor and Delivery specialty." That would preserve info without a separate section. That seems better to avoid thin sections. Similarly, we could incorporate schedule info into About the role or a Schedule section. Since schedule info is specific (13 weeks, 36 hrs/week, 12hr night shifts, travel employment type). That's substantive; we could make a Schedule section. Pay section: we have info about pay package based on bill rate, etc. That's substantive. Benefits section: we have list. Thus we will have sections: About the role, Benefits, Pay, Schedule. We must not include headings with filler text. Ensure each heading has real content. Now we need to strip boilerplate: EEO, Equal Employment Opportunity, navigation, legal, duplicated lines, application instructions (like "If interested please contact Medical Solutions at Medical Solutions Job ID #1180850.") Also remove "Posted job title: L&D (Labor and Delivery)" maybe not needed. Also remove "About Medical Solutions" section? That's boilerplate about the company; not specific to the job. Should we remove? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Medical Solutions" is not exactly boilerplate but it's generic company description; might be considered boilerplate? It's not specific to the job posting. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "About Medical Solutions" is generic marketing; could be considered boilerplate. However it's not explicitly listed as boilerplate to remove, but it's not specific to the job. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not explicitly say to remove generic company description. However earlier they said "Preserve ALL substantive information; do NOT invent or summarize away detail." The "About Medical Solutions" is substantive about the company, but not about the job. Might be considered not needed for the job posting fragment? The user likely wants only job-specific content. The example sections they gave include Benefits, Pay, Schedule, etc. They didn't include a section about the company. So I'd drop the "About Medical Solutions" paragraph. Also remove duplicated lines: there is a Benefits list repeated later? Actually there is a Benefits section near the end with list; earlier there is a list of benefits in the paragraph: "Some of the industry-leading benefits enjoyed by Medical Solutions travel nurses..." then later a Benefits section with list. We need to preserve all substantive information; we should combine them, not duplicate. So we need to extract the benefits list from both places and combine into a single list without duplication. Let's parse the benefits mentioned: First paragraph benefits list: - 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 (but we remove EEO) - And More! 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 combine, avoid duplicates. Also note some items overlap: Medical, Dental, Vision benefits appear both; 401k appears both; Pet insurance appears both; Company provided housing options vs Paid, Private, Fully Furnished, Pet-Friendly Housing (similar). Licensure and certification reimbursement appears both. Per Diem Allowance and Paid Travel maybe not in second list. Weekly pay, Holiday Pay, Guaranteed Hours, Continuing Education, Cancelation protection, Wellness and fitness programs, Mileage reimbursement, Referral bonus, Employee assistance programs, Life insurance, Discount program are new. We should produce a single
    • list of benefits, preserving all unique items. Need to be careful not to lose any. Let's compile a set: From first list: - 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 - (EEO removed) - And More! (we can ignore as vague) From second list: - Weekly pay - Holiday Pay - Guaranteed Hours - Continuing Education - 401k retirement plan (similar to Day One 401(k) with Company Contribution; but we can keep both? Might be duplicate. We'll keep one generic: 401(k) retirement plan with company contribution.) - Pet insurance (already in Voluntary Benefits) - Company provided housing options (similar to Paid, Private, Fully Furnished, Pet-Friendly Housing) - Cancelation protection - Wellness and fitness programs - Mileage reimbursement - Referral bonus - Employee assistance programs - Medical benefits (covered in Day One Medical...) - Dental benefits - Vision benefits - Benefits start day 1 (implicit in Day One) - License and certification reimbursement (duplicate) - Life insurance - Discount program We need to avoid duplication but still preserve all substantive info. We can combine similar items into more generic statements that encompass both. However instruction: do NOT invent or summarize away detail. Summarizing could be considered inventing? We need to preserve detail; we can list both even if similar, but that may be duplication. The instruction says remove duplicated lines. So we should not duplicate identical lines. For similar but not identical, we need to decide if they are duplicates