Trading partner network

Healthcare and Pharmaceutical EDI and API integration

Health systems, payers, distributors, pharmaceutical and medical device companies. ECOM connects your business with healthcare organizations through EDI, APIs, managed file transfer and portal automation, integrated with your ERP.

Trading partner network

Healthcare organizations we connect with

Through its network, ECOM can connect your business with 3.1M+ trading partners. The 235 healthcare organizations below are highlights, by name and business segment. Companies with an integration guide link to it, and each guide says whether it rests on the company’s own documents or on typical industry practice.

How the exchange works

How healthcare organizations exchange business documents

Healthcare EDI covers two different areas. In the supply chain, manufacturers, distributors and providers exchange orders, ship notices, invoices and sales reports. Between providers and payers, HIPAA names the X12 standards used for administrative transactions such as claims and remittances.

Common documents with healthcare organizations
DocumentWhat it does in this relationship
EDI 850Purchase Order Purchase orders from hospitals, pharmacies and distributors.
EDI 856Advance Ship Notice Ship notices, often with lot numbers and expiration dates for regulated products.
EDI 810Invoice Invoices, matched against contract prices and receipts.
EDI 867Product Transfer and Resale Report Product transfer and resale reports that distributors send to manufacturers, used for contract pricing and chargebacks.
EDI 837Health Care Claim The health care claim a provider sends to a payer.
EDI 835Health Care Claim Payment/Advice The payer’s claim payment and remittance advice.

What onboarding a new healthcare and pharmaceutical partner usually involves

  1. Separate supply-chain partners from payer connections: they follow different guides and rules.
  2. For payers, follow each payer’s companion guide and enrollment steps for HIPAA transactions.
  3. For products, agree lot, serial and expiration data so ship notices meet traceability requirements.

Integration guides

Healthcare and Pharmaceutical integration guides

Detailed guides covering documents, workflows, connectivity and ERP options for specific companies. A selection is shown here; search all 223 healthcare organizations guides in the directory above.

AbbVie EDI integration

How EDI and API integration with AbbVie typically works: pharmaceutical manufacturing documents, workflows, onboarding and common problems, as typical practice to confirm with AbbVie.

Read the guide

Agilent Technologies EDI integration

How EDI and API integration with Agilent Technologies typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Agilent Technologies.

Read the guide

Alkermes EDI integration

How EDI and API integration with Alkermes typically works: pharmaceutical manufacturing documents, workflows, onboarding and common problems, as typical practice to confirm with Alkermes.

Read the guide

Alnylam Pharmaceuticals EDI integration

How EDI and API integration with Alnylam Pharmaceuticals typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Alnylam Pharmaceuticals.

Read the guide

Amgen EDI integration

How EDI and API integration with Amgen typically works: pharmaceutical manufacturing documents, workflows, onboarding and common problems, as typical practice to confirm with Amgen.

Read the guide

Amneal Pharmaceuticals EDI integration

How EDI and API integration with Amneal Pharmaceuticals typically works: pharmaceutical manufacturing documents, workflows, onboarding and common problems, as typical practice to confirm with Amneal Pharmaceuticals.

Read the guide

argenx US EDI integration

How EDI and API integration with argenx US typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with argenx US.

Read the guide

Ascendis Pharma US EDI integration

How EDI and API integration with Ascendis Pharma US typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Ascendis Pharma US.

Read the guide

AstraZeneca US EDI integration

How EDI and API integration with AstraZeneca typically works: pharmaceutical manufacturing documents, workflows, onboarding and common problems, as typical practice to confirm with AstraZeneca.

Read the guide

Bausch + Lomb EDI integration

How EDI and API integration with Bausch + Lomb typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Bausch + Lomb.

Read the guide

Bausch Health EDI integration

How EDI and API integration with Bausch Health typically works: pharmaceutical manufacturing documents, workflows, onboarding and common problems, as typical practice to confirm with Bausch Health.

Read the guide

Baxter International EDI integration

How EDI and API integration with Baxter International typically works: pharmaceutical manufacturing documents, workflows, onboarding and common problems, as typical practice to confirm with Baxter International.

Read the guide

General EDI flow

How EDI with your trading partner typically works

Many trading partners do not publish their EDI or API specifications. This is the general sequence most programs of this kind follow.

  1. 850 Purchase order

    From your trading partner

    The buyer sends the order: items, quantities, prices, ship-to and requested dates.

  2. 855 Order acknowledgment

    From you to your trading partner

    You confirm, change or reject the order, where the partner asks for it.

  3. 856 Advance ship notice

    From you to your trading partner

    You tell the buyer what is on the shipment, with the carton and label details the buyer needs to receive it.

  4. 810 Invoice

    From you to your trading partner

    You bill for what shipped, in the format the buyer's payables system expects.

  5. 997 Functional acknowledgment

    Both directions

    Each side confirms that every file it received was readable. A rejected file is corrected and resent.

Need help with the specification?

Tell ECOM which program you are in and what the partner has given you. We help you read it, confirm the applicable requirements, map them to your systems and test against them. Do not send passwords or EDI identifiers with your request.

Connecting with a healthcare and pharmaceutical partner not listed here?

ECOM connects businesses with partners of every size using their published EDI, API or file requirements.