276 Health Care Claim Status Request (003070)

This is the standard X12 003070 spec, with 5 loops and 25 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 (58 KB) Generate classes

The ediFabric .NET template, class TS276. It needs the common segments, composites and codes of X12 003070, one download for every transaction in the version. Download C# (1 KB) Common files (238 KB)

The intermediary model ediFabric Native loads with set_map. Download Native (43 KB)

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

ediFabric Native

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

ediFabric Native returns each 276 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 TS276. 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.

276 structure

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

ID	Name	Usage	Max use
ST	Transaction Set Header	Optional	1
BHT	Beginning of Hierarchical Transaction	Mandatory	1
REF	Reference Identification	Optional	10
Loop NM1	Individual or Organizational Name	Optional	>1
NM1	Individual or Organizational Name	Mandatory	1
N2	Additional Name Information	Optional	2
N3	Address Information	Optional	2
N4	Geographic Location	Optional	1
REF	Reference Identification	Optional	2
PER	Administrative Communications Contact	Optional	1
Loop HL	Hierarchical Level	Mandatory	>1
HL	Hierarchical Level	Mandatory	1
SBR	Subscriber Information	Optional	1
PAT	Patient Information	Optional	1
DMG	Demographic Information	Optional	1
Loop NM1	Individual or Organizational Name	Optional	>1
NM1	Individual or Organizational Name	Mandatory	1
N3	Address Information	Optional	2
N4	Geographic Location	Optional	1
PER	Administrative Communications Contact	Optional	1
Loop TRN	Trace	Optional	>1
TRN	Trace	Mandatory	1
REF	Reference Identification	Optional	3
AMT	Monetary Amount	Optional	1
DTP	Date or Time or Period	Optional	2
Loop SVC	Service Information	Optional	>1
SVC	Service Information	Mandatory	1
REF	Reference Identification	Optional	1
DTP	Date or Time or Period	Optional	1
SE	Transaction Set Trailer	Optional	1