Field Medical Outcomes, Director, non-MD

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to extract content. The posting includes Role Summary (which could be About the role). Then Role Responsibilities (list). Then Basic Qualifications (list). Then Preferred Qualifications (list). Then Non-standard Work Schedule, Travel Or Environment Requirements (travel, schedule). Also there is "Other Job Details: La" truncated but ignore. We need to map: - About the role: Role Summary paragraph(s). Provide as

. - Responsibilities: list of responsibilities. Use

• . - Requirements: maybe Basic Qualifications? The spec says Requirements section for list of duties/requirements/benefits. Could treat Basic Qualifications as Requirements. Or we could have Requirements and Qualifications separate. The spec says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide what goes where. We have Basic Qualifications (education, experience, skills). Preferred Qualifications (additional). Skills maybe from those. Could combine. We need to avoid filler like "commensurate with experience". Not present. We need to include Pay and Schedule only if posting actually states them. There's no explicit pay or salary. So we should NOT include Pay or Schedule sections unless there is specific content. There's travel requirements, schedule flexibility, but not explicit schedule like "full-time" etc. The spec says: never create Pay/Schedule/Benefits sections unless the posting actually states them. There's no explicit benefits listed. So we should omit Benefits, Pay, Schedule sections. We need to include Qualifications section maybe for Preferred Qualifications? Or we could put Basic Qualifications under Requirements and Preferred under Qualifications. Let's interpret: - Requirements: mandatory qualifications (Basic Qualifications). - Qualifications: preferred qualifications (Preferred Qualifications). - Skills: maybe we could extract skills from both, but we could also omit Skills if not distinct. But we could include a Skills section summarizing skills like "Strong analytic skills, excellent oral/written communication, interpersonal skills, leadership, etc." However we must not invent or summarize away detail; we can list them as items if they appear. The posting includes many skill-like statements: "Excellent oral and written communication skills required", "Excellent and demonstrated interpersonal skills...", "Strong analytic skills including creativity...", "Strong comprehension and communication skills...", "Well-organized with the ability to be flexible, prioritize multiple demands, and employ strong situational leadership skills", "Breadth of diverse leadership experiences and capabilities including the ability to influence and collaborate with peers and create business impact". Those are in Basic Qualifications. Also Preferred Qualifications include experience analyzing health care data, expertise in Clinical Informatics/HIT, residency/fellowship, Microsoft Access, statistics software, data programming, experience with EHR optimization, leadership in innovative project start-up, understanding of US healthcare system, etc. We could create a Skills section that lists those skill statements. But we must not invent; we can extract them as list items. But we also have Responsibilities already covering duties. So we could have: - About the role: Role Summary paragraph(s). - Responsibilities: list from Role Responsibilities. - Requirements: list from Basic Qualifications (education, experience, etc.) - Qualifications: list from Preferred Qualifications. - Skills: maybe we could omit if we consider those already covered. But spec says we can include Skills section if there is real specific content. There are skill statements; we could put them under Skills. However we might double-count. Better to follow typical structure: Requirements (education/experience), Qualifications (preferred), Skills (specific abilities). Let's extract skill statements from both Basic and Preferred. But we must preserve ALL substantive information; we cannot drop any. If we put skill statements under Skills, we must also keep them somewhere else? The spec says preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication? It says preserve all substantive information; we could place them in multiple sections but that would be duplication but still preserving. However better to not duplicate; we can assign each piece to a section logically. Let's parse the posting: Role Summary paragraph(s): multiple sentences. We'll combine into one

  . Role Responsibilities: a long list of responsibilities, each sentence starting with a verb. We'll make each as

• . Basic Qualifications: bullet list after "Candidate demonstrates a breadth of diverse leadership experiences and capabilities including: the ability to influence and collaborate with peers, develop and coach others, oversee and guide the work of other colleagues to achieve meaningful outcomes and create business impact". Then list items: Bachelor’s degree in health science required; PharmD, PhD, or equivalent terminal doctoral degree preferred; Relevant experience required: 8+ years with bachelor’s degree; 7+ years with master’s degree; 5+ years with terminal doctorate degree (PharmD, PhD); Experience should be in any of the following: Clinical, formulary, and/or other management experience; Managed Care, pharmaceutical industry, and/or Quality Improvement; Data Analytics and/or HEOR activities, with demonstrated strong methodological skills (study design, data analysis, and interpretation) in health services research; Significant experience in interacting with payers and other organized customers is required; Excellent oral and written communication skills required; Excellent and demonstrated interpersonal skills: ability to understand and respond to multiple external and internal customers’ demands, manage and handle conflict constructively required; Breadth of diverse leadership experiences and capabilities including the ability to influence and collaborate with peers and create business impact; Strong analytic skills including creativity and effectiveness in proactively identifying and addressing challenges; Strong comprehension and communication skills, including ability to communicate large amounts of scientific information in a manner that is clear and concise; Well-organized with the ability to be flexible, prioritize multiple demands, and employ strong situational leadership skills. We need to capture each as list items. Preferred Qualifications: list after "Preferred Qualifications". Items: Previous experience in field-based medical/outcomes role; Experience analyzing health care data (claims, electronic health records, other health care data); Expertise in Clinical Informatics or Health Information Technology (HIT), including working with claims data sets or Electronic Health Record (EHR) systems; Residency or Fellowship experience; Microsoft Access, statistics software, and/or data programming experience; Experience in the clinical, functional, and technical application of health information technology used in the U.S; Experience with optimization/customization of EHR platforms, including developing EHR clinical solutions; Leadership in innovative project start-up and management; Understanding of the complex business environment within the US healthcare system as well as emerging healthcare trends. Non-standard Work Schedule, Travel Or Environment Requirements: includes: Valid US driver’s license and driving record in compliance with company standards. Any DUI/DWI or other impaired driving citation within the past 7 years will disqualify you from being hired; Flexibility to travel 40-50% of time; Reasonable proximity to airline ‘hub’ city; must be within a 2-hour drive of a major airport; Ability to work on weekends occasionally (e.g. attend advisory boards and congress meetings); Ability to regularly fly on airplanes (i.e. attend medical stakeholder meetings; attend HQ meetings, regional and national scientific meetings, etc.) required; Ability to travel, including overnight travel for internal and external meetings (customer, industry, and professional society meetings). We could put travel/schedule info under a "Schedule" section? The spec says only create Schedule section if posting actually states them. It does state travel flexibility, weekend work, flying, etc. That's schedule-related. So we could include a Schedule section with those details. However the spec also says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule/travel requirements, so we can include a Schedule section. Benefits not present, so omit Benefits. Pay not present, omit Pay. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Schedule. (We could also include Skills if we want, but we already have skill statements in Requirements and Qualifications; maybe we can omit Skills to avoid thin sections. But we have many skill statements; we could still include Skills section with those skill statements extracted from both Basic and Preferred. However then we would be duplicating. Better to not include Skills and keep skill statements within Requirements and Qualifications. The spec says "Prefer a few substantive sections over many thin ones." So we can omit Skills. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Schedule. Now we need to output HTML fragment: use

  for each section heading. Use

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

    for prose. Thus:

    About the role

    Role Summary ...

    Responsibilities

    • ...
    ...

    Requirements

    • ...
    ...

    Qualifications

    • ...
    ...

    Schedule

    • ...
    ...
    We must not include any extra text like comments. Now we need to extract the exact sentences preserving meaning. Let's craft About the role paragraph: combine the Role Summary sentences. Original Role Summary: "The Field Medical Outcomes is a field medical colleague responsible for informing customer decision-making and improving population health through real-world data analytics, pharmacoeconomic analyses, outcomes evaluations and medical presentations. The role is responsible for educating customers on the clinical and economic impact of Pfizer medicines and products. The colleague may also be responsible for providing disease area/therapeutic area/product-based expertise for designated TA areas with a primary focus on integrated health care organizations, including but not limited to Integrated Delivery Systems, Payer customers and Specialty Pharmacy Providers (SPPs). The responsibilities of the role are to contribute to Pfizer’s ability to (a) Plan and execute the independent Medical strategy and engagement for appropriate assigned customers within a territory, compliantly coordinating with other Pfizer colleagues as needed to achieve Medical objectives (b) Understand the priorities of Pfizer Medical Affairs in order to contribute to Medical educational content strategy development and execute aligned Field Medical tactics (c) Maintain effective and appropriate communication and collaboration among headquarters Medical colleagues, Medical Information, and other Pfizer Field Medical colleagues (d) Demonstrate expertise in scientific communication across multiple channels, including, but not limited to, live and virtual presentations in small or large settings, written communication, and telephone or virtual conversations (e) Compliantly integrate understanding of clinical, Health Information Technology (HIT), market, and account considerations to develop and execute mutually beneficial customer-specific projects, collaborations, strategic medical partnerships, and non-interventional studies with the goal of advancing quality of care and improving patient outcomes (f) Optimize patient care improvements in centricity of Medical communications and deliverables, incorporating Health Literacy and cultural awareness principles to ensure that patients remain the ultimate focus. The role may interact with accounts in the region including Healthcare Decision Makers (HCDM) affiliated with organized customers. The colleague will respond to medical questions regarding Pfizer products for the designated therapeutic area and other Pfizer medicines as appropriate. The individual may be involved in presentations to payers, managed care organizations, formulary decision makers and regional medical advisory boards in accordance with the designated therapeutic area medical strategy. The Medical Outcomes colleague will also facilitate communication between regional and national HCOs and headquarters Medical Affairs colleagues and provide customer insights that contribute to the development of brand medical strategies as appropriate. The role may facilitate Pfizer sponsored research projects/studies which could include collaborative projects, quality improvement research and non-interventional studies. The colleague will maintain required level of knowledge of relevant TA/disease states and Pfizer medicines, providing therapeutic area/product information to both internal and external stakeholders as needed, and serve as a conduit and resource for Medical Information and customer insights, providing requested information to medical stakeholders as allowed by Pfizer guidance and sharing customer viewpoints with Pfizer as appropriate." We need to preserve all that. We'll put as a single

    maybe with line breaks? It's okay. Now Responsibilities list: