Jobs · Administrative · Tennessee

VITAL RECORDS INFO ASSISTANT - 10202026-81825

State of Tennessee · Nashville, TN · 1 wk ago
Administrative$44k/yrFull-time
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: - About the role / Overview - Responsibilities - Qualifications / Requirements - Skills / Competencies (KSA's) - Benefits? Not mentioned. - Pay / Salary: Yes, salary is given. - Schedule? Not explicitly mentioned, but "Full-Time" and "in office" are noted. - Location: Nashville, TN, Department of Health, Vital Records and Statistics Division, Andrew Johnson Tower. - Other metadata: Opening/closing dates, job type, criminal background check, driver standards. 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 (the page already shows it). The job title isn't explicitly given, but the posting is for a position in Vital Records. I'll assume the title is not to be repeated. - Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. - Preserve ALL substantive information; do NOT invent or summarize away detail. - Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). - Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. - Never create Pay/Schedule/Benefits sections unless the posting actually states them. - Prefer a few substantive sections over many thin ones. - Output ONLY the HTML fragment — no /, no markdown code fences. Let's parse the content: Job Information: - Opening Date/Time: 10/20/2026 12:00AM Central Time - Closing Date/Time: 10/26/2026 11:59PM Central Time - Salary (Monthly): $3,650.00 - Salary (Annually): $43,800.00 - Job Type: Full-Time - City, State Location: Nashville, TN - Department: Health - LOCATION OF (1) POSITION(S) TO BE FILLED: DEPARTMENT OF HEALTH, DAVIDSON COUNTY - This position is located within the Vital Records and Statistics Division, Andrew Johnson Tower. - This position requires a criminal background check. Therefore you may be required to provide information about your criminal history to be considered for this position. - This position is designed as in office. Qualifications: - Education and Experience: Education equivalent to graduation from a standard high school and experience equivalent to two years of full-time work in one or a combination of the following: vital records, medical records, clerical/office support work, or customer service delivery of health information. - Substitution of Education for Experience: Qualifying experience in vital records, medical records, clerical/office support work, or any customer service delivery may substitute for the required education on a year for year basis to a maximum of four years (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 Experience for Education: Course work credit received from an accredited college or university may substitute for the required experience on a month-month basis to a maximum of two years (e.g., 45 quarter hours may substitute for one year of the required experience). Overview: - Under immediate supervision, is responsible for vital records information assistance work of average difficulty; and performs related work as required. An employee in this class is responsible for advanced work providing direct assistance and information pertaining to vital record issues to the general public, various agencies, and officials. Work involves providing vital records assistance by telephone, email, correspondence, or in person. This class differs from the Vital Records Supervisor in that an incumbent of the latter is responsible for supervising a vital records unit. Responsibilities: (list of bullet points) - Responds to inquiries from the general public; interacts with state and federal agencies, and external stakeholders daily to provide or obtain information. - Collects and receipts appropriate fees for certificates or services; prepares correspondence requesting additional information, documents, or fees to finalize a legal process. - Updates/Edits actual record in the database to correct information of a vital event, amends electronic image of records of event in compliance with Vital Records laws and rules, and enters request data into databases to track, locate and issue a record or certify no record found. - Reviews court orders, forms, applications to determine compliance with laws and rules to process new certificate of birth. - Reviews applications to determine entitlement to a requested service or record of event. - Reviews scanned documents to ensure each document is attached to the correct image and explain and enforce Vital Records laws, rules, policies and procedures as they apply to each request. - Accurately maintains daily cash drawer to ensure proper closeout; monitors activities in customer service lobby to ensure safety, traffic flow, and supplies. - Reports suspicious documents, activity or behavior to supervisor for further action or investigation. - Retrieves original certificates from storage boxes for inclusion in a sealed record file. - Reviews documents to determine acceptability of records as supporting evidence to file or amend a record. Competencies (KSA's): - Competencies: Customer Focus, Communicates Effectively, Situational Adaptability, Manages Complexity, Drives Results - Knowledges: Clerical, Customer and Personal Service - Skills: Active Learning and Listening, Speaking, Writing, Reading Comprehension, Service Orientation - Abilities: Written Comprehension, Information Ordering, Inductive Reasoning, Selective Attention - Tools & Equipment: Computer, Telephone, Cashiering Equipment, Scanner, Copier TN Driver Standards: - 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. Now, I need to structure into sections. Potential sections: 1. About the role (Overview) 2. Responsibilities 3. Qualifications (Education and Experience, Substitutions) 4. Competencies (KSA's) - could be Skills or Qualifications 5. Pay (Salary) 6. Schedule? Not explicitly, but "Full-Time" and "in office" could be mentioned in a short paragraph. 7. Location/Department metadata. 8. Driver Standards (maybe part of Requirements or separate) The rules: include a section ONLY when the posting has real, specific content. So I'll create sections for: - About the role (Overview) - Responsibilities - Qualifications (including education/experience and substitutions) - Competencies (KSA's) - maybe combine with Skills? The heading "Skills" is allowed. But the posting has "Competencies (KSA's)" with subcategories. I'll use "Competencies" as heading. - Pay (since salary is given) - Additional Requirements (criminal background check, driver standards, in-office) But "Benefits" not mentioned, so omit. "Schedule" not explicitly, but "Full-Time" and "in office" could be in a short paragraph under "Position Details" or similar. However, the allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I should stick to those headings. The user said: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I can use those exact headings. I can also use "Requirements" for qualifications? The posting has "Qualifications" heading. I'll use "Qualifications" for education/experience. "Requirements" could be for other requirements like background check, driver standards. But the example includes both "Requirements" and "Qualifications". I'll use "Qualifications" for the education/experience section, and "Requirements" for the background check, driver standards, and in-office requirement. But the rule: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." The opening/closing dates, job type, location, department are metadata. I can fold them into a short paragraph at the top, maybe under "About the role" or a separate "Position Details" but not a heading. Since the allowed headings don't include "Position Details", I'll include a short paragraph before sections. Let's structure: First, a paragraph with metadata: Opening/closing dates, salary, job type, location, department, division, background check, in-office. Then sections: - About the role (Overview) - Responsibilities - Qualifications (Education and Experience, Substitutions) - Requirements (Criminal background check, Driver standards) - Competencies (KSA's) - but the allowed heading is "Skills". The posting says "Competencies (KSA's)". I'll use "Skills" as heading, but include competencies, knowledges, skills, abilities, tools. Or use "Competencies" as heading? The example includes "Skills". I'll use "Skills" and include all. - Pay (Salary) Schedule? Not explicitly, but "Full-Time" and "in office" could be mentioned in Pay section or in metadata paragraph. I'll include in metadata. Benefits? Not mentioned, omit. Now, write HTML. I'll start with a

    for metadata. Then

    About the role

    with

    for overview.

    Responsibilities

    with
    • for each responsibility.

      Qualifications

      with

      for education/experience, and maybe

        for substitutions? The substitutions are prose. I'll use

        for each substitution paragraph.

        Requirements

        with
        • for criminal background check, driver standards.

          Skills

          with
          • for each category? Could be nested lists. But keep simple: list each competency, knowledge, skill, ability, tool as separate list items? Might be long. Better to group: Competencies, Knowledges, Skills, Abilities, Tools & Equipment. Use

            for each group with comma-separated? Or use

              with sub-lists. The rule: use
              • for any list of duties/requirements/benefits. So I can make a list for each category. I'll do:

                Skills

                Competencies: Customer Focus, Communicates Effectively, Situational Adaptability, Manages Complexity, Drives Results

                Knowledges: Clerical, Customer and Personal Service

                Skills: Active Learning and Listening, Speaking, Writing, Reading Comprehension, Service Orientation

                Abilities: Written Comprehension, Information Ordering, Inductive Reasoning, Selective Attention

                Tools & Equipment: Computer, Telephone, Cashiering Equipment, Scanner, Copier

                That's prose, not list. But they are lists. Could do
                  for each. But the rule says use
                  • for any list. I'll use
                      for each category. But the heading "Skills" might be too broad. The posting calls it "Competencies (KSA's)". I'll use "Competencies" as heading? The example includes "Skills". I'll use "Skills" as heading and include all.

Similar jobs

CLERK 3 - 08272026-80513

State of TennesseeBeersheba Springs, TN· 2 mo ago
OTHR$31k–$46k/yrapply on careers.edison.tn.gov