Registered Nurse (RN) - Emergency

We need to produce HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. The provided text includes: Summary (Occasionally JOB SUMMARY/PURPOSE...), DEPARTMENT DESCRIPTION, EXPERIENCE/EDUCATION/QUALIFICATIONS, KNOWLEDGE/SKILLS/ABILITIES, PHYSICAL DEMANDS (a table-like list). No explicit Benefits, Pay, Schedule. So we should not include those sections. We need to map content to appropriate headings: "About the role" could correspond to JOB SUMMARY/PURPOSE and DEPARTMENT DESCRIPTION combined? Possibly we can have "About the role" heading with prose summarizing job summary and department description. "Responsibilities" maybe not explicit; but we could infer responsibilities from job summary? However we must not invent detail. The posting does not list responsibilities explicitly; only summary says RN accountable for utilizing nursing process to provide safe, age-appropriate direct and indirect patient care. That could be considered responsibilities. But we need to be careful: we should not invent; but we can use that sentence as responsibilities. The summary says: "The Registered Nurse (RN) is accountable for utilizing the nursing process to provide safe, age-appropriate, direct and indirect patient care, while practicing within the scope of practice of the Oregon State Board of Nursing." That is a responsibility. So we could put that under Responsibilities. "Requirements" and "Qualifications": The posting has EXPERIENCE/EDUCATION/QUALIFICATIONS: Current unencumbered Oregon RN license required. Healthcare Provider Level BLS required upon hire. NLH Emergency: ACLS and PALS required within 90 days of hire. TNCC/ATCN required within six (6) months of hire. That's qualifications/requirements. We could put under Requirements or Qualifications. Since we have both headings possible, but we should avoid thin sections. Perhaps combine into one section "Requirements" containing those bullet points. "Skills": KNOWLEDGE/SKILLS/ABILITIES section includes Social Perceptiveness, Adaptability/Flexibility, Time Management, Communication. Those are skills. So we can put under Skills. "Physical Demands": Could be under a separate section maybe "Physical Demands" but not in allowed headings list. Allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Physical Demands not listed; we could maybe incorporate into Responsibilities or Requirements? But better to create a section? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples, not exclusive? It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. But we could still add other headings if needed? The instruction says "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 are typical. However they also say "Prefer a few substantive sections over many thin ones." So we could combine physical demands into Responsibilities or Requirements? Might be better to add a section "Physical Demands" as

but it's not in the list; risk of being considered not following instruction. Safer to incorporate physical demands into Responsibilities or Requirements? Probably Responsibilities includes physical demands? Not exactly. Could add a section "Physical Demands" but risk being marked incorrect. However the instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." implies those are examples, not exhaustive. So we can use other headings if needed. I'd include Physical Demands as its own section. We must not repeat job title as heading. No Job ID etc. We must remove boilerplate etc. The provided text seems clean. We need to output only HTML fragment, no /, no markdown fences. We'll produce something like:

About the role

The Registered Nurse (RN) is accountable for utilizing the nursing process to provide safe, age-appropriate, direct and indirect patient care, while practicing within the scope of practice of the Oregon State Board of Nursing. The Emergency Department provides care for patients with a wide variety of needs from non-critical to emergent medical conditions including emergent and urgent mental health care. All patients are welcome whether walking in or arriving by emergency transport. All Emergency Department staff are certified to care for critical cardiac and trauma patients including children.

Responsibilities

Utilize the nursing process to deliver safe, age-appropriate direct and indirect patient care; practice within Oregon State Board of Nursing scope; respond to diverse patient populations; manage time and prioritize tasks; communicate effectively with team members and patients.

But we must not invent details beyond what's given. The responsibilities we wrote includes some inference (respond to diverse patient populations, manage time, communicate). Those are from knowledge/skills section. Might be okay but could be considered invention. Better to keep responsibilities exactly as the summary sentence: "The Registered Nurse (RN) is accountable for utilizing the nursing process to provide safe, age-appropriate, direct and indirect patient care, while practicing within the scope of practice of the Oregon State Board of Nursing." That's the only responsibility given. So we can put that as responsibilities. Then Requirements: list bullet points. Qualifications: maybe same as requirements; we could combine. But we have both headings; we could put license and certifications under Requirements, and maybe nothing under Qualifications (but we shouldn't create empty heading). So better to have only one of them. Choose Requirements. Skills: list bullet points from knowledge/skills/abilities. Physical Demands: we could present as

• ... but it's a big list. We could just output as

  with the list? But instruction: Use

  • for any list of duties/requirements/benefits. Physical demands is a list, so we should use
    • . We'll need to parse the physical demands text: It's a weird format with categories and frequencies. We need to preserve all substantive information. The text includes headings like "CLIMB - STAIRS", "LIFT (Floor to Waist: 0\"-36\") 40 - 60 Lbs", etc. It's a table-like but we can just keep as is, each line as
    • . We'll need to extract each line. Let's copy the physical demands section exactly as given: PHYSICAL DEMANDS Rarely (1 - 10% of the time) (11 - 33% of the time) Frequently (34 - 66% of the time) Continually (67 - 100% of the time) CLIMB - STAIRS LIFT (Floor to Waist: 0"-36") 40 - 60 Lbs LIFT (Waist to Eye: up to 54") 20 - 40 Lbs SQUAT Static (hold >30 sec) KNEEL (on knees) SIT LIFT (Floor to Waist: 0"-36") 20 - 40 Lbs LIFT (Knee to chest: 24"-54") 0 - 20 Lbs LIFT (Waist to Eye: up to 54") 0 - 20 Lbs LIFT (Overhead: 54" and above) 0 - 20 Lbs CARRY 1-handed, 0 - 20 pounds CARRY 2-handed, 20 - 40 pounds SQUAT Repetitive ROTATE TRUNK Sitting REACH - Upward PULL (20-40 pounds force) WALK - LEVEL SURFACE LIFT (Floor to Waist: 0"-36") 0 - 20 Lbs CARRY 2-handed, 0 - 20 pounds ROTATE TRUNK Standing MANUAL DEXTERITY Hands/wrists FINGER DEXTERITY PINCH Fingers PULL (0-20 pounds force) STAND BEND FORWARD at waist REACH - Forward GRASP Hand/Fist PUSH (0-20 pounds force) PUSH (20-40 pounds force) PUSH (40-60 pounds force) PUSH (60 or more pounds force) This is messy. Likely they intended a table with frequency columns but got flattened. We need to preserve all substantive information; we can just output as a

      containing the text? But instruction says use

      • for any list of duties/requirements/benefits. Physical demands is a list, but it's not clearly delineated items. Could treat each line after the frequency header as an item. However the lines are not separated by line breaks in the source? They are separated by spaces. We could split by double spaces? Might be too complex. Simplify: We'll output the physical demands as a

        preserving the exact text (including line breaks). That may violate the instruction to use

        • for any list, but it's not a clear list. The instruction may be interpreted as: if there is a list (like bullet points), use
          • . Physical demands is not a list but a table; we can keep as

            . I'll do that. Now produce HTML:

            About the role

            The Registered Nurse (RN) is accountable for utilizing the nursing process to provide safe, age-appropriate, direct and indirect patient care, while practicing within the scope of practice of the Oregon State Board of Nursing. The Emergency Department provides care for patients with a wide variety of needs from non-critical to emergent medical conditions including emergent and urgent mental health care. All patients are welcome whether walking in or arriving by emergency transport. All Emergency Department staff are certified to care for critical cardiac and trauma patients including children.

            Responsibilities

            The Registered Nurse (RN) is accountable for utilizing the nursing process to provide safe, age-appropriate, direct and indirect patient care, while practicing within the scope of practice of the Oregon State Board of Nursing.

            Requirements

            • Current unencumbered Oregon RN license required.
            • Healthcare Provider Level BLS required upon hire.
            • ACLS and PALS required within 90 days of hire (NLH Emergency).
            • TNCC/ATCN required within six (6) months of hire.

            Skills

            • Social Perceptiveness: Ability to work with a diverse population from pediatrics to geriatrics; basic understanding of age-related differences in caring for and/or communicating with patients and caregivers; personal sensitivity to the needs and experiences of others; non‑judgmental attitude towards persons of differing standards, values, lifestyles, and ages.
            • Adaptability/Flexibility: Ability to respond quickly and appropriately to situations that may arise with high risk or diverse patient populations; ability to adjust actions in relation to others and adapt to offer best possible care to patients.
            • Time Management: Ability to organize, plan and prioritize work to complete within required time frames and to follow‑up on pending issues; ability to perform multiple tasks simultaneously and thrive in dynamic fast‑paced environments and under pressure.
            • Communication: Effective written and oral communication skills to explain complex issues, exchange information between team members, and tactfully discuss issues.