IT Support Technician

The user wants me to convert this job posting into clean semantic HTML. I need to follow the rules: use

for section headings,

• for lists,

  for prose. Don't repeat job title as heading. Don't include Job ID/requisition numbers. Preserve all substantive info. Remove boilerplate. Only include sections with real content. No filler text. Output only HTML fragment. Let me analyze the content: 1. Position Summary - prose description 2. Work Schedule - specific: Monday through Friday 7:30am-4pm 3. Essential Job Duties - multiple subsections with lists: - EHR Management - Ongoing Technical Support - Training Coordination - SharePoint Form Development - Google Workspace Management 4. Additional Job Responsibilities - list 5. Supervisory Functions - statement (no supervisory duties) 6. Requirements - with subsections: - Education And Experience Required - Knowledge, Skills, And Abilities Required - Other Requirements 7. Working Conditions - list I should structure this with appropriate headings. The rules say use

  for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But I should only include sections that have real content. Let me map: - "About the role" could be Position Summary - "Schedule" for Work Schedule - "Responsibilities" for Essential Job Duties (with subsections) - "Additional responsibilities" for Additional Job Responsibilities - "Supervisory functions" maybe not needed as separate heading if just one line - "Requirements" or "Qualifications" for Requirements section - "Working conditions" for Working Conditions The rules say: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I should use those standard headings where appropriate. I'll create: -

  About the role

  for Position Summary -

  Schedule

  for Work Schedule -

  Responsibilities

  for Essential Job Duties (with subsections as nested lists or maybe subheadings? But rules say only

  for section headings. Could use

  ? Not specified. Better to keep flat with

  for main sections and use lists for sub-items. The subsections (EHR Management, etc.) are categories of duties. I could make them

  but not in rules. I'll include them as bold text within list items or as separate list headers? The rule: "Use

  • for any list of duties/requirements/benefits". So I can have a list where each item is a category with sub-list. That would be nested
    . That's acceptable. -

    Additional responsibilities

    for Additional Job Responsibilities -

    Requirements

    for Requirements (with subsections as nested lists) -

    Working conditions

    for Working Conditions Supervisory Functions is just a statement, could be a paragraph under Requirements or separate. I'll include as a paragraph under Requirements or separate small section. But rules: "include a section ONLY when the posting has real, specific content for it". It has content: "This position does not have supervisory duties." That's specific. Could be a paragraph under a heading "Supervisory functions". But not in example headings. I'll include as a paragraph under Requirements or as a separate

    Supervisory functions

    . The example headings include "Qualifications, Skills, Benefits, Pay, Schedule". Not supervisory. I'll fold into Requirements as a paragraph. Also note: "Work Schedule: Monday through Friday 7:30am-4pm" is specific, so include Schedule section. Now, ensure no boilerplate: The text includes "As an IT Support Technician, you will serve as a cornerstone..." that's part of position summary? Actually it's after the duties list, before Additional Job Responsibilities. It's more prose about role. I'll include in About the role. Also "For employees with a history of substance use disorder, Fora Health’s policy requires certification of a minimum of six months of sobriety for this position." That's under Other Requirements. Now produce HTML. I'll write:

    About the role

    ...position summary prose...

    As an IT Support Technician, you will serve as a cornerstone...

    Schedule

    Monday through Friday, 7:30am–4:00pm

    Responsibilities

    • EHR Management
      • Document, group session, and schedule creation and maintenance.
      • Manage lab orders and medication orders.
      • Administer user creation and permissions.
      • Collaborate with EHR support team to identify and address errors and bugs.
      • Coordinate with Billing team to ensure accurate coding for claims processing.
    • Ongoing Technical Support
      • Provide daily troubleshooting and coaching to end users.
      • Address application and equipment issues promptly.
      • Maintain system setup, including user management and permissions.
      • Manage error queues and ensure resolution through ticketing system.
      • Communicate EHR or workflow changes to end users.
      • Collaborate with clinical staff for system improvements.
      • Coordinate with IT vendor for support.
      • Assist in IT equipment allocation using inventory management system.
    • Training Coordination
      • Coordinate and conduct training for new clinic staff and providers.
      • Identify opportunities for additional training for existing staff.
    • SharePoint Form Development
      • Manage the lifecycle of SharePoint form and List reporting requests.
      • Validate and write reports to extract necessary information in usable format.
    • Google Workspace Management
      • Configure Google Workspace for efficient Chromebook deployment.
      • Provision Chromebooks, manage device policies, and deploy apps/extensions.
      • Provide comprehensive training on Google Workspace tools.
      • Ensure Chromebook setups adhere to security protocols and compliance standards.
      • Address technical issues and perform routine maintenance tasks for Chromebook setup.

    Additional responsibilities

    • Attend staff meetings as scheduled.
    • Complete additional training as assigned in a timely manner.
    • Perform special projects and other duties as assigned.
    • Participate in ongoing supervision.
    • Attend appropriate clinic department meetings as EHR expert/liaison.

    Requirements

    Education and experience

    ... but rules say only

    for section headings. Could use

    for each subsection? But that would be many headings. The example headings include "Qualifications, Skills". I could split Requirements into Qualifications and Skills. But the posting has "Education And Experience Required", "Knowledge, Skills, And Abilities Required", "Other Requirements". I'll make them subsections under Requirements using

    ? Not allowed. The rule: "use

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

    , but says use

    for section headings. I think they want only

    for top-level sections. Subsections can be handled with bold or nested lists. I'll keep Requirements as one section with nested lists for each category. So:

    Requirements

    • Education and experience
      • Associate’s degree in information systems, computer science, or a related field preferred.
      • Minimum of 1 year of professional, full-time work experience required, preferably in a healthcare environment.
      • Experience with Electronic Health Record (EHR) systems preferred.
      • Certification in relevant technologies (e.g., CompTIA A+, Microsoft Certified Professional, Google Workspace Administrator) preferred.
    • Knowledge, skills, and abilities
      • Proficient in relevant computer applications — MS Office Suite.
      • Communicate information effectively in writing and verbally.
      • Maintain confidentiality of sensitive information and documents.
      • Strong initiative and problem-solving skills, organized, attention to detail, effective communication, ability to remain calm and focused under pressure.
      • Comfortable working with clinical, non-clinical, and IT staff members.
      • Patience supporting non-technical end users using a highly technical EHR.
      • Ability to understand EHR software use and workflows and how those relate to data definitions and reporting.
      • Ability to work independently as well as collaboratively.
      • Flexible, adaptable, and resourceful, with a willingness and ability to self-teach and learn quickly.
      • Maintain a professional demeanor especially under stressful circumstances.
      • Willingness to perform a wide range of tasks.
    • Other requirements
      • For employees with a history of substance use disorder, Fora Health’s policy requires certification of a minimum of six months of sobriety for this position.
      • Ability to pass a pre-employment or for-cause drug test.
      • Ability to pass DHS criminal background check.

    Working conditions

    • Prolonged use of computer.
    • Position generally works in an indoor office environment with infrequent travel between sites or to special events.
    • Position requires some overtime, including evening and weekend work.
    • Position generally works in an indoor office environment with occasional travel between sites or to special events.
    • Possible exposure to communicable diseases which can encompass a variety of illnesses and infections, including COVID, tuberculosis, Hepatitis A, B, and C, and HIV.
    • Possible exposure to upset, angry, severely traumatized, disabled or emotionally disturbed adults, adolescents, and families.
    • Exposure to potentially hazardous cleaning chemicals; personal protective equipment provided.
    • Fast-paced, high-volume work environment.
    Note: There's duplicate line about indoor office environment. I'll keep both? The posting has two similar lines: "Position generally works in an indoor office environment with infrequent travel between sites or to special events." and "Position generally works in an indoor office environment with occasional travel between sites or to special events." Slight difference: infrequent vs occasional. I'll include