Patient Financial Services Representative, Full Time, Days (8a-4p), Morristown, NJ

The user wants me to reformat a job posting into clean semantic HTML. Let me analyze the content and apply the rules. First, identify sections: - The job description starts with "Job Description" - this is prose about the role. - "Principal Accountabilities" - list of duties. - "Required QUALIFICATIONS" - list of requirements. - "About Us" - company info, prose. - "Summary" - benefits summary, but note it says "Below is a general summary, with role-specific enhancements highlighted:" then lists benefits. This is a benefits section. - There's a note about NJ Pay Transparency Act mentioning hourly wage or salary range, but no actual pay range given. It says "all job postings will include the hourly wage or salary (or a range)" but doesn't provide it. So no pay section. - EEO statement - boilerplate, remove. Rules: - Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. - Use

• for lists,

  for prose. - Do NOT repeat job title as heading (not provided anyway). - Do NOT put Job ID/requisition numbers as headings. - Preserve ALL substantive information. - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. - Include section ONLY when posting has real specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). - Never create Pay/Schedule/Benefits sections unless posting actually states them. - Prefer few substantive sections over many thin ones. - Output ONLY HTML fragment — no /, no markdown code fences. Now, map content to sections: 1. "Job Description" paragraph: This is about the role. Could be "About the role" heading with prose. 2. "Principal Accountabilities": list of duties -> Responsibilities section with

  . 3. "Required QUALIFICATIONS": list of requirements -> Requirements section with
  . 4. "About Us": company description -> could be "About the company" but not in allowed headings. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About Us" is not listed. Could fold into "About the role" or separate? The rules say use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So only those headings. "About Us" is not in the list. Might need to incorporate into "About the role" or omit? But it's substantive company info. The rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, but likely we should stick to those. However, "About Us" is not one of them. Could we use "About the role" for the job description and maybe include company info there? But the company info is separate. The rule says "Prefer a few substantive sections over many thin ones." Might create a section "About the role" for job description, and maybe "About the company" not allowed. Could we use "Qualifications" for requirements? Already have Requirements. The list includes "Required QUALIFICATIONS" - that's qualifications. Could use "Qualifications" heading. But also "Requirements" heading. The example includes both "Requirements" and "Qualifications". Might treat "Required QUALIFICATIONS" as "Qualifications". But the content is a list of degree and experience. That's qualifications. Could also be "Requirements". I'll use "Qualifications" for that list. 5. "Summary" section: benefits list. That's Benefits section. It has a list of benefits. Should include. 6. Pay: The note says "In Compliance with the NJ Pay Transparency Act... all job postings will include the hourly wage or salary (or a range)" but doesn't actually give a range. It says "Final compensation and benefit eligibility may vary by role and employment status and will be confirmed at the time of offer." So no specific pay range. Therefore, do NOT create Pay section. 7. Schedule: Not mentioned. 8. Skills: Not explicitly listed. Thus sections: About the role, Responsibilities, Qualifications, Benefits. Now, structure: - About the role: combine the initial "Job Description" paragraph and maybe the "About Us" paragraph? But "About Us" is about the company, not the role. The rule says "About the role" heading. Could include the job description prose. The "About Us" could be separate but not allowed heading. Might include as a paragraph under "About the role" or omit? The rule says preserve ALL substantive information. So I should include company info. Could create a heading "About the company" but not in allowed list. The allowed list is examples, but 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 says "e.g." meaning for example. However, the rule also says "include a section ONLY when the posting has real, specific content for it". The posting has "About Us" content. But the allowed headings are those. I think we should stick to the given headings. Could we put "About Us" under "About the role"? Might be okay. But the company info is not about the role. However, the job posting includes it. I'll include it as a separate paragraph under "About the role" or maybe create a heading "About the company" but that might violate the rule. The rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot use others, but the examples are those. To be safe, I'll include the company info in the "About the role" section as a separate paragraph, or maybe create a "About the company" heading? The instruction says "Output ONLY the HTML fragment". I'll follow the examples. Let's see typical output: They want semantic HTML with those headings. I'll create:

  About the role

  Job description paragraph...

  About us paragraph...

  But the "About Us" is long with list of facilities and awards. That's a lot. Could be separate section but not allowed. Might be considered boilerplate? It's company marketing. The rule says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". Company description might be considered boilerplate? But it's part of the job posting. The rule says "Preserve ALL substantive information". So keep it. I'll include it under "About the role" or maybe create a separate "About the company" heading? I think it's okay to add a heading not in the list if it's substantive. But 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 the typical ones. I'll include "About the company" as a heading? Might be safer to include under "About the role". However, the "About the role" heading is for the role description. The company info is separate. I'll create a heading "About the company" but that might not be expected. Let's check the rule: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say "only these". It says "e.g." meaning for example. So I can use other headings if needed. But the rule also says "include a section ONLY when the posting has real, specific content for it". The posting has "About Us" content. So I'll create a section "About the company" with that content. But the user might expect only those headings. The instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It might be a closed set. I'll stick to those headings. I'll put the company info under "About the role" as a separate paragraph, but that might be weird. Alternatively, I could omit the company info? But rule says preserve ALL substantive information. The company info is substantive. I'll include it as a separate section with heading "About the company". I think that's acceptable. Let's decide: I'll include "About the company" as an

  . The rule says "use

  for section headings (e.g. ...)". It doesn't forbid others. I'll do it. Now, the benefits section: The "Summary" section lists benefits. That's a Benefits section. Use

  • for each benefit. The list includes many items. I'll parse them. The benefits list: - Medical, Dental, Vision, Prescription Coverage (22.5 hours per week or above for full-time and part-time team members) - Life & AD&D Insurance. - Short-Term and Long-Term Disability (with options to supplement) - 403(b) Retirement Plan: Employer match, additional non-elective contribution - PTO & Paid Sick Leave - Tuition Assistance, Advancement & Academic Advising - Parental, Adoption, Surrogacy Leave - Backup and On-Site Childcare - Well-Being Rewards - Employee Assistance Program (EAP) - Fertility Benefits, Healthy Pregnancy Program - Flexible Spending & Commuter Accounts - Pet, Home & Auto, Identity Theft and Legal Insurance Each as
  • . Now, the "Principal Accountabilities" list: - Answers inbound calls for all billing inquiries for all facilities. - Ensures insurance information is entered properly on accounts, process credit card payments, complete customer service forms for various customer service requests. - Completes weekly backlog. - Performs other related duties as assigned. Each as
  • . "Required QUALIFICATIONS": - Bachelor's Degree in finance, healthcare management or related field. - 3-5 years of experience in Customer Service Call Center or relevant area. Each as
  • . Now, the initial "Job Description" paragraph: "Responsible for supporting management in the billing and collection of accounts receivable for inpatient and outpatient accounts, cash application and reconciliation and/or resolving customer service issues. Additional responsibilities may include notifying the patient and/or guarantor of liabilities, verifying insurance benefits, and assisting customers regarding billing questions." That's prose. Now, the note about NJ Pay Transparency Act: It says "Note: In Compliance with the NJ Pay Transparency Act... all job postings will include the hourly wage or salary (or a range), as well as this summary of benefits. Final compensation and benefit eligibility may vary by role and employment status and will be confirmed at the time of offer." This is not a specific pay range, just a statement. So no Pay section. EEO statement: remove. Now, output HTML fragment. Let's write:

    About the role

    Responsible for supporting management in the billing and collection of accounts receivable for inpatient and outpatient accounts, cash application and reconciliation and/or resolving customer service issues. Additional responsibilities may include notifying the patient and/or guarantor of liabilities, verifying insurance benefits, and assisting customers regarding billing questions.

    About the company

    At Atlantic Health, our promise to our communities is; Anyone who enters one of our facilities will receive the highest quality care delivered at the right time, at the right place, and at the right cost. This commitment is also echoed in the respect,