Sr Integration Analyst
Abbott · Illinois, United States · 3 wk ago
Research$78k–$156k/yrFull-time
We need to output HTML fragment with sections using 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 etc. Remove boilerplate. 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 role overview. So we can put that under
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 etc. Remove boilerplate. 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 role overview. So we can put that under About the role
with paragraphs.
- Responsibilities: The "Essential Duties include but are not limited to the following :" list of duties. So we can put Responsibilities
with - each duty.
- Requirements: Minimum Qualifications list. Could be under
Requirements
(or Qualifications). The instruction says we can use sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to use. We have Minimum Qualifications and Preferred Qualifications. Could combine into Requirements and Qualifications? Perhaps Requirements = Minimum Qualifications, Qualifications = Preferred Qualifications. Or we could just have one Qualifications section. But we need to avoid thin sections. Let's create:
- Requirements
for Minimum Qualifications (bullet list).
- Preferred Qualifications
maybe under Qualifications? But we have a section Qualifications. Could use that for Preferred Qualifications. Or we could combine both under Qualifications with subheadings? But we must only use for section headings, not subheadings. So we could have two sections: Requirements (minimum) and Qualifications (preferred). That seems okay.
- Skills: The posting includes many skill statements within Minimum Qualifications (analytical, technical, troubleshooting, etc.) Could be separate Skills section. But we already have those in Minimum Qualifications. Might be redundant. Better to keep Requirements as the list of qualifications (including skills). Could also create a Skills section pulling out skill statements. However we must not invent or summarize away detail; we can keep them as is. If we create a Skills section, we need to extract skill statements from the text. The Minimum Qualifications includes: "Strong analytical, technical, and troubleshooting skills.", "Ability to analyze data, solve problems, 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.", "Skill at tracking tasks, defining next steps, identifying owners, and holding 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 navigate HL7, XML, and HTML.", "Authorization to work in the United States without sponsorship." plus the preferred qualifications: "Corepoint Level 1 and 2 training.", "1+ additional Epic certifications beyond Bridges."
We could separate into Requirements (education, experience, certifications) and Skills (abilities). But the instruction says prefer a few substantive sections over many thin ones. So maybe we keep just two sections: Responsibilities and Requirements (which includes qualifications and skills). But we also need About the role. Pay is present: base pay range $78,000 – $156,000. So we need a Pay section. Schedule? Not mentioned. Benefits? Not mentioned. So we include About the role, Responsibilities, Requirements, Pay.
We must not include sections with filler like "not specified". So we omit Benefits, Schedule.
Now we need to format.
We need to preserve all substantive information. So we need to include the company overview? The "About the role" section should include the position overview paragraph(s). Also maybe include the company description? The instruction says do not repeat job title as heading, but we can include company description as part of About the role? The position overview includes the mission etc. The initial paragraph about Abbott is more company overview; could be included in About the role as context. It's substantive. We'll include it.
Thus About the role: combine the Abbott description and the Position Overview paragraph.
Now Responsibilities: list each duty from "Essential Duties include but are not limited to the following :" through the list ending with "Maintain regular and reliable attendance." plus the physical abilities? Those are more like requirements (physical). Might be better to put them under Requirements as they are qualifications. But they are physical abilities; could be part of Requirements. We'll decide.
Let's extract duties list:
- Mentor other EHR Integration Analysts on, and create best practices for, interface engine development and system integrations.
- Provide EHR integration team representation on both large and small project teams.
- Coordinate with other engineers on evidence-based solutions to meet operational needs.
- Develop new interfaces in the Corepoint interface engine.
- Configure interfaces within the Epic EHR system.
- Work closely with application teams, subject matter experts, and third‐party application experts to determine the business needs for interfaces, document those requirements, and configure the interfaces per the requirements.
- Manage the entire cycle of interface application development, including analysis, design, specification, implementation, go‑live, and support.
- Drive the interface projects, working with the interface project manager to ensure that results are achieved and deadlines are met.
- Develop, write, and execute test plans to ensure that product requirements, quality system requirements, regulatory requirements, and design specifications have been met.
- Monitor the health of live interfaces.
- Provide proactive support by monitoring live interfaces and collaborating with experts to provide permanent solutions to problems.
- Understand data structures and document technical specifications detailing target data elements.
- Analyze and manipulate external data into an appropriate format for HL7 conversion filing into target system.
- Communicate effectively with technical internal and external database analysts.
- Communicate effectively with non-technical leadership from the business.
- Support and comply with the company’s Quality Management System policies and procedures.
- Maintain 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 to travel approximately 5% of working time.
These last three are physical abilities; could be considered requirements but they are listed under Essential Duties. We'll keep them in Responsibilities as they are part of duties list.
Now Requirements (Minimum Qualifications):
- Bachelor’s degree in engineering, physics, computer science, math, information systems, statistics, or related field.
- 5+ years of IT experience supporting system integrations.
- 3+ years of Interface Engine Development.
- Epic Bridges Certification.
- Ability to develop in Corepoint or another interface engine.
- Strong analytical, technical, and troubleshooting skills.
- Ability to analyze data, solve problems, 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.
- Skill at tracking tasks, defining next steps, identifying owners, and holding 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 navigate HL7, XML, and HTML.
- Authorization to work in the United States without sponsorship.
Preferred Qualifications:
- Corepoint Level 1 and 2 training.
- 1+ additional Epic certifications beyond Bridges.
We could put Preferred Qualifications under Qualifications section.
Now Pay: The base pay for this position is $78,000.00 – $156,000.00. In specific locations, the pay range may vary from the range posted.
We'll put that in a
.
Now we need to output only HTML fragment, no markdown fences.
Let's craft:
About the role
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.
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. The Senior Integration Analyst is the primary owner of Exact’s 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 Senior Integration Analyst coordinates the technical design, analysis, validation, and issue triage necessary to implement and support their assigned interfaces. They work closely with the interface project managers, application teams, and technical teams to ensure that new and existing interfaces meet stakeholder needs. They also mentor other interface analysts to help determine technical solutions and act as subject matter expert representation for the team in project and design conversations. They are primarily responsible for the configuration of our interface engine and the interfaces module of our EHR system, as well as the setup of new interfaces that they are assigned. Additionally, they are responsible for monitoring the interface engine to ensure business processes continue. They develop data‐translation routines and methods to support internal and external systems' data and format needs. This position includes a rotating on-call responsibility.
Responsibilities
- Mentor other EHR Integration Analysts on, and create best practices for, interface engine development and system integrations.
- Provide EHR integration team representation on both large and small project teams.
- Coordinate with other engineers on evidence-based solutions to meet operational needs.
- Develop new interfaces in the Corepoint interface engine.
- Configure interfaces within the Epic EHR system.
- Work closely with application teams, subject matter experts, and third‐party application experts to determine the business needs for interfaces, document those requirements, and configure the interfaces per the requirements.
- Manage the entire cycle of interface application development, including analysis, design, specification, implementation, go‑live, and support.
- Drive the interface projects, working with the interface project manager to ensure that results are achieved and deadlines are met.
- Develop, write, and execute test plans to ensure that product requirements, quality system requirements, regulatory requirements, and design specifications have been met.
- Monitor the health of live interfaces.
- Provide proactive support by monitoring live interfaces and collaborating with experts to provide permanent solutions to problems.
- Understand data structures and document technical specifications detailing target data elements.
- Analyze and manipulate external data into an appropriate format for HL7 conversion filing into target system.
- Communicate effectively with technical internal and external database analysts.
- Communicate effectively with non-technical leadership from the business.
- Support and comply with the company’s Quality Management System policies and procedures.
- Maintain 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 to travel approximately 5% of working time.
Requirements
- Bachelor’s degree in engineering, physics, computer science, math
Requirements
(or Qualifications). The instruction says we can use sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to use. We have Minimum Qualifications and Preferred Qualifications. Could combine into Requirements and Qualifications? Perhaps Requirements = Minimum Qualifications, Qualifications = Preferred Qualifications. Or we could just have one Qualifications section. But we need to avoid thin sections. Let's create: -Requirements
for Minimum Qualifications (bullet list). -Preferred Qualifications
maybe under Qualifications? But we have a section Qualifications. Could use that for Preferred Qualifications. Or we could combine both under Qualifications with subheadings? But we must only usefor section headings, not subheadings. So we could have two sections: Requirements (minimum) and Qualifications (preferred). That seems okay. - Skills: The posting includes many skill statements within Minimum Qualifications (analytical, technical, troubleshooting, etc.) Could be separate Skills section. But we already have those in Minimum Qualifications. Might be redundant. Better to keep Requirements as the list of qualifications (including skills). Could also create a Skills section pulling out skill statements. However we must not invent or summarize away detail; we can keep them as is. If we create a Skills section, we need to extract skill statements from the text. The Minimum Qualifications includes: "Strong analytical, technical, and troubleshooting skills.", "Ability to analyze data, solve problems, 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.", "Skill at tracking tasks, defining next steps, identifying owners, and holding 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 navigate HL7, XML, and HTML.", "Authorization to work in the United States without sponsorship." plus the preferred qualifications: "Corepoint Level 1 and 2 training.", "1+ additional Epic certifications beyond Bridges." We could separate into Requirements (education, experience, certifications) and Skills (abilities). But the instruction says prefer a few substantive sections over many thin ones. So maybe we keep just two sections: Responsibilities and Requirements (which includes qualifications and skills). But we also need About the role. Pay is present: base pay range $78,000 – $156,000. So we need a Pay section. Schedule? Not mentioned. Benefits? Not mentioned. So we include About the role, Responsibilities, Requirements, Pay. We must not include sections with filler like "not specified". So we omit Benefits, Schedule. Now we need to format. We need to preserve all substantive information. So we need to include the company overview? The "About the role" section should include the position overview paragraph(s). Also maybe include the company description? The instruction says do not repeat job title as heading, but we can include company description as part of About the role? The position overview includes the mission etc. The initial paragraph about Abbott is more company overview; could be included in About the role as context. It's substantive. We'll include it. Thus About the role: combine the Abbott description and the Position Overview paragraph. Now Responsibilities: list each duty from "Essential Duties include but are not limited to the following :" through the list ending with "Maintain regular and reliable attendance." plus the physical abilities? Those are more like requirements (physical). Might be better to put them under Requirements as they are qualifications. But they are physical abilities; could be part of Requirements. We'll decide. Let's extract duties list: - Mentor other EHR Integration Analysts on, and create best practices for, interface engine development and system integrations. - Provide EHR integration team representation on both large and small project teams. - Coordinate with other engineers on evidence-based solutions to meet operational needs. - Develop new interfaces in the Corepoint interface engine. - Configure interfaces within the Epic EHR system. - Work closely with application teams, subject matter experts, and third‐party application experts to determine the business needs for interfaces, document those requirements, and configure the interfaces per the requirements. - Manage the entire cycle of interface application development, including analysis, design, specification, implementation, go‑live, and support. - Drive the interface projects, working with the interface project manager to ensure that results are achieved and deadlines are met. - Develop, write, and execute test plans to ensure that product requirements, quality system requirements, regulatory requirements, and design specifications have been met. - Monitor the health of live interfaces. - Provide proactive support by monitoring live interfaces and collaborating with experts to provide permanent solutions to problems. - Understand data structures and document technical specifications detailing target data elements. - Analyze and manipulate external data into an appropriate format for HL7 conversion filing into target system. - Communicate effectively with technical internal and external database analysts. - Communicate effectively with non-technical leadership from the business. - Support and comply with the company’s Quality Management System policies and procedures. - Maintain 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 to travel approximately 5% of working time. These last three are physical abilities; could be considered requirements but they are listed under Essential Duties. We'll keep them in Responsibilities as they are part of duties list. Now Requirements (Minimum Qualifications): - Bachelor’s degree in engineering, physics, computer science, math, information systems, statistics, or related field. - 5+ years of IT experience supporting system integrations. - 3+ years of Interface Engine Development. - Epic Bridges Certification. - Ability to develop in Corepoint or another interface engine. - Strong analytical, technical, and troubleshooting skills. - Ability to analyze data, solve problems, 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. - Skill at tracking tasks, defining next steps, identifying owners, and holding 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 navigate HL7, XML, and HTML. - Authorization to work in the United States without sponsorship. Preferred Qualifications: - Corepoint Level 1 and 2 training. - 1+ additional Epic certifications beyond Bridges. We could put Preferred Qualifications under Qualifications section. Now Pay: The base pay for this position is $78,000.00 – $156,000.00. In specific locations, the pay range may vary from the range posted. We'll put that in a
. Now we need to output only HTML fragment, no markdown fences. Let's craft:
About the role
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.
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. The Senior Integration Analyst is the primary owner of Exact’s 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 Senior Integration Analyst coordinates the technical design, analysis, validation, and issue triage necessary to implement and support their assigned interfaces. They work closely with the interface project managers, application teams, and technical teams to ensure that new and existing interfaces meet stakeholder needs. They also mentor other interface analysts to help determine technical solutions and act as subject matter expert representation for the team in project and design conversations. They are primarily responsible for the configuration of our interface engine and the interfaces module of our EHR system, as well as the setup of new interfaces that they are assigned. Additionally, they are responsible for monitoring the interface engine to ensure business processes continue. They develop data‐translation routines and methods to support internal and external systems' data and format needs. This position includes a rotating on-call responsibility.
Responsibilities
- Mentor other EHR Integration Analysts on, and create best practices for, interface engine development and system integrations.
- Provide EHR integration team representation on both large and small project teams.
- Coordinate with other engineers on evidence-based solutions to meet operational needs.
- Develop new interfaces in the Corepoint interface engine.
- Configure interfaces within the Epic EHR system.
- Work closely with application teams, subject matter experts, and third‐party application experts to determine the business needs for interfaces, document those requirements, and configure the interfaces per the requirements.
- Manage the entire cycle of interface application development, including analysis, design, specification, implementation, go‑live, and support.
- Drive the interface projects, working with the interface project manager to ensure that results are achieved and deadlines are met.
- Develop, write, and execute test plans to ensure that product requirements, quality system requirements, regulatory requirements, and design specifications have been met.
- Monitor the health of live interfaces.
- Provide proactive support by monitoring live interfaces and collaborating with experts to provide permanent solutions to problems.
- Understand data structures and document technical specifications detailing target data elements.
- Analyze and manipulate external data into an appropriate format for HL7 conversion filing into target system.
- Communicate effectively with technical internal and external database analysts.
- Communicate effectively with non-technical leadership from the business.
- Support and comply with the company’s Quality Management System policies and procedures.
- Maintain 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 to travel approximately 5% of working time.
Requirements
- Bachelor’s degree in engineering, physics, computer science, math