Medical Director - Heart Failure - US Central / West

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content. We need to extract content. The posting includes: - About Us (company description) – but we are told not to repeat job title as heading; we can have About the role? Actually "About Us" is company description. 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 "Job Purpose" which is like About the role. So we can put that under

About the role

. We have "Job Responsibilities" with two pillars and details. That's Responsibilities. We have "Education & Professional Background", "Required Experience and Capabilities", "GCP Requirement", "Additional Preferred Experience", "Success Profile", "Competencies", "Attitude and Demeanor", "Flexibility", "Additional Information". These could map to Requirements, Qualifications, Skills. We need to decide. We have no explicit Pay, Benefits, Schedule. There's mention "Travelling – approximately 65% of the time" – that's schedule? It's travel requirement, not schedule. No explicit pay or benefits. So we should not include Pay, Benefits, Schedule sections because no real specific content. We need to preserve all substantive information, not invent or summarize away detail. So we need to include all details from the posting under appropriate sections. We must not include boilerplate like EEO etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is EEO statement; we should drop that. Also drop "All job requirements listed indicate the minimum level..." etc? That's generic but maybe considered boilerplate? It's part of job description but not specific? It says "All job requirements listed indicate the minimum level...". That's somewhat boilerplate but still part of description. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. That line is not exactly those categories, but it's a generic statement. Might be considered boilerplate? It's not EEO. It's a standard disclaimer. Might be okay to keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. That line is substantive? It's a generic statement about requirements. Might be considered boilerplate but not explicitly listed to remove. Safer to keep? However they said "Prefer a few substantive sections over many thin ones." Might be okay to include under Requirements. We also need to drop duplicated lines. Not seeing duplicates. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

Job Purpose ... (the paragraph)

Responsibilities

• ... each bullet? The responsibilities are long paragraphs; we could break into
• items for each duty. The instruction: Use
  • for any list of duties/requirements/benefits. So we need to convert responsibilities into list items. The responsibilities are structured in two pillars with many sentences. We can split each sentence or each bullet-like item into
  • . Must preserve all info. Similarly for Requirements/Qualifications/Skills: we need to list items. We need to decide which sections to create: About the role, Responsibilities, Requirements (maybe combine Required Experience and Capabilities, Education, GCP, Additional Preferred Experience), Qualifications (maybe Success Profile?), Skills (Competencies, Attitude and Demeanor, Flexibility, Additional Information). But we must not create thin sections; prefer few substantive sections. Could combine all into Requirements and Responsibilities only? But we have headings list; we can choose to include only those with real content. The posting has content for About the role, Responsibilities, Requirements (education, experience, GCP, preferred experience), Qualifications (maybe success profile), Skills (competencies, attitude, flexibility, additional info). Could be many sections. But we can merge some: For example, we could have Requirements (education, experience, GCP, preferred experience) and Skills (competencies, attitude, flexibility, additional info). Qualifications maybe not needed if we treat success profile as part of Requirements or Skills. However the instruction says use those headings if content exists. We have content for Success Profile; we could put under Qualifications. We need to avoid filler like "commensurate with experience". Not present. Thus produce sections:

    About the role

    Job Purpose ... (the paragraph)

    Responsibilities

    • 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.
    • 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.
    • Stay current and in compliance both individually and as a department to align with industry best practices. This includes all Corporate Policies as well as mandated government Regulations. Ensure adherence to all relevant laws, regulations, and guidelines related to pharmaceutical operations, including FDA, EMA, and other global health authority regulations.
    • Stay current with and adhere to all policies and procedures as outlined in the employee handbook.

    Requirements

    • Education & Professional Background: Advanced scientific or healthcare degree preferred, e.g., MD, PharmD, PhD, NP, PA, MSc, or equivalent.
    • Required Experience and Capabilities: 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.
    • GCP Requirement: Basic GCP training or certification is preferred. Training can be provided for an otherwise qualified candidate.
    • Additional Preferred Experience: 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.

    Qualifications

    • Success Profile: The ideal candidate combines scientific credibility with strategic thinking and strong interpersonal skills. They are equally comfortable discussing heart failure science with leading investigators, understanding operational challenges that affect study execution, generating insights from the external environment, and translating those insights into recommendations that influence US and global strategy. They enjoy working in a collaborative environment and are motivated by the opportunity to help shape both the successful execution of ICONIC-HF and the future development of a US heart failure franchise. The role should appeal to an individual who values close collaboration with both Pharmacosmos HQ in Denmark and the US affiliate, Pharmacosmos Therapeutics Inc., and who is energized by the opportunity to build a strategically important US heart failure platform from an early stage.

    Skills

    • Competencies: 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.
    • Flexibility: Our roles can evolve over time. Reasonable flexibility is, therefore, a key part of any job at Pharmacosmos. Significant variations in duties and responsibilities should be discussed between the employee and manager.
    • Additional Information: Requires budgetary responsibilities and discretion with confidential data; Travelling – approximately 65% of the time; To learn more visit www.pharmacosmos.us.
    We must not include Pay, Benefits, Schedule. We need to ensure we didn't include any boilerplate like EEO etc. We removed that. Check for duplicated lines: none. Check that we preserved all substantive info: We included About Us? Actually we omitted About Us company description. The posting starts with "About Us ..." which is company description. Should we include that? The instruction: use headings for sections like About the role, Responsibilities, etc. There's no explicit heading for About Us. But we could treat that as part of About the role? The About Us is company overview, not role. The instruction says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid including company description. But we have no heading for company description; we could include it under About the role as a paragraph before Job Purpose? However the About Us is separate from Job Purpose. The instruction says preserve ALL substantive information. So we should include the About Us content somewhere. Where to put? Could be a

    before About the role heading? But we must not add extra headings not listed. We could include it as a

    under About the role