Hospice Home Care, RN Clinical Manager

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. Content: - Intro: "BAYADA Hospice is seeking a Clinical Nurse Manager (RN required) to join out our Wilmington, DE Home Hospice office. In this role, you will lead care teams committed to delivering the finest hospice services in the country. You will share your vision by leading a hospice interdisciplinary team and ensuring excellent clinical and social care. You will develop relationships within the community and local facilities, collaborate with other hospice providers, and recruit core hospice team members. This unique position allows you to keep your clinical skills strong, while at the same time developing relationships and leadership skills. BAYADA Hospice has a special purpose — to provide the highest quality end-of-life care so our patients can remain at home with comfort, grace, and dignity. We believe people with advanced illness and their families deserve hospice services and palliative care delivered with compassion, excellence, and reliability — the core values of our philosophy, The BAYADA Way." That's about the role. Could be "About the role" heading. - Then "Responsibilities for a Hospice RN Nurse Manager:" list items: Support the team by providing clinical guidance and judgment to promote understanding of and response to patient and family needs; Participate in Performance Improvement & Quality Assurance activities; Develop and mentor future hospice leaders. - Then "Qualifications for Hospice RN Nurse Manager:" list: Passion for focusing on hospice care (Former Hospice experience required); Desire to lead an interdisciplinary care team; Registered Nurse, BSN or Masters preferred; Management experience strongly preferred. - Then "Why you'll love BAYADA:" includes bullet points: Base Salary: $95,000-$98,000 / year depending on qualifications; BAYADA Home Health Care offers the stability and structure of a national company with the values and culture of a family-owned business.; Check out our blog: ... (list of awards); Paid Weekly; Mon-Fri work hours; AMAZING culture; Strong employee values and recognition; Small team at a local office; Growth opportunities; BAYADA Home Health Care offers a comprehensive benefits plan that includes the following: Paid holidays, vacation and sick leave, vision, dental and medical health plans, employer paid life insurance, 401k with company match, direct deposit and employee assistance program; To learn more about BAYADA Home Health Care benefits, https://www.bayada.com/benefits; BAYADA believes that our employees are our greatest asset: Enjoy being part of a team that cares and a company that believes in leading with our values.; Develop your skills with training and scholarship opportunities.; Advance your career with specially designed career tracks.; Be recognized and rewarded for your compassion, excellence, and reliability; As an accredited, regulated, certified, and licensed home health care provider, BAYADA complies with all state/local mandates.; BAYADA is celebrating 50 years of compassion, excellence, and reliability. Learn more about our 50th anniversary celebration and how you can join in here.; BAYADA Home Health Care, Inc., and its associated entities and joint venture partners, are Equal Opportunity Employers... (EEO boilerplate) - we need to remove EEO boilerplate. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should strip the EEO paragraph at the end. Also we need to remove duplicated lines? Not many. We need to preserve all substantive info. We need to decide sections: About the role (intro paragraph), Responsibilities (list), Qualifications (list), Benefits (list), Pay (salary), Schedule (Mon-Fri work hours, Paid Weekly maybe). Also maybe "Why you'll love BAYADA" could be split into Benefits, Culture, etc. But we should follow instruction: Use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They said "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings if content exists. We have About the role (intro). Responsibilities (list). Qualifications (list). Benefits (list of benefits). Pay (salary). Schedule (Mon-Fri work hours, Paid Weekly). Possibly also "Skills" but not explicit; we could skip if no specific skills list. Requirements maybe same as Qualifications? They have both Requirements and Qualifications as possible headings; we have Qualifications content; we could treat that as Qualifications. Requirements maybe not present; we can omit. We need to avoid filler like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

... intro paragraph ...

Responsibilities

• Support the team by providing clinical guidance and judgment to promote understanding of and response to patient and family needs
• Participate in Performance Improvement & Quality Assurance activities
• Develop and mentor future hospice leaders

Qualifications

• Passion for focusing on hospice care (Former Hospice experience required)
• Desire to lead an interdisciplinary care team
• Registered Nurse, BSN or Masters preferred
• Management experience strongly preferred

Benefits

• Paid holidays, vacation and sick leave
• Vision, dental and medical health plans
• Employer paid life insurance
• 401k with company match
• Direct deposit
• Employee assistance program

Pay

Base Salary: $95,000-$98,000 / year depending on qualifications

Schedule

• Paid Weekly
• Mon-Fri work hours

We might also include other "Why you'll love BAYADA" items like culture, growth opportunities, etc. Those could go under Benefits or maybe a separate section like "Why you'll love BAYADA" but not in allowed headings. Could incorporate into Benefits or maybe a separate

About the role? But we already have About the role. Could add a

About the role

extended with those culture points? But they are not about role; they are about company. Could add a

Benefits

extended to include culture, growth opportunities, recognition, small team, etc. However the instruction: "Use

• for any list of duties/requirements/benefits, and

  for prose." So we can put those as list items under Benefits. Thus Benefits list could include: Paid holidays, vacation and sick leave; Vision, dental and medical health plans; Employer paid life insurance; 401k with company match; Direct deposit; Employee assistance program; Paid Weekly; Mon-Fri work hours; AMAZING culture; Strong employee values and recognition; Small team at a local office; Growth opportunities; Training and scholarship opportunities; Specially designed career tracks; Recognition and rewarded for compassion, excellence, reliability; 50th anniversary celebration (maybe not needed). Also the blog links and awards maybe not needed as they are promotional; but they are substantive? Might be considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The blog links and awards are not boilerplate; they are promotional but could be kept. However they are not duties/requirements/benefits; they are more like "Why you'll love BAYADA". Could be placed under a section like "About the role" or maybe a separate heading not in list; but we are limited to those headings. Could add a

  About the role

  and include those as prose after intro? But that might mix. Better to create a section "Why you'll love BAYADA" but not in allowed headings; but instruction says use those headings as examples, not that we cannot use others? It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples; we could use other headings if needed, but better to stick to those. However we could incorporate those points into Benefits or About the role. Given the instruction to "Prefer a few substantive sections over many thin ones." So we could combine culture points into Benefits or maybe a separate "About the role" section that includes role description and why you'll love it. But that may dilute. I think we can create a section "Benefits" that includes all the benefits and also culture points, growth opportunities, etc. That seems reasonable. Thus Benefits list items: - Paid holidays, vacation and sick leave - Vision, dental and medical health plans - Employer paid life insurance - 401k with company match - Direct deposit - Employee assistance program - Paid Weekly - Mon-Fri work hours - AMAZING culture - Strong employee values and recognition - Small team at a local office - Growth opportunities - Training and scholarship opportunities - Specially designed career tracks - Recognition and rewarded for compassion, excellence, and reliability - 50th anniversary celebration (maybe optional) But note that Paid Weekly and Mon-Fri work hours also could go under Schedule; but we already have Schedule section. To avoid duplication, we should not repeat. So we keep Paid Weekly and Mon-Fri under Schedule only. Benefits list should exclude those. Thus Benefits list: Paid holidays, vacation and sick leave; Vision, dental and medical health plans; Employer paid life insurance; 401k with company match; Direct deposit; Employee assistance program; AMAZING culture; Strong employee values and recognition; Small team at a local office; Growth opportunities; Training and scholarship opportunities; Specially designed career tracks; Recognition and rewarded for compassion, excellence, and reliability; 50th anniversary celebration (maybe). Also maybe "Check out our blog: ..." and awards could be omitted as not essential. We need to preserve ALL substantive information; do not invent or summarize away detail. So we should keep the blog link and awards? They are substantive? They are about recognition; but they are not benefits per se. Could be under "Why you'll love BAYADA". Since we don't have a heading for that, maybe we can add a

  About the role

  and after the intro paragraph include a

  that mentions the blog and awards? But that might be stray. Better to create a section "Why you'll love BAYADA" as a heading, even if not in the examples, but 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 typical but not exclusive. However to be safe, we could use "Why you'll love BAYADA" as a heading; it's still an h3. The instruction didn't forbid other headings. It just gave examples. So we can add that. Thus we can have sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule, Why you'll love BAYADA. But we also need to avoid thin sections; Why you'll love BAYADA may be