The PostgreSQL component is the heart of CLAIMS Direct. It contains the XML for the entire data warehouse collection, processes updates from the primary, and functions as data source for the optional SOLR index.
|Storage Capacity||6TB (SSD preferred)|
|Operating System||RHEL 8, CentOS 8, Amazon Linux 2|
yum -y install \
|IFI CLAIMS Repository|
Amazon Linux 2
Note: This installs EPEL and the PowerTools repositories.
Some CLAIMS Direct loading and maintenance code utilizes the PostgreSQL perl extension (plperl) as well as a heavy reliance on the libxml2 XML parsing library. IFI CLAIMS has produced a patched release of libxml2 as an RPM. It is highly recommended to update libxml2 from the IFI CLAIMS software repository. For additional distributions, please contact email@example.com.
PostgreSQL Schema and Tools
In an effort to further streamline CLAIMS Direct PostgreSQL schema versioning, we are introducing a schema and tools package into the CLAIMS Direct
yum repository. The new package offers the main CLAIMS Direct database schema as well as the supporting
users database to support deployment of on-site web services. The new package can be installed as follows:
The package contains the SQL needed to create the database(s) supporting PostgreSQL versions 9.2 - 10.x, as well as tools to check installation, populate the tables, and perform extracts. To create the databases, simply load the SQL via
psql into the instance.
In addition to the schema, there is a collection of tools to help determine instance loading feasibility, populating, bulk extracting, counts and sizes of tables, and more. All tools accept the same parameters with reasonable defaults for a Type-1 CLAIMS Direct installation.
Use this tool to test the viability of populating the newly created database. It runs a few simple checks.
You can use this tool to populate the initial data delivery. After unpacking or otherwise making the initial data available,
Note: This tool expects there to be a
This tool counts the rows in all tables in the main schema (cdws, xml).
|Analyze all tables in the main schema.|
Calculate the on-disk size of each table in the main schema.
Extract all relevant table data to