Insurance Verification Specialist

We need to output HTML fragment only, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. Given text: Locations: Atlanta, GA Schedule: Full-time Hourly, On-site Compensation: Competitive hourly rate + benefits Perks: Pre-cert expertise, patient interaction, collaborative team environment About OrthoAtlanta ... (description) What You'll Do ... (list of duties) A Great Fit If You… (list of traits) What You’ll Need (requirements) Why OrthoAtlanta? (benefits/perks) We need to map to sections. We have: - About the role: maybe the "About OrthoAtlanta" description? Actually "About the role" could be the description of role? The posting includes "What You'll Do" as responsibilities. "About OrthoAtlanta" is about the organization, not role. But we can treat "About the role" as a short paragraph summarizing role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content. We have content for: - Responsibilities: the bullet list under "What You'll Do". That's duties. - Requirements/Qualifications/Skills: The "What You’ll Need" list includes education, experience, knowledge, EMR, multitask, communication, etc. Could split into Requirements (education/experience), Qualifications (knowledge), Skills (communication etc). But we can combine if not enough distinct content. However we should follow instruction: prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section? But headings are predefined; we can choose to include only those with real content. Could include "Requirements" for education/experience, "Skills" for communication etc. But we need to see if we have distinct content. "What You’ll Need" includes: - High School Diploma or equivalent - 5+ years of experience in a healthcare setting, preferably with insurance verification - Strong knowledge of medical insurance plans, authorizations, and medical terminology - Experience with EMR systems (Epic preferred) - Ability to multitask and maintain accuracy in a fast-paced environment - Excellent communication, critical thinking, and organizational skills - Ability to work independently and collaboratively across departments We could treat first two as Requirements (education/experience). Next two as Qualifications (knowledge, EMR). Last three as Skills (communication, critical thinking, organizational, ability to work independently/collaboratively). That seems reasonable. Benefits: The posting mentions "Compensation: Competitive hourly rate + benefits" and "Perks: Pre-cert expertise, patient interaction, collaborative team environment" and "Why OrthoAtlanta?" includes: Be part of a respected and growing healthcare organization, Collaborate with a supportive and experienced team, Make a meaningful impact on patient care and access, Enjoy opportunities for professional growth and development. Also "Perks" earlier. So we have benefits content. Pay: The posting says "Compensation: Competitive hourly rate + benefits". That's not a specific number, just "competitive hourly rate". According to instruction: do NOT include Pay section unless posting actually states them, and avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Competitive hourly rate" is vague but still a statement of compensation type. Is that considered substantive? It says "competitive hourly rate + benefits". That's not a specific number but it's a statement. The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Competitive hourly rate" could be considered placeholder? It's not a specific number, but it's still a description. Might be considered vague but not exactly placeholder like "commensurate with experience". However it's still non-specific. Safer to omit Pay section because it's not a concrete figure. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state compensation: "Competitive hourly rate + benefits". So it does state them, albeit vague. But we might still include Pay with that sentence. However we also have Benefits section separate. Could combine Pay and Benefits? But we have separate headings. Schedule: The posting says "Schedule: Full-time Hourly, On-site". That's specific: Full-time Hourly, On-site. So we can include Schedule section with that. Thus we will include sections: - About the role: maybe we can use the "About OrthoAtlanta" paragraph as about the role? Actually it's about the organization. But we could treat it as "About the role" describing the role context. However there is also a separate "About OrthoAtlanta". Might be better to include "About the role" as a short paragraph summarizing the role: "As an Insurance Verification Specialist at OrthoAtlanta, you'll play a key role in ensuring accurate and timely insurance processing for our patients." That's from the first line of "What You'll Do". But that's already part of responsibilities. Hmm. Better to follow the example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for: - About the role: we could use the introductory sentence: "As an Insurance Verification Specialist at OrthoAtlanta, you'll play a key role in ensuring accurate and timely insurance processing for our patients." That's a prose description of the role. That seems appropriate. - Responsibilities: the bullet list under "What You'll Do". - Requirements: education and experience (High School Diploma or equivalent; 5+ years of experience in a healthcare setting, preferably with insurance verification). - Qualifications: knowledge of medical insurance plans, authorizations, medical terminology; Experience with EMR systems (Epic preferred). - Skills: Ability to multitask and maintain accuracy in a fast-paced environment; Excellent communication, critical thinking, and organizational skills; Ability to work independently and collaboratively across departments. - Benefits: The "Why OrthoAtlanta?" list plus Perks and maybe "competitive hourly rate + benefits"? Actually benefits include: Be part of a respected and growing healthcare organization; Collaborate with a supportive and experienced team; Make a meaningful impact on patient care and access; Enjoy opportunities for professional growth and development; Pre-cert expertise, patient interaction, collaborative team environment (perks). Also compensation includes benefits but we may put that in Pay. - Pay: "Competitive hourly rate + benefits". We'll include that as a short paragraph. - Schedule: "Full-time Hourly, On-site". We must not repeat the job title as a heading. The job title is "Insurance Verification Specialist". We'll not use that as heading. We must not put Job ID/requisition numbers as headings. We must remove boilerplate etc. There's none. We must output only HTML fragment, no /, no markdown. We'll produce something like:

About the role

As an Insurance Verification Specialist at OrthoAtlanta, you'll play a key role in ensuring accurate and timely insurance processing for our patients.

Responsibilities

• Contact insurance companies to verify pre-certification, pre-authorization, and medical necessity requirements for radiology and other outpatient procedures
• Enter insurance and referral details into the EMR with accuracy
• Obtain cost estimates and communicate patient financial responsibility prior to procedures
• Coordinate referrals and schedule appointments for MRIs and follow-up visits
• Work closely with physicians and clinical staff to obtain necessary documentation to support authorizations
• Apply critical thinking to prevent insurance denials and maximize reimbursement
• Educate patients on their coverage, co-pays, deductibles, and referral expectations
• Prioritize and manage incoming referrals and scheduling requests
• Act as a key resource for staff on insurance plans, authorizations, and procedural codes
• Provide coverage at clinic front desks as needed (on-site coverage may be sporadic and unplanned)

Requirements

• High School Diploma or equivalent
• 5+ years of experience in a healthcare setting, preferably with insurance verification

Qualifications

• Strong knowledge of medical insurance plans, authorizations, and medical terminology
• Experience with EMR systems (Epic preferred)

Skills

• Ability to multitask and maintain accuracy in a fast-paced environment
• Excellent communication, critical thinking, and organizational skills
• Ability to work independently and collaboratively across departments

Benefits

• Be part of a respected and growing healthcare organization
• Collaborate with a supportive and experienced team
• Make a meaningful impact on patient care and access
• Enjoy opportunities for professional growth and development
• Pre-cert expertise, patient interaction, collaborative team environment

Pay

Competitive hourly rate + benefits

Schedule

Full-time Hourly, On-site

Check if any section is filler: Benefits list includes "Pre-cert expertise, patient interaction, collaborative team environment" which is a perk but okay. We should ensure we didn't include any boilerplate like EEO etc. Not present. We must not include Locations? The posting had Locations: Atlanta, GA. Should we include that? Not in headings list. Could we include as a short paragraph maybe under About the role? But instruction: only use those headings; we can add other paragraphs but not headings. Could we include location as a paragraph? 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 use those for section headings. It didn't say we cannot add other headings, but better to stick to those. However location is substantive info; we could include it as a paragraph under About the role or maybe a separate

before sections. The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't forbid extra paragraphs. So we could add a

for location. But we need to preserve ALL substantive information. So we should include location somewhere. Could add a

at top:

Location: Atlanta, GA

. That's not a heading, just a paragraph. That seems fine. Similarly, we might want to include the "About OrthoAtlanta" description beyond the role sentence. We used only one sentence for About the role. But there is more description about OrthoAtlanta mission etc. That is also substantive. Should we include it? Possibly under About the role or maybe a separate section like "About the company". But not in headings list. We could incorporate it into About the role paragraph, making it longer. Let's combine: About the role paragraph could include both the role description and company overview. That would preserve all substantive info. Thus About the role paragraph: "Become part of OrthoAtlanta, one of the largest independent physician-owned orthopedic and sports medicine practice in Georgia and contribute to our mission of providing comprehensive orthopedic care. At OrthoAtlanta, you'll be an integral member of a dedicated team of Healthcare Professionals committed to enhancing our patients' quality of life. We offer diverse career paths for talented individuals seeking professional growth and development within a supportive and rewarding work environment where your contributions will make a significant impact. As an