Behavior Hlth Spec I

The user wants me to reformat a job posting into clean semantic HTML. Let me analyze the content and structure it according to the rules. First, I need to identify the sections: - Job Responsibilities (detailed list) - Job Qualifications (brief) - About Us (company info) - Some metadata at the top (location, department, shift, schedule, hours, pay range) 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 - Remove boilerplate (EEO, equal opportunity, scam warnings, application instructions) - Include section ONLY when real specific content exists - Never emit heading with filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Output ONLY HTML fragment, no html/body, no markdown fences Looking at the content: Top metadata: - Primary Location: Burnet Campus - Department: Transport - Shift: 2-3 Shift (United States of America) - Schedule: Full time - Weekly Hours: 40 - FTE: 1 - Employee Status: Regular - Expected Starting Pay Range: $21.14 - $26.47 with details This metadata could go into a "Schedule" or "Pay" section? The rules say only create Pay/Schedule sections if posting actually states them. It does state pay range and schedule details. But also says "fold minor metadata into a short

  or drop it". The pay range is substantive. Schedule details are substantive. I think I should include a "Pay" section with the pay range details, and maybe a "Schedule" section with shift/schedule/hours. But the rules say "Prefer a few substantive sections over many thin ones." Could combine into one "Position Details" section? But the allowed headings are specific: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I should use those headings. The posting has: - Job Responsibilities (very detailed) - Job Qualifications (brief) - About Us (company description) - Pay range info - Schedule info No explicit Benefits section, but "Additional pay (e.g., shift, on‑call, or weekend differentials) and benefits may apply." That's vague, not specific benefits. So no Benefits section. No Skills section separate from qualifications. I'll create sections: 1. Pay (since pay range given) 2. Schedule (since shift, schedule, hours given) 3. Responsibilities (the main duties) 4. Qualifications (the requirements) 5. About the role (maybe the "About Us" but that's company, not role. The heading "About the role" is allowed. But the content is "About Us" company info. Could put under "About the role" or maybe not include? The rules say include section ONLY when posting has real specific content for it. The posting has "About Us" section. That's about the company, not the role. But the allowed headings include "About the role". Could rename? Better to include as "About the organization" but not in allowed list. The allowed headings are fixed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About Us" is not in list. Could fold into a paragraph at top? Or maybe create "About the role" with company info? The rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." suggests those are examples, but likely they want those exact headings. I'll use "About the role" for the company description? But that's not about the role. However, the posting includes "About Us" which is company info. I think I should include it as a section, maybe "About the organization" but not in list. The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says "e.g." meaning for example. But they might expect only those. However, the posting has "About Us" which is substantive. I'll include it as "About the organization" but that's not in the list. Safer to include as "About the role" with the company description? That seems off. Alternatively, I could put the company description in a paragraph at the beginning without a heading? But the rule says use h3 for section headings. The company description is a section in the posting. I'll create a section "About the organization" but the instruction says "use

  for section headings (e.g. About the role, ...)". It doesn't forbid other headings, but says "e.g." So I can use other headings? But they said "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings". They didn't say only those headings. But they gave examples. I think it's okay to have "About Us" as a heading. However, to be safe, I'll use "About the role" for the company description? That's misleading. Let me re-read: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests those are the typical sections. The posting has "About Us" which is not exactly "About the role". But many job postings have "About Us" as a section. I'll include it as "About the organization" but maybe they'd consider that not in the list. However, the instruction says "include a section ONLY when the posting has real, specific content for it". The posting has "About Us" with specific content. So I should include it. I'll use

  About Us

  as it's a clear section. But the examples are just examples. I'll proceed with the sections that have content. Let's structure: - Pay section: with pay range details. - Schedule section: with shift, schedule, hours, FTE, employee status. - Responsibilities section: the long list of duties. - Qualifications section: the qualifications. - About Us section: the company description. I'll omit the EEO boilerplate at the end. Now, for Responsibilities: it's a long list of bullet points. The posting uses paragraphs with multiple sentences. I need to convert to
  • for list of duties. The responsibilities are grouped under subheadings: "Team Member", "Environment Management and Care Delivery", "Patient Plan of Care", "Clinical Activity", "Relationship Development /Communication", "Documentation and Data Management". I could keep those as subheadings? But the rule says use

    for section headings, and

    • for any list of duties/requirements/benefits. It doesn't mention subheadings. I could either make each subheading an

      ? But the instruction only mentions

      for section headings. It says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other heading levels, but to keep simple, maybe I should just make a single Responsibilities section with a list of all duties as

      items. However, the content is long and grouped. I could create sub-lists? But the rule says "use

      • for any list of duties". I think I should break down the responsibilities into individual bullet points. The posting has paragraphs separated by blank lines. Each paragraph could be a bullet point. But some paragraphs are long with multiple sentences. I'll split into logical bullet points. Better to preserve the structure: maybe use

        for sub-sections? The instruction doesn't forbid. But to be safe, I'll keep only

        for main sections and use

        • for duties. I'll combine all responsibilities into one list, but that might be huge. Alternatively, I could create multiple
          lists under the same Responsibilities heading, each preceded by a bold label? But that's not semantic. I think using

          for subheadings is acceptable as they are subsections. The instruction says "use

          for section headings" implying top-level sections. Subsections could be

          . I'll do that. Similarly for Qualifications, it's short. Now, let's write HTML. First, Pay section:

          Pay

          Expected Starting Pay Range: $21.14 - $26.47 per hour. Starting pay is based on experience, skills, and equity; exceptions may apply for highly qualified candidates. Additional pay (e.g., shift, on‑call, or weekend differentials) and benefits may apply. Annual pay may vary based on FTE status.

          Schedule section:

          Schedule

          • Primary Location: Burnet Campus
          • Department: Transport
          • Shift: 2-3 Shift (United States of America)
          • Schedule: Full time
          • Weekly Hours: 40
          • FTE: 1
          • Employee Status: Regular
          Responsibilities section:

          Responsibilities

          Then subsections with

          and

          • . But the rule says "use

            for section headings". It doesn't say not to use

            . I'll use

            for subheadings. Let's parse responsibilities: 1. Team Member - Accountable for delivering patient care... (paragraph) 2. Environment Management and Care Delivery - Coordinates the assigned area... (multiple paragraphs) 3. Patient Plan of Care - Implement/document the patient's response... (multiple paragraphs) 4. Clinical Activity - Leads psychoeducation and recreational group activities... (multiple paragraphs) 5. Relationship Development /Communication - Provides trauma informed... (multiple paragraphs) 6. Documentation and Data Management - Assures seclusion and restraint documentation... (multiple paragraphs) 7. Final paragraph: "Care delivery occurs in a team fashion..." I'll make each subheading an

            and each paragraph a

            ? But some subheadings have multiple paragraphs. I'll make each paragraph a separate

            under that subheading. Alternatively, I could make each subheading a

            with the content as text? But the rule says use

            • for any list of duties. So each duty is a list item. The subheadings are categories. I'll do:

              Responsibilities

              Team Member

              • Accountable for delivering patient care by following processes and procedures and demonstrates resilience by being receptive to ongoing instruction, coaching, and feedback.
              • Take ownership of personal clinical development by actively engaging with advanced team members and the multidisciplinary team, exhibits curiosity, and proactively seeks out knowledge and learning opportunities.
              • Leverages practical experience to identify recurring patterns, recognizing behaviors and proactively anticipating typical reactions.
              • Supports the team by sharing knowledge to enhance overall clinical proficiency and foster a collaborative learning environment.
              • Adapts communication style to effectively listen and communicate with a diverse group, including our patients, their families, and the multidisciplinary team.

              Environment Management and Care Delivery

              • Coordinates the assigned area by utilizing the following components: safety, structure, planning, participation, and support.
              • Performs environmental checks while adhering to patient safety and treatment schedules.