Home / Insights / The X12 EDI Transaction Set, Explained: 837, 835, 834, 270/271, 276/277, 278
November 16, 2026

The X12 EDI Transaction Set, Explained: 837, 835, 834, 270/271, 276/277, 278

A plain-English guide to the X12 EDI transactions health plans and providers exchange — what each one does, the acknowledgements that keep it from failing silently, and how it connects to your FHIR work.

Every payer conversation about interoperability eventually hits the same wall: the X12 EDI transaction set. These numbered formats — 837, 835, 834, 270/271, 276/277, 278 — are the language health plans and providers have exchanged for decades, and they are not going away just because FHIR arrived. Here is what each one does, in plain English, and where they trip plans up.

The core transactions, decoded

The acknowledgements nobody talks about

The transactions above get the attention, but the acknowledgements are where real-world EDI breaks or holds together. A TA1 confirms the interchange envelope was readable. A 999 reports whether the transaction set was syntactically valid. A 277CA (claim acknowledgement) tells the submitter whether a claim was accepted into the adjudication system at all. Skip these and claims fail silently — the single most common cause of “we never got it” disputes.

Where plans get stuck

The format is standardized; the data behind it rarely is. The recurring problems we see at regional plans:

How X12 connects to your FHIR work

CMS-0057-F doesn’t replace X12 — it layers FHIR APIs on top of the same underlying data. The 278 prior-auth transaction maps conceptually to the FHIR Prior Authorization API (PAS), and the claims and encounter data in your 837/835 history is exactly what feeds the Patient Access and Provider Access APIs. Getting the X12 layer clean is a prerequisite, not a side quest — which is why we treat mapping claims and X12 data to FHIR as the real work behind interoperability.

EIXSYS runs the full X12 set and is CAQH CORE certified for EDI connectivity. If you’re weighing EDI modernization alongside the 2027 deadline, a readiness assessment maps both in one pass.

← All insights

Get started

Have a similar challenge?