Medical Director - Heart Failure - US Central / West

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to parse the job posting: It includes "About Us" (company description). Not required heading? Could be "About the role"? Actually "About Us" is company description, not role. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these headings if present. We have sections: "Job Purpose" (maybe "About the role"?). "Job Responsibilities" (Responsibilities). "Education" (Education & Professional Background) could be Qualifications or Requirements. "Required Experience and Capabilities" (Experience). "Additional Preferred Experience". "Success Profile". "Competencies". "Flexibility". "Additional Information". Also "Policies, Procedures & Compliance". Also "GCP Requirement". Also "Travel". Also "Budgetary responsibilities". Also "Additional Information" includes travel, budget, etc. We need to decide which headings to include: About the role (Job Purpose). Responsibilities (Job Responsibilities). Requirements (Education & Professional Background, Required Experience and Capabilities, GCP Requirement maybe). Qualifications (maybe same as Requirements). Skills (Competencies). Benefits (none explicit). Pay (none). Schedule (none). So we will include About the role, Responsibilities, Requirements, Qualifications, Skills maybe. But we must avoid duplication. Could combine Education & Experience into Requirements. Qualifications maybe same as Requirements; but we can include both if distinct content. However instruction: Prefer a few substantive sections over many thin ones. So we can combine. Thus sections:

About the role

with Job Purpose paragraph.

Responsibilities

with two pillars content.

Requirements

with Education & Professional Background, Required Experience and Capabilities, GCP Requirement.

Skills

with Competencies (Attitude and Demeanor list) maybe also Success Profile? Could include Success Profile as part of Skills or separate? But we can include Skills. We should not include Benefits, Pay, Schedule as no specific content. We must preserve all substantive information, not invent or summarize away detail. Must not omit details. Must include all content from those sections. We need to format lists with

• for any list of duties/requirements/benefits. For prose use

  . We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. At end there is EEO statement; we must remove that. Also "All job requirements listed indicate the minimum level..." etc maybe considered boilerplate? It's generic but maybe part of job description; but it's not specific to role? It's a standard disclaimer; could be considered boilerplate. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The EEO statement is definitely to remove. The "All job requirements listed indicate the minimum level..." maybe not EEO but still generic; but it's not explicitly listed to remove. However it's a generic statement that could be considered boilerplate but not in list. Safer to keep? Might be considered part of job description; but it's not specific to role. I'd keep it as part of Requirements maybe? But it's a statement about job requirements; could be kept as prose. Also "To learn more visit www.pharmacosmos.us" is maybe application instruction? It's a link to learn more; could be considered application instruction? Probably remove as it's not substantive about role. The instruction: remove application instructions. So remove that line. Also "Requires budgetary responsibilities and discretion with confidential data Travelling – approximately 65% of the time" is substantive; keep. Now we need to extract content. Let's parse sections: About Us: company description. Not needed for role? Could be considered "About the role"? Actually "About Us" is company overview; not role. The instruction says use headings like About the role, Responsibilities, etc. So we may not include About Us. The job purpose is separate. Thus About the role: Job Purpose paragraph. Let's copy Job Purpose text exactly: "This role offers the opportunity to help shape Pharmacosmos’ future presence in heart failure while supporting one of the company’s most important clinical development programs. The role sits at the interface of Clinical Development and Medical Affairs and has two complementary objectives Support successful execution and patient recruitment of the ICONIC-HF trial in the United States through investigator engagement, site support, insight generation, and identification of barriers to study execution. Build the scientific, stakeholder, and market foundation for future IV iron adoption in heart failure, including KOL engagement, strategic insight generation, advocacy development, launch readiness, and future medical-marketing support. The relative emphasis of the role is expected to evolve over time. During active execution of ICONIC-HF, the primary focus will be investigator engagement, site support, and insight generation related to trial execution. As the program matures, the center of gravity is expected to shift progressively toward heart failure market understanding, advocacy development, launch readiness, and broader medical affairs support for the future heart failure franchise. The successful candidate will work closely with both the US affiliate and global headquarters in Denmark and will have regular interaction with cross-functional leadership teams across Clinical Development, Medical Affairs, Strategy and Operations, and Market Access. The role is intended for an individual who enjoys combining scientific engagement, strategic thinking, and execution in a highly collaborative global environment." Note there is missing punctuation after "objectives". We'll keep as is. Now Responsibilities: The responsibilities are structured in two complementary pillars Boundaries of the Role Trial Support ICONIC-HF Site Engagement and Enrollment Enablement ... then list of bullet-like sentences. Then second pillar: Strategic Heart Failure Insights, Advocacy Development and Launch Readiness ... then list. We need to format as

  • for any list of duties/requirements/benefits. So we need to turn each sentence into
  • . However some sentences are long and contain multiple clauses; but we can keep each sentence as a list item. We must preserve all substantive information; not invent or summarize away detail. So we need to include each bullet. Let's extract first pillar bullet points: - Establish and maintain strong scientific relationships with investigators, study coordinators, and other site personnel involved in ICONIC-HF. - Conduct regular site engagements, virtually and in person where relevant, to understand local opportunities, challenges, operational barriers and operate within compliance, GCP, and trial governance frameworks. - Serve as a US-based scientific liaison between participating sites and the HQ R&D ICONIC-HF trial team in coordination with the US affiliate and the contracted CRO. - Identify, understand, and communicate barriers that may impact screening, enrollment, site engagement, or study execution, analyze potential root causes, and help defining mitigations activities with HQ R&D ICONIC-HF trial team and the CRO. - Facilitate appropriate cross-functional problem solving and escalation pathways when barriers are identified. - Support protocol understanding and scientific discussions within approved governance frameworks. - Gather and communicate investigator insights, competitive intelligence, protocol feedback, and study-related observations to internal stakeholders. - Organize and facilitate regional sponsor-investigator touchpoint meetings as appropriate. - Identify and share best practices from successful sites to support broader site engagement efforts, where appropriate and compliant. - Support site activation and engagement initiatives in partnership with HQ R&D ICONIC-HF trial team and the CRO. - Maintain a strong understanding of site experiences and investigator perspectives throughout the study lifecycle. - Does not function as a CRA. - Does not perform monitoring activities. - Does not conduct source data verification. - Does not own enrollment metrics or site performance targets. - Does not manage day-to-day clinical trial operations. These responsibilities remain with HQ Clinical Operations and the CRO. Note the last bullet includes a sentence after period; we can keep as one
  • . Now second pillar bullet points: - Develop a deep understanding of the evolving US heart failure landscape, including treatment pathways, referral patterns, unmet needs, evidence gaps, barriers to adoption, and emerging trends relevant to IV iron. - Map, prioritize, and engage regional and national heart failure thought leaders. - Build and maintain scientific relationships with key experts beyond the ICONIC-HF investigator network. - Generate actionable insights that can support future evidence generation, publication planning, congress activities, scientific communication, advisory board strategy, and launch readiness. - Partner closely with HQ and the US affiliate to ensure field insights are translated into strategic recommendations. - Support identification and prioritization of investigator-sponsored research opportunities. - Contribute to long-term medical affairs strategy and launch-readiness planning for IV iron in heart failure. - Support future launch-readiness initiatives through close partnership with Medical Affairs, Strategy and Operations, Market Access, and Commercial colleagues while maintaining full compliance with applicable governance requirements. Now also there is a section "Policies, Procedures & Compliance" after responsibilities. Should we include that? It's not a standard heading but could be part of Requirements or maybe separate. The instruction only lists certain headings; but we can include other headings if they have substantive content? It says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. However we should probably map Policies, Procedures & Compliance into Requirements or maybe a separate section like Compliance. But to keep few sections, we can include under Requirements as a bullet. Also "Education" section: "Education & Professional Background Advanced scientific or healthcare degree preferred, e.g., MD, PharmD, PhD, NP, PA, MSc, or equivalent." Then "Required Experience and Capabilities" list: - Experience within cardiology is required; heart failure experience is preferred. - Experience from clinical development, research and/or Medical Affairs. - Demonstrated understanding of clinical trial conduct and investigator engagement. - Experience collaborating with investigators, academic institutions, and cross-functional internal stakeholders. - Ability to work effectively within cross-functional and matrix organizations. - Strong scientific communication, relationship-building, and stakeholder-management skills. - Ability to translate external insights into actionable recommendations for internal stakeholders. Then "GCP Requirement Basic GCP training or certification is preferred. Training can be provided for an otherwise qualified candidate." Then "Additional Preferred Experience" list: - Heart failure expertise. - Cardiovascular outcomes trial experience. - Launch or pre-launch experience. - Experience engaging US-based KOLs and national thought leaders. - Experience working across both clinical development and medical affairs environments. - Established KOL network within heart failure/cardiology. Then "Success Profile" paragraph. Then "Competencies" list: - Attitude and Demeanor Proud Pharmacosmos ambassador Strong personal leadership Inspire cross-functional transparency and collaboration Customer-centric ‘can-do’ attitude and goal focused Ambitious, independent, analytical, collaborative, loyal, organized Exemplifies Medical Affairs TRAC (Trust, Respect, Accountability, Collaboration) values Actually the list seems to be a paragraph with multiple traits separated by spaces. We need to parse into list items? The instruction: Use

    • for any list of duties/requirements/benefits. This is a list of competencies; we can treat each trait as
    • . However the text is not separated by line breaks; it's a sentence. We could split by commas? But better to keep as a paragraph? The instruction says use list for any list of duties/requirements/benefits. Competencies is a list of traits; we could make a list. But we need to preserve all substantive information; we can convert to list items by splitting on commas and "and". However that may be risky. Perhaps we keep as a paragraph

      and not list. The instruction says use list for any list of duties/requirements/benefits. Competencies is not duties/requirements/benef