Private Duty Nurse LVN - Nights & Weekends
Affinity Home Health Care Inc · Georgetown, TX · 1 mo ago
On-siteHealthcareFull-time
Here's a thinking process:
1. **Analyze User Input:**
- Input is a job posting for an LPN/LVN role
- Contains sections: Role Overview, Key Responsibilities, Qualifications & Skills, Physical & Environmental Requirements
- User wants me to reformat 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 section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use `- ` for any list 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
2. **Identify Sections in Input:**
- Role Overview (prose description)
- Key Responsibilities (list of duties)
- Qualifications & Skills (mixed prose and list items, but I'll structure as list where appropriate)
- Physical & Environmental Requirements (list/prose mix)
Note: The input doesn't have "Benefits", "Pay", "Schedule" sections. Per rules, I should NOT create those sections unless the posting actually states them. So I'll only include sections that have real content.
Also note: The rules say use `
` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But I should only use headings that have content. I need to map the input sections to the allowed heading names, but only if there's real content.
Let's map:
- "Role Overview" -> could become "About the role" or keep as is? Rules say use `` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It lists examples. I think I can use "About the role" or keep the original meaningful heading. But the rule says "Do NOT repeat the job title as a heading (the page already shows it)". The job title is LPN/LVN. The section headings are different from job title. I'll use concise headings that match the spirit: "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", etc. But I need to be careful: the input has "Role Overview", "Key Responsibilities", "Qualifications & Skills", "Physical & Environmental Requirements".
Let's re-read: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This gives examples of valid heading texts. I can use these or similar, as long as they're meaningful. I'll map:
- "Role Overview" -> `About the role
` or `Role Overview
`. I'll use "About the role" as it's in the example, but the input says "Role Overview". To be safe and follow rules strictly, I'll use the exact example terms if the content matches, or use descriptive but concise ones. Actually, the rule says "e.g." so it's not exhaustive/exclusive. I'll use headings that match the content naturally. Let's see: "About the role" fits "Role Overview". "Responsibilities" fits "Key Responsibilities". "Requirements" could fit "Qualifications & Skills" and "Physical & Environmental Requirements". But there's also "Qualifications" and "Skills" as separate examples. I might split or combine. The rule also says "Prefer a few substantive sections over many thin ones." So I should combine related ones if needed.
Let's look at the input content:
- Role Overview: paragraph about LPN/LVN providing skilled nursing care in patients' homes under supervision, ensuring adherence to care plans, physician orders, and confidentiality standards.
- Key Responsibilities: bullet points (actually numbered/phrased as sentences, but I'll make them `
- `)
- Qualifications & Skills: includes graduation, license, CPR, TB test, preferred experience, skills (attention to detail, organization, communication, problem-solving)
- Physical & Environmental Requirements: ability to lift 50 pounds, reposition, travel, adapt to home settings, exposure to hazards
No Benefits, Pay, Schedule mentioned. So I won't create those sections.
Rule: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text... and never create Pay/Schedule/Benefits sections unless the posting actually states them."
So I'll only have sections for: About the role, Responsibilities, Requirements (or Qualifications/Skills), Physical requirements. But I need to map carefully.
Let's decide on headings that match the examples and the content:
- "About the role" (from Role Overview)
- "Responsibilities" (from Key Responsibilities)
- "Qualifications" (from Qualifications & Skills - but there's also "Skills" example. I could do "Qualifications & Skills" as one heading, or split. The example lists "Qualifications, Skills" as separate items. But the rule says "Prefer a few substantive sections over many thin ones." So I'll combine Qualifications and Skills into one section "Qualifications & Skills" or just "Qualifications". The input mixes them. I'll use "Qualifications & Skills" as a heading, it's in the example list as "Qualifications, Skills" but can be combined.)
- "Physical requirements" - but the example has "Schedule", "Pay", "Benefits". "Physical & Environmental Requirements" doesn't exactly match, but I can use "Requirements" or "Physical requirements". The example list includes "Requirements". I'll use "Requirements" maybe, but need to be careful not to create too many thin sections. Actually, the input has "Qualifications & Skills" and "Physical & Environmental Requirements" as distinct. I'll keep them separate if there's enough content, but the rule says prefer few substantive sections. Let's see: "Qualifications & Skills" has a lot of items. "Physical & Environmental Requirements" also has specific items. I'll keep both, but map headings appropriately.
Let's re-read the heading examples: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". So "Requirements", "Qualifications", "Skills" are separate examples. I could split into three sections, but that might be too many. The input's "Qualifications & Skills" section contains both qualifications (license, certifications) and skills (attention to detail, etc.). I'll likely combine into one "Qualifications & Skills" section, or do "Qualifications" and "Skills" as separate `
`s but that would require separating the content. To keep it few and substantive, I'll combine into "Qualifications & Skills". But the example lists them as separate items. I think it's safer to use "Qualifications" as the heading, and include both qual and skills within, or use "Qualifications & Skills" as a single heading. The rule says "e.g." so it's not strict. I'll use "Qualifications & Skills" as the heading text, as it matches the input's section name and is reasonable.
For "Physical & Environmental Requirements", I could use "Requirements" but that might conflict with "Qualifications Requirements". I'll use "Physical requirements" or keep "Physical & Environmental Requirements" but wrapped in ``. The example has "Requirements" as a heading, so maybe I'll just use "Requirements" and put the physical content under it, but then it overlaps with qualifications. Better to use "Physical requirements" or "Environmental requirements". I think I'll use "Physical requirements" as the heading, since the content is about physical demands.
Let's plan the structure:
About the role
...prose from Role Overview...
Responsibilities
- ...
Qualifications & Skills
- ...qualifications...
- ...skills...
Physical requirements
- ...physical requirements...
But I need to check the exact content and map properly without inventing or summarizing away detail.
Let's extract exact text:
"Role Overview: The Licensed Practical/Vocational Nurse (LPN/LVN) provides skilled nursing care in patients' homes under supervision, ensuring adherence to care plans, physician orders, and confidentiality standards."
Wait, the input starts with "Role Overview:" then text. But the rule says "Do NOT repeat the job title as a heading (the page already shows it)". The job title is LPN/LVN. The "Role Overview" is a section heading. I should not create a heading for the job title itself, but "Role Overview" is a section description. I'll use `About the role
` and put the prose inside. Or I could use `Role Overview
` but the example suggests "About the role". I'll use "About the role" as it's cleaner and matches the example. The prose will include the description.
"Key Responsibilities" section has 8 bullet points (sentences). I'll put them as ` - ` items.
"Qualifications & Skills" section has:
- Graduate of an accredited nursing program.
- Current, unrestricted state license (LPN/LVN).
- CPR certification with hands-on component.
- TB test within last 12 months.
- Preferred: Six months of clinical experience or home health background.
- Strong attention to detail, organization, communication, and problem-solving abilities.
"Physical & Environmental Requirements" section has:
- Ability to lift 50 pounds, perform patient repositioning, travel, and adapt to various home settings with exposure to potential hazards.
Now, rules: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Not present in input, good.
"Preserve ALL substantive information; do NOT invent or summarize away detail." So I must include all the bullet points exactly, or as close as possible.
"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 won't create those.
"Prefer a few substantive sections over many thin ones." I'll have 4 sections: About the role, Responsibilities, Qualifications & Skills, Physical requirements. That seems reasonable.
Now, mapping headings to the exact example terms: The examples given are "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I'll use:
- "About the role" (matches
` 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 2. **Identify Sections in Input:** - Role Overview (prose description) - Key Responsibilities (list of duties) - Qualifications & Skills (mixed prose and list items, but I'll structure as list where appropriate) - Physical & Environmental Requirements (list/prose mix) Note: The input doesn't have "Benefits", "Pay", "Schedule" sections. Per rules, I should NOT create those sections unless the posting actually states them. So I'll only include sections that have real content. Also note: The rules say use `
` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But I should only use headings that have content. I need to map the input sections to the allowed heading names, but only if there's real content.
Let's map:
- "Role Overview" -> could become "About the role" or keep as is? Rules say use `` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It lists examples. I think I can use "About the role" or keep the original meaningful heading. But the rule says "Do NOT repeat the job title as a heading (the page already shows it)". The job title is LPN/LVN. The section headings are different from job title. I'll use concise headings that match the spirit: "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", etc. But I need to be careful: the input has "Role Overview", "Key Responsibilities", "Qualifications & Skills", "Physical & Environmental Requirements".
Let's re-read: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This gives examples of valid heading texts. I can use these or similar, as long as they're meaningful. I'll map:
- "Role Overview" -> `About the role
` or `Role Overview
`. I'll use "About the role" as it's in the example, but the input says "Role Overview". To be safe and follow rules strictly, I'll use the exact example terms if the content matches, or use descriptive but concise ones. Actually, the rule says "e.g." so it's not exhaustive/exclusive. I'll use headings that match the content naturally. Let's see: "About the role" fits "Role Overview". "Responsibilities" fits "Key Responsibilities". "Requirements" could fit "Qualifications & Skills" and "Physical & Environmental Requirements". But there's also "Qualifications" and "Skills" as separate examples. I might split or combine. The rule also says "Prefer a few substantive sections over many thin ones." So I should combine related ones if needed.
Let's look at the input content:
- Role Overview: paragraph about LPN/LVN providing skilled nursing care in patients' homes under supervision, ensuring adherence to care plans, physician orders, and confidentiality standards.
- Key Responsibilities: bullet points (actually numbered/phrased as sentences, but I'll make them `
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This gives examples of valid heading texts. I can use these or similar, as long as they're meaningful. I'll map:
- "Role Overview" -> `About the role
` or `Role Overview
`. I'll use "About the role" as it's in the example, but the input says "Role Overview". To be safe and follow rules strictly, I'll use the exact example terms if the content matches, or use descriptive but concise ones. Actually, the rule says "e.g." so it's not exhaustive/exclusive. I'll use headings that match the content naturally. Let's see: "About the role" fits "Role Overview". "Responsibilities" fits "Key Responsibilities". "Requirements" could fit "Qualifications & Skills" and "Physical & Environmental Requirements". But there's also "Qualifications" and "Skills" as separate examples. I might split or combine. The rule also says "Prefer a few substantive sections over many thin ones." So I should combine related ones if needed.
Let's look at the input content:
- Role Overview: paragraph about LPN/LVN providing skilled nursing care in patients' homes under supervision, ensuring adherence to care plans, physician orders, and confidentiality standards.
- Key Responsibilities: bullet points (actually numbered/phrased as sentences, but I'll make them `
`s but that would require separating the content. To keep it few and substantive, I'll combine into "Qualifications & Skills". But the example lists them as separate items. I think it's safer to use "Qualifications" as the heading, and include both qual and skills within, or use "Qualifications & Skills" as a single heading. The rule says "e.g." so it's not strict. I'll use "Qualifications & Skills" as the heading text, as it matches the input's section name and is reasonable.
For "Physical & Environmental Requirements", I could use "Requirements" but that might conflict with "Qualifications Requirements". I'll use "Physical requirements" or keep "Physical & Environmental Requirements" but wrapped in ``. The example has "Requirements" as a heading, so maybe I'll just use "Requirements" and put the physical content under it, but then it overlaps with qualifications. Better to use "Physical requirements" or "Environmental requirements". I think I'll use "Physical requirements" as the heading, since the content is about physical demands.
Let's plan the structure:
About the role
About the role
...prose from Role Overview...
Responsibilities
- ...
Qualifications & Skills
- ...qualifications...
- ...skills...
Physical requirements
- ...physical requirements...