Central Scheduling Specialist - Prior Authorization - Full time

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, no invented or summarized away detail. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. We need to parse the posting. Given text: Location: Basalt, CO Position Type: Full time Requisition Number: JR102124 Description We are currently hiring for a full time Central Scheduling Specialist within the Prior Authorization department here at Aspen Valley Health. Work Shift Mids - 8 Hour Compensation Range $24.25 - $38.81 The compensation range listed is an estimate. Final compensation will be determined based on your qualifications including years of experience performing similar work, level of formal education in a relevant field of study, and any professional certifications related to the position. Requirements Preferred Qualifications Previous experience working in a healthcare setting preferred. Experience with EPIC preferred. Bilingual in Spanish preferred. We will consider equivalent combinations of experience and education for certain jobs. If you don't meet the job requirements as listed, but you believe you possess equivalent experience or education, you are encouraged to apply. Position Overview Responsible for scheduling, cancelling, rescheduling and preregistering of outpatient visits and procedures for multiple ambulatory departments, procedures, and surgery by collecting all necessary information for schedule and registration preparation. What To Love Aspen Valley Health has earned numerous accolades and awards, which are a tribute to the tradition of high-tech, high-touch care we provide for our patients. What We Offer Our comprehensive benefits package can be viewed here. Continuing education, professional development, and tuition assistance. Healthcare as low as $46 per month, plus an additional 50% off of all AVH services for you AND your family! All preventative services covered at 100%, zero copay. Virtual and robust mental health resources available. Earn up to 22 days PTO within your first year. Rollover what you don’t use. Bereavement Leave that covers miscarriages, extended family, and pets. Robust Paid Medical and Family Leave. Weeks 1-6 are paid at 100% for parental or personal illness/injury. You will be automatically enrolled into the 457b plan at 6% to kick start your retirement savings. In addition, AVH matches 50% of your 457b contributions up to a max of 3% of earnings each pay period into our 401a plan. In lieu of Social Security, AVH contributes 7.5% of your annual salary each year to the Cash Balance Pension Plan. This means you are no longer paying social security taxes out of your paycheck! (Your take home will be much higher!) Housing assistance - We provide resources to establish roots in the Roaring Fork Valley. Employee referral bonuses. Discounted ski passes! Transportation discounts and carpool incentives. Environment And Culture Aspen Valley Health is a twenty-five-bed community hospital that represents the best of two worlds — the warmth and friendliness of a small town and the technical expertise of a major medical center. "I love the people, the sense of family and community on this team and in a broader sense across the hospital as a whole. I have worked for a HUGE corporation, and this is so much better!! It’s like CHEERS, where everybody knows your name." - Stacy "I love the flexibility that this job gives me, and the people I get to connect with and learn from. The job is challenging and ever-changing, which helps keep my brain sharp! AVH has been a great company to work for over the last 8 years, and it shows in how employees are valued and cared for." - Melissa “The team members are incredibly dedicated to the delivery of care for our patients, to helping our staff feel valued and supported, and to the fiscal health of the hospital. They also genuinely care about each other, are able to laugh at themselves, and tease each other because there is a basis of trust and mutual support. I have laughed so hard at meetings that I have actually cried.” - Diana It's no surprise that our retention rate is BETTER than 90% of all other hospitals in the country! This application will close once a qualified candidate is successfully hired. Compensation details: 24.25-38.81 Hourly Wage PIddd4b8a6ed4f-25448-41524458 We need to extract sections: - About the role: maybe "Position Overview" or "Description". The description includes: "We are currently hiring for a full time Central Scheduling Specialist within the Prior Authorization department here at Aspen Valley Health." Also "Work Shift Mids - 8 Hour". Could be considered About the role. - Responsibilities: "Responsible for scheduling, cancelling, rescheduling and preregistering of outpatient visits and procedures for multiple ambulatory departments, procedures, and surgery by collecting all necessary information for schedule and registration preparation." - Requirements: The "Requirements" heading includes "Preferred Qualifications" bullet list. Also maybe "Requirements" includes "Preferred Qualifications". Also "We will consider equivalent combinations..." etc. - Qualifications: Could be same as Requirements? But we need to avoid duplicate thin sections. We can combine Requirements and Qualifications into one section? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include a section only when posting has real specific content for it. We have content for Requirements (Preferred Qualifications). We have maybe Qualifications (like "Previous experience working in a healthcare setting preferred. Experience with EPIC preferred. Bilingual in Spanish preferred.") That's essentially same as Requirements. Could treat them as Requirements and Qualifications both present but they'd be similar. Might be better to have Requirements section with the list, and Qualifications maybe not needed. But we need to decide. - Skills: Not explicitly listed; maybe "Experience with EPIC" is a skill, "Bilingual in Spanish" is a skill. Could be included under Skills. But we already have them under Requirements. Could create Skills section with those items. However we must not invent or summarize away detail; we can move them to Skills if they are indeed skills. The posting says "Preferred Qualifications" includes those items. So they are qualifications, not necessarily skills. But we could still put them under Qualifications. Let's decide: We'll have Requirements (maybe generic) and Qualifications (the list). But we need to avoid duplication. Perhaps better: Requirements section includes the statement "We will consider equivalent combinations..." and maybe the "If you don't meet..." statement. Qualifications section includes the bullet list of preferred qualifications. That seems reasonable. - Benefits: The "What We Offer" section includes many benefits. We'll list them as

• . - Pay: Compensation range $24.25 - $38.81 hourly. Also note "Compensation details: 24.25-38.81 Hourly Wage". We'll include Pay section with that range and note that it's an estimate and final based on qualifications. - Schedule: Work Shift Mids - 8 Hour. Could be schedule. - About the role: Could include location, position type, department, etc. Also maybe "What To Love" and "Environment And Culture" could be part of About the role or separate? But we only have headings list; we could put "About the role" to include location, position type, department, work shift, and maybe the culture quotes? However "Environment And Culture" could be its own section but not in the list; we could incorporate into About the role or maybe not include as separate heading because not in allowed list. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings; we can also use other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings only. So we should map content to those headings. Thus we need to decide which headings to include based on content. Let's extract content for each: About the role: - Location: Basalt, CO - Position Type: Full time - Department: Prior Authorization - Job title: Central Scheduling Specialist (but we shouldn't repeat job title as heading; but we can mention it in prose) - Work Shift: Mids - 8 Hour - Maybe also "What To Love" and "Environment And Culture" could be part of About the role? But they are more about culture; could be included but not required. We'll keep them maybe under About the role as additional prose. Responsibilities: - The sentence about scheduling, cancelling, rescheduling, preregistering outpatient visits and procedures. Requirements: - Maybe the statement: "We will consider equivalent combinations of experience and education for certain jobs. If you don't meet the job requirements as listed, but you believe you possess equivalent experience or education, you are encouraged to apply." Qualifications: - Preferred Qualifications bullet list: - Previous experience working in a healthcare setting preferred. - Experience with EPIC preferred. - Bilingual in Spanish preferred. Skills: - Could be same as qualifications? But we could treat "Experience with EPIC" and "Bilingual in Spanish" as skills, and "Previous experience working in a healthcare setting" as experience. However we already have them under Qualifications. To avoid duplication, maybe we put them under Skills and keep Qualifications empty? But we need to include only sections with real specific content. If we put them under Skills, we need to have content. We could split: Qualifications: "We will consider equivalent combinations..." (that's more about qualifications). Skills: the bullet list. But the bullet list is under "Preferred Qualifications". Might be better to treat them as Qualifications. Let's see typical job posting: Requirements often list required qualifications; Qualifications list preferred qualifications. But we have only "Preferred Qualifications". So we could put them under Qualifications. Then Requirements could be the generic statements about equivalent experience. Thus: Requirements: - "We will consider equivalent combinations of experience and education for certain jobs. If you don't meet the job requirements as listed, but you believe you possess equivalent experience or education, you are encouraged to apply." Qualifications: - bullet list of three items. Skills: maybe we could leave out if no distinct skill content beyond qualifications. But we could extract "Experience with EPIC" as a skill, "Bilingual in Spanish" as a skill, "Previous experience working in a healthcare setting" as experience not skill. But we could still include Skills section with those two items. However that would duplicate content from Qualifications. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not prohibited but might be considered redundant. Better to avoid duplication. So we will not create Skills section if we already covered those items under Qualifications. But we need to check if there is any other skill content not captured: maybe "Experience with EPIC" is a skill; "Bilingual in Spanish" is a skill; "Previous experience working in a healthcare setting" is experience. So we could put those under Qualifications (as preferred qualifications). That seems fine. Benefits: - All the bullet points under "What We Offer". Also maybe "Our comprehensive benefits package can be viewed here." but that's a link; we can ignore link. Pay: - Compensation range $24.25 - $38.81 hourly. Also note that it's an estimate and final compensation based on qualifications. Schedule: - Work Shift Mids - 8 Hour. Now we need to output HTML fragment with