Docker Configuration

Claim Insight image is available from our docker hub’s repo.

You can run the Claim Insight container using docker compose or in any Kubernetes cluster.

This docker-compose file provides a good starting point for standalone configuration.

The default configuration includes a local instance of MongoDB. If you will be running your own MongoDB cluster to host the Claim Insight’s database (see below), you can remove the MongoDB service from the docker-compose file.

Follow these steps to run Claim Insight using docker compose:

  • Save your docker-compose file to the folder named clinsight.
  • Create a folder for the Mongo DB volume, it must be named “mongo_data”, e.g., mkdir mongo_data. If you want to use a different location, update the docker-compose.yaml
  • Navigate to the clinsight folder.
  • Run docker compose up -d from the clinsight folder.

The main URL for Claim Insight UI is http://:5080/clinsight/ui.

The API documentation is available at http://:5080/clinsight/api-docs

REST APIs are available at http://<your host>:5080/clinsight/api. For example, the URL for Claim API is http://:5080/clinsight/api/claims.

You can change the port by updating the port mapping of the Claim Insight’s docker container.

The app’s maximum Java heap size is set to 6GB, so the host VM should have at least 8GB, or 16GB if MongoDB is running on the same host.

You can lower the maximum heap size if you have low data volumes and few users. This can be done by defining the following environment variable in your docker-compose file:

JAVA_OPTS=-XshowSettings:vm -Xms512m -Xmx2g -XX:+ExitOnOutOfMemoryError

The —Xmx option defines the JVM’s maximum heap size. It is not recommended to go below 2G.