Generate Reporting Views (Deprecated)

This section describes deprecated reporting views. A future release will drop them. Instead, base view generation is now part of the application itself. There is no need for a runnable .jar file.

Oracle Health Insurance applications have dedicated database schemas for reporting views. Reporting views are a logical presentation on the tables, resolving details such as dynamic field definitions, languages.

The views must regenerate after:

  • An upgrade of an Oracle Health Insurance application.

  • Change in dynamic field or dynamic record definitions.

  • Using the Configuration Migration utility.

Running the Generator

The generator is a .jar file. The way to run it is:

$ java -jar ohi-views-generator.jar -h
usage: java -jar ohi-views-generator.jar <options>
 -c <configFile>               Config file
 -d <definitionsDir>           Directory containing the XML definition
                               file(s)
 -e,--env <environment name>   Name of target the environment
                               configuration
 -h,--help                     Show usage information and quit
 -n                            Do not execute the SQL on the database
 -o <outputFile>               The file the generator writes SQL
                               statements to
 -s                            Do not regenerate base views

The config file is mandatory. Use ohi_create_views.cfg.template to create this file. Omitting the -d argument will not generate functional views. However, it is possible to provide the directory containing the functional view XML definition files when using the argument.

To run the generator once and apply the result to multiple databases, write the SQL statements to a file by using the -o argument. Note that this will still execute the SQL unless using the -n flag.

The config file defines which views are confidential (that is, OHI_<APPLICATION>_CONF_VWS_ROLE grants access to which views).

For example, Claims marks the following views as confidential (because of PHI data):

  • CLA_CLAIMS_V

  • CLA_CLAIM_LINES_V

  • CLA_BILLS_V

  • OHI_AUTHORIZATIONS_V

  • CLA_MEDICAL_CASES_V

  • CTR_CLAIMS_V

  • CTR_CLAIM_LINES_V

  • CTR_BILLS_V