147 Response to Request for Student Educational Record (Transcript) (003050)

This is the standard X12 003050 spec, with 2 loops and 14 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 (31 KB) Generate classes

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

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

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

ediFabric Native

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

ediFabric Native returns each 147 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 TS147. 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.

147 structure

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

ID	Name	Usage	Max use
ST	Transaction Set Header	Optional	1
BGN	Beginning Segment	Mandatory	1
AAA	Request Validation	Mandatory	1
REF	Reference Numbers	Mandatory	10
PWK	Paperwork	Optional	1
NTE	Note/Special Instruction	Optional	15
Loop N1	Name	Mandatory	2
N1	Name	Mandatory	1
N2	Additional Name Information	Optional	1
N3	Address Information	Optional	1
N4	Geographic Location	Optional	1
PER	Administrative Communications Contact	Optional	1
Loop IN1	Individual Identification	Mandatory	15
IN1	Individual Identification	Mandatory	1
IN2	Individual Name Structure Components	Mandatory	10
SE	Transaction Set Trailer	Optional	1