Database Access

As Oracle Health Insurance Cloud Services are a secure SaaS offering, SQL access or database query capabilities, for example, a query for configuration details or data extraction are not available. If there is a need to get details from the database, the following approaches are suggested to meet the requirements or use cases:

• Query Oracle Health Insurance Resources using the Oracle Analytic Server

• Query Oracle Health Insurance Resources using the REST API

If the above approaches do not meet the requirements, please log a Service Request on My Oracle Support.

Query Oracle Health Insurance Resources Using the Oracle Analytic Server

With Oracle Analytics Publisher, users can use SQL query instructions to visualize, explore data and make ad-hoc reports against the base views. For more information refer to Create a Report on Base Views.

The use of Oracle Analytics Publisher is limited to the Base views provided for Oracle Health Insurance components available in your Cloud Service.

Query Oracle Health Insurance Resources Using the REST API

This section explains how to use REST API to query resources. Some examples and scenarios are listed below.

Scenario: Check the Status History of a Claim

To check the status history of a claim using API, do the following:

Request

HTTP Method	POST
Base URL	{apiurl}/generic/claimstatushistory/search
Content-Type	application/json

Request Body

{
"resource": {
"q":"claim.code.eq('CALC1')",
"orderBy": "creationDate",
"offset": 0,
"limit": 200,
"totalResults": *true*
},
"resourceRepresentation":
{
"fields":"all"
}
}

For more information on Status History of the Claim, refer to Claim Task Processing Performance in the System Administration Guide of product documentation.

Scenario: To Update the External Message Code

To update the external message code using API, do the following:

Request

HTTP Method	POST
Base URL	{apiurl}/generic/message/search
Content-Type	application/json

Request Body

{
"resource":
{
"q": "externalCode.eq(null).and.severity.eq('F').and.system.eq(true).and.active.eq(true)",
"totalResults": "true"
}
}

Scenario: GEN-ORA-ERR Nested Exception - Cannot Allocate Resources to Applications

To perform API queries when the nested exception occurs, do the following:

Request

HTTP Method	POST
Base URL	{apiurl}/generic/datasetprocesses/search
Content-Type	application/json

Request Body

{
"resource":
{
"q": "result.eq(null)"
}
,
"resourceRepresentation":
{
"fields": "all"
}
}

Other Possible Scenarios

Scenario: Get an overview of the current configuration

• Solution: Use OHI Insurance Gateway (OIG) to run an activity in OHI that creates an extract file with configurable content in a configurable format. This file can be retrieved through the file Integration Point (IP).

Scenario: Desire to build certain dynamic logic by first prototyping the queries in SQL

• Solution 1: Use the dynamic logic test API to prototype dynamic logic queries using the Domain Specific Language (DSL). For more information refer to Test Dynamic Logic Integration Point.

• Solution 2: Use the dynamic logic data retrieval DSL to retrieve data and store it in Dynamic Records when the unit of dynamic logic is executed. This way results can be viewed and establishes a build, execute, or review cycle that can be used for the development of dynamic logic.

Scenario: Extracts on an ad-hoc basis to obtain data for upstream and downstream systems or services

• Solution: Use the generic extracts API to generate feeds for downstream systems. For information refer to Starting the Extract Process.

Also, almost all salient data elements in Oracle Health Insurance Components are available via web-services. For example,

• Web services for point access and updates of objects.

• Restful query API which handles ad hoc data requests.

• DataFile services for Bulk Imports.

• Generic file extracts and BIPublisher configuration for bulk extracts.

• DataSync API and Event IPs for streaming changes and workflow events respectively.