Travel Nurse RN - PICU - Pediatric Intensive Care - $2,668 per week

We need to output HTML fragment with sections: h3 headings for sections present. Must not repeat only sections with real content. No job title heading. No Job ID. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info. Let's parse content: - Meda Health is seeking a travel nurse RN PICU - Pediatric Intensive Care for a travel nursing job in Oklahoma City, Oklahoma. - Job Description & Requirements Specialty: PICU - Pediatric Intensive Care Discipline: RN Start Date: ASAP Duration: 13 weeks 36 hours per week Shift: 12 hours, nights Employment Type: Travel IMPORTANT – TRAVEL ELIGIBILITY: Applicants must reside more than 50 miles from the facility to qualify for the travel stipend and travel-related benefits. Meda Health is looking for an PICU RN to work a travel assignment in an acute care hospital setting. Must have at least two years of experience, state licensure and BLS/PALS (at minimum). Competitive and Transparent Pay ... (some prose) At Meda Health, your coverage starts when you do. You’re covered, period. Our employees get the following benefits right off the bat: Health Vision Dental Life insurance Meda Health Job ID #19119479. 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: RN:PICU,19:00:00-07:00:00 (looks like weird) About Meda Health (mission statement etc.) We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. - About the role: maybe description of role: travel nurse RN PICU in acute care hospital setting. Could be a short paragraph. - Responsibilities: Not explicitly listed; maybe we can infer from description? But we must not invent. If no explicit responsibilities, we should not create a Responsibilities section. The instruction: include a section ONLY when the posting has real, specific content for it. So we should not create Responsibilities if not present. - Requirements: Must have at least two years of experience, state licensure and BLS/PALS (at minimum). Also travel eligibility: reside >50 miles. Also maybe discipline RN, specialty PICU. - Qualifications: Could be similar to requirements; but we need to differentiate? Usually qualifications include experience, licensure, certifications. We could put those under Requirements or Qualifications. Since we need to avoid thin sections, we can combine into one section maybe "Requirements" covering experience, licensure, certifications, travel eligibility. Or we could have "Qualifications" for experience/licensure/certs and "Requirements" for shift/hours etc. But we need to see if there is distinct content. - Skills: Not listed. - Benefits: Health Vision Dental Life insurance. Also coverage starts immediately. Also travel stipend? Travel eligibility mentions travel stipend and travel-related benefits. So benefits include health, vision, dental, life insurance, travel stipend (though amount TBD). Also maybe immediate coverage. - Pay: Competitive and Transparent Pay prose; Pay package based on 12 hour shifts and 36.0 hours per week; tax-free stipend amount to be determined. So we have some pay info but not specific numbers. The instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we cannot create a Pay section if the content is just vague like "Competitive and Transparent Pay" and "tax-free stipend amount to be determined". However we do have "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation)". That's still vague but includes specifics about shift and hours. But the actual pay amount is not given. Is that considered filler? The instruction says never emit a heading followed by filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Competitive and Transparent Pay" is vague but not exactly those placeholders. However it's still not specific pay. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does not require specific numbers, just that the posting states them. The posting does state "Competitive and Transparent Pay" and mentions pay package based on shifts and hours, tax-free stipend amount to be determined. So there is some mention of pay. So we can include a Pay section with that prose. - Schedule: Shift: 12 hours, nights; 36 hours per week; Duration: 13 weeks; Start Date: ASAP. So we have schedule info. So we can include Schedule section. - Benefits: we have health, vision, dental, life insurance, travel stipend (though amount TBD). Also coverage starts immediately. So we can include Benefits. - Requirements/Qualifications: we have experience, licensure, BLS/PALS, travel eligibility (>50 miles). Also discipline RN, specialty PICU. So we can put those in Requirements (or Qualifications). Since we need to avoid thin sections, we can combine into one section maybe "Requirements". Or we could have "Qualifications" for experience/licensure/certs and "Requirements" for shift/hours etc. But shift/hours is schedule. So we can have Requirements for experience/licensure/certs/travel eligibility. That's substantive. - About the role: we have description: Meda Health is seeking a travel nurse RN PICU - Pediatric Intensive Care for a travel nursing job in Oklahoma City, Oklahoma. Meda Health is looking for an PICU RN to work a travel assignment in an acute care hospital setting. That's about the role. So we can have About the role section. - About Meda Health: mission statement etc. That's not a required section but could be included as "About the company"? Not in list. The list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add extra sections like About Meda Health unless it fits one of those headings. The mission statement is not about the role; it's about the company. The instruction says use headings for those specific sections. It didn't forbid other headings, but 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 they want only those. Safer to stick to those. So we can omit About Meda Health content? But we must preserve ALL substantive information. If we omit it, we lose substantive info. However maybe we can incorporate it into About the role? Not appropriate. Could we put it under a generic

without heading? The instruction: Output ONLY the HTML fragment. It didn't forbid other headings, but says use

for section headings (e.g. ...). It didn't say you cannot use other headings. But to be safe, we could include a section like "About Meda Health" using

as well, though not in the list. The instruction says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies those are the expected headings, but not exclusive. However they also say "include a section ONLY when the posting has real, specific content for it". So we could add a section for About Meda Health if we want. But the list of examples may be just illustrative; they didn't forbid other headings. However the test might expect only those headings. Safer to stick to those headings and incorporate Meda Health mission into maybe a

under About the role? Not ideal but could be considered part of role description? Might be okay. Alternatively we could create a section "About Meda Health" as

About Meda Health

and put the mission there. The instruction didn't explicitly forbid that. It said use

for section headings (e.g. ...). So using

for other headings is still using

. So it's compliant. The examples are just examples. I'd include it. But we must not repeat the job title as a heading. Already not. We must not put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. So we should not have a heading for Job ID. We can drop it or put in a

. Probably drop it as minor metadata. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. There's none evident besides maybe the "IMPORTANT – TRAVEL ELIGIBILITY:" which is substantive. We need to preserve ALL substantive information. So we need to include: location Oklahoma City, Oklahoma; specialty PICU; discipline RN; start date ASAP; duration 13 weeks; 36 hours per week; shift 12 hours nights; employment type Travel; travel eligibility >50 miles; must have at least two years experience, state licensure, BLS/PALS; benefits: health, vision, dental, life insurance; coverage starts immediately; travel stipend (tax-free) amount TBD; pay package based on 12 hour shifts and 36.0 hours per week; competitive and transparent pay; maybe mention that pay package is subject to confirmation. We also have "Posted job title: RN:PICU,19:00:00-07:00:00" which seems weird; maybe it's a timestamp? Could be minor metadata; we can drop. Now craft sections:

About the role

Meda Health is seeking a travel nurse RN specializing in Pediatric Intensive Care (PICU) for a travel nursing assignment in Oklahoma City, Oklahoma. The role involves working in an acute care hospital setting.

Maybe also include that it's a travel nursing job.

Requirements

• Active RN license (state licensure)
• Minimum two years of recent PICU experience
• BLS and PALS certifications (at minimum)
• Must reside more than 50 miles from the facility to qualify for travel stipend and travel-related benefits

We could also add discipline RN and specialty PICU but those are covered in About the role. Could also add them under Requirements but it's okay.

Benefits

• Health insurance
• Vision insurance
• Dental insurance
• Life insurance
• Travel stipend (tax‑free, amount to be determined)
• Coverage effective from first day of assignment

Pay

Competitive and transparent pay package based on 12‑hour shifts and 36 hours per week (subject to confirmation), with a tax‑free stipend component.

Schedule

• Shift: 12‑hour nights
• Hours per week: 36
• Assignment length: 13 weeks
• Start date: ASAP

We could also add Employment Type: Travel but maybe under About the role or Schedule. Could add a line in About the role: "This is a travel nursing position." We need to ensure we didn't invent or summarize away detail. We kept all specifics. Check for any duplicated lines: we didn't repeat. Check for boilerplate: we removed Job