MANAGEMENT ANALYST III

We need to output HTML fragment with sections: About the role? The posting includes Position Overview, Description Of Duties / Essential Functions, Working Conditions, Minimum Requirements (Education, Experience, Substitutions, License), Preferences, General Information (Selection/Skills Tests Required, Safety Impact Position, Pay Grade, Salary Information, Application Procedures). We must not repeat job title as heading. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly. We need to include sections only when posting has real specific content. We have responsibilities (duties). We have requirements (education, experience). We have qualifications (maybe preferences). Skills (preferences list). Pay (Pay Grade 21, Salary Information). Schedule (Workdays & Hours: M-F, 8am-5pm as needed). Benefits? Not mentioned. So we omit Benefits. We must not include filler like "commensurate with experience". We have Pay Grade 21 and Salary Information: "Factors used in determining the salary offered include the candidate's qualifications as well as the pay rates of other employees in this classification." That's not a specific number but still some info. Should we include Pay section? It says include Pay section only when posting actually states them. It states Pay Grade 21 and Salary Information (though not a number). That's still some content. We'll include Pay section with that info. Schedule: Workdays & Hours: M-F, *8am-5pm as needed * Subject to Change. That's schedule info. About the role: Could be Position Overview paragraph. We'll put that under About the role. Responsibilities: Description Of Duties / Essential Functions. Requirements: Minimum Requirements (Education, Experience, Substitutions, License). Could be under Requirements. Qualifications: Preferences? Actually Preferences are "Preference shall be given to eligible veteran applicants..." plus list of preferred experience. That's more like qualifications/preferred qualifications. We'll put under Qualifications. Skills: The list of skills: Experience with Epic..., Experience analyzing..., Experience providing..., Strong analytical, communication, problem-solving skills. We'll put under Skills. We must not include duplicated lines, boilerplate like EEO, application instructions, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the APPLICATION PROCEDURES, EOE, etc. Also remove "GENERAL INFORMATION" maybe? But we need to keep safety impact position? That's not a heading we have; we could incorporate into Requirements? It's not a standard heading; we might drop it as it's not requested. The instruction: "Prefer a few substantive sections over many thin ones." We can include Safety Impact Position maybe under Requirements? But we have no heading for that. Probably drop it as it's not one of the allowed headings. Similarly, Pay Grade and Salary Information we can put under Pay. We must not include "Selection/Skills Tests Required" etc. That's application instructions; drop. We must preserve all substantive information; but we can drop application instructions as per rule. So we drop the APPLICATION PROCEDURES paragraph, the EOE paragraph, the safety impact maybe? It's not application instruction but it's a condition; but we have no heading for it; maybe we could include under Requirements as a note? But the instruction says "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." Safety impact is minor metadata; we could fold into a short p under Requirements or drop. I'd drop to keep sections thin. We need to output only HTML fragment, no html/body tags, no markdown. Let's craft:

About the role

Position Overview APPLICATIONS ACCEPTED FROM: All Persons Interested Division: Public Health Services Section: AOS Reporting Location: Various Workdays & Hours: M-F, *8am-5pm as needed * Subject to Change Description Of Duties / Essential Functions The Houston Health Department is seeking a dynamic and skilled professional to serve as a Management Analyst III, responsible for the following core functions:

But we already have responsibilities separate. Actually About the role could be just the Position Overview paragraph before duties. Let's extract: "Position Overview APPLICATIONS ACCEPTED FROM: All Persons Interested Division: Public Health Services Section: AOS Reporting Location: Various Workdays & Hours: M-F, *8am-5pm as needed * Subject to Change". That's the overview. We'll put that in About the role. Then Responsibilities: list of duties. We need to use

• for any list of duties/requirements/benefits. So responsibilities list should be ul. We have many duty sentences; we can make each as li. Similarly, Requirements: Education Requirements, Experience Requirements, Substitutions, License Requirements. We'll make ul. Qualifications: Preferences: veteran preference plus list of preferred experience. We'll make ul. Skills: list of skills (experience with Epic, etc.) We'll make ul. Pay: Pay Grade 21 and Salary Information paragraph. Schedule: Workdays & Hours. Let's extract duties list exactly as in posting: - Supports Epic system operations, reporting, data analytics, and workflow improvement for Public Health Services programs and Health Center operations. - Develops, runs, and maintains reports using Epic Reporting Workbench and other Epic reporting tools to monitor patient access, scheduling, encounters, service utilization, productivity, and operational performance. - Extracts and exports Epic data for analysis, validation, and reporting to support operational and management decision-making. - Develops and maintains reports using BusinessObjects and creates Power BI dashboards and visualizations to monitor key performance indicators, utilization trends, patient volumes, productivity, and other operational metrics. - Compiles, analyzes, validates, and interprets data from Epic and other systems to identify trends, discrepancies, performance gaps, and opportunities for improvement. - Collaborates with Health Center leadership, clinical programs, and other stakeholders to identify reporting needs and develop reports and dashboards that support program and operational objectives. - Provides Epic training and ongoing support to staff, including new-user training, workflow education, system updates, reporting tools, and standardized Epic processes. - Troubleshoots Epic issues reported by users, identifies potential workflow or system-related causes, provides guidance and support, and escalates technical issues when necessary. - Submits and tracks Jira requests for Epic system issues, enhancements, reporting needs, and workflow changes and coordinates with OCHIN and appropriate stakeholders through resolution and implementation. - Assists with Epic system enhancements, workflow changes, testing, validation, and implementation of new functionality. - Develops, reviews, and updates policies and Standard Operating Procedures (SOPs) related to Epic workflows, system processes, reporting, and Health Center operations. - Provides recurring and ad hoc reports to leadership and assists with interpreting data to support operational planning, performance monitoring, audits, and program requirements. - Develops and maintains reporting documentation, data definitions, training materials, procedures, and standardized reporting processes. - Serves as a resource for Epic users by assisting with system functionality, reporting, workflow questions, and identification of training or process improvement needs. - Participates in Epic-related meetings, projects, system initiatives, and continuous process improvement activities. - Performs special analyses, projects, and other duties as assigned. Now Requirements: Education Requirements: Requires a Bachelor's degree in Public Administration, Business Administration, Finance or a field directly related to the job. Experience Requirements: Four (4) years of professional experience in accounting, budget analysis, finance, public administration or a field directly related to the job are required. Substitutions: Experience cannot be substituted for the Bachelor’s degree requirement. A Master’s degree in a field directly related to the job may substitute for two years of the above experience requirement. License Requirements: None. We'll put each as li. Qualifications (Preferences): - Preference shall be given to eligible veteran applicants provided such persons possess the qualifications necessary for competent discharge of the duties involved in the position applied for, such persons are among the most qualified candidates for the position, and all other factors in accordance with Executive Order 1-6. - Experience with Epic or other electronic health record systems, including reporting and troubleshooting. - Experience with Epic Reporting Workbench, BusinessObjects, and/or Power BI. - Experience analyzing healthcare or operational data and developing reports and dashboards. - Experience providing Epic training and user support. - Strong analytical, communication, and problem-solving skills. But note the last bullet is also under Skills; but we have both Preferences and Skills. The posting lists under PREFERENCES: those bullet points. The last bullet "Strong analytical, communication, and problem-solving skills." is part of PREFERENCES. So we can put that under Qualifications (Preferences). Then Skills maybe we could omit or combine? The instruction says we can have Skills section. But we already have those skills in Preferences. To avoid duplication, we could put Skills empty? Better to merge: we can treat Preferences as Qualifications and not have separate Skills. But the instruction allows Skills section; we could still have Skills but we must not duplicate content. We could put Skills as the same list but that would be duplication. Better to not include Skills section if its content is already covered under Qualifications. However the instruction: "Prefer a few substantive sections over many thin ones." So we can omit Skills if its content is already in Qualifications. But we need to decide mapping: The posting has a "PREFERENCES" section that includes experience and skills. We'll treat that as Qualifications. Then we can omit Skills. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay, Schedule. Now Pay: Pay Grade 21 and Salary Information: "Pay Grade 21 SALARY INFORMATION GENERAL FUND POSITION Grants & Special fund positions are dependent upon continued available funds. If funding is no longer available, employee may be laid off or transferred. Factors used in determining the salary offered include the candidate's qualifications as well as the pay rates of other employees in this classification." We'll put that as a paragraph under Pay. Schedule: "Workdays & Hours: M-F, *8am-5pm as needed * Subject to Change". We'll put as paragraph. Now ensure we don't include any boilerplate like "APPLICATION PROCEDURES", "EOE", etc. Now produce HTML. Let's craft:

  About the role

  Position Overview APPLICATIONS ACCEPTED FROM: All Persons Interested Division: Public Health Services Section: AOS Reporting Location: Various Workdays & Hours: M-F, *8am-5pm as needed * Subject to Change

  Responsibilities

  • Supports Epic system operations, reporting, data analytics, and workflow improvement for Public Health Services programs and Health Center operations.
  • Develops, runs, and maintains reports using Epic Reporting Workbench and other Epic reporting tools to monitor patient access, scheduling, encounters, service utilization, productivity, and operational performance.
  • Extracts and exports Epic data for analysis, validation, and reporting to support operational and management decision-making.
  • Develops and maintains reports using BusinessObjects and creates Power BI dashboards and visualizations to monitor key performance indicators, utilization trends, patient volumes, productivity, and other operational metrics.
  • Compiles, analyzes, validates, and interprets data from Epic and other systems to identify trends, discrepancies, performance gaps, and opportunities for improvement.
  • Collaborates with Health Center leadership, clinical programs, and other stakeholders to identify reporting needs and develop reports and dashboards that support program and operational objectives.
  • Provides Epic training and ongoing support to staff, including new-user training, workflow education, system updates, reporting tools, and standardized Epic processes.
  • Troubleshoots Epic issues reported by users, identifies potential workflow or system-related causes, provides guidance and support, and escalates technical issues when necessary.
  • Submits and tracks Jira requests for Epic system issues, enhancements, reporting