EDI Exchange is a module available in most HIPAAsuite EDI applications. It is an option that you can purchase for an additional cost. Some of our products, such as HIPAA Claim Master, process EDI files but do not receive or send EDI files to and from your trading partners. EDI Exchange is created to do that. EDI Exchange is designed for those organizations that have a large volume of EDI files, need more order and automation and adhere to tougher compliance rules. The EDI Exchange is an EDI pre-processor that handles FTP transport, encryption, HIPAA compliance check, trading partner management, etc. Outgoing EDI files can be checked for compliance; individual records that do not pass the check can be withheld.
HIPAAsuite products with EDI Exchange module have a main menu item called "EDI Exchange" with sub-menus to call the module's functions.
The "EDI Exchange" menu in HIPAA Enrollment Master
EDI Exchange performs the following functions:
| • |
Trading Partners Management — The following Trading Partner's parameters can be stored and transparently managed with the help of EDI Exchange: name, address, EDI identifiers, delivery methods, encryption parameters, FTP servers, CORE-Compliant server addresses and credentials, communication numbers and folders to keep files separated, special requirements specific to this trading partner. Read more in Setting up Trading Partners. |
| • |
File Transport — EDI Exchange has a built-in FTP client that can securely connect to your trading partner's FTP servers. If you employ your own FTP server, you can utilize the folder structure that EDI Exchange uses to manage incoming files, users, home directories and permissions so that your Trading Partners can drop off and pick up EDI files. Supported are: |
| • |
Secure Shell FTP or sFTP |
Read more in Using FTP Client.
| • |
Encryption — Many healthcare-related companies use encryption to cloak the content of their EDI files. The prevalent method of encryption is PKI (Private Key Infrastructure) that uses the product of two incredibly large prime numbers as cipher. EDI Exchange supports PGP (Pretty Good Privacy), the leader in PKI products as well as the open source GPG project with its Windows sub project PGP4Win. Both are implementations of the same encryption mechanism. Read more in Using Encryption. |
| • |
File Management — EDI Exchange uses a clear directory structure to store EDI files. The structure is based on root directories for incoming files, outgoing files, processed files and suspended files. Below these root directories, there are subdirectories for each trading partner and then each transaction set. Read more in Defining Root Directory and Initializing EDI Exchange. |
| • |
EDI Compliance Check — EDI standards are strict and precise; adherence to the standards is very important so that any organization can work with them regardless of their backend system software. EDI Exchange has a built-in compliance engine that checks incoming files for compliance. The engine also generates a report listing each problem with the exact location. Outgoing EDI files can also be checked and you have an option to withhold individual records that violate the rules. Read more in Checking EDI Files. |
| • |
EDI Control for Transactions — The EDI protocols have a few supporting transaction sets that are useful to the smooth functioning of EDI exchanges. They provide the sender with an instant feedback on receipt. The following transaction sets are available: |
| • |
997/999 Functional Acknowledgment |
| • |
277U/277CA Unsolicited Claim Status Response (in case of Claims) |
| • |
Logging — EDI Exchange has several logs that are instrumental to keep processing in order and allows to forensically investigate mishaps. There are three logs in EDI Exchange: |
