Healthcare and Pharmaceutical integration

Intermountain Health EDI integration

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

At a glance

Intermountain Health integration, in three pictures

The industry, the document flow and the outcome for your team. Illustrations only: they show typical practice, not a specific Intermountain Health program or a customer relationship.

Illustration of a hospital building, a pill bottle and a medical cross, representing the healthcare and pharmaceutical industry that Intermountain Health operates in.
Industry. Healthcare and Pharmaceutical: where Intermountain Health operates.
Workflow diagram: your ERP and distribution systems exchange documents with Intermountain Health through ECOM. You send 855, 856, 810, 846; you receive 850; 835 and 997 acknowledgments go both ways. Your systems ERP · distribution · finance ECOM integration map · validate · connect · monitor Intermountain Health 855 856 810 846 855 856 810 846 850 850 835 997 both ways
Workflow. Documents in each direction. Orange: you send. Blue: you receive. Typical, not confirmed.
Comparison diagram: without integration, documents are re-keyed, files are emailed and rejections are found late; with ECOM, documents are mapped to your ERP, validated and monitored, and exceptions are visible early. Without integration Orders re-keyed by hand Files emailed or uploaded Rejections found late With ECOM Documents mapped to your ERP Every file validated and monitored Exceptions visible early
Outcome. From manual handling to a monitored flow. No figures: results depend on your setup.

Talk to an EDI/API Expert about Intermountain Health

Tell us which documents you exchange with Intermountain Health, which ERP you run and when you need to be live. A specialist will outline the connection, mapping and testing plan. This page is a guide based on typical practice; it does not mean ECOM works with Intermountain Health.

  • Review of Intermountain Health's requirements with you, once you have them
  • EDI and API integration with your ERP and distribution systems
  • Monitoring and managed service after go-live, if you want it

Prefer to call? Sales 972-836-7750 or email sales@ecom-specialist.com.

Takes about 30 seconds. Phone and note are optional.

Your request is about

Trading partner
Intermountain Health

When should we talk?

Times are in your time zone. We use this to schedule the conversation.

We use your details only to respond to your request. See our privacy notice. Prefer to talk? Call Sales at 972-836-7750.

Integration and onboarding

How Intermountain Health integration fits your systems

Your systemsERP, distribution and accounting
ECOMMapping, validation, connectivity and monitoringAS2, SFTP or VAN · API or portal
Intermountain HealthIts program, documents and requirements
  1. ConfirmConfirm your Intermountain Health program, role and the documents it requires.
  2. MapMap each document to your ERP fields and business rules.
  3. ConnectConfigure the connection and security the program needs.
  4. TestTest against the applicable specifications and acknowledgments.
  5. Go liveGo live with monitoring, alerts and exception handling.
Typical implementation path. Exact requirements are confirmed against the applicable specifications during onboarding.

Overview

Understanding Intermountain Health integration

Who this is for: Medical-surgical, pharmaceutical and equipment suppliers, distributors and revenue-cycle partners that exchange orders, invoices and remittance data with Intermountain Health.

Scope: This guide describes typical practice for this kind of trading relationship; Intermountain Health's own program details are confirmed during onboarding.

Intermountain Health is a Utah-based nonprofit health system, which includes IHC Health Services, with hospitals across several states and a health plan. ECOM's directory lists it under hospital system.

Operating hospitals, clinics and a health plan means supply documents and claim flows both run through finance. For a health system there are two document families. On the supply side it buys medical, surgical and pharmaceutical products and services and typically handles purchase orders, acknowledgments, ship notices, invoices and inventory data with suppliers and distributors. On the revenue side it receives claim payments and remittance advice from payers (X12 835), which finance teams post to patient accounts. Typical practice keeps these separate and secures patient-related data under healthcare privacy rules.

Intermountain Health's own EDI or API specification is not part of this guide. What follows is typical practice for hospital system, so confirm the documents, formats, delivery method and testing steps with Intermountain Health. ECOM helps confirm your trading program, map the required documents, configure connectivity, and complete testing against the applicable specifications, as software, as a managed service or both.

Business scenarios

Where Intermountain Health integration gets complicated

Typical requirements—confirm with your trading partner.

Integrated system and plan

Operating hospitals, clinics and a health plan means supply documents and claim flows both run through finance.

How ECOM helps: ECOM maps the data in your ERP or finance system to the format Intermountain Health's program needs, validates it before it is sent and routes exceptions to a named owner.

What you gain: Problems are found on your side, before they turn into rejections or delayed payment.

Supply chain and payer remittance

Intermountain Health buys supplies from many distributors and manufacturers while receiving claim payments from many payers, so purchasing documents and remittance advice are two separate high-volume flows.

How ECOM helps: ECOM connects purchase-to-pay documents to your ERP and maps remittance files to your revenue-cycle systems, monitoring each file.

What you gain: Fewer invoice exceptions and faster, cleaner posting of payments.

Workflows

Typical Intermountain Health business workflows

Typical requirements—confirm with your trading partner. Typical flows in this industry, not Intermountain Health's published process.

Supply order to invoice

  1. 1Receive 850 purchase order
  2. 2Send 855 acknowledgment
  3. 3Send 856 ship notice
  4. 4Send 810 invoice
  5. 5Receive payment

Documents and APIs

Intermountain Health documents by program

General guidance. We could not verify Intermountain Health's EDI requirements from a published source, so these are documents commonly exchanged in this industry, not Intermountain Health's confirmed requirements. Confirm the list, versions and programs with Intermountain Health.

DocumentNameDirectionProgramStatusPurpose
850 Purchase Order From Intermountain Health Not stated General guidance Typically carries an order for equipment, materials or services: items, quantities, prices, delivery locations and dates.
855 Purchase Order Acknowledgment To Intermountain Health Not stated General guidance Typically confirms an order, or reports changes to quantities, prices or dates.
856 Ship Notice/Manifest To Intermountain Health Not stated General guidance Typically tells the receiver what is on each shipment, with serial numbers or carton detail where the program needs them.
810 Invoice To Intermountain Health Not stated General guidance Typically bills for goods or services delivered, matched against the order or contract.
846 Inventory Inquiry/Advice To Intermountain Health Not stated General guidance Typically shares inventory positions or availability between the two sides.
835 Health Care Claim Payment/Advice Both directions Not stated General guidance Typically explains payer payments and adjustments on claims, for posting to patient accounts.
997 Functional Acknowledgment Both directions Not stated General guidance Typically confirms that each file was received and could be read.

Connectivity

How companies connect

  • AS2, SFTP or VAN

    Trading partners commonly exchange EDI over AS2, SFTP or a value-added network.

    General guidance

  • API or portal

    Some programs use REST APIs, a supplier or vendor portal, or a cloud service for part of the flow. A login is usually required for portals.

    General guidance

Challenges

Common integration challenges

  • Item and contract pricing

    Supply items are bought under contract prices through group purchasing programs, so invoice prices must match the contract.

  • Remittance posting

    Payer remittance (835) has to be applied to the correct patient accounts, with adjustments and denials categorized.

  • Program-specific rules

    Requirements differ by program and are set by Intermountain Health's procurement, finance or operations teams, so confirm them before you build maps.

  • Program-specific details

    The documents, identifiers, versions and test steps for your program are set by Intermountain Health. ECOM works from them during mapping and testing.

Automation options for Intermountain Health suppliers

Four ways to automate. One foundation.

ECOM helps you automate them, meet Intermountain Health's labeling and ship notice requirements, and see what needs action. Intermountain Health sets its program's rules; ECOM confirms which options fit yours.

PRISM Supply Chain Automation Foundation

One platform beneath every option. Use one, or combine them for different partners and documents.

Compliance and actionable visibility

Connect order processing, shipping documentation, trading partner requirements, and performance monitoring through one coordinated workflow. These capabilities help teams improve shipment accuracy, reduce manual work, address compliance risks, and respond to exceptions before they affect customers.

Discuss Your Trading Partner Requirements

Connect Intermountain Health documents to your ERP

ECOM connects the documents and files you exchange with Intermountain Health to your ERP and finance systems, so orders, invoices and payments post without re-keying and reconcile from the data you already hold.

Industry

Healthcare

See how ECOM supports healthcare suppliers and providers.

Solution

Procure-to-Pay Automation

Connect purchase orders, receipts and invoices for a provider's supply chain.

Service

Trading Partner Setup

Have ECOM confirm the program, map the documents and test with the trading partner before go-live.

Zero Trust for EDI and file transfer

Zero Trust EDI and MFT for your Intermountain Health connection

Exchanges with Intermountain Health move business documents between your systems and an outside party. A Zero Trust design assumes no connection, file or user is safe by default.

  • Authentication

    Every connection proves who it is: partner-specific accounts with SSH keys or certificates over SFTP, FTPS, HTTPS or AS2, never a shared login.

    Business outcome: A lost or reused credential affects one partner, not all of them.

  • Least privilege

    Each partner and user reaches only its own folders, file types and actions. Internal user permissions are managed centrally and reviewed with you.

    Business outcome: A mistake or compromise in one account stays limited to what that account could reach.

  • Isolation

    Partners are kept apart by account and file area. Where your design calls for it, a proxy or DMZ keeps outside connections away from internal systems. The design follows your architecture.

    Business outcome: Outside connections do not land directly on your internal systems.

  • Encryption

    Encrypted protocols in transit and PGP for files at rest. Encryption protects the data. It is one control, and not Zero Trust on its own.

    Business outcome: Less exposure if a file is intercepted or a file store is reached.

  • Certificate and key management

    Partner keys and certificates are managed centrally. Renewal and rotation are planned with you, so an expiring certificate does not stop a flow.

    Business outcome: Fewer outages caused by an expired certificate or key.

  • Monitoring and access controls

    Real-time transfer status and alerts for late, missing or failed files, so unexpected access or a broken flow is seen quickly.

    Business outcome: Late, missing or failed files are noticed early, before they hold up payment, shipping or reporting.

  • Audit trail

    Every transfer is logged with sender, receiver, time and outcome, which supports your own review and audit work.

    Business outcome: You can answer who sent what and when, for your own audits and partner reviews.

What this means for your data

Partner access

Each trading partner connects with its own identity and a limited scope, and any connection can be reviewed or removed on its own.

File and document handling

Documents are verified when they arrive and every transfer is logged.

Exceptions

Late, missing or rejected files raise an alert and go to a named owner.

Zero Trust is an approach, not a product or a certification. ECOM covers the EDI and file-transfer side. Your identity, network and endpoint controls stay yours, and so does the assessment of your own compliance obligations. ECOM does not guarantee compliance or any security outcome. Intermountain Health may set its own security requirements, which come first.

General EDI flow

How EDI with Intermountain Health typically works

The documents, their order and the timing are Intermountain Health's to set; this is the general sequence most programs of this kind follow.

  1. 850 Purchase Order

    From Intermountain Health to you

    Typically carries an order for equipment, materials or services: items, quantities, prices, delivery locations and dates.

  2. 855 Purchase Order Acknowledgment

    From you to Intermountain Health

    Typically confirms an order, or reports changes to quantities, prices or dates.

  3. 856 Ship Notice/Manifest

    From you to Intermountain Health

    Typically tells the receiver what is on each shipment, with serial numbers or carton detail where the program needs them.

  4. 810 Invoice

    From you to Intermountain Health

    Typically bills for goods or services delivered, matched against the order or contract.

  5. 846 Inventory Inquiry/Advice

    From you to Intermountain Health

    Typically shares inventory positions or availability between the two sides.

  6. 835 Health Care Claim Payment/Advice

    Both directions

    Typically explains payer payments and adjustments on claims, for posting to patient accounts.

  7. 997 Functional Acknowledgment

    Both directions

    Typically confirms that each file was received and could be read.

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.

Next step

Get help with your Intermountain Health program

Each request goes to an ECOM EDI specialist with Intermountain Health's name attached, so the reply starts from your program.

  • Review Intermountain Health's requirements

    Send us Intermountain Health's guide or your program details; we explain the documents, rules and options for meeting them.

    Request a requirements review
  • Connect Intermountain Health to your ERP

    The documents you exchange, in and out of the ERP and operating systems you already run.

    Discuss ERP integration
  • Testing and certification

    Build, test and certify each Intermountain Health document, then go live with monitoring from the first file.

    Plan testing and certification
  • Shipping labels and ASNs

    Labels and ship notices that match Intermountain Health's rules, to help avoid receiving problems and compliance deductions.

    Review shipping compliance

Intermountain Health integration FAQs

Does Intermountain Health use EDI or file exchange with its partners?

Organizations of this type commonly exchange structured files and EDI with suppliers, banks and service providers, but this page does not include Intermountain Health's own requirements.

Which documents are typical for a company like Intermountain Health?

Typical documents or file types are 850, 855, 856, 810, 846, 835, 997. That is general practice for hospital system, not Intermountain Health's published list.

Why does integrated system and plan matter for Intermountain Health integrations?

Operating hospitals, clinics and a health plan means supply documents and claim flows both run through finance. For Intermountain Health, that shapes how documents are built, matched and checked.

How does onboarding with Intermountain Health usually work?

Typically you get the requirements from the trading partner, agree the connection and security steps, map to your systems, test until the partner accepts the documents, then go live with monitoring. Timing depends on Intermountain Health's requirements and your systems.

Does this guide mean Intermountain Health endorses ECOM?

No. This is an independent integration guide. It does not indicate an endorsement, partnership or approval by Intermountain Health.

Sources and accuracy

This guide summarizes publicly available information as of November 2026. Intermountain Health sets its own requirements and can change them at any time; your Intermountain Health implementation guide, supplier portal or account contact is the authoritative source for your program.

  • Intermountain Health: company website Official Intermountain Health source
  • ASC X12: transaction set reference (standards body) Standards reference
  • Intermountain Health: company description Background, not checked against a company source The description of Intermountain Health comes from general public knowledge and was not checked against Intermountain Health's own website for this page.
  • Intermountain Health: no company document read Background, not checked against a company source No Intermountain Health supplier, customer or integration document was read for this page. Everything shown is typical practice for this type of company.

Request Intermountain Health integration assistance

Tell us about your Intermountain Health program, documents and ERP. We will outline the connection, mapping and testing plan.