<< Click to Display Table of Contents >> Navigation:  Database > Background

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 Authorizer 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 Authorizer uses two database tables:

oA header table: EDI_AuthorizerHeader.

oA detail table: EDI_AuthorizerDetails.

 

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 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 Authorizer application provides the "Data Import" option. This allows the user to import the request data to a database while printing or imaging requests (see Processing a Authorization Request and Printing Authorization Authorization Requests). Under "Screen" mode, data import does not work since this can interrupt the viewing of EDI Authorization Authorization Requests at any time; this might lead to incomplete data import.

 

Note: The image file will be created based on the pre-defined settings. Read more in Doing Image Setup.

 

The "Data Import" 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.

 

 

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