HYBRID Clinic RN - Centralized Triage

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate etc. We need to parse description. Key content: - Description paragraph: "The Journey Clinic RN provides comprehensive nursing care for patients in an ambulatory care environment based on individual physical, emotional, spiritual needs, and appropriate care strategies throughout the lifespan. This position facilitates care coordination by using the nursing process to assess, identify, plan, implement, and evaluate all aspects of care and teaching needs via direct and telephonic/telehealth or electronic encounters. This role works in collaboration with other members of the health care team. The Clinic RN maintains compliance with professional nursing standards and regulatory requirements and supports clinicians in delivering quality health care to patients. Actions will reflect the organization's core values. Providence caregivers are not simply valued – they’re invaluable. Join our team at Swedish Health Services DBA Swedish Medical Group in our culture of patient-focused, whole-person care built on understanding, commitment, and mutual respect. Your voice matters here, because we know that to inspire and retain the best people, we must empower them." That's prose about role. Could go under "About the role" or "Responsibilities". We need to decide sections. We have "Required Qualifications" list: Graduate of an accredited registered nursing school. Associate's Degree Nursing Or Bachelor's Degree Nursing. Washington Registered Nurse License upon hire. National Provider BLS - American Heart Association upon hire. 18 months professional nursing experience. That's qualifications. We have "Why Join Providence?" paragraph about benefits: best-in-class benefits designed to support you and your family in staying well, growing professionally, achieving financial security. We take care of you, so you can focus on delivering our mission... Then "About Providence" paragraph about organization, mission, benefits, inclusive workplace, etc. Then "Providence offers a comprehensive benefits package including a retirement 401(k) Savings Plan with employer matching, health care benefits (medical, dental, vision), life insurance, disability insurance, time off benefits (paid parental leave, vacations, holidays, health issues), voluntary benefits, well-being resources and much more. Learn more at providence.jobs/benefits." Also "Posted are the minimum and the maximum wage rates on the wage range for this position. The successful candidate's placement on the wage range for this position will be determined based upon relevant job experience and other applicable factors. These amounts are the base pay range; additional compensation may be available for this role, such as shift differentials, standby/on-call, overtime, premiums, extra shift incentives, or bonus opportunities." Later: "Providence offers a comprehensive benefits package..." Already covered. Also "Applicants in the Unincorporated County of Los Angeles: Qualified applications with arrest or conviction records will be considered for employment in accordance with the Unincorporated Los Angeles County Fair Chance Ordinance for Employers and the California Fair Chance Act." That's EEO/legal boilerplate; should be removed. Then "About The Team Providence Swedish is the largest not-for-profit health care system..." That's about organization; could be part of About Providence but maybe not needed as separate section. Might be considered boilerplate? It's substantive about team but maybe we can include under "About the role" or "About Providence". However we need to avoid duplication. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About The Team" might be considered not boilerplate but descriptive; but we already have About Providence. Might be redundant. We could keep a short paragraph about team under "About the role" or "About Providence". But we need to preserve ALL substantive information; not invent or summarize away detail. So we need to include that info somewhere. However we must not create sections with filler. We can include it under "About the role" as prose. Also we have details: Job Schedule: Per-Diem, Job Shift: Day, Career Track: Nursing, Department: 3908 FLOAT PERSONNEL WA 1, Address: WA Seattle 515 Minor Ave Work Location: Swedish First Hill 515 Minor-Seattle Workplace Type: Hybrid. These are metadata; we should not put Job ID/requisition numbers as headings; fold minor metadata into a short

or drop it. The schedule and shift etc could be considered schedule info. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can have a Schedule section if there is specific schedule info: "Per-Diem", "Day". That's specific. So we can include Schedule section with those details. Pay section: we have Pay Range: $43.82 - $68.03 and note about base pay range and additional compensation. That's specific, so include Pay section. Benefits section: we have details about benefits: retirement 401(k) with employer matching, health care benefits (medical, dental, vision), life insurance, disability insurance, time off benefits (paid parental leave, vacations, holidays, health issues), voluntary benefits, well-being resources, plus earlier mention of best-in-class benefits. So include Benefits. Requirements vs Qualifications: The posting has "Required Qualifications". Could treat as Requirements section. Also there may be "Qualifications" separate? Not really. We'll have a Requirements section for those. Responsibilities: we have description of role; could be Responsibilities. Skills: not explicitly listed; maybe we can infer from responsibilities but we should not invent. So we should not create Skills section if no specific content. About the role: we could have a short intro about the role; but we already have Responsibilities covering that. The instruction: Prefer a few substantive sections over many thin ones. So we could combine About the role and Responsibilities into one section maybe "About the role". But we need headings exactly as allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to include only those with content. We could put the narrative under "About the role". Then responsibilities maybe not needed separately. But we have a list of duties: "provides comprehensive nursing care... facilitates care coordination... works in collaboration... maintains compliance... supports clinicians..." That's duties. Could be under Responsibilities. But we could also put them under About the role. To avoid thin sections, maybe we combine About the role and Responsibilities into one heading? But we must use allowed headings; we cannot create custom headings. We could choose to use "About the role" for the narrative and omit Responsibilities if it would be thin. However the narrative includes duties; it's still about the role. So we can put all that under About the role. Then we can omit Responsibilities heading. Requirements: we have required qualifications list. Could be Requirements. Qualifications: maybe we could separate education/license vs experience? But we have all in Required Qualifications. Could put under Requirements and omit Qualifications. Skills: none specific, omit. Benefits: include. Pay: include. Schedule: include. We also have workplace type Hybrid, location etc. Could be minor metadata; we could fold into a short p under About the role or Schedule? Not needed. We must not include Job ID etc. We must preserve all substantive info: need to include the description about Providence Swedish being largest not-for-profit health care system etc. That's substantive about team. Where to put? Could be under About the role as additional prose. Also the statement about "Your voice matters here..." etc. Also the statement about "Providence caregivers are not simply valued – they’re invaluable." etc. Also the statement about "Join our team at Swedish Health Services DBA Swedish Medical Group in our culture of patient-focused, whole-person care built on understanding, commitment, and mutual respect." Also the statement about "At Providence, our strength lies in Our Promise of “Know me, care for me, ease my way.” ..." Also the statement about "Together, our 120,000 caregivers (all employees) serve in over 50 hospitals, over 1,000 clinics and a full range of health and social services across Alaska, California, Montana, New Mexico, Oregon, Texas and Washington." Also the statement about "As a comprehensive health care organization, we are serving more people, advancing best practices and continuing our more than 100-year tradition of serving the poor and vulnerable." Also the statement about "Providence Swedish is the largest not-for-profit health care system in the greater Puget Sound area..." etc. We need to include all that. We must not include boilerplate like EEO, Fair Chance Ordinance, etc. Also remove duplicated lines. We also need to remove application instructions (like "Learn more at providence.jobs/benefits.") That's actually part of benefits description; it's okay to keep as it's part of benefits info. But the instruction says remove application instructions. That line is not exactly application instruction; it's a link to learn more about benefits. Might be okay to keep. We also need to remove "Posted are the minimum and the maximum wage rates..." we already used for Pay. Now craft HTML. Structure:

About the role

... (combined narrative)

Requirements

• Graduate of an accredited registered nursing school.
• Associate's Degree Nursing Or Bachelor's Degree Nursing
• Washington Registered Nurse License upon hire.
• National Provider BLS - American Heart Association upon hire.
• 18 months professional nursing experience

Benefits

• Retirement 401(k) Savings Plan with employer matching
• Health care benefits (medical, dental, vision)
• Life insurance
• Disability insurance
• Time off benefits (paid parental leave, vacations, holidays, health issues)
• Voluntary benefits
• Well‑being resources

Learn more at providence.jobs/benefits.

Pay

Pay range: $43.82 – $68.03 (base pay). Placement within the range is based on relevant job experience and other applicable factors. Additional compensation may be available, such as shift differentials, standby/on‑call, overtime, premiums, extra shift incentives, or bonus opportunities.

Schedule

Job schedule: Per‑Diem. Shift: Day. Workplace type: Hybrid. Location: Swedish First Hill, 515 Minor Ave, Seattle, WA.

We need to ensure we didn't miss any substantive info: The description about "The Journey Clinic RN provides comprehensive nursing care..." we included in About the role paragraph. Also the part about "This position facilitates care coordination..." etc. Also "This role works in collaboration..." etc. Also "The Clinic RN maintains compliance..." etc. Also "Actions will reflect the organization's core values." Also "Providence caregivers are not simply valued – they’re invaluable." Also "Join our team at Swedish Health Services DBA Swedish Medical Group in our culture of patient-focused, whole-person care built on understanding, commitment, and mutual respect." Also "Your voice matters here, because we know that to inspire and retain the best people, we must empower them." Also the Providence Swedish team description about largest not-for-profit health care system etc. Also the Providence mission statement "Know me, care for me, ease my way." Also the stats about 120,000 caregivers etc. Also the statement about serving more people, advancing best practices, continuing 100-year tradition serving poor and vulnerable. Also the "About The Team" details about eight hospital campuses etc. We need to include that. We need to incorporate all that into About the role paragraph(s). Could split into multiple

under same heading; that's fine