VP, Patient Access Strategy - Remote

We need to produce HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Any offer of employment is contingent upon..." etc. Also remove "Our Commitment to Equal Opportunity". Also remove "Please note that this job description is not intended to be an exhaustive list..." etc. We need to preserve all substantive information. So we need to extract sections: About the role (company description), Responsibilities (list of essential functions), Requirements (what you'll need to thrive), Preferred Attributes (maybe under Requirements or separate), Benefits (list of benefits), maybe Pay and Schedule not present (no mention). So we should not include Pay or Schedule sections. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not create sections with filler like "commensurate with experience". Not present. We need to include About the role: description of Valeris, mission, etc. That's at start: "Valeris is a fully integrated life sciences commercialization partner..." up to "To learn more about Valeris, please visit www.valeris.com." Also mention headquarters. That's about the role/company. Then Responsibilities: The essential functions list (starting with "Your Impact in This Role Essential Functions" then bullet list). We need to capture each bullet as

• . The text includes many sentences; we can split by line breaks? The original has sentences separated by line breaks? It appears as a paragraph with sentences separated by spaces. We need to parse into list items. Probably each sentence starting with a verb is a responsibility. We'll extract each distinct responsibility as separate
• . Let's list them: - Lead the development of our strategy for specific new business development opportunities in addition to working with our product, operations, technology, marketing and commercial teams to evolve Valeris’ enterprise strategy for our entire Patient Access portfolio. - Contribute to the strategy and tactics for access services opportunities by developing content that reinforces Valeris’ differentiated value proposition (RFP responses and executive summaries, Bid Defense Slides, Technology Strategy, etc.) and attending in person presentations or via conference call when it is not possible to travel in person - Be available as the go-to resource to help resolve complex questions, strategies, and potential issues raised by our commercial, operations, and product teams for ongoing Patient Services Programs and our Innovation & Product Development Roadmap - Function as a Key Thought Leader in the Patient and Market Access marketplace by representing Valeris’ solutions and enterprise strategy through a partnership with marketing and peers to develop white papers, create and deliver podium talks, and develop other types of promotional marketing campaigns. - Serve as a resource to Valeris’ client services team to help problem-solve any complex program operational challenges and opportunities, as well as preview new strategic solutions to our top clients at QBRs and in other key strategic meetings - Partner with Commercial Learning & Development to ensure appropriate team members fully understand commercial strategy - Work with our client’s brand strategy owners regarding tactical planning process for Patient Access Services - Grow the portfolio of Valeris business in the utmost ethical manner - Network with industry contacts to uncover new business opportunities and enhance the market reputation of Valeris - Provide leadership through communication, and utilization of personal expertise - Improve Valeris employee product knowledge, market awareness, and overall understanding of Patient Services from the many perspectives of the constituents we service including manufacturer, patient, payer, provider, and pharmacy - Always maintain confidentiality as exposure to sensitive information regarding Valeris operations is mandatory for proper analysis of channel opportunities - Communicate and be accountable to all Valeris identified standards and expectations - Be a knowledgeable teammate and maintain a positive attitude to all - Always maintain a professional relationship with all customers and clients - Provide consistent communication and collaboration with internal and external stakeholders - Adhere to administrative task responsibilities - Utilize Valeris’ leadership competencies as the driving force behind the team’s success - On time adherence to training deadlines for all corporate policies and procedures governing access to confidential data - Ensure all SOPs are followed with consistency - Conducts miscellaneous tasks or projects as assigned We need to ensure each is a list item. Then Requirements: "What You’ll Need To Thrive In This Role" list: - History of working in the pharmaceutical services industry with a focus on patient access and affordability services - Defines and designs use cases and requirements for patient access program transactions and processes - Works with clients to establish strategic opportunities, operational standards, policies, and procedures for HUB, DTP, Pharmacy, Field Reimbursement, Nursing, and Affordability services operations to leverage next best action/service - Understands the nuances of PSP programs and leveraging the data available to determine what a patient needs within the ecosystem and how to support these needs - In-depth knowledge of the functional process for PSP operations and how HUB and Affordability Services programs are built within pharmaceutical organizations. - In-depth knowledge of the functional aspects of the technology enabling the processes within the PSP functions and how they work together - Ability to perform Valeris focused requirements regarding Patient Access Services through written proposals/presentations, data validation, documentation of business and conversion processes, and show the ability to manage critical projects - Understanding of industry best practices and possess the ability to communicate those insights to help improve the Valeris business model - Leverage industry network and contacts to identify new business opportunities to drive Valeris growth Then Preferred Attributes: maybe under Requirements or separate section "Preferred Attributes". Could be a subsection under Requirements but we can make a separate section "Preferred Attributes". However the instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Preferred Attributes not listed; but we could incorporate into Requirements or Qualifications. Since they are "Preferred Attributes", we could put them under Requirements as a sublist? But we must not invent headings not in list. Better to include them under Requirements as part of the list, maybe separate
  with a note? Could add a

  saying "Preferred attributes:" then list. But we need to follow instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings. We can put Preferred Attributes under Requirements as part, maybe as a separate

  with a preceding

  indicating they are preferred. That's acceptable. Qualifications: Not explicitly separate; maybe we can treat Requirements as qualifications. Skills: maybe not separate; we could embed skills within Requirements. But we could create a Skills section if there is explicit skill list. There is mention of typing speed, etc. That's under Physical Demands & Work Environment. That's not a skill but a requirement. Could be part of Requirements. Benefits: list under "Why Work for Valeris?" includes many benefits. We'll create Benefits section with

  . Pay and Schedule: not present, so omit. We must remove boilerplate: "Any offer of employment is contingent upon..." and "Please note that this job description is not intended..." and "Our Commitment to Equal Opportunity". Also remove duplicated lines? Not seeing duplicates. Now produce HTML fragment. Structure:

  About the role

  ... (company description)

  Responsibilities

  • ...
  ...

  Requirements

  History of working in the pharmaceutical services industry with a focus on patient access and affordability services

  maybe better as list. But we need to use
  • for any list of duties/requirements/benefits. So Requirements should be a list. Thus:

    Requirements

    • History of working in the pharmaceutical services industry with a focus on patient access and affordability services
    • Defines and designs use cases and requirements for patient access program transactions and processes
    ...
    Then maybe a

    for preferred attributes: "Preferred attributes:" then list. But we need to keep list format for preferences as well. Could do another

    under Requirements with a preceding

    indicating preferred. Or we could add a separate section "Qualifications" for preferred attributes? Not ideal. Better: after Requirements list, add a

    Preferred attributes:

    then another
    for those. But the instruction says use
    • for any list of duties/requirements/benefits. So we can have multiple lists. Thus:

      Requirements

      • History of working in the pharmaceutical services industry with a focus on patient access and affordability services
      ...

      Preferred attributes:

      • Advanced degree (MBA, MPH, etc.)
      • Market Access experience in pharmaceutical, biotech or related field
      • Experience in the community and/or hospital setting selling and/or supporting specialty, value-oriented, non-commodity products
      Then Benefits:

      Benefits

      • Medical, dental, and vision plans, including HSA- and FSA-eligible options, with Valeris contributing toward premium costs
      • Additional health support, including telehealth and Employee Assistance Program (EAP) services
      • Company match on Health Savings Account contributions
      • Free Basic Life and AD&D coverage equal to your annual earnings, with a minimum of $50,000 and a maximum of $300,000
      • Company-paid Short-Term Disability coverage, with the option to purchase Long-Term Disability
      • 401(k) Retirement Savings Plan with 100% match on the first 5% you contribute, with immediate vesting
      • Paid Time Off (PTO) and Sick Leave to support work-life balance
      • Team members receive nine paid holidays plus two floating holidays
      • Opportunities for advancement in a company that supports personal and professional growth
      • A challenging, stimulating work environment that encourages new ideas
      • Work for a company that values diversity and makes deliberate efforts to create an inclusive workplace
      • A mission-driven, inclusive culture where your work makes a meaningful impact
      We should also include Physical Demands & Work Environment? Not a standard heading; maybe we could include under Requirements as additional items? But it's not a requirement per se, but could be included as part of Requirements. However the instruction says only use those headings; we could add a section "Requirements" and include those details as list items. But they are not exactly requirements but work environment. Could be omitted? The instruction says preserve ALL substantive information. So we need to include that info somewhere. Could add a section "Requirements" and include those as list items under a subheading? But we cannot add new headings. Could add a

      within Requirements describing physical demands. That's acceptable: we can have a

      after the list. Thus after Requirements lists, add a

      Physical demands & work environment: While performing the duties of this job, the employee is regularly required to talk or hear. The employee is frequently required to sit for long periods of time, use hands to type, handle or feel; and reach with hands and arms. Prefer candidates who can type at least 35 words per minute with 97% accuracy.Although very minimal, flexibility to travel as needed is preferred.This job operates in a professional office environment. This role routinely uses standard office equipment such as computers, phones, photocopiers, etc.

      That preserves info. Now ensure we didn't include any boilerplate like EEO etc. Also removed "Any offer of employment..." and "Please note that this job description is not intended