Travel Nurse RN - Long Term Acute Care - $1,854 per week

We need to output HTML fragment with sections: headings

for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. From posting: - About the role: description of LTAC RN tasks. That's substantive. - Responsibilities: list of tasks (the bullet list). Could be under Responsibilities. - Requirements: experience, certifications (ACLS, BLS, 2 Years? Actually says "Requirements*: ACLS, BLS, 2 Years * Additional certifications may be required before beginning an assignment." Also earlier: "The ideal candidate must have at least one year of experience as an RN in a Long-Term Acute Care setting. Additionally, they should possess a current BLS certification and be eligible for State licensure." So we have requirements. - Qualifications: maybe same as requirements? Could combine but we need separate sections only if content. Could put Qualifications: maybe "Current RN license, BLS, ACLS, 2 years experience". But we need to avoid duplication. Might put Qualifications separate from Requirements? The instruction: prefer few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one section? But headings are fixed list; we can choose which to include. Could include Requirements and Qualifications both if they have distinct content. Let's see: Requirements list: ACLS, BLS, 2 Years (maybe years experience). Additional certifications may be required. Qualifications maybe: "Current RN license, eligible for State licensure, at least one year recent experience in LTAC or similar high acuity setting." That's also present. Could combine but we need to decide. Better: Use sections: About the role (description), Responsibilities (list of tasks), Requirements (experience, certifications, licensure), Benefits (list), Pay (mention of pay package based on 12 hour shifts and 36 hours per week with tax-free stipend amount to be determined – but that's vague; "tax-free stipend amount to be determined" is not specific; also "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation)". That's not a specific number; it's placeholder. According to rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state pay package based on 12 hour shifts and 36 hours per week, but no actual pay rate. Is that considered substantive? 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 amount; it's vague. The rule says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here "tax-free stipend amount to be determined" is placeholder/TBD. So we should not create Pay section. Schedule: posting says Shift: 12 hours, nights; Duration: 13 weeks; 36 hours per week. That's schedule info. Could we create Schedule section? It has specific shift length, nights, weekly hours, duration. That's substantive. So include Schedule. Benefits: list of benefits: Weekly pay, Guaranteed Hours, Continuing Education, 401k retirement plan, Sick pay, Wellness and fitness programs, Referral bonus, Employee assistance programs, Medical benefits, Dental benefits, Vision benefits, Benefits start day 1. That's substantive. So include Benefits. Now we need to avoid repeating job title as heading. Not include Job ID. We need to output only HTML fragment, no /. Use

for each section heading. Use

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

  for prose. We need to preserve all substantive information. Let's extract content. About the role: The paragraph: "We're looking for Registered Nurses (RNs) for an immediate travel opening in an LTAC (Long-Term Acute Care) facility in Wyandotte, MI. The right RN should have at least 1 year of recent experience in a Long-Term Acute Care or similar high acuity setting. Read below for more requirements. As an RN in LTAC, you will care for patients with serious medical conditions who require extended hospital-level care. These patients often have complex needs such as ventilator support, wound care, or post-ICU recovery. You will be responsible for providing direct nursing care, monitoring patients' conditions, and collaborating with an interdisciplinary team to support patient recovery and discharge planning." That's prose. Could be in

  . Responsibilities: The bullet list after "As an RN, you should be prepared to perform the following tasks:" then list items. We'll put each as

• . Requirements: Combine experience, certifications, licensure. The text: "The ideal candidate must have at least one year of experience as an RN in a Long-Term Acute Care setting. Additionally, they should possess a current BLS certification and be eligible for State licensure. Additional certifications may be required." Then later: "Requirements*: ACLS, BLS, 2 Years * Additional certifications may be required before beginning an assignment." There's some conflict: 1 year vs 2 Years. We need to preserve all substantive information; we should include both statements. Could combine: "At least one year of recent experience in LTAC or similar high acuity setting; current BLS certification; eligible for state licensure; ACLS preferred; 2 years experience may be required; additional certifications may be required." We'll keep as list. Qualifications: Might be redundant; maybe we skip Qualifications section to avoid thin. We'll not include Qualifications if we think it's duplicate. But we could include Qualifications with content like "Current RN license, BLS, ACLS, 2 years experience". However that duplicates Requirements. To avoid thin sections, better to combine into Requirements and skip Qualifications. The instruction: Prefer a few substantive sections over many thin ones. So we will include Requirements only, not Qualifications. Skills: Not explicitly listed; we could infer but not given. So skip Skills. Benefits: list as
  . Schedule: include shift details: 12 hour shifts, nights; 36 hours per week; duration 13 weeks. Could also mention employment type Travel. We'll put in

  or

  . Since it's a list of schedule items, we can use
  . Pay: we decided not to include because placeholder. Now ensure we don't include boilerplate like "About TotalMed RN" etc. That's not a section heading we need; but we could include as About the role? Actually "About TotalMed RN" is company description, not role. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About TotalMed RN" is company description; is that considered boilerplate? It's not required to preserve? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The company description might be considered substantive? It's about the agency, not the job. Might be considered boilerplate? It's not navigation/legal/EEO etc. It's about the agency. Could be considered substantive but not required for job posting? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It doesn't say to remove company description. However earlier they said "Prefer a few substantive sections over many thin ones." The company description could be a section like "About the company". But we only have allowed headings list; we could put it under About the role? That's not appropriate. Better to omit it because it's not about the role. The instruction says preserve ALL substantive information; but maybe they consider that as not substantive for the job? It's ambiguous. I'd lean to include it as a paragraph under a section like "About the company" but we don't have that heading. Since we cannot invent headings, we could put it as a

  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 forbid other headings, but says use those for section headings. It doesn't say we cannot have other headings, but we should follow the pattern. Safer to include it as a

  without a heading? But then it's not under a heading; still HTML fragment. Could be okay. However they said "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for sections; we can still have other content not under headings? Probably they expect each section to be one of those headings. So we should not add extra headings. We could incorporate the company description into About the role paragraph? Might be odd but we could add a sentence about the agency. However the About the role currently is about the role; we could extend it to include company description. That would preserve info. Let's do that: In About the role

  , we can include both role description and company info. Thus About the role paragraph: combine the role description and TotalMed RN description. Now we need to ensure we don't repeat job title as heading. Not include. Now produce HTML. Structure:

  About the role

  ... combined text ...

  Responsibilities

  • ...
  ...

  Requirements

  • At least one year of recent experience in a Long-Term Acute Care or similar high acuity setting.
  • Current BLS certification.
  • Eligible for state licensure.
  • ACLS certification (preferred or required).
  • Two years of experience may be required.
  • Additional certifications may be required before beginning an assignment.
  Benefits

• Weekly pay
• Guaranteed Hours
• Continuing Education
• 401k retirement plan
• Sick pay
• Wellness and fitness programs
• Referral bonus
• Employee assistance programs
• Medical benefits
• Dental benefits
• Vision benefits
• Benefits start day 1

Schedule

• 12‑hour night shifts
• 36 hours per week
• 13‑week assignment duration
• Employment type: Travel

We need to ensure we didn't miss any substantive info: The posting also mentions "Posted job title: Long Term Acute Care - LTAC RN - Travel Nurse". That's job title; we should not repeat as heading. Could include as a

maybe under About the role? But we already have role description; we could add that the posted job title is as given. However instruction: do NOT repeat the job title as a heading (the page already shows it). It doesn't forbid including it elsewhere. Could include as a sentence. But it's minor metadata; we could fold into short

or drop it. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we could include job title as a short

maybe under About the role? But we already have a paragraph; we could add a sentence: "Posted job title: Long Term Acute Care - LTAC RN - Travel Nurse." That's minor metadata; okay. Also there is "TotalMed RN Job ID #14