Glossary · Billing

EDI 837 (electronic claim)

The EDI 837 is the HIPAA-mandated electronic transaction standard for submitting healthcare claims to payers. It replaces paper forms (CMS-1500 for professional claims, UB-04 for institutional claims) with a structured, machine-readable format that payers can validate and adjudicate automatically.

Verified May 8, 2026 · 7 sources ↓

Drawn from CMSSignalediDastifysolutionsAAOSAoassn

Definition

Source · Editorial summary grounded in 7 cited references ↓

EDI 837 is defined under HIPAA Transaction and Code Set Standards (45 CFR Part 162) as the required format for any covered entity submitting claims electronically. The standard is maintained by the Accredited Standards Committee (ASC) X12 and currently operates under version 5010. Three variants exist: 837P (professional services, the version orthopedic practices use most), 837I (institutional/facility), and 837D (dental). Each claim line in an 837P carries the provider NPI, patient demographics, ICD-10-CM diagnosis codes, CPT/HCPCS procedure codes, place-of-service code, date of service, and billed charge.

Before an 837 reaches a payer, it typically passes through a clearinghouse that performs technical validation—checking X12 5010 formatting, required field completeness, code set validity, and payer-specific edits. The payer returns an EDI 999 functional acknowledgment confirming the file was received and syntactically acceptable. A separate EDI 277 claim-status response follows to indicate whether the claim was accepted or rejected on clinical/administrative grounds. When the claim is adjudicated, the payer issues an EDI 835 electronic remittance advice (ERA) that maps payment or denial back to each service line.

For orthopedic practices, every surgical CPT code submitted—whether a total knee arthroplasty, a meniscectomy, or a fracture repair—travels to Medicare, Medicaid, and commercial payers via an 837P. The data elements in that transaction must exactly mirror the operative documentation: matching diagnosis codes that establish medical necessity, procedure codes that reflect what was performed, and modifiers that clarify bilateral procedures, distinct services, or assistant-surgeon roles. Mismatches between the operative note and the 837 are among the most common triggers for payer audit.

Why it matters

Every orthopedic reimbursement event flows through an 837 transaction, so errors at the claim-construction stage have direct financial and compliance consequences. A claim rejected at the clearinghouse (invalid code, missing NPI, wrong place-of-service) never reaches the payer adjudicator and must be corrected and resubmitted, adding days or weeks to accounts-receivable cycles. A claim that clears the clearinghouse but carries a procedure code unsupported by the documented diagnosis will either deny on medical-necessity grounds or trigger a post-payment audit. In orthopedics specifically, bundling edits enforced by NCCI are applied against 837P service lines automatically—submitting a separately payable code that is already bundled into a primary CPT (for example, billing 29881 alongside 29880) will generate a prepayment NCCI edit denial. Getting the 837 right the first time is not an administrative nicety; it is the precondition for being paid on time and avoiding recoupment.

Common mistakes

Where people most often go wrong with this concept.

Source · Editorial brief grounded in cited references ↓

  • Submitting an 837P with a place-of-service code that contradicts where the surgery actually occurred (e.g., POS 11 Office instead of POS 22 Outpatient Hospital), which triggers medical-necessity and fee-schedule mismatches.
  • Omitting or incorrectly sequencing ICD-10-CM diagnosis codes on the claim loop—the primary diagnosis pointer must link to the procedure that requires it, not default to whatever diagnosis is listed first in the EHR problem list.
  • Failing to append required modifiers (e.g., RT/LT for laterality, 50 for bilateral, 80 for assistant surgeon) in the correct modifier position on the 837P service line, causing automatic denial or incorrect payment.
  • Transmitting CPT codes that are bundled under NCCI as separate line items without a valid modifier override, resulting in prepayment denial of the component code.
  • Not reconciling the 837 claim data against the operative report before submission—a mismatch between documented procedure and billed CPT code is a top audit flag.
  • Allowing clearinghouse enrollment (EDI enrollment with the payer) to lapse or submitting to the wrong payer ID, so the 837 is never delivered and the claim ages in accounts receivable without a denial notice.

Related codes

Codes commonly involved when this concept appears in practice.

ICD-10

Frequently asked questions

Source · Generated from the editorial pipeline, verified against 7 cited references ↓

01What is the difference between an 837P and a CMS-1500?
They carry the same claim data, but in different formats. The CMS-1500 is a paper (or scanned) form submitted by mail or fax. The 837P is the HIPAA-required electronic version of that same claim, structured in ASC X12 5010 format so payers can process it automatically without manual data entry. Medicare requires electronic submission for most providers; paper is the exception.
02Why does an orthopedic claim sometimes get rejected at the clearinghouse before it even reaches the payer?
Clearinghouse rejection means the 837 file failed technical or structural validation—common causes include an invalid or missing NPI, an ICD-10 code that is not at the required level of specificity, a CPT code that does not exist in the current code year, or a required data segment left blank. These rejections do not count as payer denials and must be corrected and resubmitted; they do not reset timely-filing clocks with most payers, but they do delay payment.
03How does the 837P connect to the 835 remittance?
After adjudication, the payer generates an EDI 835 electronic remittance advice that references the original 837P claim by a shared claim control number. Each service line payment, adjustment, or denial reason code in the 835 maps back to the corresponding CPT line in the 837. Automated posting in a practice management system uses this linkage to reconcile payments against expected reimbursement and flag underpayments or contractual adjustments that look incorrect.
04Do orthopedic ASC cases use an 837P or an 837I?
It depends on who is billing. The surgeon bills professional services on an 837P regardless of site of care. The ambulatory surgery center bills its facility fee on an 837I, which maps to the UB-04 paper form. Both transactions for the same case will reference the same date of service and patient, but they are separate claims submitted by separate billing entities to potentially different payer IDs.
05What is the EDI 999 and why does it matter?
The EDI 999 is a functional acknowledgment the payer or clearinghouse returns after receiving an 837. An 'accepted' 999 means the file was syntactically valid and entered the payer's system. A 'rejected' 999 means the entire batch was refused due to a structural error—no claims in that file will be adjudicated until the problem is fixed and the file is resubmitted. Monitoring for 999 responses is a basic accounts-receivable control that many smaller orthopedic practices overlook.

Sources & references

Editorial content was developed using the following public sources. Last verified May 8, 2026.

  1. 01
    cms.gov
    https://www.cms.gov/files/document/837p-cms-1500pdf
  2. 02
    signaledi.com
    https://signaledi.com/blog/edi-837-healthcare-claims
  3. 03
    dastifysolutions.com
    https://www.dastifysolutions.com/blog/complete-guide-to-edi-837-healthcare-claims/
  4. 04
    aaos.org
    https://www.aaos.org/quality/coding-and-reimbursement/
  5. 05
    aoassn.org
    https://www.aoassn.org/wp-content/uploads/2020/12/CodingTTP.pdf
  6. 0645 CFR Part 162 (HIPAA Transaction and Code Set Standards)
  7. 07ASC X12 5010 Technical Report Type 3 — 837P Implementation Guide

Mira AI Scribe

Mira participates directly in 837P claim construction by validating that each structured data element captured at the point of documentation will map correctly to the outgoing electronic claim. Specifically, Mira checks: (1) that the ICD-10-CM diagnosis codes documented in the operative note are in the correct priority order and linked to the appropriate CPT procedure code line via diagnosis pointer; (2) that the place-of-service code matches the facility context selected during the encounter; (3) that any modifier logic triggered by documentation—bilateral procedures, distinct procedural services, assistant-surgeon presence, or increased procedural complexity—is surfaced for coder review before the claim is finalized; and (4) that CPT combinations flagged by current NCCI PTP edits are identified and a modifier rationale is requested if the services were genuinely distinct. Mira does not autonomously submit 837 transactions; a certified coder or biller reviews and approves all claim data before transmission. When Mira detects a potential bundling conflict or a diagnosis-to-procedure linkage gap, it generates an in-workflow alert so the issue is resolved at documentation time rather than after a clearinghouse rejection or post-payment audit.

See Mira's approach

Related terms

Ready?

Ready to transform your orthopedic practice?

See how orthopedic practices are running documentation, billing, and operations on a single voice-first platform.

Get started for free