Patient Access 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. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "EOE including Disabled and Veterans." etc. Also remove "Background Check", "Artificial Intelligence Disclosure", "Sign-on Bonus Eligibility". Also remove "Please visit our Benefits section to learn more." etc. We need to extract substantive content: The posting includes an introductory paragraph about Northwestern Medicine, patient-first approach, etc. That could be "About the role" or maybe a general description. The job description includes many responsibilities, technology, efficiency etc. We need to categorize into sections. We have sections: About the role (intro). Responsibilities (list). Requirements (maybe qualifications). Qualifications (maybe required and preferred). Skills (maybe list of skills). Benefits (they mention benefits but not specific details; they say "We offer a wide range of benefits...". That's vague, not specific. The rule: never create Benefits section unless posting actually states them. It does state benefits generally but not specific like tuition reimbursement etc earlier: earlier they said "We pride ourselves on providing competitive benefits: from tuition reimbursement and loan forgiveness to 401(k) matching and lifecycle benefits". That is specific enough? It mentions tuition reimbursement, loan forgiveness, 401(k) matching, lifecycle benefits. That's specific. So we can include Benefits section with those items. Pay: not mentioned. Schedule: not mentioned (they mention schedule may change to reflect shifting business needs under Efficiency section, but not specific schedule like full-time, shift). So we should not create Schedule or Pay sections. We need to avoid filler like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can reorganize into sections. Must not omit any substantive info. That's a lot. We need to ensure we capture everything from the posting that is not boilerplate. Let's parse the posting: Intro paragraph: "At Northwestern Medicine, every patient interaction makes a difference in cultivating a positive workplace. This patient-first approach is what sets us apart as a leader in the healthcare industry. As an integral part of our team, you'll have the opportunity to join our quest for better health care, no matter where you work within the Northwestern Medicine system. We pride ourselves on providing competitive benefits: from tuition reimbursement and loan forgiveness to 401(k) matching and lifecycle benefits, our goal is to take care of our employees. Ready to join our quest for better?" Then "Job Description" heading (but we ignore as we already have heading). Then: "The Patient Access Specialist reflects the mission, vision, and values of NMHC, adheres to the organizations Code of Ethics and Corporate Compliance Program, and complies with all relevant policies, procedures, guidelines and all other regulatory and accreditation standards." That's a description of role; could go under About the role. Then "Responsibilities:" followed by a long list of responsibilities (many sentences). We need to turn each responsibility into

• items. Then after responsibilities, there is "Communication and Collaboration:" with more items. Then "Technology:" with items. Then "Efficiency, Process Improvement, and Business Growth:" with items. These could be considered subcategories but we can just treat all as responsibilities list. However we need to preserve all substantive info; we can keep them as separate subheadings? 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 we should follow that pattern. Probably best to have a single Responsibilities section with all duties listed as

  . That would preserve all info. Then after that, there is "Qualifications Required:" list, then "Preferred:" list. Then "Additional Information" includes EEO statement (boilerplate) and Background Check, AI Disclosure, Sign-on Bonus Eligibility (these are boilerplate/legal). We need to remove those. Also "Benefits" section after that: "We offer a wide range of benefits that provide employees with tools and resources to improve their physical, emotional, and financial well-being while providing protection for unexpected life events. Please visit our Benefits section to learn more." That's vague but we already have specific benefits earlier. We should include the specific benefits from earlier: tuition reimbursement, loan forgiveness, 401(k) matching, lifecycle benefits. Also maybe the generic statement about benefits could be included as prose. We must not include the "Please visit our Benefits section to learn more." as it's basically a reference; could be considered boilerplate? Might be okay to keep as prose but it's not substantive detail. Safer to omit. We also need to include "Sign-on Bonus Eligibility" maybe? It's specific but it's about eligibility conditions; could be considered part of Benefits? It's about sign-on bonus. The posting includes that. Should we include? It's substantive info about sign-on bonus eligibility. The rule: include a section ONLY when posting has real, specific content for it. Benefits section we have. Sign-on bonus could be part of Benefits. We could include it as a bullet under Benefits. However the rule says never create Benefits section unless posting actually states them. It does state benefits (tuition reimbursement etc). So we can include Benefits with those items plus sign-on bonus eligibility details. But we need to check if sign-on bonus eligibility is considered boilerplate? It's specific to the position. I'd include it. Now we need to decide sections: - About the role: include introductory paragraph and the description about reflecting mission etc. Possibly also the sentence "As an integral part of our team..." etc. We'll combine. - Responsibilities: all duties listed under Responsibilities, Communication and Collaboration, Technology, Efficiency, Process Improvement, and Business Growth. We'll combine into one list. - Requirements: maybe we treat "Qualifications Required:" as Requirements. Or we could have Requirements and Qualifications separate. The instruction lists both Requirements and Qualifications as possible headings. We need to decide. The posting has "Qualifications Required:" and "Preferred:" . Could map Required to Requirements, Preferred to Qualifications? Or we could have Requirements (required) and Qualifications (preferred). Let's do that. Thus:

  Requirements

  with

  of required qualifications.

  Qualifications

  with
  of preferred qualifications. Skills: maybe we could extract skills from required list (interpersonal, communication, computer skills, typing speed, multitask, organizational, time management, analytical, problem solving). But those are already in qualifications. Could create a Skills section but might duplicate. The instruction says prefer a few substantive sections over many thin ones. So maybe we skip Skills section and keep qualifications. But we have both Requirements and Qualifications sections; that's two sections. Could we combine them into one Qualifications section with required and preferred? The instruction gave both as possible headings but we can choose to use only one if we think it's better. However we need to preserve all substantive info; we can still preserve by having subheadings inside? But we cannot use

  etc? Not prohibited but they said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but we should follow that pattern. Using both Requirements and Qualifications is okay. We'll include: - About the role (

  ) - Responsibilities (

  ) - Requirements (

  ) - Qualifications (

  ) - Benefits (

  ) No Pay or Schedule. Now we need to extract the exact text for each bullet, preserving all detail, not summarizing. Let's extract the introductory paragraph: "At Northwestern Medicine, every patient interaction makes a difference in cultivating a positive workplace. This patient-first approach is what sets us apart as a leader in the healthcare industry. As an integral part of our team, you'll have the opportunity to join our quest for better health care, no matter where you work within the Northwestern Medicine system. We pride ourselves on providing competitive benefits: from tuition reimbursement and loan forgiveness to 401(k) matching and lifecycle benefits, our goal is to take care of our employees. Ready to join our quest for better?" That's prose; we can put in

  . Then the role description sentence: "The Patient Access Specialist reflects the mission, vision, and values of NMHC, adheres to the organizations Code of Ethics and Corporate Compliance Program, and complies with all relevant policies, procedures, guidelines and all other regulatory and accreditation standards." We could include that in About the role as well. Now Responsibilities: we need to list each responsibility as

  . Let's extract them from the text after "Responsibilities:" until before "Communication and Collaboration:"? Actually the responsibilities list includes many items, then after that there is a heading "Communication and Collaboration:" which is more responsibilities. Then "Technology:" then "Efficiency, Process Improvement, and Business Growth:". We'll treat all as responsibilities. Let's copy the responsibilities list exactly as given, preserving punctuation. From the posting: "Responsibilities: Consistently practices Patients First philosophy and adheres to high standards of customer service. This includes setting an example to peers, coworkers, etc. by fostering a team atmosphere. Responds to questions and concerns. Forwards, directs, and notifies Team Lead or Operations Coordinator of extraordinary issues as necessary. Maintains patient confidentiality per HIPAA regulations. Provides exceptional customer service to patients which establish a positive first impression of Northwestern Medicine. Exceeds all consumer requests and alerts management of issues or concerns that require escalation. Correctly identifies and collects patient demographic information in accordance with organization standards. Interacts with various hospital departments and physicians offices to effectively schedule and direct patients through the NMHC systems in a patient/customer friendly manner. Reaches out to patients to schedule an appointment as defined. Performs medical necessity checks as necessary for scheduled services, communicates options to patient if appointment fails. Informs patients of any issues with securing the financial account for their encounter. Completes out-of-pocket estimations as requested by patients. Provides training and education as needed. Manages work schedule efficiently, completing tasks and assignments on time. Completes other duties assigned by manager. Cross-training between various departments will take place to ensure coverage. Participates in Quality Assurance reviews to ensure integrity of patient data information. Uses effective service recovery skills to solve problems or service breakdowns when they occur. Utilizes department and hospital policies and procedures to complete assigned tasks. Adheres to all department policies and compliance requirements. Avoids putting patient in financial or safety risk. Other duties as assigned." Then after that, there is "Communication and Collaboration:" with items: "Communicates information to the patient regarding questions about physician referrals, insurance referrals and consultations. Collects authorization numbers in appropriate systems as applicable. Provides professional and constructive environment for communication across units/departments and resolves operational issues. May attend intra/interdepartmental meetings which involve walking within NM Campus. Communicates customer satisfaction issues to appropriate individuals. Demonstrates teamwork by helping co-workers within and across departments. Communicates effectively with others, respects diverse opinions and styles, and acknowledges the assistance and contributions of others. Interacts with internal customers to provide excellent support service to staff in departments which provide direct patient care. Accommodates all levels of communication ability." Then "Technology:": "Utilizes multiple online order retrieval systems to verify or print the patients order. Verifies insurance eligibility and benefit levels through the use of online