EMR Analyst II - Epic Digital Platforms

We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. The posting includes: Primary Location Remote Department IS Epic Shift Day (United States of America) Schedule Full time Weekly Hours 40 FTE 1 Employee Status Regular ... This is metadata; we should fold minor metadata into a short

or drop it. Not headings. We need sections: About the role (maybe from first paragraph). Responsibilities (list of duties). Requirements (maybe qualifications). Qualifications (maybe separate). Skills (maybe from responsibilities). Benefits (none given). Pay (none). Schedule (maybe from metadata: Full time Weekly Hours 40). Since schedule is mentioned, we can include Schedule section with that info. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO etc. We need to preserve all substantive info. Let's parse content: Primary Location Remote Department IS Epic Shift Day (United States of America) Schedule Full time Weekly Hours 40 FTE 1 Employee Status Regular Cincinnati Children’s is advancing its support of Epic tools that how our clinical teams connect, collaborate, and deliver care through an expansion of our Epic Digital Platforms team. Managing applications like Care Everywhere, EpicCare Link, Teamwork, Unified Communications, and Ambient listening technologies, the Epic Digital Platforms team manages products which assure the right information and staff are available at the right time to provide high-quality patient care. This role is critical to ensuring seamless integration, technical excellence, and strategic alignment as we continue to evolve our enterprise communication, ambient listening, and interoperability ecosystem. By strengthening our Epic Digital Platforms team, we are enhancing care coordination, improving workflow efficiency, and supporting safer, more connected patient care delivery across the organization. Then sections: Build/Configuration/Release Management (list of duties). Leadership (list). Professional Growth & Development (list). Project Management Support/and or lead... (list). Customer Support (list). Job Qualifications (Bachelor's Degree...). Preferred Qualifications (list). About Us (description). Comprehensive Job Description Provided Upon Request. (maybe ignore). Then EEO etc. We need to map to headings: About the role (maybe first paragraph after metadata). Responsibilities (maybe combine Build/Configuration/Release Management, Leadership, Professional Growth & Development, Project Management Support, Customer Support). Could separate but we need to avoid many thin sections. Could combine all duty lists under Responsibilities. Requirements: maybe Job Qualifications (Bachelor's Degree or equivalent...). Qualifications: maybe Preferred Qualifications (Epic certifications etc). Skills: maybe from responsibilities? Could list skills like Epic certifications, troubleshooting, etc. But we should not invent. We could put Skills section if there is explicit skill list; not really. Might omit Skills. Benefits: none. Pay: none. Schedule: we have Full time Weekly Hours 40. So we can include Schedule section with that. We need to output HTML fragment only. Let's craft:

Primary Location: Remote; Department: IS Epic; Shift: Day (United States of America); Employee Status: Regular.

Then

About the role

... (the paragraph about advancing support...)

Then

Responsibilities

combine all bullet-like sentences. We need to extract each duty as list items. From Build/Configuration/Release Management: - Analyze, design, implement, and maintain moderately complex systems that greatly improves clinical care and patient management. - Support system testing. - Document testing outcomes. - Work to develop technical solutions. - Utilize development lifecycle process, operating procedures, and documentation to implement and support system solutions. - Where applicable, collaborate on the scheduling of the applicable clinical systems training and build environments to ensure currency and usability to support end user training. - Independently develops educational technology content for applicable use. - Recommends opportunities for and participates in process improvement to advance education and learning processes, content tracking, content review and revision. - Drives the use of multivariate learning modalities to cover the adult learning spectrum and clinical system education need. Leadership: - Take ownership of tasks with sense of urgency and drive them to completion. - Take initiative and know what needs to be done. - Communicate to supervisor regarding overall issues, roadblocks. - Identify the appropriate resources needed to complete small/medium projects. - Support the communication on project-related issues and developments. - Work with cross functional teams. - Attend and participate in design and leadership team meetings for the various clinical applications deployed throughout the hospital. - Consult with end users to ensure that clinical system applications and accompanying training programs and materials support global and unique patient care delivery processes. - Network with internal and external experts to identify best practices for clinical system use and training. - Promote use of industry best practice tools for efficiency and innovative education and learning. Professional Growth & Development: - Maintain currency in the field by participating in educational opportunities provided by vendor and other customer connections. - Conduct and participate in instructional sessions. - Use knowledge to improve skills. - Develop and maintain positive relationships, both internal and external to CCHMC. - Motivate people and encourage teamwork. - Work well with others and fosters a positive team environment. - Prepare oral and written presentations. Project Management Support/and or lead the design, development, and implementation of new and enhanced application requests. - Support and/or lead project plans and other project- related documentation for moderately complex projects. - Determine the scope of moderately complex projects. - Coordinate the appropriate resources needed. - Prioritize, organize, and complete assigned tasks and associated documentation upon directives from supervisor or customers. - Seek the appropriate resources needed for activities. - Coordinate and facilitate communication between internal and external parties on assigned tasks and related issues. - Effectively works with cross functional teams to ensure proper integration. - Consult with and support the end user community to develop and validate requirements for system solutions. Customer Support: - Develop collaborative professional relationships with customer group and key stakeholders. - Demonstrates advanced troubleshooting skills. - Ensure outstanding end-user support is provided, including ongoing monitoring of Service Level Agreements for incident management and collaboration with other areas to ensure customer-centered incident management and support. - Independently critically thinks to work through details of a problem to reach a positive solution. - Plan and execute the support for a user base through clinical system training and the creation and curation of advanced education and training materials. - Adhere to and promote continual adoption of change management policies and procedures. - Interact with all levels of staff throughout the Medical Center in a collaborative manner. - Strong sense of personal accountability. - Model outstanding customer service behavior, including timely and effective follow-up with customers. - Always maintain CCHMC¿s service standards of being Courteous, Attentive, Respectful and Enthusiastic team members, and Safe (CARES). Now Job Qualifications: - Bachelor's Degree or equivalent combination of education and experience - 2+ years of work experience in a related job discipline Preferred Qualifications: - Possession of one or more current Epic certifications, such as: Epic Care Everywhere, Epic Inpatient Clinical Documentation, EpicCare Link, Epic Ambulatory, Epic Inpatient Procedure Orders, Epic Cadence Grand Central, Other Epic certifications related to clinical care delivery. - Comprehensive understanding of Epic workflows and how they integrate across diverse clinical and operational areas. About Us: paragraph. We could include About Us as a section maybe "About the organization" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map About Us maybe to About the role? Already have About the role. Could add another section "About the organization" but not allowed. Better to incorporate About Us into About the role? Might be okay to add a separate section "About the organization" but not in list; risk of violating rule. Safer to drop About Us or incorporate into About the role as extra paragraph. We must preserve all substantive info; dropping About Us loses info. Could add a section "About the organization" but not allowed heading. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, not exclusive? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should not create other headings. We could embed About Us content within About the role section as additional paragraph. Thus About the role section will have two paragraphs: first about advancing support, second about Us. Now Requirements: maybe we treat Job Qualifications as Requirements. Qualifications: Preferred Qualifications as Qualifications. Skills: maybe we could extract skills from responsibilities like "advanced troubleshooting skills", "educational technology content", etc. But we could also omit Skills if no explicit list. The instruction: "Prefer a few substantive sections over many thin ones." So we could omit Skills if not substantive. Schedule: we have schedule info. Pay: none, omit. Benefits: none, omit. Now construct HTML. We need to wrap metadata in a

. Let's do:

Primary Location: Remote; Department: IS Epic; Shift: Day (United States of America); Employee Status: Regular; Schedule: Full time; Weekly Hours: 40; FTE: 1.

But schedule also will be in Schedule section; maybe we avoid duplication. Could put schedule info only in Schedule section. The metadata includes schedule; we can drop from metadata and put in Schedule section. Thus metadata p: Primary Location: Remote; Department: IS Epic; Shift: Day (United States of America); Employee Status: Regular; FTE: 1. Now Schedule section:

Schedule

Full time, 40 hours per week.

Now About the role:

About the role

Cincinnati Children’s is advancing its support of Epic tools that how our clinical teams connect, collaborate, and deliver care through an expansion of our Epic Digital Platforms team. Managing applications like Care Everywhere, EpicCare Link, Teamwork, Unified Communications, and Ambient listening technologies, the Epic Digital Platforms team manages products which assure the right information and staff are available at the right time to provide high-quality patient care. This role is critical to ensuring seamless integration, technical excellence, and strategic alignment as we continue to evolve our enterprise communication, ambient listening, and interoperability ecosystem. By strengthening our Epic Digital Platforms team, we are enhancing care coordination, improving workflow efficiency, and supporting safer, more connected patient care delivery across the organization.

At Cincinnati Children’s, we come to work with one goal: to make children’s health better. We believe in a holistic team approach, both in caring for patients and their families, and in advancing science and discovery. We strive to do better and find energy and inspiration in our shared purpose. If you want to be the best you can be, you can do it at Cincinnati Children’s. Cincinnati Children's Is Recognized by U.S. News & World Report as a top 10 best Children's Hospitals in the nation for more than 15 years Consistently among the top 3 Children's Hospitals for National Institutes of Health (NIH) Funding Recognized as one of America’s Best Large Employers (2025), America’s Best Employers for New Grads (2025) One of the nation's America’s Most Innovative Companies as noted by Fortune Consistently certified as great place to work A Leading Disability Employer as noted by the National Organization on Disability Magnet® designated for the fourth consecutive time by the American Nurses Credentialing Center (ANCC) We Embrace Innovation—Together. We believe in empowering our teams with the tools that help us work smarter and care better. That’s why we support the responsible use of artificial intelligence. By encouraging innovation, we’re creating space for new ideas, better outcomes, and a