Medical Science Liaison, Rheumatology (NJ & Eastern PA)

We need to output HTML fragment with sections: About the role? The posting includes description about purpose, etc. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title as heading. Must not put Job ID/requisition numbers as headings. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Also must not include sections with filler like "commensurate with experience". Pay and Schedule only if posting actually states them. The posting includes Compensation Overview with pay range. So we can include Pay section with that info. Schedule? Not explicitly stated; maybe not. Benefits: there is a Benefits paragraph. So include Benefits section. Responsibilities: there is a big block under "Key Responsibilities". So include Responsibilities. Requirements: there is "Position Requirements" with required experience, knowledge desired, experience desired, essential qualification, travel requirement. So include Requirements. Qualifications? Might overlap with Requirements; but we can treat Requirements as qualifications. The instruction says use headings for those categories; we can include Qualifications if there is distinct content. The posting includes "Essential Qualification Ability to drive a company-provided car is an essential qualification". That's part of Requirements. Could also include Skills: there are many skill descriptors. Could put Skills section. But we need to avoid thin sections. Perhaps combine Requirements and Skills? But we need to follow instruction: use headings for those categories if content exists. We can include Responsibilities, Requirements, Skills, Benefits, Pay. Avoid Schedule (no info). About the role: there is introductory paragraph about BMS purpose and MSL role. Could be About the role. So include About the role. We must not repeat job title as heading. So no heading for "Medical Science Liaison, Rheumatology (NJ & Eastern PA)". We'll just output sections. We need to preserve all substantive information; do not invent or summarize away detail. Must keep details but can rephrase? Probably we should keep the info as is, but we can format into

and

• . Must not include boilerplate like EEO, legal, etc. Also must remove duplicated lines. Also remove application instructions like "To check your application status..." etc. Also remove links? Probably we can keep URLs? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It doesn't explicitly say to remove URLs, but they might be part of benefits or ways of working. Might be okay to keep them? Safer to keep them if they are substantive (like benefits link). However the benefits paragraph includes a link to benefits page; that's substantive. The "How We Work" includes a link; maybe that's not essential but could be considered navigation? Might be considered boilerplate? It's about ways of working; could be considered substantive. But we can keep. We need to strip out sections like "Supporting People With Disabilities", "Candidate Rights", "Data Protection", etc. Those are legal/EEO boilerplate. Remove them. Also remove the final line with Job ID and requisition number: "R1606224 : Medical Science Liaison, Rheumatology (NJ & Eastern PA)". That's metadata; we should drop it. Now craft HTML. Structure:

  About the role

  ... (intro paragraph about BMS purpose and MSL role)

  Responsibilities

  • ... each responsibility as separate li.
  We need to preserve all substantive info from responsibilities block. That block is long; we can break into bullet points for each sentence or clause. Must not lose detail. We'll create li for each distinct responsibility. Let's extract responsibilities from the text: "Key Responsibilities External Environment and Customer FocusDevelop and maintain relationships with academic and community research thought leaders, appropriate HCPs, and access stakeholders, within a given geography to answer scientific, unsolicited product, and HEOR related questions. The MSL will use various channels for interactions (1:1, group presentations, remote, etc.) Demonstrate proficiency in using available scientific resources and presentations. Effectively present information to TL/HCPs and be able to respond to questions, ensuring medical accuracy and compliance with local procedures, ethical and legal guidelines and directives.Actively assess the medical landscape by meeting with TL/HCPs/Access Stakeholders to understand their needs and expertise. Continuously update own knowledge in treatment strategies, products, unmet medical needs, clinical trials, health economics outcomes research and scientific activities. Understand the competitive landscape and evolving healthcare models and actively prepare to address informational needs of customersIdentify opportunities to partner with HCPs on disease state initiatives, collaborative research projects, and investigator sponsored research (ISR) of interest and in alignment with BMS strategic objectivesAttend medical congresses and local/regional meetings. Collect and provide meaningful medical insights and/or impact by communicating these back to the medical and commercial organizations to support strategy development and business decisionsContribute to the Medical PlanDevelop geography-specific Field Medical and TL Interaction plans based on therapeutic area objectives and TLs needsAdopt institution/account planning approach and contribute to cross-functional institution/account plansContribute to development and delivery of scientifically meaningful medical programs/projects in line with the local Medical and Field Medical planProvide Medical SupportEstablish a customer-centric, compliant collaboration with cross-matrix field teams within assigned geographyAs necessary and appropriate, support the initial and ongoing medical/scientific area and product specific training and provide key scientific updates to internal stakeholders (e.g. Commercial, Regulatory, Pharmacovigilance, Legal, HEOR, Value Access & Payment)Provide scientific support at promotional meetings by presenting scientific and clinical data, by evaluating speakers and by giving support to BMS-contracted speakers (if applicable)Participate in assigned Congress activitiesSupport Clinical Trial ActivitiesSupport Interventional and Non Interventional Research (NIR) studies (e.g. identification and assessment of potential study sites) to facilitate patient recruitment and/or discussions around the safe and effective use of BMS investigational products, as agreed with home office medical and Global Development Operations (GDO) and as defined by the study scope documentProvide recommendations and insights to clinical development team on study and site feasibilities within the therapeutic area based on knowledge of the field and through direct contacts with potential investigators, as agreed with home office medical and GDOSupport HCPs in the ISR submission and execution process and study follow-up as agreed upon with home office medical and GDOEnsure that BMS Pharmacovigilance procedural documents are understood and applied by investigators of local studies, and alert appropriate BMS personnel to any identified Adverse EventsActively support CRO sponsored studies as agreed with home office medical and GDO and as defined by the study scope document" We need to split into sensible bullet points. We'll create bullets for each major responsibility. Now Requirements block: "Position Requirements Required Experience MD, PharmD, PhD, APP, PA, NP with experience in a specific Disease Area or with a broad medical background and relevant pharmaceutical experience Knowledge Desired Disease area knowledge and an understanding of scientific publicationsKnowledge of a scientific or clinical area, competitive landscape and patient treatment trendsKnowledge of clinical trial design and processKnowledge of the national healthcare and access environmentKnowledge of HEOR core conceptsExcellent English language skills, spoken and written Experience Desired A minimum of 2 years working in a clinical and/or pharmaceutical environmentPrior MSL experienceAbility to work independently and act as a team playerTranslating scientific or clinical data into an understandable and valuable form to help physicians best serve their patientsGood communication and presentation skills to present scientific and/or clinical data to research or healthcare professionalsDeveloping peer-to-peer relationships with TLs, scientists and other healthcare professionalsAbility to quickly and comprehensively learn about new subject areas and environmentsDemonstration of the BMS Values Essential Qualification Ability to drive a company-provided car is an essential qualification of this position. Candidates must be able to drive a BMS-provided vehicle between locations (often great distances apart) and arrive at each location ready and able to enthusiastically and efficiently demonstrate an applied knowledge of pertinent health care industry trends. Candidates must possess a high level of ethics, integrity, and a responsible and safe driving history Travel Requirement Position is field based, MSL will be required to live in the territory which they manage or within 50 miles of the territory bordersThe MSL will spend majority of their time in the field with their external customers. Further requirements based on territory assignment and team needs" We need to preserve all that. We'll break into bullets for each requirement. Skills: many of those are overlapping with requirements; but we could create a Skills section for the skill-based items: translating data, communication, presentation, peer-to-peer relationships, quick learning, etc. However to avoid duplication, maybe we just keep Requirements and not Skills. But instruction says we can include Skills if there is real specific content. The posting includes many skill descriptors; we could put them under Skills. But then Requirements would be reduced to just experience/qualifications. However the instruction says preserve ALL substantive information; we can split but must not lose any. It's okay to have overlapping content? Might be considered duplication but not necessarily boilerplate. Safer to keep Requirements only and not Skills, to avoid thin sections. But we need to decide. We also have Benefits section: paragraph about benefits. Pay section: compensation overview. Schedule: none. Now About the role: we need to capture the introductory paragraphs before "Key Responsibilities". Let's extract: "At Bristol Myers Squibb, our employees often ask, “Who are you working for?”—a question that fuels collaboration, accountability, and urgency in our work. Our purpose-driven culture inspires us to discover, develop, and deliver innovative medicines to prevail over serious diseases. We offer uniquely interesting and meaningful work, opportunities for growth, and a supportive environment that values inclusion, wellbeing, flexibility, and comprehensive benefits. This is work that transforms the lives of patients, and the careers of those who do it. The Medical Science Liaison (MSL) role embodies our medical mission to be recognized as the trusted partner for internal stakeholders and the healthcare community, driving scientific exchange to enhance medical education, data generation, insight generation and patients’ access to medicine. The MSL is responsible for identifying disease and product related medical needs in a defined geography. The primary role of the MSL is to develop and maintain relationships with Thought Leaders (TL) and Healthcare Providers (HCP) within their healthcare system. The purpose of their interactions is to engage in meaningful scientific exchange that will ensure patients have access to BMS medicines, to ensure their safe and appropriate use through peer to peer discussions aligned with medical strategies and needs expressed by external stakeholders, and to facilitate research. The MSL also serves as the medical resource for external stakeholders in the community." We'll put that in About the role. Now we need to strip out any boilerplate like "We hire for skills and capabilities, not just credentials – if this role excites you, but doesn’t perfectly match your resume, we encourage you to apply anyway." That's application encouragement; maybe considered application instruction? It's not exactly instruction to apply but encouragement. Might be considered boilerplate? It's not legal/EEO but could be considered generic. Safer to remove it as it's not substantive detail about role. Also remove "We hire for skills and capabilities..." line. Also remove "Supporting People With Disabilities", "Candidate Rights", "Data Protection", etc. Also remove the "How We Work" paragraph? It's about work models; could be considered substantive about role? It's generic across roles; maybe not needed. But it's not boilerplate legal; it's about ways of working. Could be considered substantive but maybe not needed. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "How We Work" is not those. Might keep but it's not specific to role. However it's still substantive info about the role's work model. Could keep under About the role or a separate section? There's no heading for Work Model. Could incorporate into About the role. But