271 Eligibility, Coverage or Benefit Information (005010X279A1)

Payers return the 271 in reply to a 270, with the patient's coverage, benefits, copays and deductibles. This is the standard X12 HIPAA 005010 spec, with 16 loops and 69 segment positions, as OpenEDI JSON, an ediFabric C# template and an ediFabric Native model. To change it for a trading partner, customize it in the EDI Spec Builder.

Loading the spec…
The spec as an OpenAPI 3 schema with x-openedi-* extensions, for ediFabric Native, ediFabric Cloud and the EDI Spec Builder. Download OpenEDI (251 KB) Generate classes
The ediFabric .NET template, class TS271. The download includes the common segments, composites and codes it needs. Download C# (92 KB)
The intermediary model ediFabric Native loads with set_map. Download Native (91 KB)

Use the 271 spec in your code

ediFabric .NET

Add the C# template and its common files to your project, or reference the template NuGet package, and read 271 files into TS271 objects. See ediFabric .NET.

ediFabric Native

Map version 005010X279A1 to the Native model with set_map, then parse 271 files to JSON from Python, Java, C or C#. See Convert between EDI and JSON.

OpenEDI

Select Customize in Spec Builder to copy the spec under your own name, change it for your partner, and parse files against it in EdiNation, ediFabric Native or ediFabric Cloud. Read about OpenEDI.

Generate 271 classes in Python, Java, Node.js, Go, Rust or C

ediFabric Native returns each 271 as JSON, with the property names of the OpenEDI schema. To work with that JSON as typed objects, generate classes from the OpenEDI file in your language and deserialize the JSON into TS271. Serialize the objects back to JSON to build EDI with ediFabric Native. The classes keep the loops, segments, lengths and code lists, but not the EDI data formats, so validate files with ediFabric Native. Read more in Generate a class from OpenEDI.

Python: datamodel-code-generator. Node.js: openapi-typescript. Java, Go, Rust and C: OpenAPI Generator.

For a sample file, the same data as JSON, and code to parse, validate and generate the 271, see the 271 transaction guide.

271 structure

Loops and segments of the standard 271, with their usage and maximum repeats.

IDNameUsageMax use
STTransaction Set HeaderOptional1
BHTBeginning Of Hierarchical TransactionMandatory1
Loop 2000AInformation Source LevelMandatory>1
HLInformation Source LevelMandatory1
AAARequest ValidationOptional9
Loop 2100AInformation Source NameMandatory1
NM1Information Source NameMandatory1
PERInformation Source Contact InformationOptional3
AAARequest ValidationOptional9
Loop 2000BInformation Receiver LevelOptional>1
HLInformation Receiver LevelMandatory1
Loop 2100BInformation Receiver NameMandatory1
NM1Information Receiver NameMandatory1
REFInformation Receiver Additional IdentificationOptional9
N3Information Receiver AddressOptional1
N4Information Receiver City State ZIP CodeOptional1
AAAInformation Receiver Request ValidationOptional9
PRVInformation Receiver Provider InformationOptional1
Loop 2000CSubscriber LevelOptional>1
HLSubscriber LevelMandatory1
TRNSubscriber Trace NumberOptional3
Loop 2100CSubscriber NameMandatory1
NM1Subscriber NameMandatory1
REFSubscriber Additional IdentificationOptional9
N3Subscriber AddressOptional1
N4Subscriber City State ZIP CodeOptional1
AAASubscriber Request ValidationOptional9
PRVProvider InformationOptional1
DMGSubscriber Demographic InformationOptional1
INSSubscriber RelationshipOptional1
HISubscriber Health Care Diagnosis CodeOptional1
DTPSubscriber DateOptional9
MPISubscriber Military Personnel InformationOptional1
Loop 2110CSubscriber Eligibilityor Benefit InformationOptional>1
EBSubscriber Eligibilityor Benefit InformationMandatory1
HSDHealth Care Services DeliveryOptional9
REFSubscriber Additional IdentificationOptional9
DTPSubscriber Eligibility Benefit DateOptional20
AAASubscriber Request ValidationOptional9
MSGMessage TextOptional10
Loop 2115CSubscriber Eligibilityor Benefit Additional InformationOptional10
IIISubscriber Eligibilityor Benefit Additional InformationMandatory1
Loop LSHeaderOptional1
LSHeaderMandatory1
Loop 2120CSubscriber Benefit Related Entity NameOptional23
NM1Subscriber Benefit Related Entity NameMandatory1
N3Subscriber Benefit Related Entity AddressOptional1
N4Subscriber Benefit Related Entity City State ZIP CodeOptional1
PERSubscriber Benefit Related Entity Contact InformationOptional3
PRVSubscriber Benefit Related Provider InformationOptional1
LETrailerMandatory1
Loop 2000DDependent LevelOptional>1
HLDependent LevelMandatory1
TRNDependent Trace NumberOptional3
Loop 2100DDependent NameMandatory1
NM1Dependent NameMandatory1
REFDependent Additional IdentificationOptional9
N3Dependent AddressOptional1
N4Dependent City State ZIP CodeOptional1
AAADependent Request ValidationOptional9
PRVProvider InformationOptional1
DMGDependent Demographic InformationOptional1
INSDependent RelationshipOptional1
HIDependent Health Care Diagnosis CodeOptional1
DTPDependent DateOptional9
MPIDependent Military Personnel InformationOptional1
Loop 2110DDependent Eligibilityor Benefit InformationOptional>1
EBDependent Eligibilityor Benefit InformationMandatory1
HSDHealth Care Services DeliveryOptional9
REFDependent Additional IdentificationOptional9
DTPDependent Eligibility Benefit DateOptional20
AAADependent Request ValidationOptional9
MSGMessage TextOptional10
Loop 2115DDependent Eligibilityor Benefit Additional InformationOptional10
IIIDependent Eligibilityor Benefit Additional InformationMandatory1
Loop LSHeaderOptional1
LSHeaderMandatory1
Loop 2120DDependent Benefit Related Entity NameOptional23
NM1Dependent Benefit Related Entity NameMandatory1
N3Dependent Benefit Related Entity AddressOptional1
N4Dependent Benefit Related Entity City State ZIP CodeOptional1
PERDependent Benefit Related Entity Contact InformationOptional3
PRVDependent Benefit Related Provider InformationOptional1
LETrailerMandatory1
SETransaction Set TrailerOptional1