Travel Nurse RN - Long Term Care - $2,026 per week

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: Job description & requirements: Specialty: Long Term Care, Discipline: RN, Start Date: 10/12/2026, Duration: 26 weeks, 36 hours per week, Shift: 12 hours, days, Employment Type: Travel. Then a paragraph about LRS Healthcare (company description). Then Benefits list. Then "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; it's not a specific pay amount, just says based on shifts and tax-free stipend amount to be determined. According to rules: never create Pay/Schedule/Benefits sections unless posting actually states them. For Pay, we have a statement but it'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')". The phrase "tax-free stipend amount to be determined" is placeholder/TBD. So we should not create a Pay section. Schedule: we have shift details: 12 hours, days, 36 hours per week. That's specific schedule info. So we can include a Schedule section with that info. Benefits: we have a list of benefits. So include Benefits section. About the role: we have description of role? The posting includes "Job Description & Requirements" but not detailed duties. It includes specialty, discipline, start date, duration, hours, shift, employment type. That's more metadata. There's also a paragraph about LRS Healthcare (company description). That could be "About the role" or "About the company". The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" containing the description of the role (specialty, discipline, start date, duration, hours, shift, employment type). Could also have "Requirements" but we don't have specific requirements beyond RN license? Not given. So we skip. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include start date, duration, hours per week, shift, employment type, specialty, discipline. Also include the company description paragraph (the repeated paragraph). Benefits list. We must not repeat job title as heading. Do not put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include Job ID in a short paragraph maybe. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes "Adventure is Calling! Apply today!" which is application instruction; we should remove that. Also duplicate benefits list appears twice; we should include only once. We need to output only HTML fragment, no /, no markdown fences. Thus structure:

About the role

Specialty: Long Term Care. Discipline: RN. Start Date: 10/12/2026. Duration: 26 weeks. Hours per week: 36. Shift: 12 hours, days. Employment Type: Travel.

Maybe also include Job ID in a short paragraph after that? Could be separate

Job ID: 2603749

but it's minor metadata; we can fold into a short

. Probably better to include after About the role. Then

Benefits

• Streamlined, simple credentialing process through the LRS Connect App
• Health, Dental, and Vision Insurance
• Life and Disability Insurance
• 401(k) with Employer Match
• Generous Referral Bonus Program
• Employee Assistance Program (EAP)
• Weekly Direct Deposit
• 24/7/365 Support

Then

Schedule

36 hours per week, 12‑hour shifts, days.

We could also include Start Date etc in About the role. Check for any other substantive content: The paragraph about LRS Healthcare (the company description) appears twice; we could include that as "About the company" but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add About the company. The company description is generic; maybe we can incorporate into About the role? The About the role section could include that description as part of role context. But 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

for section headings (e.g. ...)" implying those are examples; we could still use other headings but better to stick to those. The company description is not about the role specifically; it's about the employer. Could be omitted? But we must preserve ALL substantive information; do not invent or summarize away detail. The company description is substantive. Where to put it? Could be placed in a

without a heading, or under a heading like "About LRS Healthcare". But that heading is not in the list; but 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

for section headings (e.g. ...). It might be okay to use other headings as long as they are

. However, to be safe, we could incorporate the company description into a paragraph under About the role or as a separate

without heading. The instruction: "Prefer a few substantive sections over many thin ones." So we could have About the role paragraph include both role specifics and company description. That would preserve the info. Thus About the role

will have a paragraph containing: Specialty, Discipline, Start Date, Duration, Hours per week, Shift, Employment Type, plus the company description paragraph. We need to ensure we don't repeat duplicated lines. The company description appears twice; we include once. Now check for any other substantive content: "Adventure is Calling! Apply today!" is application instruction; remove. Now ensure no filler placeholder text: We have no "commensurate with experience" etc. Now output HTML. Let's craft:

About the role

Specialty: Long Term Care. Discipline: RN. Start Date: 10/12/2026. Duration: 26 weeks. Hours per week: 36. Shift: 12 hours, days. Employment Type: Travel. At LRS Healthcare, we connect skilled nursing and allied health professionals with rewarding opportunities at top healthcare facilities across the country. Whether you're looking to explore a new city, gain experience in a different clinical setting, or take the next step in your career, our specialized recruiters are here to help you find travel assignments that align with your personal goals, professional aspirations, and sense of adventure. From your first conversation to your final day on assignment, you'll have a dedicated team in your corner. Our experienced recruiters, credentialing specialists, payroll professionals, and HR team work together to ensure a smooth, stress-free experience so you can focus on what matters most—caring for patients and making the most of every opportunity. Wherever your journey takes you, LRS Healthcare is here to support you every step of the way.

Benefits

• Streamlined, simple credentialing process through the LRS Connect App
• Health, Dental, and Vision Insurance
• Life and Disability Insurance
• 401(k) with Employer Match
• Generous Referral Bonus Program
• Employee Assistance Program (EAP)
• Weekly Direct Deposit
• 24/7/365 Support

Schedule

36 hours per week, 12‑hour shifts, days.

We might also include Job ID as a short paragraph: maybe after About the role before Benefits. But it's minor metadata; we can fold into a short

. Let's add a

Job ID: 2603749

after About the role. Check if any other metadata like "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." This is placeholder; we should not create Pay section. Could we include that as a note under Schedule? It mentions pay package based on shifts; but it's not specific pay. The rule says never create Pay/Schedule/Benefits sections unless posting actually states them. For Pay, we have a statement but it's vague; it's basically saying pay package based on shifts and stipend TBD. That's not a specific pay amount; it's placeholder. So we should not include Pay section at all. We could mention it in a paragraph under About the role? But that would be adding pay info that is not specific; maybe better to omit because it's not substantive. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The pay statement is substantive? It says pay package based on 12 hour shifts and 36 hours per week with tax-free stipend amount to be determined. That's somewhat substantive but includes TBD. It's not a specific amount; but it's still info about pay structure. However, the rule says never create Pay section unless posting actually states them. It does state something about pay package, albeit vague. But the rule also says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The phrase "tax-free stipend amount to be determined" is TBD. So if we made a Pay section, we would have heading with filler. So we should not create Pay section. We could incorporate the pay statement into a paragraph under About the role or Schedule? But that would still include the TBD phrase. The instruction about filler text is about headings followed by filler text; not about content within paragraphs. So we could include the pay statement in a paragraph, as it's not a heading. However, we must consider if we want to preserve ALL substantive information. The pay statement is substantive albeit vague. I'd include it as a short paragraph maybe under About the role or as its own

without heading. But we already have About the role paragraph; we could add a sentence about pay package. However, the About the role paragraph currently is long; we could add after the company description: "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 preserves the info. But note that we already have Schedule section with hours/shift; the pay statement repeats hours/shift. Might be redundant but okay. Let's add that sentence at end of About the role paragraph. Now final HTML:

About the role

Specialty: Long Term Care. Discipline: RN. Start Date: 10/12/2026. Duration: 26 weeks. Hours per week: 36. Shift: 12 hours, days. Employment