Epic Certified Beaker Clinical Pathology Laboratory Consultant

We need to output HTML fragment with sections: About the role? Actually the posting includes "We Are Accenture" description (company overview) maybe not needed as "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. Include a section ONLY when posting has real, specific content for it. So we need to decide which sections have content. Content: There's a description of Accenture (company overview) maybe could be "About the role"? Actually "About the role" would be description of role responsibilities. The posting includes "Core Responsibilities" bullet list. So we can have

Responsibilities

with

• items. Then "Here Is What You Need" includes Minimum of 2 years' experience etc. That's qualifications/requirements. Could be

  Requirements

  or

  Qualifications

  . We need to decide. The posting includes "Minimum of 2 years' of experience in Healthcare IT in an Epic Beaker Clinical Pathology Analyst role Experience and certification in Epic Beaker Clinical Pathology Bachelor's degree or equivalent (minimum 12 years) work experience. (If Associate Degree, must have minimum 6 years' of work experience)". Also "Bonus Points If You Have ...". So we can have Requirements (mandatory) and maybe Skills? But we can combine into Requirements. We also have "Compensation at Accenture varies depending on a wide array of factors..." plus a table of salary ranges by location. That's Pay info. So we can have

  Pay

  with maybe a

  describing variation and then a

  of location ranges? The instruction: Use
  • for any list of duties/requirements/benefits. So we can list the salary ranges as list items. Benefits: The posting includes "Benefits Accenture offers a market competitive suite of benefits including medical, dental, vision, life, and long-term disability coverage, a 401(k) plan, bonus opportunities, paid holidays, and paid time off." So we can have

    Benefits

    with
    • . Schedule: The posting includes "This role is located in one of the following locations and will require on-site 3 days per week. Nashville, TN; Atlanta, GA; Columbus, OH; Dallas, TX". That's schedule (on-site 3 days per week) and location. Could be Schedule section: mention on-site 3 days per week. Also location list maybe could be separate but we can include location in Schedule or maybe separate? There's no explicit "Location" heading in allowed list, but we could put location under Schedule or maybe under Pay? Better to include location in Schedule as it's about work arrangement. So Schedule: on-site 3 days per week, locations list. We also have "We anticipate this job posting will be posted until 11/07/2026." That's metadata, could be dropped (minor metadata). Also "Job ID / requisition numbers as headings — fold minor metadata into a short

      or drop it." So we can drop that. We must remove boilerplate: EEO, accommodation, legal statements, etc. So we will omit those sections. We must preserve all substantive information: responsibilities, requirements (including bonus points), benefits, pay (salary ranges), schedule (on-site 3 days per week, locations). Also maybe include the company overview? The instruction: "We Are Accenture is a global professional services company..." That's company description, not role-specific. Could be considered "About the role"? But it's about the company. The allowed headings include "About the role". Could we put that as About the role? It describes Accenture, not the role. Might be considered filler but it's substantive about the employer. The instruction: "Prefer a few substantive sections over many thin ones." Could include a short

      about Accenture under maybe "About the role" or we could omit as not required. The posting includes that at start; but we are told to preserve ALL substantive information. So we should keep it. Where to put? Could be a

      before any headings, as introductory paragraph. That's allowed: we can have prose

      not under a heading. The instruction: Use

      for prose. So we can have an opening

      with the Accenture overview. Then sections: Responsibilities, Requirements, Benefits, Pay, Schedule. Check if any other sections: Skills? Not explicitly separate; we could incorporate skills into Requirements. So fine. Now we need to format HTML fragment only, no or . Use

      for headings. We need to ensure we don't repeat job title as heading. Not needed. Now extract responsibilities list: From posting: "Core Responsibilities Depending on the client engagement, the Epic Beaker Clinical Pathology Laboratory Consultant will be responsible for collaborating with Accenture team, software vendor team, and client in the following areas. Document current state business workflows. Assist with the analysis and design of new business workflows. Identify and define detailed product requirements and use cases. Provide input into high level functional specifications. Work with project managers, architects, business analysts and other team members to define metrics and performance goals for the application. Participate in transitioning the requirements and use cases to ensure a clear and complete understanding of the requirements. Assist in translating requirements and use cases into test conditions and expected results for product, performance, and user acceptance testing. Participate in quality management reviews of the design and performance of work products to ensure they fulfill the requirements. Perform or advise on system configuration and integration setup and assist with testing activities. Serve as an intermediary with client's Epic team and Accenture tech leads to support bilateral understanding of data structures, workflows and technology capabilities and limitations. Assist in the development and documentation of data requests and source to target mapping. Other duties as assigned. This work may include implementation, optimization, upgrades, and application support." We'll make each line a

      . Now Requirements: "Minimum of 2 years' of experience in Healthcare IT in an Epic Beaker Clinical Pathology Analyst role Experience and certification in Epic Beaker Clinical Pathology Bachelor's degree or equivalent (minimum 12 years) work experience. (If Associate Degree, must have minimum 6 years' of work experience) Bonus Points If You Have Minimum of 1 year of experience working for a consulting firm Experience in at least 1 full implementation of Epic Experience in Anatomic Pathology Laboratory Lab Instrument experience" We'll separate mandatory vs bonus? Could keep as list with note. We'll just list all items; maybe we can separate into two

      but not required. We'll just list. Now Benefits: "Accenture offers a market competitive suite of benefits including medical, dental, vision, life, and long-term disability coverage, a 401(k) plan, bonus opportunities, paid holidays, and paid time off." We'll list each benefit as
      • . Now Pay: We have description: "Compensation at Accenture varies depending on a wide array of factors, which may include but are not limited to the specific office location, role, skill set, and level of experience. As required by local law, Accenture provides a reasonable range of compensation for roles that may be hired as set forth below." Then a table of location salary ranges. We'll list each location as
      • with range. Locations list includes many states plus also at bottom: "Nashville, TN Atlanta, GA Columbus, OH Irving, TX". Actually the earlier location list for schedule: Nashville, TN; Atlanta, GA; Columbus, OH; Dallas, TX. The pay table includes many states and also those cities? At bottom they repeated Nashville, TN Atlanta, GA Columbus, OH Irving, TX (maybe a mistake). We'll include all distinct entries from the table. We'll list each as "
      • Location: $X to $Y
      " maybe. Now Schedule: "This role is located in one of the following locations and will require on-site 3 days per week. Nashville, TN; Atlanta, GA; Columbus, OH; Dallas, TX" We'll make a

      stating on-site 3 days per week, then a

      of locations. Now we need to ensure we don't include boilerplate like EEO, accommodation, legal, etc. So we will stop before those sections. We also need to remove duplicated lines: The posting includes "Visit us at www.accenture.com." at start and end; we can keep only once maybe in intro paragraph. We'll craft intro paragraph: "We Are Accenture is a global professional services company with leading capabilities in digital, cloud and security. Combining unmatched experience and specialized skills across more than 40 industries, we offer Strategy and Consulting, Interactive, Technology and Operations services—all powered by the world’s largest network of Advanced Technology and Intelligent Operations centers. Our 674,000 people deliver on the promise of technology and human ingenuity every day, serving clients in more than 120 countries. We embrace the power of change to create value and shared success for our clients, people, shareholders, partners, and communities. Visit us at www.accenture.com." Now after that, we go to sections. Now produce HTML. Check for any stray HTML tags inside text like tags in benefits link etc. We must remove those as they are boilerplate/application instructions? The benefits paragraph includes a link: "See more information on our benefits here: U.S. Employee Benefits | Accenture" That's a link; we should drop the link and just keep the text? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits link is not exactly boilerplate but it's an application instruction? It's a link to benefits details. Might be considered navigation? Safer to drop the link and just keep the benefits description without the link. So we will produce benefits list without the link. Similarly, there may be other links in the posting (like accommodation, EEO). We'll drop those sections entirely. Now ensure we don't include any markdown code fences. Now produce final HTML. Let's draft:

      We Are Accenture is a global professional services company with leading capabilities in digital, cloud and security. Combining unmatched experience and specialized skills across more than 40 industries, we offer Strategy and Consulting, Interactive, Technology and Operations services—all powered by the world’s largest network of Advanced Technology and Intelligent Operations centers. Our 674,000 people deliver on the promise of technology and human ingenuity every day, serving clients in more than 120 countries. We embrace the power of change to create value and shared success for our clients, people, shareholders, partners, and communities. Visit us at www.accenture.com.

      Responsibilities

      • Document current state business workflows.
      • Assist with the analysis and design of new business workflows.
      • Identify and define detailed product requirements and use cases.
      • Provide input into high level functional specifications.
      • Work with project managers, architects, business analysts and other team members to define metrics and performance goals for the application.
      • Participate in transitioning the requirements and use cases to ensure a clear and complete understanding of the requirements.
      • Assist in translating requirements and use cases into test conditions and expected results for product, performance, and user acceptance testing.
      • Participate in quality management reviews of the design and performance of work products to ensure they fulfill the requirements.
      • Perform or advise on system configuration and integration setup and assist with testing activities.
      • Serve as an intermediary with client's Epic team and Accenture tech leads to support bilateral understanding of data