An 837 is an X12 healthcare claim sent by a provider to a payer.

What comes after an 837?

A payer or clearinghouse commonly returns 999 and 277 acknowledgements/status updates, followed by 835 remittance after adjudication.

Document guide

EDI 837: 837 healthcare claim guide

The 837 is the core healthcare claim transaction providers send to payers for adjudication.

Validate EDI 837 See Interactive Demo

What the 837 is

An 837 replaces paper claim forms with structured X12 loops for provider, subscriber, payer, service lines, and claim totals.

837P for professional claims
837I for institutional claims
837D for dental claims

Example segments

ST*837*0001*005010X222A1~
BHT*0019*00*CLAIM1042*20260504*1430*CH~
NM1*85*2*SIGNAL CLINIC*****XX*1234567893~
CLM*CLAIM1042*145.00***11:B:1*Y*A*Y*I~

Common errors

Missing or malformed NM1 provider identifiers
CLM amount mismatch
Invalid payer or subscriber loop
Control number mismatch

Activation path for EDI 837

Use this page as the middle of the internal-link path: ICP page to document guide, document guide to partner requirements, partner requirements to comparison/pricing, then demo or trial.

Understand the document and partner requirement
Validate a representative X12 sample
Preview the normalized JSON or QuickBooks-ready mapping
Confirm partner onboarding, testing, and acknowledgement expectations
Start trial and move the workflow into the onboarding wizard

Buyer-intent next steps

Healthcare EDIReturn to the ICP pillar and compare the full workflow.Partner pagesFind retailer, payer, marketplace, or distributor onboarding requirements.Compare vendorsSee why self-serve EDI matters against legacy alternatives.PricingMatch documents/month and partners to a plan before trial.Interactive demoReplay validation, mapping, lifecycle, and acknowledgement paths.Trust centerReview HIPAA posture, PHI boundaries, audit logs, RBAC, and status.

How SignalEDI handles EDI 837

Detects envelope, ST, BHT, NM1, and CLM issues before send.
Simulates 999/277 acknowledgement expectations in the public validator.
Keeps claim lifecycle visible from sample validation through payer status.