Health Unit Clerk

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. First, I need to identify the sections: - Job Summary (prose) - Benefits (list) - Job Description / Essential Functions (list) - Preferred Additional Requirements (list with sub-items: Education, Certification, Experience) - Scheduling Requirements (prose) - Physical Requirements (prose) - Some metadata: Primary Location, Department, Scheduled Weekly Hours, Starting Pay Rate Range, Job Category, Job Family, Shift, Employee Type Rules: - Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use

• for lists,

  for prose - Do NOT repeat job title as heading (not provided anyway) - Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short

  or drop - Preserve ALL substantive information; do NOT invent or summarize - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions - Include section ONLY when posting has real, specific content — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment — no /, no markdown code fences Now, let's map content to sections: 1. Job Summary: "Assist the nursing staff..." -> This is "About the role" or "Job Summary". Use

  About the role

  with

  . 2. Benefits: "Monument Health offers competitive wages and benefits on qualifying positions. Some of those benefits can include: ..." followed by a list. This is a Benefits section. Use

  Benefits

  with
  • for each benefit. 3. Job Description Essential Functions: list of duties. This is "Responsibilities". Use

    Responsibilities

    with
    • . 4. Preferred Additional Requirements: Education, Certification, Experience. This is "Qualifications" or "Requirements". Use

      Qualifications

      with
      • for each item. Could be nested but flat list is fine. 5. Scheduling Requirements: "Requires the ability to work assigned schedules and hours as determined by the department." This is schedule info. Could be part of "Schedule" section. But also there is "Shift Requires the ability to work assigned schedules and hours as determined by the department" duplicated. Also "Scheduled Weekly Hours 20" and "Starting Pay Rate Range $17.67 - $20.31". Pay and Schedule are present. Should we include Pay and Schedule sections? The rules: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states Starting Pay Rate Range and Scheduled Weekly Hours, and Scheduling Requirements. So we can include Pay and Schedule sections. However, the user says "Prefer a few substantive sections over many thin ones." We could combine Pay and Schedule into one section? But the headings are predefined: Pay, Schedule. We can include them if they have specific content. 6. Physical Requirements: prose. Could be "Requirements" or "Physical Requirements". Might fit under "Requirements" but we already have Qualifications. Could create a "Physical Requirements" section? Not in the predefined list. The predefined headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Physical Requirements" could be under "Requirements". But we have "Preferred Additional Requirements" which are qualifications. Physical requirements are also requirements. Could make a "Requirements" section that includes both? But the rules say use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use "Requirements" for physical requirements and maybe scheduling? But scheduling is separate. Let's see. Better to structure as: - About the role (Job Summary) - Responsibilities (Essential Functions) - Qualifications (Preferred Additional Requirements) - Physical Requirements (maybe under Requirements? But not in list. Could use "Requirements" heading for physical requirements and maybe other requirements like scheduling? However, scheduling is separate. The posting has "Scheduling Requirements" and "Physical Requirements". Could create a "Requirements" section that includes both? But the predefined headings include "Schedule" for scheduling. So we can have: - Schedule (for Scheduled Weekly Hours, Starting Pay Rate Range? Actually Pay is separate. Schedule includes shift, hours. Pay includes pay rate.) - Pay (for Starting Pay Rate Range) - Physical Requirements? Not in list. Could be under "Requirements" but that might be confused with qualifications. The rules say "Requirements" is a heading example. Could use "Requirements" for physical requirements. But we also have "Qualifications". Usually "Requirements" and "Qualifications" are similar. The posting has "Preferred Additional Requirements" which are qualifications. Physical requirements are also requirements. I think we can create a "Requirements" section for physical requirements and maybe other requirements like "Requires the ability to work assigned schedules..." but that's scheduling. Let's examine the metadata: Primary Location, Department, Scheduled Weekly Hours, Starting Pay Rate Range, Job Category, Job Family, Shift, Employee Type. These are minor metadata. The rules: "fold minor metadata into a short

        or drop it." We can include a short paragraph at the top or bottom with location, hours, pay range, etc. But the user says "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it." So we can create a

        with key details: "Primary Location: Rapid City, SD USA | Department: RCH Emergency Services | Scheduled Weekly Hours: 20 | Starting Pay Rate: $17.67 - $20.31 | Job Category: Nursing | Job Family: Nursing Support | Shift: As assigned | Employee Type: Regular". That's a good summary. Now, we must remove boilerplate: "Current Employees If you are a current Monument Health employee, please apply via the internal career site..." - this is application instructions, remove. "Monument Health is an Equal Opportunity/Affirmative Action employer..." - EEO boilerplate, remove. "Make a difference. Every day." - tagline, remove. "10 Monument Health Rapid City Hospital, Inc." - maybe part of footer, remove. Now, let's construct HTML. Sections: 1. About the role (Job Summary) 2. Responsibilities (Essential Functions) 3. Qualifications (Preferred Additional Requirements) 4. Physical Requirements (maybe under "Requirements"? But not in predefined. Could use "Requirements" heading for physical requirements. However, the predefined list includes "Requirements". I'll use "Requirements" for physical requirements and maybe scheduling? But scheduling is separate. Let's see: The posting has "Scheduling Requirements" and "Physical Requirements". Could combine into a "Requirements" section with two sub-lists? But the rule says use

        • for any list. Could do:

          Requirements

          Scheduling: Requires the ability to work assigned schedules and hours as determined by the department.

          Physical: Medium work - exerting up to 10 pounds of force constantly...

          But the rule says use
          • for any list of duties/requirements/benefits. These are not lists but prose. Could keep as paragraphs. Alternatively, create "Schedule" section for scheduling requirements and "Physical Requirements" as a separate section? But "Physical Requirements" is not in the example headings. The examples are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So "Requirements" could encompass physical requirements. "Schedule" for scheduling. "Pay" for pay rate. Thus: - About the role - Responsibilities - Qualifications - Requirements (physical) - Schedule (scheduling requirements, weekly hours, shift) - Pay (pay rate range) - Benefits But note: "Scheduled Weekly Hours 20" and "Starting Pay Rate Range" are also metadata. Could include in Schedule and Pay sections. Let's decide: The posting has "Scheduled Weekly Hours 20" and "Starting Pay Rate Range $17.67 - $20.31". Also "Shift Requires the ability to work assigned schedules and hours as determined by the department". And "Scheduling Requirements: Requires the ability to work assigned schedules and hours as determined by the department." Duplicate. We'll create: - Schedule section: include weekly hours, shift description, scheduling requirements. - Pay section: include pay rate range. But the rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state them. So we can create. Now, Benefits section: list of benefits. Now, Qualifications: list of preferred additional requirements. Now, Responsibilities: list of essential functions. Now, About the role: job summary. Now, Requirements: physical requirements. We'll also include a brief metadata paragraph at the top or bottom. Probably at the top after About the role? Or before sections. The rules don't specify order. Typically job postings have summary first, then responsibilities, qualifications, benefits, etc. We'll follow logical order. Let's write HTML. We'll start with a

            for metadata: "Primary Location: Rapid City, SD USA | Department: RCH Emergency Services | Scheduled Weekly Hours: 20 | Starting Pay Rate: $17.67 - $20.31 | Job Category: Nursing | Job Family: Nursing Support | Shift: As assigned | Employee Type: Regular" But the pay rate is also in Pay section. Could duplicate? Better to include in metadata and also in Pay section? The rule: preserve all substantive information. It's okay to have in both? Might be redundant. Could include in metadata and not create separate Pay section? But the rule says include Pay section if posting states it. The posting states "Starting Pay Rate Range $17.67 - $20.31". That's specific. So we should have a Pay section. The metadata paragraph can include it as well, but that's okay. Alternatively, we can omit metadata paragraph and rely on sections. But the metadata includes location, department, job category, etc. Those are not covered in sections. The rules: "fold minor metadata into a short

            or drop it." So we should include a short

            with those details. Let's place it at the beginning. Now, write HTML. Note: Use

            for headings. Use

            • for lists. Use

              for prose. Let's draft:

              Primary Location: Rapid City, SD USA | Department: RCH Emergency Services | Scheduled Weekly Hours: 20 | Starting Pay Rate: $17.67 - $20.31 | Job Category: Nursing | Job Family: Nursing Support | Shift: As assigned | Employee Type: Regular

              About the role

              Assist the nursing staff in providing efficient, effective and safe patient care specific to diagnosis and age of patient served, utilizing communication, and clerical skills. This is based on the knowledge of growth and development over the life span. The care is provided under the direction of the nurse in accordance with accepted hospital standards, policies, unit specific competencies and the South Dakota Nurse Practice Act.

              Responsibilities

              • Completes all assigned clerical activities.
              • Contributes to patient care in accordance with unit guidelines.