In Home Healthcare LVN - Full-Time

Here's a thinking process: 1. **Analyze User Request:** - **Goal:** Reformat a job posting into clean, well-structured semantic HTML. - **Rules:** - Use `

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

• ` for lists of duties/requirements/benefits - Use `

  ` for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID / requisition numbers as headings - fold minor metadata into short `

  ` or drop it - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions - IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no `/`, no markdown code fences 2. **Analyze the Input Job Posting:** Let me extract the content carefully: "We are seeking compassionate Licensed Vocational Nurses (LVNs) to provide skilled nursing care in home settings. Key Responsibilities Deliver and document patient care according to physician care plans and orders.Assess patient conditions, recognize changes, and report to supervisors or physicians.Educate patients and families on disease management, self-care, and prevention.Maintain accurate documentation of assessments, interventions, and responses.Implement infection control measures and adhere to confidentiality and professional standards.Participate in ongoing education and skill development. Qualifications & Skills Active, unencumbered LPN/LVN license in the practice state (compact licenses transferable within 90 days).Current CPR certification (assistance available post-hire if needed).TB test within last 12 months.Preferred: Six months of recent clinical nursing experience; home health experience is a plus.Reliable transportation, strong attention to detail, excellent communication and time management skills. Physical & Environment Requirements Ability to lift 50 pounds, reposition patients, and perform physical activities like walking, standing, and bending.Effective in diverse environments, with exposure to bodily fluids and infectious agents possible.Must respond appropriately to emergency situations. Additional Details Flexible scheduling options, including days, nights, weekends, full-time, part-time, or PRN shifts.Benefits include health insurance, paid time off, weekly/daily pay, and career advancement opportunities.Work involves electronic documentation via tablets and requires travel to patient homes." Let me break it down by sections/headers that are implicitly or explicitly present: - "Key Responsibilities" -> list of duties - "Qualifications & Skills" -> list of qualifications/skills - "Physical & Environment Requirements" -> list of physical/env requirements - "Additional Details" -> contains scheduling, benefits, work details - There's no explicit "About the role" but there's an opening sentence: "We are seeking compassionate Licensed Vocational Nurses (LVNs) to provide skilled nursing care in home settings." This could be prose under a section or just introductory text. The rules say use `

  ` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). I should map the content to these headings appropriately, but only include sections that have real content. Let's map: - Responsibilities: The "Key Responsibilities" paragraph has 5 bullet-point-like duties. I'll put them in a `

  • `. - Requirements/Qualifications: "Qualifications & Skills" section has license, CPR, TB test, preferred experience, transportation, skills. I'll put in `
    • `. - Physical & Environment Requirements: Explicit section. I'll put in `
      • ` or keep as prose with `

        `. The rules say `

        • ` for lists of duties/requirements/benefits. This is a list of requirements, so `
          • `. - Additional Details: Contains "Flexible scheduling options, including days, nights, weekends, full-time, part-time, or PRN shifts." -> This maps to "Schedule". - "Benefits include health insurance, paid time off, weekly/daily pay, and career advancement opportunities." -> Maps to "Benefits". - "Work involves electronic documentation via tablets and requires travel to patient homes." -> Could be prose under a section or just part of the details. I might fold it into a `

            ` or under Benefits/Schedule, but need to be careful not to create sections with filler. Let's review the heading list allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I need to only create sections when there's real content. Let's see what's present: - Responsibilities: Yes, explicit "Key Responsibilities" with 5 duties. - Qualifications/Requirements: The posting has "Qualifications & Skills" and "Physical & Environment Requirements". I could split or combine. The rules list "Requirements" and "Qualifications" as separate heading examples. I'll likely use "Requirements" for the physical/env and license/cert stuff, and maybe "Qualifications" for the skills/license/experience. But I need to be careful not to create thin sections. Let's see. - Benefits: Explicit "Benefits include health insurance, paid time off, weekly/daily pay, and career advancement opportunities." -> Yes. - Schedule: "Flexible scheduling options, including days, nights, weekends, full-time, part-time, or PRN shifts." -> Yes. - Pay: Not explicitly stated. "weekly/daily pay" is mentioned under Benefits, but not a separate Pay section. The rules say never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits is stated, Schedule is stated. Pay is not explicitly a pay range, just "weekly/daily pay" as a benefit. I'll avoid a Pay section. - About the role: The opening sentence "We are seeking compassionate Licensed Vocational Nurses (LVNs) to provide skilled nursing care in home settings." could be an intro `

            `, but the rules say use `

            ` for section headings (e.g. About the role, Responsibilities, ...). I could either make it a section or just a `

            ` before headings. The rules say "use

            for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say I must have all of them. It says include a section ONLY when the posting has real, specific content for it. The opening sentence is substantive, but is it a section? I'll treat it as a brief intro `

            ` or maybe fold into Responsibilities or just as a lead. To be safe, I'll not create an "About the role" heading unless I can dedicated specific content beyond the opening line. The rules say "never emit a heading followed by filler/placeholder text". The opening line is real content, but I need to see if it's better as a `

            ` or an `

            `. I'll probably just keep it as a `

            ` lead, or omit a separate About section if it's too thin. Actually, the rules list "About the role" as an example of heading format, not a mandate. I'll use headings that have clear content. Let's re-evaluate mapping with strict adherence: - "Key Responsibilities" -> Responsibilities section with `

            • ` - "Qualifications & Skills" -> This combines qualifications and skills. I'll split into "Requirements" (license, certifications, TB test, transportation, skills) and maybe not create a separate "Qualifications" if it overlaps. But the posting has "Qualifications & Skills" as one block. I could make one section "Requirements" that includes both qual and skills, or two sections. The rules say "Prefer a few substantive sections over many thin ones." I'll likely combine into one "Requirements" section, or maybe "Qualifications & Skills" as a heading? But the rules say use headings like "Requirements, Qualifications, Skills". I'll use "Requirements" for the license/cert/TB/transportation/physical, and maybe fold skills into it, or use "Qualifications". Let's see the exact text: "Qualifications & Skills Active, unencumbered LPN/LVN license... Current CPR certification... TB test... Preferred: Six months... Reliable transportation, strong attention to detail, excellent communication and time management skills." This is all under one heading in the posting. I'll create a section called "Requirements" (or "Qualifications") and list them. I think "Requirements" is better since it includes license, certs, and skills. I'll just use "Requirements". - "Physical & Environment Requirements" -> This is explicit. I'll use "Requirements" or maybe keep separate? The rules list "Requirements" as a heading. I'll fold physical into Requirements, or create a separate "Physical Requirements" but the rules say only create sections with real content. I'll include physical/env requirements under the same "Requirements" section, or maybe use "Physical & Environment Requirements" as the heading? The rules say use headings like "Requirements", not "Physical & Environment Requirements" specifically, but I can adapt. To be safe, I'll include them under a "Requirements" section, but the physical ones are quite specific. Actually, I'll make a separate "Physical Requirements" section if it has content, but the rules say "Prefer a few substantive sections over many thin ones." Having maybe 4 sections is better than 7 thin ones. Let's target: Responsibilities, Requirements (covering qual/skills/physical), Benefits, Schedule. That's 4 sections. That seems good. Let's map carefully: - Responsibilities: 5 duties from "Key Responsibilities" - Requirements: Includes license, CPR, TB test, preferred experience, transportation, communication skills, AND physical requirements (lift 50 lbs, reposition, walking/standing/bending, exposure to bodily fluids, emergency response). I'll list all as `
              • ` items. - Benefits: health insurance, PTO, weekly/daily pay, career advancement - Schedule: flexible scheduling, days/nights/weekends, full-time/part-time/PRN Wait, the rules say: "Use

                for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This implies I should use these exact labels or similar, but only when content exists. It also says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

                or drop it." There's no job ID or requisition number in the input, good. Also: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them." So I must not create a Pay section since there's no actual pay range, just "weekly/daily pay" under Benefits. I'll create Benefits and Schedule since they are stated. Let's re-read the "Additional Details" part: "Flexible scheduling options, including days, nights, weekends, full-time, part-time, or PRN shifts. Benefits include health insurance, paid time off, weekly