Public Page

2022-06-28 Architecture Meeting Minutes

Owned by Paulette Reed
Last updated: Jul 05, 2022
4 min read

Public Page

Date: Jun 28, 2022

 

 

 

ANTITRUST STATEMENT

As participants in this meeting, we need to be mindful of the constraints of antitrust laws. There shall be no discussions of agreements or concerted actions that may restrain competition. This prohibition includes the exchange of information concerning individual prices, rates, coverages, market practices, claims settlement practices, or any other competitive aspect of an individual company’s operation. Each participant is obligated to speak up immediately for the purpose of preventing any discussion falling outside these bounds.

Agenda

  • Antitrust

  • Welcome/Networking

  • Meeting Minutes Review

  • Face to Face Meeting July 13 and 14

  • Review New API Guidelines and Help page for cieca.com

  • Meeting for CIECA Product Committees to review Vehicle is scheduled for June 29

  • Kickoff Party

Meeting Minutes

  • Antitrust Accepted

  • Meeting Minutes Review and Accepted

    • Dan likes to keep me on my toes and send me updates right before the meeting

  • Architecture Committee Face to Face Meeting

  • Party

    • Reviewed Dan’s excel document

      • Party Types and enumerations is to have plural array names

      • CustomElements and OtherInfo is two different ways in the BMS to have named value pairs.

        • Propose we don’t have both of them in CAPIS

        • In the example we are reviewing we will keep CustomElements at this time, we may be able to remove this later.

      • Last week we reviewed, and we had 17 different Party content models and we want to bring to 1, by allowing all optional party properties under party.

      • ID Infos is a named value pair

  • Reviewed AdminInfo in BMS

    • There are 65 Parties

    • The CAPIS project will work on the most common parties (InsuranceCompany, Insured, Owner, Claimant, InspectionSite, RepairFacility, VehicleLocationSite, LossLocationSite)

    • We will do Zero Based budgeting approach where we will work on the most common and then allow the Product Committees to add the additional properties they need.

  • Reviewed Assignment Test Instance Study

    • Bundling was used with ClaimInfo and VehicleInfo to have effect of using smaller schemas comprised of things that is used.

    • OtherParties is equal to Excel we just looked at.

      • This reflects one model of Party instead of 17.

        • Optional fields instead of different instances with different properties.

    • Insurance Company using Party

      • New capability of draft 2020 12 of JSON schema where email is string and format is email, confirms this is the best idea instead of CIECA being in the business of managing regular expressions for email.

    • PII indicator for Privacy would be a good additional field for Party Object.

    • Address - How will we handle a Bill to Address and a Ship to Address.

      • BMS had the communications aggregate that had a type, and we should have a similar structure for addresses to show the type.

      • Doing an array with addresses, array, and have a type added that will be a new code list to show what type of address.

    • IDInfo Array

      • idNums is requested to be singular so we have a one-to-one relationship between idQualifierCode and idNum.

        • TaxID

        • EPAId

        • BarId (funny thing here is that with the Style Guide approach of treating acronyms just like words for camelCase purposes, these would be “taxId”, “epaId”, and “barId”)

        • AirQualityNumber

    • CustomElements or CDF (Customer Defined Fields) or UDF (User Defined Fields)

      • In the BMS we have named value pair

      • In JSON we can use additional properties

      • If a new property is needed, it is good to bring to CIECA and get the properties added to the schema. If you work for a company that does not want to share properties, the additional properties can be used.

      • We will have additional properties set to true

      • Custom Elements if they do not need to be grouped, it does not need to be an array and be an object

      • property names can have spaces because they are quoted “ “ strings.

  • Presenting the vehicle to CEICA committees tomorrow

    • We have about 14-20 people from other industry segments attending the meeting

 

Thanks everyone great meeting, one more virtual meeting before our in-person meeting.

 

Action items

Decisions

  1. BMS Code List for Options will not be changed to match the CAPIS

 

Participants

  • Paulette Reed

  • Andy Bober

  • Dan Webster

  • Paul Barry

  • Jody Prather

  • Brad B

  • Jeff Schroder

  • Mike Hastings

Participants in the meetings are noted for your information.  If you have questions on the committee’s activities, please contact a recent attendee. https://cieca.atlassian.net/wiki/spaces/ARCH