PUBLIC HEALTH OFFICE ASSISTANT - 09222026-81034

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

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

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate. Include sections only when posting has real specific content. Avoid filler like "commensurate with experience". Pay: posting includes Salary (Monthly) $2,581.00 - $3,870.00 and Salary (Annually) $30,972.00 - $46,440.00. So we can include Pay section with that info. Schedule: not given (full-time but no schedule details). So we should not create Schedule section. Benefits: not given explicitly. No benefits listed. So omit Benefits. We need sections: About the role (Overview), Responsibilities, Qualifications (Education and Experience etc), Skills (maybe Competencies/KSAs). Also maybe "Requirements" could be combined with Qualifications? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose which sections have content. We have Overview (About the role). Responsibilities. Qualifications (Education and Experience). Skills (Competencies, Knowledges, Skills, Abilities, Tools & Equipment). Pay. Possibly also "Requirements" could be same as Qualifications but we can keep Qualifications. We must not repeat job title. No metadata like Opening Date/Time etc. Should we include them? The instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

  or drop it. Opening/Closing dates maybe minor metadata; we could drop them. Probably drop. We need to preserve all substantive information. So we need to include the overview text, responsibilities list, qualifications text (education/experience, substitution rules), competencies etc. Also driver standards? That is a requirement maybe under Requirements? It mentions driver qualifications. Could be part of Requirements. But we have no separate Requirements section; we could include driver qualifications under Qualifications or maybe a separate Requirements section. Since we have Qualifications already, we could add driver qualifications there as part of qualifications. But the instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have a Requirements section for driver qualifications. However we already have Qualifications covering education/experience. Might be okay to have both Requirements and Qualifications. But we need to avoid thin sections. Let's see: driver qualifications is a specific requirement; we could include it under Qualifications as a bullet. Or we could have a Requirements section with that content. Since we already have Qualifications, maybe better to keep Qualifications for education/experience and include driver qualifications there as a bullet. That keeps sections fewer. We need to output only HTML fragment. Structure:

  About the role

  Overview text...

  Responsibilities

  • ...
  ...

  Qualifications

  Education and Experience: ...

  • Substitution of Experience for Education: ...
  • Substitution of Education for Experience: ...

  Competencies (KSA's)...

  maybe we need to break into Knowledges, Skills, Abilities, Tools & Equipment. Could be separate subsections but we can keep as list. Better: after qualifications paragraph, we can have

  Skills

  with lists. But we already used Qualifications heading; we could have Skills separate. Let's decide: Sections: - About the role (Overview) - Responsibilities - Qualifications (Education & Experience) - Skills (Competencies, Knowledges, Skills, Abilities, Tools & Equipment) - Pay We need to include driver qualifications maybe under Qualifications as a bullet. Now extract content. Overview text: "The Public Health Office Assistant (PHOA) provides essential frontline support in Tennessee¿s local health departments, helping ensure smooth clinic operations and high¿quality customer service. PHOAs handle patient check¿in and registration, maintain accurate records, schedule appointments, and support services such as WIC, Vital Records, and TennCare Presumptive Eligibility. They process payments, verify insurance, and manage document scanning while following all policies and confidentiality standards. PHOAs maintain working knowledge of public health programs, communicate effectively with patients and staff, and contribute to efficient clinic flow. Strong customer service skills, attention to detail, and proficiency with electronic health record systems are key. By supporting both daily operations and broader public health initiatives, PHOAs serve as a vital link between the community and the health department." Responsibilities list: many bullet points from "Reviews departmental policies..." to "Handles complaints, settles disputes, and resolves grievances and conflicts, or otherwise negotiates with others." Let's list them: - Reviews departmental policies and procedures to keep abreast of any changes, revisions, or additions. - Discusses with clients all possibilities for assistance within and outside the health department; informs client of rights and responsibilities for participation in various programs. - Interviews health department clients for medical and administrative services while maintaining confidentiality. - Collects and updates client demographic information for registration, schedules appointments, and informs client of any visit requirements. - Reviews and verifies insurance information, financial information, immunization status, program eligibility, and client co-pay/deductible responsibilities. - Discusses charges for services and explains sliding fee scale where applicable. - Prepares medical record for services to be provided, which may include attaching necessary forms, encounter labels, or any special instructions for the medical provider or laboratory. - Performs administrative activities including processing and evaluating information to determine compliance with standards. - Processes and maintains medical and administrative records and reports; reviews client encounter forms for accuracy and enters service/encounter data into the health department computer system. - Creates certificate of deposit to allocate funds to proper program area budget codes and calculates charges to initiate the billing process. - Reconciles fees collected with cash drawer report; collects payments for services rendered. - Serves as the health department representative and effectively communicates all health department services available to the public. - Maintains positive, constructive and cooperative communication by telephone, in written form, email or in person with supervisors, peers or clients. - Handles complaints, settles disputes, and resolves grievances and conflicts, or otherwise negotiates with others. Qualifications: Education and Experience: "Education equivalent to graduation from a standard high school and experience equivalent to two years of full-time customer service delivery and/or clerical/office work." Substitution of Experience for Education: "Qualifying full-time customer service delivery and/or clerical/office support work may substitute for the required education on a year-for-year basis (e.g., experience equivalent to one year of full-time work in one or a combination of the above listed fields may substitute for one year of the required education)." Substitution of Education for Experience: "Course work credit received from an accredited college or university may substitute for the required experience on a year-for-year basis to a maximum of two years (e.g., 45 quarter hours may substitute for one year of the required experience)." Driver qualifications: "State of Tennessee positions that may involve driving responsibilities require candidates to meet the following minimum driver qualifications: A valid driver's license. For the past five years, the candidate's driver record must not have record of the following violations: driving under the influence (DUI), reckless driving, license suspension for moving violations, more than 4 moving violations. Please include your Driver's License Information under the Licenses and Certifications section of your application. Agencies may allow an exception based on other factors." We can include driver qualifications as a bullet under Qualifications. Now Skills/KSAs: The posting lists: Competencies (KSA's) Competencies Customer Focus Interpersonal Savvy Communicates Effectively Drives Engagement Instills Trust Knowledges Clerical Customer and Personal Service Information Technology Telecommunications Sociology and Anthropology Skills Active Learning and Listening Time Management Equipment Operation Reading Comprehension Judgment and Decision Making Abilities Mathematical Reasoning Written Comprehension Perceptual Speed Problem Sensitivity Speech Clarity Tools & Equipment Personal Computer Multi-Line Phone Print/Fax/Copy/Scan Machine iPad Plum Case We can put these under Skills heading with subheadings maybe but we can just list as
  with items grouped? Could separate with

  but not allowed? Only headings

  for sections. We could still use

  inside? Not prohibited but better to keep simple: we can have

  Skills

  then

  Competencies: ...

  etc. But we need to use
  • for any list of duties/requirements/benefits. For competencies etc, they are lists, so we should use
    • . We can have multiple lists under Skills. We could do:

      Skills

      Competencies

      ...

      Knowledges

      ...
      ... But h4 is not prohibited; only instruction says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we could avoid extra headings and just make one big list with all items, but that loses grouping. However we can still use

      with items and maybe include headings as plain text inside
      • ? Not ideal. Better to keep simple: Use

        Skills

        then

        Competencies: Customer Focus, Interpersonal Savvy, Communicates Effectively, Drives Engagement, Instills Trust.

        etc. But that would be prose not list. The instruction: Use
        • for any list of duties/requirements/benefits. For skills/competencies, they are lists but not duties/requirements/benefits. Might be okay to use

          . However to be safe, we can treat them as list and use

          • . We'll just make one list under Skills containing all items, maybe with subheadings as
          • Competencies: ...
          . That's acceptable. Let's do:

          Skills

          • Competencies: Customer Focus, Interpersonal Savvy, Communicates Effectively, Drives Engagement, Instills Trust.
          • Knowledges: Clerical, Customer and Personal Service, Information Technology, Telecommunications, Sociology and Anthropology.
          • Skills: Active Learning and Listening, Time Management, Equipment Operation, Reading Comprehension, Judgment and Decision Making.
          • Abilities: Mathematical Reasoning, Written Comprehension, Perceptual Speed, Problem Sensitivity, Speech Clarity.
          • Tools & Equipment: Personal Computer, Multi-Line Phone, Print/Fax/Copy/Scan Machine, iPad, Plum Case.
          Now Pay section:

          Pay

          Salary (Monthly): $2,581.00 - $3,870.00

          Salary (Annually): $30,972.00 - $46,440.00

          We could also combine into one

          but it's fine. Now About the role: we need

          About the role

          then

          Overview text