837 (electronic claim transaction)
The 837 is the standard electronic transaction that carries a claim to a payer — the HIPAA-mandated format behind nearly every claim submitted today.
Updated
The 837 is the X12 transaction set that carries healthcare claim data from a provider to a payer. It is the electronic claim: when a practice submits a claim, an 837 is what physically moves, whether it goes direct to the payer or through a clearinghouse.
It comes in variants for different kinds of billing — 837P for professional services, 837I for institutional, 837D for dental. Two different rules put it almost everywhere, and they are worth keeping apart: HIPAA does not require a claim to be electronic — it requires that a claim sent electronically by a covered entity use the adopted standard format. What requires most providers to submit Medicare claims electronically at all is the Administrative Simplification Compliance Act (ASCA), which has limited exceptions. HIPAA standardized the shape; ASCA is why so few paper claims remain.
In practice
Its companions define the round trip. The 837 goes out; a 999 acknowledges whether the transmission was structurally accepted; a claim acknowledgment such as the 277CA reports whether the payer accepted the claims inside it; and an 835 returns the payment decision. Exactly which acknowledgments a given payer or clearinghouse returns varies, so the round trip is worth confirming per channel rather than assumed. A claim that seems to vanish has usually stopped at one of them, and the report that would have said so was not read.
The transaction is structured, not a document: it carries the same information a paper claim would, in segments and loops rather than boxes. That is why a rejection can name a field a biller has never seen on a form.
Commonly confused with
- 835: The 837 carries the claim to the payer; the 835 carries the payment decision back. Different transactions, opposite directions.
- CMS-1500 / UB-04: Those are paper claim forms. The 837 is the electronic transaction that carries the same data — and is what is actually sent in nearly every case.