BMT Clinical Pharmacy Specialist

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if there is real specific content. We must not repeat job title. Remove boilerplate. Preserve all substantive info. We need to parse the posting. Content: - About Us: description of MSK mission etc. This is about organization, not role. Should we include as "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. The "About Us" could be considered "About the role"? Actually "About the role" is more about role overview. The posting includes "Role Overview" after "Exciting Opportunity at MSK". So we can put that under "About the role". The "About Us" paragraph is generic about MSK; maybe we can include as part of "About the role" or maybe we can omit because it's not specific to role? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the "About Us" info somewhere. It is substantive about the organization. Could be placed under a heading like "About MSK" but not in allowed list. However we can include it as a

without heading? The instruction says use

for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but says "Use

for section headings (e.g. About the role, Responsibilities...)" implying we should use those headings for sections. It doesn't say we cannot have other headings, but likely they want only those headings. However we need to preserve all substantive info; we could put the "About Us" paragraph under "About the role" heading as part of that section. That would be okay. Let's extract sections: About the role: combine "About Us" and "Role Overview". Actually "About Us" is about MSK; "Role Overview" describes the role. We'll combine. Responsibilities: list bullet points after "Responsibilities". The text: "If you want to be at the forefront of novel therapy and impact patients’ lives then join the team at MSK), where our mission is to end cancer for life. In the CPS role you will serve in a purely clinical role rounding with the inpatient teams and seeing patients in the ambulatory clinics with responsibilities including: Drug therapy design and monitoring, patient medication counseling, and participation in Collaborative Drug Therapy Management (CDTM)Committee participation and development of treatment guidelines and pharmacy policiesPreceptorship of PGY2 Pharmacy residents and pharmacy studentsEducation of hospital staff through Grand Rounds presentations and in-service training" We need to split into list items. The text seems messy: after colon, list separated by commas and maybe missing punctuation. We'll extract items: - Drug therapy design and monitoring - Patient medication counseling - Participation in Collaborative Drug Therapy Management (CDTM) - Committee participation and development of treatment guidelines and pharmacy policies - Preceptorship of PGY2 Pharmacy residents and pharmacy students - Education of hospital staff through Grand Rounds presentations and in-service training We need to ensure each is separate

. Requirements: maybe "Key Qualifications" and "Core Skills"? Actually "Key Qualifications" includes doctorate, license, residency, etc. That's qualifications. "Core Skills" includes leader, problem solver, etc. That's skills. So we have: Requirements: maybe "Key Qualifications" (Doctorate in Pharmacy, Oncology experience preferred, NYS license (or eligibility), Completion of an ASHP-accredited pharmacy practice residency and an ASHP-accredited oncology residency, or equivalent experience are required (BCOP certified/eligible).) Qualifications: maybe we treat "Key Qualifications" as Requirements? Actually the list includes Requirements, Qualifications, Skills. We need to decide mapping. Often "Requirements" are mandatory items; "Qualifications" could be preferred; "Skills" are abilities. But we can follow the headings given: Requirements, Qualifications, Skills. We have: - Key Qualifications (Doctorate in Pharmacy, Oncology experience preferred, NYS license (or eligibility), Completion of an ASHP-accredited pharmacy practice residency and an ASHP-accredited oncology residency, or equivalent experience are required (BCOP certified/eligible).) This seems like requirements. - Core Skills (A confirmed, dynamic leader and creative problem solver. Self-motivated and driven for excellency. A collaborator and contributor for team integration. Passionate about working in a state-of-the-art institution. Continually striving to increase your knowledge and expertise in oncology practice.) These are skills. We might also have "Qualifications" maybe from "Oncology experience preferred" etc. But we already used that. Could treat "Key Qualifications" as Qualifications, and "Core Skills" as Skills, and maybe Requirements empty? But we need to include a section only when posting has real specific content. We have content for Qualifications and Skills. For Requirements maybe we can include the license and degree as requirements. Actually the "Key Qualifications" includes required items: Doctorate in Pharmacy, NYS license, completion of residencies. Those are requirements. Oncology experience preferred is a qualification. So we could split: Requirements: Doctorate in Pharmacy, NYS license (or eligibility), Completion of an ASHP-accredited pharmacy practice residency and an ASHP-accredited oncology residency, or equivalent experience are required (BCOP certified/eligible). Qualifications: Oncology experience preferred. Skills: list of core skills. But the instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Requirements and Qualifications into one section? But they ask to use headings for each if content exists. We could have Requirements (including required items) and Qualifications (preferred experience) and Skills. Let's extract precisely: From "Key Qualifications Doctorate in Pharmacy, Oncology experience preferredNYS license (or eligibility)Completion of an ASHP-accredited pharmacy practice residency and an ASHP-accredited oncology residency, or equivalent experience are required (BCOP certified/eligible)." There is missing punctuation; we need to parse: - Doctorate in Pharmacy, - Oncology experience preferred - NYS license (or eligibility) - Completion of an ASHP-accredited pharmacy practice residency and an ASHP-accredited oncology residency, or equivalent experience are required (BCOP certified/eligible). Thus required: Doctorate in Pharmacy, NYS license, completion of residencies (or equivalent). Preferred: Oncology experience. Thus we can put Requirements: Doctorate in Pharmacy, NYS license (or eligibility), Completion of an ASHP-accredited pharmacy practice residency and an ASHP-accredited oncology residency, or equivalent experience are required (BCOP certified/eligible). Qualifications: Oncology experience preferred. Skills: list. Now Benefits: The posting includes "Helpful Links Compensation PhilosophyBenefits Pay Range: $137,500.00 - $227,000.00 FSLA Status: Exempt". There's also "Compensation Philosophy" maybe a link. Benefits section maybe not detailed; only Pay Range is given. There's no explicit benefits description besides maybe "Compensation Philosophy" link. The instruction: never create Benefits section unless posting actually states them. It mentions "Benefits" word but no actual benefits listed. It says "Helpful Links Compensation PhilosophyBenefits Pay Range: ...". That seems like a garbled phrase: "Helpful Links Compensation PhilosophyBenefits Pay Range: $137,500.00 - $227,000.00". Likely they intended to have a link to Compensation Philosophy and Benefits, but no details. Since no specific benefits described, we should not create a Benefits section. Pay: we have Pay Range: $137,500.00 - $227,000.00. Also FSLA Status: Exempt. That's pay info. So we can create a Pay section with that. Schedule: "Schedule: Regular hours of work fall between Monday - Friday, 37.5 hours per week. Flexibility may be required depending upon the needs of the department". That's specific, so Schedule section. Location and Reporting to: maybe not needed as headings; could be included in About the role or maybe omitted? The instruction: Preserve ALL substantive information. So we need to keep location and reporting info. Where to put? Could be part of About the role or maybe a separate section like "Location" but not in allowed headings. Could add as a paragraph under About the role. We'll include after role overview. Also "Helpful Links Compensation PhilosophyBenefits" maybe we ignore as boilerplate. Now we need to output HTML fragment with

headings and

• for lists,

  for prose. We must not include job title heading. No markdown. Let's craft:

  About the role

  About Us paragraph + Role Overview paragraph combined.

  We need to include the About Us text: "The people of Memorial Sloan Kettering Cancer Center (MSK) are united by a singular mission: ending cancer for life. Our specialized care teams provide personalized, compassionate, expert care to patients of all ages. Informed by basic research done at our Sloan Kettering Institute, scientists across MSK collaborate to conduct innovative translational and clinical research that is driving a revolution in our understanding of cancer as a disease and improving the ability to prevent, diagnose, and treat it. MSK is dedicated to training the next generation of scientists and clinicians, who go on to pursue our mission at MSK and around the globe." Then Role Overview: "Exciting Opportunity at MSK: Our Clinical Pharmacy team is looking for a BMT Clinical Pharmacy Specialist to join our team! Role Overview We are recruiting for a Clinical Pharmacy Specialist (CPS) for our Adult BMT service. As a CPS you will have the opportunity to play a critical role and practice at the top of your license in collaboration with our innovative multidisciplinary teams in both the inpatient and outpatient settings. The Clinical Pharmacy Specialist (CPS) is a designated hospital-wide expert in clinical pharmacy and directly provides leadership for the continued growth of comprehensive clinical pharmacy services. The CPS plays an integral role as the therapeutic resource for drug information and pharmacotherapy of their service’s patients. The position is also responsible for the division's educational and quality improvement programs." We can combine. Then Responsibilities heading with list. Then Requirements heading with list? Actually Requirements are not a list but could be a paragraph. Could be

  with items separated by commas or semicolons. Could also be

  • . The instruction: Use
    • for any list of duties/requirements/benefits. So if we have multiple items, we should use list. For Requirements we have multiple items: Doctorate in Pharmacy, NYS license (or eligibility), Completion of an ASHP-accredited pharmacy practice residency and an ASHP-accredited oncology residency, or equivalent experience are required (BCOP certified/eligible). That's maybe one sentence but includes multiple items. Could still be a list: each requirement as
    • . Let's do that. Qualifications: Oncology experience preferred. That's single item; could be

      or

      • . Use list if we want consistency; but it's okay as

        . Skills: list of core skills items. Pay:

        with Pay Range and FSLA Status. Schedule:

        with schedule details. We also need to include location and reporting info. Could add a paragraph under About the role after role overview. Let's extract location: "Location: Main Hospital Campus, 1275 York Avenue, and The David H. Koch Center for Cancer Care, 530 E. 74th St, New York, NY". Reporting: "Reporting to: Manager, Oncology Clinical Pharmacy". We'll include as a paragraph. Now