Health System Specialist

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. First, I need to identify the sections: 1. Summary/About the role 2. Qualifications (with sub-sections: Individual Occupational Requirement, Specialized Experience, Education, Combination, Preferred Experience) 3. Duties/Responsibilities 4. Work Schedule 5. Telework 6. Position Description/PD# 7. Relocation/Recruitment Incentives 8. Critical Skills Incentive 9. Permanent Change of Station But I need to follow the rules: use

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

• for lists,

  for prose. Don't repeat job title as heading. Don't put Job ID/requisition numbers as headings - fold minor metadata into short

  or drop it. Preserve ALL substantive information. Remove boilerplate. Include section ONLY when posting has real specific content. Never emit heading followed by filler/placeholder text. Never create Pay/Schedule/Benefits sections unless posting actually states them. Looking at the content: - There's a Summary section describing the role - Qualifications section with detailed requirements - Duties section with many bullet points - Work Schedule: Monday-Friday 7:30 AM - 4:00 PM CT - Telework: Ad Hoc Available - Virtual: not virtual - Position Description/PD#: Health System Specialist/PD70516A - Relocation/Recruitment Incentives: Not Authorized - Critical Skills Incentive (CSI): Not Approved - Permanent Change of Station (PCS): Not Authorized I should structure this as: - About the role (from Summary) - Qualifications (with subsections) - Responsibilities (from Duties) - Schedule (work schedule and telework) - Maybe a metadata section for PD#, incentives, etc. But 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. Also: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So I'll create:

  About the role

  Qualifications

  Responsibilities

  Schedule

  And maybe a

  for the metadata. Let me parse the content carefully. Summary: "The incumbent serves as the Health Systems Specialist (HSS) to the Executive Director and is responsible for the administrative and operational functions in support of the Executive Director and subordinate services (hereafter referred to as the Office). The position requires working closely with all levels of administrative and technical staff within the Office and other clinical staff throughout the Medical Center." Qualifications: There's a lot here. I need to preserve all substantive information. The qualifications section has: - Individual Occupational Requirement (two options: experience or education) - Special Provision for Inservice Placement - Note about transcripts - To qualify at GS-11 level: Specialized Experience, Education, or Combination - Preferred Experience: Completion of Graduate Healthcare Administration Training Program (GHATP) - Link to OPM website Duties: Many bullet points. I'll convert to

  • . Work Schedule, Telework, Virtual, Position Description, Relocation, CSI, PCS - these are metadata. The rules say: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Work Schedule and Telework, so Schedule section is appropriate. The others are minor metadata - fold into a short

    or drop. I'll include them in a brief metadata paragraph. Also note: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." There's none of that here. Now, I need to output ONLY the HTML fragment — no /, no markdown code fences. Let me write the HTML. I'll start with

    About the role

    then

    for the summary. Then

    Qualifications

    with subsections. Since the rules say use

    for section headings, but within Qualifications there are sub-headings. I could use

    but the rules only mention

    . However, the rules say "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 be safe, I'll use

    for main sections and maybe or

    for sub-sections. But the content has clear sub-sections. I think using

    is fine semantically, but the instruction says "use

    for section headings". It doesn't say "only use

    ". I'll use

    for main sections and

    for sub-sections within Qualifications. That seems reasonable. Alternatively, I could use

    for each sub-section? But that would be many

    . The example list includes "Requirements, Qualifications" as separate, but here they are nested. I'll use

    for Qualifications, then

    for Individual Occupational Requirement, Specialized Experience, etc. But the rule: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It implies those are the top-level sections. So I'll keep top-level as

    , and for sub-sections, I'll use

    or just in

    . I think

    is acceptable. Let me structure:

    About the role

    ...

    Qualifications

    Individual Occupational Requirement

    ...

    ...

    Special Provision for Inservice Placement

    ...

    ...

    Note: ...

    GS-11 Qualification Requirements

    Specialized Experience

    ...

    ...

    Education

    ...

    Combination

    ...

    Preferred Experience

    ...

    For more information...

    But the rules say "use

    for section headings". It doesn't mention

    or . To be safe, I could use

    for each sub-section? That might be too many. But the instruction says "Prefer a few substantive sections over many thin ones." So maybe I should keep Qualifications as one section with internal structure using

    and

    with bold labels. Let me re-read: "use

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

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

      for prose." It doesn't forbid other headings, but it says "use

      for section headings". I think using

      for the main sections and then using for sub-headings within prose is fine. I'll do:

      Qualifications

      Individual Occupational Requirement: ...

      • ...

      Special Provision for Inservice Placement: ...

      • ...

      Note: ...

      To qualify for this position at the GS-11 level, you must meet one of the following:

      Specialized Experience: ...

      • ...

      Education: ...

      Combination: ...

      Preferred Experience: ...

      For more information on these qualification standards, please visit the United States Office of Personnel Management's website at https://www.opm.gov/policy-data-oversight/classification-qualifications/general-schedule-qualification-standards/.

      That preserves all content. Now Responsibilities: from Duties. There's a list of duties. I'll make

      Responsibilities

      then

      • for each duty. Schedule: Work Schedule and Telework. I'll make

        Schedule

        with

        for work schedule and telework. Metadata: Position Description/PD#, Relocation/Recruitment Incentives, Critical Skills Incentive, Permanent Change of Station. I'll put in a

        at the end or maybe a

        Additional Information

        ? But the rules say only include section when real specific content. These are minor metadata. I'll fold into a short

        at the end. Also, the posting mentions "VA Tennessee Valley Healthcare System (TVHS) is an integrated tertiary health care system..." That's part of Duties section? Actually it's in the Duties section but it's descriptive about the organization. I'll include it as a

        before the duties list. Let me extract the duties list: - Provides consultation, direction, and leadership for professional, technical, administrative and clerical employees, particularly with regard to governance related issues and agency issue briefs - Develops, plans, coordinates, and directs administrative technical functions, particularly with regard to governance related issues and agency issue briefs - Provides full and complete staff assistance to the Executive Director and other leadership as required to meet the goals and mission - Works to establish and implement the primary goals and support the mission of TVHS, setting the direction and overlay for governance related issues - Provides insight in a variety of operational and management issues and integrates this understanding into the development and implementation of governance programs - Provides full and thorough review, analysis and evaluation of governance related programmatic activities and development - Develops tools required to collect and evaluate data and information into reports, tables, charts and graphs, reviews subject matter, and provides a concise analysis to leadership, particularly with regard to governance related issues and agency issue briefs - Establishes, in concert with leadership and key support staff, both long term and short term governance related plans, policies and procedures, assuring that administrative and clinical programs are integrated in order to provide high quality patient care with optimal resource utilization - Serves as the technical advisor and consultant to all levels of TVHS leadership on governance issues such as committee structure, requirements, membership, documentation, responsibilities, and oversight - By thoroughly reviewing all applicable higher level agency, local facility, and external oversight guidance, ensures that all committees are properly chartered, organized, and managed - Oversees the management of all TVHS governance related documentation to include policies, charters, and minutes ensuring files are properly protected and readily available when needed - Serves as the facility subject matter expert and manager of facility level policy creation, modifications, maintenance, storage, and distribution - Ensures local policies adhere to higher level policy guidance and appropriately support accreditation readiness and external oversight regulations - Creates and maintains a document control system for publications and committee documentation via the most