IMPDEF EDI implementation guide definition

TBG16 Entry Point

The EDI implementation guideline definition message (IMPDEF) permits the exchange of implementation details of an EDI message, including its usage and its presentation.

Send feedback Share via email

Header

Position
Segment
Name
Max use

  1. A service segment starting and uniquely identifying a message. The message type code for the EDI implementation guide definition message is IMPDEF. Note: EDI implementation guide definition messages conforming to this document must contain the following data in segment UNH, composite S009: Data element 0065 IMPDEF 0052 D 0054 11B 0051 UN

    1. Data element S009/0057 is retained for upward compatibility. The use of
    S016 and/or S017 is encouraged in preference.
    2. The combination of the values carried in data elements 0062 and S009 shall
    be used to identify uniquely the message within its group (if used) or if
    not used, within its interchange, for the purpose of acknowledgement.

  2. A segment to indicate the beginning of the message and to transmit function, type and number of the message.

  3. A segment identifying a message type to which the implementation details apply.

  4. A segment specifying the distribution conditions for the implementation.

  5. A segment specifying the identity of the source directory set and giving its language and maintenance operation. This identifies the underlying standard from which the standard message is drawn.

  6. A segment carrying reference information for the implementation as a whole. This may specify the unique registration identifier of this implementation guide; it may carry references to graphical information to be used or displayed whenever the implementation is physically displayed.

  7. A segment specifying dates related to the implementation guide, such as date of issue or date of approval.

  8. A segment providing implementation guide notes which relate to the implementation as a whole. It may also carry various legal or contractual phrases which may apply to the ownership or copyright of the implementation guide, or contractual terms which will be incorporated by reference into any contract of which a data transmission using this implementation is a part.

  9. Segment group 1
    Repeat 5

    1. A segment identifying the names of the parties involved in the transaction, e.g., originator, requester, author or secretariat.

    2. A segment identifying the address of the party.

    3. Segment group 2
      Repeat 9999

      1. A segment identifying a person or a department for the party to whom the communication should be directed.

      2. A segment identifying communication type and number of the person.

  10. Segment group 3
    Repeat 99999

    1. A segment identifying the object of the definition, and containing an optional 'name' or identifier.

    2. A segment providing implementation guide notes pertaining to the preceding definition, or to carry the text of a constraint expression.

    3. Segment group 4
      Repeat 1

      1. A segment specifying the usage of a segment group in a definition. The segment may identify one or more instances of a target segment group.

      2. A segment providing implementation guide notes or textual information related to the specific group in the underlying message.

    4. Segment group 5
      Repeat 999

      1. A segment specifying the usage of a segment in a message type structure for this definition. As well as defining the specific usage of a particular target segment, this segment also provides the segment context for the following element usage details. The segment may identify one or more instances of usage for any particular segment in the target data message.

      2. A segment providing implementation guide notes, or textual information relating to the specific segment in the underlying message.

    5. Segment group 6
      Repeat 99

      1. A segment specifying a footnote identification number that may place the relationship in the current context.

      2. A segment specifying a relationship between the various components, typically data elements in a segment, in the current context.

      3. A segment identifying the various components in a relationship, typically data elements in a segment, in the current context.

      4. A segment carrying text notes to the preceding relationship.

    6. Segment group 7
      Repeat 99

      1. A segment identifying a reference document or a following constraint expression.

      2. A segment carrying the text of a constraint expression or providing implementation guide notes pertaining to the preceding constraint.

    7. Segment group 8
      Repeat 99

      1. A segment identifying the usage of a simple or composite data element in the current context. This segment starts a block of information about any one particular contextualised usage of a data element in a target data message. The data element usage determines whether this segment is defining a composite context, a simple element context or a component element context.

      2. A segment providing details of any variation or restriction of the current data element as used in this context. Typically this segment will convey details of restricted size or character representation.

      3. A segment providing details of any editing information such as maximum field length and status that would be used by a screen-based editor, forms input or data output process when physical representation of the data carried in a data message using this implementation guide is required.

      4. A segment providing further details of presentational information such as text alignment and style that might be used by a screen-based editor, forms input or data output process when physical representation of the data carried in a data message using this implementation guide is required.

      5. A segment providing further details of processing information such as data handling, positioning or control that might be used by a screen-based editor, forms input or data output process when data is carried, stored or collected by a data message using this implementation guide is required.

      6. A segment providing implementation guide notes, or other textual information relating to this element usage. The segment will also be used to carry the final set of information that would be used by a screen-based editor; forms input or data output process; a legend or user- recognisable description; and a help text.

    8. Segment group 9
      Repeat 999

      1. A segment to measure the number of instances of usage of a component in a message. The segment may specify minima, maxima, range or instance criteria.

      2. A segment providing implementation guide notes, or other textual information relating to this measurement.

    9. Segment group 10
      Repeat 99999

      1. A segment identifying one or more components of an element value constraint series. It also may provide a default value for the current element context. This is expressed in a single text field so as to be used by or applicable to the broadest range of applications.

      2. A segment providing implementation guide notes, or other textual information related to the particular context. Such a context may include implementation guide notes for the default value.

    10. Segment group 11
      Repeat 99999

      1. A segment identifying the code value, its source and usage preference.

      2. A segment providing implementation guide notes, or other textual information related to the particular context.

    11. Segment group 12
      Repeat 99999

      1. A segment identifying an underlying data representation by tag, basic data type and size. This is the representation itself, and not a pointer to an external document.

      2. A segment providing implementation guide notes, or other relevant textual information.

  11. Segment group 13
    Repeat 1

    1. A segment specifying the details of any authentication (validation) procedure applied to the IMPDEF message.

    2. A segment specifying the date of authentication.

  12. A service segment ending a message, giving the total number of segments in the message (including the UNH & UNT) and the control reference number of the message.

    1. 0062, the value shall be identical to the value in 0062 in the
    corresponding UNH segment.
Stedi.comDocumentationContact us

Stedi is a registered trademark of Stedi, Inc. Stedi's EDI Reference is provided for marketing purposes and is free of charge. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.