Jobs · Sales

Field Access Manager - Diabetes - Southern California

EVERSANA · San Diego, CA · 1 mo ago
RemoteRemoteSalesFull-time
We need to output HTML fragment with sections: About the role? The posting includes description paragraphs before "Job Description". The "About the role" could be the introductory paragraph about EVERSANA? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We have: - Intro about EVERSANA (company description) maybe "About the role"? Actually "About the role" would be description of the role. The posting includes "Job Description" paragraph describing role: "The Field Access Manager (FAM) will act as the main point of contact..." That's role description. So we can put that under

About the role

with

. - Responsibilities: The "Essential Duties And Responsibilities" list. We'll output

Responsibilities

with
  • each duty. - Qualifications: There's "Qualifications" section with MINIMUM KNOWLEDGE, SKILLS AND ABILITIES list. Also "Preferred Qualifications". We can combine into Requirements? The instruction: Use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have qualifications content. We could put under

    Qualifications

    with
    • for minimum and maybe separate for preferred? Could also split into Requirements (minimum) and Qualifications (preferred). But we need to avoid thin sections. Let's decide: Use

      Qualifications

      for minimum, and maybe

      Preferred Qualifications

      not in allowed list; but we could incorporate into Qualifications as separate
        with heading? Not allowed headings besides those. Could put both under Qualifications with two lists: one for Minimum, one for Preferred. Use

        to label? Might be okay. - Skills: The qualifications include many skills; but we could also extract skills into Skills section. However we already have qualifications covering skills. Might be redundant. The instruction: Prefer a few substantive sections over many thin ones. So maybe just Qualifications section covering both minimum and preferred. - Benefits, Pay, Schedule: The posting mentions "EVERSANA is committed to providing competitive salaries and benefits for all employees." but no specific benefits listed. It says "More information about EVERSANA’s benefits package can be found at eversana.com/careers." No concrete benefits. So we should NOT create Benefits section because no specific content. Pay: mentions compensation will be determined based on experience etc, but no salary range. So no Pay section. Schedule: not mentioned. Thus we output sections: About the role, Responsibilities, Qualifications. We must not repeat job title as heading. No Job ID etc. We must remove boilerplate: navigation, EEO, fraud warnings, etc. Also remove "Our team is aware of recent fraudulent job offers..." etc. Also remove "Follow us on LinkedIn | Twitter". Also remove "OUR CULTURAL BELIEFS" list? That is cultural beliefs but not a section heading; could be considered part of About the role? Might be considered boilerplate? It's specific content about cultural beliefs; could be included in About the role as a paragraph. But we need to preserve all substantive information. The cultural beliefs list is substantive; we could include it in About the role paragraph or as a separate section? Not in allowed headings. Could embed as

        list. We must not include duplicated lines. Let's extract content: Intro about EVERSANA (first paragraph up to "Join us!"): Actually there is a lot about EVERSANA mission. That's company overview, not role. Could be part of About the role? Might be considered "About the company". But we only have About the role heading allowed. Could we put company overview under About the role? Might be okay but it's not role-specific. However we need to preserve all substantive information; we could include it as a paragraph before role description under About the role. But the instruction: "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So About the role likely expects role description, not company overview. However we could still include company overview as part of About the role? Might be considered filler but it's substantive about the company. The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we need to include that company overview somewhere. If we don't have a heading for About the company, we could put it under About the role as a preamble. That's acceptable. Thus About the role section will contain: - Paragraph(s) describing EVERSANA mission, vision, team size, clients, etc. - Then the role description paragraph from "Job Description". We must not repeat the job title as heading. Now Responsibilities: list each duty from "Essential Duties And Responsibilities". Need to capture each bullet (they are sentences separated by periods). We'll split into list items. Let's extract duties: 1. 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. 2. Offer educational resources to support the entire patient’s journey by optimizing processes for prior authorizations/appeals/specialty pharmacy and addressing access issues. 3. 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. 4. Coordinate annual pharmacy reauthorizations at designated accounts to ensure timely reauthorization and continuation of therapy is maintained. 5. 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. 6. 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. 7. Build and execute a strategic business plan to meet the needs of top accounts and ensure successful implementation of market access initiatives. 8. 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. 9. Continuously strive to understand the alignment of Payer/PBM/SP and how national/regional pharmacy drug formularies impact market access in their designated geography. 10. 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. 11. Anticipate, navigate and address individual account and patient access issues that arise by partnering with all appropriate stakeholders. 12. Demonstrate a commitment to diversity, equity, and inclusion through continuous development, modeling inclusive behaviors, and proactively managing bias. 13. All other duties as assigned. Now 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 the biopharmaceutical industry a plus (e.g. product marketing, managed care, field sales, case management or large healthcare practice experience). We could combine these into Qualifications section with two sub-lists: Minimum and Preferred. We need to use
        • for any list of duties/requirements/benefits. So we can have
            for minimum, then maybe a

            "Preferred Qualifications:" then another

              . That's okay. Now we must exclude boilerplate: "Our team is aware of recent fraudulent job offers..." etc. Also "Follow us on LinkedIn | Twitter". Also "OUR CULTURAL BELIEFS" list? That is cultural beliefs but we could include as part of About the role? It's a list of beliefs; we could embed as a
                maybe under About the role? But we already have About the role with paragraphs; we could add a
                  for cultural beliefs. However the instruction says use
                  • for any list of duties/requirements/benefits. Cultural beliefs list is not duties/requirements/benefits, but it's still a list; we could still use
                      but it's not prohibited. Safer to embed as

                      with sentences. But we need to preserve all substantive information; we can include cultural beliefs as a paragraph. Let's craft About the role content: Paragraph 1: EVERSANA intro: "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." Paragraph 2: Role description: "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." Now Responsibilities list as above. Qualifications: We'll have heading

                      Qualifications

                      . Then maybe a

                      Minimum Knowledge, Skills and Abilities:

Similar jobs