OSI/MHS Gateway Programmatic Interface (GPI) Programming Guide

EDI Concepts
OSI/MHS Gateway Programmatic Interface (GPI) Programming Guide—424822-001
D-4
EDI Notifications
and therefore cannot encode EDI interchanges in the form of EDIMs. These
components might, for instance, encode the interchange as undefined content of an
X.400 message (“the P0 method”). Alternately, they might encode the interchange as
the body part of an interpersonal message (IPM), extracting information from the
interchange to put into the IPM header (“the P2 method”).
Because the GPI supports CCITT Recommendation X.435 explicitly, you can use it to
develop gateway EDI applications that fully utilize X.435 features. For example:
•
Well-defined, universal format for encoding interchanges into X.400 messages
•
Efficient means to forward interchanges based on concept of EDI responsibility
•
Efficient means of notification of nondelivered or forwarded interchanges
•
Efficient authorization (security) checking of EDI messages and notifications
•
Mechanism to handle future EDI protocol changes (through extensions)
EDI Notifications
In addition to messages (EDIMs), the X.435 recommendation defines EDI notifications
(EDINs). An EDIN is a structure that indicates the disposition of a received EDIM. An
EDIN can be requested by the originator of an EDIM when the EDIM is sent. The
EDIN is generated by the EDI-UA, EDI-MS, or EDI-UA associated with the recipient.
Three possible conditions can be requested and reported on: forwarded notification
(FN), negative notification (NN), and positive notification (PN).
Figure D-3. Relationship Between an EDIM and an X.400 Message
*
*
907CDT .CDD
Heading
Primary Body Part
Add'l Body Part n
Add'l Body Part n+1
EDIM (EDI-C-EDIM)
MH-C-CONTENT
P1 Envelope