GESMES Generic statistical

TBG7 Statistics

The compilation of statistics is a continuous chain starting with raw data collection, followed by a number of harmonization and aggregation processes leading to aggregated statistical data. Raw data collection is realized by means of surveys, sampling, direct reporting from individuals, economic operators. Harmonization and aggregation processes are very often handled by statistical bodies or authorized economic operators in case of direct reporting. A Generic Statistical Message (GESMES) is used by an organisation involved in this elaboration process to transmit a statistical data set. It permits the transmission of the following, either in the same and/or different messages: -the statistical concepts comprising the data set and their structure -if required, all related information ( code sets, labels, methodological notes, footnotes, etc.), -the statistical figures of the data set. This message could be used by producers and users of statistical information such as: National Statistical Offices, ministries, private and public administrations, private companies etc.

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 Generic statistical message is GESMES. Note: Generic statistical messages conforming to this document must contain the following data in segment UNH, composite S009: Data element 0065 GESMES 0052 D 0054 17B 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 specifying the functional use (e.g. sub-set) of the Generic Statistical Message and identifying the message sent.

  3. A segment identifying dates which are relevant to the whole of the message.

  4. Segment group 1
    Repeat 9999

    1. A segment containing the unique identifier of the footnote.

    2. A segment containing the text relevant to the footnote.

  5. Segment group 2
    Repeat 9

    1. A segment identifying the name and address of a party.

    2. A segment giving the identity number of the data transmitted as it is known by the organisation described in the NAD segment.

    3. Segment group 3
      Repeat 5

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

      2. A segment providing a communication number for the contact identified in the CTA segment.

  6. Segment group 4
    Repeat 99

    1. A segment identifying the value list.

    2. A segment identifying the period of validity of the value list and, if the value list is a date list, then a date value in that list.

    3. A segment containing text associated with the value list.

    4. Segment group 5
      Repeat 9

      1. A segment containing an identifier of an object related to the value list (e.g. a statistical nomenclature from which the codes in the list are derived, or a footnote).

      2. A segment containing date information related to the identified object of the value list such as validity date or date range.

    5. Segment group 6
      Repeat 5

      1. A segment containing additional identifiers associated with the value list (e.g. for a statistical nomenclature this could be a revision number or level number).

      2. A segment identifying the period of validity relating to the object identified in the GIR of this group.

    6. Segment group 7
      Repeat 9999

      1. A segment identifying a particular value of a code.

      2. A segment containing the textual description of the code. Multi-lingual definitions may be present in different occurrences of this segment.

      3. Segment group 8
        Repeat 9

        1. A segment containing an identifier of an object related to the code value (e.g. a related code list containing a list of code values for the code, or a footnote).

        2. A segment identifying the period of validity relating to the object identification.

  7. Segment group 9
    Repeat 999

    1. A segment identifying a statistical concept.

    2. A segment containing the name, definition or description of the statistical concept.

    3. A segment containing the identity of a footnote relevant to the statistical concept.

  8. Segment group 10
    Repeat 9999

    1. A segment containing the unique identifier of the array structure.

    2. A segment containing a processing indicator associated with the array structure.

    3. A segment containing a name/title or description of the structure of an array.

    4. A segment containing the identity of a footnote relevant to the structure.

    5. Segment group 11
      Repeat 999

      1. A segment that defines a statistical concept or other object (such as a value list) used by an array and its position in the array.

      2. A segment containing an attribute that further defines the structure component (e.g. type of value, type of measurement, etc.).

      3. Segment group 12
        Repeat 9999

        1. A segment identifying the value list or value.

        2. A segment containing an attribute that further defines the value (e.g. type of value, type of measurement etc.).

        3. A segment identifying period of validity of the value list or other dates relevant to the value list.

  9. Segment group 13
    Repeat 999

    1. A segment containing the unique identifier of the data set.

    2. A segment containing information on the status of the information in the data set, e.g. its elaboration or privacy status.

    3. A segment identifying a date relevant to the data set, e.g. date of original elaboration.

    4. A segment containing a textual description of the data set.

    5. A segment containing additional identifiers associated with the data set (e.g. identification of the source or destination of the data in the data set).

    6. Segment group 14
      Repeat 99

      1. A segment containing an identifier relevant to the data set, such as the scope or structure definition used by the data set.

      2. A segment containing a processing indicator associated with the array data.

      3. A segment identifying a date relevant to the identity e.g. date relating to the scope of the data.

      4. Segment group 15
        Repeat 999

        1. A segment identifying a particular value of a code.

        2. A segment containing the textual description of the code. Multi-lingual definitions may be present in different occurrences of this segment.

      5. Segment group 16
        Repeat 999

        1. A segment that identifies the structure component.

        2. A segment containing an attribute that further defines the structure component (e.g. type of value, type of measurement etc.).

        3. A segment specifying a date relevant to the structure component e.g. a date for time series data.

        4. Segment group 17
          Repeat 9999

          1. A segment identifying a particular value of a code.

          2. A segment containing the textual description of the code. Multi-lingual definitions may be present in different occurrences of this segment.

    7. A segment containing the data in the data set.

      The composite C770 - array cell details - occurs
      9,999 times in the segment. The use of the ARR
      segment is restricted to be used only with Version 3
      of ISO-9735.
      The component 9424 - array cell information - occurs
      100 times in the composite C770. The use of C770 is
      restricted to be used only with the ARR segment
      within Version 3 of ISO-9735.
    8. Segment group 18
      Repeat 5

      1. A segment identifying a particular department in an organisation responsible for the data set.

      2. A segment containing an identifier used by the sender or receiver to identify the data set.

      3. Segment group 19
        Repeat 5

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

        2. A segment providing a communication number for the contact identified in the CTA segment.

    9. Segment group 20
      Repeat 999

      1. A segment identifying a set of footnotes, which are either defined in this group or have been defined previously.

      2. Segment group 21
        Repeat 9999

        1. A segment defining the scope of a footnote in terms of the relationship between the data in the ARR segment in segment group 22 and the data in the ARR segment in segment group 13.

        2. Segment group 22
          Repeat 9999

          1. A segment containing data values that identify the location in the data set to which a footnote is relevant.

            The composite C770 - array cell details - occurs
            9,999 times in the segment. The use of the ARR
            segment is restricted to be used only with Version 3
            of ISO-9735.
            The component 9424 - array cell information - occurs
            100 times in the composite C770. The use of C770 is
            restricted to be used only with the ARR segment
            within Version 3 of ISO-9735.

          2. A segment containing a footnote value.

          3. Segment group 23
            Repeat 9999

            1. A segment containing the identity of a footnote relevant to the data in the data set.

            2. A segment containing an uncoded attribute value.

            3. Segment group 24
              Repeat 9999

              1. A segment which specifies a coded attribute value.

              2. A segment which specifies the name, description or definition of a coded attribute value.

    10. Segment group 25
      Repeat 9999

      1. A segment containing the unique identifier of the footnote.

      2. A segment containing the text of the footnote.

  10. 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.