HIM Specialist (Part-time)

We need to output HTML fragment with sections using

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Remove boilerplate. We need to extract content. Given posting: It starts with "Why Join UCS ..." then description of organization, then "UCS Offers Generous Benefits" list. Then description of role under direction etc. Then "Major Responsibilities" list. Then "QUALITY ASSURANCE" paragraph. Then "Required Professional Skills" list. Then "Education/Professional Experience Requirements". Also there is mention of competitive pay? Actually "UCS Offers Generous Benefits Competitive pay" appears as a line: "UCS Offers Generous Benefits Competitive payGenerous paid time offMedical, dental, and vision insuranceRetirement plan with employer matchEmployer paid life insuranceEmployer paid short term and long-term disability insuranceEmployee Assistance ProgramCareer development opportunitiesFree clinical supervision towards licensureLoan repayment and tuition assistance programAward winning worksite wellness programAn inclusive workplace supported by an active Diversity, Equity, Inclusion, and Belonging committee.Rewarding experience making a difference in the community." Thus benefits list includes competitive pay, generous PTO, medical/dental/vision, retirement plan with employer match, employer paid life insurance, employer paid short/long term disability, EAP, career development, free clinical supervision towards licensure, loan repayment and tuition assistance, award winning worksite wellness program, inclusive workplace with DEI committee, rewarding experience making a difference. We need to create sections: About the role (description of role and organization?), Responsibilities (Major Responsibilities list), Requirements (Education/Professional Experience Requirements?), Qualifications (maybe Required Professional Skills?), Skills (maybe combine?), Benefits (list), Pay (if mentioned: competitive pay), Schedule (none). We should not create sections with placeholder or vague. Pay: we have "Competitive pay" mentioned; that's specific enough? It says "Competitive pay". That's a statement; we can include Pay section with that line. Schedule: none, so omit. We need to avoid duplication. Also need to include About the role: maybe combine the initial description about UCS and the role purpose. The posting includes "Why Join UCS ..." and then description of role under direction etc. We'll craft About the role paragraph summarizing: UCS mission, role purpose under HIM and Data Analytics Supervisor, responsibilities overview. Must preserve all substantive info; not invent. We'll need to include details: Under direction of HIM and Data Analytics Supervisor, the HIM Systems Support Specialist is responsible for troubleshooting end user issues related to various databases managed by HIM. Supports integrity, security, effective use of health information systems across organization. Serves as key liaison between clinical, administrative, IT functions, providing day-to-day systems support, managing user access, assisting with technical audits, supporting workflows related to training and documentation. We'll put that in About the role. Responsibilities: list from "Major Responsibilities". We'll output each as

. Requirements: Education/Professional Experience Requirements: Bachelor’s degree preferred, or a minimum of 2 years related experience. Qualifications: maybe we can treat Required Professional Skills as Qualifications? But we also have Skills section. The instruction: use headings for Skills, Benefits, Pay, Schedule. So we need to separate Skills and Qualifications. Qualifications could be education/experience; Skills could be the list of required professional skills. Let's do that. Thus:

About the role

...

Responsibilities

• ...
...

Requirements

Bachelor’s degree preferred, or a minimum of 2 years related experience.

Qualifications

??? Actually we might not have separate qualifications beyond education; but we could put nothing? Better to combine education/experience as Requirements and skills as Skills. Qualifications maybe we can omit if no distinct content. But we need to include a section only when posting has real specific content. We have Required Professional Skills list; that's skills. So we can put Skills section. Thus we may omit Qualifications heading. But the instruction list includes Qualifications as possible heading; we can omit if not needed. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. Now Benefits: list items from UCS Offers Generous Benefits. We'll extract each benefit as

. Need to ensure we capture all. List: - Competitive pay - Generous paid time off - Medical, dental, and vision insurance - Retirement plan with employer match - Employer paid life insurance - Employer paid short term and long-term disability insurance - Employee Assistance Program - Career development opportunities - Free clinical supervision towards licensure - Loan repayment and tuition assistance program - Award winning worksite wellness program - An inclusive workplace supported by an active Diversity, Equity, Inclusion, and Belonging committee. - Rewarding experience making a difference in the community. We'll put each as

. Pay section: we already have Competitive pay in benefits; but we could also have separate Pay section with "Competitive pay". However that would duplicate. The instruction: avoid duplicated lines. So we should not repeat Competitive pay in both Benefits and Pay. Since Benefits already includes Competitive pay, we could omit Pay section. But we need to decide: The posting says "UCS Offers Generous Benefits Competitive payGenerous paid time off..." It seems Competitive pay is part of benefits. So we can keep it within Benefits and not create separate Pay section. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Benefits is stated, so we include Benefits. Pay is also stated as "Competitive pay". But if we already included it in Benefits, we could still create Pay section with that line, but that would duplicate. Better to not duplicate; we can either put Competitive pay only in Benefits and not have Pay section. Since Benefits already covers it, we can omit Pay. The instruction says prefer few substantive sections over many thin ones. So we omit Pay. Schedule: none. Thus final HTML:

About the role

Under the direction of the HIM and Data Analytics Supervisor, the Health Information Management (HIM) Systems Support Specialist is responsible for troubleshooting end user issues related to the various databases managed by HIM. The HIM System Support Specialist supports the integrity, security, and effective use of health information systems across the organization. This role serves as a key liaison between clinical, administrative, and IT functions, providing day-to-day systems support, managing user access, assisting with technical audits, and supporting workflows related to training and documentation.

Responsibilities

• Provide support for help desk tickets and troubleshooting user issues.
• Manage staff user accounts, permissions, and role-based access in accordance with privacy, security, and compliance requirements.
• Assist with developing, maintaining, and updating end-user training documentation to support accurate clinical documentation and consistent use of health information systems.
• Demonstrate working knowledge of health information data storage, access controls, interoperability, and secure information-sharing practices.
• Demonstrate understanding of healthcare business operations, including client throughput, documentation workflows, and their impact on data quality and reporting.
• Demonstrate understanding of the healthcare revenue cycle and the role of health information management in billing accuracy, coding, and reimbursement.
• Assist with technical audits and monitoring related to the EHR. Help maintain documentation and workflows.
• Perform basic data pulls, validation, and preparation for internal reporting and external/state reporting requirements.
• Assist with ongoing training for staff on system use, data entry standards, and best practices.
• Identify opportunities to improve system workflows, reporting processes, and user experience.
• Participate in system testing, upgrades, and implementation of new tools or processes.
• Provide feedback and recommendations based on user support trends and system usage.

Requirements

Bachelor’s degree preferred, or a minimum of 2 years related experience.

Skills

• Advanced Microsoft skills which must include Outlook, Word, Excel, and PowerBI
• Experience with electronic health records
• Strong critical thinking and problem-solving skills
• Exceptional communication skills
• Exceptional soft skills
• Ability to use Crystal Reports software
• Time management skills with ability to set and meet deadlines with limited supervision
• Ability to produce well-written documentation

Benefits

• Competitive pay
• Generous paid time off
• Medical, dental, and vision insurance
• Retirement plan with employer match
• Employer paid life insurance
• Employer paid short term and long-term disability insurance
• Employee Assistance Program
• Career development opportunities
• Free clinical supervision towards licensure
• Loan repayment and tuition assistance program
• Award winning worksite wellness program
• An inclusive workplace supported by an active Diversity, Equity, Inclusion, and Belonging committee.
• Rewarding experience making a difference in the community.

We must ensure no extra text. Output only HTML fragment. Check for any boilerplate removed: We removed "Why Join UCS..." intro? Actually we used some of that in About the role? We used only the role description; we omitted the introductory paragraph about UCS history etc. That's considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The introductory paragraph about UCS history and mission might be considered substantive? It's about the organization; could be considered part of About the role? The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." The intro about UCS's history, mission, facilities, etc is substantive. Should we include it? The About the role section could include that info. We omitted it; that would be losing substantive info. We need to include that info somewhere, perhaps in About the role paragraph. Let's incorporate that. We need to preserve all substantive info: The first paragraph: "Why Join UCS For over 65 years, UCS has been providing exceptional and thoughtful care to individuals and families in our community through programs, services, and educational opportunities. Our staff includes positions such as administration, clinicians, nurses, teachers, case managers, psychiatrists, and direct support providers who work within our 15 facilities to support over 3,000 individuals annually. We are proud to be part of Vermont Care Partners, a network of sixteen agencies that provide mental health, substance use disorder, and developmental disability services and supports in every county in Vermont. We are looking for team players to join us in making a difference in the lives of others and building a stronger community." That's substantive about organization. We should include that in About the role, perhaps before the role description. Thus About the role paragraph will combine both. Let's craft:

For over 65 years, UCS has been providing exceptional and thoughtful care to individuals and families in the community through programs, services, and educational opportunities. Staff includes administration, clinicians, nurses, teachers, case managers, psychiatrists, and direct support providers working across 15 facilities to support over 3,000 individuals annually. UCS is part of Vermont Care Partners, a network of sixteen agencies providing mental health, substance use disorder, and developmental disability services in every Vermont county. The organization seeks team players to make a difference and build a stronger community