VP Service Line Executive, Hospital Medicine

We need to output HTML fragment with sections: About the role? The posting includes "Our Promise To You" (maybe about the role). Then "Job Description". Then "Knowledge, Skills, And Abilities". Then "Education". Then "Work Experience". Then "Additional Information" includes Licenses And Certifications, Physical Requirements, Pay Range, Background Screening Requirement, EEO etc. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Our Promise To You" maybe considered boilerplate? It's a description of culture; could be considered "About the role" or "About the company". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real, specific content. We have content for: About the role (maybe "Our Promise To You" and job description summary). Responsibilities: the VP duties listed. Requirements: Knowledge, Skills, And Abilities, Education, Work Experience, Licenses And Certifications. Benefits: list of benefits (Medical, Dental, Vision Insurance, Life Insurance, Disability Insurance, Paid Time Off from Day One, 403-B Retirement Plan, 4 Weeks 100% Paid Parental Leave, Career Development, Whole Person Well-being Resources, Mental Health Resources and Support, Pet Benefits). Pay: they gave Pay Range $0.00 - $0.00 which is placeholder; we must NOT include Pay section if it's placeholder like "0.00 - 0.00" or "not specified". So we should omit Pay. Schedule: they have "Schedule Full time Shift Day (United States of America)". That's specific: Full time, Shift Day. So we can include Schedule section. We must not repeat job title as heading. No Job ID. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from responsibilities, etc. We need to format using

for each section heading, then content: either

for prose or

• for lists. We need to decide which content goes where. Let's extract sections: - About the role / Our Promise To You: The first paragraph about belonging to community, thriving professionally, etc. Also maybe the "Job Description" intro paragraph: "The Vice President (VP), Service Line Executive for a designated hospital-based specialty provides statewide physician leadership as part of the Florida Specialty Network (FSN)." That could be part of About the role or Responsibilities. But we have a Responsibilities section later with bullet list of duties. So we can put the introductory paragraph under About the role. - Responsibilities: list of duties from "The VP is responsible for..." through many bullet-like sentences. We'll turn each sentence into
• . - Requirements: Could combine Knowledge, Skills, And Abilities, Education, Work Experience, Licenses And Certifications. But the instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could have separate sections: Requirements (maybe combine Knowledge, Skills, And Abilities), Qualifications (Education and Work Experience), Skills (maybe separate?), but we should avoid thin sections. Better to have: Requirements (Knowledge, Skills, And Abilities), Qualifications (Education & Work Experience), Licenses & Certifications (maybe under Requirements). However we need to follow the examples: they gave list of possible headings but not mandatory to use all. We can choose a few substantive sections. We need to include Benefits section: list of benefits. Schedule section: Full time Shift Day. We must not include Pay. We must remove boilerplate: EEO, background screening? Background screening requirement is substantive? It's a requirement but maybe considered boilerplate? It's a legal requirement; but it's specific to Florida Law. Might be considered substantive? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Background screening requirement is legal; but it's a requirement for the job. Might be considered boilerplate? It's a legal requirement; but it's not EEO. It's a condition of employment. Might be considered substantive? The instruction says remove legal boilerplate. I'd treat background screening as legal boilerplate and remove it. Also remove "Physical Requirements: (Please click the link below to view work requirements)" - that's a link; maybe we can keep? It's a reference to physical requirements; but it's a link; we could keep as a note? Probably better to remove as it's just a link. We must preserve all substantive information; but if we remove the background screening, we might be removing a requirement. However it's a legal requirement; maybe considered boilerplate. The instruction says remove legal/EEO/equal-opportunity/scam-warning boilerplate. So we remove it. Similarly, "Physical Requirements: (Please click the link below to view work requirements)" is a link to legal; we can drop. Now Benefits: list them exactly as given. Schedule: "Full time Shift Day (United States of America)". We'll output as a

  . Now we need to ensure we don't include any filler like "commensurate with experience". Not present. Now craft HTML. Structure:

  About the role

  Our Promise To You Joining AdventHealth is about being part of something bigger. It’s about belonging to a community that believes in the wholeness of each person, and serves to uplift others in body, mind and spirit. AdventHealth is a place where you can thrive professionally, and grow spiritually, by Extending the Healing Ministry of Christ. Where you will be valued for who you are and the unique experiences you bring to our purpose-minded team. All while understanding that together we are even better.

  The Vice President (VP), Service Line Executive for a designated hospital-based specialty provides statewide physician leadership as part of the Florida Specialty Network (FSN). This role partners with the Administrative VP of the hospital-based specialty and market leaders to unify operations across Florida's three divisions with potential to expand across AdventHealth.

  Then Responsibilities:

  Responsibilities

  • Developing and executing statewide, specialty-specific strategies that reflect deep expertise in the specialty, foster clinical integration, advance quality outcomes, drive innovation, expand consumer access, and sustain growth.
  • Serving as a consultant to all other medical groups across AdventHealth to develop hospital-based specialty specific strategies and clinical standards as it relates to their respective specialty and service line in context of those markets competitive landscape.
  • Creating specialty specific playbooks for clinical integration, advance quality outcomes, drive innovation, expand consumer access, and sustain growth and financial stability, deployed across AdventHealth in appropriate timing with market specific relevance under the leadership of the specialty dyad.
  • Modeling dyad leadership by co-developing strategic, operational, clinical and financial priorities with the Administrative VP, presenting a unified vision for each service line across the state.
  • Convening cross-divisional leaders to ensure alignment of roles, governance, and accountability.
  • Leading design, development, and execution of statewide specialty specific clinical strategies that integrate best practices, innovation, and efficient resource utilization, including inpatient/hospitalist models and call strategies (when applicable).
  • Partnering with Market Strategy & Development to support market expansion, prioritization, and workforce planning.
  • Collaborating with AHMG and Strategy leaders to recruit, engage, and develop physicians and APPs.
  • Promoting diversity, mentorship, and succession planning in physician leadership pipelines.
  • Strengthening fellowship and academic partnerships in collaboration with , when applicable.
  • Driving adoption of evidence-based clinical standards, care pathways, benchmarking, and safety practices.
  • Advancing innovation by evaluating and scaling AI-powered screening, predictive analytics, digital platforms, and clinical research that are relevant to the specialty and aligned with statewide strategy.
  • Continuously evaluating emerging trends and technologies in the specialty, recommending strategic adoption to improve quality, access, and operational efficiency.
  • Collaborating with consumer access and marketing leaders to enhance the patient journey.
  • Building a unified brand identity statewide while honoring local market needs.
  • Partnering with Finance and Operations to optimize productivity, cost-of-care variation, and supply chain efficiency.
  • In collaboration with statewide strategy, representing AdventHealth in national societies, philanthropy, and industry collaborations.
  • Financial stewardship shared with administrative leadership, tied to growth, access, and outcomes.
  • Physician engagement and culture, with a focus on wellness, succession planning, and leadership pipelines.
  • Providing consultation and expertise to other AdventHealth medical groups across the company to develop specialty specific strategies and clinical playbooks to foster clinical integration, advance quality outcomes, drive innovation, expand consumer access, and sustain growth.
  • At the direction of AH Physician Enterprise, leading in partnership across AdventHealth along with AHMG leadership the deployment and governance of specialty specific playbooks created in Florida Specialty Network, to foster clinical integration, advance quality outcomes, drive innovation, expand consumer access, and sustain growth and financial stability.
  • Serving as a statewide convener and advocate for physicians, fostering trust and alignment across divisions.
  • Serving as the statewide clinical authority for the specialty, ensuring evidence-based practice is advanced and adapted to meet emerging trends and innovations.
  • Providing consultation and expertise on specialty specific clinical strategies to AdventHealth strategy and market development teams when they are establishing a new market that will include the specialty.
  Now Requirements: Knowledge, Skills, And Abilities.

  Requirements

  • Expertise in physician leadership, program growth, and specialty care integration. [Required]
  • Demonstrated success in dyad or shared leadership models, with ability to balance clinical authority and administrative strategy in joint decision-making. [Required]
  • Strong skills in strategic planning, change leadership, and cross-functional collaboration. [Required]
  • Knowledge of hospital-based operations, access optimization, and workforce modeling. [Required]
  • Ability to influence and align diverse stakeholders across markets and divisions. [Required]
  • Commitment to high reliability, quality, safety, and patient-centered care. [Required]
  • Recognized expertise in the specialty, with ability to translate clinical insight into system-wide strategies. [Required]
  • Capacity to innovate and challenge traditional models of care, balancing clinical rigor with operational efficiency. [Required]
  Now Qualifications: Education and Work Experience.

  Qualifications

  Education

  Doctor of Medicine (MD) or Doctor of Osteopathic Medicine (DO). [Required]

  Master’s degree in Business, Healthcare Administration, or Public Health (MBA, MHA, MPH). [Preferred]

  Work Experience

  • Minimum 3 years of progressive physician leadership experience in a large, matrixed, multi-division health system. [Required]
  • Demonstrated success in program strategy, growth, and collaboration. [Required]
  • Minimum 5 years of progressive physician leadership experience in a large, matrixed, multi-division health system. [Preferred]
  • Experience with clinical innovation, digital health, and academic partnerships. [Preferred]
  But we used

  inside; the instruction only said use

  for section headings. It didn't forbid other headings, but to be safe we could avoid

  and just use

  for Education and Work Experience headings? Could use

  for each subsection but that would be many sections. Better to keep

  for main sections and use

  or for subheadings. The instruction: "use

  for section headings (e.g. About the role, Respons