Art2link ESB is built around six core integration use cases. Most enterprises run two or three of them in production. This page is the map — start with the problem closest to where your team sits today, or pick the one that comes up most often in steering meetings.
Use-case taxonomy aside, the realities of an enterprise environment usually stack multiple solutions on the same platform. Here’s what we see most often.
Clinical message routing between EHRs (Epic, Cerner, Athena) with a full audit trail, plus integrations into ERP/billing systems and Healthcare X12 transactions (270/271 eligibility, 837 claims, 835 remittance) on the payer side. The stack a typical multi-hospital network deploys in year one.
X12 transactions with hundreds of trading partners (204 load tenders, 214 status, 210 invoices), ERP and TMS integrations for billing and fleet operations, and a migration path off the legacy BizTalk that still routes the high-volume freight. Typical for freight and 3PL.
Core banking integrations across SAP, Oracle, and proprietary systems, a wave-based migration path off the legacy BizTalk still running batch settlement, and X12 820/822/824 transactions for commercial banking remittance. Typical for retail and commercial banks.
Most integration vendors sell one of these as their headline and bolt the rest on through acquisitions, third-party adapters, or per-feature SKUs. Art2link was built with all six on the same plane — one App Service deployment, one Entra ID tenant, one transaction-tracking UI. The platform you adopt for migration is the same platform you adopt for HL7, for EDI, for API management.
Industries pages show how the same six solutions deploy inside healthcare, financial services, manufacturing, logistics, insurance, and pharma environments — with vertical-specific compliance and integration patterns.
Describe what you’re trying to do. We’ll point you at the right solution or combination, recommend a starting wave, and show you a working session of the relevant patterns — no slides.