Packaged/SaaS Application Engineer-Epic Integration

We need to output HTML fragment with sections: About the role? The posting includes Job Description/Responsibilities etc. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if there is real specific content. We must not repeat job title as heading. No Job ID. Remove boilerplate. Must preserve all substantive info. We need to parse the posting: Title: Packaged/SaaS Application Engineer-Epic Integration - CorePoint. Location: Remote. Contract Duration: 6-7 months contract with chances of extension. Then "Job Description/ Responsibilities What are must-have skills for this role?" Then sections: Required Experience (list of bullet-like sentences). Then "Experience working within integrated healthcare delivery networks..." etc. Then "Core Technical Skills" with sub-bullets. Then "Epic Experience (Preferred)". Then "Integration Architecture". Then "Operational Support". Then "Preferred Certifications And Experience". Then "Desired Project Experience". Also "Corepoint Interface Engine required." etc. We need to decide sections: Could have "About the role" (maybe location and contract). "Responsibilities" (maybe the duties). "Requirements" (must-have skills). "Qualifications" (preferred certifications). "Skills" (technical skills). "Benefits" none. "Pay" none. "Schedule" none. We must not create sections with placeholder like "not specified". So only include sections with content. We need to preserve all substantive info; not invent or summarize away detail. So we need to list bullet points for each piece. We need to use

• for any list of duties/requirements/benefits. Use

  for prose. Thus we can have:

  About the role

  Location: Remote. Contract Duration: 6‑7 months contract with chances of extension.

  Responsibilities

  • Support large healthcare organizations with hundreds of active interfaces using Corepoint Interface Engine.
  • Serve as lead engineer, architect, or technical SME.
  • Mentor junior engineers and transfer knowledge.
  • Develop technical documentation and build organizational capability to reduce dependency on individual resources.
  • Provide production support, including interface monitoring, alert management, root cause analysis, incident response, on‑call support, upgrade planning.
  • Collaborate with clinicians, operational leaders, application teams, vendors, and business stakeholders to develop integration solutions.
  • Support healthcare mergers, acquisitions, Epic implementations, application consolidations, or other enterprise transformation initiatives.
  • Perform Corepoint upgrades and migrations.
  • Support hospital acquisitions and onboarding initiatives.
  But we need to ensure we don't duplicate content. The posting includes many bullet-like sentences under "Required Experience", "Experience working within integrated healthcare delivery networks...", "Experience Supporting And Implementing Interfaces Involving ...", "Demonstrated understanding of patient safety considerations...", "Experience collaborating directly...", "Knowledge of HIPAA...", "Experience supporting healthcare mergers...", "Core Technical Skills" list, "Epic Experience (Preferred)" list, "Integration Architecture" list, "Operational Support" list, "Preferred Certifications And Experience" list, "Desired Project Experience" list. We need to preserve all substantive info. So we need to include all those points, maybe grouped under appropriate sections: Responsibilities, Requirements, Qualifications, Skills. We must not repeat content. So we need to decide mapping. Let's extract each bullet: From "Required Experience": - Minimum 5 years Corepoint Interface Engine experience. - Experience supporting large healthcare organizations with hundreds of active interfaces. - Experience serving as a lead engineer, architect, or technical SME. - Demonstrated experience mentoring junior engineers. - Proven success transferring knowledge, developing technical documentation, and building organizational capability to reduce dependency on individual resources. - Experience working in production support. From "Clinical Healthcare Experience Required": - Experience working within integrated healthcare delivery networks, hospitals, ambulatory clinics, and ancillary care environments. - Strong understanding of healthcare workflows, including patient registration, admissions, transfers, discharges, orders, results, medication management, scheduling, and care coordination. - Experience integrating clinical, operational, and business systems within complex healthcare organizations. - Experience Supporting And Implementing Interfaces Involving Electronic Health Records, Laboratory Information Systems, Radiology Information Systems, Pharmacy systems, Revenue cycle platforms, Medical device integrations, Patient engagement solutions, Health Information Exchange technologies. - Demonstrated understanding of patient safety considerations associated with interface design, message transformation, routing logic, downtime procedures, and production support activities. - Experience collaborating directly with clinicians, operational leaders, application teams, vendors, and business stakeholders to develop integration solutions. - Knowledge of HIPAA, healthcare privacy, security, and regulatory requirements related to electronic information exchange. - Experience supporting healthcare mergers, acquisitions, Epic implementations, application consolidations, or other enterprise transformation initiatives. From "Core Technical Skills": - Interface Engines: Corepoint Interface Engine required. - Messaging Standards: HL7 v2.x, FHIR, X12, NCPDP, XML, JSON, Flat file integrations. - Epic Experience (Preferred): Epic Bridges, Epic Care Everywhere, Epic Web Services / APIs, Epic Interconnect, Epic upgrade coordination. - Integration Architecture: End-to-end interface design, including requirements gathering. Message transformation design. Code set and correlation management. API integrations. Database integrations. SFTP and file-based workflows. High-availability design. Disaster recovery planning and implementation. - Operational Support: Interface monitoring. Alert management. Root cause analysis. Production incident response. On-call support. Upgrade planning. From "Preferred Certifications And Experience": - Corepoint Certified Associate - Corepoint Certified Professional - Epic Bridges Certification - Epic Interconnect/API experience - Healthcare Integration Architecture experience From "Desired Project Experience": - Corepoint upgrades and migrations. - Hospital acquisitions and onboarding initiatives. We also have location and contract duration. Now we need to decide sections. Potential sections: - About the role (location, contract) - Responsibilities (maybe the duties: support, lead engineer, mentor, documentation, production support, collaboration, etc.) - Requirements (must-have: 5 years Corepoint, supporting large orgs, lead engineer experience, mentoring, knowledge transfer, production support, clinical healthcare experience, workflow understanding, integration experience, patient safety, HIPAA, etc.) - Qualifications (preferred certifications: Corepoint certs, Epic Bridges cert, Epic Interconnect/API experience, Healthcare Integration Architecture experience) - Skills (technical skills: Corepoint, messaging standards, Epic experience preferred, integration architecture, operational support) - Desired Project Experience could be under Requirements or separate "Desired Experience". But we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put desired project experience under Requirements or Skills. Probably under Requirements as "Desired project experience" but it's not a must-have; still it's substantive. Could also put under Qualifications? But Qualifications is for certifications etc. We'll put under Requirements as a subsection? But we cannot create subheadings besides h3. We could just include as list items under Requirements. We must not create sections with placeholder text. So we will include only those sections with content. Thus final HTML:

  About the role

  Location: Remote. Contract Duration: 6‑7 months contract with chances of extension.

  Responsibilities

  • Support large healthcare organizations with hundreds of active interfaces using Corepoint Interface Engine.
  • Serve as lead engineer, architect, or technical SME.
  • Mentor junior engineers and transfer knowledge.
  • Develop technical documentation and build organizational capability to reduce dependency on individual resources.
  • Provide production support, including interface monitoring, alert management, root cause analysis, incident response, on‑call support, and upgrade planning.
  • Collaborate with clinicians, operational leaders, application teams, vendors, and business stakeholders to develop integration solutions.
  • Support healthcare mergers, acquisitions, Epic implementations, application consolidations, or other enterprise transformation initiatives.
  • Perform Corepoint upgrades and migrations.
  • Support hospital acquisitions and onboarding initiatives.

  Requirements

  • Minimum 5 years Corepoint Interface Engine experience.
  • Experience supporting large healthcare organizations with hundreds of active interfaces.
  • Experience serving as a lead engineer, architect, or technical SME.
  • Demonstrated experience mentoring junior engineers.
  • Proven success transferring knowledge, developing technical documentation, and building organizational capability to reduce dependency on individual resources.
  • Experience working in production support.
  • Experience working within integrated healthcare delivery networks, hospitals, ambulatory clinics, and ancillary care environments.
  • Strong understanding of healthcare workflows, including patient registration, admissions, transfers, discharges, orders, results, medication management, scheduling, and care coordination.
  • Experience integrating clinical, operational, and business systems within complex healthcare organizations.
  • Experience supporting and implementing interfaces involving Electronic Health Records, Laboratory Information Systems, Radiology Information Systems, Pharmacy systems, Revenue cycle platforms, Medical device integrations, Patient engagement solutions, and Health Information Exchange technologies.
  • Demonstrated understanding of patient safety considerations associated with interface design, message transformation, routing logic, downtime procedures, and production support activities.
  • Experience collaborating directly with clinicians, operational leaders, application teams, vendors, and business stakeholders to develop integration solutions.
  • Knowledge of HIPAA, healthcare privacy, security, and regulatory requirements related to electronic information exchange.
  • Experience supporting healthcare mergers, acquisitions, Epic implementations, application consolidations, or other enterprise transformation initiatives.
  • Desired project experience: Corepoint upgrades and migrations; hospital acquisitions and onboarding initiatives.

  Qualifications

  • Corepoint Certified Associate
  • Corepoint Certified Professional
  • Epic Bridges Certification
  • Epic Interconnect/API experience
  • Healthcare Integration Architecture experience

  Skills

  • Corepoint Interface Engine (required)
  • Messaging Standards: HL7 v2.x, FHIR, X12, NCPDP, XML, JSON, Flat file integrations
  • Epic Experience (Preferred): Epic Bridges, Epic Care Everywhere, Epic Web Services / APIs, Epic Interconnect, Epic upgrade coordination
  • Integration Architecture: End-to-end interface design (requirements gathering), message transformation design, code set and correlation management, API integrations, database integrations, SFTP and file-based workflows, high-availability design, disaster recovery planning and implementation
  • Operational Support: Interface monitoring, alert management, root cause analysis, production incident response, on-call support, upgrade planning
  We must not include Benefits, Pay, Schedule sections as they are not present. Check for any duplicated content: We have some overlapping like "Experience supporting healthcare mergers..." appears both in Requirements and maybe also in Responsibilities? We included in Responsibilities as "Support healthcare mergers, acquisitions, Epic implementations, application consolidations, or other enterprise transformation initiatives." That's similar but not duplicate exactly; it's okay to have similar but we should avoid repeating same sentence. We have it in both Responsibilities and Requirements. Might be considered duplication. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines". Duplicated lines means exact duplicate lines. Slight variation may be okay but better to avoid duplication. We could move the mergers/acquisitions/Epic implementations to either Responsibilities or Requirements, not both. Since it's more of a responsibility/experience, maybe put