Senior Medical Science Outcomes Liaison - Southern California

We need to output HTML fragment with sections: About the role? Actually the posting includes description about company, mission, location, flexible work, then role description, essential functions, skills, etc. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We need to preserve all substantive info, not invent or summarize away detail. Remove boilerplate etc. We need to decide which sections to include. The posting includes: description of company and mission (maybe "About the role"? Actually "About the role" could be the overview of position. Could also be "Responsibilities" (essential functions). "Qualifications" (basic and preferred). "Skills" (knowledge, skills and competencies). "Benefits" (additional benefits). "Pay" (targeted base salary). "Schedule" maybe not present (flexible work, hybrid). There's mention of flexible, "magnet not mandate" approach, encouraging collaboration and onsite engagement while supporting hybrid flexibility based on role and business needs. That's schedule info. So we can include Schedule section. We must not repeat job title as heading. The job title is "Medical Science Outcomes Liaison (MSOL)". Not to be used as heading. We must not include Job ID etc. We need to output only HTML fragment, no /, no markdown fences. We need to use

for each section heading. Inside sections, use

for prose,

• for lists. We must preserve all substantive information; do not invent or summarize away detail. So we need to include details like location Cambridge, MA, relocation to Waltham later this year, flexible hybrid approach, etc. Also mission statement about CKD, etc. Also essential functions broken into categories: National Account Medical Partnership, Insight Generation and Strategic Medical Support, Rare Kidney Disease Pipeline Readiness, plus another list of Essential Functions And Duties (some duplication). We need to preserve all but avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't say we must deduplicate, but we should not remove substantive info. However duplication may be okay but we could keep both. However we should avoid repeating identical blocks? The posting repeats "Essential Functions And Duties" twice with similar content but slightly different bullet points. We need to keep both? Might be considered duplication but still substantive. Safer to keep both but maybe combine? The instruction says do not summarize away detail; combining could be summarizing. Safer to keep both sections as they appear, but we need to format as lists. We need to decide headings: About the role (overview), Responsibilities (essential functions), Requirements (basic qualifications), Qualifications (preferred qualifications), Skills (knowledge, skills and competencies), Benefits (additional benefits), Pay (targeted base salary), Schedule (flexible hybrid approach). Also maybe "Location" could be part of About the role. We must not create sections with placeholder text like "not specified". All sections we create must have real content. Let's extract content: Company mission paragraph: "Nearly 37 million Americans are currently affected by Chronic Kidney Disease. 37 million. At Akebia we take that number very seriously and every day we come to work, with the purpose of bettering the lives of each person impacted by kidney disease and the renal community that serves them. Our tenacious, passionate employees’ challenge the status quo and work to develop unique therapeutics that have the potential to set new standards of care for people living with kidney disease. This is life-changing work, and we are all in, are you? This position is currently based in our Cambridge, MA office. Please note that our offices will be relocating to Waltham, MA later this year, and this role will transition accordingly. We follow a flexible, “magnet not mandate” approach to in-office work, encouraging collaboration and onsite engagement while supporting hybrid flexibility based on role and business needs." That's about the role/company. Then role description: "The Medical Science Outcomes Liaison (MSOL) is a field-based Medical Affairs professional responsible for providing scientific, clinical, health outcomes, and population health expertise regionally to key stakeholders across dialysis organizations, nephrology large group practices (LGPs), integrated delivery networks (IDNs), and other healthcare organizations involved in the care of patients with chronic kidney disease (CKD). The MSOL serves as a Medical Affairs partner to the market access National Accounts team , and is the primary point of engagement for, and collaboration with National Account Managers (NAMs) to support Akebia's strategic account objectives through compliant scientific exchange and medical engagement. The MSOL develops and maintains relationships with regional healthcare decision makers, population health leaders, medical directors, quality leaders, pharmacy stakeholders, nephrology thought leaders, and executive leadership within nephrology large group practices and regional health systems. Through scientific exchange, the MSOL translates clinical evidence, health economics and outcomes research (HEOR), real-world evidence (RWE), epidemiologic data, and healthcare quality metrics into relevant discussions that support evidence-based decision making and population health initiatives. The MSOL identifies and communicates emerging trends, evidence gaps, customer insights, and unmet medical needs that inform Medical Affairs, Market Access, Clinical Development, and National Account strategies. In addition to supporting Akebia's commercial portfolio, the MSOL develops strategic scientific relationships with nephrology centers of excellence and key kidney disease experts to support future pipeline readiness initiatives, including rare kidney disease programs. The MSOL operates as a trusted scientific partner within the healthcare ecosystem while maintaining the independence, objectivity, and compliance standards expected of Medical Affairs." Then "Essential Functions And Duties" first block (National Account Medical Partnership etc). Then "Insight Generation and Strategic Medical Support" block. Then "Rare Kidney Disease Pipeline Readiness" block. Then second "Essential Functions And Duties" block (similar but slightly different). Then "Skills And Experience" with Basic Qualifications and Preferred Qualifications. Then "Knowledge, Skills And Competencies" block. Then "Base Compensation..." paragraph with base pay range. Then "Additional benefits include health care, vision, dental, retirement, PTO, etc." Then "Targeted Base Salary: $174,680 USD - $215,781 USD". Then "Are you an Akebian? ..." which is fluff but maybe we can include as part of About the role? It's about culture; could be included but not required. It's substantive? It's describing Akebian values. Could be included in About the role or maybe a separate section like "Culture". But we only have allowed headings list; we could put it under About the role as prose. We must not include application instructions, cookie/navigation/legal/EEO etc. The posting ends with "Are you an Akebian? ..." and then cut off. That's not boilerplate; it's cultural description. We'll include. Now we need to format. We'll create sections:

  About the role

  ... (company mission, location, flexible work)

  Responsibilities

  We could combine the role description and essential functions into responsibilities. But we have separate essential functions blocks. Could list them as
  • ... each bullet. However the essential functions blocks have headings inside (National Account Medical Partnership, Insight Generation..., Rare Kidney Disease Pipeline Readiness). Those are subheadings but we are only allowed to use

    for section headings; we could still use

    inside? The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but to be safe we can treat those as or just keep as prose. But we need to preserve the content; we can keep them as

    with bold headings. Simplify: For Responsibilities, we can output a

    with each duty as
    • . But the duties are many sentences; we could break them into separate
    • items. However we must preserve all detail; breaking into list items is okay as long as we don't lose info. We have two Essential Functions And Duties blocks; we could combine them into one list, but that may lose the grouping. Safer to keep them as separate
      under Responsibilities, each preceded by a

      heading like National Account Medical Partnership. But we cannot use other headings? Might be okay but risk. Perhaps we can keep them as

      paragraphs preserving the original headings as plain text. Given the instruction to prefer few substantive sections over many thin ones, we could have just one Responsibilities section containing all the essential functions as paragraphs. Thus:

      Responsibilities

      The Medical Science Outcomes Liaison (MSOL) is a field-based Medical Affairs professional responsible for providing scientific, clinical, health outcomes, and population health expertise regionally to key stakeholders across dialysis organizations, nephrology large group practices (LGPs), integrated delivery networks (IDNs), and other healthcare organizations involved in the care of patients with chronic kidney disease (CKD). ... (continue with the role description paragraph).

      National Account Medical Partnership

      • Serve as the designated Medical Affairs partner for assigned National Account Managers and regional strategic dialysis, nephrology, and health system accounts.
      • Collaborate with NAMs on account planning activities by providing scientific, clinical, outcomes, and healthcare ecosystem expertise.
      • Develop and execute Medical Account Plans (MAPs) aligned with Medical Affairs priorities and strategic account objectives.
      • Participate in account reviews and cross-functional planning discussions to identify scientific opportunities and customer needs.
      • Provide scientific support for strategic initiatives focused on improving clinical outcomes, quality metrics, patient experience, care delivery, and population health performance.
      • Facilitate evidence-based discussions with dialysis organizations, nephrology large group practices, integrated delivery networks, and other organized healthcare customers.
      • Establish and maintain scientific relationships with medical directors, chief medical officers, quality leaders, pharmacy leaders, population health executives, and nephrology clinical leadership.
      • Conduct scientific exchange with stakeholders responsible for clinical policy, treatment pathways, quality improvement initiatives, and value-based care programs.
      • Communicate to appropriate audiences clinical, HEOR, and real-world evidence related to CKD, dialysis-dependent CKD, anemia management, healthcare resource utilization, and patient outcomes.
      • Support scientific discussions involving quality measures, hospitalization reduction, treatment optimization, patient-centered outcomes, and health equity initiatives.

      Insight Generation and Strategic Medical Support

      • Gather and communicate actionable customer insights regarding disease management, treatment pathways, healthcare delivery trends, population health priorities, and unmet medical needs.
      • Identify evidence gaps and opportunities for future outcomes research, real-world evidence generation, and scientific collaboration.
      • Provide medical and scientific insights that support Medical Affairs, HEOR, National Accounts, Clinical Development, and Market Access strategies.
      • Support scientific advisory boards, medical education initiatives, and evidence dissemination activities.

      Rare Kidney Disease Pipeline Readiness

      • Develop and maintain scientific relationships with academic nephrology centers, kidney disease centers of excellence, and rare disease investigators.
      • Identify emerging scientific leaders, referral networks, and key stakeholders within rare kidney disease communities.
      • Provide field-based insights regarding diagnostic pathways, referral patterns, unmet needs, and evolving standards of care.
      • Support future Medical Affairs planning and launch readiness activities for pipeline assets.

      Essential Functions And Duties

      • Serve as the medical lead for assigned dialysis organizations, nephrology large group practices, integrated delivery networks, and other organized healthcare customers.
      • Develop and maintain credible scientific relationships with medical, pharmacy, quality,