Registered Nurse (RN)- PACU - Part Time

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 from the posting: - Schedule information (first line) - "A Brief Overview" - this is like "About the role" - "What You Will Do" - Responsibilities - "Additional Responsibilities" - more responsibilities - "Primary Location" and "Work Locations" - location info - Job metadata (Organization, Schedule, Employee Status, Job Type, Job Level, Travel, Remote Work, Job Posting date) - Education requirements - Knowledge, Skills, & Abilities - Licenses and Certifications - Physical Demands - Travel Requirements 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 - Do NOT put Job ID/requisition numbers as headings - Fold minor metadata into short

  or drop - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/scam-warning, duplicated lines, application instructions) - Include section ONLY when posting has real, specific content for it - Never emit heading followed by filler/placeholder text (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 me map the content to appropriate sections: 1. Schedule - the first line gives schedule details: "Three 8s per week M-F plus call (4-5 shifts per 6 week schedule and one weekend day per projection)" - this is specific schedule info, so I should include a Schedule section. 2. "A Brief Overview" - this is "About the role" content. 3. "What You Will Do" - Responsibilities. 4. "Additional Responsibilities" - more responsibilities, can combine with above or separate. 5. Location info - Primary Location and Work Locations. Could be part of a "Location" section or folded into metadata. 6. Job metadata: Organization, Schedule (Part-time), Employee Status, Job Type, Job Level, Travel, Remote Work, Job Posting date. Some of this is minor metadata. The schedule is already covered. Travel says "No" but later "Travel Requirements 10%" - conflict? The metadata says Travel No, but Physical Demands section says Travel Requirements 10%. I'll include the 10% in Physical Demands or separate. 7. Education - specific degrees required/preferred. 8. Knowledge, Skills, & Abilities - specific items. 9. Licenses and Certifications - specific licenses. 10. Physical Demands - detailed list. 11. Travel Requirements - 10%. I need to decide on sections. The rules say use

  for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But only include if real content. Let me create sections: - Schedule (since specific schedule given) - About the role (from Brief Overview) - Responsibilities (from What You Will Do and Additional Responsibilities) - Qualifications (could combine Education, Licenses, Knowledge/Skills) - Physical Demands (detailed list) - Location (maybe) But the rules mention "Requirements, Qualifications, Skills" as possible headings. I should use appropriate headings. Better to have: - Schedule - About the role - Responsibilities - Qualifications (including Education, Licenses, Knowledge/Skills) - Physical Demands Travel Requirements could be part of Physical Demands or separate. Since it's a single line "Travel Requirements 10%", I can include in Physical Demands or as a small note. Also, the metadata like Organization, Job Posting date, etc. are minor. I can fold into a short

  at the end or beginning. The posting has "Job Posting Oct 19, 2026, 9:56:06 AM" - that's a date, minor. "Organization St._John_Medical_Center" - could be part of location. "Work Locations 29000 Center Ridge Road" - address. I'll create a "Location" section or include in a metadata paragraph. But the rules say "fold minor metadata into a short

  or drop it". So I can create a paragraph with key metadata: organization, location, schedule type (part-time), job type, travel, remote work. However, schedule is already a section. The metadata says "Schedule Part-time" but the detailed schedule is given at top. I'll use the detailed schedule in Schedule section. Let me structure:

  Schedule

  Three 8-hour shifts per week, Monday–Friday, plus call (4–5 shifts per 6-week schedule and one weekend day per projection).

  About the role

  Provides safe, efficient, age-specific nursing care to patients/families using the nursing process to assist them to attain, maintain, regain, and sustain optimal health status.

  Responsibilities

  • Implements the nursing process by delivering effective relationship-based nursing care.
  • Demonstrates technical skills in care delivery that result in safe practice and positive care outcomes.
  • Demonstrates clear communication and effective collaboration to optimize patient care and clinical operations.
  • Develops self and contributes to the professional practice of nursing.
  • Displays leadership that influences optimal clinical and operational outcomes.
  • Performs other duties as assigned.
  • Complies with all policies and standards.
  • Must abide by all requirements to safely and securely maintain Protected Health Information (PHI) for patients; annual training, the UH Code of Conduct, and UH policies and procedures address appropriate use of PHI in the workplace.

  Qualifications

  Education

  • Diploma in Nursing or Associate's Degree in Nursing (ADN) — required
  • Bachelor's Degree in Nursing (BSN) — preferred
  • Master's Degree in Nursing (MN) — preferred

  Licenses & Certifications

  • Registered Nurse (RN), Ohio and/or Multi-State Compact License — required upon hire
  • Basic Life Support (BLS) — required upon hire
  • Advanced Cardiac Life Support (ACLS) — may be required based on clinical care standards of the unit (refer to ACLS/PALS Unit Requirements document on DWP Nursing Portal)
  • Pediatric Advanced Life Support (PALS) — may be required based on clinical care standards of the unit (refer to ACLS/PALS Unit Requirements document on DWP Nursing Portal)

  Knowledge, Skills & Abilities

  • Knowledge of nursing process and practice (required proficiency)
  • Uses a wide variety of technical equipment to meet patient needs and prescribed clinical therapies (e.g., stethoscopes, thermometers, sphygmomanometers, electronic monitoring devices) (required proficiency)

  Physical Demands

  • Standing — frequently
  • Walking — frequently
  • Sitting — rarely
  • Lifting — frequently up to 50 lbs
  • Carrying — frequently up to 50 lbs
  • Pushing — frequently up to 50 lbs
  • Pulling — frequently up to 50 lbs
  • Climbing — occasionally up to 50 lbs
  • Balancing — occasionally
  • Stooping — frequently
  • Kneeling — frequently
  • Crouching — frequently
  • Crawling — occasionally
  • Reaching — frequently
  • Handling — frequently
  • Grasping — frequently
  • Feeling — constantly
  • Talking — constantly
  • Hearing — constantly
  • Repetitive motions — constantly
  • Eye/hand/foot coordination — constantly

  Travel requirements: 10%.

  Location

  St. John Medical Center, 29000 Center Ridge Road, Westlake, Ohio, United States.

  Part-time, regular, professional-level position. No remote work. Posted October 19, 2026.

  But the rules say "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." The metadata includes Job Posting date, Organization, etc. I'll fold into a paragraph. Also, the rules say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". I used

  for subsections under Qualifications. That's okay? The rule says use

  for section headings, but doesn't forbid

  for subsections. However, to keep it simple, maybe I should use

  for all top-level sections and use

  with bold or something for subcategories. But the example shows "Requirements, Qualifications, Skills" as separate headings. I could make Education, Licenses, Knowledge as separate

  sections. But that might be too many thin sections. The rule says "Prefer a few substantive sections over many thin ones." So combining under Qualifications with subheadings is fine, but using

  might not be allowed? The instruction says "use

  for section headings". It doesn't say you can't use other heading levels, but to be safe, I'll use

  for main sections and maybe use for subcategories within a list. Alternatively, I can make separate

  sections: Education, Licenses & Certifications, Knowledge & Skills. But they are all qualifications. I'll keep as one Qualifications section with sub-lists. But the HTML should be semantic. Using

  is semantic. I think it's acceptable. However, the user said "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This implies those are the section headings to use. So I should use

  for each of those that have content. For subcategories, I can use

  or just bold text. I'll use

  for main sections, and within Qualifications, use

  for Education, Licenses, Knowledge. That seems fine. Now, check for any boilerplate to remove: The posting includes "For specific duties and responsibilities, refer to documentation provided by the department during orientation." That's part of Additional Responsibilities, I included. "Annual training, the UH Code of Conduct and UH policies and procedures are in place to address appropriate use of PHI in the workplace." Included. "Primary Location United States-Ohio-Westlake Work Locations 29000 Center Ridge Road Job Nurse – more than 1 year experience Organization St._John_Medical_Center Schedule Part-time Employee Status Regular Job Type Standard Job Level Professional Travel No Remote Work No Job Posting Oct 19, 2026, 9:56:06 AM" - this is metadata. I'll fold into a paragraph. "Education Other