Authorization Specialist

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate like EEO, etc. Must preserve all substantive info. Let's parse the posting. Content: - Intro paragraph: "A Day in the Life at Option Care Health Extraordinary Careers. Endless Possibilities. With the nation’s largest home infusion provider, there is no limit to the growth of your career. Option Care Health, Inc. is the largest independent home and alternate site infusion services provider in the United States. With over 8,000 team members including 5,000 clinicians, we work compassionately to elevate standards of care for patients with acute and chronic conditions in all 50 states. Through our clinical leadership, expertise and national scale, Option Care Health is re-imagining the infusion care experience for patients, customers and team members. Join a company that is taking action to develop an inclusive, respectful, engaging and rewarding culture for all team members. At Option Care Health your voice is heard, your work is valued, and you’re empowered to grow. Cultivating a team with a variety of talents, backgrounds and perspectives makes us stronger, innovative, and more impactful. Our organization requires extraordinary people to provide extraordinary care, so we are investing in a culture that attracts, hires and retains the best and brightest talent in healthcare." That's about the company/culture. Could be "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map content accordingly. Job Description Summary: "Submits accurate and timely authorization requests to ensure proper reimbursement for patient services. This role involves setting up patient accounts, obtaining necessary clinical documentation, and verifying medical necessity. The specialist must have a solid understanding of basic medical coding, diagnosis codes, and medical terminology. Strong attention to detail, organizational skills, and the ability to work collaboratively with healthcare providers and payers are essential for success in this role." That's a summary; could be part of About the role. Job Responsibilities list: bullet list. Supervisory Responsibilities: "Does this position have supervisory responsibilities? (i.e. hiring, recommending/approving promotions and pay increases, scheduling, performance reviews, discipline, etc.) No X". This is not substantive content; it's just a No. Probably we can drop it as it's not specific content. The instruction: "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." This is minor metadata; we can drop. Basic Education And/or Experience Requirements: "High school diploma or equivalent is required." Basic Qualifications: list of abilities. Travel Requirements: N/A (should not create a section if N/A). So we drop. Preferred Qualifications & Interests (PQIs): "Healthcare/medical billing experience preferred." Then a note about job description usage. Then Pay: "Due to state pay transparency laws, the full range for the position is below: Salary to be determined by the applicant's education, experience, knowledge, skills, and abilities, as well as internal equity and alignment with market data. Pay Range is $16.61-$26.96" That's pay info. Benefits list: "Medical, Dental, & Vision Insurance Paid Time off Bonding Time Off 401K Retirement Savings Plan with Company Match HSA Company Match Flexible Spending Accounts Tuition Reimbursement myFlexPay Family Support Mental Health Services Company Paid Life Insurance Award/Recognition Programs" That's benefits. Schedule: Not mentioned. So we should not create Schedule section. We also have "Posted: Sep 21, 2026" maybe minor metadata; we can drop or include as short p. Probably drop. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all the bullet points exactly as given. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need headings

  for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. - About the role: we have intro paragraph and job description summary. Could combine. - Responsibilities: the list of job responsibilities. - Requirements: maybe basic education and experience requirements (high school diploma). Also maybe basic qualifications? Those could be under Requirements or Qualifications. The instruction gives separate headings for Requirements and Qualifications. We need to decide what goes where. Typically Requirements = education/experience; Qualifications = skills/abilities. But we can allocate. We have Basic Education And/or Experience Requirements: high school diploma. Basic Qualifications: ability to multi-task, work in fast past environment (typo "fast past"? keep as is), high degree of self-discipline, detail-oriented, high degree of quality focus. Preferred Qualifications & Interests: healthcare/medical billing experience preferred. Skills: maybe we could have a Skills section for abilities like attention to detail, organizational skills, ability to work collaboratively, understanding of medical coding, etc. But those are already in summary. Could put them under Skills. But we must not create thin sections; prefer a few substantive sections over many thin ones. So we might combine some. We need to include all substantive info. Let's think of sections: - About the role: intro + summary. - Responsibilities: list. - Requirements: high school diploma. - Qualifications: basic qualifications + preferred qualifications. - Skills: maybe we can incorporate into Qualifications; but we have separate heading for Skills. Could we put skills under Qualifications? The instruction says use those headings; but we can omit sections if no real specific content. So we could omit Skills if we put skill info elsewhere. However we have skill-related info in summary and basic qualifications; we could put them under Qualifications. That would satisfy. - Benefits: list. - Pay: range. - Schedule: none -> omit. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Check if any other sections like "Skills" needed? We have skill info in summary and qualifications; we can keep them there. Now we need to format. We must not include boilerplate like EEO, etc. Also remove duplicated lines (EEO appears twice). Remove application instructions like "Apply Now Search Again". Remove "Posted: Sep 21, 2026". Remove "Option Care subscribes to a policy of equal employment opportunity..." etc. Now produce HTML fragment. Structure:

  About the role

  ... intro paragraph ...

  ... job description summary ...

  But we need to preserve all substantive info; we could combine into one p or multiple. It's okay. Then

  Responsibilities

  • ... each responsibility ...
  Responsibilities list items: - Submit accurate and timely authorization requests to insurance companies and payers - Ensure proper setup and maintenance of patient accounts in the system - Obtain and review clinical documentation to verify medical necessity - Communicate with healthcare providers to gather required information for authorizations - Verify insurance benefits and eligibility for services - Monitor the status of authorization requests and follow up as needed - Ensure compliance with payer requirements and regulations - Utilize basic medical coding, diagnosis codes, and medical terminology in the authorization process - Maintain detailed records and documentation for all authorizations - Collaborate with billing and claims teams to resolve any authorization-related issues Make sure to keep exact phrasing. Then

  Requirements

  High school diploma or equivalent is required.

  Then

  Qualifications

  We need to list basic qualifications and preferred qualifications. Basic qualifications list: - Ability to multi-task and support numerous referrals/priorities at one time. - Ability to work in a fast past environment. - High degree of self-discipline in maintaining productivity expectations. - Must be detail-oriented and have a high degree of quality focus. Preferred qualifications: - Healthcare/medical billing experience preferred. We can put them in a
  maybe separate lists? Could combine into one list with both basic and preferred? But we need to preserve distinction? Not required but we can keep as separate
  with headings? But we cannot add extra headings besides the allowed ones. Could we put a

  preceding each list? That's okay. We could do:

  Basic Qualifications:

  ...

  Preferred Qualifications:

  ...
  But using is okay; not prohibited. It's still within the section. Alternatively we could just list all items in one ul and note which are preferred. But better to keep as given. We'll include

  for prose. Then

  Benefits

  • ... each benefit ...
  Benefits list items as given: - Medical, Dental, & Vision Insurance - Paid Time off - Bonding Time Off - 401K Retirement Savings Plan with Company Match - HSA Company Match - Flexible Spending Accounts - Tuition Reimbursement - myFlexPay - Family Support - Mental Health Services - Company Paid Life Insurance - Award/Recognition Programs Make sure to keep exact phrasing. Then

  Pay

  Due to state pay transparency laws, the full range for the position is below: Salary to be determined by the applicant's education, experience, knowledge, skills, and abilities, as well as internal equity and alignment with market data. Pay Range is $16.61-$26.96

  We need to preserve that exactly. Now ensure no extra sections. Check for any other substantive info: "Job Description Summary" we included in About the role. "Job Description" heading we used for Responsibilities. "Supervisory Responsibilities" we dropped. "Basic Education And/or Experience Requirements" we used. "Basic Qualifications" we used. "Travel Requirements: (if required) N/A" we dropped. "Preferred Qualifications & Interests (PQIs)" we used. The note about job description usage: "This job description is to be used as a guide for accomplishing Company and department objectives, and only covers the primary functions and responsibilities of the position. It is in no way to be construed as an all-encompassing list of duties May perform other duties as assigned". This is substantive? It's a disclaimer about the job description. Should we preserve? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. This is substantive info about the job description. It might be considered boilerplate? It's typical disclaimer but still part of posting. However it's not about the role itself; it's a note. The instruction didn't explicitly say to drop such disclaimer. It said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those categories; it's a job description disclaimer. Might be considered legal boilerplate? Possibly but it's about the job description. I'd lean to keep it as substantive. Where to put? Could be under About the role as a p. Similarly "Due to state pay transparency laws..." we already have in Pay. Also "Posted: Sep 21, 2026" is metadata; we can drop. Also "Apply Now Search Again" is application instruction; drop. Also the repeated EEO lines; drop. Now we need to ensure we didn't miss any substantive info like "With over 8,000 team members including 5,000 clinicians"