CLINICAL NURSE IV LEADER - PCICU

The user wants me to reformat a job posting into clean, well-structured semantic HTML. I need to follow the rules carefully: 1. Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) 2. Use

• for lists of duties/requirements/benefits, and

  for prose 3. Do NOT repeat the job title as a heading 4. Do NOT put Job ID / requisition numbers as headings 5. Preserve ALL substantive information 6. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) 7. Include a section ONLY when the posting has real, specific content for it 8. Never emit a heading followed by filler/placeholder text 9. Never create Pay/Schedule/Benefits sections unless the posting actually states them 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: The posting starts with Duke Health mission statement and info about Duke University Hospital - this is "About the role" or "About the organization" content. Then "Occ Summary" - this is a summary of the role. "Work Performed" - this is responsibilities/duties. Then "CNIV Pathways" with subsections: Leadership/Regulatory, Education, Informatics, Quality/Research/Innovation - these are more detailed responsibilities. "Knowledge, Skills And Abilities" - this is skills/requirements. "Required Level Characteristics" - more requirements. "Minimum Qualifications" with Education, Experience, Degrees/Licensures/Certifications - this is qualifications. Then there's EEO statement, physical job functions note - these are boilerplate to remove. I need to structure this into appropriate sections. Let me think about the sections: 1. About the role / About the organization (the intro paragraphs) 2. Responsibilities (Work Performed + CNIV Pathways) 3. Requirements / Qualifications (Knowledge, Skills And Abilities + Required Level Characteristics + Minimum Qualifications) The posting doesn't have explicit Benefits, Pay, Schedule sections with real content, so I won't create those. I'll use

  for each section heading. For lists, use

  • . For prose, use

    . Let me organize: Section 1: About the role (or About the organization) - includes the Duke Health mission and Duke University Hospital description. Section 2: Responsibilities - includes Occ Summary, Work Performed, and CNIV Pathways subsections. Section 3: Qualifications - includes Knowledge, Skills And Abilities, Required Level Characteristics, Minimum Qualifications (Education, Experience, Degrees/Licensures/Certifications). I need to preserve all substantive information. The CNIV Pathways have specific bullet points - I should include those as nested lists or separate lists. I'll structure Responsibilities with subsections using

    ? But the rules say use

    for section headings. It doesn't mention

    . But I can use

    for main sections and maybe

    for subsections? The rules only specify

    for section headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". It doesn't forbid other heading levels, but to be safe, I'll keep it flat with

    for main sections and use

    • for sub-items. Actually, the CNIV Pathways are part of responsibilities, so I can include them as sub-lists under Responsibilities. Similarly, Qualifications can have sub-lists. Let me draft the HTML. First, the About section:

      About the role

      At Duke Health, we're driven by a commitment to compassionate care that changes the lives of patients, their loved ones, and the greater community. No matter where your talents lie, join us and discover how we can advance health together.

      Duke University Hospital in Durham, North Carolina, is consistently ranked among the best in the United States. The largest of the four Duke Health hospitals with 1,062 patient beds, it features comprehensive diagnostic and therapeutic facilities, including a regional emergency/trauma center, an endo-surgery center, and more.

      Plan and provide advanced and/or specialized nursing care for patients in accordance with guidelines established within the Discipline of Nursing Clinical Ladder Program and the North Carolina Board of Nursing. The position will provide local level leadership in the areas of administration, education, informatics and quality.

      Wait, the "Occ Summary" is part of the role summary. I'll include it in About the role. Now Responsibilities:

      Responsibilities

      • Identify care needs for patient populations across the continuum of care.
      • Collaborate and provide leadership in the development of standards of care, patient/family education and staff education to address the needs of specific populations.
      • Collaborate with multidisciplinary team and provide leadership within the delivery of patient care.
      • Provide leadership in educational activities, departmental committees, research projects and other health-related projects.
      • Provide evaluation, direction and guidance in the proper selection, use, care and control of material resources.
      • Appraise quality and effectiveness of material and equipment and collaborate with appropriate departments to assist with vendor selection and feedback on performance.
      • Guide the professional growth of others across the continuum of care through role modeling, coaching and/or mentoring. This may include designing orientation modules, primary precepting of senior nursing students.
      • Provide leadership at a departmental, entity, community or regional/national level for initiatives focused on improving the quality of care for populations of patients and growth of others.
      • Conduct performance reviews.
      • Effectively recommend personnel actions including, but not limited to, hiring, performance appraisals, disciplinary actions, terminations and other related activities.
      • Perform other related duties incidental to the work described herein.
      Then CNIV Pathways - these are additional responsibilities. I'll add them as another list or sub-list. Since they are categorized, I could do:

      Responsibilities

      • ... (the Work Performed items)

      CNIV Pathways: Leadership/Regulatory

      ...
      But the rules say use

      for section headings. It doesn't say I can't use

      . But to be safe, I'll incorporate them into the Responsibilities section with subheadings using

      or just include as nested lists. However, the instruction: "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other headings, but I think it's okay to use

      for subsections. But the output should be a fragment, and using

      is fine. However, the user might expect only

      for the main sections. I'll keep it simple: include CNIV Pathways as part of Responsibilities with sub-lists labeled in

      or separate

      with a heading. I'll use

      for the pathway categories. But the rule: "use

      for section headings" - it doesn't say "only use

      ", but it's implied that those are the section headings. I'll use

      for the main sections and

      for subsections within Responsibilities and Qualifications. Alternatively, I can make each CNIV Pathway a separate

      ? That would be too many sections. Better to keep as subsections. I'll do:

      Responsibilities

      Core duties:

      ... Work Performed list ...

      CNIV Pathways

      Leadership/Regulatory
      ...
      Education
      ...
      etc. But the rule says "use

      for section headings". It doesn't mention

      or . To be safe, I'll avoid

      and and instead use or just include as list items with bold labels. But that might not be semantic. The instruction says "clean, well-structured semantic HTML". Using heading levels is semantic. I think using

      is acceptable. However, the user might have a parser that expects only

      for sections. The examples given are "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". So those are the top-level sections. Subsections are not mentioned. I'll keep only

      for those top-level sections, and for subsections, I'll use

      with a leading
      • that is a heading-like item, or use

        ...

        before a list. I'll do:

        Responsibilities

        • Identify care needs for patient populations across the continuum of care.
        ... all Work Performed items ...

        CNIV Pathways — Leadership/Regulatory

        • Monitor clinical practice and ensure compliance to practice standards and regulatory standards.
        • Collaborate with unit/clinic leadership to coach and mentor nursing colleagues.
        • Influence recruitment and development of staff.

        CNIV Pathways — Education

        • Plan and deliver in house education sessions or collaborate with subject matter experts.
        • Keep up to date with evidence-based nursing practices and adult education.
        • Assess educational needs of staff.
        • Partners with clinical nurse educator and clinical nurse specialist to address unit educational needs.
        ... etc. That seems clean. Now Qualifications section:

        Qualifications

        Knowledge, Skills, and Abilities

        • Knowledge of scope of the registered nurse, licensed practical nurse and Unlicensed staff.
        • Knowledge of and appropriate application of the nursing process.
        • Knowledge of professional theory, practice and procedure.
        • Ability to assess nursing needs of acute and chronically ill patients and their families.
        • Ability to independently seek out resources and work collaboratively.
        • Ability to establish and maintain effective working relationships.
        • Ability to communicate clearly with patients, families, visitors, healthcare team, physicians, administrators, leadership and others.
        • Ability to teach patients and families in accordance with the nursing plan of care.
        • Ability to use sensory and cognitive functions to process and prioritize information, treatment, and follow-up.
        • Ability to use fine motor skills.
        • Competent in BLS and/or other specialized life support requirements designated by work area.
        • Ability to record activities, document assessments, plan of care, interventions, evaluation and re-evaluation of patient status.
        • Ability to use computer and learn new software programs.
        • Ability to document and communicate pertinent information using computer and/or paper documentation tools.
        • Ability to navigate the entity to provide clinical care for patients.
        • Ability to withstand prolonged standing and walking.
        • Ability to remain focused and organized.
        • Working knowledge of procedures and techniques involved in administering routine and special treatments to patients.
        • Working knowledge of infection control procedures and safety precautions.
        • Working knowledge and completion of appropriate The Joint Commission (TJC) and other regulatory requirements.
        • Pre-employment Physical Capacity Testing Required.

        Required Level Characteristics

        • Provide