openIDS Work Group - 9/9/24 -Meeting Minutes and Recording

A remote meeting of the openIDL Project's Open Source Data Standard Work Group was held   Monday, September 9, 2024 at 8:30am Pacific/11:30am Eastern, via LFX zoom.

The following attendees were present:

Peter Antley (AAIS)

James Bamberger (AAIS)

Sean Bohan (The Linux Foundation)

Jeff Braswell (open

Amanda Brine (AAIS)

Rob Clark (Cloverleaf Analytics)

Josh Hershman (openIDL)

Cory Isaacson (reThought Insurance)

Catherine Myers (reThought Insurance)

Lanaya Nelson (openIDL)

Michael Payne (AAIS)

Mike Puchner (AAIS)

Andrew Regis (AAIS)

Ken Sayers (AAIS)

Michael Schwabrow (Cloverleaf Analytics)

Nathan Southern (The Linux Foundation)

Jennifer Tornquist (AAIS)

Greg Williams (AAIS)

Introductory Thoughts/Central Objective

openIDL ED Josh Hershman opened the meeting and welcomed attendees.

The chief purpose of this meeting - a precursor to the biweekly OSDS meeting series - was a special presentation by Cloverleaf Analytics of their insurance data model for usage consideration by the work group.

Ken Sayers then acknowledged Jenny Tornquist as the assigned leader of the meeting series. Ken also introduced Rob Clark of Cloverleaf, who presented one of two candidate-based models that the group is considering as the basis of the data standard it will develop. The Cloverleaf data model is based on the OMG-P&C model with some extensions.  Ken noted that another meeting (on Thursday 9/12) will evaluate the Lloyd's data model, compare/contrast this with Cloverleaf, and choose the most effective one for the work group.

Cloverleaf Data Model Demonstration - Rob Clark

Mr. Clark made the following high-level points about the Cloverleaf Data Model:

High-Level Explanatory Notes:

·      The central amalgamation is based on the OMG (Object Management Group) working model

·      It OMG as a base model, modified to load source data from multiple client organizations

·      This explains the policy source IDs - each of which identifies a specific policy coming from a specific customer.

·      The account ID was created because some companies have (for instance) multiple auto policies, multiple homeowners policies, etc.

·      The product source ID identifies which insurance product it is.

·      'Event Number' - event 1 signifies the creation of the policy, event 2 amendments or endorsements to the policy, event 3 cancellation of the policy, event 4 reinstament of the policy, etc. etc.

Mr. Clark then broke down three areas and how Cloverleaf handles them. Policy, Insurable Object (which is the Risk),  and Claims - and elaborated further on these.

Mr. Clark affirmed that this is all defined in create table statements; they have it all in a DDL statement in SQL; the DDL is fully documented with diagrams. They also have it in spreadsheet form, where each one of the tables is a spreadsheet,with a description, an example of what it is, etc. With explanations of every field, default code tables, etc. You can set up what code you are expecting in a given field; it is easy to validate against this.

-There are two different models - model 3 & model 4. Model 3 - the focus of this discussion -  has ~ 126 tables in the underlying model discounting any relational tables that may factor in that Cloverleaf doesn't supply wrt source data, but not many relational tables (10-15). In terms of the ODS, a number of the tables are further broken out into a larger number.

Action Items:

Cloverleaf Analytics - share input tables and DDL with group. 

Jenny Tornquist: Lead an email thread with questions from the group, and direct/field them to Rob Clark.

Open