Private Duty Nurse LVN - Weekend Days

Here's a thinking process: 1. **Analyze User Input:** - Input is a job posting fragment for a Licensed Practical / Vocational Nurse (LPN/LVN) at a home healthcare provider. - Sections provided: Responsibilities, Qualifications, Key Skills And Benefits. - I need to reformat this into clean, well-structured semantic HTML following specific rules. 2. **Identify Rules & Constraints:** - Use `

` for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. - Use `

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

  ` for prose. - Do NOT repeat the job title as a heading (page already shows it). - Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a 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") and never create Pay/Schedule/Benefits sections unless the posting actually states them. - Prefer a few substantive sections over many thin ones. - Output ONLY the HTML fragment — no `/`, no markdown code fences. 3. **Map Input to Required Structure:** - The input has these natural chunks: * Responsibilities (bullet points) * Qualifications (bullet points/list items) * Key Skills And Benefits (grouped, some are skills/benefits mixed) - I need to decide on section headings from the allowed list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. - The input doesn't have explicit "About the role" prose, but it does have a description: "Providing compassionate, patient-centered care to children and adults in home settings. Ensuring outstanding clinical outcomes through skilled nursing services. Utilizing electronic documentation via tablets in patient homes. Collaborating with a multidisciplinary team to deliver quality care. Participating in career development and skill advancement opportunities." This could go under "About the role" or be integrated. But the rule says "include a section ONLY when the posting has real, specific content for it". The posting does have content about the role, so "About the role" is valid if I use the actual text. - "Responsibilities" section: clear, has bullet points. - "Requirements" vs "Qualifications": The input has "Qualifications" section with bullet points. There's also "Reliable transportation is required" which could be a requirement. I should probably put the explicit qualifications under "Qualifications", and maybe fold reliable transportation into a short `

  ` or under Requirements. The allowed headings include both "Requirements" and "Qualifications". I'll use "Qualifications" for the listed ones, and maybe note transportation as part of a `

  ` if needed, but I need to check if it creates a separate section unnecessarily. The input has "Qualifications" as a clear section. I'll stick with that. - "Skills" and "Benefits": The input has "Key Skills And Benefits" which mixes skills and benefits. I need to separate them or create two sections if there's real content for both. The rules say: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state benefits: "Flexible scheduling options, including full-time, part-time, or PRN shifts, with day, night, and weekend availability. Local support and a supportive workplace culture that values diversity and work-life balance. Competitive benefits such as health, dental, vision, paid time off, weekly/daily pay, and employee stock plans. Opportunities for professional growth and skill development." So Benefits section is valid. Skills are also mentioned: "Key Skills And Benefits" but the actual skill items aren't bullet-pointed separately; they're mixed into the benefits text. I could extract skills or just fold into Benefits. The allowed heading is "Skills". I need to check if there's substantive specific skill content. The responsibilities mention skills implicitly, but not explicit "Skills" section. I think I'll create a "Skills" section only if there's clear skill content. Re-reading: "Key Skills And Benefits" is the heading in the source, but the content is a mix. To be safe, I might not create a separate "Skills" section unless I can extract real specific skills. The rule says prefer a few substantive sections over many thin ones. I'll probably combine skills into Benefits or use a `

  ` if needed, but not create a thin "Skills" section with filler. Let's see: The input says "Key Skills And Benefits" then lists things that are mostly benefits/perks. I'll treat them as Benefits. I won't create a "Skills" section unless there are specific skills listed beyond what's in responsibilities/qualifications. Actually, the responsibilities mention "Utilizing electronic documentation via tablets", "Collaborating with a multidisciplinary team", "Providing compassionate, patient-centered care" - those could be skills, but they're framed as responsibilities. I'll stick to the explicit sections. - "Pay" and "Schedule": The benefits section mentions "weekly/daily pay" and scheduling options. But there's no separate Pay section heading allowed unless the posting states pay specifics. It says "weekly/daily pay" as part of benefits. I could include pay info in a `

  ` or under Benefits, but not create a "Pay" section unless it's a dedicated salary figure. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "weekly/daily pay" and scheduling options, but I think those are better placed in Benefits or a short `

  `. I'll avoid a separate "Pay" section. For "Schedule", the posting says "Flexible scheduling options, including full-time, part-time, or PRN shifts, with day, night, and weekend availability." That's schedule content. I could create a "Schedule" section, but the rule says prefer few sections. I could fold it into Benefits or have a short Schedule section with actual content. Let's check: The allowed headings include "Schedule". The posting has real schedule content. I think I can include a "Schedule" section with the actual text, but I need to be careful not to thin out the structure. Actually, the benefits section already covers flexible scheduling. I might just include schedule info within Benefits or as a short `

  ` before Benefits. But the rule says "include a section ONLY when the posting has real, specific content for it". Schedule content is real and specific. I'll consider creating a "Schedule" section, but I need to see if it's better to have it separate or combined. To be safe, I'll probably combine schedule and pay into a brief `

  ` or integrate into Benefits, since the posting groups them under "Key Skills And Benefits". However, the rules explicitly list "Schedule" as a valid heading. I'll evaluate after drafting. - Let's list all substantive content from input: * Responsibilities: - Providing compassionate, patient-centered care to children and adults in home settings. - Ensuring outstanding clinical outcomes through skilled nursing services. - Utilizing electronic documentation via tablets in patient homes. - Collaborating with a multidisciplinary team to deliver quality care. - Participating in career development and skill advancement opportunities. * Qualifications: - Active, unencumbered LPN/LVN license in the practice state. - Current CPR certification with hands-on component. - TB skin test within the past 12 months. - At least 6 months of hands-on nursing experience; new graduates are not eligible. - Reliable transportation is required. * Key Skills And Benefits: - Flexible scheduling options, including full-time, part-time, or PRN shifts, with day, night, and weekend availability. - Local support and a supportive workplace culture that values diversity and work-life balance. - Competitive benefits such as health, dental, vision, paid time off, weekly/daily pay, and employee stock plans. - Opportunities for professional growth and skill development. - Now, map to headings: - "About the role": I can use the first paragraph of responsibilities/description, but the input starts with "Responsibilities Include...". Actually, the very first line: "Providing compassionate, patient-centered care to children and adults in home settings. Ensuring outstanding clinical outcomes through skilled nursing services. Utilizing electronic documentation via tablets in patient homes. Collaborating with a multidisciplinary team to deliver quality care. Participating in career development and skill advancement opportunities." This is essentially the role description/responsibilities intro. I could put this under "About the role" or merge into Responsibilities. The rules say use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The input has a section labeled "Responsibilities Include" followed by bullet points. I think I'll keep "Responsibilities" as a heading, and maybe the prose intro can be a

  before the list, or I can fold it into the Responsibilities section as a

  lead-in. But the rules say "Use

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

    for prose." So I can have a

    for the descriptive paragraph, then

    • for the bullet points. However, the bullet points are the responsibilities. I'll structure Responsibilities as a
      • list, and maybe the first paragraph is part of it or separate. Let's see: The input says "Responsibilities Include [list]". I'll make "Responsibilities" an

        , then a

        with the prose? Actually, the prose is the list items themselves. I'll just do

        Responsibilities

        • ...
        . But the rule says "Use

        for prose." There's some prose at the start: "Providing compassionate, patient-centered care to children and adults in home settings. Ensuring outstanding clinical outcomes through skilled nursing services." I could put that in a

        , then the bullet points. But it might be cleaner to have the

        Responsibilities

        followed by
        • items that include the text. I'll check the exact input: "Responsibilities Include Providing compassionate, patient-centered care to children and adults in home settings. Ensuring outstanding clinical outcomes through skilled nursing services. Utilizing electronic documentation via tablets in patient homes. Collaborating with a multidisciplinary team to deliver quality care. Participating in career development and skill advancement opportunities." It's all one sentence block with "Responsibilities Include" then the list. I think I'll do:

          Responsibilities

          • Providing compassionate, patient-centered care to children and adults in home settings.
          • Ensuring outstanding clinical outcomes through skilled nursing services.
          • Utilizing electronic documentation via tablets in patient homes.
          • Collaborating with a multidisciplinary team to deliver quality care.
          • Participating in career development and skill advancement opportunities.
          . That's clean. - "Qualifications": The input has a section "Qualifications" with bullet points. I'll use

          Qualifications

          • ...
          . The items: Active, unencumbered LPN/LVN license in the practice state. Current CPR certification with hands-on component. TB skin test within the past 12 months. At least 6 months of hands-on nursing experience; new graduates are not eligible. Reliable transportation is required. I