Part-Time Patient Access Specialist

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We need to parse the job posting. Key info: - Serves as a patient advocate and resource through scheduling, pre-registration, registration, admitting/discharge and authorization process. Greets, screens and checks in patients, families vendors and visitors in a professional manner while working to exceed customer service expectations. Pre-registers current and prospective patients which includes: performing verification of demographic and insurance eligibility/benefit information, identifying and communicating out of pocket liability, providing cost estimations as well as attempting to collect in advance or at time of service as well as making referrals to Patient Financial Counselor for self-pay or inability to pay. - SCHEDULE: Lincoln Clinic: 575 S 70th St: Flexible Hours,20hrs/week - MAJOR RESPONSIBILITIES & DUTIES: (list many duties) - KNOWLEDGE, SKILLS, AND ABILITIES: (list) - REQUIRED QUALIFICATIONS: High school diploma or equivalent required. Basic Life Support (BLS) certification within 120 days of transfer or hire required. - PREFERRED QUALIFICATIONS: Minimum of 3 years’ experience working in a clinic and/or hospital setting preferred. Knowledge of Explanation of Benefits (EOB) preferred. - Other Duties: (generic) maybe ignore. - PHYSICAL REQUIREMENTS, EQUIPMENT USAGE, WORK ENVIRONMENT: (some content) but we may not have a heading for that; we can ignore unless we map to something like Requirements? Not needed. - About Boys Town: (description of organization) could be "About the role"? Actually "About Boys Town" is about the organization, not role. Could be placed under "About the role"? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role (maybe summarizing role description). Responsibilities (major responsibilities & duties). Requirements (maybe required qualifications). Qualifications (maybe preferred qualifications). Skills (knowledge, skills, abilities). Benefits (the benefits described). Pay (none given). Schedule (given). We must not create sections with filler like "commensurate with experience". So we include only those with actual content. We have schedule: "Lincoln Clinic: 575 S 70th St: Flexible Hours,20hrs/week". That's specific. Benefits: The paragraph about Boys Town benefits: reduced/no cost visits, pharmacy benefits low to zero-dollar co-pays, no cost mental health visits, generous match on 401K, tuition reimbursement, parenting resources, professional development opportunities. That's specific. Pay: Not mentioned; we should not include Pay section. Now we need to output HTML fragment with

headings and appropriate content:

for prose,

• for lists. We need to decide what goes into each section. About the role: Could be the initial description: "Serves as a patient advocate and resource through the scheduling, pre-registration, registration, admitting/discharge and authorization process. Greets, screens and checks in patients, families vendors and visitors in a professional manner while working to exceed customer service expectations. Pre-registers current and prospective patients which includes: performing verification of demographic and insurance eligibility/benefit information, identifying and communicating out of pocket liability, providing cost estimations as well as attempting to collect in advance or at time of service as well as making referrals to Patient Financial Counselor for self-pay or inability to pay." That seems like role overview. Responsibilities: The MAJOR RESPONSIBILITIES & DUTIES list (multiple bullet-like sentences). We can turn each sentence into
• . Requirements: Could be REQUIRED QUALIFICATIONS: High school diploma or equivalent required. Basic Life Support (BLS) certification within 120 days of transfer or hire required. Qualifications: PREFERRED QUALIFICATIONS: Minimum of 3 years’ experience working in a clinic and/or hospital setting preferred. Knowledge of Explanation of Benefits (EOB) preferred. Skills: KNOWLEDGE, SKILLS, AND ABILITIES: list items. Benefits: The Boys Town benefits paragraph. Schedule: The schedule line. We must not repeat job title as heading; we don't have job title given. We must not include Job ID/requisition numbers. We must remove boilerplate like EEO, E-Verify, accommodation contact, etc. Also remove "Other Duties: This job description incorporates..." and "PHYSICAL REQUIREMENTS, EQUIPMENT USAGE, WORK ENVIRONMENT:" maybe we could ignore or incorporate into something else? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The PHYSICAL REQUIREMENTS etc is not exactly boilerplate but maybe not needed for sections; we could ignore as not fitting headings. It's not required to include everything; we must preserve ALL substantive information; but we can drop sections that don't map to headings? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep all substantive info. If we drop the PHYSICAL REQUIREMENTS etc, we lose substantive info. However we could incorporate that info into a section like "Requirements" or "Work Environment" but we don't have a heading for that. The allowed headings list is limited but we could still add other headings? 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 examples, but we should prefer those headings. It doesn't explicitly forbid other headings, but says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. However we need to preserve all substantive info; we could embed physical requirements etc into a

  under maybe "Requirements" or "Qualifications"? But that might be misrepresenting. Better to create a section like "Work Environment" but not in the list. The instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but the examples are given. Safer to stick to those headings and incorporate all info into them. We can put physical requirements etc under "Requirements" or maybe "Qualifications". But they are not exactly requirements; they are about physical demands. Could be placed under "Requirements" as additional requirement. Or we could create a separate section "Work Environment" but risk deviating. I'd rather incorporate into "Requirements" as additional note. Similarly, "Other Duties" generic can be omitted as it's boilerplate. "About Boys Town" description could go under "About the role" or maybe a separate "About the organization" but not in list. Could incorporate into "About the role" as context. We need to avoid duplication. Let's extract all substantive info: - Role overview (first paragraph) - Schedule: Lincoln Clinic: 575 S 70th St: Flexible Hours,20hrs/week - Major Responsibilities & Duties (list) - Knowledge, Skills, and Abilities (list) - Required Qualifications (list) - Preferred Qualifications (list) - Benefits ( Boys Town benefits ) - Physical Requirements, Equipment Usage, Work Environment (description) - About Boys Town (organization description) - Other Duties (generic) maybe ignore. - EEO etc ignore. We need to embed physical requirements and About Boys Town somewhere. We could add a section "About the organization" but not in examples. However 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." So we could add "About Boys Town" as a heading. But they said "Prefer a few substantive sections over many thin ones." Adding many sections may be thin. But we have a lot of info; we could combine About Boys Town into About the role or Benefits? Probably better to have a separate "About Boys Town" section as it's substantive. But the instruction about headings: they gave examples; we can follow them but not strictly limited. However to be safe, we could incorporate About Boys Town into "About the role" as a brief description of the organization. That would preserve info. Physical requirements: Could be placed under "Requirements" as additional requirement about physical ability. Let's decide sections: - About the role: combine role overview + About Boys Town description (maybe shortened). But we must not lose detail; we can include both paragraphs. - Responsibilities: list of major responsibilities. - Requirements: combine Required Qualifications + Physical Requirements, Equipment Usage, Work Environment. - Qualifications: Preferred Qualifications. - Skills: Knowledge, Skills, and Abilities. - Benefits: Benefits description. - Schedule: Schedule line. We must not create Pay section. Now we need to format lists. Let's extract each piece. Role overview paragraph: "Serves as a patient advocate and resource through the scheduling, pre-registration, registration, admitting/discharge and authorization process. Greets, screens and checks in patients, families vendors and visitors in a professional manner while working to exceed customer service expectations. Pre-registers current and prospective patients which includes: performing verification of demographic and insurance eligibility/benefit information, identifying and communicating out of pocket liability, providing cost estimations as well as attempting to collect in advance or at time of service as well as making referrals to Patient Financial Counselor for self-pay or inability to pay." We can keep as a single

  . About Boys Town description: "At Boys Town, we cultivate a culture of belonging for all employees that respects their individual strengths, views, and experiences. We believe that our differences enable us to be a better team – one that makes better decisions, drives innovation, and delivers better business results. About Boys Town: Boys Town has been changing the way America cares for children and families since 1917. With over a century of service, our employees have helped us grow from a small boardinghouse in downtown Omaha, Nebraska, into one of the largest national child and family care organizations in the country. With the addition of Boys Town National Research Hospital in 1977, our services branched out into the health care and research fields, offering even more career opportunities to those looking to make a real difference. Our employees are our #1 supporters when it comes to achieving Boys Town's mission, which is why we are proud of their commitment to making the world a better place for children, families, patients, and communities. A unique feature for employees and their dependents enrolled in medical benefits are reduced to no cost visits for services performed by a Boys Town provider at a Boys Town location. Additional costs savings for the employee and their dependents are found in our pharmacy benefits with low to zero-dollar co-pays on certain maintenance drugs. Boys Town takes your mental health seriously with no cost mental health visits to an in-network provider. We help our employees prepare for retirement with a generous match on their 401K or 401K Roth account. Additional benefits include tuition reimbursement, parenting resources from our experts and professional development opportunities within the organization, just to name a few. Working at Boys Town is more than just a job, it is a way of life." Note that benefits are repeated later in Benefits section; we might duplicate. Actually the Benefits paragraph includes many of these points. The About Boys Town paragraph also includes benefits. To avoid