EDI in Healthcare: HIPAA 45 CFR Part 162 Standards, ASC X12N 5010 Transactions (837P, 837I, 835, 270/271, 278, 834), and NCPDP SCRIPT

Health informatics engineers, healthcare revenue cycle management (RCM) architects, and health services researchers working with administrative claims databases need a precise reference for EDI in healthcare. Under the Administrative Simplification provisions of the Health Insurance Portability and Accountability Act (HIPAA) codified at 45 CFR Part 162, covered entities—health plans, medical claims clearinghouses, and healthcare providers transmitting financial or administrative transactions electronically—are legally required to exchange data using standardized ASC X12N Version 5010 electronic data interchange (EDI) formats for medical claims and NCPDP standards for retail pharmacy prescribing and claims.

What Are the Core X12 EDI Transactions in Healthcare (45 CFR Part 162)?

Developed by the Accredited Standards Committee (ASC) X12 Insurance Subcommittee (X12N) and adopted by the U.S. Department of Health and Human Services (HHS) via Technical Report Type 3 (TR3) implementation guides, HIPAA EDI transactions standardize every step of the payer–provider administrative lifecycle:

Transaction Code	ASC X12N 5010 TR3 Implementation ID	Transaction Name & Direction	Core Data Elements & Research / Operational Use
EDI 270 / 271	005010X279A1 (45 CFR § 162.1202)	Eligibility, Coverage, or Benefit Inquiry (270) & Response (271) (Provider ↔ Payer)	Verifies active subscriber coverage, plan effective dates, service-type benefit status, remaining deductible, copayment, and coinsurance amounts prior to care.
EDI 278	005010X217 (45 CFR § 162.1302)	Health Care Services Review — Request & Response (Provider ↔ Payer)	Transmits electronic prior authorization requests, specialist referrals, inpatient admission certifications, and payer certification/denial decision numbers.
EDI 837P	005010X222A1 (45 CFR § 162.1102)	Health Care Claim: Professional (Provider → Clearinghouse → Payer)	Electronic equivalent of the CMS-1500 paper form used by physicians, ambulatory clinics, and DMEPOS suppliers; carries ICD-10-CM diagnoses, CPT/HCPCS procedure codes, modifiers, and rendering/billing NPIs.
EDI 837I	005010X223A2 (45 CFR § 162.1102)	Health Care Claim: Institutional (Facility → Clearinghouse → Payer)	Electronic equivalent of the UB-04 (CMS-1450) form used by hospitals, skilled nursing facilities, and outpatient hospital departments; carries revenue codes, condition codes, ICD-10-PCS inpatient procedures, and DRG/APC grouper inputs.
EDI 837D	005010X224A2 (45 CFR § 162.1102)	Health Care Claim: Dental (Provider → Payer)	Electronic equivalent of the ADA Dental Claim Form carrying CDT procedure codes, tooth numbers, and oral cavity surface designations.
EDI 276 / 277	005010X212 (45 CFR § 162.1402)	Health Care Claim Status Request (276) & Response (277) (Provider ↔ Payer)	Queries and returns the processing status (accepted, pended, adjudicated, or rejected for front-end edits via 277CA Claim Acknowledgment) of a previously submitted 837 claim.
EDI 835	005010X221A1 (45 CFR § 162.1602)	Health Care Claim Payment / Advice (ERA) (Payer → Provider)	Delivers the Electronic Remittance Advice (ERA / EDI 835) detailing line-item allowed amounts, paid amounts, patient responsibility, Claim Adjustment Group Codes (CO, PR, OA, PI), CARCs/RARCs, and EFT trace numbers.
EDI 834	005010X220A1 (45 CFR § 162.1502)	Benefit Enrollment and Maintenance (Sponsor/Employer → Health Plan)	Transmits member enrollment additions, terminations, demographic changes, and plan tier selections from employer sponsors or state/federal exchanges to health plans.
EDI 820	005010X218 (45 CFR § 162.1702)	Payroll Deducted and Other Group Premium Payment (Sponsor → Health Plan)	Accompanies premium payments from employers or government sponsors to reconcile member-level premium remittances.

What Is the Difference Between an EDI 837 Claim and an 835 ERA?

In observational health services research (such as building longitudinal cohorts from CMS Research Identifiable Files [RIF] or commercial claims databases) and hospital billing operations, researchers must distinguish between the outbound claim (X12 837) and the inbound remittance (X12 835):

• Direction and Legal Function: An EDI 837 (837P for professional services or 837I for institutional hospital facilities) is the request for payment transmitted from the healthcare provider to the payer. It reflects billed charges and the clinical diagnosis/procedure codes attested by the provider at the time of billing. By contrast, an EDI 835 is the adjudication and payment explanation returned by the payer after applying benefit rules, fee schedules, bundling edits (NCCI), and medical necessity policies.
• Envelope and Hierarchical Loop Structure: Every X12 5010 file is wrapped in three nested control envelopes—the Interchange Control Header/Trailer (ISA / IEA), Functional Group Header/Trailer (GS / GE), and Transaction Set Header/Trailer (ST / SE)—with segments delimited by tildes (~) and elements delimited by asterisks (*). Inside an 837P/837I, hierarchical loops (HL) nest Billing Provider (2000A), Subscriber (2000B), Patient (2000C), Claim Information (2300, containing the CLM segment and HI ICD-10 diagnosis segments), and Service Lines (2400, containing SV1 or SV2 procedure lines). Inside an 835 ERA, Loop 2100 (CLP Claim Payment Information) and Loop 2110 (SVC Service Payment Information) return the final adjudicated allowed amount, payer payment, patient deductible/coinsurance, and Claim Adjustment Segment (CAS) reason codes, alongside Loop 1000/TRN reassociation trace numbers that link the 835 to the Automated Clearing House (ACH) Electronic Funds Transfer (EFT).
• Clinical Trial Billing Significance: In qualifying clinical trials (Medicare NCD 310.1), the outbound 837P/837I carries clinical trial modifiers (Q0 for investigational clinical services, Q1 for routine clinical services), ICD-10-CM diagnosis code Z00.6, and the 8-digit ClinicalTrials.gov National Clinical Trial (NCT) identifier in Loop 2300 REF*P4, while the inbound 835 verifies whether the MAC paid routine care costs or denied a sponsor-paid item.

How Does the NCPDP SCRIPT Standard Govern Electronic Prescribing and Pharmacy EDI?

Whereas physician and hospital medical claims use ASC X12N 5010 standards, outpatient retail pharmacy transactions are governed by the National Council for Prescription Drug Programs (NCPDP) under two separate federal standards:

1. NCPDP Telecommunication Standard (45 CFR § 162.1102): Used for real-time point-of-sale retail pharmacy claim submission, eligibility verification, and coordination of benefits between retail pharmacies and Pharmacy Benefit Managers (PBMs). Unlike batch X12 medical claims that adjudicate over days, NCPDP Telecommunication transactions (Version D.0, transitioning to Version F6 under HHS rulemaking) adjudicate synchronously in seconds while the patient is at the pharmacy counter using National Drug Codes (NDCs).
2. NCPDP SCRIPT Standard (42 CFR § 423.160): Governed under Medicare Part D electronic prescribing (e-prescribing) regulations, the NCPDP SCRIPT standard (XML-based Version 2017071, with CMS finalizing a transition to Version 2023011) regulates clinical prescription transmission between a prescriber’s EHR and a retail or mail-order pharmacy. Core NCPDP SCRIPT message types include:
   • NewRx: Transmits a new electronic prescription (carrying RxNorm drug concepts, NDCs, SIG dosing instructions, quantity, days’ supply, and diagnosis codes).
   • RxRenewalRequest / RxRenewalResponse and RxChangeRequest / RxChangeResponse: Bi-directional electronic workflows for refill renewals, therapeutic substitutions, or prior authorization initiation.
   • CancelRx / CancelRxResponse: Electronically cancels an active prescription at the pharmacy when a clinician discontinues a medication in the EHR, preventing adverse drug events.
   • RxFill: Notifies the prescribing EHR whether the patient picked up or abandoned the dispensed medication (medication adherence tracking).
   • Electronic Prescribing for Controlled Substances (EPCS): Combined with Drug Enforcement Administration (DEA) cryptographic two-factor authentication and digital signature rules under 21 CFR Part 1311.

How X12 EDI Intersects with HL7 FHIR R4 (CMS-0057-F and Da Vinci Implementation Guides)

Because legacy X12 5010 EDI transactions (such as the 278 prior authorization transaction) cannot easily embed rich clinical chart notes or laboratory trends without separate attachment standards, federal interoperability policy—specifically the CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F)—bridges X12 EDI with HL7 FHIR R4 via the HL7 Da Vinci Project Implementation Guides: Coverage Requirements Discovery (CRD), Documentation Templates and Rules (DTR), and Prior Authorization Support (PAS) (which translates FHIR Claim / ClaimResponse bundles into HIPAA-compliant X12 278 transactions behind the scenes) alongside the CARIN Blue Button (Consumer-Directed Payer Data Exchange) profile that maps adjudicated 837/835 claims into FHIR ExplanationOfBenefit resources.