Manager, Patient Access Services- Mount Sinai Morningside-Full-Time-Days

We need to output HTML fragment with sections: About the role? Actually we have description: Job Description Manager, Patient Access Services- Mount Sinai Morningside-Full-Time-Days. The description includes responsibilities, qualifications, etc. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We have responsibilities content, qualifications (education, experience), skills (knowledge, abilities). Pay is given: salary range $86772 - $130159 Annually. Schedule? Not specified (Full-Time-Days maybe schedule: Full-Time Days). The posting says Full-Time-Days. That indicates schedule: Full-Time, Days. We could include Schedule section with that info. Benefits? Not mentioned explicitly. So we should not include Benefits unless content. There's no benefits detail. So omit Benefits. We need to not repeat job title as heading. The page already shows it. So we don't put heading for job title. We need to include metadata like Job ID? Not present. So ignore. We need to remove boilerplate: EEO, etc. Remove equal opportunity employer text, etc. Also remove employer description? The "Employer Description Strength through Unity and Inclusion" and "About The Mount Sinai Health System" maybe considered boilerplate? It's descriptive but could be considered "About the role"? Actually "About the role" could be the description paragraph at top: "The RCM – Manager of Patient Access Services is responsible for the day-to-day management..." That's substantive. So we can put that under About the role. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details like responsibilities bullet points, qualifications, etc. We need to use

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

  for prose. Thus we need to parse responsibilities into list items. The responsibilities section includes many sentences; we can break into list items each duty. Similarly, Minimum Knowledge, Skills, And Abilities Required could be under Skills or Requirements? The instruction: Use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content. - About the role: introductory paragraph(s) describing role. - Responsibilities: list of duties. - Requirements: maybe "Minimum Knowledge, Skills, And Abilities Required" plus maybe "Experience working in a unionized healthcare environment preferred." Could be considered requirements. - Qualifications: Education Requirements, Experience Requirements, Working Conditions? Actually Working Conditions maybe part of Qualifications? Could be separate but we only have those headings. We'll put Education and Experience under Qualifications. - Skills: maybe the knowledge, skills, abilities? But we already used Requirements for that. Could also put under Skills. However we need to avoid duplication. Let's decide: Use Requirements for minimum knowledge, skills, abilities. Use Qualifications for education and experience. Use Skills maybe for specific skills like EPIC, etc. But we have "Experience with EPIC preferred." Could be under Skills. Also "Strong interpersonal, communication, and leadership skills." That's skill. Better to follow typical: Responsibilities, Qualifications (education+experience), Skills (knowledge, skills, abilities), Pay, Schedule. Requirements maybe not needed if we have Skills and Qualifications. But we must include heading only if content. We can include Requirements as maybe "Minimum Knowledge, Skills, And Abilities Required". That is content. So we will have Requirements heading. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay, Schedule. We need to ensure we don't create sections with filler like "commensurate with experience". We have actual content. Now craft HTML. We'll start with

  About the role

  then

  ...

  . Responsibilities:

  Responsibilities

  then
  • each duty. We need to extract duties from the responsibilities paragraph. Responsibilities text: "Operational Oversight Manage daily Patient Access operations to ensure accurate and timely registration, insurance capture, and compliance with regulatory and payer requirements.Monitor performance metrics related to productivity, accuracy, and quality; implement corrective actions as needed.Identify workflow gaps and lead process improvement initiatives to enhance efficiency and data integrity.Ensure staff receive appropriate onboarding, ongoing education, and regulatory training, including customer service standards (AIDET).Maintain working knowledge of patient access workflows, payer requirements, and front-end revenue cycle metrics.Support standardized, efficient, and compliant Patient Access practices.Build effective working relationships with internal stakeholders across departments.Ensure compliance with HIPAA privacy and security standards.Adhere to established organizational policies, procedures, and standards of behavior.Perform other duties as assigned.Supervise, coach, and develop Patient Access supervisors, leads, and frontline staff.Foster a culture of accountability, professionalism, and service excellence.Manage staff performance in accordance with 1199 collective bargaining agreements, including counseling, corrective action, and disciplinary documentation.Maintain effective working relationships with Human Resources and Labor Relations. Staff Supervision & Development Participate in investigatory meetings, grievance processes, and other labor-related matters as required. Collaboration & Communication Communicate operational performance, risks, and improvement initiatives to leadership as appropriate.Partner with IT and Revenue Cycle teams to ensure Patient Access workflows are optimized within EPIC.Participate in system upgrades, testing, and workflow improvements to support front-end revenue capture and operational performance." We need to split into sensible list items. Could break at each sentence or clause. Let's create list items: - Manage daily Patient Access operations to ensure accurate and timely registration, insurance capture, and compliance with regulatory and payer requirements. - Monitor performance metrics related to productivity, accuracy, and quality; implement corrective actions as needed. - Identify workflow gaps and lead process improvement initiatives to enhance efficiency and data integrity. - Ensure staff receive appropriate onboarding, ongoing education, and regulatory training, including customer service standards (AIDET). - Maintain working knowledge of patient access workflows, payer requirements, and front-end revenue cycle metrics. - Support standardized, efficient, and compliant Patient Access practices. - Build effective working relationships with internal stakeholders across departments. - Ensure compliance with HIPAA privacy and security standards. - Adhere to established organizational policies, procedures, and standards of behavior. - Perform other duties as assigned. - Supervise, coach, and develop Patient Access supervisors, leads, and frontline staff. - Foster a culture of accountability, professionalism, and service excellence. - Manage staff performance in accordance with 1199 collective bargaining agreements, including counseling, corrective action, and disciplinary documentation. - Maintain effective working relationships with Human Resources and Labor Relations. - Participate in investigatory meetings, grievance processes, and other labor-related matters as required. - Communicate operational performance, risks, and improvement initiatives to leadership as appropriate. - Partner with IT and Revenue Cycle teams to ensure Patient Access workflows are optimized within EPIC. - Participate in system upgrades, testing, and workflow improvements to support front-end revenue capture and operational performance. That seems comprehensive. Now Requirements: "Minimum Knowledge, Skills, And Abilities Required Experience managing Patient Access or front-end revenue cycle operations within a hospital or large health system.Knowledge of registration, insurance verification, and financial clearance processes.Strong interpersonal, communication, and leadership skills.Ability to manage multiple priorities in a fast-paced healthcare environment.Ability to work effectively in a collaborative, matrixed organization." We can make list items: - Experience managing Patient Access or front-end revenue cycle operations within a hospital or large health system. - Knowledge of registration, insurance verification, and financial clearance processes. - Strong interpersonal, communication, and leadership skills. - Ability to manage multiple priorities in a fast-paced healthcare environment. - Ability to work effectively in a collaborative, matrixed organization. Now Qualifications: Education Requirements Bachelor’s Degree strongly preferred; or High School Diploma/GED with equivalent, 3-4 years of directly relevant experience. Experience Requirements Minimum 3 years of leadership or supervisory experience in Patient Access or revenue cycle operations within a hospital or large health system. Experience working in a unionized healthcare environment preferred. Experience with EPIC preferred. Working Conditions Hospital or ambulatory environment. We can split into list items under Qualifications: - Bachelor’s Degree strongly preferred; or High School Diploma/GED with equivalent, 3-4 years of directly relevant experience. - Minimum 3 years of leadership or supervisory experience in Patient Access or revenue cycle operations within a hospital or large health system. - Experience working in a unionized healthcare environment preferred. - Experience with EPIC preferred. - Working Conditions: Hospital or ambulatory environment. Now Skills: maybe we could include specific skills like EPIC, etc. But we already have EPIC under Qualifications. Could also include "Strong interpersonal, communication, and leadership skills" already in Requirements. Might be redundant. Perhaps we can omit Skills section if content overlaps. But we need to follow instruction: Prefer a few substantive sections over many thin ones. Could combine Requirements and Skills? But we already used Requirements for knowledge, skills, abilities. Could skip Skills. However we have to decide if we need Skills heading. The posting includes "Strong interpersonal, communication, and leadership skills." That's a skill. But we already have it under Requirements. Could move it to Skills and keep Requirements for experience/knowledge only. But we already have experience under Requirements. Let's think: The headings list includes Requirements and Skills separate. We can allocate: - Requirements: Experience managing Patient Access..., Knowledge of registration..., Ability to manage multiple priorities..., Ability to work effectively... - Skills: Strong interpersonal, communication, and leadership skills.; Experience with EPIC preferred (maybe skill). But EPIC is experience. Better to keep Requirements as the list we made (experience, knowledge, abilities). Skills could be "Strong interpersonal, communication, and leadership skills." plus maybe "Experience with EPIC preferred" (skill). But we already have EPIC under Qualifications; maybe we move it to Skills. Let's restructure: Qualifications: Education and Experience (leadership years, union, etc). Actually experience requirements could be under Qualifications. We'll keep Qualifications for education and experience (including years, union, EPIC). Then Skills for interpersonal, communication, leadership, ability to manage priorities, collaborative matrix. But the posting says "Ability to manage multiple priorities in a fast-paced healthcare environment." and "Ability to work effectively in a collaborative, matrixed organization." Those are abilities, could be Skills. Thus: Qualifications: - Bachelor’s Degree strongly preferred; or High School Diploma/GED with equivalent, 3-4 years of directly relevant experience. - Minimum 3 years of leadership or supervisory experience in Patient Access or revenue cycle operations within a hospital or large health system. - Experience working in a unionized healthcare environment preferred. - Working Conditions: Hospital or ambulatory environment. Skills: - Experience with EPIC preferred. - Strong interpersonal, communication, and leadership skills. - Ability to manage multiple priorities in a fast-paced healthcare environment. - Ability to work effectively in a collaborative, matrixed organization. Requirements: - Experience managing Patient Access or front-end revenue cycle operations within a hospital or large health system. - Knowledge of registration, insurance verification, and financial clearance processes. But we have overlapping. Might be okay as long as we preserve all info. We need to avoid duplication? Not prohibited but better not duplicate same sentence. We'll try to allocate each piece once. Let's list all distinct pieces from posting: Intro paragraph: "The RCM – Manager of Patient Access Services is responsible for the day-to-day management of Patient Access operations across assigned hospital service areas (e.g., Emergency Department, Admitting, Same Day Surgery, Labor & Delivery). As needed, this role will also provide leadership support to other patient access areas across one or more hospital locations. This role ensures accurate patient registration, insurance verification, and financial clearance, and compliance with all regulatory, payer, and organizational requirements. The Manager provides direct leadership to Patient Access supervisors, leads, and staff. They also support center led revenue cycle initiatives, and promote a consistent, patient-centered access experience. This position works collaboratively with Revenue Cycle, Finance, Case Management, Clinical leadership, IT, and Human Resources to support operational efficiency, regulatory compliance