![]() |
|
I'M Europe OII Home Page What is OII? Whats new in OII? OII Fora List OII Guides OII Index OII FAQ OII Feedback Disclaimer Search Database |
Electronic Data Interchange (EDI) StandardsThis section of the OII Standards and Specifications List provides information on standards used for electronic data interchange (EDI). It contains details of:
The standards in this section have been prepared by both private and public organisations. The following public bodies have been involved in their preparation:
On-line information on all aspects of EDI can be obtained over the World Wide Web by contactinghttp://www.sol.no/norsk/edipro/ediweb.html. |
Section Contents OII Documents OII Index OII Help |
UN/EDIFACTExpanded name Area covered Sponsoring body and standard details
The various UN/EDIFACT Directories and the Code List are generally referred to as the UN/EDIFACT Directory set. A number ofdirectory sets have been issued since 1988, with D97B being the most recent. The nomenclature for each directory set has changed repeatedly over the years, as has the number of yearly releases and draft/standard status. Currently, standard directory sets containing UNSMs (United Nations Standard Messages) are issued twice each year. Note that the concept of trial, draft and standard directories has now been replaced by the concepts of MIDs (messages in development) and UNSMs. The D93A Standards Directory was used as the basis of CEN European Standards (ENs) through a fast track procedure in relation to WEEB/EBES associated standards body status within CEN. These were to be "frozen" for a minimum of three years so providing stability. However as several UN/EDIFACT directory sets have been released since 1993, a decision has recently been taken to propose the withdrawal of D93A based ENs. A decision, if any, has yet to be taken on the submission of a new directory set to CEN. Through the ISO/IEC/ECE MoU coordination management group, discussions are also taking place on the possibility of using ISO's fast track procedure (modified) in order for UN/EDIFACT directory sets to be recognised as ISO standards -- without change. The UN/EDIFACT Data Elements Directory is a subset of the United Nations Trade Data Elements Directory (ISO 7372:1993). The WP.4/CEFACT Syntax Development group has been working on the new draft version 4 of the UN/EDIFACT Syntax. The syntax is divided in 10 parts, each of which has a separate route through the WP.4/CEFACT and the joint ISO (TC 154)/UN/ECE fast track approval process. The first trace voting within ISO has approved parts 1,2,3,8. The other syntax parts are either still for approval in CEFACT and/or ISO. On this basis, the complete edition of ISO 9735 should be issued in late 1998. The new UN/EDIFACT batch Message Design Rules (MDR) covering Version 3 of the Syntax are being finalised and will be for CEFACT approval in late 1997 and implementation in mid 1998. Through the CEFACT AC1 Group, work is being progressed on Object Orientated EDI (OO-EDI) to build from UN/EDIFACT’s semantic and model content into today's technologies, notably the use of a top-down object oriented approach coupled with the rigorous use of modelling techniques -- principally the IDEF (Integration DEFinition) method. This means starting at the level of the business process, and decomposing this process, through a number of logical steps, all the way down to the semantic level. Characteristics/description In UN/EDIFACT, individual (simple) data elements can be combined into composite data elements. Simple data elements and/or composite data elements are structured together into segments. Both segments and composites allow qualification, which allows the creation of very generic components. This genericity is one of the key differences between UN/EDIFACT and TDI. Messages are the end-products of the UN/EDIFACT process. A UN/EDIFACT message describes a particular business process which often corresponds to a traditional paper document (examples of UN/EDIFACT messages range from invoicing (INVOIC) through to MEDREQ (Medical Service Request Message). The structure of a UN/EDIFACT message is defined by a collection of segments -- generally organised into groups. The message specification includes the maximum number of occurrences of the individual segment groups and their component segments, as well as their status (mandatory or conditional). The EDIFACT Syntax Rules define the structuring of (simple) data elements, composite data elements, segments, and messages. The principal characteristics of the EDIFACT Syntax Rules are:
Version 3 EDIFACT Syntax Rules is designed for batch mode data transfer. Draft Version 4 of the Syntax Rules formally includes new parts on interactive data transfer, security mechanisms, multi-format data exchange, a specific service message for acknowledgement and error notification, as well as significant revisions to the batch mode EDI transfer rules. Interactive EDIFACT (I-EDI) is characterised by a formalised association between the two interchange parties through the use of a dialogue, short response times, and the ability to dynamically direct the course of the transaction as a result of earlier exchanges within the dialogue. Usage (Market segment and penetration) Since the approval of the Invoice Message (INVOIC) as a UNSM in 1988, UN/EDIFACT has been widened to cover a multitude of industry sectors. To date around 160 messages have been approved as UNSMs (Previously Status 1 and Status 2) and approximately 100 have been approved as "Messages in development (MID)" (previously Status 0). It should be noted that the UN/EDIFACT process has spawned a number of European EDI user groups (EUREDIS), who input to the development of UN/EDIFACT message specifications. Typically, these EUREDIS are industry-sector specific. Some of the EUREDIS also have a large programme of work for the development of Message Implementation Guidelines specific to their sector needs, as well as other activities in EDI related areas. A number of EUREDIS have widened their scope to cover Electronic Commerce. An example of EUREDIS and their activities is the Travel Technology Initiative which consists of about 100 member companies (mostly travel principles and agents, plus a few technology suppliers) from 6 European countries. This Initiative has created two UN/EDIFACT-based standards which are known to be in use in about 70 European companies and a few outside Europe. The two standards are:
In addition to EUREDIS, UN/EDIFACT message development is supported by industry groupings whose activities are considerably wider than but include EDI. Some of these are international organisations. Examples are SWIFT and UIC, which are covered elsewhere in this report as these two organisations have also developed their own proprietary EDI standards which pre-date UN/EDIFACT. Sectorial areas covered by UN/EDIFACT messages include :
Use of UN/EDIFACT has increased considerably in Europe, as well as in other parts of the world. Cross-border EDI transactions are also rising. Many EDI communities who have proprietary EDI standards have now (partially) migrated to UN/EDIFACT (including ODETTE, SWIFT, the TDI community, and ANSI X12). Further details available from:
|
Section Contents OII Documents OII Index OII Help |
EANCOMExpanded name Area covered Sponsoring body and standard details
Characteristics/description
Usage (Market segment and penetration) Further details available from: |
Section Contents OII Documents OII Index OII Help |
HealthcareExpanded name Area covered Sponsoring body and standard details
Characteristics/description Usage (Market segment and penetration) The majority of HL7 members are in the USA although affiliate organisations have been established in other states including several in Europe (e.g. Germany and Netherlands). Much of the impetus for these "Internationalisation" activities comes from the fact that US suppliers provide native HL7 compliant hospital systems to these countries. HL7 covers admission, discharge, transfers, orders, results, queries, detailed financial transactions, and ancillary reporting. Further details available from: |
Section Contents OII Documents OII Index OII Help |
IATA-EDIExpanded name Area covered Sponsoring body and standard details
Characteristics/description Usage (Market segment and penetration) IATA has undertaken a major activity to migrate from its own standard to UN/EDIFACT. For instance, the IATA Cargo-IMP series of messages have now been mapped onto UN/EDIFACT (Cargo-FACT). Another important development of IATA has been the development of the IATA Interactive UN/EDIFACT. This is based on the interactive UN/EDIFACT specifications at the interchange level and OSI Transaction Processing at the communications level. IATA members have been some of the main driving forces for the addition of interactive components to the UN/EDIFACT directory sets. Further details available from: |
Section Contents OII Documents OII Index OII Help |
ODETTEExpanded name Area covered Sponsoring body and standard details
Characteristics/description Usage (Market segment and penetration) It should be noted that the remit of ODETTE is considerably wider than the development of EDI standards. ODETTE has produced its own communications software for EDI transactions, including the ODETTE File Transfer Protocol (OFTP), which is used by the ODETTE members as well as other communities (eg White goods). Further details available from: |
Section Contents OII Documents OII Index OII Help |
Open-edi Reference ModelArea covered Sponsoring body and standard details
Characteristics/description
The Open-edi Reference Model uses two views to describe the relevant aspects of business transactions: Business Operational View (BOV) and Functional Service View (FSV). The BOV addresses the aspects of semantics of business data in business transactions and associated data interchanges. The FSV addresses the supporting services meeting the mechanistic needs of Open-edi, with a focus on the Information Technology aspects (service capabilities, service interfaces and protocols). Usage (Market segment and penetration) Further details available from: More on-line information on Open-edi can be obtained by contacting |
Section Contents OII Documents OII Index OII Help |
SPEC 2000(M)Expanded name Area covered Sponsoring body and standard details
Characteristics/description Usage (Market segment and penetration) Further details available from: |
Section Contents OII Documents OII Index OII Help |
SWIFTExpanded name Area covered Sponsoring body and standard details Characteristics/description Each SWIFT message comprises a header, the user data, an authenticator, and a trailer. On entering the network, the message is automatically encrypted to ensure secrecy. The authenticator guarantees that the text has not been modified during transmission. The user data is organised into two kinds of fields. Mandatory fields contain information essential for the messages to be processed. Optional fields are used for transactions that are more complex and for additional instructions. Service or "system" messages are also available to enable users to communicate with the SWIFT system itself (for requesting system functions, special reports, message retrieval, training, etc) and vice versa (for responding to user requests, announcing system upgrades and new services, etc). Usage (Market segment and penetration) SWIFT has announced its intention to support UN/EDIFACT messages for the trader to bank interface. Further details available from: |
Section Contents OII Documents OII Index OII Help |
TDIExpanded name Area covered Sponsoring body and standard details
Characteristics/description Unlike UN/EDIFACT, qualified data elements and composite data elements are not available in TDI. Usage (Market segment and penetration) Further details available from: |
Section Contents OII Documents OII Index OII Help |
UIC 912Expanded name Area covered Sponsoring body and standard details
Characteristics/description Each message format contains a header followed by a series of 32 bit fields. 912 is unique in that the first 32 bit field identifies the optional elements to be used in the message by invoking the bit rate of the particular element if it is present in the actual transmission. The message format contains both optional and mandatory elements. Usage (Market segment and penetration) Further details available from: |
Section Contents OII Documents OII Index OII Help |
X12Expanded name Area covered Sponsoring body and standard details
Note: X12.5 and X12.6 define the X12 Syntax. The most recent transaction sets and messages are published in Draft Standards for Trial Use (DSTU) Version 3 Release 5 (December 1994). This contains 225 transaction sets and two (UN/EDIFACT) messages. DSTUs are fully approved by ASC X12, though not by ANSI. Once approved by ANSI, DSTUs become American National Standards (ANS). It is expected that ANS Version 4 will be functionally equivalent to DSTU Version 3, Release 7. ANS Version 3, published in March 1992, is functionally equivalent to DSTU Version 2, Release 4. Characteristics/description ANSI transaction sets include those that share very similar business functions. Thus, there are a number of different ANSI transaction sets for sector-specific invoicing, all of which relate closely to the single UN/EDIFACT Invoice Message. Usage (Market segment and penetration) In 1994 ASC X12 balloted its members concerning the migration to UN/EDIFACT, with 1997 being set as the target date. A majority of 75% was returned in favour of the migration plan. The original migration plan was, however, amended through a motion tabled by the US healthcare community at an X12 meeting in February 1995. The amendment means that future versions of ANS will be issued beyond Version 4 originally planned for 1997, and X12 transaction sets will continue to be processed as ANS’s after 1997. It has however been decided that the ballot on migration to UN/EDIFACT is to be carried out every three years until a firm position on migration is reached. It is uncertain if the 75% majority will be maintained. Further details available from: |
Section Contents OII Documents OII Index OII Help |
Other-EDIExpanded name Area covered Sponsoring body and standard details
Characteristics/description Usage (Market segment and penetration) Further details available from: |
Section Contents OII Documents OII Index OII Help |
This information set on OII standards is maintained by Martin Bryan of The SGML Centre and Man-Sze Li of IC Focus on behalf of European Commission DGXIII/E. File last updated: September 1997 |