Travel ED RN - $2,240 per week

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Let's parse the posting: - Job: travel nurse RN ED - Emergency Department in Lafayette, Colorado. - Specialty: ED - Emergency Department - Discipline: RN - Duration: 13 weeks - 36 hours per week - Shift: 12 hours - Employment Type: Travel - Description: ER nurses provide care for patients requiring emergency attention because of physical trauma or acute illness. ER nurses work to quickly assess the needs of each patient to avoid long-term complications, disabilities, or even death. - Benefits listed: *$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 - Job ID #877227 (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. (Pay info: not specific amount, just based on shifts/hours, tax-free stipend TBD. This is vague; we should not create Pay section unless posting actually states them. 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 pay amount; it's vague. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits we have specific items, so we can include Benefits. Pay: not specific amount, so we should not include Pay section. Schedule: we have shift 12 hours, 36 hours per week, duration 13 weeks. That's schedule info. Should we include Schedule section? The rule: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here schedule specifics: 12 hour shifts, 36 hours per week, 13 weeks duration. That's specific. So we can include Schedule section. - About Stability Healthcare: description of agency, mission, etc. That could be About the role? Actually About the role is about the job, not agency. But we could use About the role for description of role/responsibilities. The posting includes a description of ER nurses responsibilities. That could go under Responsibilities. Also we have Requirements? Not explicit beyond specialty, discipline, duration, hours, shift. Those could be Requirements or Qualifications. We need to decide. We have: Specialty: ED - Emergency Department, Discipline: RN, Duration: 13 weeks, 36 hours per week, Shift: 12 hours, Employment Type: Travel. Those are job requirements/qualifications. Could put under Requirements. Responsibilities: description of ER nurses duties. Benefits: list of benefits. Schedule: shift details. We should not include About the role if we already have Responsibilities. But we could include About the role as a brief summary. However rule: prefer a few substantive sections over many thin ones. So we can combine. Let's decide sections: - Responsibilities (description of ER nurse duties) - Requirements (specialty, discipline, duration, hours, shift, employment type) - Benefits (list) - Schedule (shift details) maybe redundant with Requirements? Actually schedule includes shift length, weekly hours, duration. Could be part of Requirements but we can separate. But we must not repeat info. Let's see: Requirements could include specialty, discipline, duration, employment type. Schedule could include shift hours, weekly hours, length. That's okay. We need to use

for section headings. Use

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

  for prose. We must not include Job ID, navigation, boilerplate, EEO, etc. We must preserve all substantive information. Let's extract: Responsibilities: - ER nurses provide care for patients requiring emergency attention because of physical trauma or acute illness. - ER nurses work to quickly assess the needs of each patient to avoid long-term complications, disabilities, or even death. That's two sentences. Could be a

  or list. Since it's prose, we can use

  . Requirements: - Specialty: ED - Emergency Department - Discipline: RN - Duration: 13 weeks - Employment Type: Travel (Weekly hours and shift are schedule, not requirement.) But we could also include 36 hours per week and 12 hour shift under Schedule. 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 Schedule: - Shift: 12 hours - Hours per week: 36 hours - Duration: 13 weeks We could also mention that pay package based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. Since stipend TBD, we should not include Pay section. Now produce HTML:

  Responsibilities

  ER nurses provide care for patients requiring emergency attention because of physical trauma or acute illness. ER nurses work to quickly assess the needs of each patient to avoid long-term complications, disabilities, or even death.

  Requirements

  • Specialty: ED - Emergency Department
  • Discipline: RN
  • Duration: 13 weeks
  • Employment Type: Travel

  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

  Schedule

  • Shift: 12 hours
  • Hours per week: 36 hours
  • Duration: 13 weeks
  Check for any duplicate: Duration appears both in Requirements and Schedule. That's duplication. We should avoid repeating same info. The rule: Preserve ALL substantive information; do NOT invent or summarize away detail. But we can avoid duplication by placing duration only once. Where does it belong? Duration is more like schedule (length of contract). Could be under Schedule. Requirements could exclude duration. Let's move duration to Schedule only. Thus Requirements: Specialty, Discipline, Employment Type. (maybe also note travel nurse RN ED). But we already have specialty. Let's adjust. Requirements: - Specialty: ED - Emergency Department - Discipline: RN - Employment Type: Travel Schedule: - Shift: 12 hours - Hours per week: 36 hours - Duration: 13 weeks Now we have no duplicate. Check if any other info: Posted job title: ERA (maybe irrelevant). Not needed. About Stability Healthcare: description of agency. Could be a section About the company? Not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could put agency description under About the role? Actually About the role is about the job, not agency. But we could use About the role to include a brief summary of the role and agency? Might be stretching. Better to omit agency description because not covered by allowed headings? The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, not exclusive? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those headings. Agency description doesn't fit any of those. Could we put it under About the role? Possibly as a brief description of the role within the agency. But the agency description is about the company, not the role. Might be considered filler. Better to omit it, as it's not required to preserve all substantive information? The instruction says "Preserve ALL substantive information". The agency description is substantive? It's about the company, not the job. Might be considered boilerplate? It's not navigation/legal/EEO, but it's promotional. The instruction didn't explicitly say to remove company description. It said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company description is not those. So we should preserve it. But we need a heading for it. Not in list, but we could use About the role as heading and include both role description and agency info? That might be mixing. Alternatively, we could create a heading "About the role" and put the ER nurse responsibilities there, and then maybe another heading "About the company"? Not allowed. But maybe we can treat "About the role" as the place for any descriptive prose about the role and the company. The responsibilities are already there. Could add agency description as a paragraph under About the role. That would preserve info. Let's do:

  About the role

  Stability Healthcare is seeking a travel nurse RN ED - Emergency Department for a travel nursing job in Lafayette, Colorado. Stability Healthcare was founded in 2009, with the mission of becoming the best Travel Nursing Agency in California. We have been rated one of the top travel nursing agencies and offer our nurses the highest paying travel nursing jobs available. We have access to the best travel assignments from 1000’s of facilities. You can start the year off in sunny California, spend the Spring in the Colorado Rockies, enjoy the Summer in the Mid-West, experience the change of seasons in Boston and New York, and hit the beaches of Florida in the winter. Our Nurses work in the best hospitals and health systems in the country.

  Then Responsibilities section with the ER nurse duties. But note that the first sentence duplicates the job posting intro. That's okay. Now we have About the role, Responsibilities, Requirements, Benefits, Schedule. Check for any other specifics: Guaranteed HoursBenefits start day 1 (mentioned under Benefits? Actually there is a line "BenefitsGuaranteedHoursBenefits start day 1" seems garbled. Probably means Guaranteed Hours, Benefits start day 1. We have benefits start day 1 already in health insurance line. Guaranteed Hours maybe a benefit? Not sure. The posting includes "BenefitsGuaranteedHoursBenefits start day 1". Could be a formatting error: "Benefits Guaranteed Hours Benefits start day 1". Might refer to guaranteed hours benefit. We have not captured guaranteed hours. We should include if present. The line: "BenefitsGuaranteedHoursBenefits start day 1". Likely means "Benefits: Guaranteed Hours Benefits start day 1". So there is a benefit: Guaranteed Hours (maybe guaranteed hours). And benefits start day 1 (we already have health insurance day 1). We could add a benefit item: Guaranteed hours. Let's add. Thus Benefits list add: Guaranteed hours