What Is X12 (HIPAA EDI)?
ASC X12 is the standards body whose X12N subcommittee develops the HIPAA-named electronic data interchange transactions for healthcare administrative data: 837 (claims), 835 (remittance), 270/271 (eligibility), 276/277 (claim status), 278 (prior auth), and 834 (enrollment).
- Billing teams troubleshooting 999 or 277CA rejections need to read X12 segments.
- Common rejection causes: missing required loops (e.g., subscriber name not in 2010BA), invalid code values (e.g., expired CPT), and segment-level data type errors (e.g., DOB not in CCYYMMDD format).
- Reading the 835 is only half the gain.
- How the 835 pairs with EFT enrollment determines whether the remittance and the money arrive together and whether the TRN reassociation number ties them cleanly.
X12 (HIPAA EDI)
Also known as: ASC X12; HIPAA EDI; X12N; EDI Standards
ASC X12 is the standards body whose X12N subcommittee develops the HIPAA-named electronic data interchange transactions for healthcare administrative data: 837 (claims), 835 (remittance), 270/271 (eligibility), 276/277 (claim status), 278 (prior auth), and 834 (enrollment).
Definition
Named under HIPAA Transactions and Code Sets (45 CFR Part 162), the X12 transactions form the backbone of healthcare administrative interoperability. The current production version is 5010 (mandated since 2012). Transactions: 837P (Professional Claim), 837I (Institutional Claim), 837D (Dental Claim), 835 (Claim Payment/Remittance Advice), 270 (Eligibility Inquiry), 271 (Eligibility Response), 276 (Claim Status Inquiry), 277 (Claim Status Response), 278 (Authorization), 834 (Plan Enrollment), 820 (Premium Payment), and 999 (Functional Acknowledgment). Each transaction has a strict loop-segment-element structure governed by an Implementation Guide (TR3).
Example
An 837P claim file uses ISA/GS envelopes, the ST*837 transaction set header, NM1 segments for patient/provider/payer entities, CLM segments for the claim, HI segments for diagnoses, and SV1 segments for service lines. Each element is positionally placed and validated against the X12 5010 Professional Implementation Guide.
Common Misconceptions
X12 is not the same as HL7 — X12 covers administrative transactions (claims, eligibility, payment), while HL7 v2/v3/FHIR covers clinical data exchange (lab results, ADT, clinical notes). Modern healthcare IT uses both: X12 for billing, FHIR for clinical interoperability.
Practical Application
Billing teams troubleshooting 999 or 277CA rejections need to read X12 segments. Common rejection causes: missing required loops (e.g., subscriber name not in 2010BA), invalid code values (e.g., expired CPT), and segment-level data type errors (e.g., DOB not in CCYYMMDD format). To read an 835 remittance in three steps: (1) locate the CLP segment for the claim — CLP03 is the billed amount, CLP04 the paid amount; (2) read each CAS segment for the group code (CO, PR, OA, PI) and the CARC explaining every dollar adjusted; (3) check the MOA/MIA and LQ segments for RARCs that explain why, then post line-by-line against the matching 837 service lines. Reading the 835 is only half the gain. How the 835 pairs with EFT enrollment determines whether the remittance and the money arrive together and whether the TRN reassociation number ties them cleanly.
X12 (HIPAA EDI): Frequently Asked Questions
Common questions about X12 (HIPAA EDI) in medical billing.
Which X12 transactions does HIPAA name?
The HIPAA-named healthcare transactions are 837P (professional claim), 837I (institutional claim), 837D (dental claim), 835 (claim payment/remittance advice), 270 (eligibility inquiry), 271 (eligibility response), 276 (claim status inquiry), 277 (claim status response), 278 (authorization), 834 (plan enrollment), 820 (premium payment) and 999 (functional acknowledgment).
What is the difference between the 837P and the 837I?
Both are X12 claim transactions, but the 837P carries the professional claim — the electronic equivalent of the CMS-1500 — and the 837I carries the institutional claim, the electronic equivalent of the UB-04. Each has its own loop-segment-element structure governed by an Implementation Guide (TR3).
Which X12 version is currently in production?
Version 5010 is the current production version and has been mandated since 2012. The transactions are named under HIPAA Transactions and Code Sets at 45 CFR Part 162.
Is X12 the same thing as HL7 or FHIR?
No. X12 covers administrative transactions — claims, eligibility, claim status and payment. HL7 v2/v3 and FHIR cover clinical data exchange such as lab results, ADT messages and clinical notes. Modern healthcare IT uses both: X12 for billing, FHIR for clinical interoperability.
How do you read an 835 remittance?
In three steps. First, locate the CLP segment for the claim — CLP03 is the billed amount and CLP04 the paid amount. Second, read each CAS segment for the group code (CO, PR, OA, PI) and the CARC explaining every dollar adjusted. Third, check the MOA/MIA and LQ segments for the RARCs that explain why, then post line by line against the matching 837 service lines.
Why does a claim reject with a 999 or a 277CA?
Because the file failed structural or content validation before adjudication. The common causes are missing required loops — for example a subscriber name absent from loop 2010BA — invalid code values such as an expired CPT, and segment-level data type errors such as a date of birth not formatted as CCYYMMDD.
Related Terms
Clearinghouse
A clearinghouse is a HIPAA-defined entity that processes health information from one format into a standard electronic format and transmits 837 claims, 835 remittances, 270/271 eligibility, and 276/277 claim status transactions between providers and payers.
Read definition arrow_forwardERA (Electronic Remittance Advice / 835)
The ERA (X12 835 transaction) is the HIPAA-standard electronic file payers send to providers detailing claim adjudication results — payments, adjustments, denials with CARC/RARC codes — typically paired with EFT funds transfer.
Read definition arrow_forwardCMS-1500 form
The CMS-1500 is the standard paper claim form used by non-institutional providers (physicians, NPPs, suppliers) to bill Medicare and most commercial payers; its electronic equivalent is the 837P (Professional) HIPAA EDI transaction.
Read definition arrow_forwardUB-04 form
The UB-04 (also known as CMS-1450) is the standard paper claim form used by institutional providers (hospitals, SNFs, home health, hospice) to bill Medicare and other payers; its electronic equivalent is the 837I (Institutional) HIPAA EDI transaction.
Read definition arrow_forwardWhere This Applies on MedPrecision
Need help with billing?
If this term is showing up in your denials, EOBs, or A/R aging, we can help. Get a free billing audit and we will trace the issue to its root cause.
- check_circleNo contract
- check_circleNo setup fees
- check_circleReply within 1 business day