Edi what is isa

Within each segment, various kinds of information appear, each separated by an asterisk or other identifier. Each position is set of by generally asterisks. This is the beginning segment of almost all EDI documents. This is the outermost envelope, all of the EDI data is placed within this layer. The purpose of this segment is to identify the sender and receiver, date, time and control number information.

This segment must match the IEA trailer segment. They served authorization and security password purposes in the past. In the example above ISA has a qualifier of 12 which means the phone number and ISA has the actual phone number.

In the example above this document was sent on November, 1st at AM. ISA For EDI Versions see ISA and greater this will serve as a repetition separator used to separate repeated occurrences of a simple data element or a composite data structure. More on repeating and composite data element structures will be discussed later in this course.

For example, the address segment might be used repeatedly to convey multiple sets of address information. The X12 standard defines the sequence of segments in the Transaction Set and also the sequence of elements within each segment. The relationship between segments and elements can be compared to the relationship between records and fields in a database environment.

See Figure 6 and Figure 7. ST Segment See Figure 6 for a diagram and following explanation of a definition for each element for this segment.

The following list describes the ST segments shown in Figure 6 Transaction Set Identifier Code 3 character code to represent transaction type e. Each X12 message is made up of a combination of the following elements: Data Segments Loops Elements are separated by delimiters.

The remainder of this section explains these elements. Data The data element is the smallest named unit of information in the X12 standard. Data elements can be broken down into types. The distinction between the types is strictly a matter of how they are used. The types are: Simple — If a data element occurs in a segment outside the defined boundaries of a composite data structure, it is called a simple data element.

Composite — If a data element occurs as an ordinally positioned member of a composite data structure, it is called a composite data element. A telephone number is a simple example of a composite. It has a three-digit area code, which must precede the three-digit central office code, which must precede the final four digits.

Each data element has a unique reference number, and it also has a name, description, data type, and minimum and maximum length. Segments A segment is a logical grouping of data elements. In X12, the same segment can be used for different purposes. For example: The NM1 segment is for any name patient, provider, organization, doctor The DTP segment is for any date date of birth, discharge date, coverage period Loops Loops are sets of repeating ordered segments.

The delimiters used in a message are defined in the interchange control header, the outermost layer enveloping the message. For this reason, there is flexibility in the delimiters that are used. No suggested delimiters are recommended as part of the X12 standards, but the industry-specific implementation guides do have recommended delimiters.