Authorization Coordinator- Central Authorization Unit - FT Day Shift

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. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Also must not include sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. Let's parse the posting. We have: Who We Are: description of UCI Health. That's about the organization, not necessarily "About the role". Could be considered "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map content to these headings. We have "Your Role on the Team Position Summary" which is about the role: "Incumbent is responsible for obtaining all necessary authorizations in accordance with established guidelines. Verifies eligibility, obtains benefit information, and generates letters for authorizations. Responds to Member Services and Call Center inquiries and resolves any identified authorization issues which arise. Utilizes a team based approach to delivering patient care services." That's responsibilities. Then "Required Qualifications What It Takes to be Successful" list: many items. Then "Preferred Qualifications" list. Then "Total Rewards" section: benefits description. Then "Conditions Of Employment" includes many items (background check etc). This is not in the allowed headings list; but we could possibly treat as part of Requirements? But it's more conditions. The instruction says only use those headings; we should not create other headings. So we need to decide where to place that info. Possibly under "Requirements" or "Qualifications"? But it's conditions of employment, not qualifications. However we must preserve all substantive information. We could include it under a generic

without a heading? The instruction: 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 need to keep the Conditions Of Employment info, but we cannot create a heading not in the list. Perhaps we can incorporate it into a

  under a relevant heading like "Requirements" or "Qualifications". But it's not exactly a requirement; it's conditions. However we could treat it as part of "Requirements" (since they are conditions of employment). The instruction says we can have sections only when posting has real, specific content for it. So we could have a section "Requirements" and include both the required qualifications and conditions of employment as list items? Might be okay. But we also have "Preferred Qualifications". That could go under "Qualifications" or "Skills". The headings list includes Qualifications and Skills separate. We could put required qualifications under "Requirements" and preferred under "Qualifications"? Or we could combine. Better to follow typical pattern: About the role (maybe a brief description of UCI Health?), Responsibilities (position summary), Requirements (required qualifications), Qualifications (preferred qualifications), Skills (maybe skills like MS Office, communication, etc), Benefits (Total Rewards), Pay (if present), Schedule (if present). Since Pay and Schedule not present, we omit those sections. We need to decide what goes where. Let's extract substantive content: - Who We Are: description of UCI Health (size, facilities, service area). This is about the organization, not the role. Could be placed under "About the role"? Actually "About the role" could be a brief description of the role, but we have that in Position Summary. The "Who We Are" is more about the employer. Could be placed under a heading like "About UCI Health" but not in allowed list. However we could incorporate it into a

  without a heading? 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? It says use

  for section headings (e.g. ...). It might imply we should only use those headings. It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the allowed headings. It also says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we should only output those headings if we have content. So we cannot add a custom heading like "About UCI Health". So we need to fit that info somewhere else, maybe as a

  under "About the role"? But "About the role" is supposed to be about the role, not the employer. However we could stretch: "About the role" could include context about the organization as part of the role description. Might be acceptable. Alternatively we could omit the "Who We Are" paragraph entirely? But instruction says preserve ALL substantive information. So we must keep it. So we need to embed it somewhere. We could put it as a

  before any headings, as introductory paragraph. The instruction didn't forbid having a

  without heading. It said use

  for section headings (e.g ...). Use

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

    for prose. So we can have a leading

    that is not under a heading. That seems okay. Thus we can start with a

    containing the "Who We Are" description. Then we can have headings for Responsibilities, Requirements, Qualifications, Skills, Benefits. Now we need to parse the content. Responsibilities: from Position Summary: "Incumbent is responsible for obtaining all necessary authorizations in accordance with established guidelines. Verifies eligibility, obtains benefit information, and generates letters for authorizations. Responds to Member Services and Call Center inquiries and resolves any identified authorization issues which arise. Utilizes a team based approach to delivering patient care services." We can turn that into a

    or maybe a

    • list? It's prose; we can keep as

      . Requirements: Required Qualifications list: - Previous experience with computer registration and registration scheduling system - Must possess the skill, knowledge and ability essential to the successful performance of assigned duties - Must demonstrate general understanding of medical terminology - Must demonstrate customer service skills appropriate to the job - Must be able to travel to off site physician practices - Minimum one (1) year recent experience (within past two (2) years) registering patients in a hospital or clinic, working as a Medical Assistant, or working in medical billing - General knowledge of ICD9 and CPT codes - Excellent written and verbal communication skills in English - Demonstrated experience using MS Office - Ability to work weekends, holidays, and evenings - Ability to maintain a work pace appropriate to the workload - Ability to interpret and understand various medical insurance plans and make accurate determinations regarding coverage - Ability to establish and maintain effective working relationships across the Health System We should keep each as list items. Preferred Qualifications: - Knowledge of University and medical center organizations, policies, procedures and forms - Familiarity of Joint Commission standards - Experience with Epic - Demonstrated experience with authorization process and surgical scheduling - Bilingual skill in Spanish or Vietnamese or Chinese These could go under Qualifications heading. Skills: maybe we could extract specific skills like MS Office, communication, medical terminology, customer service, etc. But many of those are already in required qualifications. Could create a Skills section for things like "MS Office", "communication", "medical terminology", "customer service", "bilingual". But we risk duplication. The instruction says preserve ALL substantive information; we can keep them in Required Qualifications and Preferred Qualifications; we might not need a separate Skills section unless there is distinct skill content not covered elsewhere. However the headings list includes Skills; we could still include it if we have content. But we might avoid duplication. However we could move some items to Skills to avoid long list under Requirements. But we must preserve all info; moving is fine as long as we keep it. Better to follow typical pattern: Requirements = mandatory qualifications; Qualifications = preferred qualifications; Skills = specific abilities like MS Office, communication, medical terminology, customer service, bilingual, etc. But many of those are already in required qualifications. Could still list them there; duplication is not prohibited but might be considered redundant. The instruction didn't forbid duplication, but said preserve ALL substantive information; duplication would still preserve it, but could be considered unnecessary. I'd avoid duplication. Thus we can assign: - Responsibilities: as above. - Requirements: the list of required qualifications (including experience, knowledge, abilities). - Qualifications: the preferred qualifications list. - Skills: maybe we can list specific technical skills: MS Office, Epic (though Epic is in preferred), maybe we can put MS Office under Skills, and bilingual under Skills, etc. But we already have MS Office in required qualifications; we could move it to Skills to avoid duplication. However the required qualifications list includes "Demonstrated experience using MS Office". That's a skill. So we could move it to Skills. Similarly "Ability to interpret and understand various medical insurance plans" is more of an ability; could be under Requirements. "Ability to maintain a work pace appropriate to the workload" also ability. "Ability to work weekends, holidays, and evenings" also ability. "Ability to establish and maintain effective working relationships" also ability. "Must demonstrate customer service skills appropriate to the job" could be skill. "Must demonstrate general understanding of medical terminology" skill. "Must possess the skill, knowledge and ability essential to the successful performance of assigned duties" vague. We could keep required qualifications as is, and not have a Skills section. But the heading list includes Skills; we could omit it if no specific skill content beyond what's already captured. The instruction says include a section ONLY when the posting has real, specific content for it. If we don't have distinct skill content not already covered, we could omit Skills. However we might have some skill content like "MS Office", "Epic", "bilingual". Those are in required and preferred. But we could still create a Skills section listing them, but that would duplicate. I'd rather omit Skills to avoid duplication and keep sections minimal. Benefits: Total Rewards: "We offer a wealth of benefits to make working at UCI even more rewarding. These benefits may include medical insurance, sick and vacation time, retirement savings plans, and access to a number of discounts and perks. Please utilize the links listed here to learn more about our compensation practices and benefits." We need to preserve that. It's prose; we can put as

      under Benefits heading. Pay and Schedule: not present, omit. Now we also have Conditions Of Employment. This is substantive. Where to put? Could be under Requirements as additional items? Or we could create a separate section but not allowed heading. Could we put it under Qualifications? Not ideal. Could we put it under Responsibilities? No. Maybe we can treat Conditions Of Employment as part of "Requirements" because they are conditions that must be met for employment. So we can add them as list items under Requirements heading. Thus Requirements will include both the required qualifications list and the conditions of employment list. Let's extract Conditions Of Employment items: - Background Check and Live Scan - Employment Misconduct* - Legal Right to Work in the United States - Vaccination Policies - Smoking and Tobacco Policy - Drug Free Environment