On-Premise Installation and Configuration

Claim Insight Components

Claim Insight is a SpringBoot application with the MongoDB database back-end.

Claim Insight can be installed as a standalone SpringBoot application.

If you use Microsoft Azure cloud, you can also install Claim Insight from our image on Azure marketplace. In this case, you can follow regular Azure VM provisioning steps and skip all the installation steps below.

MongoDB Configuration

Claim Insight automatically manages its database. You do not need to perform any setup or fine-tuning tasks.

Upon its first startup, Claim Insight will automatically create the database and all of the database artifacts.

A database can always be recreated from your X12 EDI and/or NCPDP files. Te Claim Insight’s database could be treated as an ephemeral data store. It is important to have backups of your source files.

By default, a local instance of MongoDB will be installed as part of the Claim Insight installation.

You can also use a hosted MongoDB service, such as MongoDB Atlas. Simply provide an appropriate MongoDB URL as part of your installation process.

Requirements

Claim Insight can be installed on any Linux or Windows server.

Here are the requirements for the host VM:

  • RAM: 32 GB minimal, 64 or higher is recommended

  • Disk space: 200 GB or more

  • Cores: at least 4 processor cores

Software requirements:

  • MongoDB: 4.7 or higher (if using an external MongoDB instance). MongoDB Enterprise is recommended.

Installation Steps

  • Download Claim Insight zip file from URL provided by Healthcare Data Insight

  • Unzip the file into a folder of your choice

  • If you configured an external MongoDB instance, define your connection parameters in the application.properties file, e.g. spring.data.mongodb.uri=mongodb://mongo:27017

  • Run clinisigh install. This will install the application as a local service

The application will run on port 80 and port 443 by default. You can configure application parameters in the application.properties file by modifying appropriate SpringBoot properties.