RN Infusion Therapy PRN

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID. Remove boilerplate like EEO, legal, etc. Must preserve all substantive info. Let's parse the posting: - Employment Type: Part time - Shift: Day Shift - Description: At Saint Alphonsus Health System, we are looking for people who are living out their calling... (some prose) - Skills, Knowledge, Education & Experience: list of requirements: RN license, multistate license residency, BLS certification, etc. - Essential Functions: list of duties (many bullet-like sentences) - About Saint Alphonsus: paragraph about benefits, culture, etc. Also mention competitive compensation with full benefits package, opportunity for growth, etc. Also mention social media links (should be removed as navigation? It's not boilerplate but maybe considered navigation? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Social media links maybe considered navigation? Might be okay to keep? Probably they are not essential; but they are not boilerplate. However they are not substantive job content; they are just promotional. Could be removed as navigation. Safer to remove them. - Also mention Equal Opportunity Employer etc. That's EEO boilerplate; must remove. Thus we need sections: - About the role: could be the Description paragraph? Or maybe "About Saint Alphonsus" is about the organization. The role description is the first paragraph after Description. We'll treat that as About the role. - Responsibilities: Essential Functions list. - Requirements: Skills, Knowledge, Education & Experience (license, BLS, etc.) - Qualifications: maybe combine with Requirements? But we need to decide. The posting includes "Skills, Knowledge, Education & Experience" which is essentially qualifications. Could treat as Qualifications. Could also have Skills section separate? But we should avoid thin sections. Perhaps combine Requirements and Qualifications into one? But we need to follow headings list; we can include only those with content. Could have "Requirements" for license/certifications, and "Qualifications" for experience/education? However the posting doesn't separate experience beyond RN license and new graduate vs experienced. That is in Essential Functions? Actually there is a paragraph about new graduate nurses hired as Level I etc. That's more about role expectations and career ladder. Could be part of Responsibilities or Qualifications. Might be better to put under Qualifications. Let's extract substantive content: Description paragraph: "At Saint Alphonsus Health System, we are looking for people who are living out their calling. We want you to be passionate about coming to work, and challenged to achieve your potential. Living by these virtues, we pride ourselves on exceptional service and the highest quality of care." That's about the role/organization. Essential Functions list: many sentences each starting with a verb. We'll turn each into

. Skills, Knowledge, Education & Experience: bullet-like sentences: - A current RN license is required. - Multistate licenses must establish residency with the Idaho Board of Nursing within 60 days from hire. - At hire, Basic Life Support certification from the American Heart Association or American Red Cross is required. (ACLS and/or PALS may be accepted in lieu of BLS) - Other certifications may be required as identified in the SAHS Certification Crosswalk. Also there is mention about new graduate nurses hired as Level I etc. That is under Essential Functions? Actually after Essential Functions list there is a paragraph: "New graduate nurses are hired on as a Level I with the expectation of advancing to a Level II after successful completion of the first year of employment and accomplishing the specific department criteria and competencies for a Level I RN. Level II must be maintained for the duration of employment with the opportunity to advance on the Professional Development Ladder if criteria are met. New experienced RN hires with one year of experience or more are hired as Level II’s with the expectation that Level II be maintained for the duration of employment with the opportunity to advance on the Professional Development Ladder if appropriate criteria are met." That seems like qualifications/expectations; could be placed under Qualifications. About Saint Alphonsus paragraph: "Colleagues of Saint Alphonsus Health System enjoy competitive compensation with a full benefits package and opportunity for growth throughout SAHS and Trinity Health! Visit www.saintalphonsus.org/careers to learn more about the benefits, culture, and career development opportunities available to you at Saint Alphonsus Health System. Visit Saint Alphonsus on LinkedIn, Facebook, Instagram, YouTube, and Twitter!" plus EEO stuff after. We need to keep substantive info: competitive compensation with full benefits package, opportunity for growth. The visit URLs maybe navigation; could be removed. The social media links maybe navigation; remove. So we keep: "Colleagues of Saint Alphonsus Health System enjoy competitive compensation with a full benefits package and opportunity for growth throughout SAHS and Trinity Health!" Also maybe we could include Benefits section: they mention full benefits package. But we don't have details; just mention full benefits package. According to rule: never create Benefits section unless posting actually states them. It does state "full benefits package". That's somewhat vague but still a statement. However they said avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Full benefits package" is not filler; it's a statement. Could create Benefits section with that sentence. But we also have mention of competitive compensation; could be Pay section? They said "competitive compensation". That's vague but still a statement. However they said avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Competitive compensation" is somewhat vague but maybe acceptable? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state competitive compensation and full benefits package. So we could include Pay and Benefits sections with those statements. However we need to avoid thin sections; but we have substantive content for both. Schedule: they gave Employment Type: Part time, Shift: Day Shift. That's schedule info. So we can create Schedule section with that. Thus sections: - About the role (description paragraph) - Responsibilities (Essential Functions) - Requirements (license, certifications) - Qualifications (new graduate vs experienced RN level info) - Benefits (full benefits package) - Pay (competitive compensation) - Schedule (Part time, Day Shift) We must not repeat job title. Use

for each section heading. Use

• for any list of duties/requirements/benefits. For prose use

  . We need to ensure we don't include boilerplate like EEO, navigation, social media, application instructions. Let's craft HTML. First, About the role:

  About the role

  At Saint Alphonsus Health System, we are looking for people who are living out their calling. We want you to be passionate about coming to work, and challenged to achieve your potential. Living by these virtues, we pride ourselves on exceptional service and the highest quality of care.

  Second, Responsibilities:

  Responsibilities

  • Meets medical center’s Guiding Behaviors and Caring Standards including interpersonal communication and professional conduct expectations with all co-workers, other departments, and with patients and visitors.
  • Demonstrates knowledge and skills to competently care for all assigned age groups (Neonate, Child, Adolescent, Adult, and Geriatric as applicable).
  • Revenue Management - Ensure the accuracy of documenting services and supplies provided to the patients.
  • Demonstrates compliance with hospital safety policies and procedures.
  • Performs and documents comprehensive physical and psychosocial assessments.
  • Educates patient based on assessment of needs.
  • Develops, implements and evaluates a plan of care based on patient's needs.
  • Communicates patient's current status and plan of care to other caregivers (verbally and in writing).
  • Prepares, gives and evaluates the effectiveness of medications.
  • Demonstrates safe operation of patient care equipment.
  • Advocates for the rights of patients.
  • Provides nursing measures to alleviate or reduce pain.
  • Demonstrates therapeutic communication.
  • Establishes therapeutic and professional boundaries.
  • Integrates knowledge, experience, professional standards and hospital policies into nursing practice.
  • Meets unit specific technical skills.
  • Practices with the rules and regulations defined by the Idaho State Board of Nursing.
  Third, Requirements:

  Requirements

  • A current RN license is required.
  • Multistate licenses must establish residency with the Idaho Board of Nursing within 60 days from hire.
  • At hire, Basic Life Support certification from the American Heart Association or American Red Cross is required. (ACLS and/or PALS may be accepted in lieu of BLS)
  • Other certifications may be required as identified in the SAHS Certification Crosswalk.
  Fourth, Qualifications:

  Qualifications

  New graduate nurses are hired on as a Level I with the expectation of advancing to a Level II after successful completion of the first year of employment and accomplishing the specific department criteria and competencies for a Level I RN. Level II must be maintained for the duration of employment with the opportunity to advance on the Professional Development Ladder if criteria are met. New experienced RN hires with one year of experience or more are hired as Level II’s with the expectation that Level II be maintained for the duration of employment with the opportunity to advance on the Professional Development Ladder if appropriate criteria are met.

  Fifth, Benefits:

  Benefits

  Colleagues of Saint Alphonsus Health System enjoy competitive compensation with a full benefits package and opportunity for growth throughout SAHS and Trinity Health!

  But note we already used "competitive compensation" in Benefits; maybe better to separate Pay and Benefits. However the sentence includes both compensation and benefits. Could split: Pay: competitive compensation; Benefits: full benefits package and opportunity for growth. But opportunity for growth is not a benefit per se but could be under Benefits. Let's follow instruction: create Pay and Benefits sections only if posting actually states them. It states "competitive compensation" and "full benefits package". So we can have: Pay section: competitive compensation. Benefits section: full benefits package and opportunity for growth. But the sentence also includes "opportunity for growth throughout SAHS and Trinity Health!" which is more about career development; could be under Benefits or maybe under About the role. But we already have About the role. Might be okay to keep in Benefits. Let's separate: Pay:

  Pay

  Competitive compensation.

  Benefits:

  Benefits

  Full benefits package and opportunity for growth throughout SAHS and Trinity Health.

  Schedule:

  Schedule

  Part time, Day Shift.

  Now check for any duplicated lines: we have not included the social media links, EEO, etc. Check for any filler: we have no "commensurate with experience", etc. All substantive info preserved? Let's verify: - Description paragraph: included. - Essential Functions: all bullet points included. - License, multistate residency, BLS, other certifications: included. - New graduate vs experienced RN level info: included. - Competitive compensation: included in Pay. - Full benefits package: included in Benefits. - Opportunity for growth: included in Benefits. - Part time, Day Shift: included in Schedule. We omitted the visit URLs and social media links; they are navigation, okay to remove. We omitted the EEO statements; good. We omitted the "