Field Access Manager - Diabetes - Minneapolis/Milwaukee

We need to output HTML fragment with sections: About the role? Actually the job description includes a paragraph about EVERSANA then "Job Description". The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: 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. Prefer a few substantive sections over many thin ones. We need to extract substantive content: The posting includes: - Intro about EVERSANA (company description). Could be "About the role"? Actually "About the role" is typical heading for description of role. The posting includes "Job Description" then description of role. So we can have

About the role

with paragraphs describing the role (the Job Description paragraph). Then responsibilities: list of essential duties and responsibilities (multiple bullet points). Then qualifications: Minimum knowledge, skills and abilities (list). Then preferred qualifications (list). Then cultural beliefs (list). Then additional information: includes statements about compensation, benefits, location, EEO, fraud warning, etc. Many of those are boilerplate (EEO, fraud warning, accommodation, etc.) Should be removed. However we need to preserve substantive info: "EVERSANA is committed to providing competitive salaries and benefits for all employees. If this job posting includes a base salary range, it represents the low and high end of the salary range for this position and is not applicable to locations outside of the U.S. Compensation will be determined based on relevant experience, other job-related qualifications/skills, and geographic location (to account for comparative cost of living). This role is eligible for hire in select U.S. locations based on business and operational considerations. For a full list of locations, visit eversana.com/careers. More information about EVERSANA’s benefits package can be found at eversana.com/careers. EVERSANA reserves the right to modify this base salary range and benefits at any time." This includes mention of compensation and benefits but no actual numbers. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does not state actual salary range or benefits specifics, just says competitive salaries and benefits, refer to website. That's likely considered boilerplate/filler. So we should not create Pay/Benefits sections. Also location info: "This role is eligible for hire in select U.S. locations based on business and operational considerations. For a full list of locations, visit eversana.com/careers." That's also generic. Could be considered minor metadata; we could fold into a short

maybe under Additional Information? But we are told to remove boilerplate, duplicated lines, and application instructions. This is somewhat boilerplate but still substantive? It says eligible for hire in select U.S. locations. Might be considered minor metadata; we could include a short paragraph under maybe "Additional Information". However the instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we could include a short

for location eligibility. But we also need to avoid creating sections like Benefits/Pay/Schedule unless actual content. So we can have sections: About the role, Responsibilities, Qualifications (maybe split into Minimum Qualifications and Preferred Qualifications?), Skills? The qualifications already include skills. Could combine Minimum and Preferred under Qualifications with subheadings? But we only allowed headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We cannot add custom headings like "Preferred Qualifications". So we need to fit content into those allowed headings. We could put all qualifications (minimum and preferred) under

Qualifications

. Skills could be separate if we want to pull out skills from qualifications. But we can also just have Qualifications and maybe Skills separate if we want. However we must not create sections with filler. If we put Skills heading but no specific skill list beyond what's already in Qualifications, that might be filler. Better to have Qualifications covering both minimum and preferred, and maybe Skills not needed. We also have "Essential Duties And Responsibilities" which maps to Responsibilities. We have "Additional Information" containing cultural beliefs list, fraud warning, EEO, accommodation, etc. We need to remove boilerplate (EEO, fraud warning, accommodation, etc.) but keep cultural beliefs list? The cultural beliefs list is substantive: "Patient Minded - I act with the patient’s best interest in mind. Client Delight - I own every client experience and its impact on results. Take Action - I am empowered and hold myself accountable. Grow Talent - I own my development and invest in the development of others. Win Together - I passionately connect with anyone, anywhere, anytime to achieve results. Communication Matters - I speak up to create transparent, thoughtful and timely dialogue. Embrace Diversity - I create an environment of awareness and respect." That's a list of beliefs. Could be placed under a section? Not in allowed headings. Could be part of About the role? Or maybe we can put under Qualifications? Not ideal. Could we create a section "Requirements"? Not exactly. The allowed headings include Requirements. Could we put cultural beliefs under Requirements? Not really. Could we put under About the role? The About the role section could include company overview and role description; cultural beliefs maybe not fit. But we could include them as a separate

after Qualifications without a heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid having paragraphs without headings, but likely they expect sections with headings. However we could add a heading "Requirements" and put cultural beliefs there? Not accurate. Better: we could treat cultural beliefs as part of "About the role" or "Qualifications"? Actually they are about company values, not job requirements. Could be placed under About the role as a paragraph describing company culture. That seems acceptable. Thus sections: - About the role: includes company intro (first paragraph about EVERSANA) and role description paragraph (Job Description). Also could include cultural beliefs paragraph. - Responsibilities: list of essential duties and responsibilities (the bullet points after "Essential Duties And Responsibilities"). - Qualifications: includes Minimum Knowledge, Skills and Abilities and Preferred Qualifications. We should not include Skills separate. We need to ensure we preserve all substantive information: The responsibilities list includes many items; we need to keep each as

. The qualifications list includes many items; we need to keep each as

. Also need to keep the "Bachelor’s degree required; Healthcare degree advantageous, including MS, RN, PA, PharmD, or similar advanced healthcare/scientific degree." etc. We need to strip out boilerplate: The "Additional Information" includes cultural beliefs (we keep), fraud warning, EEO, accommodation, etc. We'll remove those. Also need to remove duplicated lines: I see some repeated sentences? Not many. We must not include job title heading. We must not include Pay/Benefits/Schedule sections. Thus final HTML:

About the role

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.

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.

Responsibilities

• 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.

Qualifications

• Bachelor’s degree required; Healthcare degree advantageous, including MS, RN, PA, PharmD, or similar advanced healthcare/scientific degree.