PDN LPN/RN HOMECARE

The user wants me to convert this job posting into clean semantic HTML following specific rules. Let me analyze the content and structure it properly. First, I need to identify the sections: - Overview (with employment type, schedule, setting, patient population, care type) - Key Responsibilities (list of duties) - What We Offer (benefits/perks) - Qualifications (requirements) - Why Choose Private Duty Nursing? (more benefits/reasons) - Optional Enhancements (pay range, shift differentials, benefits, sign-on bonus) - Maxim Benefits (detailed benefits) - About Maxim Healthcare (company info) But I must follow rules: only include sections with real specific content, no filler. Use h3 for section headings, ul/li for lists, p for prose. Don't repeat job title as heading. Don't include Job ID/requisition numbers. Remove boilerplate (EEO, equal opportunity, etc.). No Pay/Schedule/Benefits sections unless explicitly stated. Looking at the content: - "Overview" has specific details: Employment Type, Schedule, Setting, Patient Population, Care Type. This could be a section. - "Key Responsibilities" has a list of duties plus skilled care sub-items. Good for ul. - "What We Offer" has a list of perks. Good for ul. - "Qualifications" has a list of requirements. Good for ul. - "Why Choose Private Duty Nursing?" has a list of reasons. Could be a section. - "Optional Enhancements You Can Add" seems like placeholder text? It says "Optional Enhancements You Can Add" and lists examples like hourly pay range, shift differentials, benefits, sign-on bonus. But the posting doesn't actually state these; it's suggesting what you could add. The user says "Preserve ALL substantive information; do NOT invent or summarize away detail." But this section appears to be a template placeholder, not actual offered benefits. However, later there is "Maxim Benefits" with detailed benefits. So maybe "Optional Enhancements" is not actual content but a note to the poster. I should probably skip it because it's not actual offered benefits; it's instructional. The real benefits are in "Maxim Benefits". - "Maxim Benefits" has three subsections: Health and Wellness, Retirement And Financial Security, Lifestyle Benefits. Each with lists. This is substantive. - "About Maxim Healthcare" has company description. Good for a section. Also note: "Benefit eligibility is dependent on employment status." That's a note. The EEO statement at the end should be removed as boilerplate. Now, headings: Use h3 for section headings. The user gave examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections that have real content. Let's map: - Overview -> could be "About the role" or "Overview". The user said use h3 for section headings like "About the role". But the posting has "Overview". I'll use "Overview" as heading. - Key Responsibilities -> "Responsibilities" - What We Offer -> "Benefits" or "What We Offer". The user said "Benefits" is a heading example. But "What We Offer" includes guaranteed hourly pay, consistent assignments, flexible scheduling, supportive supervision, overtime opportunities, meaningful care. That's benefits/perks. Could be "Benefits" or "What We Offer". I'll use "What We Offer" as it's in the posting. - Qualifications -> "Qualifications" or "Requirements". The user said "Requirements" and "Qualifications" are examples. I'll use "Qualifications". - Why Choose Private Duty Nursing? -> "Why Choose Private Duty Nursing?" or "Benefits". It's more reasons to choose. Could be a section. - Maxim Benefits -> "Benefits" (detailed). But we already have "What We Offer". Might be redundant. However, "Maxim Benefits" is more detailed and specific (health, retirement, lifestyle). The posting includes both. I think we should include both but maybe combine? The user says "Prefer a few substantive sections over many thin ones." But both have substantive content. "What We Offer" is more about the role perks, "Maxim Benefits" is company benefits. They are different. I'll keep both. - About Maxim Healthcare -> "About Maxim Healthcare" or "About the Company". Use "About Maxim Healthcare". Also, "Optional Enhancements You Can Add" seems like a template note, not actual content. I'll omit it. Now, for each section, use p for prose, ul/li for lists. Let's structure:

Overview

Employment Type: Full-Time, Part-Time, or PRN

Schedule: Flexible shifts (day, night, weekend options available)

Setting: Patient’s home

Patient Population: Pediatric to Geriatric

Care Type: One-on-one continuous care

But the user said "Use

• for any list of duties/requirements/benefits, and

  for prose." The overview items are key-value pairs, not a list of duties. Could be a list. But they are not bullet points in the original; they are lines. I'll use a list for clarity. Actually, the original has "Overview" then lines. I'll make it a list.

  Overview

  • Employment Type: Full-Time, Part-Time, or PRN
  • Schedule: Flexible shifts (day, night, weekend options available)
  • Setting: Patient’s home
  • Patient Population: Pediatric to Geriatric
  • Care Type: One-on-one continuous care
  Then "Key Responsibilities" -> "Responsibilities"

  Responsibilities

  • Provide direct, individualized nursing care tailored to each patient
  • Monitor patient condition and report changes
  • Administer medications and treatments as prescribed
  • Assist with activities of daily living (as appropriate)
  • Skilled care may include:
    • Tracheostomy (trach) care
    • Ventilator support (if applicable)
    • Feeding tubes and nutritional support
    • Wound care
    • Diabetic management
  • Educate patients and families on care plans
  • Maintain accurate and timely documentation
  Note: The skilled care items are sub-items. I'll nest a ul. "What We Offer" -> "What We Offer"

  What We Offer

  • Guaranteed hourly pay (not per visit)
  • Consistent assignments – build relationships with your patients
  • Flexible scheduling to fit your lifestyle
  • Supportive clinical supervision and training
  • Opportunities for overtime and long shifts
  • Meaningful, hands-on patient care in a low-ratio environment
  "Qualifications" -> "Qualifications"

  Qualifications

  • Active RN or LPN license (state-specific)
  • Experience in private duty, home health, pediatric, or critical care preferred
  • Comfort with hands-on patient care and long-duration shifts
  • Experience with trach, vents, or skilled care is a plus (training may be available)
  • Current CPR certification
  • Reliable transportation
  • Compassionate, dependable, and patient-focused
  "Why Choose Private Duty Nursing?" -> "Why Choose Private Duty Nursing?"

  Why Choose Private Duty Nursing?

  • True one-on-one care—no rushed visits or high patient loads
  • Ability to form lasting connections with patients and families
  • Greater focus on quality, comfort, and continuity of care
  • Flexible work-life balance
  "Maxim Benefits" -> "Benefits" (but we already have "What We Offer". The user said "Benefits" is a heading example. I'll use "Benefits" for this section, but note that "What We Offer" is also benefits. However, the posting separates them. I'll keep both but maybe rename "What We Offer" to "Role Benefits" and "Maxim Benefits" to "Company Benefits"? But the user said use headings like "Benefits". I'll use "Benefits" for the detailed benefits section, and "What We Offer" for the role perks. But the user said "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states "What We Offer" and "Maxim Benefits". So both are stated. I'll keep both headings as they appear. But "Maxim Benefits" has subsections: Health and Wellness, Retirement And Financial Security, Lifestyle Benefits. I'll include those as subheadings? The user said use h3 for section headings. Could use h4? But the instruction says use h3 for section headings. It doesn't forbid h4. But to keep simple, I'll make them part of the list or use nested lists. However, they are distinct categories. I'll use h3 for "Benefits" and then maybe h4 for subcategories? But the instruction says "use

  for section headings". It doesn't say not to use h4. But to be safe, I'll keep all top-level sections as h3. For subcategories, I could use strong or just list them as items with bold. But the user wants semantic HTML. I'll use h3 for "Benefits" and then use ul with sub-lists for each category. Let's do:

  Benefits

  Benefit eligibility is dependent on employment status.

  Health and Wellness

  • Medical/Prescription
  • Dental
  • Vision
  • Health Advocacy (company paid if enrolled Medical)
  • Health Advocate Employee Assistance Program

  Retirement and Financial Security

  • Health Savings Account
  • 401(k)
  • Short Term Disability
  • Voluntary Group Life Insurance and Supplemental Accidental Insurance
  • Hospital Expense Protection Plan
  • Critical Illness Insurance
  • Home and Auto Insurance discounts
  • Pet Insurance
  • Legal Benefits

  Lifestyle Benefits

  • Paid Time Off
  • Employee Discount Program
  • Transportation Benefits
  • College Partnership Program
  But the user said "use

  for section headings". Using h4 might be okay, but they didn't explicitly forbid. However, they said "Output ONLY the HTML fragment — no /, no markdown code fences." They didn't restrict heading levels. I think using h4 for subsections is fine. But to be safe, I could make them part of the list with strong labels. But semantic HTML would use headings. I'll use h4. Alternatively, I could make each category a separate h3 section: "Health and Wellness Benefits", "Retirement and Financial Security Benefits", "Lifestyle Benefits". But that might be too many thin sections. The user said "Prefer a few substantive sections over many thin ones." So grouping under one "Benefits" section with subheadings is better. I'll use h3 for "Benefits" and h4 for subcategories. Now "About Maxim Healthcare" -> "About