Travel Home Health Registered Nurse - Make $2,478 to $2,674/week

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. First, I need to identify the sections that have real, specific content. The job posting has: - Job details (pay, assignment length, shift, schedule, openings, start date, charting system) - Requirements (experience, certifications & skills, licensure, travel experience) - Facility & Unit Information (facility type, compact license accepted, charting experience) - Aya Delivers section (benefits, support, etc.) Rules: - Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use

• for lists,

  for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) - Include section ONLY when posting has real, specific content for it - Never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment — no /, no markdown code fences Now, let's map the content to appropriate sections. The posting has: - Pay: $2478 to $2674 weekly (specific) - Schedule: 5, 8-Hour 08:00 - 16:30 (specific) - Assignment Length: 13 weeks - Shift: Days - Start Date: 11/30/2026 - Charting System: Epic - Openings: 1 These could go under "Job Details" or "Pay" and "Schedule" sections. Since the rules mention Pay and Schedule as possible headings, and the posting has specific info for both, I should include them. Requirements section: Experience, Required Certifications & Skills, Licensure, Travel Experience Required. This fits "Requirements" or "Qualifications". The rules mention "Requirements" and "Qualifications" as possible headings. I'll use "Requirements" for the list of required experience, certifications, skills, licensure. Facility & Unit Information: Facility Type, Compact License Accepted, Charting Experience. Could be part of "About the role" or separate. Might be "Facility Information". Aya Delivers: This is essentially benefits and perks. The posting lists: exceptional benefits including premium medical, dental, vision, life insurance day one; keep insurance coverage up to 24 days between assignments; 401(k) match; paid company housing or housing stipend; paid sick time; unlimited CEUs; licensure, relocation reimbursements; pay includes taxable wages and tax-free expense reimbursements. This is a Benefits section. Also there is a note about pay including taxable wages and tax-free expense reimbursements. That could be in Pay section. The posting also has "Aya Healthcare has an immediate opening..." and "We'll work with you to build the healthcare career of your dreams..." which is marketing fluff. Should I include? The rules say preserve ALL substantive information. That's more marketing, but it's part of the posting. However, the rules say remove boilerplate. This might be considered boilerplate. But it's specific to Aya. I think we can include a brief "About the Company" or "About Aya Healthcare" section? The rules don't mention that heading. The allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About the role" could be used for the introductory paragraph. But the rule says "Do NOT repeat the job title as a heading (the page already shows it)". The introductory paragraph is not the job title. It's a description. Could be "About the role". However, the posting doesn't have a clear "About the role" section; it's just a marketing blurb. Might be better to omit or include as a short paragraph under a heading? The rules say include a section ONLY when the posting has real, specific content for it. The marketing blurb is not specific to the role; it's generic. I'd omit it. Also, there are hashtags at the end: #HP #HNHomeHealthRN. That's metadata, drop. Now, let's structure: Possible sections: 1. Pay (specific weekly range) 2. Schedule (specific shift and hours) 3. Job Details (assignment length, start date, charting system, openings) - but maybe combine with Pay and Schedule? The rules have separate Pay and Schedule headings. Could have a "Job Details" heading for the rest. But the rules list "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". "Job Details" is not listed, but "About the role" could cover it. However, "About the role" is more about description. I think we can create a "Job Details" heading? The rules say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." suggests those are examples, not exhaustive. But we should prefer those. However, "Job Details" is not in the list. Could use "About the role" for the details like assignment length, shift, schedule, start date, charting system. But Pay and Schedule are separate headings. So maybe: - Pay - Schedule - Requirements - Benefits - Facility Information (or "Facility & Unit Information") But the rules say "Prefer a few substantive sections over many thin ones." So maybe combine some. Let's see: The posting has distinct categories: Job Details (pay, schedule, assignment length, shift, start date, charting system, openings), Requirements, Facility & Unit Information, Aya Delivers (benefits). I'll create sections for each that has substantial content. I'll use: - Pay (since specific) - Schedule (since specific) - Job Details (for assignment length, start date, charting system, openings) - but maybe "Assignment Details" or "Position Details". The rules don't forbid custom headings, but they gave examples. I'll use "Position Details" as an h3. - Requirements (for experience, certifications, skills, licensure, travel experience) - Facility Information (for facility type, compact license, charting experience) - Benefits (for the Aya Delivers benefits) Now, ensure no filler. Each section must have real content. Let's write HTML. First, Pay section:

  Pay

  $2,478 to $2,674 weekly (includes taxable wages and tax-free expense reimbursements).

  Schedule:

  Schedule

  Days, 5 × 8-hour shifts (08:00–16:30).

  Position Details:

  Position Details

  • Assignment length: 13 weeks
  • Start date: 11/30/2026
  • Charting system: Epic
  • Openings: 1
  Requirements:

  Requirements

  • Experience: 1 year
  • Required certifications: BLS
  • Licensure: Missouri license or Compact license (quick license state, application process takes 2 weeks or less)
  • Travel experience required: Yes
  • Skills: Admission Assessment, Adult Home Health, Feeding tube care and management, Intravenous infusions, OASIS, Phlebotomy skills, Clinical assessment documentation, Routine visit, Wound care, Wound V.A.C. management
  Facility Information:

  Facility Information

  • Facility type: Hospice
  • Compact license accepted: Yes
  • Charting experience required: Yes
  Benefits:

  Benefits

  • Premium medical, dental, vision, and life insurance beginning day one of assignment
  • Option to keep insurance coverage for up to 24 days between assignments
  • Generous 401(k) match
  • Paid company housing (pet-friendly) or generous housing stipend, if eligible
  • Paid sick time in accordance with applicable laws (accrual: 1 hour per 30 hours worked)
  • Unlimited continuing education units (CEUs) online
  • Licensure, relocation, and other reimbursements when applicable
  Also note: "Aya Delivers" includes some marketing points like "most jobs in the industry", "front-of-the-line access", "expedited licensing", "expert career guidance", "best-in-class support system". These are not benefits per se, but could be included in Benefits or a separate "Why Aya" section. However, the rules say preserve ALL substantive information. But they also say remove boilerplate. The "Aya Delivers" section is essentially a list of selling points. Some are benefits (insurance, 401k, housing, sick time, CEUs, reimbursements). Others are about the agency's advantages. I think we can include them in Benefits or a separate "Agency Benefits" section. But the rules say "Benefits" heading. I'll include the tangible benefits in Benefits, and maybe the other points in a "Why Choose Aya" section? But that might be too many thin sections. The rules say prefer few substantive sections. I'll incorporate the agency advantages into a "Benefits" section as bullet points, but they are not traditional benefits. However, the posting lists them under "Aya Delivers". I'll include them as part of Benefits, but separate with a sublist? Better to keep as separate bullets. Let's include all bullet points from Aya Delivers that are substantive. From Aya Delivers: - The most jobs in the industry... (marketing) - Competitive advantage... front-of-the-line access... (marketing) - Expedited licensing and streamlined compliance... (marketing) - Expert career guidance... (marketing) - Best-in-class support system... (marketing) - Exceptional benefits, including premium medical, dental, vision and life insurance beginning day one... (benefit) - Keep insurance coverage for up to 24 Days between assignments (benefit) - Generous 401(k) match (benefit) - Paid company housing... or housing stipend (benefit) - Paid sick time... (benefit) - Access to unlimited continuing education units online (benefit) - Licensure, relocation and other reimbursements (benefit) - Pay listed above includes taxable wages and tax-free expense reimbursements (already in Pay) I'll include the tangible benefits in Benefits section. The marketing points are not specific to this job; they are generic agency claims. The rules say remove boilerplate. This might be considered boilerplate. But it's part of the posting. However, the user said "Preserve ALL substantive information". The marketing points are not substantive for the job itself. I'll omit them. Thus, Benefits section will have the tangible benefits. Now, check for any other sections: "Responsibilities" not listed. The posting doesn't have explicit responsibilities. So no Responsibilities section. "Skills" is part of Requirements. "Qualifications" similar to Requirements. I'll use Requirements. Now, ensure no duplicate info. Also, the posting mentions "Charting Experience: Yes" under Facility & Unit Information