Senior Manager Informatics - Strategy and Development
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real, specific content. We have content for About the role (the intro paragraph). Responsibilities: the "What You Will Do" bullet list. Requirements/Qualifications: "For This Role You Will Need - Minimum Requirements" and "Education Preferred Qualifications". Skills: maybe combine with requirements? We can have a Skills section for listed skills like analytical, problem-resolution, interpersonal, etc. Benefits: there is "Great Benefits For Great People" describing benefits. Pay: there is pay range. Schedule: not mentioned, so omit.
We must not repeat job title as heading. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO etc. There's a line about "Qualified applicants with arrest or conviction records will be considered..." that's EEO; we should remove. Also "Our people fuel our future..." maybe not boilerplate but could be considered fluff; but it's about culture; maybe keep as part of About the role? It's not specific to role; but we can keep as part of About the role? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Our people fuel our future..." is not EEO but maybe generic; but we can keep as part of About the role? It's not specific to role but could be considered fluff. Safer to keep only substantive role-specific content. The intro paragraph about building a world of health is generic but could be considered About the role/company. We'll keep as About the role.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points from "What You Will Do". Also include the bullet points from "For This Role You Will Need - Minimum Requirements". Also include "Education Preferred Qualifications". Also include "Hands-on Epic experience" etc under Preferred Qualifications? Actually after Education Preferred Qualifications they list: Bachelor's degree or equivalent relevant experience. Master's degree preferred. Hands-on Epic experience Experience with JIRA, Confluence, or similar project and intake management tools.Experience with vendor contracting, procurement, or cost accounting in a healthcare or enterprise IT setting. Those are preferred qualifications.
We need to decide sections: About the role (intro paragraph). Responsibilities (What You Will Do). Requirements (minimum requirements). Qualifications (education and preferred). Skills maybe separate but could be merged. Benefits (Great Benefits...). Pay (Pay Range). No Schedule.
We must not create sections with filler like "commensurate with experience". Not present.
We need to use - for any list of duties/requirements/benefits. For prose use
.
We need to ensure we don't duplicate content.
Let's extract sections:
About the role: The first paragraph(s) before "Job Profile Summary": "We’re building a world of health around every individual — shaping a more connected, convenient and compassionate health experience. At CVS Health®, you’ll be surrounded by passionate colleagues who care deeply, innovate with purpose, hold ourselves accountable and prioritize safety and quality in everything we do. Join us and be part of something bigger – helping to simplify health care one person, one family and one community at a time."
Then there is "Job Profile Summary" which is a heading but we should not repeat job title as heading; but we can treat that as part of About the role? Actually "Job Profile Summary" is a section heading but we are told to use
for section headings like About the role, Responsibilities, etc. So we could map "Job Profile Summary" to About the role? But we already have About the role intro. Maybe we should treat "Job Profile Summary" as About the role content. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we can use headings like About the role, Responsibilities, etc. So we can have About the role
and then include the content from Job Profile Summary and the intro paragraph.
Thus About the role content: combine the intro paragraph and the Job Profile Summary paragraph: "The role is focused on strategic planning, financial management, and enterprise alignment for the enterprise Epic (EHR) program and related clinical informatics initiatives. Owns the connection between long-range strategy and day-to-day execution, and building roadmaps, evaluating vendor direction, managing the financial portfolio, and identifying and mitigating risk across the program. Partners closely with Medical, IT, Privacy, Legal, and Compliance leaders to ensure initiatives are sound from every angle, and works directly with business and technical stakeholders to translate project requests into requirements and, ultimately, delivered outcomes. This role directly supports the organization's ability to deliver efficient, high-quality, and safe healthcare through its technology investments."
Also maybe include "A Brief Overview" paragraph? That seems like a summary of responsibilities; but we have a separate Responsibilities section. The "A Brief Overview" could be considered part of About the role or Responsibilities. It says: "Shapes the strategic direction of the Epic and clinical informatics portfolio by developing multi-year roadmaps, evaluating vendor roadmaps for applicability and opportunity, and aligning initiatives to enterprise priorities. Manages budgeting, capital planning, and financial tracking for the program, while proactively identifying project and program risks and engaging the right cross-functional partners to resolve them. Serves as a bridge between business users and technical teams, ensuring requests are well understood, properly scoped, and translated into requirements and deliverables that hold up through implementation. Brings structure and discipline to a fast-moving, matrixed environment through strong documentation, clear governance, and consistent follow-through."
That seems like responsibilities. So we could put that in Responsibilities section as well, but we already have a detailed "What You Will Do" list. To avoid duplication, we could merge the "A Brief Overview" into Responsibilities as prose, and then the bullet list as list. But we must preserve all substantive information; we can include both prose and list.
Thus Responsibilities: include the paragraph from "A Brief Overview" as
, then the bullet list from "What You Will Do" as
- ... each bullet.
Now Requirements: Minimum Requirements bullet list: "7–10 years of related experience in healthcare, strategy, finance, or healthcare IT/informatics is required. Experience supporting or working with an Epic (EHR) and/or healthcare delivery settings. Strong analytical, problem-resolution, and interpersonal skills. Demonstrated experience with strategic planning, roadmap development, and portfolio or financial management within a healthcare IT or informatics setting. Experience working on large, cross-functional projects; strong knowledge of clinical applications and the healthcare industry. Demonstrated ability to bridge communication among technical and non-technical project staff and customers. Strong executive presence with experience presenting to and building relationships with senior stakeholders across a large enterprise. Experience participating in budgeting, capital planning, or financial portfolio management."
We can put each as
- .
Qualifications: Education Preferred Qualifications: "Bachelor's degree or equivalent relevant experience. Master's degree preferred. Hands-on Epic experience Experience with JIRA, Confluence, or similar project and intake management tools. Experience with vendor contracting, procurement, or cost accounting in a healthcare or enterprise IT setting."
We could split into Education and Skills? But we have a Skills section maybe for skills like analytical, problem-resolution, interpersonal, etc. However those are already in Requirements. Could create a Skills section for those soft skills. But we already have them in Requirements; we could keep them there. The instruction: Use sections like Skills only if posting has real specific content. It does list skills: Strong analytical, problem-resolution, and interpersonal skills; Demonstrated ability to bridge communication; Strong executive presence; etc. Could put them in Skills. But to avoid duplication, we could keep them in Requirements and not have a separate Skills section. However the instruction says we can use Skills section; but we must not create thin sections. If we put skills in Requirements, that's fine.
Thus we have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
Now Benefits: The paragraph under "Great Benefits For Great People": "We take pride in offering a comprehensive and competitive mix of pay and benefits that reflects our commitment to our colleagues and their families. This full‑time position is eligible for a comprehensive benefits package designed to support the physical, emotional, and financial well‑being of colleagues and their families. The benefits for this position include medical, dental, and vision coverage, paid time off, retirement savings options, wellness programs, and other resources, based on eligibility. Additional details about available benefits are provided during the application process and on Benefits Moments."
We need to preserve that. Also there is line: "We anticipate the application window for this opening will close on: 10/26/2026" - that's application instruction; we should remove. Also "Qualified applicants with arrest or conviction records will be considered..." remove.
Pay: The paragraph(s) under "Pay Range": "The Typical Pay Range For This Role Is $82,940.00 - $182,549.00 This pay range represents the base hourly rate or base annual full-time salary for all positions in the job grade within which this position falls. The actual base salary offer will depend on a variety of factors including experience, education, geography and other relevant factors. This position is eligible for a CVS Health bonus, commission or short-term incentive program in addition to the base pay range listed above. This position also includes an award target in the company’s equity award program."
We need to preserve all that.
Now we need to output only HTML fragment, no /, no markdown.
We'll structure:
About the role
We’re building a world of health around every individual — shaping a more connected, convenient and compassionate health experience. At CVS Health®, you’ll be surrounded by passionate colleagues who care deeply, innovate with purpose, hold ourselves accountable and prioritize safety and quality in everything we do. Join us and be part of something bigger – helping to simplify health care one person, one family and one community at a time.
The role is focused on strategic planning, financial management, and enterprise alignment for the enterprise Epic (EHR) program and related clinical informatics initiatives. Owns the connection between long-range strategy and day-to-day execution, and building roadmaps, evaluating vendor direction, managing the financial portfolio, and identifying and mitigating risk across the program. Partners closely with Medical, IT, Privacy, Legal, and Compliance leaders to ensure initiatives are sound from every angle, and works directly with business and technical stakeholders to translate project requests into requirements and, ultimately, delivered outcomes. This role directly supports the organization's ability to deliver efficient, high-quality, and safe healthcare through its technology investments.
Responsibilities
Shapes the strategic direction of the Epic and clinical informatics portfolio by developing multi-year roadmaps, evaluating vendor roadmaps for applicability and opportunity, and aligning initiatives to enterprise priorities. Manages budgeting, capital planning, and financial tracking for the program, while proactively identifying project and program risks and engaging the right cross-functional partners to resolve them. Serves as a bridge between business users and technical teams, ensuring requests are well understood, properly scoped, and translated into requirements and deliverables that hold up through implementation. Brings structure and discipline to a fast-moving, matrixed environment through strong documentation, clear governance, and consistent follow-through.
- Develop and maintain strategic roadmaps for the Epic and clinical informatics portfolio, aligning initiatives to enterprise and CI priorities.
- Review vendor (Epic) roadmaps and upcoming features/functionality on an ongoing basis to assess applicability, opportunity, and fit within the current software environment.
- Identify potential project and program risks early, develop mitigation plans, and engage business
. We need to ensure we don't duplicate content. Let's extract sections: About the role: The first paragraph(s) before "Job Profile Summary": "We’re building a world of health around every individual — shaping a more connected, convenient and compassionate health experience. At CVS Health®, you’ll be surrounded by passionate colleagues who care deeply, innovate with purpose, hold ourselves accountable and prioritize safety and quality in everything we do. Join us and be part of something bigger – helping to simplify health care one person, one family and one community at a time." Then there is "Job Profile Summary" which is a heading but we should not repeat job title as heading; but we can treat that as part of About the role? Actually "Job Profile Summary" is a section heading but we are told to use
for section headings like About the role, Responsibilities, etc. So we could map "Job Profile Summary" to About the role? But we already have About the role intro. Maybe we should treat "Job Profile Summary" as About the role content. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we can use headings like About the role, Responsibilities, etc. So we can have About the role
and then include the content from Job Profile Summary and the intro paragraph.
Thus About the role content: combine the intro paragraph and the Job Profile Summary paragraph: "The role is focused on strategic planning, financial management, and enterprise alignment for the enterprise Epic (EHR) program and related clinical informatics initiatives. Owns the connection between long-range strategy and day-to-day execution, and building roadmaps, evaluating vendor direction, managing the financial portfolio, and identifying and mitigating risk across the program. Partners closely with Medical, IT, Privacy, Legal, and Compliance leaders to ensure initiatives are sound from every angle, and works directly with business and technical stakeholders to translate project requests into requirements and, ultimately, delivered outcomes. This role directly supports the organization's ability to deliver efficient, high-quality, and safe healthcare through its technology investments."
Also maybe include "A Brief Overview" paragraph? That seems like a summary of responsibilities; but we have a separate Responsibilities section. The "A Brief Overview" could be considered part of About the role or Responsibilities. It says: "Shapes the strategic direction of the Epic and clinical informatics portfolio by developing multi-year roadmaps, evaluating vendor roadmaps for applicability and opportunity, and aligning initiatives to enterprise priorities. Manages budgeting, capital planning, and financial tracking for the program, while proactively identifying project and program risks and engaging the right cross-functional partners to resolve them. Serves as a bridge between business users and technical teams, ensuring requests are well understood, properly scoped, and translated into requirements and deliverables that hold up through implementation. Brings structure and discipline to a fast-moving, matrixed environment through strong documentation, clear governance, and consistent follow-through."
That seems like responsibilities. So we could put that in Responsibilities section as well, but we already have a detailed "What You Will Do" list. To avoid duplication, we could merge the "A Brief Overview" into Responsibilities as prose, and then the bullet list as list. But we must preserve all substantive information; we can include both prose and list.
Thus Responsibilities: include the paragraph from "A Brief Overview" as
, then the bullet list from "What You Will Do" as
- ... each bullet. Now Requirements: Minimum Requirements bullet list: "7–10 years of related experience in healthcare, strategy, finance, or healthcare IT/informatics is required. Experience supporting or working with an Epic (EHR) and/or healthcare delivery settings. Strong analytical, problem-resolution, and interpersonal skills. Demonstrated experience with strategic planning, roadmap development, and portfolio or financial management within a healthcare IT or informatics setting. Experience working on large, cross-functional projects; strong knowledge of clinical applications and the healthcare industry. Demonstrated ability to bridge communication among technical and non-technical project staff and customers. Strong executive presence with experience presenting to and building relationships with senior stakeholders across a large enterprise. Experience participating in budgeting, capital planning, or financial portfolio management." We can put each as
- .
Qualifications: Education Preferred Qualifications: "Bachelor's degree or equivalent relevant experience. Master's degree preferred. Hands-on Epic experience Experience with JIRA, Confluence, or similar project and intake management tools. Experience with vendor contracting, procurement, or cost accounting in a healthcare or enterprise IT setting."
We could split into Education and Skills? But we have a Skills section maybe for skills like analytical, problem-resolution, interpersonal, etc. However those are already in Requirements. Could create a Skills section for those soft skills. But we already have them in Requirements; we could keep them there. The instruction: Use sections like Skills only if posting has real specific content. It does list skills: Strong analytical, problem-resolution, and interpersonal skills; Demonstrated ability to bridge communication; Strong executive presence; etc. Could put them in Skills. But to avoid duplication, we could keep them in Requirements and not have a separate Skills section. However the instruction says we can use Skills section; but we must not create thin sections. If we put skills in Requirements, that's fine.
Thus we have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
Now Benefits: The paragraph under "Great Benefits For Great People": "We take pride in offering a comprehensive and competitive mix of pay and benefits that reflects our commitment to our colleagues and their families. This full‑time position is eligible for a comprehensive benefits package designed to support the physical, emotional, and financial well‑being of colleagues and their families. The benefits for this position include medical, dental, and vision coverage, paid time off, retirement savings options, wellness programs, and other resources, based on eligibility. Additional details about available benefits are provided during the application process and on Benefits Moments."
We need to preserve that. Also there is line: "We anticipate the application window for this opening will close on: 10/26/2026" - that's application instruction; we should remove. Also "Qualified applicants with arrest or conviction records will be considered..." remove.
Pay: The paragraph(s) under "Pay Range": "The Typical Pay Range For This Role Is $82,940.00 - $182,549.00 This pay range represents the base hourly rate or base annual full-time salary for all positions in the job grade within which this position falls. The actual base salary offer will depend on a variety of factors including experience, education, geography and other relevant factors. This position is eligible for a CVS Health bonus, commission or short-term incentive program in addition to the base pay range listed above. This position also includes an award target in the company’s equity award program."
We need to preserve all that.
Now we need to output only HTML fragment, no /, no markdown.
We'll structure:
About the role
We’re building a world of health around every individual — shaping a more connected, convenient and compassionate health experience. At CVS Health®, you’ll be surrounded by passionate colleagues who care deeply, innovate with purpose, hold ourselves accountable and prioritize safety and quality in everything we do. Join us and be part of something bigger – helping to simplify health care one person, one family and one community at a time.
The role is focused on strategic planning, financial management, and enterprise alignment for the enterprise Epic (EHR) program and related clinical informatics initiatives. Owns the connection between long-range strategy and day-to-day execution, and building roadmaps, evaluating vendor direction, managing the financial portfolio, and identifying and mitigating risk across the program. Partners closely with Medical, IT, Privacy, Legal, and Compliance leaders to ensure initiatives are sound from every angle, and works directly with business and technical stakeholders to translate project requests into requirements and, ultimately, delivered outcomes. This role directly supports the organization's ability to deliver efficient, high-quality, and safe healthcare through its technology investments.
Responsibilities
Shapes the strategic direction of the Epic and clinical informatics portfolio by developing multi-year roadmaps, evaluating vendor roadmaps for applicability and opportunity, and aligning initiatives to enterprise priorities. Manages budgeting, capital planning, and financial tracking for the program, while proactively identifying project and program risks and engaging the right cross-functional partners to resolve them. Serves as a bridge between business users and technical teams, ensuring requests are well understood, properly scoped, and translated into requirements and deliverables that hold up through implementation. Brings structure and discipline to a fast-moving, matrixed environment through strong documentation, clear governance, and consistent follow-through.
- Develop and maintain strategic roadmaps for the Epic and clinical informatics portfolio, aligning initiatives to enterprise and CI priorities.
- Review vendor (Epic) roadmaps and upcoming features/functionality on an ongoing basis to assess applicability, opportunity, and fit within the current software environment.
- Identify potential project and program risks early, develop mitigation plans, and engage business