Intake Coordinator
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose. Remove boilerplate etc. Include only sections with real specific content.
We have content:
- About Us: description of company (maybe not needed? It's not a section heading per list; but we could include as maybe "About Us"? Not in allowed headings list. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not include About Us as a heading; maybe we can incorporate into About the role? But the instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we could also use other headings? Probably we should stick to those. The posting includes "About the Role:" and "About the Benefits:" and "Schedule:" and "Minimum Qualifications:" and "Essential Functions:" (which are duties). Also "Physical Demands:" and other statements (EEO etc) to drop.
We need to map:
- About the Role: we have a paragraph about purpose. Use that.
- Responsibilities: list of essential functions (duties). Use - .
- Requirements: maybe Minimum Qualifications (Experience/Education). Could be Requirements.
- Qualifications: maybe same as Requirements? Might be redundant. Could treat Minimum Qualifications as Requirements, and maybe Qualifications as something else like "Proficient at partner programs" etc. But we can combine.
- Skills: maybe "Proficient at partner programs (i.e.: MS Outlook, Word, Excel). Ability to cope with ambiguous, changing environment while under pressure in a calm. Must be able to work as a team member..." Could be skills.
- Benefits: list of benefits.
- Pay: Not specified; we should not create Pay section unless posting actually states them. No pay info given, so omit.
- Schedule: given: Monday – Friday; 8:00 AM – 5:00 PM. So include Schedule section.
We must not include filler like "commensurate with experience". Not present.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting that are relevant.
Let's extract:
About Us: description of Palmetto Infusion. Should we include? It's substantive but not under allowed headings. Could we include as a
before any headings? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't forbid extra paragraphs not under headings. It said use
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 (the page already shows it) and 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.
Thus we can include a brief About Us paragraph as prose (
) before headings. It's substantive. Not a heading. That's okay.
Similarly, Patient Advocacy Statement and Physical Demands and Other (confidentiality, HIPAA, EEO) are boilerplate? Physical Demands maybe substantive but not under allowed headings; could be included as prose under maybe a heading? Not in list. Could we create a heading "Physical Demands"? Not in allowed list but maybe allowed as e.g. The 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 exclusive. However later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't restrict to only those headings. So we could add other headings if needed. But to be safe, we could incorporate Physical Demands into a
under maybe a heading "Physical Demands". But the instruction didn't forbid other headings. However they gave a list of examples; maybe they expect us to use those headings only. Safer to stick to those headings and put other info as prose under appropriate sections or as general paragraphs.
We have Patient Advocacy Statement: could be included as prose under maybe About the role? Not exactly. Could be its own paragraph.
We also have "Other All employees must uphold the confidentiality..." that's boilerplate EEO? Actually it's about confidentiality and HIPAA, not EEO. Might be considered substantive but could be included as a paragraph.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we must include that info somewhere.
Thus we need to decide structure: maybe we can have sections:
- About the Role (h3) with paragraph about purpose.
- Responsibilities (h3) with ul of essential functions.
- Requirements (h3) with ul of minimum qualifications (Experience/Education etc).
- Qualifications (h3) maybe we can put skills like proficiency, teamwork, ability to cope.
- Benefits (h3) with ul of benefits.
- Schedule (h3) with p of schedule.
- Additional Info (maybe not needed) but we could add a generic section "Additional Information" with paragraphs about Patient Advocacy, Physical Demands, Confidentiality/HIPAA, etc. But if we add a heading not in examples, is that okay? The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but to be safe we could avoid extra headings and just put those as
elements after the sections.
Thus final HTML:
About Us: Palmetto Infusion provides comprehensive ambulatory and home-based infusion services to both acute and chronically ill patients. Our centers care for people by providing patients and their families with a convenient, affordable, and safe place to receive infusion treatments. We strive for more than personal service – always delivering a warm and attentive health care experience that boosts patients’ state-of-mind, improves their health, and quality of life. At Palmetto Infusion, we believe in creating an experience that goes beyond just a job. It's about being part of something bigger than yourself - a connected group of caretakers who work together to restore health and hope to our patients. We call it The Palmetto Experience, and we believe it's what sets us apart from other employers. For our employees, The Palmetto Experience means we serve and support people in our purpose to restore health and hope, we build a culture of belonging and collaboration, we deliver on our promise to treat people with respect and empathy, and we strive to embrace change and search for new opportunities.
About the Role
The purpose of this position is to ensure accurate and timely insurance verification, benefit investigation, and authorization processing to support efficient patient care coordination. This role plays a critical part in optimizing revenue cycle operations while providing clear communication to patients and healthcare providers regarding coverage and financial responsibilities.
Responsibilities
- Verify and obtain code-specific insurance information via phone and third-party payer portals.
- Complete new referrals by conducting benefits verification, interpreting insurance policies, and securing authorizations and predeterminations.
- Review and confirm patients’ insurance coverage, including pharmacy benefits (PBM), and obtain prior authorizations when applicable.
- Communicate with patients regarding benefits, coverage details, and financial responsibilities.
- Resolve authorization issues, coverage discrepancies, and insurance claim denials.
- Maintain and update patient appointment calendars, including weekly responsibility tracking.
- Monitor and track incoming tasks and inquiries, ensuring timely follow-up and resolution.
- Collaborate with healthcare providers to clarify coverage requirements and necessary documentation.
- Partner with team members to streamline workflows and achieve departmental goals.
- Prioritize tasks effectively in a high-volume, fast-paced environment while meeting all deadlines.
Requirements
- High School Diploma or Equivalent.
- One year of healthcare experience or customer service experience.
Qualifications
- Proficient at partner programs (i.e.: MS Outlook, Word, Excel).
- Ability to cope with ambiguous, changing environment while under pressure in a calm.
- Must be able to work as a team member and develop productive and cooperative working relationships with all members of the Palmetto Infusion.
Benefits
- Competitive Compensation
- Comprehensive Medical Insurance
- Dental and Vision Insurance
- Company Life Insurance
- Voluntary Life and Disability Insurance
- Additional Voluntary Supplemental Plans
- Flexible Spending Account (Medical and Dependent Care)
- Health Savings Account
- 401K Retirement Plan
- Employee Assistance Program (EAP)
- Employee Discounts
- Ramsey SmartDollar Program
- Referral Program
- Tuition Assistance
- Paid Time Off
- 8 Paid Company Holidays
Schedule
Monday – Friday; 8:00 AM – 5:00 PM.
Now we need to also include Patient Advocacy Statement, Physical Demands, Confidentiality/HIPAA, EEO statements. We must preserve ALL substantive information. So we need to add those as paragraphs after maybe a generic section or as without heading.
We could add a
for Patient Advocacy Statement, then a
for Physical Demands, then a
for Confidentiality/HIPAA, then a
for EEO statement (though EEO is boilerplate but still substantive). However the instruction says remove EEO/equal-opportunity/scam-warning boilerplate. So we should remove EEO lines. It says: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". So we should drop the EEO statements. Good.
Physical Demands: not explicitly listed as boilerplate; it's substantive. So we keep.
Patient Advocacy Statement: also substantive.
Confidentiality/HIPAA: also substantive (about protecting PHI). Not EEO, so keep.
Thus after Schedule we can add:
Patient Advocacy Statement: At Palmetto Infusion, we believe that patient advocacy is at the heart of everything we do, regardless of our roles within the organization. Each member of our team is dedicated to putting the needs and well-being of our patients first. Whether we're working directly with patients or supporting them behind the scenes, our commitment to being a compassionate advocate is paramount. We understand that every interaction, every decision, and every effort contribute to the quality of care our patients receive. Together, we strive to ensure that every individual feels heard, supported, and empowered throughout their healthcare journey. This dedication to patient-centered care is what creates "The Palmetto Experience" — a standard of excellence
for prose. Remove boilerplate etc. Include only sections with real specific content. We have content: - About Us: description of company (maybe not needed? It's not a section heading per list; but we could include as maybe "About Us"? Not in allowed headings list. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not include About Us as a heading; maybe we can incorporate into About the role? But the instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we could also use other headings? Probably we should stick to those. The posting includes "About the Role:" and "About the Benefits:" and "Schedule:" and "Minimum Qualifications:" and "Essential Functions:" (which are duties). Also "Physical Demands:" and other statements (EEO etc) to drop.
We need to map:
- About the Role: we have a paragraph about purpose. Use that.
- Responsibilities: list of essential functions (duties). Use - .
- Requirements: maybe Minimum Qualifications (Experience/Education). Could be Requirements.
- Qualifications: maybe same as Requirements? Might be redundant. Could treat Minimum Qualifications as Requirements, and maybe Qualifications as something else like "Proficient at partner programs" etc. But we can combine.
- Skills: maybe "Proficient at partner programs (i.e.: MS Outlook, Word, Excel). Ability to cope with ambiguous, changing environment while under pressure in a calm. Must be able to work as a team member..." Could be skills.
- Benefits: list of benefits.
- Pay: Not specified; we should not create Pay section unless posting actually states them. No pay info given, so omit.
- Schedule: given: Monday – Friday; 8:00 AM – 5:00 PM. So include Schedule section.
We must not include filler like "commensurate with experience". Not present.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting that are relevant.
Let's extract:
About Us: description of Palmetto Infusion. Should we include? It's substantive but not under allowed headings. Could we include as a
before any headings? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't forbid extra paragraphs not under headings. It said use
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 (the page already shows it) and 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.
Thus we can include a brief About Us paragraph as prose (
) before headings. It's substantive. Not a heading. That's okay.
Similarly, Patient Advocacy Statement and Physical Demands and Other (confidentiality, HIPAA, EEO) are boilerplate? Physical Demands maybe substantive but not under allowed headings; could be included as prose under maybe a heading? Not in list. Could we create a heading "Physical Demands"? Not in allowed list but maybe allowed as e.g. The 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 exclusive. However later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't restrict to only those headings. So we could add other headings if needed. But to be safe, we could incorporate Physical Demands into a
under maybe a heading "Physical Demands". But the instruction didn't forbid other headings. However they gave a list of examples; maybe they expect us to use those headings only. Safer to stick to those headings and put other info as prose under appropriate sections or as general paragraphs.
We have Patient Advocacy Statement: could be included as prose under maybe About the role? Not exactly. Could be its own paragraph.
We also have "Other All employees must uphold the confidentiality..." that's boilerplate EEO? Actually it's about confidentiality and HIPAA, not EEO. Might be considered substantive but could be included as a paragraph.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we must include that info somewhere.
Thus we need to decide structure: maybe we can have sections:
- About the Role (h3) with paragraph about purpose.
- Responsibilities (h3) with ul of essential functions.
- Requirements (h3) with ul of minimum qualifications (Experience/Education etc).
- Qualifications (h3) maybe we can put skills like proficiency, teamwork, ability to cope.
- Benefits (h3) with ul of benefits.
- Schedule (h3) with p of schedule.
- Additional Info (maybe not needed) but we could add a generic section "Additional Information" with paragraphs about Patient Advocacy, Physical Demands, Confidentiality/HIPAA, etc. But if we add a heading not in examples, is that okay? The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but to be safe we could avoid extra headings and just put those as
elements after the sections.
Thus final HTML:
About Us: Palmetto Infusion provides comprehensive ambulatory and home-based infusion services to both acute and chronically ill patients. Our centers care for people by providing patients and their families with a convenient, affordable, and safe place to receive infusion treatments. We strive for more than personal service – always delivering a warm and attentive health care experience that boosts patients’ state-of-mind, improves their health, and quality of life. At Palmetto Infusion, we believe in creating an experience that goes beyond just a job. It's about being part of something bigger than yourself - a connected group of caretakers who work together to restore health and hope to our patients. We call it The Palmetto Experience, and we believe it's what sets us apart from other employers. For our employees, The Palmetto Experience means we serve and support people in our purpose to restore health and hope, we build a culture of belonging and collaboration, we deliver on our promise to treat people with respect and empathy, and we strive to embrace change and search for new opportunities.
About the Role
The purpose of this position is to ensure accurate and timely insurance verification, benefit investigation, and authorization processing to support efficient patient care coordination. This role plays a critical part in optimizing revenue cycle operations while providing clear communication to patients and healthcare providers regarding coverage and financial responsibilities.
Responsibilities
- Verify and obtain code-specific insurance information via phone and third-party payer portals.
- Complete new referrals by conducting benefits verification, interpreting insurance policies, and securing authorizations and predeterminations.
- Review and confirm patients’ insurance coverage, including pharmacy benefits (PBM), and obtain prior authorizations when applicable.
- Communicate with patients regarding benefits, coverage details, and financial responsibilities.
- Resolve authorization issues, coverage discrepancies, and insurance claim denials.
- Maintain and update patient appointment calendars, including weekly responsibility tracking.
- Monitor and track incoming tasks and inquiries, ensuring timely follow-up and resolution.
- Collaborate with healthcare providers to clarify coverage requirements and necessary documentation.
- Partner with team members to streamline workflows and achieve departmental goals.
- Prioritize tasks effectively in a high-volume, fast-paced environment while meeting all deadlines.
Requirements
- High School Diploma or Equivalent.
- One year of healthcare experience or customer service experience.
Qualifications
- Proficient at partner programs (i.e.: MS Outlook, Word, Excel).
- Ability to cope with ambiguous, changing environment while under pressure in a calm.
- Must be able to work as a team member and develop productive and cooperative working relationships with all members of the Palmetto Infusion.
Benefits
- Competitive Compensation
- Comprehensive Medical Insurance
- Dental and Vision Insurance
- Company Life Insurance
- Voluntary Life and Disability Insurance
- Additional Voluntary Supplemental Plans
- Flexible Spending Account (Medical and Dependent Care)
- Health Savings Account
- 401K Retirement Plan
- Employee Assistance Program (EAP)
- Employee Discounts
- Ramsey SmartDollar Program
- Referral Program
- Tuition Assistance
- Paid Time Off
- 8 Paid Company Holidays
Schedule
Monday – Friday; 8:00 AM – 5:00 PM.
Now we need to also include Patient Advocacy Statement, Physical Demands, Confidentiality/HIPAA, EEO statements. We must preserve ALL substantive information. So we need to add those as paragraphs after maybe a generic section or as without heading.
We could add a
for Patient Advocacy Statement, then a
for Physical Demands, then a
for Confidentiality/HIPAA, then a
for EEO statement (though EEO is boilerplate but still substantive). However the instruction says remove EEO/equal-opportunity/scam-warning boilerplate. So we should remove EEO lines. It says: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". So we should drop the EEO statements. Good.
Physical Demands: not explicitly listed as boilerplate; it's substantive. So we keep.
Patient Advocacy Statement: also substantive.
Confidentiality/HIPAA: also substantive (about protecting PHI). Not EEO, so keep.
Thus after Schedule we can add:
Patient Advocacy Statement: At Palmetto Infusion, we believe that patient advocacy is at the heart of everything we do, regardless of our roles within the organization. Each member of our team is dedicated to putting the needs and well-being of our patients first. Whether we're working directly with patients or supporting them behind the scenes, our commitment to being a compassionate advocate is paramount. We understand that every interaction, every decision, and every effort contribute to the quality of care our patients receive. Together, we strive to ensure that every individual feels heard, supported, and empowered throughout their healthcare journey. This dedication to patient-centered care is what creates "The Palmetto Experience" — a standard of excellence
before any headings? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't forbid extra paragraphs not under headings. It said use
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 (the page already shows it) and 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.
Thus we can include a brief About Us paragraph as prose (
) before headings. It's substantive. Not a heading. That's okay.
Similarly, Patient Advocacy Statement and Physical Demands and Other (confidentiality, HIPAA, EEO) are boilerplate? Physical Demands maybe substantive but not under allowed headings; could be included as prose under maybe a heading? Not in list. Could we create a heading "Physical Demands"? Not in allowed list but maybe allowed as e.g. The 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 exclusive. However later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't restrict to only those headings. So we could add other headings if needed. But to be safe, we could incorporate Physical Demands into a
under maybe a heading "Physical Demands". But the instruction didn't forbid other headings. However they gave a list of examples; maybe they expect us to use those headings only. Safer to stick to those headings and put other info as prose under appropriate sections or as general paragraphs.
We have Patient Advocacy Statement: could be included as prose under maybe About the role? Not exactly. Could be its own paragraph.
We also have "Other All employees must uphold the confidentiality..." that's boilerplate EEO? Actually it's about confidentiality and HIPAA, not EEO. Might be considered substantive but could be included as a paragraph.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we must include that info somewhere.
Thus we need to decide structure: maybe we can have sections:
- About the Role (h3) with paragraph about purpose.
- Responsibilities (h3) with ul of essential functions.
- Requirements (h3) with ul of minimum qualifications (Experience/Education etc).
- Qualifications (h3) maybe we can put skills like proficiency, teamwork, ability to cope.
- Benefits (h3) with ul of benefits.
- Schedule (h3) with p of schedule.
- Additional Info (maybe not needed) but we could add a generic section "Additional Information" with paragraphs about Patient Advocacy, Physical Demands, Confidentiality/HIPAA, etc. But if we add a heading not in examples, is that okay? The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but to be safe we could avoid extra headings and just put those as
elements after the sections.
Thus final HTML:
About Us: Palmetto Infusion provides comprehensive ambulatory and home-based infusion services to both acute and chronically ill patients. Our centers care for people by providing patients and their families with a convenient, affordable, and safe place to receive infusion treatments. We strive for more than personal service – always delivering a warm and attentive health care experience that boosts patients’ state-of-mind, improves their health, and quality of life. At Palmetto Infusion, we believe in creating an experience that goes beyond just a job. It's about being part of something bigger than yourself - a connected group of caretakers who work together to restore health and hope to our patients. We call it The Palmetto Experience, and we believe it's what sets us apart from other employers. For our employees, The Palmetto Experience means we serve and support people in our purpose to restore health and hope, we build a culture of belonging and collaboration, we deliver on our promise to treat people with respect and empathy, and we strive to embrace change and search for new opportunities.
About the Role
The purpose of this position is to ensure accurate and timely insurance verification, benefit investigation, and authorization processing to support efficient patient care coordination. This role plays a critical part in optimizing revenue cycle operations while providing clear communication to patients and healthcare providers regarding coverage and financial responsibilities.
Responsibilities
- Verify and obtain code-specific insurance information via phone and third-party payer portals.
- Complete new referrals by conducting benefits verification, interpreting insurance policies, and securing authorizations and predeterminations.
- Review and confirm patients’ insurance coverage, including pharmacy benefits (PBM), and obtain prior authorizations when applicable.
- Communicate with patients regarding benefits, coverage details, and financial responsibilities.
- Resolve authorization issues, coverage discrepancies, and insurance claim denials.
- Maintain and update patient appointment calendars, including weekly responsibility tracking.
- Monitor and track incoming tasks and inquiries, ensuring timely follow-up and resolution.
- Collaborate with healthcare providers to clarify coverage requirements and necessary documentation.
- Partner with team members to streamline workflows and achieve departmental goals.
- Prioritize tasks effectively in a high-volume, fast-paced environment while meeting all deadlines.
Requirements
- High School Diploma or Equivalent.
- One year of healthcare experience or customer service experience.
Qualifications
- Proficient at partner programs (i.e.: MS Outlook, Word, Excel).
- Ability to cope with ambiguous, changing environment while under pressure in a calm.
- Must be able to work as a team member and develop productive and cooperative working relationships with all members of the Palmetto Infusion.
Benefits
- Competitive Compensation
- Comprehensive Medical Insurance
- Dental and Vision Insurance
- Company Life Insurance
- Voluntary Life and Disability Insurance
- Additional Voluntary Supplemental Plans
- Flexible Spending Account (Medical and Dependent Care)
- Health Savings Account
- 401K Retirement Plan
- Employee Assistance Program (EAP)
- Employee Discounts
- Ramsey SmartDollar Program
- Referral Program
- Tuition Assistance
- Paid Time Off
- 8 Paid Company Holidays
Schedule
Monday – Friday; 8:00 AM – 5:00 PM.
Now we need to also include Patient Advocacy Statement, Physical Demands, Confidentiality/HIPAA, EEO statements. We must preserve ALL substantive information. So we need to add those as paragraphs after maybe a generic section or as without heading.
We could add a
for Patient Advocacy Statement, then a
for Physical Demands, then a
for Confidentiality/HIPAA, then a
for EEO statement (though EEO is boilerplate but still substantive). However the instruction says remove EEO/equal-opportunity/scam-warning boilerplate. So we should remove EEO lines. It says: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". So we should drop the EEO statements. Good.
Physical Demands: not explicitly listed as boilerplate; it's substantive. So we keep.
Patient Advocacy Statement: also substantive.
Confidentiality/HIPAA: also substantive (about protecting PHI). Not EEO, so keep.
Thus after Schedule we can add:
Patient Advocacy Statement: At Palmetto Infusion, we believe that patient advocacy is at the heart of everything we do, regardless of our roles within the organization. Each member of our team is dedicated to putting the needs and well-being of our patients first. Whether we're working directly with patients or supporting them behind the scenes, our commitment to being a compassionate advocate is paramount. We understand that every interaction, every decision, and every effort contribute to the quality of care our patients receive. Together, we strive to ensure that every individual feels heard, supported, and empowered throughout their healthcare journey. This dedication to patient-centered care is what creates "The Palmetto Experience" — a standard of excellence
for prose. Do NOT repeat the job title as a heading (the page already shows it) and 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. Thus we can include a brief About Us paragraph as prose (
) before headings. It's substantive. Not a heading. That's okay. Similarly, Patient Advocacy Statement and Physical Demands and Other (confidentiality, HIPAA, EEO) are boilerplate? Physical Demands maybe substantive but not under allowed headings; could be included as prose under maybe a heading? Not in list. Could we create a heading "Physical Demands"? Not in allowed list but maybe allowed as e.g. The 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 exclusive. However later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't restrict to only those headings. So we could add other headings if needed. But to be safe, we could incorporate Physical Demands into a
under maybe a heading "Physical Demands". But the instruction didn't forbid other headings. However they gave a list of examples; maybe they expect us to use those headings only. Safer to stick to those headings and put other info as prose under appropriate sections or as general paragraphs. We have Patient Advocacy Statement: could be included as prose under maybe About the role? Not exactly. Could be its own paragraph. We also have "Other All employees must uphold the confidentiality..." that's boilerplate EEO? Actually it's about confidentiality and HIPAA, not EEO. Might be considered substantive but could be included as a paragraph. We need to preserve ALL substantive information; do not invent or summarize away detail. So we must include that info somewhere. Thus we need to decide structure: maybe we can have sections: - About the Role (h3) with paragraph about purpose. - Responsibilities (h3) with ul of essential functions. - Requirements (h3) with ul of minimum qualifications (Experience/Education etc). - Qualifications (h3) maybe we can put skills like proficiency, teamwork, ability to cope. - Benefits (h3) with ul of benefits. - Schedule (h3) with p of schedule. - Additional Info (maybe not needed) but we could add a generic section "Additional Information" with paragraphs about Patient Advocacy, Physical Demands, Confidentiality/HIPAA, etc. But if we add a heading not in examples, is that okay? The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but to be safe we could avoid extra headings and just put those as
elements after the sections. Thus final HTML:
About Us: Palmetto Infusion provides comprehensive ambulatory and home-based infusion services to both acute and chronically ill patients. Our centers care for people by providing patients and their families with a convenient, affordable, and safe place to receive infusion treatments. We strive for more than personal service – always delivering a warm and attentive health care experience that boosts patients’ state-of-mind, improves their health, and quality of life. At Palmetto Infusion, we believe in creating an experience that goes beyond just a job. It's about being part of something bigger than yourself - a connected group of caretakers who work together to restore health and hope to our patients. We call it The Palmetto Experience, and we believe it's what sets us apart from other employers. For our employees, The Palmetto Experience means we serve and support people in our purpose to restore health and hope, we build a culture of belonging and collaboration, we deliver on our promise to treat people with respect and empathy, and we strive to embrace change and search for new opportunities.
About the Role
The purpose of this position is to ensure accurate and timely insurance verification, benefit investigation, and authorization processing to support efficient patient care coordination. This role plays a critical part in optimizing revenue cycle operations while providing clear communication to patients and healthcare providers regarding coverage and financial responsibilities.
Responsibilities
- Verify and obtain code-specific insurance information via phone and third-party payer portals.
- Complete new referrals by conducting benefits verification, interpreting insurance policies, and securing authorizations and predeterminations.
- Review and confirm patients’ insurance coverage, including pharmacy benefits (PBM), and obtain prior authorizations when applicable.
- Communicate with patients regarding benefits, coverage details, and financial responsibilities.
- Resolve authorization issues, coverage discrepancies, and insurance claim denials.
- Maintain and update patient appointment calendars, including weekly responsibility tracking.
- Monitor and track incoming tasks and inquiries, ensuring timely follow-up and resolution.
- Collaborate with healthcare providers to clarify coverage requirements and necessary documentation.
- Partner with team members to streamline workflows and achieve departmental goals.
- Prioritize tasks effectively in a high-volume, fast-paced environment while meeting all deadlines.
Requirements
- High School Diploma or Equivalent.
- One year of healthcare experience or customer service experience.
Qualifications
- Proficient at partner programs (i.e.: MS Outlook, Word, Excel).
- Ability to cope with ambiguous, changing environment while under pressure in a calm.
- Must be able to work as a team member and develop productive and cooperative working relationships with all members of the Palmetto Infusion.
Benefits
- Competitive Compensation
- Comprehensive Medical Insurance
- Dental and Vision Insurance
- Company Life Insurance
- Voluntary Life and Disability Insurance
- Additional Voluntary Supplemental Plans
- Flexible Spending Account (Medical and Dependent Care)
- Health Savings Account
- 401K Retirement Plan
- Employee Assistance Program (EAP)
- Employee Discounts
- Ramsey SmartDollar Program
- Referral Program
- Tuition Assistance
- Paid Time Off
- 8 Paid Company Holidays
Schedule
Monday – Friday; 8:00 AM – 5:00 PM.
Now we need to also include Patient Advocacy Statement, Physical Demands, Confidentiality/HIPAA, EEO statements. We must preserve ALL substantive information. So we need to add those as paragraphs after maybe a generic section or aswithout heading. We could add a
for Patient Advocacy Statement, then a
for Physical Demands, then a
for Confidentiality/HIPAA, then a
for EEO statement (though EEO is boilerplate but still substantive). However the instruction says remove EEO/equal-opportunity/scam-warning boilerplate. So we should remove EEO lines. It says: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". So we should drop the EEO statements. Good. Physical Demands: not explicitly listed as boilerplate; it's substantive. So we keep. Patient Advocacy Statement: also substantive. Confidentiality/HIPAA: also substantive (about protecting PHI). Not EEO, so keep. Thus after Schedule we can add:
Patient Advocacy Statement: At Palmetto Infusion, we believe that patient advocacy is at the heart of everything we do, regardless of our roles within the organization. Each member of our team is dedicated to putting the needs and well-being of our patients first. Whether we're working directly with patients or supporting them behind the scenes, our commitment to being a compassionate advocate is paramount. We understand that every interaction, every decision, and every effort contribute to the quality of care our patients receive. Together, we strive to ensure that every individual feels heard, supported, and empowered throughout their healthcare journey. This dedication to patient-centered care is what creates "The Palmetto Experience" — a standard of excellence