Term a Group

This sample use case explains the use of macros to term a group. Termination of a group implies the end date of all the group account product availability as of the termination date. Also, terminate the policy enrollments linked to the group as of the term date. To configure such a macro, set up the definition as follows:

Table 1. Term Group Macro Definition

Field	Configuration
Code	TERM_GROUP
Description	Terms the group account product availability and policy enrollment products linked to the group as of the term date.
Type	Oracle Insurance Gateway Integration
requestContext	Group Client
Access Restriction	-
Page Template	-

The macro requires the term date as a parameter.

Parameter setup is necessary only if the intention is to start the macro from the user interface. The user interface displays the correct input form elements depending on the parameter configuration—for example, a date picker or a list of values to choose from.

The following parameter configurations ensure that a field of type date, labeled as Term Date, is displayed on the user interface:

Table 2. Term Group Parameter Configurations

Field	Configuration
Usage Name	termDate
Display Name	Term Date
Data Type	Date
Mandatory?	true
Multi Value?	false
Pick List	-
Filter	-

This macro is based on the Oracle Insurance Gateway Integration, which means that all the business logic, that is, term group account product availability, and policy enrollment are performed by an Oracle Insurance Gateway integration. Such integration can be invoked by sending the following POST request:

http://[requestContext:host]/exchanges/integration/termgroup

The user can start the macro from the user interface page or directly make the following request to the Macro Integration Point:

{
  "parameters": [
    {
      "name": "termDate",
      "value": "2022-01-01"
    }
  ],
  "macroDefinitionCode": "TERM_GROUP",
  "requestContext": "{ \"id\": \"26551\" }"
}

The macro integration point creates a macro history and starts the Oracle Health Insurance Integration. For the integration point to be able to start Oracle Health Insurance Exchange, the following additional setup must be configured:

Table 3. Additional Setup

Property	Value
ohi.macro.TERM_GROUP.endpoint,	http://[requestContext:host]/exchanges/integration/termgroup
ohi.service.OIG_INTEGRATION_TERM_GROUP.client.authentication	BasicAuthentication
Setup credential for OIG_INTEGRATION_TERM_GROUP	Credentials Integration Point

The macro integration point invokes Oracle Insurance Gateway integration with the following payload:

{
  "parameters": [
    {
      "name": "termDate",
      "value": "2022-01-01"
    }
  ],
  "requestContext": "{ \"id\": \"26551\" }",
  "links": [
    {
      "href": "refers to macro history",
      "rel": "subject",
      "httpMethod": "GET"
    }
  ]
}

Oracle Insurance Gateway can use the term date and requestContext information to first end-date policy enrollment products (by starting a bulk update activity) and then send a patch request on the group account to end availability of all the group account products as of the term date.

Oracle Insurance Gateway can update the macro history dynamic fields, records and status (dynamic field) to supply the execution requestContext.