Overview

Base views are a set of database views, generated by the Oracle Health Insurance application, that correspond with the entity model of the application. These base views make the actual data model easier to work with by resolving both language sensitive field values and user defined fields.

The main use case of base views is to support Operational Reporting: the definition of low-volume, straightforward reports supporting the day to day operation of an OHI application.

Translation

Background

The data model of an OHI application provides the ability to store multilingual descriptions for many entities.

Take for example the entity Access Role: Some fields are not multilingual, those fields (a.o) are stored in the internal table OHI_ACCESS_ROLES_B:

  • ID

  • CODE

  • IND_ENABLED

Other fields are multilingual, those fields (a.o.) are stored in the internal table OHI_ACCESS_ROLES_TL:

  • DESCR

  • NAME

You can think of a _TL table as a detail table of a _B table: for a single record in a _B table, multiple related records exist in the _TL table, depending on the number of different languages used by the users of the system.

Translation handling in a Base View

A base views combines the fields from the _B and the _TL table.

So for the access role example above, the base view will have the columns:

  • ID

  • CODE

  • IND_ENABLED

  • DESCR

  • NAME

The multilingual columns show the value of the TL row with the language = OHI default language. The default language is picked upon installation. The base views do not depend upon the language settings in the User Preferences.

Extensibility

By defining dynamic fields and/or -records, the data model of an OHI application can be extended. The base views do expose those customer data model extensions as well. Either:

  • The base view includes the extensions right away. This is the case for single valued, non time valid, dynamic fields.

  • or a separate base view is created: This happens for time valid dynamic fields, multi valued dynamic fields and dynamic records contains the values.

See Base View Details for details.

Using the Base Views

The base views can be accessed using any SQL query tool.

Usage Guidelines

Querying the base views does put a load on the environment where the views run. Using the base views to query large amounts of data could lead to a performance decline of other tasks running on the same server. Therefore:

  • Pay attention to the volume (number of rows) that is accessed.

  • When volume is high, pay attention to the access path used and make sure indexes are used to speed up retrieval.