Field Access Manager - Diabetes - Kansas City/St. Louis

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Remove boilerplate, navigation, EEO, etc. Keep substantive info. We need to parse the posting. Company Description: It's about EVERSANA. Could be "About the role"? Actually "Company Description" is about the company, not role. The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have "Job Description" paragraph describing role. That could be "About the role". Then "Essential Duties And Responsibilities" list -> Responsibilities. Then "Qualifications" section includes MINIMUM KNOWLEDGE, SKILLS AND ABILITIES: list of requirements. That could be Requirements and Qualifications? Actually they separate Requirements and Qualifications maybe. We can treat "Qualifications" heading for the list of qualifications (both minimum and preferred). The "Additional Information" includes cultural beliefs, fraud warning, benefits statement, etc. Some of that is boilerplate (EEO, fraud warning) to remove. But there is mention of benefits: "EVERSANA is committed to providing competitive salaries and benefits for all employees." and "More information about EVERSANA’s benefits package can be found at eversana.com/careers." Also mention of salary range: "If this job posting includes a base salary range, it represents the low and high end of the salary range for this position...". However no actual numbers given. So we cannot create Pay section because no specific numbers. Benefits: they mention benefits package but no specifics. According to rule: never create Benefits section unless posting actually states them. It states they provide competitive salaries and benefits, but not specifics. Likely we should not create Benefits section because no concrete benefits listed. Similarly Pay: no specific range, so omit. Schedule: not mentioned. Skills: we could extract skills from qualifications: strong analytical skills, knowledge of CMS, specialty markets, Veeva systems, Microsoft applications, ability to conduct presentations, etc. Could be a Skills section. Requirements: maybe the minimum qualifications (education, years experience). Qualifications: maybe preferred qualifications. We need to avoid duplication. Let's decide: - About the role: paragraph from Job Description. - Responsibilities: list from Essential Duties And Responsibilities (each sentence as

). - Requirements: Minimum Knowledge, Skills and Abilites (the bullet list). Could be formatted as

• each requirement. - Qualifications: Preferred Qualifications list. - Skills: maybe combine some skill statements from both? But we might already have skills in Requirements and Qualifications. Could create a Skills section highlighting specific skills: strong analytical skills, knowledge of CMS, specialty markets, Veeva, Microsoft Teams, ability to manage multiple priorities, organizational/problem-solving, cross-functional work, impactful educational presentations. However these are already in Requirements. To avoid duplication, maybe we don't create separate Skills section unless we have distinct skill statements not covered elsewhere. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one "Qualifications" section, and have Responsibilities and About the role. But they asked to use headings for those specific names if content exists. We can decide to have About the role, Responsibilities, Qualifications (covering both minimum and preferred). That's three sections. Check if any content for Benefits, Pay, Schedule: none specific, so omit. Thus output:

  About the role

  ... (the Job Description paragraph)

  Responsibilities

  • ... each duty
  ...

  Qualifications

  Minimum Knowledge, Skills and Abilities:

  ... minimum requirements

  Preferred Qualifications:

  ... preferred
  But we need to use

  for prose,

  • for lists. Could also embed headings inside Qualifications? Not needed. We must preserve all substantive information, not invent or summarize away detail. Must not omit any substantive info. So we need to include all duties, all minimum requirements, all preferred qualifications, and the company description? The company description is about EVERSANA; is that substantive? It's about the company, not role. The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It didn't list Company Description as a heading. But we could include it as a

    before headings? The instruction says output only HTML fragment, no /. It didn't forbid other paragraphs not under headings. We could include a brief intro paragraph about company description as a

    before sections. That would preserve info. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to strip the fraud warning, EEO, cultural beliefs? The cultural beliefs list maybe considered substantive? It's part of company culture; but it's maybe boilerplate? It's not a standard EEO but it's cultural beliefs. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. Cultural beliefs might be okay to keep? It's not explicitly prohibited. However it's somewhat generic. Might be considered boilerplate? Safer to remove it? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Cultural beliefs not listed, so we can keep. But the later part includes "Our team is aware of recent fraudulent job offers..." that's scam-warning, must remove. Also the EEO statement at end must remove. Also the "Follow us on LinkedIn | Twitter" is navigation/social, remove. Thus we keep: Company Description paragraph(s), Job Description paragraph, Essential Duties And Responsibilities list, Qualifications (minimum and preferred), maybe Cultural beliefs? But we need to see if cultural beliefs are duplicated elsewhere? Not. We'll keep cultural beliefs as a

    maybe under a heading? Not a defined heading. Could just put as a

    after Qualifications before closing. But we should avoid creating extra sections not requested. It's okay to have stray

    elements. Let's extract content. Company Description: "At EVERSANA, we are proud to be certified as a Great Place to Work across the globe. We’re fueled by our vision to create a healthier world. How? Our global team of more than 7,000 employees is committed to creating and delivering next-generation commercialization services to the life sciences industry. We are grounded in our cultural beliefs and serve more than 650 clients ranging from innovative biotech start-ups to established pharmaceutical companies. Our products, services and solutions help bring innovative therapies to the market and support the patients who depend on them. Our jobs, skills and talents are unique, but together we make an impact every day. Join us! Across our growing organization, we embrace diversity in backgrounds and experiences. Improving patient lives around the world is a priority, and we need people from all backgrounds and swaths of life to help build the future of the healthcare and the life sciences industry. We believe our people make all the difference in cultivating an inclusive culture that embraces our cultural beliefs. We are deliberate and self-reflective about the kind of team and culture we are building. We look for team members that are not only strong in their own aptitudes but also who care deeply about EVERSANA, our people, clients and most importantly, the patients we serve. We are EVERSANA." That's a lot. We'll keep as

    . Job Description paragraph: "The Field Access Manager (FAM) will act as the main point of contact at designated accounts providing account management support to Healthcare Professionals (HCPs) and their staff on behalf of patients who are prescribed a product for approved indications. As a part of this strategy, the FAM will provide on-going education to accounts regarding the Patient Services program, the regional payer landscape, and pharmacy channel access. The FAM will help coordinate pull-through efforts for patients who have been prescribed the product, irrespective of channel (HUB, specialty pharmacy, etc.), provided proper HIPAA consent has been secured from the patient. The FAM will be expected to be the primary face of the Patient Services platforms within designated HCP offices. The FAM is also responsible for partnering with internal and external stakeholders to optimize access to the product for patients." That's the prose. Responsibilities list: each sentence after "Essential Duties And Responsibilities". Let's extract: - Expand advocacy within HCP offices and equip the staff, through education, to navigate the access and payer approval process, identify access barriers that the HCP must act on to overcome, and highlight HCP actions that support patient access to therapy. - Offer educational resources to support the entire patient’s journey by optimizing processes for prior authorizations/appeals/specialty pharmacy and addressing access issues. - Coordinate utilization of the patient service platform to seamlessly support the customer and patient when office chooses the HUB or SP as their ideal path to approved therapy. - Coordinate annual pharmacy reauthorizations at designated accounts to ensure timely reauthorization and continuation of therapy is maintained. - Work cross functionally and collaboratively with partners in Sales, Market Access, Patient Services, Strategic Accounts and more to act as a process and payer expert. The FAM will help identify and address time sensitive market development and implementation efforts to remove access barriers to the product for appropriate patients, while optimizing adherence. - Build and execute a strategic business plan to meet the needs of top accounts and ensure successful implementation of market access initiatives. - Obtain and maintain knowledge and understanding of payer landscape, including specialty pharmacy and utilization management criteria, on a national, regional and local level so that you can act as a process and payer expert. - Continuously strive to understand the alignment of Payer/PBM/SP and how national/regional pharmacy drug formularies impact market access in their designated geography. - Assist in providing appropriate field insights to ensure support of all access and patient/payer support programs and resources offered by the company’s Patient Support Programs. - Anticipate, navigate and address individual account and patient access issues that arise by partnering with all appropriate stakeholders. - Demonstrate a commitment to diversity, equity, and inclusion through continuous development, modeling inclusive behaviors, and proactively managing bias. - All other duties as assigned. We'll make each a

    . Qualifications: Minimum Knowledge, Skills and Abilities list: - Bachelor’s degree required; Healthcare degree advantageous, including MS, RN, PA, PharmD, or similar advanced healthcare/scientific degree. - 10+ years in pharmaceutical industry with experience in payer policy and patient access. - 5+ years of experience in benefit verifications and/or prior-authorization requirements or equivalent experience in patient access. - Knowledge of Centers of Medicare & Medicaid Services (CMS) policies and processes with experience in Medicare Parts B & D. - Knowledge and understanding of specialty markets, HUB/reimbursement services and patient access programs. - Strong understanding of specialty product access/reimbursement processes including Patient Support Services programs. - Strong analytical skills to assess market dynamics, competitor activity, and continuous diabetes monitoring trends. Ability to gather and interpret data to guide regional strategy, including understanding the role of HUB and patient claims data. - Knowledge of Integrated Delivery Network/Integrated Health Systems. - Strong understanding of Microsoft applications and the ability to conduct virtual engagements via Microsoft Teams. - Ability to manage multiple priorities with excellent organizational and problem-solving skills with a high level of initiative and independence. - Proven success in working in a cross functional environment. - Ability to conduct impactful educational presentations. - Strong knowledge of Veeva systems. Preferred Qualifications: - Bachelor’s degree required; Advanced Degree preferred. - Pediatric Endocrinology and/or Endocrinology experience preferred. - Previous launch experience in Access/Reimbursement role - Previous experience in other functions within