Travel Nurse RN - ED - Emergency Department - $2,489 per week

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Let's parse the posting. Job description: "Trustaff is seeking a travel nurse RN ED - Emergency Department for a travel nursing job in Olympia Fields, Illinois." Then "Job Description & Requirements" heading. Specialty: ED - Emergency Department Discipline: RN Start Date: ASAP Duration: 13 weeks 36 hours per week Shift: 12 hours, nights Employment Type: Travel Then description: "As an Emergency Room RN, you'll provide care for patients requiring emergency attention due to illness or trauma. One of the most critical parts of the Emergency RN job is performing a focused assessment of each patient and triaging them appropriately. ER nurses must be able to recognize and effectively treat life-threatening conditions, so be ready to work as part of a close-knit team in a fast-paced environment." Then "Trustaff Job ID #2178276. 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: Emergency Room" Then "About Trustaff" paragraph. Then bullet list of reasons: "Priority access to thousands of travel nursing jobs", "Industry-leading pay", "Guaranteed weekly hours", "Experienced recruiters", "Comprehensive benefits, including medical, dental, and vision", "401k with employer match", "Assistance with travel, compliance, and housing", "Great bonuses for completions, referring friends, and more" Then "Benefits" list: "Weekly pay", "Guaranteed Hours", "Wellness and fitness programs", "Referral bonus", "Medical benefits", "Dental benefits", "Vision benefits" We need to extract sections. We need to avoid repeating job title as heading. So no heading for "Emergency Room". Use

for sections. We need to decide which sections have content. - About the role: Could be the description of role: "As an Emergency Room RN, you'll provide care..." That's prose. So we can put that under

About the role

with

. - Responsibilities: Could be the duties: "provide care for patients requiring emergency attention due to illness or trauma", "performing a focused assessment of each patient and triaging them appropriately", "recognize and effectively treat life-threatening conditions", "work as part of a close-knit team in a fast-paced environment". That's responsibilities. - Requirements: Could be specialty, discipline, shift, hours, etc. The posting includes Specialty, Discipline, Start Date, Duration, 36 hours per week, Shift, Employment Type. Those could be requirements/qualifications. We need to decide if we have enough for Requirements and Qualifications separate. Usually Requirements = mandatory qualifications (license, experience). Qualifications = preferred? Not given. Might combine. But we need to follow instruction: include a section ONLY when posting has real, specific content for it. So we can have sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Possibly Qualifications if we have specifics like RN license, etc. Not given explicitly but implied RN discipline. Could treat that as Requirements. Pay: "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 amount. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Pay package based on 12 hour shifts and 36 hours per week with tax-free stipend amount to be determined. That's still some info about pay structure, though amount TBD. Is that considered "real, specific content"? It says "tax-free stipend amount to be determined." That's not specific. The rule: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here we have "tax-free stipend amount to be determined." That's similar to TBD. So we should not create a Pay section because it's placeholder. However we have shift and hours info which could go to Schedule. Schedule: we have Shift: 12 hours, nights; 36 hours per week. That's specific. So we can create Schedule section. Benefits: we have a list of benefits: Weekly pay, Guaranteed Hours, Wellness and fitness programs, Referral bonus, Medical benefits, Dental benefits, Vision benefits, plus earlier list: Comprehensive benefits including medical, dental, vision; 401k with employer match; Assistance with travel, compliance, housing; Great bonuses for completions, referring friends, etc. So we have specific benefits. So we can create Benefits section. Now About the role: we have description. Responsibilities: we have bullet points. Requirements: we have Specialty: ED - Emergency Department; Discipline: RN; Start Date: ASAP; Duration: 13 weeks; 36 hours per week; Shift: 12 hours, nights; Employment Type: Travel. Those could be considered requirements. However some of those (shift, hours) also go to Schedule. But we can still include them in Requirements as qualifications like specialty, discipline, start date, duration, employment type. We'll keep schedule separate. Qualifications: maybe we don't have extra beyond requirements. Could omit. Skills: not explicitly listed. Could infer but not given. So omit. Now we need to output HTML fragment only, no /. Use

for each section heading. Use

• for lists. Use

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. Let's gather content. About the role: "As an Emergency Room RN, you'll provide care for patients requiring emergency attention due to illness or trauma. One of the most critical parts of the Emergency RN job is performing a focused assessment of each patient and triaging them appropriately. ER nurses must be able to recognize and effectively treat life-threatening conditions, so be ready to work as part of a close-knit team in a fast-paced environment." That's from the posting. Responsibilities: Could be same as above? Actually that is description of role. Might be better to split: Responsibilities: provide care for patients requiring emergency attention due to illness or trauma; perform focused assessment of each patient and triage appropriately; recognize and effectively treat life-threatening conditions; work as part of a close-knit team in a fast-paced environment. We can list those as

  . Requirements: Specialty: ED - Emergency Department; Discipline: RN; Start Date: ASAP; Duration: 13 weeks; Employment Type: Travel. Also maybe mention 36 hours per week? But that goes to schedule. We'll keep schedule separate. Schedule: Shift: 12 hours, nights; 36 hours per week. Benefits: List: Weekly pay; Guaranteed Hours; Wellness and fitness programs; Referral bonus; Medical benefits; Dental benefits; Vision benefits; Comprehensive benefits including medical, dental, vision (but that's duplicate); 401k with employer match; Assistance with travel, compliance, and housing; Great bonuses for completions, referring friends, and more. We need to avoid duplication. We'll combine unique items. Let's list unique benefits: - Weekly pay - Guaranteed Hours - Wellness and fitness programs - Referral bonus - Medical benefits - Dental benefits - Vision benefits - 401k with employer match - Assistance with travel, compliance, and housing - Great bonuses for completions, referring friends, and more We could also include "Industry-leading pay" but that's more about pay, not benefit. Already we have weekly pay. Now ensure we don't include placeholder text. Now construct HTML. We'll have:

  About the role

  As an Emergency Room RN, you'll provide care for patients requiring emergency attention due to illness or trauma. One of the most critical parts of the Emergency RN job is performing a focused assessment of each patient and triaging them appropriately. ER nurses must be able to recognize and effectively treat life-threatening conditions, so be ready to work as part of a close-knit team in a fast-paced environment.

  Responsibilities

  • Provide care for patients requiring emergency attention due to illness or trauma
  • Perform a focused assessment of each patient and triage appropriately
  • Recognize and effectively treat life-threatening conditions
  • Work as part of a close-knit team in a fast-paced environment

  Requirements

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

  Schedule

  • Shift: 12 hours, nights
  • 36 hours per week

  Benefits

  • Weekly pay
  • Guaranteed Hours
  • Wellness and fitness programs
  • Referral bonus
  • Medical benefits
  • Dental benefits
  • Vision benefits
  • 401k with employer match
  • Assistance with travel, compliance, and housing
  • Great bonuses for completions, referring friends, and more
  We should not include Pay section because it's placeholder. Check if any content missing: The posting also mentions "Trustaff Job ID #2178276." That's minor metadata; we can drop or fold into short p. Instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. We can drop it. Also "Posted job title: Emergency Room" - we drop as not heading. Also "About Trustaff" paragraph: we could incorporate into About the role? Actually About Trustaff is about the company, not role. Could be a separate section like "About the company". But we only have predefined headings list; we could put under About the role? Might be misrepresenting. However instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those headings. The "About Trustaff" paragraph is not exactly about the role but about the company. Could we treat it as "About the role"? Not accurate. But we could omit it because it's not required to include all content? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we must include that info somewhere. If we don't have a heading for it, we could incorporate it into a

  under About the role? That would be mixing role description with company info, but still preserving. However the heading would be "About the role" but content includes company info. Might be okay but could be considered misrepresenting. Another option: we could create a custom heading like "About Trustaff" but instruction says use those headings as examples, not strictly limited? It 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 we should likely stick to those. However we could add another heading like "About the company" if we want, but not in the list. Safer to stick to given headings and fold the Trustaff paragraph into About the role or maybe into Responsibilities? Not ideal. We could