Patient Health Advocate- VBC
Somatus · Akron, OH · 1 mo ago
HealthcareFull-time
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 when there is real specific content. Need to extract content from posting.
We must not repeat job title as heading (the page already shows it). No Job ID etc. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Also remove "How We Show Up For Our Patients" etc? That's introductory marketing; maybe we can include as About the role? The posting includes "How We Show Up For Our Patients" paragraph describing company. That could be About the role? Actually "About the role" is typical heading for description of role. But we have sections: "How We'll Support You" (benefits/perks), "How You'll Make An Impact" (responsibilities), "How You'll Strengthen Our Team" (qualifications/skills). So we can map:
- About the role: maybe combine the introductory paragraphs about Somatus mission? Could be considered About the role? But we have "How You'll Make An Impact" which is responsibilities. "How We'll Support You" is benefits/perks. "How You'll Strengthen Our Team" is qualifications/skills.
We need to decide headings: Use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when there is real specific content. Need to extract content from posting.
We must not repeat job title as heading (the page already shows it). No Job ID etc. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Also remove "How We Show Up For Our Patients" etc? That's introductory marketing; maybe we can include as About the role? The posting includes "How We Show Up For Our Patients" paragraph describing company. That could be About the role? Actually "About the role" is typical heading for description of role. But we have sections: "How We'll Support You" (benefits/perks), "How You'll Make An Impact" (responsibilities), "How You'll Strengthen Our Team" (qualifications/skills). So we can map:
- About the role: maybe combine the introductory paragraphs about Somatus mission? Could be considered About the role? But we have "How You'll Make An Impact" which is responsibilities. "How We'll Support You" is benefits/perks. "How You'll Strengthen Our Team" is qualifications/skills.
We need to decide headings: Use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not create Pay/Schedule/Benefits sections unless posting actually states them. Benefits are listed: "We offer 25+ health, growth, and wealth work perks..." includes subsidized personal healthcare coverage, PTO, professional development. That's benefits. So we can have a Benefits section.
Pay: not mentioned. Schedule: not mentioned (though hybrid telehealth environment mentioned but not schedule specifics). So we should not create Pay or Schedule sections.
We need to include About the role? The posting includes introductory description of Somatus and mission. Could be considered About the role or About the company. Since we need to avoid filler, we can include a short About the role paragraph summarizing the company's mission and the role context. That seems substantive.
Responsibilities: from "How You'll Make An Impact" includes many bullet-like sentences. We'll turn into
- .
Qualifications: from "How You'll Strengthen Our Team" includes Qualifications: bullet list. Also includes Preferred Qualifications, Knowledge, Skills, And Abilities, Physical Requirements. Could combine into Requirements and Skills sections? The instruction says use headings like Requirements, Qualifications, Skills, Benefits, etc. We can have Qualifications (required) and Skills (knowledge, skills, abilities). Also maybe Requirements (physical requirements). But we need to avoid many thin sections; prefer few substantive sections. Could combine Qualifications and Skills into one section? But we have headings list; we can choose to include Qualifications and Skills as separate if they have content. Let's see.
Qualifications (required): High school diploma or equivalent required. 1+ years experience in case management or care management, preferably coordinating care across multiple settings. 2+ years healthcare related experience. Experience working with Medicare, Medicaid, and/or Special Needs populations. Experience working in a physician office.
Preferred Qualifications: Medical Assistant, Licensed Practical Nurse, Patient Care Technician, Engagement Specialist, Community Health Worker experience, or exposure to Renal patients. Bilingual in either Spanish, Cantonese, or Mandarin, with ability to converse fluently in a clinical setting using clinical terms.
Knowledge, Skills, And Abilities: list of many items.
Physical Requirements: list.
We could have sections: Qualifications (covering required and preferred), Skills (knowledge, skills, abilities), and maybe Physical Requirements as part of Qualifications or separate? Could be a separate Requirements section? But we have headings: Requirements, Qualifications, Skills. We could put physical requirements under Requirements. But we also have required experience etc under Qualifications. Might be okay.
Let's decide:
- About the role:
Somatus is a leading provider of outcomes-driven care for individuals living with chronic conditions, delivering whole‑person integrated care to help patients enjoy More Healthy Days at Home™. The Patient Health Advocate (PHA) role supports high‑need CKD and ESKD populations, working in a hybrid telehealth environment and partnering with physician practices to improve care coordination and patient outcomes.
- Responsibilities: - ... each duty as
-
- Qualifications: - Required: High school diploma or equivalent; 1+ years case/care management experience; 2+ years healthcare experience; experience with Medicare/Medicaid/Special Needs; physician office experience.
- Preferred: Medical Assistant, LPN, Patient Care Technician, Engagement Specialist, Community Health Worker background or renal patient exposure; bilingual Spanish/Cantonese/Mandarin with clinical fluency.
- Skills: - Knowledge, skills, and abilities: demonstrated success in multidisciplinary teamwork; effective written/verbal communication with cultural awareness; computer proficiency (MS Office, telecom); ability to obtain BLS certification; proven experience engaging patients in behavior change; ability to navigate health systems and make linkages; ability to consult with physicians to implement care plans; participate in CMCC meetings; patient‑centered core values; adaptability; adherence to policies; self‑motivated; strong work ethic.
- Benefits: - Subsidized personal healthcare coverage (Medical, Dental & Vision) plus wellness programs.
- Paid Time Off: accrual of 3 weeks’ Vacation (PTO).
- Professional development: CEU and tuition reimbursement.
We should not include Pay or Schedule.
We need to ensure we preserve all substantive information. Did we miss any responsibilities details? Let's extract from "How You'll Make An Impact" paragraph.
The paragraph is long; we need to break into bullet points covering each duty.
Let's list duties:
- Supports Somatus high needs CKD and ESKD populations that face multiple challenges, from accessing resources to adhering to a physician’s treatment plan.
- The PHA for VBC will work closely with Somatus patients and physician practices, including spending time working from within physician offices and will be the first and primary representative of Somatus, responsible for establishing trust and building relationships with the partnered physician s and practices.
- Somatus offers a Hybrid Telehealth environment with a combination of remote days and visits to members’ homes.
- Works under the guidance of practice physicians and/or a nurse care manager.
- Partners closely with physicians and practice office staff to build a positive, collaborative relationship focused on working together to improve care for patients, support clinical and operational goals, and improves Somatus’ primary representative in the practice.
- Supports the preparation and management of the regular integrated, interdisciplinary care team meetings each month.
- Serve as primary contact for provider practice regarding patient needs and care coordination.
- Follow-up with health management plans and goals in coordination with the RNCM.
- Collaborates with the provider practice to build and fine-tune workflows to support operational goals with the RNCM and care team.
- Educate the provider practice about the Somatus program, reinforcing collaborative workflows.
- Function as an advocate for the patient and support the patients throughout their journeys.
- Conduct patient outreach (i.e., telephonic and in-person) to introduce and align patients to the Somatus program, encourage enrollment, and engage patients.
- Conduct outreach to members currently or recently in the inpatient setting to engage in the Somatus program and/or connect with a Transitions of Care RN to complete an assessment.
- Assist patients during periods of transitions of care to facilitate effective transitions and minimize avoidable readmissions.
- Assist members in scheduling appointments for follow-up post-discharge from the inpatient setting with their provider.
- Schedule members for initial and subsequent Somatus assessments with the RNCM.
- Use the care coordination platform to document all activities in collaboration with physician practices.
- Engages with patients who need assistance with self-care needs, such as:
- Address language and cultural barriers to care management and self-care.
- Coach and guide the patient to meet both personal and clinical goals.
- Schedules provider appointments on behalf of their patients.
- Accompanies patients to their appointments when needed.
- Reminds patients of their upcoming appointments.
- Helps patients access community and government-based services and resources.
- Helps to reinforce education provided to the patient and/or caregiver about symptom response plans.
- Arranges transportation.
- Facilitates closing gaps in care by reinforcing education to patients about preventive monitoring and collaborating with physician practices to schedule / complete diagnostic testing.
- Assists patients with access to educational videos.
- Support NP and RNCM care team members by facilitating in-home telehealth visits with patients.
- Utilize motivational interviewing techniques to encourage patients to make behavioral changes.
We need to preserve all these. We'll create - for each bullet. For sub-bullets under "Engages with patients who need assistance with self-care needs, such as:" we can either keep as a single li with sublist or flatten. Probably better to keep as a li with sub-ul.
We'll need to ensure we don't lose any.
Now Qualifications: we need to include both required and preferred. We'll maybe separate required and preferred as separate li.
Skills: list of knowledge, skills, abilities.
Physical Requirements: we haven't included yet. Should we include? The posting includes Physical Requirements section. We should include that as a section maybe under Requirements or as its own section. Since we have headings: Requirements, Qualifications, Skills. We could put Physical Requirements under Requirements. Let's create a Requirements section for physical requirements.
Thus sections: About the role, Responsibilities, Qualifications, Skills, Requirements (physical), Benefits.
Check if any other sections like "How We'll Support You" is benefits. Good.
Now ensure we don't include any boilerplate like EEO etc. We removed.
Now produce HTML fragment: only the HTML, no markdown fences.
We'll need to wrap sections in maybe or just headings and content. The instruction: output ONLY the HTML fragment — no /, no markdown code fences. So we can just output headings and elements.
We'll do:
About the role
...
Responsibilities
- ...
...
Qualifications
- Required: ...
- Preferred: ...
Skills
- ...
...
Requirements
- Physical requirements: ...
...
Benefits
- ...
...
Make sure to preserve all details.
Now craft the content.
About the role paragraph: combine mission and role description.
Let's write:
Somatus is a leading provider of outcomes‑driven care for individuals and communities living with chronic conditions, delivering whole‑person integrated care to help patients enjoy More Healthy Days at Home™. The Patient Health Advocate (PHA) role supports high‑need Chronic Kidney Disease (CKD) and End‑Stage Kidney Disease (ESKD) populations, working in a hybrid telehealth environment and partnering with physician practices to improve care coordination, patient engagement, and clinical outcomes.
Now Responsibilities bullets: need to capture each duty.
I'll create list items:
- Supports Somatus high‑needs CKD and ESKD populations facing challenges accessing resources and adhering to treatment plans.
- Acts as the first and primary representative of Somatus, working closely with patients and physician practices (including time spent within physician offices) to establish trust and build relationships.
- Operates in a hybrid telehealth environment combining remote days and visits to members’ homes.
- Works under the guidance of practice physicians and/or a nurse care manager.
- Partners with physicians and practice office staff to build a positive
- for any list of duties/requirements/benefits. Use
for prose. We must not create Pay/Schedule/Benefits sections unless posting actually states them. Benefits are listed: "We offer 25+ health, growth, and wealth work perks..." includes subsidized personal healthcare coverage, PTO, professional development. That's benefits. So we can have a Benefits section. Pay: not mentioned. Schedule: not mentioned (though hybrid telehealth environment mentioned but not schedule specifics). So we should not create Pay or Schedule sections. We need to include About the role? The posting includes introductory description of Somatus and mission. Could be considered About the role or About the company. Since we need to avoid filler, we can include a short About the role paragraph summarizing the company's mission and the role context. That seems substantive. Responsibilities: from "How You'll Make An Impact" includes many bullet-like sentences. We'll turn into
- .
Qualifications: from "How You'll Strengthen Our Team" includes Qualifications: bullet list. Also includes Preferred Qualifications, Knowledge, Skills, And Abilities, Physical Requirements. Could combine into Requirements and Skills sections? The instruction says use headings like Requirements, Qualifications, Skills, Benefits, etc. We can have Qualifications (required) and Skills (knowledge, skills, abilities). Also maybe Requirements (physical requirements). But we need to avoid many thin sections; prefer few substantive sections. Could combine Qualifications and Skills into one section? But we have headings list; we can choose to include Qualifications and Skills as separate if they have content. Let's see.
Qualifications (required): High school diploma or equivalent required. 1+ years experience in case management or care management, preferably coordinating care across multiple settings. 2+ years healthcare related experience. Experience working with Medicare, Medicaid, and/or Special Needs populations. Experience working in a physician office.
Preferred Qualifications: Medical Assistant, Licensed Practical Nurse, Patient Care Technician, Engagement Specialist, Community Health Worker experience, or exposure to Renal patients. Bilingual in either Spanish, Cantonese, or Mandarin, with ability to converse fluently in a clinical setting using clinical terms.
Knowledge, Skills, And Abilities: list of many items.
Physical Requirements: list.
We could have sections: Qualifications (covering required and preferred), Skills (knowledge, skills, abilities), and maybe Physical Requirements as part of Qualifications or separate? Could be a separate Requirements section? But we have headings: Requirements, Qualifications, Skills. We could put physical requirements under Requirements. But we also have required experience etc under Qualifications. Might be okay.
Let's decide:
- About the role:
Somatus is a leading provider of outcomes-driven care for individuals living with chronic conditions, delivering whole‑person integrated care to help patients enjoy More Healthy Days at Home™. The Patient Health Advocate (PHA) role supports high‑need CKD and ESKD populations, working in a hybrid telehealth environment and partnering with physician practices to improve care coordination and patient outcomes.
- Responsibilities:- ... each duty as
- Required: High school diploma or equivalent; 1+ years case/care management experience; 2+ years healthcare experience; experience with Medicare/Medicaid/Special Needs; physician office experience.
- Preferred: Medical Assistant, LPN, Patient Care Technician, Engagement Specialist, Community Health Worker background or renal patient exposure; bilingual Spanish/Cantonese/Mandarin with clinical fluency.
- Knowledge, skills, and abilities: demonstrated success in multidisciplinary teamwork; effective written/verbal communication with cultural awareness; computer proficiency (MS Office, telecom); ability to obtain BLS certification; proven experience engaging patients in behavior change; ability to navigate health systems and make linkages; ability to consult with physicians to implement care plans; participate in CMCC meetings; patient‑centered core values; adaptability; adherence to policies; self‑motivated; strong work ethic.
- Subsidized personal healthcare coverage (Medical, Dental & Vision) plus wellness programs.
- Paid Time Off: accrual of 3 weeks’ Vacation (PTO).
- Professional development: CEU and tuition reimbursement.
- for each bullet. For sub-bullets under "Engages with patients who need assistance with self-care needs, such as:" we can either keep as a single li with sublist or flatten. Probably better to keep as a li with sub-ul.
We'll need to ensure we don't lose any.
Now Qualifications: we need to include both required and preferred. We'll maybe separate required and preferred as separate li.
Skills: list of knowledge, skills, abilities.
Physical Requirements: we haven't included yet. Should we include? The posting includes Physical Requirements section. We should include that as a section maybe under Requirements or as its own section. Since we have headings: Requirements, Qualifications, Skills. We could put Physical Requirements under Requirements. Let's create a Requirements section for physical requirements.
Thus sections: About the role, Responsibilities, Qualifications, Skills, Requirements (physical), Benefits.
Check if any other sections like "How We'll Support You" is benefits. Good.
Now ensure we don't include any boilerplate like EEO etc. We removed.
Now produce HTML fragment: only the HTML, no markdown fences.
We'll need to wrap sections in maybe or just headings and content. The instruction: output ONLY the HTML fragment — no /, no markdown code fences. So we can just output headings and elements.
We'll do:
About the role
...
Responsibilities
- ... ...
Qualifications
- Required: ...
- Preferred: ...
Skills
- ... ...
Requirements
- Physical requirements: ... ...
Benefits
- ... ...
- .
Qualifications: from "How You'll Strengthen Our Team" includes Qualifications: bullet list. Also includes Preferred Qualifications, Knowledge, Skills, And Abilities, Physical Requirements. Could combine into Requirements and Skills sections? The instruction says use headings like Requirements, Qualifications, Skills, Benefits, etc. We can have Qualifications (required) and Skills (knowledge, skills, abilities). Also maybe Requirements (physical requirements). But we need to avoid many thin sections; prefer few substantive sections. Could combine Qualifications and Skills into one section? But we have headings list; we can choose to include Qualifications and Skills as separate if they have content. Let's see.
Qualifications (required): High school diploma or equivalent required. 1+ years experience in case management or care management, preferably coordinating care across multiple settings. 2+ years healthcare related experience. Experience working with Medicare, Medicaid, and/or Special Needs populations. Experience working in a physician office.
Preferred Qualifications: Medical Assistant, Licensed Practical Nurse, Patient Care Technician, Engagement Specialist, Community Health Worker experience, or exposure to Renal patients. Bilingual in either Spanish, Cantonese, or Mandarin, with ability to converse fluently in a clinical setting using clinical terms.
Knowledge, Skills, And Abilities: list of many items.
Physical Requirements: list.
We could have sections: Qualifications (covering required and preferred), Skills (knowledge, skills, abilities), and maybe Physical Requirements as part of Qualifications or separate? Could be a separate Requirements section? But we have headings: Requirements, Qualifications, Skills. We could put physical requirements under Requirements. But we also have required experience etc under Qualifications. Might be okay.
Let's decide:
- About the role: