2023-03-14 Architecture Meeting Minutes

Public Page

Date: Mar 14, 2023

Agenda

• Network/Welcome

• Antitrust Statement

  • This meeting is subject to the terms of our anti-trust statement shown here.  In addition, this meeting may be recorded. 

• Review Meeting Minutes

• Work Meeting

• New Code List

• Work on CAPIS/Contact

Meeting Minutes

• Antitrust Accepted

• Meeting Minutes Reviewed and Accepted

• Dan will be on a two-week vacation prior to the April 19 Release

  • CAPIS Release may not be ready for April 19, we should wait until we have it complete before we release.

  • BMS has been mature, and the work can be completed, but with CAPIS we are in beginning stages and need to have a full valid concept in place before the release (for example) Contact.

  • We need to do QA for BMS before Dan’s vacation and we will release BMS changes April 19

  • 1/2 Day meeting will be March 31st.

• 1/2 Day Work Session for Architecture

• Approved New Code List to be added for Prior Salvage

• CAPIS Contact

  • In trying to flatten the Contact object, the communications were causing issues, that is where these new concepts came from was flattening communications.

  • Discussed Primary Phone Number

    • Is naming of Primary or Preferred an issue?

      • Andy does not see a problem with how it is named but wanted to point out the value of 1 property referring to the name of another one, is something JSON schema can do conditional validation based on fields. We could make the schema detect that if they try and reference something that is not there.

      • For naming Preferred is a good name because it removes the order for a secondary and what is next.

    • Jeff’s example is having preferred under Primary Contact

    • The example does not look at a contact different from a party. So, a party is a user, or a company and we are saying a user can contain a contact object, a user object can contain a contact object. If you are talking about a primary user or a primary party, that is different than the primary contact for a user.

    • Looking at a perspective of an Owner, Claimant and Insured as all being Parties and a UI may have a radio button for primary Contact. In the BMS the Preferred one is in the party; with the proposed CAPIS it is only helpful if we are using the whole Primary Contact Object as the flag.

    • Where the contact and we're saying, well, you might pull the contact information out of the party, but they're really different things.

      And so, and in fact you have a one to one between a party and it's contact information.

      And so, we have a one to many between a party and a contact information, but it's still OK. You're really looking for the primary party as opposed to the primary contact. So, it's mostly we're getting hung up in linguistics.

    • Amazon model uses array of contact's model.

    • Eliminate both communications and contacts and promote those child elements up to the top level in party.

  • Slack upgrade to Pro Version so we can see previous comments.

Great Discussion everyone

Up Next

• Network/Welcome

• Antitrust

• Review Meeting Minutes

• Continue with Contacts

Action items

Decisions

Participants

• Paulette Reed

• Dan Webster

• Mike Hastings

• Andy Bober

• Jeff Schroder

• Paul Barry

• Phil Martinez

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