Patient Financial Services, Associate - Insurance
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. "Position Summary" could be "About the role". Use About the role
then paragraph(s) summarizing.
- Job Duties & Essential Functions -> Responsibilities.
- Required Experience And Qualifications -> Requirements (or Qualifications). Could combine.
- Preferred Qualifications -> maybe Qualifications as well, but we could have a separate "Preferred Qualifications" but instruction only lists certain headings; we could still use "Qualifications" for required and maybe add a note. But we can also have "Qualifications" and include both required and preferred. However they said prefer few substantive sections over many thin ones. So we could have "Requirements" for required, and maybe "Preferred Qualifications" not in list; but we could still include as a subsection within Qualifications? The instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. Probably best to stick to those.
Thus we can have:
About the role
(position summary)
Responsibilities
(job duties)
Requirements
(required experience and qualifications)
Qualifications
(preferred qualifications)
Maybe also Skills: we could extract skills like knowledge of Word and Excel, medical terminology, etc. Could put under Skills.
Pay: we have salary range $26.56 - $28.52 per hour. So we need a Pay section.
Schedule: Full-time.
Benefits: Not explicitly listed; there is mention of benefits in company overview? Not specific benefits like health insurance etc. So we should not create Benefits section unless posting actually states them. It mentions "total compensation goes beyond the number in your paycheck!" but not specific benefits. So we should not create Benefits.
We also have other info like physical demands, special notes, etc. Those could be placed under maybe "Additional Information" but not in allowed headings. Could we incorporate them into Responsibilities or Requirements? Probably better to create a section "Additional Information" but instruction says prefer those headings; but we could still include if needed. However they said "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". Physical demands is specific content. So we need to include it somewhere. Could we put under "Requirements"? It's not a requirement but a physical demand. Could create a section "Physical Demands" but not in list. The instruction didn't forbid other headings, just gave examples. It said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we can use those headings, but not limited to them. However to be safe, we could incorporate physical demands into Responsibilities or Requirements as a bullet. But it's not a duty. Could add as a bullet under Responsibilities? Might be odd.
Alternatively we could create a section "Additional Details" with h3. The instruction didn't forbid; they just gave examples. I'd say it's okay to add other headings if needed, but better to stick to given ones if possible. However we have to preserve ALL substantive information. Physical demands is substantive. So we need to include it somewhere.
We could add a Physical Demands
with bullet list.
Similarly "Special Notes" includes resume/CV, smoke free, travel, shift changes, respiratory protection, essential position. Those are also substantive. Could be under "Additional Information". But we could also incorporate some into Responsibilities (like travel to other locations) or Requirements (like ability to adapt to system changes, manage heavy call volume). But the special notes about resume/CV, smoke free, essential position, etc are not requirements but notes. Could create a section "Important Notes". But again not in list.
Given the instruction's emphasis on not creating sections with filler, but we have real content for physical demands and special notes. So we should include them.
Thus final sections:
- About the role (position summary)
- Responsibilities (job duties)
- Requirements (required experience and qualifications)
- Qualifications (preferred qualifications)
- Skills (maybe knowledge of Word and Excel, medical terminology, etc.) Could be part of Requirements but we can separate.
- Pay (salary range)
- Schedule (full-time)
- Physical Demands
- Special Notes (or Additional Information)
We must not include boilerplate like EEO, etc. The company overview includes some EEO statements; we should remove those. Also remove "Job Field Clerical/Secretarial", "Primary Location US-NY-Southampton", "Posting Start Date", "Posting End Date". Those are metadata; we could fold minor metadata into a short
Physical Demands
with bullet list. Similarly "Special Notes" includes resume/CV, smoke free, travel, shift changes, respiratory protection, essential position. Those are also substantive. Could be under "Additional Information". But we could also incorporate some into Responsibilities (like travel to other locations) or Requirements (like ability to adapt to system changes, manage heavy call volume). But the special notes about resume/CV, smoke free, essential position, etc are not requirements but notes. Could create a section "Important Notes". But again not in list. Given the instruction's emphasis on not creating sections with filler, but we have real content for physical demands and special notes. So we should include them. Thus final sections: - About the role (position summary) - Responsibilities (job duties) - Requirements (required experience and qualifications) - Qualifications (preferred qualifications) - Skills (maybe knowledge of Word and Excel, medical terminology, etc.) Could be part of Requirements but we can separate. - Pay (salary range) - Schedule (full-time) - Physical Demands - Special Notes (or Additional Information) We must not include boilerplate like EEO, etc. The company overview includes some EEO statements; we should remove those. Also remove "Job Field Clerical/Secretarial", "Primary Location US-NY-Southampton", "Posting Start Date", "Posting End Date". Those are metadata; we could fold minor metadata into a shortor drop it. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we could include location and maybe schedule etc as separate sections. But schedule we already have as section. Location maybe as a short p under About the role? Could include. We need to preserve ALL substantive information. So location is substantive; we should keep it. Could add a paragraph after About the role: "Location: US-NY-Southampton". Or incorporate into About the role. Similarly posting dates maybe not needed; could drop as minor metadata. The instruction says fold minor metadata into a short
or drop it. So we could include a short p with posting dates if we want, but maybe drop. Company overview: we should keep substantive info about hospital, location, community size, recognition, StaffCo arrangement, etc. That's substantive. So we need to include that. Could be under "About the company" but not in list. Could add a section "Company Overview". But we could incorporate into About the role? Might be too long. Better to have a separate section "Company Overview". The instruction didn't forbid; it's just examples. So we can add. Thus final sections: - About the role (position summary) - Responsibilities - Requirements - Qualifications (preferred) - Skills - Pay - Schedule - Physical Demands - Special Notes - Company Overview We need to ensure we use
- for any list of duties/requirements/benefits. So for responsibilities, requirements, qualifications, skills, physical demands, special notes we should use lists.
We need to use
for prose. We must not repeat job title as heading. We must not include boilerplate like EEO, legal, etc. Let's extract content. Position Summary: "Under the direction of the PFS Team Lead and/or PFS Assistant Director, the Patient Financial Services (PFS) Associate is responsible for the accurate and timely review, billing, follow‑up, and resolution of assigned third‑party and/or patient accounts. This includes high‑dollar and complex service claims, ensuring that responsible payers are billed correctly and that payment is secured in accordance with payer requirements and organizational standards." That's the summary. Responsibilities (Job Duties & Essential Functions): List items: - The PFS Associate actively manages account activity throughout the revenue cycle by performing account analysis, follow‑up, and resolution, and by documenting all claim statuses, actions taken, and outcomes clearly and accurately within the patient accounting systems. - The role requires independent judgment to identify billing errors, underpayments, and claim delays, and to take appropriate corrective action to promote clean claim resolution and timely reimbursement. - The PFS Associate ensures a high level of customer satisfaction by providing timely, accurate, and professional responses to patient inquiries, requests for information, and claim appeals. This includes explaining account balances, insurance determinations, and billing outcomes in a clear and compassionate manner, while adhering to privacy, compliance, and customer service standards. - In addition, the PFS Associate is responsible for identifying and analyzing complex claim issues, denial patterns, payment variances, and payer trends, and for communicating findings to leadership. - The Associate escalates unresolved or high‑risk issues as appropriate and contributes recommendations to improve billing accuracy, workflow efficiency, and overall revenue cycle performance. - This role requires a working knowledge of payer regulations, billing processes, and revenue cycle workflows, and plays a critical role in safeguarding hospital reimbursement and financial integrity. We could also include "ensuring that responsible payers are billed correctly..." but that's in summary. We'll put each as
- . Requirements (Required Experience And Qualifications): - High School diploma or equivalent. - Must have 3+ years prior healthcare billing experience and knowledge of medical terminology. - Knowledge of Word and Excel applications. - Must be able to adapt to system changes, manage heavy call volume, be a self-starter, organized, detail oriented. We could also include "Must be able to adapt to system changes, manage heavy call volume, be a self-starter, organized, detail oriented." as separate bullet. Qualifications (Preferred Qualifications): - College degree and or certifications in billing and coding. - Bilingual. Skills: Could be knowledge of Word and Excel, medical terminology, etc. But we already have those in requirements. Could still separate but might duplicate. Perhaps we combine skills into Requirements and not have separate Skills section. However we need to avoid duplication. The instruction says preserve ALL substantive information; duplication is okay if it's same info but we could avoid redundancy. I'd rather keep Skills separate for things like "knowledge of Word and Excel applications" and "medical terminology". But those are already in requirements. Could still list them under Skills but that duplicates. Might be okay but better to avoid duplication. Perhaps we can put "knowledge of Word and Excel applications" and "medical terminology" under Skills, and keep requirements focused on experience and education. Let's split: Requirements: education, years experience, ability to adapt, self-starter, organized, detail oriented, manage heavy call volume. Skills: knowledge of medical terminology, Word and Excel. But the original says "Knowledge of Word and Excel applications." and "Must have 3+ years prior healthcare billing experience and knowledge of medical terminology." So medical terminology is part of experience requirement. Could still be under Skills. We'll decide: Requirements: - High School diploma or equivalent. - Must have 3+ years prior healthcare billing experience. - Must be able to adapt to system changes. - Manage heavy call volume. - Be a self‑starter, organized, detail oriented. Skills: - Knowledge of medical terminology. - Proficiency with Word and Excel applications. Qualifications (Preferred): - College degree and/or certifications in billing and coding. - Bilingual. Pay: Salary $26.56 - $28.52 per hour. Schedule: Full-time. Physical Demands: - Lift stored document boxes up to 10 lbs. - As part of employment at Southampton Hospital, there may be occasions when travel to other locations is needed to support operational needs. - This position may require the wearing of respiratory protection, which may prohibit the wearing of facial hair. - This function/position maybe designated as “essential.” This means that when the Hospital is faced with an institutional emergency, employees in such positions may be required to remain at their work location or to report to work to protect, recover, and continue operations at Stony Brook Medicine, Stony Brook University Hospital and related facilities. - All Hospital positions may be subject to changes in pass days and shifts as necessary. Special Notes: - Resume/CV should be included with the online application. - Stony Brook Medicine is a smoke