Associate Vice President Health System Quality & Operational Excellence
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for any list of duties/requirements/benefits, and
for prose
- Do NOT repeat the job title as a heading (the page already shows it)
- Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it
- Preserve ALL substantive information; do NOT invent or summarize away detail
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
- Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them
- Prefer a few substantive sections over many thin ones
- Output ONLY the HTML fragment — no /, no markdown code fences
Now, let's analyze the job posting content.
The posting starts with "WHY UT SOUTHWESTERN?" which is a promotional section about the organization. This could be an "About the organization" or "Why join us" section. But the rules say to use headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". The "WHY UT SOUTHWESTERN?" is not exactly "About the role". It's more about the employer. However, the rules say to include a section ONLY when the posting has real, specific content for it. The posting does have a "Benefits" section later. The "WHY UT SOUTHWESTERN?" could be considered part of the employer branding, but maybe we can include it as a section like "About UT Southwestern" or "Why UT Southwestern". But the rules specify certain headings: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". It says "e.g." so we can use other headings if appropriate. However, we should not create headings that are not in the list unless they are substantive. The "WHY UT SOUTHWESTERN?" is a substantive section describing the organization. I think we can include it as a section with heading "About UT Southwestern" or "Why UT Southwestern". But the rules say "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 prefer those standard ones. However, the posting has a "Job Summary" section, which is like "About the role". Then "Benefits" section. Then "Required EXPERIENCE AND EDUCATION" which is Requirements/Qualifications. Then "Preferred Education" and "Preferred Experience". Then "Job Duties" which is Responsibilities. Then "Knowledge, Skills And Abilities" which is Skills. Then "Physical Requirements/Working Conditions". Then "Salary Information" which says "Salary Is Commensurate With Education, Skills, And Relevant Experience." That's a placeholder, not specific. According to rules: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting states "Salary Information Salary Is Commensurate With Education, Skills, And Relevant Experience." That's not a specific pay range; it's a generic statement. The rules say: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should NOT create a Pay section for that. Similarly, "Schedule" is mentioned in the metadata at the bottom: "Schedule Full-time Shift Day Job". That's specific: Full-time, Day shift. That could be a Schedule section. But the rules say never create Schedule sections unless the posting actually states them. It does state them in the metadata. However, the metadata also includes "Primary Location", "Work Locations", "Job Professional & Executive Organization", "Employee Status", "Job Type", "Job Posting date". Those are minor metadata; we should fold them into a short
or drop them. The rules: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include a short paragraph at the end with location, schedule, etc.
Also, we must remove EEO statement, security statement, etc. Those are boilerplate.
Now, let's structure the HTML.
We'll have sections:
1. About UT Southwestern (or Why UT Southwestern) - from the first paragraph.
2. About the role (Job Summary)
3. Responsibilities (Job Duties) - broken down by subsections: Analytics, Performance Improvement, Project Management, Systems Management, Financial Planning, Analysis and Management, Human Capital Management.
4. Requirements (Required EXPERIENCE AND EDUCATION) - Education and Experience.
5. Preferred Qualifications (Preferred Education and Experience)
6. Skills (Knowledge, Skills And Abilities)
7. Benefits (Benefits section)
8. Physical Requirements/Working Conditions
9. Additional Information (maybe a short paragraph for location, schedule, job type, posting date)
But we need to be careful: The rules say "Prefer a few substantive sections over many thin ones." So we might combine some.
Let's list the substantive content:
- Why UT Southwestern (promotional)
- Job Summary
- Benefits (detailed list)
- Required Education and Experience (with bullet points)
- Preferred Education and Experience
- Job Duties (detailed with subcategories)
- Knowledge, Skills and Abilities (list)
- Physical Requirements/Working Conditions (Office Setting)
- Salary Information (generic, so omit section)
- Metadata: Location, Schedule, Shift, Job Type, Employee Status, Organization, Posting date.
We should not include EEO, Security statements.
Now, we need to output HTML fragment with
headings and - for lists,
for prose.
We'll create sections for each major heading.
Let's decide on headings:
-
Why UT Southwestern
(or "About UT Southwestern")
- About the Role
(for Job Summary)
- Benefits
- Requirements
(for Required Education and Experience)
- Preferred Qualifications
- Responsibilities
(for Job Duties)
- Skills
(for Knowledge, Skills And Abilities)
- Working Conditions
(for Physical Requirements/Working Conditions)
- Additional Details
(for metadata)
But the rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So we should use those exact headings where appropriate. "About the role" matches Job Summary. "Responsibilities" matches Job Duties. "Requirements" matches Required Education and Experience. "Qualifications" could be used for Preferred Qualifications. "Skills" matches Knowledge, Skills And Abilities. "Benefits" matches Benefits. "Pay" and "Schedule" we might not include because Pay is generic and Schedule is in metadata. But we could include a "Schedule" section if we want, but the metadata says "Schedule Full-time Shift Day Job". That's specific. However, the rules say never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Schedule. But it's in the metadata at the bottom. The posting also states "Work Locations", "Primary Location". That's location. Could be part of "Additional Details".
I think we can include a "Schedule" section with the schedule info. But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state "Schedule Full-time Shift Day Job". So we can create a Schedule section. However, the metadata also includes "Employee Status Regular", "Job Type Standard", "Job Posting Oct 20, 2026". Those are minor. We can fold them into a short paragraph.
But the rules also say "fold minor metadata into a short
or drop it." So we can create a short paragraph at the end with location, schedule, job type, posting date.
Let's see: The posting has "Primary Location Texas-Dallas-5323 Harry Hines Blvd Work Locations 5323 Harry Hines Blvd Job Professional & Executive Organization 720001 - HSQ - Quality & Op Excellence Schedule Full-time Shift Day Job Employee Status Regular Job Type Standard Job Posting Oct 20, 2026, 8:40:37 PM". That's a block of metadata. We can put that in a
at the end.
Now, we need to preserve ALL substantive information. So we must include all bullet points from Job Duties, Requirements, Benefits, Skills, etc.
Let's write the HTML.
We'll start with Why UT Southwestern as a section. But the heading "Why UT Southwestern" is not in the example list. However, the rules say "e.g." so it's okay. But maybe we can call it "About UT Southwestern". I'll use "Why UT Southwestern" as it's the heading in the posting.
Then "About the Role" for Job Summary.
Then "Benefits" for Benefits.
Then "Requirements" for Required Education and Experience.
Then "Preferred Qualifications" for Preferred Education and Experience.
Then "Responsibilities" for Job Duties.
Then "Skills" for Knowledge, Skills And Abilities.
Then "Working Conditions" for Physical Requirements/Working Conditions.
Then a final paragraph for metadata.
We must not include the EEO and Security statements.
Now, let's write the HTML.
We'll use
for each section. For lists, use - . For prose, use
.
We need to ensure we don't duplicate content.
Let's parse the content:
**WHY UT SOUTHWESTERN?** paragraph: "With over 75 years of excellence in Dallas-Fort Worth, Texas, UT Southwestern is committed to excellence, innovation, teamwork, and compassion. As a world-renowned medical and research center, we strive to provide the best possible care, resources, and benefits for our valued employees. Ranked as the No. 1 hospital in Dallas-Fort Worth according to U.S. News & World Report, we invest in you with opportunities for career growth and development to align with your future goals. Our highly competitive benefits package offers healthcare, PTO and paid holidays, on-site childcare, wage, merit increases and so much more. We invite you to be a part of the UT Southwestern team where you’ll discover a culture of teamwork, professionalism, and a rewarding career!"
That's a prose paragraph. We'll put in
.
**Job Summary**: "The Assistant Vice President for Quality & Operational Excellence is responsible for devising, planning, and leading the implementation of key comprehensive and integrated strategies in support of the Office of the CQO. Reporting directly to the CQO, the AVP will direct and integrate critical functions that are essential to the efficient and effective execution of the quality enterprise. Such functions include evaluating operations, analyzing data and information for reporting and informed decision making and recommending solutions to help achieve performance and strategic objectives. The AVP will ensure the coordination of activities across the areas of analytics, performance improvement, and project management to achieve quality and operational excellence."
Prose.
for prose - Do NOT repeat the job title as a heading (the page already shows it) - Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions - Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no /, no markdown code fences Now, let's analyze the job posting content. The posting starts with "WHY UT SOUTHWESTERN?" which is a promotional section about the organization. This could be an "About the organization" or "Why join us" section. But the rules say to use headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". The "WHY UT SOUTHWESTERN?" is not exactly "About the role". It's more about the employer. However, the rules say to include a section ONLY when the posting has real, specific content for it. The posting does have a "Benefits" section later. The "WHY UT SOUTHWESTERN?" could be considered part of the employer branding, but maybe we can include it as a section like "About UT Southwestern" or "Why UT Southwestern". But the rules specify certain headings: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". It says "e.g." so we can use other headings if appropriate. However, we should not create headings that are not in the list unless they are substantive. The "WHY UT SOUTHWESTERN?" is a substantive section describing the organization. I think we can include it as a section with heading "About UT Southwestern" or "Why UT Southwestern". But the rules say "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 prefer those standard ones. However, the posting has a "Job Summary" section, which is like "About the role". Then "Benefits" section. Then "Required EXPERIENCE AND EDUCATION" which is Requirements/Qualifications. Then "Preferred Education" and "Preferred Experience". Then "Job Duties" which is Responsibilities. Then "Knowledge, Skills And Abilities" which is Skills. Then "Physical Requirements/Working Conditions". Then "Salary Information" which says "Salary Is Commensurate With Education, Skills, And Relevant Experience." That's a placeholder, not specific. According to rules: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting states "Salary Information Salary Is Commensurate With Education, Skills, And Relevant Experience." That's not a specific pay range; it's a generic statement. The rules say: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should NOT create a Pay section for that. Similarly, "Schedule" is mentioned in the metadata at the bottom: "Schedule Full-time Shift Day Job". That's specific: Full-time, Day shift. That could be a Schedule section. But the rules say never create Schedule sections unless the posting actually states them. It does state them in the metadata. However, the metadata also includes "Primary Location", "Work Locations", "Job Professional & Executive Organization", "Employee Status", "Job Type", "Job Posting date". Those are minor metadata; we should fold them into a short
or drop them. The rules: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include a short paragraph at the end with location, schedule, etc. Also, we must remove EEO statement, security statement, etc. Those are boilerplate. Now, let's structure the HTML. We'll have sections: 1. About UT Southwestern (or Why UT Southwestern) - from the first paragraph. 2. About the role (Job Summary) 3. Responsibilities (Job Duties) - broken down by subsections: Analytics, Performance Improvement, Project Management, Systems Management, Financial Planning, Analysis and Management, Human Capital Management. 4. Requirements (Required EXPERIENCE AND EDUCATION) - Education and Experience. 5. Preferred Qualifications (Preferred Education and Experience) 6. Skills (Knowledge, Skills And Abilities) 7. Benefits (Benefits section) 8. Physical Requirements/Working Conditions 9. Additional Information (maybe a short paragraph for location, schedule, job type, posting date) But we need to be careful: The rules say "Prefer a few substantive sections over many thin ones." So we might combine some. Let's list the substantive content: - Why UT Southwestern (promotional) - Job Summary - Benefits (detailed list) - Required Education and Experience (with bullet points) - Preferred Education and Experience - Job Duties (detailed with subcategories) - Knowledge, Skills and Abilities (list) - Physical Requirements/Working Conditions (Office Setting) - Salary Information (generic, so omit section) - Metadata: Location, Schedule, Shift, Job Type, Employee Status, Organization, Posting date. We should not include EEO, Security statements. Now, we need to output HTML fragment with
headings and - for lists,
for prose.
We'll create sections for each major heading.
Let's decide on headings:
-
Why UT Southwestern
(or "About UT Southwestern")
- About the Role
(for Job Summary)
- Benefits
- Requirements
(for Required Education and Experience)
- Preferred Qualifications
- Responsibilities
(for Job Duties)
- Skills
(for Knowledge, Skills And Abilities)
- Working Conditions
(for Physical Requirements/Working Conditions)
- Additional Details
(for metadata)
But the rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So we should use those exact headings where appropriate. "About the role" matches Job Summary. "Responsibilities" matches Job Duties. "Requirements" matches Required Education and Experience. "Qualifications" could be used for Preferred Qualifications. "Skills" matches Knowledge, Skills And Abilities. "Benefits" matches Benefits. "Pay" and "Schedule" we might not include because Pay is generic and Schedule is in metadata. But we could include a "Schedule" section if we want, but the metadata says "Schedule Full-time Shift Day Job". That's specific. However, the rules say never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Schedule. But it's in the metadata at the bottom. The posting also states "Work Locations", "Primary Location". That's location. Could be part of "Additional Details".
I think we can include a "Schedule" section with the schedule info. But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state "Schedule Full-time Shift Day Job". So we can create a Schedule section. However, the metadata also includes "Employee Status Regular", "Job Type Standard", "Job Posting Oct 20, 2026". Those are minor. We can fold them into a short paragraph.
But the rules also say "fold minor metadata into a short
or drop it." So we can create a short paragraph at the end with location, schedule, job type, posting date.
Let's see: The posting has "Primary Location Texas-Dallas-5323 Harry Hines Blvd Work Locations 5323 Harry Hines Blvd Job Professional & Executive Organization 720001 - HSQ - Quality & Op Excellence Schedule Full-time Shift Day Job Employee Status Regular Job Type Standard Job Posting Oct 20, 2026, 8:40:37 PM". That's a block of metadata. We can put that in a
at the end.
Now, we need to preserve ALL substantive information. So we must include all bullet points from Job Duties, Requirements, Benefits, Skills, etc.
Let's write the HTML.
We'll start with Why UT Southwestern as a section. But the heading "Why UT Southwestern" is not in the example list. However, the rules say "e.g." so it's okay. But maybe we can call it "About UT Southwestern". I'll use "Why UT Southwestern" as it's the heading in the posting.
Then "About the Role" for Job Summary.
Then "Benefits" for Benefits.
Then "Requirements" for Required Education and Experience.
Then "Preferred Qualifications" for Preferred Education and Experience.
Then "Responsibilities" for Job Duties.
Then "Skills" for Knowledge, Skills And Abilities.
Then "Working Conditions" for Physical Requirements/Working Conditions.
Then a final paragraph for metadata.
We must not include the EEO and Security statements.
Now, let's write the HTML.
We'll use
for each section. For lists, use - . For prose, use
.
We need to ensure we don't duplicate content.
Let's parse the content:
**WHY UT SOUTHWESTERN?** paragraph: "With over 75 years of excellence in Dallas-Fort Worth, Texas, UT Southwestern is committed to excellence, innovation, teamwork, and compassion. As a world-renowned medical and research center, we strive to provide the best possible care, resources, and benefits for our valued employees. Ranked as the No. 1 hospital in Dallas-Fort Worth according to U.S. News & World Report, we invest in you with opportunities for career growth and development to align with your future goals. Our highly competitive benefits package offers healthcare, PTO and paid holidays, on-site childcare, wage, merit increases and so much more. We invite you to be a part of the UT Southwestern team where you’ll discover a culture of teamwork, professionalism, and a rewarding career!"
That's a prose paragraph. We'll put in
.
**Job Summary**: "The Assistant Vice President for Quality & Operational Excellence is responsible for devising, planning, and leading the implementation of key comprehensive and integrated strategies in support of the Office of the CQO. Reporting directly to the CQO, the AVP will direct and integrate critical functions that are essential to the efficient and effective execution of the quality enterprise. Such functions include evaluating operations, analyzing data and information for reporting and informed decision making and recommending solutions to help achieve performance and strategic objectives. The AVP will ensure the coordination of activities across the areas of analytics, performance improvement, and project management to achieve quality and operational excellence."
Prose.
for prose. We'll create sections for each major heading. Let's decide on headings: -
Why UT Southwestern
(or "About UT Southwestern") -About the Role
(for Job Summary) -Benefits
-Requirements
(for Required Education and Experience) -Preferred Qualifications
-Responsibilities
(for Job Duties) -Skills
(for Knowledge, Skills And Abilities) -Working Conditions
(for Physical Requirements/Working Conditions) -Additional Details
(for metadata) But the rules say "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So we should use those exact headings where appropriate. "About the role" matches Job Summary. "Responsibilities" matches Job Duties. "Requirements" matches Required Education and Experience. "Qualifications" could be used for Preferred Qualifications. "Skills" matches Knowledge, Skills And Abilities. "Benefits" matches Benefits. "Pay" and "Schedule" we might not include because Pay is generic and Schedule is in metadata. But we could include a "Schedule" section if we want, but the metadata says "Schedule Full-time Shift Day Job". That's specific. However, the rules say never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Schedule. But it's in the metadata at the bottom. The posting also states "Work Locations", "Primary Location". That's location. Could be part of "Additional Details". I think we can include a "Schedule" section with the schedule info. But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state "Schedule Full-time Shift Day Job". So we can create a Schedule section. However, the metadata also includes "Employee Status Regular", "Job Type Standard", "Job Posting Oct 20, 2026". Those are minor. We can fold them into a short paragraph. But the rules also say "fold minor metadata into a short
or drop it." So we can create a short paragraph at the end with location, schedule, job type, posting date. Let's see: The posting has "Primary Location Texas-Dallas-5323 Harry Hines Blvd Work Locations 5323 Harry Hines Blvd Job Professional & Executive Organization 720001 - HSQ - Quality & Op Excellence Schedule Full-time Shift Day Job Employee Status Regular Job Type Standard Job Posting Oct 20, 2026, 8:40:37 PM". That's a block of metadata. We can put that in a
at the end. Now, we need to preserve ALL substantive information. So we must include all bullet points from Job Duties, Requirements, Benefits, Skills, etc. Let's write the HTML. We'll start with Why UT Southwestern as a section. But the heading "Why UT Southwestern" is not in the example list. However, the rules say "e.g." so it's okay. But maybe we can call it "About UT Southwestern". I'll use "Why UT Southwestern" as it's the heading in the posting. Then "About the Role" for Job Summary. Then "Benefits" for Benefits. Then "Requirements" for Required Education and Experience. Then "Preferred Qualifications" for Preferred Education and Experience. Then "Responsibilities" for Job Duties. Then "Skills" for Knowledge, Skills And Abilities. Then "Working Conditions" for Physical Requirements/Working Conditions. Then a final paragraph for metadata. We must not include the EEO and Security statements. Now, let's write the HTML. We'll use
for each section. For lists, use - . For prose, use
.
We need to ensure we don't duplicate content.
Let's parse the content:
**WHY UT SOUTHWESTERN?** paragraph: "With over 75 years of excellence in Dallas-Fort Worth, Texas, UT Southwestern is committed to excellence, innovation, teamwork, and compassion. As a world-renowned medical and research center, we strive to provide the best possible care, resources, and benefits for our valued employees. Ranked as the No. 1 hospital in Dallas-Fort Worth according to U.S. News & World Report, we invest in you with opportunities for career growth and development to align with your future goals. Our highly competitive benefits package offers healthcare, PTO and paid holidays, on-site childcare, wage, merit increases and so much more. We invite you to be a part of the UT Southwestern team where you’ll discover a culture of teamwork, professionalism, and a rewarding career!"
That's a prose paragraph. We'll put in
.
**Job Summary**: "The Assistant Vice President for Quality & Operational Excellence is responsible for devising, planning, and leading the implementation of key comprehensive and integrated strategies in support of the Office of the CQO. Reporting directly to the CQO, the AVP will direct and integrate critical functions that are essential to the efficient and effective execution of the quality enterprise. Such functions include evaluating operations, analyzing data and information for reporting and informed decision making and recommending solutions to help achieve performance and strategic objectives. The AVP will ensure the coordination of activities across the areas of analytics, performance improvement, and project management to achieve quality and operational excellence."
Prose.
. We need to ensure we don't duplicate content. Let's parse the content: **WHY UT SOUTHWESTERN?** paragraph: "With over 75 years of excellence in Dallas-Fort Worth, Texas, UT Southwestern is committed to excellence, innovation, teamwork, and compassion. As a world-renowned medical and research center, we strive to provide the best possible care, resources, and benefits for our valued employees. Ranked as the No. 1 hospital in Dallas-Fort Worth according to U.S. News & World Report, we invest in you with opportunities for career growth and development to align with your future goals. Our highly competitive benefits package offers healthcare, PTO and paid holidays, on-site childcare, wage, merit increases and so much more. We invite you to be a part of the UT Southwestern team where you’ll discover a culture of teamwork, professionalism, and a rewarding career!" That's a prose paragraph. We'll put in
. **Job Summary**: "The Assistant Vice President for Quality & Operational Excellence is responsible for devising, planning, and leading the implementation of key comprehensive and integrated strategies in support of the Office of the CQO. Reporting directly to the CQO, the AVP will direct and integrate critical functions that are essential to the efficient and effective execution of the quality enterprise. Such functions include evaluating operations, analyzing data and information for reporting and informed decision making and recommending solutions to help achieve performance and strategic objectives. The AVP will ensure the coordination of activities across the areas of analytics, performance improvement, and project management to achieve quality and operational excellence." Prose.