Benefit Navigator (Onsite)
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.
We must not repeat job title as heading. Do not put Job ID/requisition numbers as headings; fold minor metadata into short
or drop it.
Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
We need to preserve all substantive information; do not invent or summarize away detail.
We need to include a section ONLY when 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.
We have Pay Range: "The estimated base pay for this position is $18.77 to $28.13. Additional individual compensation may be available for this role through differentials, extra shift incentives, bonuses, etc. Base pay is only a portion of the total rewards package, and a comprehensive benefits program is available for qualifying positions."
Thus we have pay info, we can create Pay section.
Schedule: "Job Shift : Day Shift", "Shift Length : 8 Hours". So we have schedule info.
Benefits: "a comprehensive benefits program is available for qualifying positions." That's vague but it's a statement about benefits. It's not specific details but it's still content. The instruction says never create Benefits sections unless posting actually states them. It does state that a comprehensive benefits program is available. So we can include Benefits section with that statement.
We also have "About Us" description of Adventist Health. That could be "About the role"? Actually "About Us" is separate. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
We have Job Summary: "Serves as the subject matter expert (SME) for insurance questions from associates, ancillary depts, and/or patients. Manages patient responsibility estimates and POS collections. Assists with financial assistance application completion, submission and approval. Partners with Medicaid eligibility vendor. Collects and/or creates cash deposits and provides change to departments. Acts as the point of contact for patient questions regarding insurance explanation of benefits, payments, and itemized statements. Provides cross coverage to patient access departments including other sites."
That's responsibilities. Could be under Responsibilities heading.
We have Job Requirements: Education and Work Experience: High School Education/GED or equivalent: Required; Associate’s/Technical Degree or equivalent combination of education/related experience: Preferred; Five years' patient access experience: Preferred. Also Essential Functions list.
We can split Requirements (education/experience) and Qualifications (maybe essential functions?). But we have headings: Requirements, Qualifications, Skills. We need to decide what to put where.
The posting includes "Education and Work Experience:" with required/preferred. That's qualifications. Also "Essential Functions" list of duties. Those could be responsibilities as well, but we already have responsibilities from job summary. Might combine.
We could treat:
- About the role: maybe a brief description of the role location and environment? Could incorporate the location description and campus info. But the instruction says "About the role" heading is optional; we can include if we have content. We have location and campus description. That seems like "About the role" (where the job is located, environment). We'll include that.
- Responsibilities: combine job summary and essential functions (maybe as bullet list). We'll list duties.
- Requirements: education and work experience (required/preferred). Could be bullet list.
- Qualifications: maybe we could include "Preferred: Associate’s/Technical Degree or equivalent combination of education/related experience; Five years' patient access experience". But that's already in requirements. Might combine.
Better to follow typical structure: About the role (overview), Responsibilities (duties), Requirements (education/experience), Qualifications (maybe skills/knowledge), Skills (specific skills), Benefits, Pay, Schedule.
We have limited specifics for skills; maybe we can extract from essential functions: benefit review, patient financial liability, eligibility for charity care, collecting patient responsibility, processing financial assistance applications, collaborating with care management, educating patient on insurance benefits, payment options, assistance programs, Medicaid/financial assistance application, assist with EOB explanations, collaborate with financial counseling stakeholder, provide cross coverage and training, perform other duties.
These are responsibilities, not skills.
We could put skills as bullet list: knowledge of insurance, medical billing, patient financial services, Medicaid eligibility, financial assistance programs, EOB explanation, etc. But we must not invent details; we can only use what's in posting. The posting does not explicitly list skills separate from duties. So we might omit Skills section if no specific skill list.
Qualifications: we could list education and experience as qualifications. But we already have Requirements for education/experience. Might combine.
Given instruction to prefer a few substantive sections over many thin ones, we can combine education/experience into Requirements, and maybe put essential functions under Responsibilities. Then we have About the role (location/campus), Responsibilities, Requirements, Benefits, Pay, Schedule.
We also have "About Us" description of Adventist Health. That could be considered "About the role"? Actually it's about the organization. Could be separate "About Us" but not in allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add About Us heading. We could incorporate that info into About the role? But it's about the organization, not the role. However we could treat it as part of About the role (company overview). The instruction says use those headings for section headings; we can include About the role with content about the role and organization. It's acceptable.
Thus we will output:
About the role
Located in the metropolitan area of Sacramento, the Adventist Health corporate headquarters have been based in Roseville, California, for more than 40 years. In 2019, we unveiled our WELL-certified campus - a rejuvenating place for associates systemwide to collaborate, innovate and connect. Whether virtual or on campus, Adventist Health Roseville and shared service teams have access to enjoy a welcoming space designed to promote well-being and inspire your best work. Adventist Health is a faith-based, nonprofit, integrated health system serving more than 100 communities on the West Coast and Hawaii with over 440 sites of care, including 27 acute care facilities. Founded on Adventist heritage and values, Adventist Health provides care in hospitals, clinics, home care, and hospice agencies in both rural and urban communities. Our compassionate and talented team of more than 38,000 includes employees, physicians, Medical Staff, and volunteers driven in pursuit of one mission: living God's love by inspiring health, wholeness and hope.
Responsibilities
- Serves as the subject matter expert (SME) for insurance questions from associates, ancillary departments, and/or patients.
- Manages patient responsibility estimates and point‑of‑service (POS) collections.
- Assists with financial assistance application completion, submission and approval.
- Partners with Medicaid eligibility vendor.
- Collects and/or creates cash deposits and provides change to departments.
- Acts as the point of contact for patient questions regarding insurance explanation of benefits, payments, and itemized statements.
- Provides cross coverage to patient access departments including other sites.
- Completes accurate and timely benefit review and determination of patient financial liability including eligibility for charity care.
- Collects expected patient responsibility or makes payment arrangements to collect that amount.
- May be responsible for reviewing and processing of financial assistance applications.
- Works collaboratively with care management department.
- Educates patient on insurance benefits, available payment options, and internal/external assistance programs including providing Medicaid and/or financial assistance application.
- Assists patients with EOB explanations and other insurance/account questions.
- Collaborates with financial counseling stakeholder if patient is eligible for government assistance programs or hospital charity care.
- Provides cross coverage and training, when needed, for other team members.
- Performs other job‑related duties as assigned.
Requirements
- High School Education/GED or equivalent: Required
- Associate’s/Technical Degree or equivalent combination of education/related experience: Preferred
- Five years' patient access experience: Preferred
Benefits
A comprehensive benefits program is available for qualifying positions.
Pay
The estimated base pay for this position is $18.77 to $28.13. Additional individual compensation may be available for this role through differentials, extra shift incentives, bonuses, etc. Base pay is only a portion of the total rewards package.
Schedule
Job Shift: Day Shift. Shift Length: 8 Hours.
We need to ensure we didn't include any boilerplate like E-Verify, etc. We removed those. Also removed Job ID, Posting Date, etc. We kept location and campus info, About Us content. We didn't repeat job title. Good.
Check for any duplicated lines: we have some overlapping responsibilities (like "Provides cross coverage..." appears twice; we have one from job summary and one from essential functions. We included both but they are similar; we could deduplicate but instruction says preserve ALL substantive information; do not invent or summarize away detail. Duplicated lines are to be removed per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. Indeed "Provides cross coverage to patient access departments including other sites." appears in job summary and also later "Provides cross coverage and training, when needed, for other team members." Not exactly same but similar. The first is about cross coverage to patient access departments; second is about cross coverage and training for other team members. They are not exact duplicates but similar. However "Provides cross coverage to patient access departments including other sites." is a line; we also have "Provides cross coverage and training, when needed, for other team members." Not duplicate. The duplicate might be "Provides cross coverage" appears twice but with different context. Not exact duplicate. The instruction says remove duplicated lines (identical). We have no identical lines besides maybe "Provides cross coverage..." appears twice but not identical. So fine.
Check for any other duplicated lines: "Assists with financial assistance application completion, submission and approval." appears in job summary and also "May be responsible for reviewing and processing of financial assistance applications." Not identical.
Thus okay.
Now ensure we didn't include any placeholders like "commensurate with experience". Not present.
We used headings as required. Used - for lists. Used
for prose.
We didn't include any markdown code fences. Output only HTML fragment.
Let's produce final
for prose. We must not repeat job title as heading. Do not put Job ID/requisition numbers as headings; fold minor metadata into short
or drop it. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to preserve all substantive information; do not invent or summarize away detail. We need to include a section ONLY when 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. We have Pay Range: "The estimated base pay for this position is $18.77 to $28.13. Additional individual compensation may be available for this role through differentials, extra shift incentives, bonuses, etc. Base pay is only a portion of the total rewards package, and a comprehensive benefits program is available for qualifying positions." Thus we have pay info, we can create Pay section. Schedule: "Job Shift : Day Shift", "Shift Length : 8 Hours". So we have schedule info. Benefits: "a comprehensive benefits program is available for qualifying positions." That's vague but it's a statement about benefits. It's not specific details but it's still content. The instruction says never create Benefits sections unless posting actually states them. It does state that a comprehensive benefits program is available. So we can include Benefits section with that statement. We also have "About Us" description of Adventist Health. That could be "About the role"? Actually "About Us" is separate. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have Job Summary: "Serves as the subject matter expert (SME) for insurance questions from associates, ancillary depts, and/or patients. Manages patient responsibility estimates and POS collections. Assists with financial assistance application completion, submission and approval. Partners with Medicaid eligibility vendor. Collects and/or creates cash deposits and provides change to departments. Acts as the point of contact for patient questions regarding insurance explanation of benefits, payments, and itemized statements. Provides cross coverage to patient access departments including other sites." That's responsibilities. Could be under Responsibilities heading. We have Job Requirements: Education and Work Experience: High School Education/GED or equivalent: Required; Associate’s/Technical Degree or equivalent combination of education/related experience: Preferred; Five years' patient access experience: Preferred. Also Essential Functions list. We can split Requirements (education/experience) and Qualifications (maybe essential functions?). But we have headings: Requirements, Qualifications, Skills. We need to decide what to put where. The posting includes "Education and Work Experience:" with required/preferred. That's qualifications. Also "Essential Functions" list of duties. Those could be responsibilities as well, but we already have responsibilities from job summary. Might combine. We could treat: - About the role: maybe a brief description of the role location and environment? Could incorporate the location description and campus info. But the instruction says "About the role" heading is optional; we can include if we have content. We have location and campus description. That seems like "About the role" (where the job is located, environment). We'll include that. - Responsibilities: combine job summary and essential functions (maybe as bullet list). We'll list duties. - Requirements: education and work experience (required/preferred). Could be bullet list. - Qualifications: maybe we could include "Preferred: Associate’s/Technical Degree or equivalent combination of education/related experience; Five years' patient access experience". But that's already in requirements. Might combine. Better to follow typical structure: About the role (overview), Responsibilities (duties), Requirements (education/experience), Qualifications (maybe skills/knowledge), Skills (specific skills), Benefits, Pay, Schedule. We have limited specifics for skills; maybe we can extract from essential functions: benefit review, patient financial liability, eligibility for charity care, collecting patient responsibility, processing financial assistance applications, collaborating with care management, educating patient on insurance benefits, payment options, assistance programs, Medicaid/financial assistance application, assist with EOB explanations, collaborate with financial counseling stakeholder, provide cross coverage and training, perform other duties. These are responsibilities, not skills. We could put skills as bullet list: knowledge of insurance, medical billing, patient financial services, Medicaid eligibility, financial assistance programs, EOB explanation, etc. But we must not invent details; we can only use what's in posting. The posting does not explicitly list skills separate from duties. So we might omit Skills section if no specific skill list. Qualifications: we could list education and experience as qualifications. But we already have Requirements for education/experience. Might combine. Given instruction to prefer a few substantive sections over many thin ones, we can combine education/experience into Requirements, and maybe put essential functions under Responsibilities. Then we have About the role (location/campus), Responsibilities, Requirements, Benefits, Pay, Schedule. We also have "About Us" description of Adventist Health. That could be considered "About the role"? Actually it's about the organization. Could be separate "About Us" but not in allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add About Us heading. We could incorporate that info into About the role? But it's about the organization, not the role. However we could treat it as part of About the role (company overview). The instruction says use those headings for section headings; we can include About the role with content about the role and organization. It's acceptable. Thus we will output:
About the role
Located in the metropolitan area of Sacramento, the Adventist Health corporate headquarters have been based in Roseville, California, for more than 40 years. In 2019, we unveiled our WELL-certified campus - a rejuvenating place for associates systemwide to collaborate, innovate and connect. Whether virtual or on campus, Adventist Health Roseville and shared service teams have access to enjoy a welcoming space designed to promote well-being and inspire your best work. Adventist Health is a faith-based, nonprofit, integrated health system serving more than 100 communities on the West Coast and Hawaii with over 440 sites of care, including 27 acute care facilities. Founded on Adventist heritage and values, Adventist Health provides care in hospitals, clinics, home care, and hospice agencies in both rural and urban communities. Our compassionate and talented team of more than 38,000 includes employees, physicians, Medical Staff, and volunteers driven in pursuit of one mission: living God's love by inspiring health, wholeness and hope.
Responsibilities
- Serves as the subject matter expert (SME) for insurance questions from associates, ancillary departments, and/or patients.
- Manages patient responsibility estimates and point‑of‑service (POS) collections.
- Assists with financial assistance application completion, submission and approval.
- Partners with Medicaid eligibility vendor.
- Collects and/or creates cash deposits and provides change to departments.
- Acts as the point of contact for patient questions regarding insurance explanation of benefits, payments, and itemized statements.
- Provides cross coverage to patient access departments including other sites.
- Completes accurate and timely benefit review and determination of patient financial liability including eligibility for charity care.
- Collects expected patient responsibility or makes payment arrangements to collect that amount.
- May be responsible for reviewing and processing of financial assistance applications.
- Works collaboratively with care management department.
- Educates patient on insurance benefits, available payment options, and internal/external assistance programs including providing Medicaid and/or financial assistance application.
- Assists patients with EOB explanations and other insurance/account questions.
- Collaborates with financial counseling stakeholder if patient is eligible for government assistance programs or hospital charity care.
- Provides cross coverage and training, when needed, for other team members.
- Performs other job‑related duties as assigned.
Requirements
- High School Education/GED or equivalent: Required
- Associate’s/Technical Degree or equivalent combination of education/related experience: Preferred
- Five years' patient access experience: Preferred
Benefits
A comprehensive benefits program is available for qualifying positions.
Pay
The estimated base pay for this position is $18.77 to $28.13. Additional individual compensation may be available for this role through differentials, extra shift incentives, bonuses, etc. Base pay is only a portion of the total rewards package.
Schedule
Job Shift: Day Shift. Shift Length: 8 Hours.
We need to ensure we didn't include any boilerplate like E-Verify, etc. We removed those. Also removed Job ID, Posting Date, etc. We kept location and campus info, About Us content. We didn't repeat job title. Good. Check for any duplicated lines: we have some overlapping responsibilities (like "Provides cross coverage..." appears twice; we have one from job summary and one from essential functions. We included both but they are similar; we could deduplicate but instruction says preserve ALL substantive information; do not invent or summarize away detail. Duplicated lines are to be removed per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. Indeed "Provides cross coverage to patient access departments including other sites." appears in job summary and also later "Provides cross coverage and training, when needed, for other team members." Not exactly same but similar. The first is about cross coverage to patient access departments; second is about cross coverage and training for other team members. They are not exact duplicates but similar. However "Provides cross coverage to patient access departments including other sites." is a line; we also have "Provides cross coverage and training, when needed, for other team members." Not duplicate. The duplicate might be "Provides cross coverage" appears twice but with different context. Not exact duplicate. The instruction says remove duplicated lines (identical). We have no identical lines besides maybe "Provides cross coverage..." appears twice but not identical. So fine. Check for any other duplicated lines: "Assists with financial assistance application completion, submission and approval." appears in job summary and also "May be responsible for reviewing and processing of financial assistance applications." Not identical. Thus okay. Now ensure we didn't include any placeholders like "commensurate with experience". Not present. We used headings as required. Used - for lists. Used
for prose.
We didn't include any markdown code fences. Output only HTML fragment.
Let's produce final
for prose. We didn't include any markdown code fences. Output only HTML fragment. Let's produce final