Business Systems Analyst - Senior / Intermediate
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. Must not include Job ID etc. Must preserve all substantive info, no summarizing away detail. Must remove boilerplate like "How to Apply", "Application Deadline", "U-M EEO Statement", etc. Also remove "Learn more about the work modes." etc. Must keep substantive content: Job Summary, Division Overview, Responsibilities, Required Qualifications (Senior/Intermediate), Desired Qualifications, Modes of Work, Work Locations, Underfill Statement, Benefits, Background Screening maybe? But we need to map to allowed sections: About the role (maybe Job Summary + Division Overview?), Responsibilities, Requirements (maybe Required Qualifications?), Qualifications (maybe Desired Qualifications?), Skills (maybe from Desired Qualifications?), Benefits, Pay, Schedule. Pay and Schedule only if posting actually states them. The posting does not mention pay or schedule specifics, only mentions "Work Locations This position offers the opportunity to negotiate alternative work schedules and remote/on-site arrangements to support work-life balance." That's schedule info? It mentions alternative work schedules, but not specific schedule. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Benefits, we have a Benefits section with description: "We offer a benefits package that includes comprehensive training and career development opportunities, generous retirement savings plans, ample paid time off, and a wealth of family care support". That's specific enough, so we can include Benefits. For Schedule, we have mention of alternative work schedules and remote/on-site arrangements. That's schedule info, albeit generic. Should we include Schedule? The posting states "This position offers the opportunity to negotiate alternative work schedules and remote/on-site arrangements to support work-life balance." That's schedule info. So we can include Schedule section with that content. Pay: no mention, so omit.
We need to avoid filler like "commensurate with experience". Not present.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like bullet points from Responsibilities, Required Qualifications (Senior/Intermediate), Desired Qualifications, Modes of Work, Work Locations, Underfill Statement, Benefits, Background Screening? Background Screening maybe not part of allowed sections; but we could include under About the role? Probably not. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine some info.
We need to decide sections: About the role (Job Summary + Division Overview). Responsibilities (the bullet list). Requirements (maybe Required Qualifications). Qualifications (maybe Desired Qualifications). Skills (maybe from Desired Qualifications like Epic certification, knowledge, etc). Benefits (the benefits description). Schedule (alternative work schedules). Possibly also Modes of Work and Work Locations could go under Schedule or About the role? But we have limited headings; we could incorporate them into About the role or Schedule. However we must not lose substantive info. We could include Modes of Work and Work Locations under Schedule section as they relate to work arrangements. Or we could create a separate section but not allowed headings. Only allowed headings are those listed. So we must fit all info into those sections.
Thus:
- About the role: include Job Summary and Division Overview paragraphs.
- Responsibilities: list bullet points from Responsibilities*.
- Requirements: include Required Qualifications* (Senior and Intermediate levels). Could be a paragraph describing both.
- Qualifications: include Desired Qualifications* (Epic certification, etc). Could be bullet list.
- Skills: maybe we could extract specific skills from Desired Qualifications: Epic certification, knowledge of Hospital Billing/Professional Billing workflows, Epic Charge Router configuration, experience implementing Epic functionality, supporting upgrades, reviewing Nova notes, Epic security and access management. Could be bullet list.
- Benefits: paragraph from Benefits.
- Schedule: include Modes of Work, Work Locations, Underfill Statement? Underfill Statement is about classification; maybe could go under Requirements? But we have no other heading. Could include Underfill Statement in About the role? Might be okay. But we need to preserve it. Could add a paragraph under About the role or Requirements. Since Underfill Statement is about classification, maybe fit under Requirements? But it's not a requirement. Could add a separate paragraph under About the role after division overview.
We must not include boilerplate like "How to Apply", "Application Deadline", "U-M EEO Statement", "Background Screening", "Learn more about the work modes." etc. So we drop those.
We must not repeat job title. Not include "Job Summary" heading; we just use About the role.
We must not include markdown fences.
Now craft HTML.
Structure:
About the role
Job Summary: The HITS One Epic team is seeking a Business Systems Analyst to support the implementation of a unified Epic electronic medical record across the organization. This role will focus on Revenue Cycle applications and workflows, including Hospital Billing, Professional Billing, Single Billing Office, Claims, Contracts, and related operational areas. As a Business Systems Analyst on the One Epic team, you will collaborate with operational leaders, subject-matter experts, and technical teams to analyze requirements, design and validate workflows, configure and test the application, resolve issues, and support readiness and implementation activities. You will also help ensure effective knowledge transfer and a smooth transition to ongoing operational support. Success in this role requires a strong understanding of organizational policies, business operations, and the impact of Epic functionality on end users and Revenue Cycle processes.
Division Overview: The HITS Clinical & Revenue Cycle IT (CRC) division is responsible for more than 350 clinical and revenue cycle applications that clinicians, staff, and patients rely upon every day. The CRC team has subdivisions that support inpatient, ambulatory, departmental, and revenue cycle areas across Michigan Medicine (MM). CRC also oversees many of the major IT platforms and applications such as electronic health record, virtual care, pharmacy, radiology, radiation oncology, registration, document management, billing, and much more. The CRC team is highly relied upon across the healthcare system and collaborates with operational partners to provide excellent service to the MM staff. Staff within CRC often interact with customers on a regular basis by implementing and configuring workflows, enhancements, optimizations, and new modules or software while also ensuring adequate change control and testing processes occur. Team members work on a vast array of projects that propel MM into the future.
Responsibilities
- Under minimal supervision, lead the planning, design, development, implementation, maintenance, and evaluation of Epic workflows.
- Analyze departmental and end-user business needs, document requirements, and translate them into appropriate system specifications.
- Evaluate workflows and system needs for new features and enhancements, document current-state processes, and collaborate with users to identify and define process improvement options.
- Participate in software upgrade projects of varying complexity by reviewing release documentation, evaluating new functionality, and completing required build, testing, and user validation activities.
- Analyze, compare, and evaluate potential courses of action to determine the best path forward for the team and its customers.
- Gather and assess information related to potential system enhancements.
- Develop and maintain project team procedures for implementing system changes and completing related tasks.
- Exercise independent judgment and make decisions on matters of significance within the scope of the role's responsibilities.
- Participate in established change control processes and procedures.
- Support training activities and collaborate directly with end users.
- Collaborate with internal teams, including MiChart and HITS, and external partners, including Epic and other third parties, to resolve integration and configuration issues.
- Coordinate the full life cycle of changes including design, build, testing, education, communication and maintain complete documentation in ServiceNow.
- Support other application coordinators in areas where you serve as the knowledge owner.
- Obtain and maintain Epic certification or accreditation in Hospital Billing, Professional Billing, Claims, and/or Reimbursement Contracts by completing the required projects and examinations.
Requirements
Required Qualifications* (Senior Level): Bachelor's degree or equivalent combination of education and experience; 5+ years of IT-related experience supporting hospital electronic health record systems, with a focus on billing.
Required Qualifications* (Intermediate Level): Bachelor's degree or equivalent combination of education and experience; 2-3 years of IT-related experience supporting hospital electronic health record systems, with a focus on billing.
Underfill Statement: This position may be underfilled at a lower classification depending on the qualifications of the selected candidate.
Qualifications
- Epic certification or accreditation in Hospital Billing, Professional Billing, Claims, and/or Reimbursement Contracts.
- Experience working in a healthcare organization.
- Knowledge of Hospital Billing and/or Professional Billing workflows and Epic Charge Router configuration.
- Experience implementing Epic functionality, supporting upgrades, and reviewing Nova notes.
- Experience with Epic security and access management.
Skills
(Skills are captured in the Qualifications section above; no additional distinct skills listed.)
But we should not create empty sections. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". If we put Skills heading but then say "(Skills are captured...)" that's filler. Better to omit Skills section if no distinct skills beyond qualifications. However we could extract skills from Desired Qualifications as separate bullet list under Skills. But those are already in Qualifications. Could we move them to Skills and keep Qualifications for certifications? But we need to avoid duplication. Perhaps better to have Qualifications for certifications and education, Skills for specific abilities. Let's split:
Qualifications: Epic certification or accreditation, Experience working in healthcare organization.
Skills: Knowledge of Hospital Billing/Professional Billing workflows and Epic Charge Router configuration; Experience implementing Epic functionality, supporting upgrades, reviewing Nova notes; Experience with Epic security and access management.
That way we have substantive content for both.
Let's adjust.
Qualifications section bullet list: Epic certification..., Experience working in a healthcare organization.
Skills section bullet list: Knowledge of Hospital Billing and/or Professional Billing workflows and Epic Charge Router configuration; Experience implementing Epic functionality, supporting upgrades, and reviewing Nova notes; Experience with Epic security and access management.
Now Benefits section: paragraph.
Schedule section: include Modes of Work, Work Locations, and maybe mention alternative work schedules.
Modes of Work: "Positions that are eligible for hybrid or mobile/remote work mode are at the discretion of the hiring department. Work agreements are reviewed annually at a minimum and are subject to change at any time, and for any reason, throughout the course of employment."
Work Locations: "This position offers the opportunity to negotiate alternative work schedules and remote/on-site arrangements to support work-life balance. Non-Michigan residents should inquire about potential employment while working remotely from a state other than Michigan."
We can combine into Schedule section.
Now ensure we removed boilerplate: "Learn more about the work modes." drop. "Background Screening" drop. "Application Deadline" drop. "U-M EEO Statement" drop. "How to Apply" drop. "Additional Information" drop. "Benefits" we kept but we need to ensure we only keep the substantive description, not the link. The Benefits paragraph includes a link: "https://careers.umich.edu/benefits". Should we keep the link? It's part of the benefits description. The rule: preserve ALL substantive information; do not invent or summarize away detail.
- for any list of duties/requirements/benefits. Use
for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like bullet points from Responsibilities, Required Qualifications (Senior/Intermediate), Desired Qualifications, Modes of Work, Work Locations, Underfill Statement, Benefits, Background Screening? Background Screening maybe not part of allowed sections; but we could include under About the role? Probably not. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine some info. We need to decide sections: About the role (Job Summary + Division Overview). Responsibilities (the bullet list). Requirements (maybe Required Qualifications). Qualifications (maybe Desired Qualifications). Skills (maybe from Desired Qualifications like Epic certification, knowledge, etc). Benefits (the benefits description). Schedule (alternative work schedules). Possibly also Modes of Work and Work Locations could go under Schedule or About the role? But we have limited headings; we could incorporate them into About the role or Schedule. However we must not lose substantive info. We could include Modes of Work and Work Locations under Schedule section as they relate to work arrangements. Or we could create a separate section but not allowed headings. Only allowed headings are those listed. So we must fit all info into those sections. Thus: - About the role: include Job Summary and Division Overview paragraphs. - Responsibilities: list bullet points from Responsibilities*. - Requirements: include Required Qualifications* (Senior and Intermediate levels). Could be a paragraph describing both. - Qualifications: include Desired Qualifications* (Epic certification, etc). Could be bullet list. - Skills: maybe we could extract specific skills from Desired Qualifications: Epic certification, knowledge of Hospital Billing/Professional Billing workflows, Epic Charge Router configuration, experience implementing Epic functionality, supporting upgrades, reviewing Nova notes, Epic security and access management. Could be bullet list. - Benefits: paragraph from Benefits. - Schedule: include Modes of Work, Work Locations, Underfill Statement? Underfill Statement is about classification; maybe could go under Requirements? But we have no other heading. Could include Underfill Statement in About the role? Might be okay. But we need to preserve it. Could add a paragraph under About the role or Requirements. Since Underfill Statement is about classification, maybe fit under Requirements? But it's not a requirement. Could add a separate paragraph under About the role after division overview. We must not include boilerplate like "How to Apply", "Application Deadline", "U-M EEO Statement", "Background Screening", "Learn more about the work modes." etc. So we drop those. We must not repeat job title. Not include "Job Summary" heading; we just use About the role. We must not include markdown fences. Now craft HTML. Structure:
About the role
Job Summary: The HITS One Epic team is seeking a Business Systems Analyst to support the implementation of a unified Epic electronic medical record across the organization. This role will focus on Revenue Cycle applications and workflows, including Hospital Billing, Professional Billing, Single Billing Office, Claims, Contracts, and related operational areas. As a Business Systems Analyst on the One Epic team, you will collaborate with operational leaders, subject-matter experts, and technical teams to analyze requirements, design and validate workflows, configure and test the application, resolve issues, and support readiness and implementation activities. You will also help ensure effective knowledge transfer and a smooth transition to ongoing operational support. Success in this role requires a strong understanding of organizational policies, business operations, and the impact of Epic functionality on end users and Revenue Cycle processes.
Division Overview: The HITS Clinical & Revenue Cycle IT (CRC) division is responsible for more than 350 clinical and revenue cycle applications that clinicians, staff, and patients rely upon every day. The CRC team has subdivisions that support inpatient, ambulatory, departmental, and revenue cycle areas across Michigan Medicine (MM). CRC also oversees many of the major IT platforms and applications such as electronic health record, virtual care, pharmacy, radiology, radiation oncology, registration, document management, billing, and much more. The CRC team is highly relied upon across the healthcare system and collaborates with operational partners to provide excellent service to the MM staff. Staff within CRC often interact with customers on a regular basis by implementing and configuring workflows, enhancements, optimizations, and new modules or software while also ensuring adequate change control and testing processes occur. Team members work on a vast array of projects that propel MM into the future.
Responsibilities
- Under minimal supervision, lead the planning, design, development, implementation, maintenance, and evaluation of Epic workflows.
- Analyze departmental and end-user business needs, document requirements, and translate them into appropriate system specifications.
- Evaluate workflows and system needs for new features and enhancements, document current-state processes, and collaborate with users to identify and define process improvement options.
- Participate in software upgrade projects of varying complexity by reviewing release documentation, evaluating new functionality, and completing required build, testing, and user validation activities.
- Analyze, compare, and evaluate potential courses of action to determine the best path forward for the team and its customers.
- Gather and assess information related to potential system enhancements.
- Develop and maintain project team procedures for implementing system changes and completing related tasks.
- Exercise independent judgment and make decisions on matters of significance within the scope of the role's responsibilities.
- Participate in established change control processes and procedures.
- Support training activities and collaborate directly with end users.
- Collaborate with internal teams, including MiChart and HITS, and external partners, including Epic and other third parties, to resolve integration and configuration issues.
- Coordinate the full life cycle of changes including design, build, testing, education, communication and maintain complete documentation in ServiceNow.
- Support other application coordinators in areas where you serve as the knowledge owner.
- Obtain and maintain Epic certification or accreditation in Hospital Billing, Professional Billing, Claims, and/or Reimbursement Contracts by completing the required projects and examinations.
Requirements
Required Qualifications* (Senior Level): Bachelor's degree or equivalent combination of education and experience; 5+ years of IT-related experience supporting hospital electronic health record systems, with a focus on billing.
Required Qualifications* (Intermediate Level): Bachelor's degree or equivalent combination of education and experience; 2-3 years of IT-related experience supporting hospital electronic health record systems, with a focus on billing.
Underfill Statement: This position may be underfilled at a lower classification depending on the qualifications of the selected candidate.
Qualifications
- Epic certification or accreditation in Hospital Billing, Professional Billing, Claims, and/or Reimbursement Contracts.
- Experience working in a healthcare organization.
- Knowledge of Hospital Billing and/or Professional Billing workflows and Epic Charge Router configuration.
- Experience implementing Epic functionality, supporting upgrades, and reviewing Nova notes.
- Experience with Epic security and access management.
Skills
(Skills are captured in the Qualifications section above; no additional distinct skills listed.)
But we should not create empty sections. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". If we put Skills heading but then say "(Skills are captured...)" that's filler. Better to omit Skills section if no distinct skills beyond qualifications. However we could extract skills from Desired Qualifications as separate bullet list under Skills. But those are already in Qualifications. Could we move them to Skills and keep Qualifications for certifications? But we need to avoid duplication. Perhaps better to have Qualifications for certifications and education, Skills for specific abilities. Let's split: Qualifications: Epic certification or accreditation, Experience working in healthcare organization. Skills: Knowledge of Hospital Billing/Professional Billing workflows and Epic Charge Router configuration; Experience implementing Epic functionality, supporting upgrades, reviewing Nova notes; Experience with Epic security and access management. That way we have substantive content for both. Let's adjust. Qualifications section bullet list: Epic certification..., Experience working in a healthcare organization. Skills section bullet list: Knowledge of Hospital Billing and/or Professional Billing workflows and Epic Charge Router configuration; Experience implementing Epic functionality, supporting upgrades, and reviewing Nova notes; Experience with Epic security and access management. Now Benefits section: paragraph. Schedule section: include Modes of Work, Work Locations, and maybe mention alternative work schedules. Modes of Work: "Positions that are eligible for hybrid or mobile/remote work mode are at the discretion of the hiring department. Work agreements are reviewed annually at a minimum and are subject to change at any time, and for any reason, throughout the course of employment." Work Locations: "This position offers the opportunity to negotiate alternative work schedules and remote/on-site arrangements to support work-life balance. Non-Michigan residents should inquire about potential employment while working remotely from a state other than Michigan." We can combine into Schedule section. Now ensure we removed boilerplate: "Learn more about the work modes." drop. "Background Screening" drop. "Application Deadline" drop. "U-M EEO Statement" drop. "How to Apply" drop. "Additional Information" drop. "Benefits" we kept but we need to ensure we only keep the substantive description, not the link. The Benefits paragraph includes a link: "https://careers.umich.edu/benefits". Should we keep the link? It's part of the benefits description. The rule: preserve ALL substantive information; do not invent or summarize away detail.