Hospice Community Liaison

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 content. We need to parse the job posting. We have: - Job Type Full-time, Exempt, Reports to: Senior Director of Business Development. Compensation: $80,000 to $90,000 Potential Bonus: Up to 30% of base salary Schedule: Monday–Friday | 8:30 a.m.– 5:00 p.m. Location: Davis, CA - Why Community Liaisons Choose YoloCares (some prose) - What You Can Expect (list: Ranked among Top 1%..., Nationally ranked..., Competitive annual compensation..., Company laptop..., Mileage reimbursement..., Company vehicle..., Comprehensive benefits package) - Benefits YoloCares offers a comprehensive benefits package... (list of benefits) - About YoloCares (mission description) - About The Role (description) - Key Responsibilities (list of responsibilities under subheadings: Referral & Community Development, Business Development & Market Growth, Strategic Partnerships & Analysis) - Requirements (list of skills/abilities) - Education, Experience, & Licensing Requirements (list) - Physical & Other Job Specifications (list) - Salary Description $80,000 - $90,000 (duplicate of compensation) We need to produce sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content goes where. - About the role: we have "About The Role" paragraph describing role. Also maybe "Why Community Liaisons Choose YoloCares" and "What You Can Expect" could be part of About the role? But we should follow instructions: Use headings for sections as listed. We need to include a section only when posting has real, specific content for it. We have content for: - About the role: Yes, we have description. - Responsibilities: Yes, we have Key Responsibilities with bullet points. - Requirements: Yes, we have Requirements list (skills). Also Education, Experience, & Licensing Requirements could be Qualifications? The headings list includes Qualifications and Skills separate. We need to map. We have: - Requirements (skills) list: Relationship management..., etc. - Education, Experience, & Licensing Requirements: could be Qualifications. - Skills: maybe we could combine skills from Requirements list? But we already have a Requirements heading for skills. The instructions say we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to use. We have content for: - Requirements: maybe the bullet list of skills/abilities (Relationship management..., etc.) fits under Requirements. - Qualifications: Education, Experience, & Licensing Requirements (degree, years experience, etc.) fits under Qualifications. - Skills: maybe we could extract some skills from the Requirements list? But we already used Requirements for skills. Could also have Skills separate but might be redundant. Better to follow typical pattern: Requirements = skills and abilities; Qualifications = education/experience/licensing. We'll not create a separate Skills heading if we already used Requirements for skills; but we could still include Skills if we have distinct skill list not covered. However we have a list of skills under Requirements; we could split: Requirements (maybe core abilities) and Skills (specific competencies). But to avoid thin sections, better to combine. The instruction: "Prefer a few substantive sections over many thin ones." So we should not create both Requirements and Skills if they'd be thin. We'll use Requirements for the skill/ability list, and Qualifications for education/experience/licensing. We'll omit Skills heading. - Benefits: we have Benefits section with list. - Pay: we have compensation and bonus info. Also Salary Description duplicate. So we have Pay content. - Schedule: we have Schedule: Monday–Friday | 8:30 a.m.– 5:00 p.m. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We need to use

for each heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. We need to include all relevant details from the posting. Let's extract content. About the role: The paragraph under "About The Role": "The Hospice Community Liaison is responsible for developing and maintaining strategic relationships that increase awareness of YoloCares and expand access to hospice services. Working closely with clinical and organizational leaders, you will engage with hospitals, physician groups, skilled nursing facilities, assisted-living and senior living communities, and other healthcare and community organizations. You will identify growth opportunities, monitor market trends, evaluate referral activity, and develop partnerships that support the long-term success of the organization." Also there is preceding "Why Community Liaisons Choose YoloCares" and "What You Can Expect". Those are also about the role/benefits. But we already have Benefits and Pay sections. The "Why Community Liaisons Choose YoloCares" is promotional prose about organization; could be part of About the role? Might be considered part of About the role (description of organization). However we already have About YoloCares separate. The instructions say we should not repeat job title as heading; we can include any prose. The "Why Community Liaisons Choose YoloCares" and "What You Can Expect" are not under a heading but are content. We could incorporate them into About the role as additional paragraphs. But we must not lose substantive info. Let's include them as part of About the role. Thus About the role will contain: - Paragraph: "Why Community Liaisons Choose YoloCares When you join YoloCares, you’ll become part of a highly rated California nonprofit hospice organization dedicated to making a meaningful difference for patients, families, and communities. As a Hospice Community Liaison, you’ll build trusted relationships with healthcare professionals, community partners, patients, and families while expanding access to compassionate hospice care and helping YoloCares reach more people who can benefit from our services." - Paragraph: "What You Can Expect Ranked among the Top 1% of hospice providers in California for quality of careNationally ranked among Modern Healthcare's Best Places to Work for five years, with more than 95% of employees saying they’re proud to work at YoloCaresCompetitive annual compensation of $80,000–90,000Company laptop and cell phoneMileage reimbursementCompany vehicle and gas card (if available)Comprehensive benefits package" But note that some of those items (compensation, laptop, mileage, vehicle, benefits) are also covered elsewhere. However we must preserve all substantive info; we can include them but might duplicate. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is okay as long as we don't lose info. However we also have separate Benefits and Pay sections; duplicating might be redundant but acceptable. However we should aim to avoid unnecessary duplication? Not explicitly forbidden. But better to keep each piece in its appropriate section to avoid duplication. The "What You Can Expect" list includes items that are benefits (laptop, mileage, vehicle, benefits package) and compensation. Those are covered in Benefits and Pay sections. To avoid duplication, we could omit those from About the role and just keep the descriptive parts about organization and role. However we must preserve all substantive info; if we omit them, we lose that info unless it's elsewhere. Since we have Benefits and Pay sections, we can keep them there. So we can keep only the descriptive sentences about organization and role in About the role. Thus About the role content: - Paragraph: "Why Community Liaisons Choose YoloCares When you join YoloCares, you’ll become part of a highly rated California nonprofit hospice organization dedicated to making a meaningful difference for patients, families, and communities. As a Hospice Community Liaison, you’ll build trusted relationships with healthcare professionals, community partners, patients, and families while expanding access to compassionate hospice care and helping YoloCares reach more people who can benefit from our services." - Paragraph: "About The Role The Hospice Community Liaison is responsible for developing and maintaining strategic relationships that increase awareness of YoloCares and expand access to hospice services. Working closely with clinical and organizational leaders, you will engage with hospitals, physician groups, skilled nursing facilities, assisted-living and senior living communities, and other healthcare and community organizations. You will identify growth opportunities, monitor market trends, evaluate referral activity, and develop partnerships that support the long-term success of the organization." We could also include "About YoloCares" paragraph? That's about the organization, not the role. But we have no separate heading for About the organization; we could incorporate into About the role or maybe we could create a separate section? Not in list. So we could incorporate that into About the role as well. However the instructions say we should use headings only for those listed; we can still include any prose under those headings. So we can put the About YoloCares description under About the role as well. Thus About the role will have multiple paragraphs: the "Why Community Liaisons Choose YoloCares", the "About YoloCares" description, and the "About The Role" description. Now Responsibilities: we have Key Responsibilities with three subheadings and bullet points under each. We need to output a

  • list. Should we preserve subheadings? The instruction: Use
    • for any list of duties/requirements/benefits. It didn't say to preserve subheadings as headings; we could keep them as part of list items or as inside li. Probably best to keep them as part of the list items, maybe preceded by a dash or bold. We'll output each responsibility as a list item; we can include the subheading as part of the item text. Thus list items: - Referral & Community Development: Develop and maintain strong relationships with healthcare providers, referral sources, payors, skilled nursing facilities, assisted-living communities, senior living organizations, and other community partners. Identify and cultivate new referral sources and business opportunities. Serve as a knowledgeable and professional representative of YoloCares throughout the community. Educate referral partners and community organizations about YoloCares' hospice services and programs. Participate in community events, professional meetings, networking opportunities, and other activities that strengthen YoloCares' visibility and connections. Maintain regular communication with key partners and respond to their needs in a timely and professional manner. - Business Development & Market Growth: Support sustainable growth of the hospice business unit through strategic outreach and market development. Research and identify new markets, services, and opportunities aligned with community needs. Monitor healthcare, hospice, senior care, and competitive trends that may affect organizational growth. Evaluate existing business development strategies and recommend adjustments based on results and market conditions. Identify opportunities to strengthen YoloCares' market position and expand access to services. Develop proposals and respond to requests for proposals (RFPs) from potential partners and customers, as appropriate. - Strategic Partnerships & Analysis: Develop strategic partnerships that support organizational goals and community needs. Analyze referral, marketing, and business development data to measure the effectiveness of outreach initiatives. Track lead generation, referral activity, and market performance. Use data and market information to identify trends, opportunities, and areas for improvement. Provide recommendations to leadership regarding market development, partnerships, services, and outreach strategies. Partner with clinical and operational teams to support a seamless experience for patients and families. Share feedback from referral sources and community partners with appropriate internal teams. Provide guidance and support to hospice team members regarding community relationships and referral development. Build cross-functional partnerships that support organizational priorities. Communicate clearly and professionally with prospective customers, referral partners, healthcare professionals, community organizations, and other stakeholders. Represent YoloCares in a manner consistent with the organization's mission, values, and commitment to compassionate care. We need to ensure we preserve all