In each program, there is a "Build your own query" under the Database menu. The interface is similar to Microsoft Access and allows non database experts to formulate complex queries.

The EDI Editor parses EDI files but only to show their structure. Each segment will be on its own line, the segment identifier will be in color and the element and sub-element separators are highlighted. You can change the data in the file by editing and saving the file, however there is nothing in the EDI Editor to prevent you from making a file unusable or syntactically wrong.

Yes, we have 5 levels of COB in the data export. These must all be added to the database field configuration to be active.

• Go to Database -> Connection and Data Fields. The Detail table contains the COB Information. 

• Click the “Select All” button to be sure all fields are added. 

• Then click “Test Configuration”,

• Finally click “Save Field Configuration”.

HIPAAsuite programs store the settings in the registry of the user who is logged in. SSIS or similar scripts use system accounts for the execution of tasks. In this case, the problem is that the HIPAAsuite program is not configured for this user account (SSIS).

There are a few solutions:

1. Run the scripts under a user that has the program configured.

2. Log in under the system account being used and configure the program.

3. Go to the menu item Log --> Daily log and look up what happened. If the program can’t find the configuration, then most likely it is executed by a user under which it was not configured. 

4. There is also a tool to migrate the setup of a single user into the setup for all users. Go to Help --> Settings Manager to this migration. (Administrator privileges needed).

There are several ways to create a Data Transformation process. One way is a SQL script using the database's innate programming language. The AutoID column is used in the detail table as the foreign key. This means that after the header record is written, we need to ask the database for the ID it just assigned to the new record. Then we can take this ID and write it in the detail record.

Here is a sample SQL script that populates HIPAA Claim Master's tables with data from a fictitious other table. Just three fields are used to show the principle.

Create a Batch script that changes the registry entries for the table names and run this script before you import your files. Then, create another script to change it back to the default value.

Here is an example:

Registry before running command:

Command to change Enrollment Header value reg add "HKEY_CURRENT_USER\Software\HIPAAEnrollmentMaster\Database Server" /v EnrollmentHeader /t REG_SZ /d EDI_Members2 /f

NOTE: This has to be executed as Administrator.

Registry after executing command:

The optional EDI Exchange module tracks every file that is processed in a database in a table called TransLog.

EDI Exchange checks before processing that the product of trading partner ID and filename is unique. If the file has been processed before, you will receive a message and the file will be moved to the Suspend directory.

NOTE: Without EDI Exchange, there is nothing preventing you from loading the same file multiple times.

All HIPAAsuite programs store the settings in the registry of the user who is logged in. The connection information and some other operative settings are stored in the Windows registry. Each user has their own hive and thus has to configure the database connection anew.

We have a tool to migrate the settings from a specific user to the system administrator, thereby allowing any user to use the established settings. 

• Run the program as Administrator. 

• Go to Help -> Settings Manager and set the program to run from global settings.

There are two possibilities:

• The file was processed twice:

  • Even though we prevent the processing of the same filename by the same trading partner, if the file is renamed, the claims will be imported and duplicated.

• The claim was submitted twice by the provider:

  • This would create identical claims with different file names and maybe a different Claim Filing Code. Such as:

    • Original

    • Resubmitted

    • Change

There is an option to not display line level provider (Rendering) when it is the same as on the claim level.

Confirm if this is turned on/off under Setup -> Specific Options