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

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invented details. Must remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Also must not include sections with filler like "commensurate with experience". Must only include sections where posting has real specific content. Let's parse the posting: - Job: Travel nurse RN Long Term Acute Care in Indianapolis, Indiana. - Specialty: Long Term Acute Care - Discipline: RN - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, days - Employment Type: Travel - Description: immediate travel opening in LTAC facility. RN should have at least 1 year recent experience in LTAC or similar high acuity setting. As RN in LTAC, you will care for patients with serious medical conditions requiring 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 interdisciplinary team to support patient recovery and discharge planning. As an RN, you should be prepared to perform the following tasks: (list tasks) - 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. RNs in LTAC should be adaptable, highly skilled in critical care practices, and passionate about supporting patients through complex and prolonged recovery. - Requirements*: BLS, ACLS, 2 Years * Additional certifications may be required before beginning an assignment. - TotalMed RN Job ID #1500316. 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: Long Term Acute Care - LTAC RN - Travel Nurse - About TotalMed RN: description of agency. - Benefits: list: 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. We need to decide sections. We have: - About the role: could include description of role, duties, responsibilities. Could combine responsibilities and description. - Responsibilities: list of tasks. - Requirements: experience, certifications, licensure. - Qualifications: maybe same as requirements? But we need to avoid duplication. The posting includes "Requirements*: BLS, ACLS, 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. Additional certifications may be required." So we can combine. - Skills: maybe mention adaptable, highly skilled in critical care practices, passionate about supporting patients. Could be a Skills section. - Benefits: list. - Pay: mention pay package based on 12 hour shifts and 36.0 hours per week, tax-free stipend amount to be determined. This is somewhat vague but it's actual content: "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 specific enough? It mentions pay package based on shifts and hours, stipend TBD. It's not a specific number but it's still content. The rule: do NOT 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 TBD. Also "subject to confirmation". This might be considered placeholder. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay package based on 12 hour shifts and 36.0 hours per week, with tax-free stipend amount to be determined. That's stating something, albeit with TBD. Is that considered filler? The phrase "tax-free stipend amount to be determined" is TBD. The rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So if we include Pay section, we would have placeholder text. Might be better to omit Pay section because it's not concrete. However, the rule also says: Prefer a few substantive sections over many thin ones. If we omit Pay, we lose that info. But maybe we can incorporate pay info into About the role or Responsibilities? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep the pay info somewhere. If we omit Pay heading, we could put it in a paragraph under About the role or maybe under a generic section like "Details". But we only allowed headings from the list. Could we add a

without heading? Yes, we can output HTML fragment with paragraphs and lists, not necessarily under headings. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can use those headings when we have content. It doesn't forbid having paragraphs outside headings. So we could include a paragraph about pay without a heading, or we could include a Pay heading but ensure we don't have placeholder text. However, the pay info includes "tax-free stipend amount to be determined" which is TBD. That's placeholder. Might be considered filler. Better to avoid Pay heading and instead include the pay info as a paragraph under About the role or maybe under a generic "Details" paragraph. But we must not invent headings. We can just put a

with that info. Similarly Schedule: we have shift: 12 hours, days; duration: 13 weeks; 36 hours per week. That's specific schedule info. So we could have a Schedule section with those details. That's substantive. Benefits: we have a list of benefits, specific. So Benefits section. Now, we need to decide which sections to include: About the role (description), Responsibilities (list of tasks), Requirements (experience, certifications, licensure), Skills (adaptable, highly skilled in critical care practices, passionate), Benefits (list), Schedule (duration, shift, hours). Possibly also Qualifications? Could combine Requirements and Qualifications. But we have both Requirements and Qualifications as possible headings. The posting includes "Requirements*" and also earlier description of ideal candidate. Could treat Requirements as the list (BLS, ACLS, 2 Years) and Qualifications as the experience and licensure. But to avoid duplication, we could have Requirements section covering experience, certifications, licensure, and maybe Skills section for adaptable etc. Or we could have Qualifications for experience and licensure, Requirements for certifications. However, the instruction: Prefer a few substantive sections over many thin ones. So maybe combine into one Requirements section that includes experience, certifications, licensure, and note about additional certifications. Then Skills section for adaptable etc. That seems reasonable. We must not repeat the job title as heading. So no heading for "Long Term Acute Care - LTAC RN - Travel Nurse". Good. We must not put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can drop the Job ID line entirely, or put it in a short paragraph if we want to preserve info. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The Job ID is metadata but maybe not substantive? It's an identifier. Could be considered minor metadata. We can drop it. The instruction says fold minor metadata into a short

or drop it. So we could drop it. Also we must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes "About TotalMed RN" which is not boilerplate; it's description of agency. That's substantive? It's about the company. Might be considered relevant but not required. The instruction: "Prefer a few substantive sections over many thin ones." The About TotalMed RN is a description of the agency; could be included as a section maybe "About the company". But not in the allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could put the TotalMed description under About the role? Or maybe we could add a paragraph without 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 suggests to use those for sections. Probably we should stick to those headings. So we can incorporate the TotalMed description into About the role paragraph (makes sense: about the role and the agency). Or we could add a separate paragraph without heading. We need to preserve ALL substantive information. The TotalMed description is substantive about the agency. If we omit it, we lose info. So we should include it somewhere. Perhaps we can include a short paragraph under About the role that includes both role description and agency info. Or we could add a heading "About TotalMed RN" but that's not in the allowed list; but the instruction says use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." implies those are examples, not an exhaustive list. However, to be safe, we could still use a heading like

About TotalMed RN

. 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 it's implied to use those for sections. Safer to stick to those. We can put the TotalMed description in a

without heading, maybe after the About the role heading. Thus structure:

About the role

... description of role, agency info ...

Responsibilities

• ... tasks ...

Requirements

• ... experience, certifications, licensure ...

Skills

• ... adaptable, highly skilled in critical care practices, passionate about supporting patients ...

Benefits

• ... list ...

Schedule

... duration, shift, hours ...

Optionally include Pay info as a paragraph under About the role or Schedule? Pay is separate. Could add a

about pay after Schedule heading or under About the role. Since we have no Pay heading (to avoid placeholder), we can just add a

with pay info. We must not include any filler like "tax-free stipend amount to be determined" if we consider that placeholder. But it's actual info: stipend amount TBD. It's still info, albeit TBD. The rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). It doesn't forbid having placeholder text in a paragraph; it's about headings followed by filler. So