Private Duty Nurse LVN - Nights & Weekends
` 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") 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. **Analyze the Provided Job Posting Text:**
Let me copy and parse the input:
"Role Overview The Licensed Practical / Vocational Nurse (LPN/LVN) provides skilled nursing care under the supervision of a Registered Nurse, following care plans and physician orders. Responsibilities include assessing patient conditions, documenting activities, updating care plans, and implementing interventions to achieve positive outcomes. The role emphasizes patient education, infection control, and maintaining professional standards in compliance with regulations and policies. Key Duties Deliver high-quality, coordinated patient care based on physician directives.Monitor and report changes in patient status promptly.Document assessments, nursing actions, and responses accurately and timely.Participate in care plan updates and implement appropriate nursing interventions.Educate patients and families on disease management, self-care, and prevention.Ensure infection control measures and maintain confidentiality. Qualifications & Skills Active, unrestricted LPN/LVN license in the practicing state.Current CPR certification and TB test within the last 12 months.Preferred: Six months of clinical experience or home health background.Strong attention to detail, organization, communication, and problem-solving skills.Ability to lift 50 pounds, reposition patients, and respond to emergencies.Reliable transportation and ability to travel. Work Environment & Requirements Ability to function in diverse environments with exposure to blood, bodily fluids, and infectious diseases.Proficiency in English (reading, writing, speaking).Physical endurance for prolonged walking, standing, and other movements."
Let me break it down by semantic sections:
- **Role Overview / About the role**: The first paragraph seems to be an overview: "Role Overview The Licensed Practical / Vocational Nurse (LPN/LVN) provides skilled nursing care under the supervision of a Registered Nurse, following care plans and physician orders. Responsibilities include assessing patient conditions, documenting activities, updating care plans, and implementing interventions to achieve positive outcomes. The role emphasizes patient education, infection control, and maintaining professional standards in compliance with regulations and policies."
Wait, the user said: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." and "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "Licensed Practical / Vocational Nurse (LPN/LVN)". I should not output a heading for the job title. But the text starts with "Role Overview...". I need to decide how to structure this.
Let me re-read the input carefully. It seems like the posting text is a continuous block, but has internal structure:
- "Role Overview [paragraph]"
- "Key Duties [list of duties]"
- "Qualifications & Skills [list of qualifications/skills]"
- "Work Environment & Requirements [paragraph/list]"
The user wants me to use specific heading names: "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But they also say: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So I should only create sections that have actual content from the posting.
Let me map the content to the requested heading style, but only where there's real content.
The posting has:
- A role overview paragraph
- Key Duties (list of 5 items)
- Qualifications & Skills (various requirements)
- Work Environment & Requirements (paragraph with 3 points)
The user said to use `` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But I shouldn't invent sections. I should use headings that match the content, but only if there's substance.
Let me parse each part:
"Role Overview The Licensed Practical / Vocational Nurse (LPN/LVN) provides skilled nursing care under the supervision of a Registered Nurse, following care plans and physician orders. Responsibilities include assessing patient conditions, documenting activities, updating care plans, and implementing interventions to achieve positive outcomes. The role emphasizes patient education, infection control, and maintaining professional standards in compliance with regulations and policies."
This seems like the "About the role" or "Role Overview" section. I'll use `About the role
` or maybe just keep it as prose under a heading. But I need to check if the posting actually has a section called "About the role". It starts with "Role Overview", so I can map that to "About the role".
"Key Duties Deliver high-quality, coordinated patient care based on physician directives.Monitor and report changes in patient status promptly.Document assessments, nursing actions, and responses accurately and timely.Participate in care plan updates and implement appropriate nursing interventions.Educate patients and families on disease management, self-care, and prevention.Ensure infection control measures and maintain confidentiality."
This is clearly a list of duties. I'll use `Responsibilities
` or `Key Duties
`. The user listed examples: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I think "Responsibilities" fits "Key Duties".
"Qualifications & Skills Active, unrestricted LPN/LVN license in the practicing state.Current CPR certification and TB test within the last 12 months.Preferred: Six months of clinical experience or home health background.Strong attention to detail, organization, communication, and problem-solving skills.Ability to lift 50 pounds, reposition patients, and respond to emergencies.Reliable transportation and ability to travel."
This mixes qualifications and skills. The user wants separate headings for "Qualifications" and "Skills" maybe, but I need to only create sections with real content. I could split this into two sections if there's distinct content, or combine them. Let me see: "Qualifications & Skills" is one block in the posting. I could make two headings: "Qualifications" and "Skills", but I need to ensure I'm not creating thin sections. The user says "Prefer a few substantive sections over many thin ones." So maybe I'll keep it as one section or split if natural. Let me look at the content: licenses/certifications are qualifications; skills like attention to detail, communication, problem-solving, ability to lift, transportation are skills/requirements. I could do `Qualifications
` and `Skills
`, but I need to check if the posting actually separates them. It says "Qualifications & Skills" as a heading in the original, but I'm reformatting. I think I'll split into two, as the user listed both "Qualifications" and "Skills" as examples of headings, and both have content.
"Work Environment & Requirements Ability to function in diverse environments with exposure to blood, bodily fluids, and infectious diseases.Proficiency in English (reading, writing, speaking).Physical endurance for prolonged walking, standing, and other movements."
This is work environment/requirements. The user listed "Requirements" as a heading example. This could map to "Requirements" or "Work Environment". I'll see. The content is about work environment and requirements. I could use `Requirements
` or `Work Environment & Requirements
`. Since the user said "Do NOT repeat the job title as a heading", and "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)", I should use the exact example names or similar. I'll map appropriately.
Now, crucial constraints:
- Do NOT create Pay/Schedule/Benefits sections unless the posting actually states them. The posting has no Pay, Schedule, or Benefits content. So I must omit those entirely.
- Remove boilerplate, duplicated lines, application instructions, etc. The input doesn't seem to have those, just the core posting text.
- Preserve ALL substantive information; do NOT invent or summarize away detail.
- Output ONLY the HTML fragment — no `/`, no markdown code fences.
Let me structure the HTML fragment.
I need to decide on headings. The user gave examples: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I should use these, but only where content exists.
Let me map:
- "About the role" → The first paragraph starting with "Role Overview...". I'll use `About the role
` and then `
` with the text. But wait, the first paragraph also includes "Responsibilities include...". I need to be careful not to duplicate. Actually, the text says: "Role Overview The Licensed Practical / Vocational Nurse (LPN/LVN) provides skilled nursing care... Responsibilities include assessing patient conditions... The role emphasizes patient education, infection control, and maintaining professional standards in compliance with regulations and policies." So it's a mix of overview and responsibilities. I might want to separate the "Role Overview" part from the "Key Duties" list. But the Key Duties list is explicitly labeled "Key Duties" later. So perhaps the first paragraph is the "About the role" prose, and "Key Duties" is the responsibilities list.
Let me re-read the input as if it's structured:
- "Role Overview [paragraph about LPN/LVN role, responsibilities summary]"
- "Key Duties [5 bullet points in prose]"
- "Qualifications & Skills [list]"
- "Work Environment & Requirements [paragraph]"
I think the cleanest approach:
- `
About the role
...` with the first paragraph's substantive content, but excluding the "Responsibilities include..." part since that's covered in Key Duties. Actually, the user said "Preserve ALL substantive information; do NOT invent or summarize away detail." So I shouldn't drop anything. Maybe I should include the overview text as-is, and then have the Key Duties list separately. The overview text includes "Responsibilities include assessing patient conditions..." which is also in Key Duties. To avoid duplication, I could either: a) keep the overview without that sentence, b) keep it and have it repeat in Key Duties, or c) integrate. The user said "do NOT invent or summarize away detail." It doesn't strictly forbid duplication if the source has it, but typically in reformatting, we avoid exact duplication. However, the instruction says "Preserve ALL substantive information". I'll keep all text, but structure it so each
` 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") 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. **Analyze the Provided Job Posting Text:** Let me copy and parse the input: "Role Overview The Licensed Practical / Vocational Nurse (LPN/LVN) provides skilled nursing care under the supervision of a Registered Nurse, following care plans and physician orders. Responsibilities include assessing patient conditions, documenting activities, updating care plans, and implementing interventions to achieve positive outcomes. The role emphasizes patient education, infection control, and maintaining professional standards in compliance with regulations and policies. Key Duties Deliver high-quality, coordinated patient care based on physician directives.Monitor and report changes in patient status promptly.Document assessments, nursing actions, and responses accurately and timely.Participate in care plan updates and implement appropriate nursing interventions.Educate patients and families on disease management, self-care, and prevention.Ensure infection control measures and maintain confidentiality. Qualifications & Skills Active, unrestricted LPN/LVN license in the practicing state.Current CPR certification and TB test within the last 12 months.Preferred: Six months of clinical experience or home health background.Strong attention to detail, organization, communication, and problem-solving skills.Ability to lift 50 pounds, reposition patients, and respond to emergencies.Reliable transportation and ability to travel. Work Environment & Requirements Ability to function in diverse environments with exposure to blood, bodily fluids, and infectious diseases.Proficiency in English (reading, writing, speaking).Physical endurance for prolonged walking, standing, and other movements." Let me break it down by semantic sections: - **Role Overview / About the role**: The first paragraph seems to be an overview: "Role Overview The Licensed Practical / Vocational Nurse (LPN/LVN) provides skilled nursing care under the supervision of a Registered Nurse, following care plans and physician orders. Responsibilities include assessing patient conditions, documenting activities, updating care plans, and implementing interventions to achieve positive outcomes. The role emphasizes patient education, infection control, and maintaining professional standards in compliance with regulations and policies." Wait, the user said: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." and "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "Licensed Practical / Vocational Nurse (LPN/LVN)". I should not output a heading for the job title. But the text starts with "Role Overview...". I need to decide how to structure this.
Let me re-read the input carefully. It seems like the posting text is a continuous block, but has internal structure:
- "Role Overview [paragraph]"
- "Key Duties [list of duties]"
- "Qualifications & Skills [list of qualifications/skills]"
- "Work Environment & Requirements [paragraph/list]"
The user wants me to use specific heading names: "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But they also say: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So I should only create sections that have actual content from the posting.
Let me map the content to the requested heading style, but only where there's real content.
The posting has:
- A role overview paragraph
- Key Duties (list of 5 items)
- Qualifications & Skills (various requirements)
- Work Environment & Requirements (paragraph with 3 points)
The user said to use `` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But I shouldn't invent sections. I should use headings that match the content, but only if there's substance.
Let me parse each part:
"Role Overview The Licensed Practical / Vocational Nurse (LPN/LVN) provides skilled nursing care under the supervision of a Registered Nurse, following care plans and physician orders. Responsibilities include assessing patient conditions, documenting activities, updating care plans, and implementing interventions to achieve positive outcomes. The role emphasizes patient education, infection control, and maintaining professional standards in compliance with regulations and policies."
This seems like the "About the role" or "Role Overview" section. I'll use `About the role
` or maybe just keep it as prose under a heading. But I need to check if the posting actually has a section called "About the role". It starts with "Role Overview", so I can map that to "About the role".
"Key Duties Deliver high-quality, coordinated patient care based on physician directives.Monitor and report changes in patient status promptly.Document assessments, nursing actions, and responses accurately and timely.Participate in care plan updates and implement appropriate nursing interventions.Educate patients and families on disease management, self-care, and prevention.Ensure infection control measures and maintain confidentiality."
This is clearly a list of duties. I'll use `Responsibilities
` or `Key Duties
`. The user listed examples: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I think "Responsibilities" fits "Key Duties".
"Qualifications & Skills Active, unrestricted LPN/LVN license in the practicing state.Current CPR certification and TB test within the last 12 months.Preferred: Six months of clinical experience or home health background.Strong attention to detail, organization, communication, and problem-solving skills.Ability to lift 50 pounds, reposition patients, and respond to emergencies.Reliable transportation and ability to travel."
This mixes qualifications and skills. The user wants separate headings for "Qualifications" and "Skills" maybe, but I need to only create sections with real content. I could split this into two sections if there's distinct content, or combine them. Let me see: "Qualifications & Skills" is one block in the posting. I could make two headings: "Qualifications" and "Skills", but I need to ensure I'm not creating thin sections. The user says "Prefer a few substantive sections over many thin ones." So maybe I'll keep it as one section or split if natural. Let me look at the content: licenses/certifications are qualifications; skills like attention to detail, communication, problem-solving, ability to lift, transportation are skills/requirements. I could do `Qualifications
` and `Skills
`, but I need to check if the posting actually separates them. It says "Qualifications & Skills" as a heading in the original, but I'm reformatting. I think I'll split into two, as the user listed both "Qualifications" and "Skills" as examples of headings, and both have content.
"Work Environment & Requirements Ability to function in diverse environments with exposure to blood, bodily fluids, and infectious diseases.Proficiency in English (reading, writing, speaking).Physical endurance for prolonged walking, standing, and other movements."
This is work environment/requirements. The user listed "Requirements" as a heading example. This could map to "Requirements" or "Work Environment". I'll see. The content is about work environment and requirements. I could use `Requirements
` or `Work Environment & Requirements
`. Since the user said "Do NOT repeat the job title as a heading", and "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)", I should use the exact example names or similar. I'll map appropriately.
Now, crucial constraints:
- Do NOT create Pay/Schedule/Benefits sections unless the posting actually states them. The posting has no Pay, Schedule, or Benefits content. So I must omit those entirely.
- Remove boilerplate, duplicated lines, application instructions, etc. The input doesn't seem to have those, just the core posting text.
- Preserve ALL substantive information; do NOT invent or summarize away detail.
- Output ONLY the HTML fragment — no `/`, no markdown code fences.
Let me structure the HTML fragment.
I need to decide on headings. The user gave examples: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I should use these, but only where content exists.
Let me map:
- "About the role" → The first paragraph starting with "Role Overview...". I'll use `About the role
` and then `
About the role
` or maybe just keep it as prose under a heading. But I need to check if the posting actually has a section called "About the role". It starts with "Role Overview", so I can map that to "About the role". "Key Duties Deliver high-quality, coordinated patient care based on physician directives.Monitor and report changes in patient status promptly.Document assessments, nursing actions, and responses accurately and timely.Participate in care plan updates and implement appropriate nursing interventions.Educate patients and families on disease management, self-care, and prevention.Ensure infection control measures and maintain confidentiality." This is clearly a list of duties. I'll use `Responsibilities
` or `Key Duties
`. The user listed examples: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I think "Responsibilities" fits "Key Duties". "Qualifications & Skills Active, unrestricted LPN/LVN license in the practicing state.Current CPR certification and TB test within the last 12 months.Preferred: Six months of clinical experience or home health background.Strong attention to detail, organization, communication, and problem-solving skills.Ability to lift 50 pounds, reposition patients, and respond to emergencies.Reliable transportation and ability to travel." This mixes qualifications and skills. The user wants separate headings for "Qualifications" and "Skills" maybe, but I need to only create sections with real content. I could split this into two sections if there's distinct content, or combine them. Let me see: "Qualifications & Skills" is one block in the posting. I could make two headings: "Qualifications" and "Skills", but I need to ensure I'm not creating thin sections. The user says "Prefer a few substantive sections over many thin ones." So maybe I'll keep it as one section or split if natural. Let me look at the content: licenses/certifications are qualifications; skills like attention to detail, communication, problem-solving, ability to lift, transportation are skills/requirements. I could do `Qualifications
` and `Skills
`, but I need to check if the posting actually separates them. It says "Qualifications & Skills" as a heading in the original, but I'm reformatting. I think I'll split into two, as the user listed both "Qualifications" and "Skills" as examples of headings, and both have content. "Work Environment & Requirements Ability to function in diverse environments with exposure to blood, bodily fluids, and infectious diseases.Proficiency in English (reading, writing, speaking).Physical endurance for prolonged walking, standing, and other movements." This is work environment/requirements. The user listed "Requirements" as a heading example. This could map to "Requirements" or "Work Environment". I'll see. The content is about work environment and requirements. I could use `Requirements
` or `Work Environment & Requirements
`. Since the user said "Do NOT repeat the job title as a heading", and "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)", I should use the exact example names or similar. I'll map appropriately.
Now, crucial constraints:
- Do NOT create Pay/Schedule/Benefits sections unless the posting actually states them. The posting has no Pay, Schedule, or Benefits content. So I must omit those entirely.
- Remove boilerplate, duplicated lines, application instructions, etc. The input doesn't seem to have those, just the core posting text.
- Preserve ALL substantive information; do NOT invent or summarize away detail.
- Output ONLY the HTML fragment — no `/`, no markdown code fences.
Let me structure the HTML fragment.
I need to decide on headings. The user gave examples: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I should use these, but only where content exists.
Let me map:
- "About the role" → The first paragraph starting with "Role Overview...". I'll use `About the role
` and then `
` with the text. But wait, the first paragraph also includes "Responsibilities include...". I need to be careful not to duplicate. Actually, the text says: "Role Overview The Licensed Practical / Vocational Nurse (LPN/LVN) provides skilled nursing care... Responsibilities include assessing patient conditions... The role emphasizes patient education, infection control, and maintaining professional standards in compliance with regulations and policies." So it's a mix of overview and responsibilities. I might want to separate the "Role Overview" part from the "Key Duties" list. But the Key Duties list is explicitly labeled "Key Duties" later. So perhaps the first paragraph is the "About the role" prose, and "Key Duties" is the responsibilities list. Let me re-read the input as if it's structured: - "Role Overview [paragraph about LPN/LVN role, responsibilities summary]" - "Key Duties [5 bullet points in prose]" - "Qualifications & Skills [list]" - "Work Environment & Requirements [paragraph]" I think the cleanest approach: - `
About the role
...` with the first paragraph's substantive content, but excluding the "Responsibilities include..." part since that's covered in Key Duties. Actually, the user said "Preserve ALL substantive information; do NOT invent or summarize away detail." So I shouldn't drop anything. Maybe I should include the overview text as-is, and then have the Key Duties list separately. The overview text includes "Responsibilities include assessing patient conditions..." which is also in Key Duties. To avoid duplication, I could either: a) keep the overview without that sentence, b) keep it and have it repeat in Key Duties, or c) integrate. The user said "do NOT invent or summarize away detail." It doesn't strictly forbid duplication if the source has it, but typically in reformatting, we avoid exact duplication. However, the instruction says "Preserve ALL substantive information". I'll keep all text, but structure it so each