MapForce and EDI

www.altova.com Print this Topic Previous Page Up One Level Next page

Home >  Data Sources and Targets >

MapForce and EDI

Altova website: _ic_link EDI mapping

 

EDI (Electronic Data Interchange) is a family of standards which enable electronic exchange of data between organizations or businesses.

 

MapForce supports translating data to or from EDI formats in any of the following transformation languages: BUILT-IN, C#, C++, Java (see also Selecting a Transformation Language ). The EDI data can be mapped to or from any of the formats supported by MapForce, including databases, flat files, XML documents, and others.

 

MapForce supports the following flavours of EDI:

 

Standard

Description

ASC X12

ASC X12 is an industry standard for document interchange. MapForce supports versions: 3040, 3050, 3060, 3070, 4010, 4020, 4030, 4040, 4041, 4042, 4050, 4051, 4052, 4060, 5010, 5011, 5012, 5020, 5030, 5040, 5050, 6010, 6020, 6030, and 6040.

 

The default ASC X12 version in MapForce is 6040.

 

ASC X12 components have "virtual" nodes into which EDI parser error information/data is written depending on the settings you select in the EDI Validation Settings dialog box (see EDI component validation ). An X12 997 Functional Acknowledgement can be generated from any X12 document.

 

For more information about ASC X12, see http://www.x12.org/.

HIPAA X12

HIPAA is based on the X12 EDI 5010 standard, but has its own specialized versions which are natively supported by MapForce 2011 Release 3 or later.

 

The default HIPAA X12 version in MapForce is release A2 of the HIPAA implementation specs (TR3). 

 

Previous releases are available for download on the MapForce Components page of the Altova website (https://www.altova.com/mapforce/download/libraries).

HL7

HL7 is an industry standard for data exchange between medical applications and is an abbreviation of "Health Level Seven". MapForce supports versions 2.2 to 2.6.

 

The default HL7 version in MapForce is 2.6.

 

A separate installer for the additional HL7 V2.2 - V2.5.1 XML Schemas and configuration files is available on the MapForce Components page of the Altova website (https://www.altova.com/mapforce/download/libraries).

 

The XML-based HL7 version 3.x is supported in MapForce 2019 using XML schema components.

 

The MapForceExamples project contains a sample that maps a HL7 V2.6 to a HL7 V3 XML file (HL7V260_to_HL7V3.mfd).

 

For more information about HL7, see https://www.hl7.org/.

IATA PADIS

PADIS (Passenger and Airport Data Interchange Standards) is an industry standard for the exchange of passenger and airport data using EDI documents. MapForce supports versions: 00.1 to 08.1.

 

The default PADIS version in MapForce is 08.1.

 

For more information about IATA PADIS, see http://www.iata.org/Pages/default.aspx.

NCPDP SCRIPT

SCRIPT is a standard for exchanging electronic information in the US healthcare sector developed by the NCPDP (National Council for Prescription Drug Programs), see http://www.ncpdp.org. MapForce supports mapping data between files in SCRIPT format and any other format supported by MapForce, including XML, CSV, Microsoft Excel, databases, and others. The supported NCPDP SCRIPT versions are: 8.1, 10.6, 10.10.

 

The default NCPDP SCRIPT version in MapForce is 10.10.

SAP IDocs

SAP IDocs (intermediate documents) documents are used to exchange business data between SAP R/3 and non-SAP applications. The documents are a form of intermediate data storage which can be exchanged between different systems.

 

For more information about SAP IDocs, see https://help.sap.com/saphelp_nw70/helpdata/en/0b/2a6095507d11d18ee90000e8366fc2/frameset.htm.

TRADACOMS

TRADACOMS (Trading Data Communications) is a UK-specific Electronic Data Interchange standard used in the retail business.

 

MapForce implements the base TRADACOMS specification as laid out in the "TRADACOMS Manual of Standards for Electronic Data Interchange", published in January 1993 by the Article Numbering Association (ANA) UK, now known as GS1 UK ( https://www.gs1uk.org ). For other TRADACOMS versions, MapForce can be customized to process new message types, data elements, and code values, by means of configuration files.

UN/EDIFACT

UN/EDIFACT (the United Nations rules for Electronic Data Interchange for Administration, Commerce and Transport) is a set of standards for electronic document interchange, see https://www.unece.org/cefact/edifact/welcome.html. MapForce supports the messages contained in directories D93.A - D.18B.

 

The default UN/EDIFACT version in MapForce is D.18B.

 

A separate installer for all previous versions back to D93.A, including the configuration files required for Interactive EDI mappings, is available on the Altova MapForce Libraries page (https://www.altova.com/components_mapforce.html).

 

 

The default version available in MapForce for each EDI flavour is highlighted in bold in the table above. If necessary, you can install previous versions of EDI configuration files from the MapForce Components page of the Altova website (https://www.altova.com/mapforce/download/libraries ). After installation, the installed EDI versions become available in MapForce in addition to the default versions.

 

For a single EDI component that you have added to the mapping area, MapForce can process multiple message types of any single standard EDI release. For example, this enables you to read data from an interchange file which includes more than one message type, or to generate as mapping output an interchange file which contains multiple message types. You can also process data from multiple instance files containing different message types. Note that operations such as the ones described above are only meaningful when they are supported by the underlying specification.

 

If your organization is using EDI specifications that are customizations of those already supported by MapForce, it is possible to adapt MapForce to your custom EDI specification by means of configuration files. For example, you can add custom messages, segments, data elements, code lists, and so on (or change the existing ones), thus creating a custom EDI collection similar to any of the EDI-related directories that are already supported by MapForce. For more information, see Customizing EDI Structure and Customizing EDI Validation.


© 2019 Altova GmbH