Registered Nurse - PACU (BCH-Walnut Creek)

We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to extract content. Job Description paragraph: "The UCSF Benioff Children's Hospital Walnut Creek OR is seeking a dedicated nurse to join its team. With a multidisciplinary approach, the hospital offers a range of services including orthopedics, urology, and general surgery. The successful candidate will be responsible for utilizing the nursing process to provide patient care, working collaboratively with the team, and ensuring a harmonious work environment. This role requires flexibility to work across UCSF Health locations and a commitment to maintaining high standards of patient care and customer service." We can treat that as About the role (or Responsibilities?). The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content. We have: - About the role: could be the description paragraph. - Responsibilities: maybe the duties: utilizing nursing process, providing patient care, working collaboratively, ensuring harmonious work environment, flexibility to work across locations, commitment to high standards. - Requirements: maybe the required qualifications list. - Qualifications: maybe the preferred qualifications? But we already have Required Qualifications and Preferred Qualifications. Could combine under Qualifications? The instruction says we can have Qualifications section. We could put both required and preferred under Qualifications, maybe separate sub-sections? But we only allowed headings from list; we could have Qualifications heading and then list items. - Skills: maybe communication, organization, computer skills, etc. - Benefits: none given (no benefits specifics). So we should not create Benefits section. - Pay: there is Salary Information but it's vague: "The final salary and offer components are subject to additional approvals based on UC policy. Your placement within the salary range is dependent on a number of factors..." No specific numbers. According to rule: 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. The posting does not give actual salary range, just generic statement. So we should NOT create Pay section. - Schedule: not mentioned specifically (no shift details). So no Schedule. - About Us: we have About UCSF and Pride Values etc. That could be About the role? Actually About Us is separate. Could we make a section "About the role"? Already used. Maybe we could have "About the organization" but not in allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should fit content into those. The About UCSF description could go under About the role? Might be okay. Or we could put it under Responsibilities? Not ideal. Perhaps we can include an "About the role" section that includes both the role description and the organization overview. That seems acceptable. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details: services (orthopedics, urology, general surgery), nursing process, collaborative team, harmonious work environment, flexibility across UCSF Health locations, commitment to high standards patient care and customer service. Qualifications Required: list items. Preferred Qualifications: list items. Licensure/Certifications: list items. We could treat Licensure/Certifications as part of Qualifications or Skills. Since we have Qualifications heading, we can include both required and preferred qualifications and licensure under that. But we need to preserve all info; we can make sub-lists? Not required; we can just list all items under Qualifications. But we also have Skills: communication, organization, multi-task, computer skills. Those could go under Skills heading. We need to avoid duplication. Let's structure:

About the role

... description paragraph plus About UCSF and Pride Values? Might be too much. But we can include About UCSF and Pride Values as part of About the role? Might be okay but could be considered filler? It's substantive about employer. Probably okay. Alternatively, we could have two sections: About the role and Responsibilities. But we need to decide. Let's parse: About the role: The UCSF Benioff Children's Hospital Walnut Creek OR is seeking a dedicated nurse to join its team. With a multidisciplinary approach, the hospital offers a range of services including orthopedics, urology, and general surgery. Responsibilities: The successful candidate will be responsible for utilizing the nursing process to provide patient care, working collaboratively with the team, and ensuring a harmonious work environment. This role requires flexibility to work across UCSF Health locations and a commitment to maintaining high standards of patient care and customer service. That seems logical. Then About UCSF and Pride Values could be considered "About the organization" but not in allowed headings. Could we put them under About the role as additional paragraph? Might be okay. Qualifications: Required Qualifications list. Skills: Preferred Qualifications? Actually preferred qualifications include Critical Care experience, BSN, Ambulatory Surgical Care Center experience. Those are more qualifications/experience. Could go under Qualifications as well. But we have Skills heading for communication, organization, multi-task, computer skills. Licensure/Certifications: could be under Qualifications or Skills. Probably Qualifications. Thus we have sections: About the role, Responsibilities, Qualifications, Skills. We must not create Benefits, Pay, Schedule. Now we need to output HTML fragment only. Let's craft:

About the role

The UCSF Benioff Children's Hospital Walnut Creek OR is seeking a dedicated nurse to join its team. With a multidisciplinary approach, the hospital offers a range of services including orthopedics, urology, and general surgery.

Responsibilities

The successful candidate will be responsible for utilizing the nursing process to provide patient care, working collaboratively with the team, and ensuring a harmonious work environment. This role requires flexibility to work across UCSF Health locations and a commitment to maintaining high standards of patient care and customer service.

Qualifications

• Two (2) years of recent PACU or PICU experience as an RN.
• Three (3) years of recent pediatric experience as an RN.
• Excellent verbal and written communication skills.
• Well-organized with strong attention to detail and the ability to multi-task under pressure.
• Basic computer keyboard skills and general PC knowledge.
• On-call commitment is required.
• Flexibility to orient and work at all UCSF Medical Center locations.
• Two (2) years of Critical Care experience as an RN (PICU, ED, ICU) – preferred.
• BSN degree is preferred.
• Experience in an Ambulatory Surgical Care Center is an asset.
• Current licensure as a Registered Nurse in California.
• Current healthcare provider CPR certification.
• Active American Heart Association PALS certification.
• ASPAN certification strongly preferred.

But we have mixed required and preferred; we could separate but not needed. However we duplicated communication skills etc. Already listed under required qualifications; we also have them as skills. Might be duplication. Better to separate: Qualifications for required and preferred experience/education; Skills for communication, organization, computer skills. Let's restructure. Qualifications (required experience/education): - Two (2) years of recent PACU or PICU experience as an RN. - Three (3) years of recent pediatric experience as an RN. - On-call commitment is required. - Flexibility to orient and work at all UCSF Medical Center locations. - Two (2) years of Critical Care experience as an RN (PICU, ED, ICU) – preferred. - BSN degree is preferred. - Experience in an Ambulatory Surgical Care Center is an asset. - Current licensure as a Registered Nurse in California. - Current healthcare provider CPR certification. - Active American Heart Association PALS certification. - ASPAN certification strongly preferred. Skills: - Excellent verbal and written communication skills. - Well-organized with strong attention to detail and the ability to multi-task under pressure. - Basic computer keyboard skills and general PC knowledge. That avoids duplication. Now we need to ensure we didn't miss any info: The description about multidisciplinary approach and services included in About the role. Responsibilities includes nursing process, collaborative team, harmonious work environment, flexibility across locations, commitment to high standards patient care and customer service. We also have About UCSF and Pride Values. Where to put? Could be part of About the role as additional paragraph after the first. Let's add a second paragraph under About the role: "About UCSF: The University of California, San Francisco (UCSF) is a leading university dedicated to promoting health worldwide through advanced biomedical research, graduate-level education in the life sciences and health professions, and excellence in patient care. It is the only campus in the 10-campus UC system dedicated exclusively to the health sciences. We bring together the world’s leading experts in nearly every area of health. We are home to five Nobel laureates who have advanced the understanding of cancer, neurodegenerative diseases, aging and stem cells. Pride Values: UCSF is a diverse community made of people with many skills and talents. We seek candidates whose work experience or community service has prepared them to contribute to our commitment to professionalism, respect, integrity, diversity and excellence – also known as our PRIDE values. In addition to our PRIDE values, UCSF is committed to equity – both in how we deliver care as well as our workforce. We are committed to building a broadly diverse community, nurturing a culture that is welcoming and supportive, and engaging diverse ideas for the provision of culturally competent education, discovery, and patient care." We should not include the link "Additional information about UCSF is available here ." That's a navigation/link; we can drop it. Also "Join us to find a rewarding career contributing to improving healthcare worldwide." That's a call to action; could be considered boilerplate? It's not exactly legal/EEO but it's a generic invitation. Might be considered filler? It's not specific detail; but it's still substantive? It's a generic statement. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This line is not exactly those categories but could be considered generic fluff. Safer to omit? It's not required to preserve; it's not essential info about role. I'd omit. Also "Equal Employment Opportunity" boilerplate should be removed. Salary Information: we decided not to create Pay section because it's vague. Should we include it as a paragraph under About the role? It's not specific salary; it's generic. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state salary information but it's vague. The rule says: 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. It does state them, but it's vague. However we could still include the salary info as a paragraph under About the role? The rule about sections: we should not create Pay section. But we could include the salary info as a paragraph elsewhere (maybe under About the role). However the info is generic and not specific; but it's still stated. The instruction about not creating sections unless posting actually states them refers to headings. So we can include the salary info as a paragraph under About the role or maybe under a separate heading like "Compensation"? Not allowed. So we could embed it in About the