uEHR Implementation Team: Resolute Professional Billing Claims and Remittance

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Key sections: - About the role: maybe the first paragraph describing role: "Valley Health System is seeking a uEHR Implementation Team member focusing on Resolute Professional Billing Claims and Remittance. This role requires understanding upstream/downstream data sources and claims-error root causes. This staff is dedicated to paper/electronic claims and electronic remittance setup/testing. Professional billing experience a plus. Also supports systems beyond Epic." - Position Summary: "The position is a technical and operational problem‑solver responsible for designing, configuring, and supporting application solutions that improve workflows, data integrity, and system usability. The role focuses on assigned applications while maintaining awareness of related systems to ensure seamless integration, effective operations, and high‑quality outcomes. This position may be required to work flexible hours or extended schedules during critical incidents or implementations and participate in on-call rotation as required." That could be part of About the role or Responsibilities. We'll decide. - Responsibilities: list of duties: many bullet-like paragraphs: "Establishes, refines, and follows approaches and standards to drive consistent, reliable outcomes within scope." etc. Also many competency sections: Application Support, Documentation, Project Management, Technical Leads, Testing, Training, Troubleshooting, Workflow, Data, General Responsibilities, Mentoring, Professionalism, Strategy, Scope. We need to extract substantive responsibilities as list items. - Requirements/Education: Education: Bachelor’s degree in Informatics, Information Systems, Computer Science, or a related discipline relevant to the supported function is strongly preferred. Equivalent combination of education and 4 years of technical application experience in lieu of degree may be considered. If an application requires certification, it must be obtained within 6 months and maintained throughout employment. - Experience: Minimum of 3 years of progressive experience in information systems, application support, or a related field preferred; 2+ years of project management experience preferred; Experience working with application support, workflow analysis, and system configuration. Epic Certification Required. - Skills: list of skills: Strong knowledge of information systems, informatics, data management, and administration; Ability to design, build, and refine application solutions within assigned systems; Understanding of system relationships, workflows, and operational impacts; Strong analytical and problem-solving skills, including gap analysis and root cause identification; Ability to translate business and technical requirements into functional solution designs; Excellent verbal and written communication skills with ability to communicate complex concepts clearly; Strong interpersonal and collaboration skills; able to work independently and as part of a team; Experience with project management, including coordinating timelines, deliverables, and dependencies; Ability to facilitate and participate in testing, including test planning, execution, and validation; Ability to develop and deliver end-user training and support system adoption; Proficiency in documentation, including creation, review, and validation for accuracy and quality; Ability to analyze and interpret data to support decisions and process improvements; Strong organizational skills with ability to manage and prioritize multiple tasks; Ability to identify risks, escalate appropriately, and support mitigation efforts; Commitment to continuous learning and maintaining current knowledge of emerging technologies. - Benefits: list: Medical/Prescription, Dental & Vision Discount Program (Full Time/Part Time Employees); Group Term Life Insurance and AD&D (Full Time Employees); Flexible Spending Accounts and Commuter Benefit Plans; Supplemental Voluntary Benefits (e.g. Short-term and Long-term Disability, Whole Life Insurance, Legal Support, etc.); 6 Paid Holidays, Paid Time Off (varies), Wellness Time Off, Extended Illness; Retirement Plan; Tuition Assistance; Employee Assistance Program (EAP); Valley Health LifeStyles Fitness Center Membership Discount; Day Care Discounts for Various Daycare Facilities. - Pay: Pay Range: $90,168.00 - $112,715.20. - Schedule: The posting mentions "Shift Day (United States of America)" and "This position may be required to work flexible hours or extended schedules during critical incidents or implementations and participate in on-call rotation as required." So schedule info: Day shift, possibly flexible hours/extended schedules, on-call rotation. We can include schedule section if there is specific content: "Shift Day" and mention flexible hours/extended schedules and on-call rotation. That's enough. We must not include sections with filler like "commensurate with experience". Not present. We must not include duplicated lines. We must output only HTML fragment, no markdown fences. We'll structure:

About the role

...

Responsibilities

• ...
...

Requirements

... maybe combine Education and Experience? Could separate Education and Experience but they said use headings for Requirements, Qualifications, Skills. They gave list of possible headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have Education and Experience -> could go under Requirements (or Qualifications). They differentiate Requirements vs Qualifications maybe but we can put education+experience under Requirements. Skills separate. Qualifications maybe could be certifications? But we have Epic Certification Required. Could put under Qualifications. But we must only include sections when posting has real specific content. We have content for all. Thus:

About the role

Valley Health System is seeking a uEHR Implementation Team member focusing on Resolute Professional Billing Claims and Remittance. This role requires understanding upstream/downstream data sources and claims-error root causes. This staff is dedicated to paper/electronic claims and electronic remittance setup/testing. Professional billing experience a plus. Also supports systems beyond Epic.

Responsibilities

• Establishes, refines, and follows approaches and standards to drive consistent, reliable outcomes within scope.
• Supports and reinforces knowledge sharing by contributing to team learning and cross‑training efforts.
• Manages and prioritizes work ensuring alignment with operational/technical requirements, quality standards, while meeting timelines.
• Proactively provides regular updates and statuses verbally and via departmental electronic systems.
• Responsible for maintaining budgets where appropriate and communicating opportunities for cost savings.
• Collaborates with colleagues and stakeholders to ensure industry and evidence‑based best practice will be implemented wherever possible to support the highest standard of care, meet regulatory requirements, and improve patient outcomes.
• Guides others in understanding relationships between systems, workflows, application behavior, and operational impacts (Mentoring).
• Maintains a high standard of professionalism including effective communication with customers and team members; refines skills, work approach, and behaviors to improve performance in response to feedback or self‑identification; creates communication for system changes, updates, and downtime procedures; identifies and escalates issues/risks while guiding others in risk assessment and mitigation; communicates concepts clearly, driving alignment across users, teams, and workflows; responsible for timely and accurate escalation utilizing the appropriate pathway based on criticality; develops and maintains strong customer, colleague, and vendor relationships, serving as a trusted point of contact; rounds regularly including relationship and shadow rounding and reports back findings; participates in meetings representing area of responsibility to build strategic partnerships, align expectations and integrate input into high‑level decisions; provides meeting summary to leadership; ensures customer needs, business priorities, and operational requirements are accurately represented in solutions and projects; facilitates and actively participates in solution decisions and ensures alignment with operational and customer needs.
• Aligns work with departmental and organizational goals; identifies opportunities for improvement and innovation (Strategy).
• Performs other duties and special projects as assigned; remains up to date on current and emerging technologies; must obtain and maintain application certifications required for any part of your role; operates within assigned applications (Scope).
• Application Support: Designs, builds, and implements solutions within assigned applications, ensuring alignment with operational and technical requirements through collaboration with business and technical teams; educates others in understanding relationships between systems, workflows, application behavior, and operational impacts; reviews and refines configurations and designs for quality and effectiveness within assigned applications; performs gap analysis within assigned applications and provides recommendations that improve workflows, integration, and overall system effectiveness; communicates design and configuration concepts clearly to end users and stakeholders; must maintain working knowledge of other applications used in the area of support; translates requirements for solution design, configuration, and technical needs.
• Documentation: Creates and validates documentation, tools, and shared knowledge resources, ensuring quality and consistency aligned with best practices.
• Project Management: Manages projects within assigned applications or functional areas, coordinating deliverables, timelines, and dependencies to ensure quality outcomes; identifies project risks, interdependencies, and issues, driving resolution to maintain progress, quality, and outcomes; communicates project status, decisions, and impacts to stakeholders for alignment and visibility.
• Technical Lead: Leads technical discussions with colleagues to identify, analyze, and resolve infrastructure‑related issues across applications.
• Testing: Facilitates and participates in quality assurance and testing initiatives, supporting test planning, execution, and issue validation within assigned applications.
• Training: Develops and delivers training for end users supporting system adoption and proper workflow utilization.
• Troubleshooting: Provides ongoing end‑user support for upgrades, new releases, and enhanced functionality; troubleshoots and resolves incidents and requests, identifying and remediating root causes and escalating complex issues as appropriate.
• Workflow: Leads workflow, process, and requirements analysis, including process mapping and comprehensive workflow documentation, within assigned applications; collaborates effectively with all customers to improve workflows and systems usability; engages with customers to understand their operational workflows and deliver solutions that meet their unique needs.
• Data: Defines and validates data requests ensuring accuracy, consistency, and alignment with operational and analytical needs; gathers information and coordinates team members to deliver to customers organized, consistent, and accurate reporting, ensuring quality and completeness; facilitates process improvement initiatives, supporting baseline data analysis and post‑implementation evaluation to assess effectiveness and efficiency gains.

But that is huge; maybe we can combine some. However we must preserve all substantive information; we can't omit. But we can group similar items under subheadings? Not allowed; only headings as specified. We can still have many

items. We need to ensure we don't duplicate content. The responsibilities list includes many sections that are essentially the competency headings. We'll include them as separate list items. Now Requirements: Education and Experience.

Requirements

Bachelor’s degree in Informatics, Information Systems, Computer Science, or a related discipline relevant to the supported function is strongly preferred. Equivalent combination of education and 4 years of technical application experience in lieu of degree may be considered. If an application requires certification, it must be obtained within 6 months and maintained throughout employment.

Minimum of 3 years of progressive experience in information systems, application support, or a related field preferred; 2+ years of project management experience preferred; Experience working with application support, workflow analysis, and system configuration. Epic Certification Required.

We could combine into one p but it's okay. Qualifications: maybe we could put Epic Certification Required under Qualifications. But we already included in Requirements. To avoid duplication, maybe we put Epic Certification under Qualifications. Let's decide: Requirements: education and experience. Qualifications: certifications (Epic Certification Required). Skills: list of skills. Thus:

Qualifications

Epic Certification Required.

Skills

• Strong knowledge of information systems, informatics, data management, and administration
• Ability to design, build, and refine application solutions within assigned systems