Staff Pharmacist - Night Shift
` for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use `- ` for any list of duties/requirements/benefits
- Use `
` for prose
- Do NOT repeat the job title as a heading (page already shows it)
- Do NOT put Job ID / requisition numbers as headings - fold minor metadata into a short `
` or drop it
- Preserve ALL substantive information; do NOT invent or summarize away detail
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
- IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them
- Prefer a few substantive sections over many thin ones
- Output ONLY the HTML fragment — no `/`, no markdown code fences
2. **Analyze the Input Text:**
Let me parse the job posting content. It's from Houston Methodist Hospital, Staff Pharmacist position, Full time - Nights.
Key sections I can identify:
- Job title/context: "Come lead with us at Houston Methodist Hospital Full time - Nights At Houston Methodist, the Staff Pharmacist position is responsible for..."
- FLSA STATUS: "Non-exempt"
- QUALIFICATIONS:
- EDUCATION: "Graduate of education program approved by the credentialing body for the required credential(s) indicated below in the Certifications, Licenses and Registrations section"
- EXPERIENCE: "No experience needed; some experience applicable to the specific work setting (e.g., hospital, specialty pharmacy) highly preferred"
- LICENSES AND CERTIFICATIONS: Required list (PHRM, PPC, IV Certification, BLS) and Preferred (ACLS)
- KNOWLEDGE AND ABILITIES: Several bullet points
- ESSENTIAL FUNCTIONS:
- PEOPLE ESSENTIAL FUNCTIONS
- SERVICE ESSENTIAL FUNCTIONS
- QUALITY/SAFETY ESSENTIAL FUNCTIONS
- FINANCE ESSENTIAL FUNCTIONS
- GROWTH/INNOVATION ESSENTIAL FUNCTIONS
- SUPPLEMENTAL REQUIREMENTS:
- WORK ATTIRE: Uniform, Scrubs, Business professional, Other
- ON-CALL*
- TRAVEL**
- END: "Houston Methodist is an Equal Opportunity Employer." (This is boilerplate to remove per instructions)
I need to map these to the requested heading format:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But I should only include sections that have real content. I need to be careful not to create sections with placeholder text.
Let's re-read the heading examples: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". These are suggestions, but I should use meaningful headings that match the content, and only include those that have substance.
Rules to strictly follow:
- Do NOT repeat the job title as a heading
- Do NOT put Job ID / requisition numbers as headings
- Remove EEO/equal-opportunity/scam-warning boilerplate
- Preserve ALL substantive information; do NOT invent or summarize away detail
- Include a section ONLY when the posting has real, specific content for it
- Never emit a heading followed by filler/placeholder text
- Never create Pay/Schedule/Benefits sections unless the posting actually states them
- Output ONLY the HTML fragment — no /, no markdown code fences
Let's plan the structure. I need to decide on headings that match the content and the requested format, but only where there's real content.
Possible mapping:
- The posting starts with a description. I could use "About the role" or similar, but the instructions say "do NOT repeat the job title as a heading (the page already shows it)". The job title is "Staff Pharmacist". I shouldn't make a heading for it. I could have a brief intro paragraph, or map the first part to "About the role" but carefully. Actually, the rule says "do NOT repeat the job title as a heading (the page already shows it)". So I shouldn't have an `Staff Pharmacist
`. I can have other headings.
Let's list the actual content sections and see what heading to use:
1. "At Houston Methodist, the Staff Pharmacist position is responsible for providing day-to-day comprehensive, patient-oriented, pharmacy services in any or all areas of the department which includes processing orders, therapy review, and education to patients and other members of the direct patient care team. This position collaborates with other health care professionals to manage patients' drug therapies for effectiveness and overall safety. The Staff Pharmacist position contributes to the fulfillment of the department's mission by collaborating to provide innovative, personalized, cost-effective pharmaceutical care in a culture dedicated to quality and safety. This position is also responsible for the oversight of pharmacy technicians and students and may serve as a preceptor, ensuring the accurate and timely delivery of pharmaceuticals."
This is a general description. I could put this under `About the role
` but need to be careful. The rule says "include a section ONLY when the posting has real, specific content for it". This section has real content. I'll use "About the role" or maybe "Role description". The examples listed "About the role" as a suggestion. I think it's fine to use it, as long as there's real content.
2. "FLSA STATUS Non-exempt" - This is metadata. The rule says "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." FLSA status is minor metadata. I'll fold it into a
perhaps, or just include it naturally. But I need to see if it's better as part of an intro or a separate line. I'll likely put it in a
somewhere, or maybe under a heading if it fits, but the rule says fold minor metadata into a short
or drop it. I'll put it in a
tag, maybe after the role description.
3. QUALIFICATIONS section has:
- EDUCATION
- EXPERIENCE
- LICENSES AND CERTIFICATIONS (Required and Preferred)
- KNOWLEDGE AND ABILITIES
4. ESSENTIAL FUNCTIONS has sub-sections:
- PEOPLE ESSENTIAL FUNCTIONS
- SERVICE ESSENTIAL FUNCTIONS
- QUALITY/SAFETY ESSENTIAL FUNCTIONS
- FINANCE ESSENTIAL FUNCTIONS
- GROWTH/INNOVATION ESSENTIAL FUNCTIONS
5. SUPPLEMENTAL REQUIREMENTS:
- WORK ATTIRE
- ON-CALL*
- TRAVEL**
6. "Houston Methodist is an Equal Opportunity Employer." - Remove per instructions.
Now, I need to map these to the requested headings: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". But I should only use those that have content. The posting doesn't have "Benefits", "Pay", or "Schedule" sections with actual content. It has "FLSA STATUS" but that's not Pay/Schedule. It has "ON-CALL*" and "TRAVEL**" but those are supplemental requirements, not exactly Benefits/Pay/Schedule. The rule says: "never create Pay/Schedule/Benefits sections unless the posting actually states them". Since there's no actual Pay/Schedule/Benefits text, I should NOT create those sections.
So I'll include sections that have real content:
- About the role (the main description)
- Responsibilities (maybe merge with about the role, or use the essential functions)
- Requirements (qualifications, licenses, etc.)
- Qualifications (education, experience, licenses, knowledge)
- Skills (maybe part of knowledge and abilities)
- Essential functions could map to Responsibilities or be separate.
Let's re-read carefully: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." These are examples of valid heading names. I can choose which ones to use, as long as they're semantic and match content. I should prefer a few substantive sections over many thin ones.
Let's outline what content I'll include:
- I'll start with a `About the role
` and put the main description paragraph.
- Then `Responsibilities
` or maybe merge essential functions there. But the essential functions are quite detailed and structured. I could use `Essential functions
` but the examples say "Responsibilities". I think "Responsibilities" is fine, or I can use "Essential functions". The rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't restrict me to exactly those, but I should use similar semantic names. I'll likely use "About the role", "Requirements", "Qualifications", "Essential functions" or "Responsibilities". Let's see.
Actually, the posting has "QUALIFICATIONS" as a heading in the source, and "ESSENTIAL FUNCTIONS" as another heading. I should map them appropriately. The rule says "do NOT repeat the job title as a heading". It doesn't forbid using headings that appear in the posting. I'll use "About the role", "Requirements", "Qualifications", "Essential functions", "Supplemental requirements". But I need to be careful not to create too many thin sections. The rule: "Prefer a few substantive sections over many thin ones."
Let's decide on sections that have enough substance:
1. "About the role" - the introductory description of the position. Has real content.
2. "Requirements" - could cover FLSA status, qualifications, licenses, knowledge/abilities. But "Requirements" might overlap with "Qualifications". I'll use "Qualifications" for the education/experience/licenses part, and maybe fold FLSA into a paragraph.
3. "Essential functions" - the detailed essential functions section. Has real content.
4. "Supplemental requirements" - work attire, on-call, travel. Has real content.
But the examples list: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I should probably use a subset that matches. Let's map:
- "About the role" → the main description
- "Responsibilities" → could be the essential functions, or I can use "Essential functions" but the rule says "use for section headings (e.g. ... Responsibilities ...)". I think it's safer to use the exact suggested names if I use them, but I don't have to use all. I'll use "About the role", "Requirements", "Qualifications", and maybe "Skills" if there's content. The "Knowledge and abilities" section could be "Skills".
- I won't create "
` for prose - Do NOT repeat the job title as a heading (page already shows it) - Do NOT put Job ID / requisition numbers as headings - fold minor metadata into a short `
` or drop it - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions - IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no `/`, no markdown code fences 2. **Analyze the Input Text:** Let me parse the job posting content. It's from Houston Methodist Hospital, Staff Pharmacist position, Full time - Nights. Key sections I can identify: - Job title/context: "Come lead with us at Houston Methodist Hospital Full time - Nights At Houston Methodist, the Staff Pharmacist position is responsible for..." - FLSA STATUS: "Non-exempt" - QUALIFICATIONS: - EDUCATION: "Graduate of education program approved by the credentialing body for the required credential(s) indicated below in the Certifications, Licenses and Registrations section" - EXPERIENCE: "No experience needed; some experience applicable to the specific work setting (e.g., hospital, specialty pharmacy) highly preferred" - LICENSES AND CERTIFICATIONS: Required list (PHRM, PPC, IV Certification, BLS) and Preferred (ACLS) - KNOWLEDGE AND ABILITIES: Several bullet points - ESSENTIAL FUNCTIONS: - PEOPLE ESSENTIAL FUNCTIONS - SERVICE ESSENTIAL FUNCTIONS - QUALITY/SAFETY ESSENTIAL FUNCTIONS - FINANCE ESSENTIAL FUNCTIONS - GROWTH/INNOVATION ESSENTIAL FUNCTIONS - SUPPLEMENTAL REQUIREMENTS: - WORK ATTIRE: Uniform, Scrubs, Business professional, Other - ON-CALL* - TRAVEL** - END: "Houston Methodist is an Equal Opportunity Employer." (This is boilerplate to remove per instructions) I need to map these to the requested heading format:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But I should only include sections that have real content. I need to be careful not to create sections with placeholder text.
Let's re-read the heading examples: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". These are suggestions, but I should use meaningful headings that match the content, and only include those that have substance.
Rules to strictly follow:
- Do NOT repeat the job title as a heading
- Do NOT put Job ID / requisition numbers as headings
- Remove EEO/equal-opportunity/scam-warning boilerplate
- Preserve ALL substantive information; do NOT invent or summarize away detail
- Include a section ONLY when the posting has real, specific content for it
- Never emit a heading followed by filler/placeholder text
- Never create Pay/Schedule/Benefits sections unless the posting actually states them
- Output ONLY the HTML fragment — no /, no markdown code fences
Let's plan the structure. I need to decide on headings that match the content and the requested format, but only where there's real content.
Possible mapping:
- The posting starts with a description. I could use "About the role" or similar, but the instructions say "do NOT repeat the job title as a heading (the page already shows it)". The job title is "Staff Pharmacist". I shouldn't make a heading for it. I could have a brief intro paragraph, or map the first part to "About the role" but carefully. Actually, the rule says "do NOT repeat the job title as a heading (the page already shows it)". So I shouldn't have an `Staff Pharmacist
`. I can have other headings.
Let's list the actual content sections and see what heading to use:
1. "At Houston Methodist, the Staff Pharmacist position is responsible for providing day-to-day comprehensive, patient-oriented, pharmacy services in any or all areas of the department which includes processing orders, therapy review, and education to patients and other members of the direct patient care team. This position collaborates with other health care professionals to manage patients' drug therapies for effectiveness and overall safety. The Staff Pharmacist position contributes to the fulfillment of the department's mission by collaborating to provide innovative, personalized, cost-effective pharmaceutical care in a culture dedicated to quality and safety. This position is also responsible for the oversight of pharmacy technicians and students and may serve as a preceptor, ensuring the accurate and timely delivery of pharmaceuticals."
This is a general description. I could put this under `About the role
` but need to be careful. The rule says "include a section ONLY when the posting has real, specific content for it". This section has real content. I'll use "About the role" or maybe "Role description". The examples listed "About the role" as a suggestion. I think it's fine to use it, as long as there's real content.
2. "FLSA STATUS Non-exempt" - This is metadata. The rule says "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." FLSA status is minor metadata. I'll fold it into a
perhaps, or just include it naturally. But I need to see if it's better as part of an intro or a separate line. I'll likely put it in a
somewhere, or maybe under a heading if it fits, but the rule says fold minor metadata into a short
or drop it. I'll put it in a
tag, maybe after the role description. 3. QUALIFICATIONS section has: - EDUCATION - EXPERIENCE - LICENSES AND CERTIFICATIONS (Required and Preferred) - KNOWLEDGE AND ABILITIES 4. ESSENTIAL FUNCTIONS has sub-sections: - PEOPLE ESSENTIAL FUNCTIONS - SERVICE ESSENTIAL FUNCTIONS - QUALITY/SAFETY ESSENTIAL FUNCTIONS - FINANCE ESSENTIAL FUNCTIONS - GROWTH/INNOVATION ESSENTIAL FUNCTIONS 5. SUPPLEMENTAL REQUIREMENTS: - WORK ATTIRE - ON-CALL* - TRAVEL** 6. "Houston Methodist is an Equal Opportunity Employer." - Remove per instructions. Now, I need to map these to the requested headings: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". But I should only use those that have content. The posting doesn't have "Benefits", "Pay", or "Schedule" sections with actual content. It has "FLSA STATUS" but that's not Pay/Schedule. It has "ON-CALL*" and "TRAVEL**" but those are supplemental requirements, not exactly Benefits/Pay/Schedule. The rule says: "never create Pay/Schedule/Benefits sections unless the posting actually states them". Since there's no actual Pay/Schedule/Benefits text, I should NOT create those sections. So I'll include sections that have real content: - About the role (the main description) - Responsibilities (maybe merge with about the role, or use the essential functions) - Requirements (qualifications, licenses, etc.) - Qualifications (education, experience, licenses, knowledge) - Skills (maybe part of knowledge and abilities) - Essential functions could map to Responsibilities or be separate. Let's re-read carefully: "use