Austin 20 (Parmer/McNeil) RX Tech - Pharmacy Tech - Part time

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and structure it according to the rules. The posting has: - Job Summary (but the user said not to repeat job title as heading, and this is a summary) - Key Responsibilities & Essential Functions with subsections: Pharmacy Operations, Compliance - Qualifications & Key Requirements with subsections: Age Requirement, Work Experience, Knowledge/Skills/Abilities, Education, Licenses/Certifications, Physical Demands & Working Conditions I need to use

for section headings. The user said: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I should map the sections accordingly. Looking at the content: - "Job Summary" could be "About the role" or just a paragraph - "Key Responsibilities & Essential Functions" -> "Responsibilities" - "Qualifications & Key Requirements" -> "Requirements" or "Qualifications" The user said: "Do NOT repeat the job title as a heading (the page already shows it)". The job title isn't explicitly in the text provided, but "H-E-B Pharmacy Tech" is mentioned. I should not include that as a heading. Also: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." There's "Last revised: 9/1/2012" which is metadata. I'll include it as a short

at the end or drop it. Probably drop it as it's not substantive. "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." None of that appears here. "Preserve ALL substantive information; do NOT invent or summarize away detail." "Use

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

  for prose." "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text" "Prefer a few substantive sections over many thin ones." I'll structure as: -

  About the role

  with the job summary as

  -

  Responsibilities

  with two subsections: Pharmacy Operations and Compliance. But the user said use

  for section headings. Should I use

  for each subsection? The example shows "Responsibilities" as a heading. The content has two clear categories: Pharmacy Operations and Compliance. I could make them

  but the user only mentioned

  . The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid subheadings, but says "use

  for section headings". I think I should use

  for main sections only. For subsections, maybe use

  or just bold? But the user said output ONLY HTML fragment, no markdown. I could use

  for subsections. However, the instruction says "use

  for section headings". It doesn't say not to use other heading levels. But to be safe, I'll use

  for main sections and for subsections I'll use

  or just incorporate into lists. Alternatively, I can make "Pharmacy Operations" and "Compliance" as separate

  sections? But they are subsections of Responsibilities. The user said "Prefer a few substantive sections over many thin ones." So maybe keep Responsibilities as one section with two lists. I'll do: -

  About the role

  -

  Responsibilities

  with two
  lists, each preceded by a

  Pharmacy Operations

  or something. But the user said use
  • for any list. I can use a heading for each list? The instruction doesn't specify. I think using

    is acceptable semantic HTML. But the user might expect only

    . Let's see: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". That suggests those are the only headings. So I should not create additional headings like "Pharmacy Operations". Instead, I can include them as part of the list items or as a paragraph. I'll structure Responsibilities as a single section with two lists, each introduced by a paragraph with strong text. Similarly for Qualifications & Key Requirements: I'll make a

    Requirements

    section (or Qualifications). The example includes both "Requirements" and "Qualifications". The posting has "Qualifications & Key Requirements". I'll use "Qualifications" as heading. Under Qualifications, there are multiple categories: Age Requirement, Work Experience, Knowledge/Skills/Abilities, Education, Licenses/Certifications, Physical Demands & Working Conditions. I'll make each a list with a leading paragraph. Now, the user said: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting mentions "Work rotating shifts to meet business needs (includes nights and weekends)" under Physical Demands. That's schedule info but not a separate section. I'll keep it under Physical Demands. Also, "Last revised: 9/1/2012" is metadata. I'll drop it. Now, let's write the HTML. I'll start with

    About the role

    As an H-E-B Pharmacy Tech, you'll work in a team environment, helping ensure we exceed patient expectations while delivering excellent, accurate, and efficient services.

    Then

    Responsibilities

    Pharmacy Operations

    • Role models / provides superior customer service and service standards
    • Promotes / embodies "Greet, Ask & Thank" and H-E-B telephone strategies
    • Manages exception station; solves third-party issues
    • Receives / processes written prescriptions from customers using RxEVO; verifies complete patient information to input into the computer system; processes third-party prescriptions; manages adjudication review
    • Coordinates Rx screening events, flu shot scheduling, immunization scheduling, and future events; may be responsible for other Professional Services activities as required
    • Maintains H-E-B Rx screener status; participates in screening events
    • Assists with Pharmacy operations-related tasks (e.g., responding to recalls, offsite record storage, DSD reconciliation, out-of-date / dead stock returns, department communications, and others as needed)
    • Orders / manages inventory; processes invoices daily, on a timely basis
    • Reviews Warehouse and DSD orders
    • Checks deliveries for accuracy; notifies H-E-B / DSD vendor of discrepancies; makes necessary adjustments
    • Maintains automated prescription processing equipment (e.g., Kirby Lester, ScriptPro, etc.), including calibration, maintenance, stocking, proper report execution
    • Applies computer troubleshooting and prescription application overview
    • Processes RxIMS reports (count compliance, no location inventory, order overrides, etc.)
    • Performs other assigned duties

    Compliance

    • Performs prescription assembly (with Kirby Lester, ScriptPro, and other tools); hand-counts controlled medications; measures liquids; reconstitutes antibiotics; verifies / labels prescriptions by 7-point check
    • Ensures privacy / confidentiality of Personal Health Information (PHI) as required by HIPAA; ensures proper procedures are followed related to prescription delivery to a patient
    • Ensures compliance with Central Fill check-in procedures
    • Participates in / ensures Pharmacy Partner compliance with ORT, 5-S, and Pharmacy Standards Review
    • Ensures proper return to stock (RTS) procedures are followed; responsible for organization / presentation of pharmacy shelves
    • Participates in / supports Pharmacy Manager in facility and office maintenance and upkeep; ensures 5-S compliance

    The responsibilities and essential functions outlined above describe the general nature and level of work assigned to this position. This is not an exhaustive list of all duties, responsibilities, and skills required. Duties and responsibilities may be modified at any time based on business needs. Employees may be required to perform other job-related tasks as requested by their supervisor, subject to reasonable accommodations.

    Then

    Qualifications

    Age Requirement

    • 18+

    Work Experience

    • 3+ years of pharmacy experience (preferred)
    • 1+ years of experience as an active retail Certified Pharmacy Technician
    • Experience working in a fast-paced environment

    Knowledge/Skills/Abilities

    • Working knowledge of all pharmacy-related management tasks and H-E-B RxEVO system
    • Knowledge / understanding of H-E-B Pharmacy Standard Operating Procedures (SOPs)
    • Advanced communication skills; advanced telephone etiquette
    • Intermediate computer skills, including MS Office, Windows, and H-E-B related systems / applications (e.g., RxEVO, RxIMS, PartnerNet, Workforce Manager)
    • Mathematical skills, including calculating measurements
    • Ability to manage multiple priorities and shift focus between tasks
    • Ability to maintain composure in high-stress situations
    • Ability to work with little direct supervision; self-starter
    • Welcomes working in a team-oriented environment and is open to cross-training

    Education

    • HS Diploma or GED or equivalent

    Licenses/Certifications

    • Active State of Texas registration as certified pharmacy technician (CPhT); maintain certification with 20 hours of continuing education every 2 years; recertify 60 days prior to expiration date
    • Certification as an H-E-B Pharmacy Technician
    • RxEVO certification
    • Successful completion of all required training (e.g., H-E-B Screener certification, Advanced Cash Register (ACR), HIPAA, FWA, MethGuard, Diversity, Company orientation, applicable modules for Pharm Tech and PCR, etc.)

    Physical Demands & Working Conditions

    • Function in a fast-paced, retail, office environment
    • Work rotating shifts to meet business needs (includes nights and weekends)
    • Stand for extended periods (up to 12 hours)
    • Regularly lift 30 lbs or more
    • Use arms / hands in repetitive motion that require hand / finger dexterity
    • Meet specific vision requirements for this job, including close vision and color vision

    The work environment characteristics described here are representative of those a Partner encounters while performing the essential functions of this job. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions.

    That seems comprehensive. I'll output only the HTML fragment. No markdown fences. Ensure no extra whitespace. Use proper HTML entities for special characters? The text includes "&" which should be & in HTML. But the user didn't specify. I'll keep as