Get the sample weekly report

Glossary

X12

Short answer

X12 is the standards organization, chartered by the American National Standards Institute, whose electronic data interchange formats carry US health care claims, remittances, eligibility checks and claim status, in the version 5010 implementation guides adopted under HIPAA.

Browse more terms in the medical billing glossary.

Last reviewed by the Remitwright billing team. Editorial policy

Also written asASC X12X12 5010

X12 has been chartered by the American National Standards Institute for more than 40 years and maintains over 320 transaction standards for industries from insurance and finance to transportation and supply chain. Health care work sits with its insurance subcommittee, X12N1. HHS adopted specific X12 transactions under HIPAA, so payers and providers who trade them electronically use one structure: the 837 for professional, institutional and dental claims, the 835 for payment and remittance, the 270/271 for eligibility and the 276/277 for claim status2.

The version in force is 5010. Each transaction has a Technical Report Type 3, the implementation guide that sets which loops, segments and codes it must contain, and Medicare’s EDI manual lists the current ones, such as 005010X222A1 for the professional claim and 005010X221A1 for the 835. Translators check every inbound file against those guides and can reject a whole transaction set over a syntax error2. The guides also supply the vocabulary of every rejection report: on the 837P, loop 2300 holds the claim-level data, and its HI segment carries the diagnosis codes3.

The mistake is treating an X12 error as a payer decision. A file rejected for its structure never reached adjudication, so there is no denial to appeal and nothing will show up on the 835. Fix the data at its source in the practice system, resend the file, and read the acknowledgments the same day so the next batch does not repeat the error.

Example

X12 in practice

A clearinghouse report flags an error in loop 2300, segment HI, on one claim. Because those names come from the X12 837P implementation guide, the biller knows to look at the claim's diagnosis codes rather than the patient or provider data. Hypothetical example.

Next step

X12 is part of claim submission, one of the services a dedicated biller runs for you.

See claim submission

Next step

Talk to a biller about this.

Three quick questions, no patient data. A billing specialist reads every request and replies in writing.

  • Three questions, about two minutes
  • No patient data, no software to buy
  • A written reply from a biller, not a sales deck

What happens next

  1. You answer three questions

  2. A billing specialist reads them

  3. A written reply by email

Prefer email? sales@remitwright.com

Get a billing review

See where claims are getting stuck. No patient data needed.

Step 1 of 3

What do you bill for?

A little about your volume
How many providers? (Medical practice)

Trips per month? (NEMT)

Active clients? (Home care / home health)

Orders per month? (DME)

How many clinicians? (Behavioral health / therapy)

Claims per month, roughly? (Something else)

What's the biggest problem right now?

Where should we send the review?

Add details (optional)

We work inside your system; this tells us which login to ask for.

Please don't include patient information in this form.

  • No patient data requested
  • No obligation
  • Reply in writing
Get a billing review
Billing review

Get a billing review

See where claims are getting stuck. No patient data needed.

Step 1 of 3

What do you bill for?

A little about your volume
How many providers? (Medical practice)

Trips per month? (NEMT)

Active clients? (Home care / home health)

Orders per month? (DME)

How many clinicians? (Behavioral health / therapy)

Claims per month, roughly? (Something else)

What's the biggest problem right now?

Where should we send the review?

Add details (optional)

We work inside your system; this tells us which login to ask for.

Please don't include patient information in this form.

  • No patient data requested
  • No obligation
  • Reply in writing

BAA signed before any access, a user you create, MFA on. Patient data stays in your systems. How access works