Float Pool RN PRN

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. First, I need to identify the sections. The posting has: - A description of the role (professional registered nurse) - Minimum Qualifications (Education, Certification, Licensure, Experience) - Core Duties and Responsibilities - For Facilities With Specialty Accreditation Requirements - Physical Requirements - Working Environment - Skills And Abilities - Additional Job Description (Scheduled Weekly Hours, Shift, Exempt/Non-Exempt, Company, Cost Center, Address) - Equal Opportunity Employer statement (boilerplate, should be removed) Rules: - Use

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

• for lists,

  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 - Preserve ALL substantive information; do NOT invent or summarize - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions - Include section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment — no /, no markdown code fences Now, let's map content to sections. The role description: "The professional registered nurse has the authority..." This is about the role. Could be "About the role" or "Description". Use

  About the role

  with

  for prose. Minimum Qualifications: Education, Certification, Licensure, Experience. This is "Requirements" or "Qualifications". Use

  Requirements

  with
  • for each item. Core Duties and Responsibilities: list of duties. Use

    Responsibilities

    with
    • . For Facilities With Specialty Accreditation Requirements: specific requirement. Could be part of Requirements or separate. Since it's a specific requirement, maybe include under Requirements or as separate section. The rule says prefer few substantive sections. Could add as a subsection under Requirements or separate. I'll include as a separate section "Specialty Accreditation Requirements" with
      • . Physical Requirements: list of physical demands. Use

        Physical Requirements

        with
        • . Working Environment: list of environment characteristics. Use

          Working Environment

          with
          • . Skills And Abilities: list of skills. Use

            Skills

            with
            • . Additional Job Description: Scheduled Weekly Hours: 0 Shift Day (United States of America) Exempt/Non-Exempt United States of America (Non-Exempt) Company CCMC Camden Clark Medical Center Cost Center 93 CCMC Nursing Nurse Resource and Float Pool Address 800 Garfield Ave Parkersburg West Virginia. This is metadata. The rule says fold minor metadata into a short

              or drop it. But some of this might be relevant: Scheduled Weekly Hours, Shift, Exempt/Non-Exempt, Company, Address. However, the rule says do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

              or drop it. This includes company, cost center, address. But schedule info (hours, shift, exempt) might be considered schedule. The posting says "Scheduled Weekly Hours: 0 Shift Day (United States of America) Exempt/Non-Exempt United States of America (Non-Exempt)". That's schedule info. Could create a "Schedule" section if substantive. But "0" hours? Might be a placeholder. The rule says never create Schedule section unless posting actually states them. It does state them, but "0" might be placeholder. However, it's explicit. I'll include a short

              with schedule details, maybe under a "Schedule" heading? But the rule says prefer few substantive sections. Could fold into a

              at the end. But the rule says include section ONLY when posting has real, specific content for it. The schedule info is specific: Scheduled Weekly Hours: 0, Shift Day, Exempt/Non-Exempt. That's specific. However, "0" hours might be an error. But we must preserve substantive information. I'll create a "Schedule" section with

              containing that info. Also company and address could be "Location" or "Company". But the rule says fold minor metadata into short

              or drop. I'll include a "Details" section with a

              for company, cost center, address, and schedule. But the rule says do NOT put Job ID/requisition numbers as headings. Cost center is like a requisition number. So drop cost center. Company and address are location info. Could be "Location". But the rule says never create Benefits/Pay/Schedule unless posting actually states them. It states schedule. So I'll create a "Schedule" section with the schedule info. For company and address, maybe a "Location" section? But not a standard heading. The allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Location" not listed. So maybe fold into a

              at the end without heading. But the rule says output only sections with headings. Could add a "Details" heading? Not in list. The list is examples: "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". It says "e.g." so we can use other relevant headings? 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 suggests those. I'll stick to those. For metadata, I'll include a short

              at the end of the fragment, maybe after Skills, without a heading? But the rule says output ONLY the HTML fragment, and we should structure with headings. Could add a "Schedule" heading for schedule info, and a "Location" heading? Not in list. Better to fold company and address into a

              under "Schedule" or separate. I'll create a "Schedule" section with schedule info, and a "Location" section? But not in list. The rule says "use

              for section headings (e.g. ...)". It doesn't say we cannot use others. But to be safe, I'll use "Schedule" for schedule, and for company/address, maybe include in a "Details" paragraph after all sections? But the fragment should be structured. I think it's okay to have a "Location" heading. However, the user might expect only those headings. Let's see the example: they gave a list of typical headings. I'll use "Schedule" for schedule, and for company/address, I'll include in a

              under "Schedule" or as a separate "Company" heading? The rule says "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

              or drop it." Company and address are not job ID. They are location. Could be "Location". I'll include a "Location" heading. But the rule says "Prefer a few substantive sections over many thin ones." So maybe combine schedule and location into one "Details" section? But "Details" not in list. I'll create a "Schedule" section with schedule info, and a "Location" section with company and address. That's two thin sections. Could combine into one "Job Details" section. But not in list. I'll decide to include a "Schedule" section with schedule info, and a "Location" section with company and address. That seems reasonable. Equal Opportunity Employer statement is boilerplate, remove. Now, let's write HTML. Structure:

              About the role

              ...role description...

              Requirements

              • Current Registered Nurse license issued by the state in which services will be provided or current multi-state Registered Nurse license through the enhanced Nurse Licensure Compact (eNLC).
              • Obtain certification in Basic Life Support within 30 days of hire date.
              • One (1) year of nursing experience.

              Specialty Accreditation Requirements

              • Completion of annual required education related to specialty accreditation as defined by accreditation standards. Training may be completed through CBLs, trainings, In-services, and competency validation.

              Responsibilities

              • Modifies patient’s plan of care based on data collection and patient’s individual needs.
              • Uses Evidence-Based Practice (EBP) to provide patient care.
              • Delegates according to scope of practice.
              • Verifies the plan of care with interprofessional colleagues, patient, and caregiver(s).
              • Provides education based on learning needs and involvement of family.
              • Promotes effective communication among interprofessional team members & healthcare consumers.
              • Influences policy to promote safe patient care.
              • Utilizes appropriate resources in providing care, especially in sensitive situations.
              • Incorporates processes to enhance the organizational plan of growth and influence.
              • Participates in developing strategies to promote healthy communities and practice environments.
              • Recognizes strategies to improve nursing quality.
              • Provides critical review and/or evaluation of policies, procedures, and guidelines to improve quality of healthcare.
              • Demonstrates understanding of importance of data collection and utilization.
              • Disseminates educational findings, experiences, and ideas with peers.
              • Engages in activities related to nurse sensitive indicators to enhance quality of care.
              • Participates in continuing professional development.
              • Identifies ethical situations and seeks assistance of appropriate colleagues.
              • Identifies ways to maintain and improve ethical environment of the work setting conducive to safe, quality health care.
              • Adheres to the moral and legal rights of patients.
              • Engages in opportunities for work/life balance.

              Physical Requirements

              • The National Institute for Occupational Safety and Health recommends minimizing the need for employees to manually lift patients, and limit safe patient handling to 35 pounds. All transfers, lifts and re-positioning will be completed utilizing the lift equipment and/or other patient handling aids as indicated by the patient’s profile and appropriate algorithms.
              • Heavy/Hard work: Work requires strength and/or stamina, lifting, moving, stooping, reaching, standing, walking, and carrying of materials and equipment weighing 40+lbs.
              • Visual acuity must be within normal range.
              • Hearing within normal range is required (i.e. to assess breath sounds, bowel sounds, apical pulse, monitors, etc.)

              Working Environment

              • Working protracted or irregular hours.
              • Working around biohazards.
              • Working around infectious diseases.
              • Working with or near the deceased.
              • Working with hands in water.
              • Working with electrical hazards associated with patient care equipment.

              Skills

              • Possesses the interpersonal skills to positively and effectively communicate, negotiate, and resolve conflict.
              • Uses competent clinical