HIPAA 5010 Transaction Sets: Complete List and Reference

June 11, 2026 · 10 min read

HIPAA 5010 defines the electronic transaction standards for healthcare in the United States. Understanding which transaction sets are required, their implementation guide versions, and their use cases is foundational for any healthcare EDI implementation team.

Overview

The HIPAA 5010 rule (45 CFR Part 162) mandated adoption of X12 version 005010 for all HIPAA standard transactions effective January 1, 2012. Every covered entity — health plans, clearinghouses, and providers with electronic billing — must use these transaction sets and implementation guide versions.

Key Concepts and Structure

Each HIPAA transaction has a specific implementation guide version that defines the exact field requirements, code sets, and business rules. These guides are published by the Washington Publishing Company (WPC) and referenced in the HIPAA regulations. The implementation guide version appears in the GS08 segment of every transaction.

HIPAA 5010 Transaction Set Reference

837 — Claims

837P (005010X222A1) professional, 837I (005010X223A2) institutional, 837D (005010X224A3) dental claim submission.

835 — Payment

835 (005010X221A1) health care claim payment and remittance advice from payer to provider.

270/271 — Eligibility

270 (005010X279A1) eligibility inquiry, 271 (005010X279A1) eligibility response. Real-time and batch.

276/277/278 — Status/Auth

276 claim status request, 277 claim status response (005010X212), 278 prior authorization (005010X217).

Testing Strategy

Testing each required transaction set before go-live is mandatory. The most common failure pattern is implementing only the happy-path scenarios for claim submission while ignoring the supporting transactions that complete the revenue cycle.

Test Scenario Checklist

✓837P/I/D claim submission and 999 functional acknowledgment receipt

✓835 remittance receipt and reconciliation against submitted claims

✓270/271 real-time eligibility verification for patient registration workflow

✓276/277 claim status inquiry and response processing

✓278 prior authorization request and response with auth number flow to 837

✓834 enrollment file for member eligibility maintenance

Common Failure Patterns

These are the transaction-level failures most commonly found after go-live:

Wrong implementation guide version in GS08

Using 005010X222 instead of 005010X222A1 for 837P, or the 4010 guide version in a 5010-required context, causes 999 rejection with error TR3.

Supporting transactions not tested

Teams test 837 submission but skip 270/271, 276/277, and 278. These gaps surface during the first production week when patients check eligibility or providers check claim status.

Mixed transaction types in one functional group

837P and 837I cannot be in the same GS/GE functional group. Each transaction type requires its own group with the correct GS01 functional identifier code.

Testing Without PHI

Testing all HIPAA transaction sets requires realistic member data, provider information, and payer configurations. Synthibase generates the full transaction family — 837, 835, 834, 270, 277, 278 — from a single synthetic patient registry, giving you coherent end-to-end testing without PHI.

→

Why Healthcare IT Go-Lives Fail

The most common go-live failure patterns and how to avoid them

Generate synthetic EDI test data in minutes

Synthibase generates valid X12 EDI transactions from a synthetic patient registry. Zero PHI. Ready for go-live testing.

Start free trial →