The EDI file received from each partner is processed and a separate DX event is created for interchange (ISA), functional group\s (GS), and the transaction\s (ST). The events are created hierarchically to reflect the hierarchical structure of the EDI file. A root event will be created for an ISA, a child event will be created for every GS within the ISA, and a child event will be created for every ST in a GS.

Every DX event type of a processed EDI file reflects its envelope level (ISA\GS\ST), its EDI-X12 Document type (e.g. 810,820,850 etc.), and direction (inbound or outbound).The event life cycle is reflected by using DX event statuses which signify success or failure of processing, or any significant event in the processing lifecycle.

Different logs are attached to the DX events to provide additional information. For example, the inbound EDI file is attached to the root event (ISA) and, if needed, the TA1 message that is created and sent back to the partner.