• Set up trading partners, communication methods, encryption and so on
• Automatically checking for new files in pre-determined intervals
• Incoming EDI files are read, examined, and logged.
• TA1 and 997 acknowledgements that are automatically created and returned to the sender if needed.
• Staff notification through email announcing the arrival of new files.
• Email notification to the sender with HIPAA compliance check results.
• File management, where files are moved to appropriate folders for further processing with the other parts of the HIPAA Suite.
• Options to process EDI files automatically without human intervention
• En- and Decryption of EDI files that go over the public internet. Supports PGP and other common encryption methods.

With the HIPAA Communication Center, EDI files can be received in the following ways:

• Use of the HIPAADirectSubmit Web Portal for receiving and delivering EDI files. This approach gives great independence and it is very cost effective.
• Signing up with a VAN (Value-Added Network), and setting up a mail box for incoming and outgoing EDI files on the VAN's server.
• Setting up an FTP (File Transfer Protocol) server locally and allowing trading partners to deposit their files in an inbox., and remove files from an outbox folder.
• Using email attachments. Email has many advantages, as it is ubiquitous and simple. Encryption and data security solutions are widely available. Routing parameters are not important, the email is sent straight to its destination.

The HIPAA Communication Center is designed to facilitate and administer EDI exchanges through the following basic workflow:

1. Email accounts are scanned for new files, and attachements are extracted and placed in the inbox
2. VAN accounts are checked for new files and those files are placed in the inbox
3. Through FTP, one or multiple EDI file(s) are deposited by trading partners in the Inbox.
4. Encrypted files are decrypted. PGP software can be integrated
5. HIPAA Communication Center scans the inbox in predetermined time intervals.
6. If files are detected, those files are then analyzed for their HIPAA compliance and a report is generated.
7. Several methods of encryption are supported.
8. The sending Trading Partner is detected and the rules for that partner are loaded.
9. A 997 EDI acknowledgement file is then produced and sent back to the Trading Partner. Warning of EDI errors are also generated and sent back.
10. A log file, with the time and date of receipt and any warning message, is created.
11. Office personnel receive an email message with the basic information about the new file.
12. The file is moved to a specific directory for further processing.
13. The Inbox is "cleaned" automatically.
14. "Bad" Files can be rejected according to established rules. Those files are placed in a suspense folder
    
15. Many Transactions can be autoprocessed.

Fig1 The FTP Inbox is checked and files are processed.

How are communication rules established?
When Trading Partner relationships are set up, the rules for communications with them are established with the following interface:


Fig2 The Trading Partner screen. (Click to enlarge).

Basic Setup includes establishing the FTP inbox, outbox and location for control files.


Fig. 3 Basic setup

2. A log is maintained for all the processed files and analysis results. This information is stored in the Transaction Log