Background

Navigation:  Database >

Background

Previous pageReturn to chapter overviewNext page

Most entities that process HIPAA transactions have a database engine on their premises. The most commonly used are Microsoft SQL Server and the open-source MySQL. Though the HIPAA 999 Master application does not come with a database.

 

HIPAA 999 Master uses four database tables:

oA implementation ack table: ImplementationAck.

oA transaction response table: TransactionResponse.

oA segment errors table: SegmentErrors.

oA element notes table: ElementNotes.

 

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 "Data Base" tab and options in the main window.

The "Data Base" 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 999 Master application provides the "Data Import" option. This allows the user to import 999 EDI files to a database. Under "Screen" mode, data import does not work since this can interrupt the viewing of EDI Implementation Acknowledgments at any time; this might lead to incomplete data import.

 

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

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.

 

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

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

 

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