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
- 837 — the healthcare claim. Professional (837P), institutional (837I), and dental (837D) variants carry the claim from provider to payer.
- 835 — the remittance advice. The payer’s answer to an 837: what was paid, adjusted, or denied, and why.
- 834 — benefit enrollment and maintenance. How a plan sponsor tells the payer who is enrolled.
- 270 / 271 — eligibility inquiry and response. “Is this member covered, and for what?”
- 276 / 277 — claim status inquiry and response. “Where is my claim?”
- 278 — services review: referral and prior authorization request and response.
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:
- Legacy systems that emit 837s with inconsistent loops and segments across lines of business.
- 270/271 eligibility responses that return coverage yes/no but omit the patient financial responsibility the operating rules require.
- No automated handling of 999/277CA rejections, so errors pile up in a queue nobody owns.
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.