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).
- Those are illustrations rather than the rule set: the governing detail sits in the transaction's Implementation Guide (TR3) and in your clearinghouse's own edits.
- How the 835 pairs with EFT enrollment determines whether the remittance and the money arrive together at all.
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's Transactions and Code Sets rules at 45 CFR part 162, the X12 transactions carry the administrative traffic between providers and health plans, and part 162 names each adopted transaction together with the exact implementation guide version it adopts: 837P (professional claim), 837I (institutional), 837D (dental), 835 (claim payment/advice), 270/271 (eligibility inquiry and response), 276/277 (claim status), 278 (referral certification and authorization), 834 (enrollment) and 820 (premium payment). For X12, the adopted version is still 5010: 45 CFR 162.1102 adopts the 5010 claim implementation guides for the period from 1 January 2012 through 14 August 2027, then re-adopts the same 5010 837 guides for 14 August 2027 through 14 April 2028 and again for the period on and after 14 April 2028 — what those later paragraphs change is retail pharmacy, from NCPDP D.0 to F6, not the 837 (read 17 September 2026). HHS has since added a subpart for claims attachments, adopting X12 275 and 277 attachment guides alongside HL7 C-CDA document specifications for the period on and after 26 May 2028 (45 CFR 162.2002). Not everything a clearinghouse sends you is on that list — the 999 and 277CA acknowledgments are defined in X12 implementation guides and required by trading partners including Medicare, but they are not themselves HIPAA-adopted transactions. 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 and HL7 are not rival answers to the same question — X12 carries administrative transactions while HL7 v2 and FHIR carry clinical data — but the line between them is no longer clean, and treating it as rigid will mislead you. HHS's claims-attachments standard puts HL7 C-CDA clinical documents inside an X12 275 envelope for the period on and after 26 May 2028. And while the X12 278 remains the adopted authorization transaction at 45 CFR 162.1302, CMS's National Standards Group announced in February 2024 that it would not take HIPAA Administrative Simplification enforcement action against covered entities that choose not to use the 278 as part of an all-FHIR prior-authorization process under the CMS Interoperability and Prior Authorization final rule. Expect both families in production side by side for years.
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). Those are illustrations rather than the rule set: the governing detail sits in the transaction's Implementation Guide (TR3) and in your clearinghouse's own edits. To read an 835 remittance: (1) start at the BPR segment, which carries the payment amount, method and effective date for the transfer as a whole rather than any per-claim detail; (2) locate the CLP segment for the claim — CLP03 is the billed amount, CLP04 the paid amount; (3) read each CAS segment for the group code (CO, PR, OA, PI) and the CARC explaining every dollar adjusted; (4) check the claim-level MOA or MIA segment and the service-line LQ segment for the RARCs that explain why, then post line by line against the matching 837 service lines. The number that ties the file to the bank is neither the BPR amount nor the claim total: it is the TRN reassociation trace number, which 45 CFR 162.1602 adopts for the addenda record of the CCD+ ACH payment so the deposit and the remittance can be matched. How the 835 pairs with EFT enrollment determines whether the remittance and the money arrive together at all.
X12 (HIPAA EDI): Frequently Asked Questions
Common questions about X12 (HIPAA EDI) in medical billing.
Which X12 transactions does HIPAA name?
The ones adopted in 45 CFR part 162: 837P (professional claim), 837I (institutional claim), 837D (dental claim), 835 (claim payment/remittance advice), 270/271 (eligibility inquiry and response), 276/277 (claim status inquiry and response), 278 (referral certification and authorization), 834 (enrollment) and 820 (premium payment). Part 162 also names a coordination of benefits transaction, NCPDP standards for retail pharmacy, and — for the period on and after 26 May 2028 — a claims-attachments transaction built on X12 275 and 277 attachment guides plus HL7 C-CDA documents. The 999 and 277CA acknowledgments are not on that list: they are defined in X12 implementation guides and required by trading partners, not adopted by rule.
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. 45 CFR 162.1102 adopts the 5010 claim implementation guides for the period from 1 January 2012 through 14 August 2027, and re-adopts the same 5010 837 guides for 14 August 2027 through 14 April 2028 and for the period on and after 14 April 2028. What changes on those dates is retail pharmacy — NCPDP D.0 gives way to F6 — not the 837. X12 has published later versions of the standard, but a later version is not the HIPAA standard until HHS adopts it by rule.
Is X12 the same thing as HL7 or FHIR?
No — but the split is not as clean as “X12 for billing, FHIR for clinical”. X12 carries administrative transactions and HL7 v2 and FHIR carry clinical data, yet HHS's claims-attachments standard sends HL7 C-CDA documents inside an X12 275, and CMS's National Standards Group said in February 2024 that it would not take HIPAA Administrative Simplification enforcement action against covered entities that skip the X12 278 as part of an all-FHIR prior-authorization process under the CMS Interoperability and Prior Authorization final rule. Expect both in production together.
How do you read an 835 remittance?
Start at the BPR segment for the transfer as a whole — the payment amount, the method and the effective date. Then, per claim, read the CLP segment (CLP03 billed, CLP04 paid), each CAS segment for the group code (CO, PR, OA, PI) and the CARC behind every dollar adjusted, and the claim-level MOA or MIA segment plus the service-line LQ segment for the RARCs that explain why. Post line by line against the matching 837 service lines. To tie the file to the deposit, use the TRN reassociation trace number rather than the BPR amount — the plan carries that number into the addenda record of the CCD+ ACH payment.
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 definitionERA (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 definitionCMS-1500 form
The CMS-1500 is the paper claim form Medicare prescribes for non-institutional providers (physicians, NPPs, suppliers); its electronic equivalent is the 837P (Professional) HIPAA EDI transaction, and many other payers accept the same form and transaction on their own terms.
Read definitionUB-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 definitionWhere 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.
- No contract
- No setup fees
- Reply within 1 business day