Overview
The following list provides an overview of the integration points that are available for exchanging data with Policies. The list is sorted in alphabetical order.
Click the triangle in front of the name of the integration point to reveal available operations. Click the name of the integration point to go to the description page of the integration point. |
Access Tokens
POST |
|
POST |
|
POST |
|
Activities
|
|
|
|
|
|
|
|
|
|
|
|
Oracle Health Insurance supports a generic activities API and a specific activities API. |
The generic activities API supports the standard generic operations.
Oracle Health Insurance also supports generic APIs on
-
/generic/groupaccountactivities
-
/generic/basefinancialobjectactivities
-
/generic/groupclientactivities
-
/generic/financialtransactionsetactivities
-
/generic/policyactivities
-
/generic/connectorconfigurationactivities
-
/generic/globalactivities
.
These are all subsets of the data returned by the generic /activities
API.
Apply Registrations
|
|
|
|
Banks
The generic banks API supports, in addition to the standard generic API operations, the GET
and the PATCH
operation on /generic/banks/key/{key}
.
This enables retrieving and updating a bank based on its code (the key).
Base Views
|
|
|
|
|
|
This a long running operation through REST. See, "HTTP API/IP Concepts" chapter of the Developer Guide for more information on the general concepts of these operations. |
This integration point can display PII data in an entity using the property ohi.baseview.exclude.pii
.
A POST
request on http://[hostName]:[portNumber]/[api-context-root]/generic/baseviews/search
retrieves information about the generated base views.
Connector Configurations
|
|
Task Processing
|
|
|
|
|
|
The /generic/tasks
API supports only search and retrieval operations.
Credentials
|
|
|
|
|
|
|
|
|
|
|
|
Data Sets
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Data File Sets
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The generic datafilesets API supports, in addition to the standard generic API operations, the GET
and the PATCH
operation on /generic/datafilesets/key/{key}
.
This enables retrieving and updating a datafileset based on its datafileset code.
Data Replication
|
|
|
|
|
|
|
|
Data Masking Configuration
|
|
|
|
Dynamic Logic
|
|
|
|
|
|
|
|
|
|
|
|
|
Invalidates all dynamic logic. |
|
|
Enrollment Files
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Extract
|
|
|
|
Enrollment Status Response
|
|
Financial Messages
This integration point sends a notification message to an external system once the financial messages for a financial transaction set are written to the data file (see Generate Financial Message).
The financial message data file can be downloaded by using the "Get details of a data file" request from the Data File Sets.
Group Clients
|
|
|
|
|
|
|
|
|
|
|
|
The generic group clients API supports, in addition to the standard generic API operations, the GET
and the PATCH
operation on /generic/groupclients/key/{key}
.
This enables retrieving and updating a group client based on its code.
Group Hierarchy
|
|
|
|
|
|
Key Stores
|
|
|
|
Macro Integration Point
|
|
Non-Entity Cache
|
|
Notes, Group Account Notes, Group Client Notes
|
|
|
|
|
|
|
|
|
|
|
|
Group Account Notes |
|
|
|
|
|
Group Client Notes |
|
|
|
|
|
OAuth2 Client Configuration
|
|
Objects
|
|
The following options are provided as query parameters to the above endpoint:
-
includeDynamicData
-
withSerialization
Organizations
|
|
|
|
In addition to the standard generic API operations, the generic organizations API supports the GET
and the PATCH
operations on /generic/organizations/key/{key}
.
This enables retrieving and updating an organization based on its code (the {key}).
Outbound Integration Points
|
|
Persons
|
|
|
|
In addition to the standard generic API operations, the generic persons API supports the GET
and the PATCH
operations on /generic/persons/key/{key}.
This enables retrieving and updating a person based on its code (the {\key}).
Policies
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Policy Accounts
|
|
|
|
Policy Account Transactions
|
|
|
|
|
|
The generic policy account transactions API supports, in addition to the standard generic API operations, the GET
and the PATCH
operation on /generic/policyaccounttransactions/key/{key}
.
This enables retrieving and updating a policy account transaction based on its authorization code (the {key}).
Policy Account Transaction List
This integration point creates policy account transactions from a data file. It requires sending in a data file and loading the file through the Load Policy Account Transactions activity.
Policy Enrollment Events
|
|
Policy Update Request
|
|
|
|
|
|
|
|
Properties
|
|
|
|
|
|
|
|
|
|
|
|
Providers
Individual Providers |
|
|
|
|
|
Organizational Providers |
|
|
|
|
|
Providers
Individual Providers |
|
|
|
|
|
Organizational Providers |
|
|
|
|
|
Purge Policies
- NOTE
-
The use of this resource in a production environment is strongly discouraged, as it may cause having financial messages in the system without the originating policies and policy changes.
|
|
|
|
Reference Sheet Lines
|
|
|
|
|
|
Registrations
The registration import is a long-running operation, a global activity which processes a data file.
Apply Registrations |
|
|
|
|
|
Process Registrations |
|
|
|
|
|
Relations
The generic relations API supports, in addition to the standard generic API operations, the GET
operation on /generic/relations/{id}
and /generic/relations/key/{key}
.
This enables retrieving a relation based on its id or on its code (the key).
Replication Entities
|
|
|
|
|
|
Replication Events
|
|
Revert Policy
|
|
|
|
User Information
|
|
`POST |
|
User Provisioning
|
|
|
|
|
|
Workflow Event
The application sends out a "fire and forget" task event when a policy pends.
See Policy Workflow Integration Point (Fixed Payload) and Policy Workflow Integration Point (Configurable Payload).
Write Policies
|
|
|
|
|
|
Policy Update Requests
|
|
|
|
|
|