Integration Analyst

We need to output HTML fragment with sections 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. No Job ID. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Content: - Intro about Abbott: "Abbott is a global healthcare leader..." This is about company, could be "About the role"? Actually "About the role" maybe includes overview. The posting includes "Position Overview At Abbott Cancer Diagnostics, we're cancer fighters..." That's about role. So we can put that in

About the role

with paragraphs. - Responsibilities: The "Essential Duties include but are not limited to the following :" list many bullet-like sentences. Those are duties. So we can create

Responsibilities

with

• each duty. - Requirements: Minimum Qualifications section: Bachelor’s degree... or High School... 3+ years IT experience... Authorization to work in US without sponsorship. That's qualifications. Could be under Requirements or Qualifications. We'll separate: Requirements maybe minimum qualifications; Qualifications maybe preferred qualifications. But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Minimum Qualifications and Preferred Qualifications. Could map Minimum to Requirements, Preferred to Qualifications. Skills: Many ability statements after duties: "Ability to understand data structures..." etc. Those are skills. Could put under Skills. Benefits: Not mentioned explicitly. No benefits listed. So we should not include Benefits section. Pay: The posting includes "The base pay for this position is $61,300.00 – $122,700.00. In specific locations, the pay range may vary from the range posted." That's pay info. So include Pay section. Schedule: Not mentioned. No schedule info. So omit Schedule. We must not include sections with placeholder/filler. So only include About the role, Responsibilities, Requirements, Qualifications, Skills, Pay. We need to preserve all substantive info; do not invent or summarize away detail. Must keep all details. We need to format as HTML fragment, no /, no markdown fences. We'll produce:

  About the role

  ... (company overview + position overview)

  But we need to ensure we don't duplicate content. Let's extract the substantive paragraphs: First paragraph: "Abbott is a global healthcare leader that helps people live more fully at all stages of life. Our portfolio of life-changing technologies spans the spectrum of healthcare, with leading businesses and products in diagnostics, medical devices, nutritionals and branded generic medicines. Our 122,000 colleagues serve people in more than 160 countries." Second: "Position Overview At Abbott Cancer Diagnostics, we're cancer fighters. That's not a tagline, it's the reason we come to work every day. Our mission is to change lives through advances in cancer detection and treatment guidance, and ultimately to help eradicate the disease and the suffering it causes. Everything we build, including the software you'd be leading, exists to move that mission forward." Third: "The Integration Analyst is the primary owner of Exacts’ EHR HL7 interfaces. This involves stewardship of both internal EHR integrations with other systems, as well as external integrations, such as order and result interfaces, with healthcare partners. The Integration Analyst coordinates the technical design, analysis, validation, and issue triage necessary to implement and support their assigned interfaces. They work closely with client implementation project managers, operational teams, and other technical teams to ensure that new and existing interfaces meet the needs of our end users. They also work regularly with external partner teams during implementation and ongoing support of external interfaces. The Integration Analyst is responsible for building new integrations, augmenting and improving existing ones, and troubleshooting interface issues as they arise. They are also responsible for monitoring error work queues to understand data quality trends and make corrections when necessary. This position includes a rotating on-call responsibility." We could combine these into About the role section. Might be long but okay. Now Responsibilities: list each duty after "Essential Duties include but are not limited to the following :". The list includes many sentences separated by periods. We need to split into list items. Let's extract each duty sentence: - Manage the entire cycle of interface application development, including analysis, design, specification, implementation, go‐live, and support. - Build and support integrations between our EHR and other systems using the Corepoint interface engine. - Work closely with application teams, subject matter experts, and third‐party application experts to determine the business needs for interfaces, document the requirements, and configure the interfaces per the requirements. - Partner with external interface project teams to collaboratively build new connections. - Partner with internal networking resources to configure and troubleshoot VPNs with external interface partners. - Work with internal and external groups to diagnose and resolve interface‐related issues. - Engage with cross-functional experts, vendors, and other application analysts on interface‐related tasks and activities like build steps, validation, cutover planning, and going live. - Work alongside the implementation project manager to ensure that high quality results are achieved and deadlines are met. - Communicate challenges and roadblocks on projects to all of the relevant stakeholders and members of management. - Provide proactive support by monitoring live interfaces and collaborating with experts to provide permanent resolutions to problems. - Define the transport method by which source system data will be communicated to target systems. - Analyze and manipulate external and internal data into an appropriate format for HL7 messaging between systems. - Troubleshoot the data transport mechanism. - Interpret the defined scope and defined business requirements for each dataset in the creation of each technical specification. - Ability to understand data structures and documenting technical specifications detailing data elements and HL7 message structures. - Communicate effectively and efficiently with both technical and non-technical audiences in meetings, virtual working sessions, emails, and phone calls. - Strong analytical, technical, and troubleshooting skills. - Ability to analyze data, problem‐solve, and clearly communicate solutions. - Ability to understand organizational requirements and their impact on the technical aspects of a solution. - Ability to work in a complex multi‐communication‑channel environment. - Ability to track tasks, define next steps, identify owners, and hold people accountable. - Ability to coordinate activities involving multiple players, including vendors, subject matter experts, interface engine developers, and end users, to design, configure, and test interfaces. - Ability to parse HL7 and XML. - Ability to collaborate cross-functionality to resolve complex issues. - Excellent communication and interpersonal skills; ability to interact with all levels of internal and external audiences. - Ability to balance critical thinking and attention to detail. - Uphold company mission and values through accountability, innovation, integrity, quality, and teamwork. - Support and comply with the company’s Quality Management System policies and procedures. - Regular and reliable attendance. - Ability to lift up to 10 pounds for approximately 5% of a typical working day. - Ability to work on a mobile device, tablet, or in front of a computer screen and/or perform typing for approximately 90% of a typical working day. - Ability and means to travel between Madison locations. Some of these are abilities/skills; but they are listed under Essential Duties. We'll keep them as responsibilities. Now Requirements (minimum qualifications): "Bachelor’s degree in Engineering, Physics, Computer Sciences, Math, Information Systems, Statistics, or related field; or High School Degree/General Education Diploma and 4 years of relevant experience in lieu of Bachelor’s degree. 3+ years of IT experience supporting system integrations. Demonstrated ability to perform the Essential Duties of the position with or without accommodation. Authorization to work in the United States without sponsorship." We'll put as
  • each. Qualifications (preferred): "Epic Bridges certification. 3+ years of experience with the Corepoint interface engine or a similar system." Skills: Many ability statements after duties (some overlapping). But we already included many ability statements in responsibilities. However we still have some ability statements that are more skill-like: "Ability to understand data structures and documenting technical specifications detailing data elements and HL7 message structures." etc. Actually those are already in responsibilities list. To avoid duplication, we could still include them under Skills but that would duplicate content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not prohibited but might be redundant. Better to avoid duplication by moving skill-like statements to Skills section and not duplicate them in Responsibilities. However the responsibilities list includes many ability statements; we could keep them there and not have a separate Skills section. But we need to include Skills section only if there is real specific content for it. We could decide to not include Skills section because the abilities are already covered under Responsibilities. However the instruction says "Prefer a few substantive sections over many thin ones." So we could omit Skills if its content is already covered. But we need to ensure we don't lose any substantive info. If we omit Skills, we still have the ability statements in Responsibilities, so info preserved. So we can omit Skills. But we need to check if there are any ability statements not already in Responsibilities list. Let's review the text after duties: after the list of duties, there is a block: "Ability to understand data structures and documenting technical specifications detailing data elements and HL7 message structures. Communicate effectively and efficiently with both technical and non-technical audiences in meetings, virtual working sessions, emails, and phone calls. Strong analytical, technical, and troubleshooting skills. Ability to analyze data, problem‐solve, and clearly communicate solutions. Ability to understand organizational requirements and their impact on the technical aspects of a solution. Ability to work in a complex multi‐communication‑channel environment. Ability to track tasks, define next steps, identify owners, and hold people accountable. Ability to coordinate activities involving multiple players, including vendors, subject matter experts, interface engine developers, and end users, to design, configure, and test interfaces. Ability to parse HL7 and XML. Ability to collaborate cross-functionality to resolve complex issues. Excellent communication and interpersonal skills; ability to interact with all levels of internal and external audiences. Ability to balance critical thinking and attention to detail. Uphold company mission and values through accountability, innovation, integrity, quality, and teamwork. Support and comply with the company’s Quality Management System policies and procedures. Regular and reliable attendance. Ability to lift up to 10 pounds for approximately 5% of a typical working day. Ability to work on a mobile device, tablet, or in front of a computer screen and/or perform typing for approximately 90% of a typical working day. Ability and means to travel between Madison locations." Many of these are similar to duties but some are not exactly same phrasing. For example "Ability to understand data structures and documenting technical specifications detailing data elements and HL7 message structures." is similar to duty "Ability to understand data structures and documenting technical specifications detailing data elements and HL7 message structures." Actually that exact sentence appears in duties list as well? Let's check duties list: I included "Ability to understand data structures and documenting technical specifications detailing data elements and HL7 message structures." as a duty item. Yes I included that. So duplicate. "Communicate effectively and efficiently with both technical and non-technical audiences in meetings, virtual working sessions, emails, and phone calls." appears as duty item "Communicate effectively and efficiently with both technical and non-technical audiences in meetings, virtual working sessions, emails, and phone calls." Yes included. "Strong analytical, technical, and troubleshooting skills." appears as duty item "Strong analytical, technical, and troubleshooting skills." Yes. "Ability to analyze data, problem‐solve, and clearly communicate solutions." appears as duty item "Ability to analyze data, problem‐solve, and clearly communicate solutions." Yes. "Ability to understand organizational requirements and their impact on the technical aspects of a solution." appears as duty item "Ability to understand organizational requirements and their impact on the technical aspects of a solution." Yes. "Ability to work in a complex multi‐communication‑channel environment." appears as duty item "Ability