Background

Most entities that process HIPAA transactions have a database engine on their premises. Some of the most commonly used are Microsoft SQL Server, Oracle, IBM, and the open-source MySQL. Though the HIPAA Claim Status Responder application does not come with a database, it can link to any Open Database Connectivity (ODBC) or Object Linking and Embedding Database (OleDB). This component is available as an add-on license.

HIPAA Claim Status Responder uses two database tables:

oA header table: EDI_ClaimStatusHeader.

oA detail table: EDI_ClaimStatusDetail.

Scripts are provided to create these tables for some database types. You might have to modify the scripts to suit your Structured Query Language (SQL) language.

The "Database" tab and options in the main window.

The sequence of actions to configure the data import is the following:

oSetting up Database Connection

oCreating Tables

How is EDI data imported to the Database?

The HIPAA Claim Status Responder application provides the "Import Data" option. This allows the user to import the claim data to a database while printing or imaging claims (see Processing an Electronic Claim).

5.2 csr import data

The "Import Data" check-box is in the main window.

The data is imported and written to the database once the user clicks on the "Run" button and only if the "Data Import" box is checked.

The "Processing Results" window will display a notification about the data import.

The "Processing Results" window after importing to the database.

After this message, the user can now browse imported data.