Jobs · Healthcare · Maryland

Advanced Practice Pharmacist - BWMC

University of Maryland, Baltimore (UMB) · Baltimore, MD · 1 mo ago
Healthcare$125k–$143k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. We need to extract content. Let's parse the posting. First paragraph: description of University, location, etc. That could be "About the role" maybe. But we need to decide. We have "Primary Duties" list: many bullet-like sentences. Those are responsibilities. We have "Minimum Qualifications": Education, Experience, Certification/Licensure, Other. We have "Knowledge, Skills, And Abilities": list. We have benefits described earlier: "Benefits UMB offers a comprehensive benefits package..." includes retirement program, leave package, health insurance, professional learning, tuition remission, flexible work schedules, teleworking options. We have Pay: "HIRING RANGE: $125,000 - $143,000 per year / Commensurate with education and experience". The phrase "Comm..." is placeholder? It says "Comm...". Actually it's "Comm...". The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we cannot include Pay section if it includes "Comm..."? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state a hiring range, but also includes "Comm...". The phrase "Comm..." is filler? It says "Comm...". Actually it's "Comm...". The text: "HIRING RANGE: $125,000 - $143,000 per year / Commensurate with education and experience". The part after slash is "Comm...". That is filler? It's basically saying it's commensurate with education and experience, which is typical but maybe considered filler? The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So if we include Pay section, we must ensure the content is not just filler. The posting gives a range, which is specific. The "Comm..." phrase is additional but not filler? It's still a phrase but maybe considered filler. Safer to include Pay section with the range and maybe omit the "Comm..." phrase? But we must preserve ALL substantive information; do NOT invent or summarize away detail. We cannot remove the "Comm..." phrase if it's part of the posting. However, the instruction says never emit a heading followed by filler/placeholder text. If we include Pay section, the content would include the range and also the phrase "Comm...". That phrase is filler? It's basically saying it's commensurate with education and experience, which is typical but maybe considered filler. The instruction example includes "commensurate with experience" as filler to avoid. So we should not include Pay section if the only substantive content is the range? Actually the range is substantive. But the phrase after slash is filler. Could we keep the range and drop the filler? That would be summarizing away detail (removing the phrase). Might be considered okay? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Removing "Comm..." might be summarizing away detail (though it's not substantive?). It's arguably not substantive; it's a standard phrase. Might be okay to drop it? Safer to include Pay section with the range and keep the phrase? But then we have filler text. The instruction says never emit a heading followed by filler/placeholder text. It doesn't say you cannot have filler within the section; it says heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") meaning if the section only contains that filler, don't include it. If there is also substantive info, it's okay? The example: they say never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). That suggests if the content under that heading is just that filler, don't include the heading. If there is more substantive content, it's okay. So we can include Pay section with the range and also the phrase; it's not just filler. Schedule: Not mentioned. No schedule info. So we omit Schedule. Benefits: we have substantive description. Include Benefits. Now sections: About the role (intro), Responsibilities (Primary Duties), Requirements (maybe Minimum Qualifications?), Qualifications (maybe Education/Experience?), Skills (Knowledge, Skills, And Abilities). But we need to avoid duplication. The posting has Minimum Qualifications and Knowledge, Skills, And Abilities. Could map Requirements to Minimum Qualifications, Qualifications to something else? Actually they want sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: - About the role: introductory paragraph about UMSOP, location, mission. - Responsibilities: Primary Duties list. - Requirements: Minimum Qualifications (Education, Experience, Certification/Licensure, Other). - Qualifications: maybe preferred qualifications? The posting mentions "Doctoral degree in pharmacy (PharmD) preferred." and "Certification in a relevant specialty ... preferred." Also maybe "preferred" items. Could treat those as Qualifications (preferred). But we have to not invent sections if no content. There is content: preferred qualifications. So we can include Qualifications section for preferred items. - Skills: Knowledge, Skills, And Abilities. - Benefits: as described. - Pay: hiring range. - Schedule: none -> omit. We must not repeat job title as heading. No Job ID etc. We need to output only HTML fragment, using

for section headings,
  • for any list of duties/requirements/benefits, and

    for prose. We need to preserve ALL substantive information; do not invent or summarize away detail. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to strip out EEO statement, ADA accommodation, Title IX, etc. Also remove "For more information, please visit HR Benefits at ..."? That's maybe part of benefits but could be considered boilerplate? It's a link for more info; maybe we keep as part of benefits? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits links are not exactly those; they are informational. Might keep them? But they are not essential substantive? Could be considered part of benefits description. However, they are URLs; we could keep them as part of

    . The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we should keep the benefit description including the links? The links are part of the benefits info. Might keep them. But we need to avoid duplication: there are two benefit links: one for HR Benefits, another for UMB Employee Perks. Keep both. Also need to remove "UMB is a public university..." etc. That's maybe boilerplate? It's about employment location requirement. Might be considered substantive? It says "All employees are expected to work primarily physically within the State of Maryland. Employees whose job duties require them to work in a clinical setting or at clinical or field sites are required to comply with the COVID-19 vaccine requirements of those specific sites." That's substantive about work location and vaccine requirement. Should we keep? It's not in the defined sections but could be part of About the role or Requirements? Might be considered a requirement (location). Could include in Requirements? But we already have Requirements for qualifications. Might add a separate paragraph under Requirements about location and vaccine. However, the instruction says to use sections only when posting has real specific content. It does have that content. Could we add a paragraph under Requirements? Or maybe under About the role? I'd add a

    under Requirements after the list? But we need to follow format: Use

    • for any list of duties/requirements/benefits, and

      for prose. So we can have prose paragraphs inside sections. Thus: not needed; just headings and content. Structure:

      About the role

      ... intro ...

      Responsibilities

      • ... each duty ...

      Requirements

      ... Minimum Qualifications prose? Actually we have list items for Education, Experience, Certification/Licensure, Other. Could be list.

      • Education: Bachelor's degree in Pharmacy. Doctoral degree in pharmacy (PharmD) preferred.
      • Experience: Two (2) years of experience in a pharmacy, OR One (1) year post-baccalaureate or post-doctoral/post-graduate pharmacy residency (PGY1) plus one (1) year of experience, OR Two (2) years post-baccalaureate or post-doctoral/post-graduate pharmacy residency (PGY2).
      • Certification/Licensure: Current Maryland licensure in good standing to practice as a pharmacist or a federal district licensure where the work will be performed upon hire. Certification in a relevant specialty by the Board of Pharmacy Specialties or Commission for Certification in Geriatric Pharmacy Board such as Certified Psychiatric Pharmacist (BCPP) or Board-Certified Geriatric Pharmacist (BCGP) eligibility preferred.
      • Other: Candidates selected for employment may be subject to medical inquiries and/or medical examinations to determine ability to perform the job. Employees in this job class may be subject to pre-employment and random drug testing.
      But we also have location and vaccine requirement; could add another
    • under Requirements: "All employees are expected to work primarily physically within the State of Maryland. Employees whose job duties require them to work in a clinical setting or at clinical or field sites are required to comply with the COVID-19 vaccine requirements of those specific sites." Alternatively, could add a separate paragraph after list.

      Qualifications

      Preferred qualifications: Doctoral degree in pharmacy (PharmD) preferred; Certification in a relevant specialty by the Board of Pharmacy Specialties or Commission for Certification in Geriatric Pharmacy Board such as Certified Psychiatric Pharmacist (BCPP) or Board-Certified Geriatric Pharmacist (BCGP) eligibility preferred.

      But we already included preferred in Requirements; maybe better to separate: Requirements = minimum qualifications (must have). Qualifications = preferred qualifications. Thus: Requirements (minimum): - Education: Bachelor's degree in Pharmacy (required). Doctoral degree in pharmacy (PharmD) preferred? Actually preferred is not required. So we need to separate. Let's parse: Minimum Qualifications Education: Bachelor's degree in Pharmacy. Doctoral degree in pharmacy (PharmD) preferred. Experience: Two (2) years of experience in a pharmacy, OR One (1) year post-baccalaureate or post-doctoral/post-graduate pharmacy residency (PGY1) plus one (1) year of experience, OR Two (2) years post-baccalaureate or post-doctoral/post-graduate pharmacy residency (PGY2). Certification/Licensure: Current Maryland licensure in good standing to practice as a pharmacist or a federal district licensure where the work will be performed upon hire. Certification in a relevant specialty by the Board of Pharmacy Specialties or Commission for Certification in Geriatric Pharmacy Board such as Certified Psychiatric Pharmacist (BCPP) or Board-Certified Geriatric Pharmacist (BCGP) eligibility preferred. Other: Candidates selected for employment may be subject to medical inquiries and/or medical examinations to determine ability to perform the job. Employees in this job class may be subject to pre-employment and random drug testing. Thus minimum:

Similar jobs

Advanced Pharmacist

HCA Houston HealthcareHouston, TX· 2 wk ago
Healthcareapply on careers.hcahealthcare.com

Advanced Pharmacist

HCA HealthcarePort St Lucie, FL· 1 mo ago
Healthcareapply on careers.hcahealthcare.com