Health Economics Solutions Manager - East
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). 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.
We have Pay info: "Along with a competitive salary, this role is eligible for an annual bonus & car reimbursement. The posted salary range includes multiple geographic locations. Final compensation will be determined based on location, experience, and internal equity, and aligned with local market ranges". That's specific enough for Pay section.
Benefits: we have detailed benefits description. So Benefits section.
Schedule: we have travel up to 50% domestic travel, location field-based, proximity to major airport required. That's not exactly schedule but could be considered Schedule (travel expectations). The instruction says include Schedule only if posting actually states them. It does state travel expectations. So we can include Schedule.
Skills: we could extract abilities like "Ability to analyze healthcare data and translate it into clear, compelling value narratives", "Comfortable leading through influence and collaborating across multiple internal teams", "Strong understanding of value‑based care frameworks, CMS regulations, and acute/post‑acute healthcare environments", "Experience engaging hospital and system‑level stakeholders". Those could be skills. We'll include Skills section.
Qualifications: we have Required Qualifications and Strongly Preferred. Could combine into Qualifications section with two sublists? But we need to use - for any list. We could have separate sections: Requirements (maybe required qualifications) and Qualifications (preferred). Or we could have Requirements for required, Qualifications for preferred. The instruction list includes both Requirements and Qualifications as possible headings. We'll use Requirements for required qualifications, Qualifications for strongly preferred.
About the role: we have introductory paragraphs.
Responsibilities: we have "What You’ll Do".
Now we need to output HTML fragment only, no extra markup.
We'll structure:
About the role
... paragraphs ...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Skills
- ...
...
Benefits
... paragraphs ...
Pay
... paragraphs ...
Schedule
... paragraphs ...
We must ensure we don't include filler like "commensurate with experience". Not present.
We must preserve all substantive information. Need to include location requirement: "Candidates should reside in Philadelphia, Charlotte, Atlanta, Nashville, New Jersey". Also "Live within territory". Also "proximity to a major airport required". Also "Travel: Up to :50% domestic travel". We'll include those in Schedule or maybe About the role? Probably Schedule.
Let's extract each piece.
About the role: combine first paragraph and maybe The Opportunity and Why This Role? Actually About the role could be the initial description before The Opportunity. We'll include the first paragraph: "As we continue to expand our Strategic Accounts & Health Economics (SAHE) function, we are adding a Health Economics Solutions Manager to help elevate the economic and clinical value of our wound care portfolio. This position is being added to provide dedicated support for key Wound Care Key Account Management (KAM) accounts, Post-Acute DSA accounts, and Government DSA accounts in the Eastern US. By expanding the team, we will strengthen customer coverage across these critical segments, ensuring customers receive the appropriate level of health economics support while maintaining focused partnership and engagement within our DSA account structure."
We could also include The Opportunity and Why This Role as part of About the role? But we have separate sections for Responsibilities etc. The Opportunity and Why This Role could be part of About the role as well. However we need to avoid duplication. Let's decide: About the role: include the first paragraph plus The Opportunity and Why This Role? Might be too much but okay.
But we have Responsibilities separate (What You’ll Do). So we can keep About the role as the initial description plus The Opportunity and Why This Role (the bullet points). However the bullet points under Why This Role are more like motivations; could be part of About the role. We'll include them as maybe.
Let's parse:
The Opportunity paragraph: "The Health Economics Solutions Manager (HESM) serves as a strategic, customer‑facing partner to hospitals and integrated delivery networks, engaging at both the facility and system level. This role blends health economics expertise, real‑world evidence generation, and executive‑level storytelling to help customers achieve measurable improvements in outcomes, quality metrics, and financial performance. This is not an entry‑level health economics role. We are seeking a professional with real‑world healthcare experience who can collaborate cross‑functionally, lead without authority, and credibly engage mid‑ to senior‑level stakeholders (including C‑suite and service line leadership)."
Why This Role bullet points: list.
We could put those under About the role as paragraphs.
Now Responsibilities: What You’ll Do bullet list.
Requirements: Required Qualifications bullet list.
Qualifications: Strongly Preferred bullet list.
Skills: maybe we can extract abilities like "Ability to analyze healthcare data and translate it into clear, compelling value narratives", "Comfortable leading through influence and collaborating across multiple internal teams", "Strong understanding of value‑based care frameworks, CMS regulations, and acute/post‑acute healthcare environments", "Experience engaging hospital and system‑level stakeholders on outcomes, economics, reimbursement, or quality initiatives". Those are already in Requirements though. But we can still have Skills separate: maybe "Ability to analyze healthcare data and translate it into clear, compelling value narratives", "Comfortable leading through influence and collaborating across multiple internal teams", "Strong understanding of value‑based care frameworks, CMS regulations, and acute/post‑acute healthcare environments", "Experience engaging hospital and system‑level stakeholders on outcomes, economics, reimbursement, or quality initiatives". However that duplicates Requirements. Might be okay but we could instead list skills like "Strategic storytelling", "Real‑world evidence generation", "Executive‑level communication", "Cross‑functional collaboration", "Influence without authority". But we need to stick to posting content. Let's extract from The Opportunity
About the role
... paragraphs ...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Skills
- ... ...
Benefits
... paragraphs ...
Pay
... paragraphs ...
Schedule
... paragraphs ...
We must ensure we don't include filler like "commensurate with experience". Not present. We must preserve all substantive information. Need to include location requirement: "Candidates should reside in Philadelphia, Charlotte, Atlanta, Nashville, New Jersey". Also "Live within territory". Also "proximity to a major airport required". Also "Travel: Up to :50% domestic travel". We'll include those in Schedule or maybe About the role? Probably Schedule. Let's extract each piece. About the role: combine first paragraph and maybe The Opportunity and Why This Role? Actually About the role could be the initial description before The Opportunity. We'll include the first paragraph: "As we continue to expand our Strategic Accounts & Health Economics (SAHE) function, we are adding a Health Economics Solutions Manager to help elevate the economic and clinical value of our wound care portfolio. This position is being added to provide dedicated support for key Wound Care Key Account Management (KAM) accounts, Post-Acute DSA accounts, and Government DSA accounts in the Eastern US. By expanding the team, we will strengthen customer coverage across these critical segments, ensuring customers receive the appropriate level of health economics support while maintaining focused partnership and engagement within our DSA account structure." We could also include The Opportunity and Why This Role as part of About the role? But we have separate sections for Responsibilities etc. The Opportunity and Why This Role could be part of About the role as well. However we need to avoid duplication. Let's decide: About the role: include the first paragraph plus The Opportunity and Why This Role? Might be too much but okay. But we have Responsibilities separate (What You’ll Do). So we can keep About the role as the initial description plus The Opportunity and Why This Role (the bullet points). However the bullet points under Why This Role are more like motivations; could be part of About the role. We'll include them asmaybe. Let's parse: The Opportunity paragraph: "The Health Economics Solutions Manager (HESM) serves as a strategic, customer‑facing partner to hospitals and integrated delivery networks, engaging at both the facility and system level. This role blends health economics expertise, real‑world evidence generation, and executive‑level storytelling to help customers achieve measurable improvements in outcomes, quality metrics, and financial performance. This is not an entry‑level health economics role. We are seeking a professional with real‑world healthcare experience who can collaborate cross‑functionally, lead without authority, and credibly engage mid‑ to senior‑level stakeholders (including C‑suite and service line leadership)." Why This Role bullet points: list. We could put those under About the role as paragraphs. Now Responsibilities: What You’ll Do bullet list. Requirements: Required Qualifications bullet list. Qualifications: Strongly Preferred bullet list. Skills: maybe we can extract abilities like "Ability to analyze healthcare data and translate it into clear, compelling value narratives", "Comfortable leading through influence and collaborating across multiple internal teams", "Strong understanding of value‑based care frameworks, CMS regulations, and acute/post‑acute healthcare environments", "Experience engaging hospital and system‑level stakeholders on outcomes, economics, reimbursement, or quality initiatives". Those are already in Requirements though. But we can still have Skills separate: maybe "Ability to analyze healthcare data and translate it into clear, compelling value narratives", "Comfortable leading through influence and collaborating across multiple internal teams", "Strong understanding of value‑based care frameworks, CMS regulations, and acute/post‑acute healthcare environments", "Experience engaging hospital and system‑level stakeholders on outcomes, economics, reimbursement, or quality initiatives". However that duplicates Requirements. Might be okay but we could instead list skills like "Strategic storytelling", "Real‑world evidence generation", "Executive‑level communication", "Cross‑functional collaboration", "Influence without authority". But we need to stick to posting content. Let's extract from The Opportunity