Travel PCU RN - $2,392 per week

We need to output HTML fragment with sections: headings using

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections only if real content. We need to parse the job posting. Content: - Job title: travel nurse RN PCU - Progressive Care Unit in Omaha, Nebraska. - Specialty: PCU - Progressive Care Unit - Discipline: RN - Start Date: 10/12/2026 - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, nights - Employment Type: Travel - Cure Healthcare is seeking a RN - PCU for positions in Omaha, Nebraska. - Current Nebraska license and AHA BLS and ACLS required and additional certifications related to this specialty. - To qualify for this travel assignment, the candidate's primary residence must be located at least 50 miles from the facility address. - This shift is 3x12 Nights. - Required: 2 years of recent experience in PCU. - Please inquire for specific job details and confirm shift required by facility. - Cure Healthcare Staffing Job ID #37764715. (metadata, drop) - 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:PCU,18:00:00-06:00:00 (maybe irrelevant) - About Cure Healthcare Staffing: description. We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to include sections only if real content. Potential sections: - About the role: could include description of role, specialty, location, start date, duration, hours, shift, employment type. - Responsibilities: not explicitly listed. Could infer but we must not invent. So we should not include Responsibilities if no explicit list. - Requirements: includes license, certifications, residence distance, experience. - Qualifications: maybe overlapping with requirements; but we can combine. - Skills: not listed. - Benefits: not listed (tax-free stipend amount to be determined is vague; but we have mention of tax-free stipend amount to be determined - that's not specific; we should not create Benefits section unless posting actually states them. It says "tax-free stipend amount to be determined." That's not a specific benefit; it's vague. According to rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should not create Benefits section. - Pay: posting 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 vague; not specific numbers. It's placeholder. So we should not create Pay section. - Schedule: we have shift details: 12 hours, nights, 3x12 Nights, 36 hours per week. That's specific. So we can include Schedule section. Thus sections: About the role (maybe include description), Requirements, Schedule. We could also include Qualifications if we separate license etc. But Requirements can cover license, certifications, experience, residence distance. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. Let's extract details: About the role: Could include: Specialty: PCU - Progressive Care Unit; Discipline: RN; Location: Omaha, Nebraska; Start Date: 10/12/2026; Duration: 13 weeks; Hours per week: 36; Employment Type: Travel. We can put that in a

  or maybe a

  . Since it's not a list of duties, we can use

  . Requirements: List: - Current Nebraska RN license - AHA BLS certification - AHA ACLS certification - Additional certifications related to PCU specialty (unspecified but mention) - Primary residence must be at least 50 miles from facility address - 2 years of recent experience in PCU - Shift: 3x12 Nights (but that's schedule; maybe we keep schedule separate) We could also include that shift is 12 hours, nights. But schedule section will cover shift details. Thus Requirements list items as above. Schedule: details: - Shift: 12 hours, nights - Pattern: 3x12 Nights (three 12-hour night shifts per week) - Hours per week: 36 hours We can put in

  . We must not repeat job title as heading. Not include Job ID. We must not include application instructions ("Please inquire for specific job details and confirm shift required by facility.") That's basically instruction to inquire; we should remove application instructions. The rule: remove application instructions. So we should omit that sentence. Also remove "Posted job title: RN:PCU,18:00:00-06:00:00" maybe irrelevant. Also remove "Cure Healthcare Staffing Job ID #37764715." Also remove "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." Since it's vague, we should not include Pay section; but we could still mention it as prose? The rule: do not create Pay/Schedule/Benefits sections unless posting actually states them. It does state pay package but it's vague; still it's stating something about pay. However it's placeholder "subject to confirmation" and "tax-free stipend amount to be determined." That's not specific. The rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should not create Pay section because the content is placeholder. However we could still include the info in About the role? But that would be placeholder. Better to omit it entirely, as it's not substantive. Similarly "tax-free stipend amount to be determined" is placeholder. Thus we omit pay. Now About Cure Healthcare Staffing description: That's about the company, not the role. Should we include? The instruction: "Preserve ALL substantive information". The company description is substantive. Should we include a section like "About the company"? Not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put company description under About the role? Might be okay but it's about the company not role. However we could include a

  after the headings maybe not under a heading? The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It might be okay to include other headings? Safer to stick to those. We could incorporate company description into About the role as a paragraph, but that might be mixing. However we could also omit company description if not required? The rule says preserve ALL substantive information. So we need to include it somewhere. We could add a

  after the sections without a heading? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot have other headings, but we should follow the pattern. Perhaps we can add a heading like "About Cure Healthcare Staffing" but that's not in the list. Might be considered extra heading not allowed? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are examples; we could use other headings if needed, but better to stick to those. However we could put the company description under a generic

  without a heading; that's allowed because we can use

  for prose. So we can just add a

  containing the company description after the sections. Thus final HTML:

  About the role

  Specialty: PCU - Progressive Care Unit. Discipline: RN. Location: Omaha, Nebraska. Start Date: 10/12/2026. Duration: 13 weeks. Hours per week: 36. Employment Type: Travel.

  Requirements

  • Current Nebraska RN license
  • AHA BLS certification
  • AHA ACLS certification
  • Additional certifications related to PCU specialty
  • Primary residence must be at least 50 miles from the facility address
  • Minimum 2 years of recent experience in PCU

  Schedule

  • Shift: 12 hours, nights
  • Schedule pattern: 3x12 Nights (three 12‑hour night shifts per week)
  • Hours per week: 36

  With 20+ years of healthcare staffing experience, Cure Healthcare Staffing helps nurses and allied health professionals rediscover their love of patient care while providing healthcare facilities with flexible staffing solutions. The company empowers clinicians with flexibility and ownership of their careers to keep qualified professionals in direct patient care. Patient care is prioritized; Cure is Joint Commission‑accredited and only accepts staff that meet its quality criteria to ensure short‑term assignments contribute to quality care.

  Check we didn't repeat job title as heading. No metadata. No application instructions. No boilerplate. We need to ensure we didn't include any filler like "subject to confirmation". We omitted pay. Check we preserved all substantive info: specialty, discipline, location, start date, duration, hours, employment type, requirements (license, certifications, residence, experience), schedule details, company description. Yes. We omitted "Current Nebraska license and AHA BLS and ACLS required and additional certifications related to this specialty." We captured that. We omitted "To qualify for this travel assignment, the candidate's primary residence must be located at least 50 miles from the facility address." captured. We omitted "Required: 2 years of recent experience in PCU." captured. We omitted "This shift is 3x12 Nights." captured in schedule. We omitted "36 hours per week" captured. We omitted "Shift: 12 hours, nights" captured. We omitted "Start Date: 10/12/2026" captured. We omitted "Duration: 13 weeks" captured. We omitted "Employment Type: Travel" captured. We omitted "Cure Healthcare is seeking a RN - PCU for positions in Omaha, Nebraska." captured in About the role. We omitted "About Cure Healthcare Staffing" description captured. We omitted phone number and website? Those are contact info; maybe considered metadata but could be considered substantive. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Phone number and website could be considered minor metadata; we could drop them or include in a short

  . The rule says preserve ALL substantive information; phone and website could be considered substantive for contacting. However they might be considered contact info, not strictly required. The instruction about minor metadata: fold minor metadata into a short

  or drop it. So we could include a short

  with contact info. But we already have a paragraph about company; we could add contact info there. However we must not include application instructions. Phone number and website are not application instructions. So we