Director, Digital Access and Capacity

We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract content. Job posting includes: description about community values, location, etc. We need to preserve substantive info, but remove boilerplate like EEO, etc. Also remove navigation, cookie, legal, duplicated lines, application instructions. There's no explicit application instructions. We need sections: maybe "About the role" could include the mission statement and location? The posting starts with community commitment, then location, etc. Could treat that as "About the role". Then "Responsibilities" from the responsibilities section. Then "Requirements" maybe from Minimum Education & Experience. Then "Qualifications" maybe from Knowledge, Skills & Abilities? Actually they have Knowledge, Skills & Abilities separate. Could map: Requirements = Minimum Education & Experience. Qualifications = maybe preferred qualifications? But we have both required and preferred. Could combine? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only those with real content. We have Pay: compensation range given. So we need a Pay section with that range. Schedule: we have Scheduled Weekly Hours 40, Work Shift UR - Day, Full time. So schedule info exists. Benefits: not mentioned explicitly. No benefits details. So we should not include Benefits heading. Skills: we have Knowledge, Skills & Abilities section. That could be Skills. Qualifications: maybe we can put Minimum Education & Experience as Requirements, and Knowledge, Skills & Abilities as Skills. Qualifications maybe we could put preferred qualifications (Master's degree preferred, experience with Epic preferred, etc.) but we could also treat that as Qualifications. However we need to avoid filler. We have both required and preferred. Could split: Requirements = required education/experience. Qualifications = preferred qualifications (Master's degree preferred, experience with Epic Cadence, MyChart, etc.). Skills = Knowledge, Skills & Abilities (the list). That seems reasonable. We need to preserve all substantive info, not invent or summarize away detail. So we need to include the details exactly as given, but we can format as

• for lists. We need to remove boilerplate: EEO statement, values statement maybe part of About the role? The initial paragraph about Meliora and values could be considered About the role? It's about the university community, not specific role. Might be considered boilerplate but it's part of the posting describing culture. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The values statement is not EEO but could be considered part of the university's commitment; it's not strictly boilerplate but could be kept as part of About the role. However it's generic. Might be okay to keep as part of About the role. We also have location info: Job Location (Full Address): 30 Corporate Woods, Brighton, New York, United States of America, 14623. That's substantive. Opening Worker Subtype: Regular Time Type Full time Scheduled Weekly Hours 40 Department 900300 Office of Digital Strategy and Innovation Work Shift UR - Day (United States of America) Range UR URG 117 Compensation Range $122,600.00 - $184,000.00 We need to include location, department, etc. Possibly in About the role. We need to avoid repeating job title as heading (not given). No Job ID/requisition numbers as headings. We need to output only HTML fragment. Let's structure:

  About the role

  ... include mission/community values, location, department, schedule basics? But schedule will be its own section. So About the role could include the university commitment, location, department, worker subtype, time type, etc.

  Then

  Responsibilities

  • ... each responsibility as separate li. The responsibilities paragraph is long; we need to split into list items. The text includes multiple sentences; we can break at each sentence that starts with a verb. But we must preserve all substantive info; we can just put the whole block as a

    ? The rule: Use

    • for any list of duties/requirements/benefits. The responsibilities are a list of duties, so we should use
      • . We need to split into items. Could create each sentence as li. Let's parse responsibilities section: "Provides leadership and operational oversight for enterprise digital access platforms that support patient scheduling, provider capacity, and operational access workflows. Leads the implementation, optimization, governance, and operational management of digital access capabilities, including Epic Cadence scheduling, scheduling workflows, provider templates, scheduling configuration, decision trees, visit types, referral workflows, and capacity optimization. Ensures operational access platforms are standardized, integrated, and optimized to maximize provider capacity, improve scheduling efficiency, and support a consistent patient access experience across ambulatory and procedural settings." Then "Essential Functions" seems to be a continuation but still responsibilities. The essential functions list many items, each starting with a verb. We could treat each sentence as li. We'll need to capture all sentences. Let's extract the responsibilities and essential functions text: Responsibilities block: "Provides leadership and operational oversight for enterprise digital access platforms that support patient scheduling, provider capacity, and operational access workflows. Leads the implementation, optimization, governance, and operational management of digital access capabilities, including Epic Cadence scheduling, scheduling workflows, provider templates, scheduling configuration, decision trees, visit types, referral workflows, and capacity optimization. Ensures operational access platforms are standardized, integrated, and optimized to maximize provider capacity, improve scheduling efficiency, and support a consistent patient access experience across ambulatory and procedural settings." Essential Functions block (multiple paragraphs): "Leads the implementation and continuous optimization of digital access initiatives in partnership with the Senior Director, Access and Capacity, including system-guided scheduling, eCheck-in, and referral management. Takes a strategic, hands-on approach to enhance patient interactions with the health system. Ensures initiatives are effectively executed and seamlessly integrated into operational workflows, and measurable improvements in patient access and overall experience are consistently delivered. Develops strategic plans, leads cross-functional collaboration and performance monitoring, and identifies and executes change management initiatives to drive adoption and achieve organizational goals. Leads and oversees the execution of enterprise-wide Demand-to-Capacity Alignment, strategically balancing patient demand with available provider capacity across ambulatory and procedural settings. Orchestrates provider template design and standardization, manages block utilization, and develops precise scheduling logic. Ensures that capacity is not only accessible and appropriately allocated but also seamlessly integrated with digital entry points for an optimized patient experience. Oversees and guides the enterprise-wide strategic design and continuous improvement of all scheduling workflows within Epic and other digital platforms. Defines and develops the architecture for appointment booking, managing system-guided scheduling, decision trees, visit types, and scheduling rules to ensure they are robust, consistent, and standardized across departments. Drives ongoing innovation, ensures scalability for future growth, and aligns optimizations with broader operational and digital access goals. Fosters cross-functional collaboration and establishes governance structures among IT, clinical operations, and patient access teams to enable seamless integration and effective implementation. Establishes enterprise access performance expectations for operational leaders and practice managers including time to third next available appointment, template utilization, referral conversion, and no-show rates. Monitors adherence to established metrics, identifies performance gaps, collaborates with leaders to implement corrective action plans, and escalates unresolved performance issues to executive leadership as appropriate. Drives accountability for performance improvement across service lines and operational partners. Drives enterprise-wide adoption and optimization of digital access tools, scheduling solutions, and standardized workflows through a collaborative partnership model with clinical, operational, and departmental leaders. Leads discovery and workflow assessment efforts to identify operational barriers, evaluate current and future-state workflows, and develop digital solutions that improve access, efficiency, and operational performance. Works with departments and key stakeholders to implement solutions, identify departmental champions, support communication and training efforts, and assist with change management activities necessary to support successful adoption. Partners with operational and departmental leadership to reinforce workflow and behavioral changes both within and outside the direct span of control of the role. Supports sustained utilization of digital solutions through ongoing engagement, performance monitoring, KPI tracking, reporting, and operational follow-up. Communicates progress, adoption metrics, and initiative outcomes through established governance and operational review structures, including reporting to senior leadership. Directly supervises a team of staff members, providing mentorship, setting priorities, and overseeing workflows to ensure high-quality results. Participates in interviews, approves hiring decisions, provides training and ongoing supervision, addresses personnel issues and actions, and conducts performance reviews. Engages and leads career development conversations and planning efforts. Ensures execution of tasks are aligned with departmental and organizational objectives. Remedies as appropriate. Fosters strong enterprise-wide partnerships with clinical, operational, digital, IT, and informatics leaders to align digital access and capacity strategies, prioritize initiatives, and support coordinated implementation across workflows and systems. Collaborates with stakeholders to advance access and capacity optimization efforts through workflow analysis, operational assessments, data-informed decision making, and implementation of digital solutions designed to improve appointment availability, patient flow, utilization, and operational efficiency. Influences cross-functional stakeholders and operational teams to align priorities, drive adoption, and support organizational change initiatives associated with digital access and capacity transformation efforts. Other duties as assigned." We need to include all that as li items. Now Requirements: Minimum Education & Experience: "Bachelor’s degree in healthcare administration, business, informatics, data analytics, or related field and 8 years of experience in healthcare operations, access and capacity management, digital health, or related field required. Or equivalent combination of education and experience. Master's degree in a related field preferred. Experience leading or managing teams or projects required. Experience with access performance metrics and operational improvement required. Experience with Epic Cadence, MyChart, or equivalent scheduling and digital access platforms preferred. Experience with digital front door capabilities (i.e., provider search, online scheduling, patient portals, eCheck-in) preferred." We need to split into li items. Qualifications: maybe we can treat preferred qualifications as Qualifications? But we already used preferred in Requirements. Could separate: Requirements = required items; Qualifications = preferred items. Let's do that. Thus: Requirements (required): - Bachelor’s degree in healthcare administration, business, informatics, data analytics, or related field and 8 years of experience in healthcare operations, access and capacity management, digital health, or related field. - Or equivalent combination of education and experience. - Experience leading or managing teams or projects. - Experience with access performance metrics and operational improvement. Qualifications (preferred): - Master's degree in a related field. - Experience with Epic Cadence, MyChart, or equivalent scheduling and digital access platforms. - Experience with digital front door capabilities (i.e., provider search, online scheduling, patient portals, eCheck-in). Skills: Knowledge, Skills & Abilities block: "Knowledge of healthcare access and capacity management, including scheduling workflows, provider templates, and patient flow required. Ability to align digital tools with operational workflows and capacity management strategies required. Ability to lead and influence others required. Ability to drive alignment and execution across cross-functional stakeholders required. Strong communication, facilitation, and problem-solving skills required. Understanding of Epic scheduling tools, including system-guided scheduling, decision trees, visit types, and template configuration preferred." We need to split into li items, marking required/preferred maybe keep the wording. Pay: Compensation Range $122,600.00 - $184,000.00 Schedule: Scheduled Weekly Hours 40, Work Shift UR - Day, Full time. Also we have Opening Worker Subtype: Regular, Time Type Full time, Department 900300 Office of Digital Strategy and Innovation. We could include those in About the role. Now we need to ensure we don't include boilerplate like EEO statement at end. Remove that.