You are here:
Integration Procedure as Rating Procedure
If you calculate ratings for multi-instance insurance products or health plans, or if you use a third-party rating engine, use an Integration Procedure as a rating procedure.
For less complex products and plans, an expression set can function as your rating procedure instead. If you're not sure whether to use an Integration Procedure, see Rating Procedure Best Practices.
Integration Procedures can include multiple steps and multiple expression sets. Manage the data structure yourself using Integration Procedure tools.
If you have Integration Procedures from earlier releases, you can use calculation matrices and calculation procedures instead of lookup tables and expression sets.
When you're working with rating Integration Procedures, the two most important things to keep track of are:
-
Input JSON structure.
Examine this structure so you understand what's coming into your Integration Procedure.
-
Output JSON structure.
Set up an output structure similar to that of a expression set's output that can be parsed by the
InsProductService:getRatedProductsorInsProductService:repriceProductservice and mapped to the correct values in the product JSON.
Your Integration Procedure can also use a merge List Action to make multi-instance ratings possible, and can transform data with Omnistudio Data Mappers.
After you create your Integration Procedure, use the Simulator on the Integration Procedure Designer to test it. Enter the same data you used to test expression sets called by this Integration Procedure. The Integration Procedure simulation result should conform to PricingCalculationService.CalculationProcedureResults.
When you go on to test your rating procedure on a product, keep in mind that Integration Procedures don't work the same way on the product simulator as expression sets do.
Before you begin:
-
Consider using an expression set instead of an Integration Procedure. Integration Procedures can use more system resources, so use them only if the calculation is too complex for expression sets.
-
Create a product model.
-
Create all lookup tables required for this rating.
-
Create all expression sets required for this rating.
- Required Input in a Rating Integration Procedure
Each input JSON node in a rating Integration Procedure must includeparentProdKeyandproductKey. These two keys carry over as input to the expression sets called by this Integration Procedure. - Calculation Steps in a Rating Integration Procedure
An Integration Procedure that rates an insurance or health product includes at least one Expression Set Action, or it includes a Remote Action that calls the third-party rating engine you use to rate products. - Data Transforms in a Rating Integration Procedure
Transform data if necessary based on the format of the input JSON and the format of the results of the expression set or external rating engine. - Required Output in a Rating Integration Procedure
The output of your rating Integration Procedure needs to follow the same structure as expression set output. - Services that Call Rating Integration Procedures
When you create a rating Integration Procedure, think about what services call it. The services inform how you create the Integration Procedure and the structure of input and output data. - Integration Procedure for an Auto Insurance Product Rating
The product model underpins all the business processes used in a line of business. Services that price insurance products pull data from the product model, perform rating procedure calculations using that data, and then insert coverage and premium prices into the product model.
