Community Health Worker
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to decide which sections to include. The posting includes:
- Intro paragraph about CVS Health mission etc. Could be "About the role" or maybe "About the company". The instruction says we can use "About the role" as a heading for section headings. So we can put the introductory paragraphs under
About the role
with content.
- Then "Role Description" which includes purpose and description. Could be part of About the role as well. But we can combine.
- Then "Core Responsibilities" which is a list of duties. Should be under
Responsibilities
with - items.
- Then "Required" section: "What we’re looking for" bullet list? Actually it's a paragraph list of items separated by line breaks? It says:
Required
What we’re looking for
Minimum of 1 year of experience in healthcare, community-based, case management, or social service environment
Strong oral and written communication skills
Ability to manage multiple priorities while maintaining a positive attitude
Dedication to serving the community and building meaningful relationships
Proficient computer skills (i.e. Windows, GSuite, Microsoft, etc.)
Access to reliable transportation and ability to travel throughout the community to various locations
US work authorization
We can treat as Requirements (or Qualifications). The instruction includes headings: Requirements, Qualifications, Skills. We need to decide which to use. The content includes experience, skills, etc. Could be "Requirements". We'll put under
Requirements
with - .
- Then "Strongly Preferred" and "Preferred" sections. Those could be under "Preferred Qualifications" maybe. But we have headings: Qualifications, Skills. Could combine strongly preferred and preferred under "Preferred Qualifications". However instruction: include a section ONLY when posting has real, specific content for it. We have content for strongly preferred and preferred. Could create a section "Preferred Qualifications" but not in the list of allowed headings? The allowed headings list includes Qualifications, Skills. We could use "Qualifications" for both required and preferred? But we already used Requirements for required. Maybe we can use "Qualifications" for preferred. Or we could add a separate "Preferred Qualifications" heading but not in the list; but instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exhaustive? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings only. So we should map content to those headings.
Thus we have:
- About the role: intro paragraphs.
- Responsibilities: core responsibilities list.
- Requirements: the "What we’re looking for" list (required).
- Qualifications: maybe the "Strongly Preferred" and "Preferred" combined.
- Skills: maybe we could separate skills like "Proficient computer skills" etc but those are already in requirements. Could also put language fluency under Skills. But we might not need Skills section if we already covered.
- Benefits: The posting mentions benefits: "Great Benefits For Great People" paragraph describing medical, dental, vision, PTO, retirement, wellness programs. So we should include Benefits section.
- Pay: The posting includes "Pay Range The Typical Pay Range For This Role Is $18.50 - $31.72". So we should include Pay section.
- Schedule: The posting includes "Anticipated Weekly Hours 40 Time Type Full time". So we can include Schedule section.
We must not include filler like "commensurate with experience". Not present.
We must remove boilerplate: EEO, etc. At end there is "Qualified applicants with arrest or conviction records will be considered..." that's EEO/legal; we should remove. Also "We anticipate the application window for this opening will close on: 03/17/2027" is application instruction; remove. Also "Our people fuel our future..." paragraph before benefits maybe not boilerplate but could be considered about culture; we could keep as part of About the role or maybe separate but we can incorporate.
We need to preserve all substantive information. So we need to include the benefits description, pay range, schedule.
We must not repeat job title as heading. So no Community Health Worker
.
We must not put Job ID/requisition numbers as headings; none present.
We need to output only HTML fragment, no /, no markdown fences.
Let's craft:
About the role
We’re building a world of health around every individual — shaping a more connected, convenient and compassionate health experience. At CVS Health®, you’ll be surrounded by passionate colleagues who care deeply, innovate with purpose, hold ourselves accountable and prioritize safety and quality in everything we do. Join us and be part of something bigger – helping to simplify health care one person, one family and one community at a time.
The purpose of a Community Health Worker (CHW) at Oak Street Health is to act as the bridge between our patients, community, and medical systems in order to remove barriers and increase wellness across all life domains. A CHW is a patient’s advocate or liaison, accompanying patients through proactive in-person and phone outreach based on their care needs to promote health literacy and increase access to resources needed to live healthier lives. High levels of flexibility, problem solving, strong communication, and an intimate knowledge of the community served are required to be successful. CHWs work closely with Medical Social Workers to manage patient care plans, support care team decision making, and coordinate clinical and complementary services needed to provide high quality health care and improve the quality and cultural competence of service delivery. CHWs are expected to work within their scope of practice. There is no expected clinical license for this position.
Then Responsibilities:
Responsibilities
- Establish and maintain strong interpersonal relationships with patients, community organizations, team members, and partners to coordinate patient needs
- Manage patient referrals defined by the care team & collaborate with the Medical Social Worker on action plan
- Facilitate communication between all identified parties involved in patients’ care as needed (e.g., family members, caregivers, medical providers, community-based organizations)
- Form relationships with and build an inventory of local community organizations that may benefit our patients
- Connect patients to state and local community resources related to housing, transportation, food, and activities of daily living among other social and physical barriers to health.
- Assist patients with completion of applications for accessing eligible benefits and resources
- Promote goal setting and achievement to improve patients’ quality of life and self efficacy with patients. Goal definitions are agreed upon by the care team
- Meet with patients in patient-centered and patient-preferred locations (e.g., Oak Street Health center, patient’s home, external medical provider facility, community setting)
- Community Health Workers should plan to spend about half of their time outside of the center in patient-centered locations; this means having access to a reliable means of transportation to do so is required
- Drive engagement with high risk individuals (e.g., completed specialty appointments, adherence to Post Discharge Visits) may include accompaniment to appointments
- Complete referrals to organizations and agencies as needed
- Deliver culturally appropriate health education in the areas where OSH has provided competency training to the CHWs
- Support care team decision making through participation in interdisciplinary team meetings
- Document interactions with patients in electronic medical record in a timely manner while maintaining HIPAA standards and confidentiality of protected health information
- Manage time, set priorities, work independently, and collaborate effectively with an interdisciplinary medical team
- Other duties as assigned
Then Requirements:
Requirements
- Minimum of 1 year of experience in healthcare, community-based, case management, or social service environment
- Strong oral and written communication skills
- Ability to manage multiple priorities while maintaining a positive attitude
- Dedication to serving the community and building meaningful relationships
- Proficient computer skills (i.e. Windows, GSuite, Microsoft, etc.)
- Access to reliable transportation and ability to travel throughout the community to various locations
- US work authorization
Then Qualifications (preferred):
Qualifications
- Fluency in language that is commonly spoken in the community when necessary. Most often this will include Bilingual English/Spanish
- Experience working on multidisciplinary teams with organizations, agencies, patients, and community members
- Knowledge of community resources and resource navigation
- Community Health Worker certification or Associates or Bachelors in a related field is a plus
- Experience utilizing electronic medical record systems
- A problem-solving orientation and a flexible and positive attitude
We could also include Skills but we already covered skills in requirements and qualifications. Might not need separate Skills section.
Then Benefits:
Benefits
Our people fuel our future. Our teams reflect the customers, patients, members and communities we serve and we are committed to fostering a workplace where every colleague feels valued and that they belong.
Great Benefits For Great People We take pride in offering a comprehensive and competitive mix of pay and benefits that reflects our commitment to our colleagues and their families. This full‑time position is eligible for a comprehensive benefits package designed to support the physical, emotional, and financial well‑being of colleagues and their families. The benefits for this position include medical, dental, and vision coverage, paid time off, retirement savings options, wellness programs, and other resources, based on eligibility. Additional details about available benefits are provided during the application process and on Benefits Moments.
But note we already used "Our people fuel our future..." earlier in About the role? Actually we placed that paragraph in About the role? We placed earlier after CVS Health mission? Actually we placed that paragraph after the CVS Health mission? Let's review: In the About the role we included two paragraphs: first the CVS Health mission paragraph, second the purpose description. The "Our people fuel our future..." paragraph appears later in the posting after the benefits heading? Actually the posting: after "Anticipated Weekly Hours..." then "Pay Range..." then "Our people fuel our future..." then "Great Benefits For Great People..." then benefits description, then application window, then EEO. So we should not duplicate that "Our people fuel our future
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include. The posting includes: - Intro paragraph about CVS Health mission etc. Could be "About the role" or maybe "About the company". The instruction says we can use "About the role" as a heading for section headings. So we can put the introductory paragraphs under
About the role
withcontent. - Then "Role Description" which includes purpose and description. Could be part of About the role as well. But we can combine. - Then "Core Responsibilities" which is a list of duties. Should be under
Responsibilities
with- items.
- Then "Required" section: "What we’re looking for" bullet list? Actually it's a paragraph list of items separated by line breaks? It says:
Required
What we’re looking for
Minimum of 1 year of experience in healthcare, community-based, case management, or social service environment
Strong oral and written communication skills
Ability to manage multiple priorities while maintaining a positive attitude
Dedication to serving the community and building meaningful relationships
Proficient computer skills (i.e. Windows, GSuite, Microsoft, etc.)
Access to reliable transportation and ability to travel throughout the community to various locations
US work authorization
We can treat as Requirements (or Qualifications). The instruction includes headings: Requirements, Qualifications, Skills. We need to decide which to use. The content includes experience, skills, etc. Could be "Requirements". We'll put under
Requirements
with- .
- Then "Strongly Preferred" and "Preferred" sections. Those could be under "Preferred Qualifications" maybe. But we have headings: Qualifications, Skills. Could combine strongly preferred and preferred under "Preferred Qualifications". However instruction: include a section ONLY when posting has real, specific content for it. We have content for strongly preferred and preferred. Could create a section "Preferred Qualifications" but not in the list of allowed headings? The allowed headings list includes Qualifications, Skills. We could use "Qualifications" for both required and preferred? But we already used Requirements for required. Maybe we can use "Qualifications" for preferred. Or we could add a separate "Preferred Qualifications" heading but not in the list; but instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exhaustive? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings only. So we should map content to those headings. Thus we have: - About the role: intro paragraphs. - Responsibilities: core responsibilities list. - Requirements: the "What we’re looking for" list (required). - Qualifications: maybe the "Strongly Preferred" and "Preferred" combined. - Skills: maybe we could separate skills like "Proficient computer skills" etc but those are already in requirements. Could also put language fluency under Skills. But we might not need Skills section if we already covered. - Benefits: The posting mentions benefits: "Great Benefits For Great People" paragraph describing medical, dental, vision, PTO, retirement, wellness programs. So we should include Benefits section. - Pay: The posting includes "Pay Range The Typical Pay Range For This Role Is $18.50 - $31.72". So we should include Pay section. - Schedule: The posting includes "Anticipated Weekly Hours 40 Time Type Full time". So we can include Schedule section. We must not include filler like "commensurate with experience". Not present. We must remove boilerplate: EEO, etc. At end there is "Qualified applicants with arrest or conviction records will be considered..." that's EEO/legal; we should remove. Also "We anticipate the application window for this opening will close on: 03/17/2027" is application instruction; remove. Also "Our people fuel our future..." paragraph before benefits maybe not boilerplate but could be considered about culture; we could keep as part of About the role or maybe separate but we can incorporate. We need to preserve all substantive information. So we need to include the benefits description, pay range, schedule. We must not repeat job title as heading. So no
Community Health Worker
. We must not put Job ID/requisition numbers as headings; none present. We need to output only HTML fragment, no /, no markdown fences. Let's craft:About the role
We’re building a world of health around every individual — shaping a more connected, convenient and compassionate health experience. At CVS Health®, you’ll be surrounded by passionate colleagues who care deeply, innovate with purpose, hold ourselves accountable and prioritize safety and quality in everything we do. Join us and be part of something bigger – helping to simplify health care one person, one family and one community at a time.
The purpose of a Community Health Worker (CHW) at Oak Street Health is to act as the bridge between our patients, community, and medical systems in order to remove barriers and increase wellness across all life domains. A CHW is a patient’s advocate or liaison, accompanying patients through proactive in-person and phone outreach based on their care needs to promote health literacy and increase access to resources needed to live healthier lives. High levels of flexibility, problem solving, strong communication, and an intimate knowledge of the community served are required to be successful. CHWs work closely with Medical Social Workers to manage patient care plans, support care team decision making, and coordinate clinical and complementary services needed to provide high quality health care and improve the quality and cultural competence of service delivery. CHWs are expected to work within their scope of practice. There is no expected clinical license for this position.
Then Responsibilities:Responsibilities
- Establish and maintain strong interpersonal relationships with patients, community organizations, team members, and partners to coordinate patient needs
- Manage patient referrals defined by the care team & collaborate with the Medical Social Worker on action plan
- Facilitate communication between all identified parties involved in patients’ care as needed (e.g., family members, caregivers, medical providers, community-based organizations)
- Form relationships with and build an inventory of local community organizations that may benefit our patients
- Connect patients to state and local community resources related to housing, transportation, food, and activities of daily living among other social and physical barriers to health.
- Assist patients with completion of applications for accessing eligible benefits and resources
- Promote goal setting and achievement to improve patients’ quality of life and self efficacy with patients. Goal definitions are agreed upon by the care team
- Meet with patients in patient-centered and patient-preferred locations (e.g., Oak Street Health center, patient’s home, external medical provider facility, community setting)
- Community Health Workers should plan to spend about half of their time outside of the center in patient-centered locations; this means having access to a reliable means of transportation to do so is required
- Drive engagement with high risk individuals (e.g., completed specialty appointments, adherence to Post Discharge Visits) may include accompaniment to appointments
- Complete referrals to organizations and agencies as needed
- Deliver culturally appropriate health education in the areas where OSH has provided competency training to the CHWs
- Support care team decision making through participation in interdisciplinary team meetings
- Document interactions with patients in electronic medical record in a timely manner while maintaining HIPAA standards and confidentiality of protected health information
- Manage time, set priorities, work independently, and collaborate effectively with an interdisciplinary medical team
- Other duties as assigned
Requirements
- Minimum of 1 year of experience in healthcare, community-based, case management, or social service environment
- Strong oral and written communication skills
- Ability to manage multiple priorities while maintaining a positive attitude
- Dedication to serving the community and building meaningful relationships
- Proficient computer skills (i.e. Windows, GSuite, Microsoft, etc.)
- Access to reliable transportation and ability to travel throughout the community to various locations
- US work authorization
Qualifications
- Fluency in language that is commonly spoken in the community when necessary. Most often this will include Bilingual English/Spanish
- Experience working on multidisciplinary teams with organizations, agencies, patients, and community members
- Knowledge of community resources and resource navigation
- Community Health Worker certification or Associates or Bachelors in a related field is a plus
- Experience utilizing electronic medical record systems
- A problem-solving orientation and a flexible and positive attitude
Benefits
Our people fuel our future. Our teams reflect the customers, patients, members and communities we serve and we are committed to fostering a workplace where every colleague feels valued and that they belong.
Great Benefits For Great People We take pride in offering a comprehensive and competitive mix of pay and benefits that reflects our commitment to our colleagues and their families. This full‑time position is eligible for a comprehensive benefits package designed to support the physical, emotional, and financial well‑being of colleagues and their families. The benefits for this position include medical, dental, and vision coverage, paid time off, retirement savings options, wellness programs, and other resources, based on eligibility. Additional details about available benefits are provided during the application process and on Benefits Moments.
But note we already used "Our people fuel our future..." earlier in About the role? Actually we placed that paragraph in About the role? We placed earlier after CVS Health mission? Actually we placed that paragraph after the CVS Health mission? Let's review: In the About the role we included two paragraphs: first the CVS Health mission paragraph, second the purpose description. The "Our people fuel our future..." paragraph appears later in the posting after the benefits heading? Actually the posting: after "Anticipated Weekly Hours..." then "Pay Range..." then "Our people fuel our future..." then "Great Benefits For Great People..." then benefits description, then application window, then EEO. So we should not duplicate that "Our people fuel our future
- .
- Then "Strongly Preferred" and "Preferred" sections. Those could be under "Preferred Qualifications" maybe. But we have headings: Qualifications, Skills. Could combine strongly preferred and preferred under "Preferred Qualifications". However instruction: include a section ONLY when posting has real, specific content for it. We have content for strongly preferred and preferred. Could create a section "Preferred Qualifications" but not in the list of allowed headings? The allowed headings list includes Qualifications, Skills. We could use "Qualifications" for both required and preferred? But we already used Requirements for required. Maybe we can use "Qualifications" for preferred. Or we could add a separate "Preferred Qualifications" heading but not in the list; but instruction says use