280 Voter Registration Information (005030)

This is the standard X12 005030 spec, with 5 loops and 27 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 (92 KB) Generate classes
The ediFabric .NET template, class TS280. It needs the common segments, composites and codes of X12 005030, one download for every transaction in the version. Download C# (1 KB) Common files (268 KB)
The intermediary model ediFabric Native loads with set_map. Download Native (67 KB)

Use the 280 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 280 files into TS280 objects. See ediFabric .NET.

ediFabric Native

Map version 005030 to the Native model with set_map, then parse 280 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 280 classes in Python, Java, Node.js, Go, Rust or C

ediFabric Native returns each 280 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 TS280. 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.

280 structure

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

IDNameUsageMax use
STTransaction Set HeaderOptional1
BGNBeginning SegmentMandatory1
Loop N1Party IdentificationOptional>1
N1Party IdentificationMandatory1
N2Additional Name InformationOptional2
N3Party LocationOptional2
N4Geographic LocationOptional1
REFReference InformationOptional>1
PERAdministrative Communications ContactOptional>1
DTMDate/Time ReferenceOptional>1
Loop PWKPaperworkOptional>1
PWKPaperworkMandatory1
REFReference InformationOptional>1
CRCConditions IndicatorOptional>1
MEAMeasurementsOptional>1
DTMDate/Time ReferenceOptional>1
PERAdministrative Communications ContactOptional>1
Loop IN1Individual IdentificationOptional>1
IN1Individual IdentificationMandatory1
IN2Individual Name Structure ComponentsOptional>1
ICHIndividual CharacteristicsOptional>1
DTMDate/Time ReferenceOptional>1
Loop NX1Property or Entity IdentificationOptional>1
NX1Property or Entity IdentificationMandatory1
NX2Location ID ComponentOptional>1
N4Geographic LocationOptional>1
REFReference InformationOptional>1
DTMDate/Time ReferenceOptional>1
Loop EFIElectronic Format IdentificationOptional>1
EFIElectronic Format IdentificationMandatory1
BINBinary Data SegmentOptional1
SETransaction Set TrailerOptional1