X12 transaction guide · Education
EDI 189 Application for Admission to Educational Institutions
The X12 document containing the information, other than official transcripts, that students use to apply for admission to institutions.
- Sent by
- Student or application service
- Received by
- Educational institution
- Standard
- ANSI ASC X12
What is an EDI 189?
The EDI 189 Application for Admission to Educational Institutions is the ANSI X12 transaction set that contains all the information, except official transcripts, that students use to apply for admission to educational institutions. Students may send it directly to the institution or through an application service.
The application carries the student's personal details, academic history, intended program and other answers. The official transcript follows separately, typically as a 130, and the institution combines both in its admissions decision. It reduces duplicate data entry.
How to read this diagram: the top row shows who sends the 189, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 189 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.
When it is used
- Submitting admission applications
- Sending applications through a central application service
- Updating application details
Where it fits in the document flow
Structure
Mandatory segments in the 189 (X12 release 008010)
The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.
- ST
- BGN
- N1
- REF
- IN1
- IN2
- N3
- COM
- EMS
- ATV
- AMT
- SSE
- LQ
- RSD
- N4
- RQS
- SST
- SES
- CRS
- TST
- SBT
- PCL
- DEG
- LX
- MSG
- LT
- SE
Practical example
The 189 in practice
A student completes one online application through a central service and selects four universities. The service sends each university a 189 with the student's details and answers. Each university creates an applicant record and requests the transcript from the student's school with a 146.
Implementation
Implementation considerations for the 189
- Protect applicants' personal data under privacy laws.
- Map application questions to the institution's fields.
- Link applications to transcripts when they arrive.
- Handle updates to submitted applications.
How ECOM helps
Automate the 189 with ECOM
Solution
Enterprise Integration
Any-to-any integration across partners, systems, protocols, security requirements, formats and ERPs, in batch or real time.
Solution
EDI Integration
Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.
Solution
B2B Integration
Connect every customer, supplier, carrier and bank across EDI, API, file and portal channels.
More general questions about EDI are answered in the EDI FAQ.
Related transactions
Related education documents
- 146Request for Student Educational Record (Transcript)
- 130Student Educational Record (Transcript)
- 131Student Educational Record (Transcript) Acknowledgment
- 133Educational Institution Record
- 138Educational Testing and Prospect Request and Report
- 147Response to Request for Student Educational Record (Transcript)
- 188Educational Course Inventory
Need help with the EDI 189?
ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.