Version 4.9.0
Version
4.8.0
Version
4.7.0
Version
4.6.0
Version
4.4.0
Version
4.3.0
Version 4.2.0
Version 4.1.0
Version 4.0
Redix Format Converter Version 4.9.0
--------------------------------------------------------------------------------
New Features:
The Redix Mapper Version 4.9.0 includes a new backup utility, which allows users to backup map files.
In previous versions, the intra-segment compliance checking was done in the OFD. In this version, it will be done in the IFD using the new G, H, or I types in the "Syntax Rules".
Additional OFD functions, including getlineno, preparelist, isuniquelist, deletelist, isvaliddate, isvalidtime, etc, have been added.
To improve performance when accessing the Oracle database, the new version will bypass the ODBC driver and directly interface with the Oracle native driver. The following OFD functions have been added in the new version for this purpose: oraconnect, orardbsqlcmd, oradisconnect, and oragetnextavailint.
Four types of code checks are supported in the new version, including Redix proprietary index files.
The new version adds a new GUI to help users view every translation error. The errors can be compared to the input file, the standard message, and the map.
The performance of the HIPAA compliance process has been improved by moving the HIPAA intra-segment checking into the IFD.
Redix
Format Converter Version 4.8.0
--------------------------------------------------------------------------------
New Features:
The Redix Mapper Version 4.8.0 now includes a HIPAA/EDI debugging screen. The screen displays detailed error information for each element if errors were found during the translation. A red box will also be displayed in front of each row to highlight the error segment. These new features will allow users to perform a detailed HIPAA GAP analysis.
The Edit Message screen in the Message Definition area now allows users to import segments and their related element information from other message definitions.
The Edit Message screen now also supports a new tree view for non-XML messages.
The new export feature in the Export a Map screen exports all of the information about each map that will be exported and its source/target message definitions, including code definitions and import OFDs.
In the Redix Editor screen, new utilities have been added, including sorting and conversion functions.
When cloning a map, the Redix Mapper Version 4.8.0 will also allow users to clone the message definitions.
The Redix Mapper Version 4.8.0 allows users to convert external table lookups to the "A" type of code check.
The Redix Automation Processor 4.8.0 includes a new server process RAPserver. Users can use VC++, VB, or Java to interface the server. Several RAP client examples are provided in the examples folder under the Redix directory.
A new default userdata screen allows users to edit ISA and GS segments, as well as separators, for each X12 and HIPAA map.
The Redix AnyToAny Engine with database module now includes two additional keywords, rdbgetnextint and rdbgetcurint.
The Redix Mapper Version 4.8.0 adds one more button to allow users quickly locate the row that has an OFD error.
The Redix Automation Processor has been modified to handle EDI/HIPAA to database translations more efficiently.
Redix
Format Converter Version 4.7.0
--------------------------------------------------------------------------------
New Features:
The Redix Mapper Version 4.7.0 with the database module now supports mapping a database in both directions, i.e., database to XML, EDI, or CSV, etc., and vice versa. The database can be any ODBC compliant database system.
The Redix AnyToAny Engine is enhanced to support more functions, including sendmail(), atocur(), etc.
The Redix HIPAA package provides more pre-defined maps, including the NSF 2.0/3.01 <-> HIPAA 837, UB92 5.0/6.0 <-> HIPPA 837, and HCFA ERA <-> HIPAA 835. The proprietary UB92 format, such as the state specific Medicare/Medicaid UB92, can also now be mapped to a HIPAA 837 transaction set in a pre-defined map.
The Redix HIPAA package with database module provides a pre-defined map, which converts the HIPAA 837 transaction set to a Microsoft SQL Server database; then in a separate pre-defined map, the data is extracted from the SQL Server and re-formulated into a HIPAA 837 message.
The Redix HIPAA package provides balance check information. With one key-stroke or an API function call, a HIPAA 837 or 835 transaction sets can be balanced. A balance report is automatically generated. The report can also be customized.
Redix Format Converter Version 4.6.0
--------------------------------------------------------------------------------
New Features:
Supports W3C XML Schema. In addition to the DTD, an XML Schema (xsd) file can be imported to the Redix Mapper. Once the XML is message is imported, the message is ready to be mapped.
In the previous version, the X12 syntax rules and EDI code definitions are defined in the OFD (Output File Descriptor). In this new release, they are defined in the IFD (Input File Descriptor) instead. The Redix XML GUI Mapper's GUI is deigned to help users construct the X12 syntax rules and EDI code definitions. When the user extracts the EDI message from the EDI standard, the X12 syntax rules and EDI code definitions are automatically generated. To support the X12 syntax rules, a new section area "#SEGCOND" is created in the IFD.
Supports RosettaNet version 2.0.
Automatically define the appropriate separators when a new map is created.
In the previous version, when an XML message was mapped, a user would have to create a dummy trailer node to hold the OFD statements, such as "endloop" or "endsegment". In the new release, the user does not have to do this any more since the Redix Mapper will automatically generate the "endloop" or "endsegment" statements without using a dummy trailer.
Supports database mapping. The new release provides a GUI to allow a user to map any message, including EDI, XML, CSV, flat file, to an ODBC database.
Redix Format Converter Version 4.4.0
--------------------------------------------------------------------------------
New
Features:
With this new version, users can now identify a variety of segment and element details through the use of the Mapper Area's Input and Output Message Definition's icons.
- An input message definition's icon can now be differentiated between segments that contain or do not contain loops.
- An output message definition's icon can also now be differentiated between segments that contain or do not contain defined elements, loops, segment loops, conditional statements, before events, and after events. In addition, different icons are now used to distinguish between different types of element definitions, as well as whether or not an element contains loops, segment loops, conditional statements, before events, and/or after events.
The Redix Mapper Area has also been expanded to allow a user to open a dialog box, which will allow the user to display and/or print a listing of additional information, e.g., element conditions, before/after events, etc., associated with a Map Definition's elements.
Redix Format Converter Version 4.3.0
--------------------------------------------------------------------------------
New
Features:
The long-awaited Integration Guide is finally available.
- This guide details the API, COM, ActiveX, and Redix Automation Processor (RAP).
- It also provides examples to interface the Redix AnyToAny engine, AnyToXML engine, user exits functions, database module, and userdata() functions with the user's existing application. These examples are in various programming languages, including VC++, VB, and JAVA (TM).
It is now possible to pass the EDI Interchange Information with an automatically generated XML to EDI Map Definition, using the userdata() function in an OFD file.
-
The ability to
pass data during translation by using the userdata() function has existed for
quite some time, but now this feature has been taken one step further. Users now
have the option to use a hybrid OFD form during the exportation of an XML to EDI
Map Definition in the Export to DTD Dialog Box.
-
In addition,
precedence has been given to existing data from the incoming XML input file. The
following rules apply to the ISA and GS segment fields:
| - | If input data is passed to the map, use this data | |
| - | Otherwise, if there is no data being passed, use the userdata() function | |
| - | If there is no input data nor userdata() function being passed, use a default value |
-
For more
details about this new feature and its specifications, please refer to the
"Extracting Using userdata() from XML to EDI" section of the "N2K
(Need To Know)" chapter from the GUI Mapper Online Help Manual.
The
integer error
return code may now be referenced to display the cause of error.
-
Upon completion of
a translation process, whether it was successful or not, an integer is always
returned, corresponding to the success of the translation. The integer zero
represents a successful translation, while a negative integer is returned to
reference a failed translation. Now, it is possible for the user to send the
returned error code to an API or command-line function to return the error
message. For example:
| - | A translation that returns the integer -104, may be passed through an API such as redix_get_err_msg(-104) to return the error message: | |
| Error in Opening the IFD. | ||
| - | or, a translation that returns a -101 may be passed through the command-line command errcode -101 to return the message: | |
| Error in Opening the Input File. | ||
-
The API function redix_get_err_msg
(integer) has now been added to the file rfcerr.lib (for Windows) and
libredixerr.a (for UNIX) located in the /lib directory of the Redix folder.
-
The command-line
executable errcode integer has now been added to the Redix folder.
-
For more
information concerning the error return code processes, please refer to the
"N2K (Need To Know)" chapter under the subject "Error Code
Messages" of the GUI Mapper Online Help Manual.
Two
new functions, redix_mem_process and redix_app_process, have been
added to allow users to interact with the Redix Automation Processor using
input/output files or data streams.
-
The
function redix_mem_process allows the user to use data streams as the
input and output data. The following is a description of the parameters, which
may be used:
| redix_mem_process( | input_string | , | A variable of type String Data containing the input information. |
| output_string | , | A variable of type String Data to contain the output information. | |
| error_string | , | A variable of type String Data to contain any error information, if one exists. | |
| ack_string | , | A variable of type String Data to contain any acknowledgement information, if one is to be created. | |
| configuration_file | , | A variable of type String Data containing the name of the configuration file of the RAP process. | |
| log_file | , | A variable of type String Data containing the name of the log file, of the RAP process, to be appended. | |
| userdata | , | A variable of type String Data containing the userdata to the AnyToAny engine. | |
| ); | |||
-
The function redix_app_process
allows a user to use data files as the input and output data. Below is a
description of the parameters, which may be used:
| redix_app_process( | input_file | , | A variable of type String Data containing the name of the input file of the RAP process. |
| output_file | , | A variable of type String Data containing the name of the output file, to be created during the RAP process. | |
| error_file | , | A variable of type String Data containing the name of the error file, to be created (if any), during the RAP process. | |
| ack_file | , | A variable of type String Data containing the name of the acknowledgement file, to be created (if any), during the RAP process. | |
| configuration_file | , | A variable of type String Data containing the name of the configuration file of the RAP process. | |
| log_file | , | A variable of type String Data containing the name of the log file, of the RAP process, to be appended. | |
| userdata | , | A variable of type String Data containing the userdata to the AnyToAny engine. | |
| ); | |||
-
The difference
between the functions redix_app_process and the redix_mem_process is that the
redix_mem_process function writes the output to a string, while the
redix_app_process writes the output to a file.
-
When these
functions are used, the directories and filenames defined in the configuration
file are NOT used; instead, the directories and filenames that are specified by
the parameters. In addition, the need to include the parameter log_file is
optional. If no value is passed for the log_file parameter, the name XMLProcess.log
will be used by default.
-
Additional
information concerning the new RAP functions may be found in the Redix
Automation Processor Manual and Integration Guide.
Redix Format Converter Version 4.2.0
--------------------------------------------------------------------------------
New
Features:
To
accommodate the user’s rapidly changing needs, as well as to enhance the
GUI’s ease of use, the RFC Conversion Area now has a new design.
-
To better integrate the RFC Conversion Area into the RFC, the Conversion
Area’s structure is now similar to the Mapper and Message Definition Areas.
-
The tabs are now designed to give the user a sense of before and after
the conversion process.
- In addition to the new design, users can now create a Conversion Area
Project from the Generate IFD / OFD Dialog Box.
Furthermore,
the RFC AnyToXML Area also has a new and innovative design.
-
As with the RFC Conversion Area, the RFC AnyToXML Area’s structure is
also similar to Mapper and Message Definition Areas.
-
Similar to the RFC Conversion Area, the tabs are now designed to show the
user before and after the conversion process.
-
Like the RFC Conversion Area, users can now create an AnyToXML Area
Project from the Export to DTD or Export to Schema dialog boxes.
To speed
up the conversion process, the Generate IFD / OFD dialog box has also been
updated.
- Through the use of the Generate IFD / OFD dialog box, the user can now create a Conversion Area project in the Mapper.
- The additions in the Generate IFD / OFD dialog box will allow the user to select a map definition to be used and specify any pertinent separators for the new project.
-
Once the project is created, all the user needs to do is to add some
personal preferences, an input file, and then, the user can view his/her own
work.
-
Additional details can now be found in the rfc.hlp manual under the
topic, The XML Cycle of the “Need 2 Know” chapter.
In
addition, the Export to DTD dialog box has also been updated.
- The Export to DTD dialog box now allows the user to create an AnyToXML Area project from any non-XML definition.
- The additions in the Export to DTD dialog box will allow the user to select a non-XML message definition to be used. Then the user can generate the new project along with a new DTD and Mapper Area Definition.
- Once the project is created, all the user needs to do is to add some personal preferences, an input file, and then, the user can view his/her own work.
-
In addition, while using the Element style structure, the user can now
construct his/her own DTD and Map Definition using the Description Naming
Convention.
-
Additional details can now be found in the rfc.hlp manual under the
topic, The XML Cycle of the "Need 2 Know" chapter.
Lastly,
the Export to Schema dialog box has also been updated.
-
The Export to Schema dialog box now has the ability to create an AnyToXML
Area project from any non-XML definition.
-
This addition in the Export to Schema dialog box will allow the user to
select any non-XML message definition and generate this into a new project along
with the Schema.
-
Once the project is created, all the user needs to do is add to some
personal preferences, an input file, and then, the user can view his/her own
work.
-
Additional details can be found in the rfc.hlp manual.
Additional
Corrections and Updates:
Bugs in the CSV
Multiple Header / Record Type have been solved.
- The program will now not only assume endsegment statements, but will also assume the endloop statement as well, allowing for proper loop cycling.
Redix Format Converter Version 4.1.0
--------------------------------------------------------------------------------
The RFC supports the ability to automatically map a message definition to its own matching, well-structured, newly created, XML definition.
The RFC now supports Message Definition Extraction to W3C Schema
- As development of the W3C Schema approaches confirmation, the standard has proven itself as a viable asset to many of our clients. In turn, Redix has included the ability for the user to extract any Message definition to the W3C Schema, with the click of a few buttons. |
- Check out http://www.w3c.org (© The World Wide Web Consortium ) for more information on the standards formatting. |
- Additional details can now be found in the rfc.hlp manual. |
The RFC Now Supports Message Definition Extraction to BizTalk Schema
Massive Mapper Tutorial Expansion
Redix Command-line Procedures Explained
- The RFC's User's Manual was added to, to provide more background involving Command-line procedures. |
- Additional details can be found in the rfc.hlp manual. |
New Database Module for Code Check Validation
New Module: Redix Automation Processor
New smart CSV data type
Java [TM] JDK 1.3 and above Version Fix
writeXMLAttribute() Bug Correction
- A bug involving the writeXMLAttribute() function was found and corrected. |
EDI Standards Additions and Correction
- The Redix EDI database, was updated and corrected, specifically dealing with composite data elements. |
- A bug found during importation of a Redix XML Definition Database was found and corrected. |
Redix Format Converter Version 4.0
New Features: Full support of CSV Files--------------------------------------------------------------------------------
- Full support of CSV files as both Input and Output file types. |
- That is correct, files of only one record type, and a set number of items of variable length may now be used as input or output message definitions. |
i.e. |
- Additional details can be found in the rfc.hlp manual. |
Redix Engine Alternate DTD location support
- Added the ability for the Redix Engine to search the PATH of the local system, if a required XML DTD is not present in the Redix Program's directory. |
- If the user uses the following statement: |
- This feature is available for the Redix Engine, not the Redix GUI mapper. |
- Additional details can be found in the rfc.hlp manual. |
The Redix Command-line now accepts the OUTFILE name
- Now the user can specify the variable "OUTFILE" within their command-line configurations files, which allows them to specify the name of the output file to be created. |
- Additional details can be found in the rfcxml.hlp manual. |
Find and Replace Utility added to the Message and XML Definition Edit Screen Tabs
- Now by clicking on the |
|
|
- The user may then replace all occurrences of a text item within a tabular column, with a new text item. |
- Details found in the rfcxml.hlp manual. |
Corrections and Updates:
Sequence Characters
- The format of converted Sequence Characters has been corrected. |
- & will now convert to & when applicable (and vise versa). |
- > will now convert to > when applicable (and vise versa). |
- As well as all other acceptable sequence characters. |
- Additional details can be found in the rfc.hlp manual. |
Split() and AllocArray() Pointer Problem
- A pointer problem in the split() and allocarray() functions has been corrected to assure stability. |
button, the following screen will be shown: