Exporting the Data

The HIPAA Claim Master does not come with a database. But it can link to any ODBC- or OleDB-compliant database. Database integration is a component of the HIPAA Claim Master and can be licensed as add-in.

Most businesses that do HIPAA transactions have a database engine on their premises. Microsoft SQL Server is probably the most widely used business database; Oracle or IBM database also have broad acceptance. The open source and free database MySQL finds more and more acceptance in the business world and is great for developers.

The HIPAA Claim Master uses two database tables for the claim information:

a claim header table
a claim detail table with the line item information.

Scripts are provided to create these tables for some database types. You might have to modify the scripts to suit your actual taste of the SQL language.

Once these tables are created, claims from EDI files can be loaded into this database. Your application can take the claim information from there and you can run your business logic on these records. The HIPAA Claim Master can in turn read the database record and re-create the claim image from the database. In the next implementation you will even be able to create an 837 EDI file from those database records.

The HIPAA Claim Master lets you set up two connections, to a test and to a production database. The deciding factor on which database is used is the ISA_15 data element of the 837 file. This indicator is either a "P" for production or "T" for test. If you need only one database, set up both connections identically.

The "Data Base" menu

The sequence of actions to setup the data export is the following:

How to Save Data to the Database

The HIPAA Claim Master provides the "Data Import" option. You can import the claim data to a database while printing or imaging claims (see Processing an Electronic Claim, Printing Electronic Claims). In the "Screen" mode, the data import will does not work since you can interrupt the viewing of EDI claims at any time and this might lead to incomplete data import.

Notice: The image file will be created based on the pre-defined settings. Read more in

The "Data Import" check-box

The data is exported once the user clicks on the "Run" button. The data is written to the database once the "Run" button has been clicked and only if the "Data Import" checkbox is activated.

The "Processing Results" window will display notification about data export.

The "Processing Results" window

Now you can browse exported data.

No questions yet.

Publish modules to the "offcanvs" position.