Callout Rules
By defining callout rules the services provided by external components can be called from within the authorization processing flow. The callout is triggered during the processing of an authorization when it encounters a callout rule. Essentially a callout can be set up by specifying the definition of the callout interface plus the conditions under which it is to be executed; together they form the callout rule. The callout interface works by sending a web service request and receiving and processing the response. By using the flexibility of dynamic logic, any externally authored XML schema definition can be adhered to.
The setup of callout rules is a combination of functional setup in a UI page of Oracle Health Insurance Authorizations and technical setup. [1]. The following fields are available as a part of the functional setup.
| Field | Description |
|---|---|
Code |
The identifying code of the callout rule (this code is used in the specification of technical configuration parameters. Refer to Property Management for more information.) |
Description |
The description of the callout rule |
Condition |
The dynamic logic condition that is executed to determine if the callout rule must be executed for an authorization |
Function |
The dynamic logic function that is executed to handle the callout |
Display in UI? |
Should the authorization callout history for the callout rule be shown in the UI? |
Enabled? |
Is the callout rule enabled for execution? |
Because response logic is always specified, the external component is required to send back a response including a message body (for example, not just a HTTP 200 status code).