2023-02-21 Architecture Meeting Minutes

Public Page

Date: Feb 21, 2023

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

Network/Welcome
This meeting is subject to the terms of our anti-trust statement shown here. In addition, this meeting may be recorded.
Review Meeting Minutes
Review Contact/Party/Person/Company Examples
Review List of ID qualifiers being flattened examples.

Meeting Minutes

Antitrust Accepted
Meeting Minutes Reviewed/Accepted
Phone Number
- Google Phone Number format
  - Google uses a Semi Colon to break up the extension from the number.
- Country Code can’t be any 10 or 100 Series numbers.
- Russia has no 70 or 700 series numbers.
- Google Consensus tool
- Dan Shared links
- A simple concept to Phone Number is A Country Code / Phone Number / Extension
- In the BMS format we pass the + if we want to send the country code, a number without a + would signal the country code is not sent.
  - The constraints of the BMS may cause complexity in implementation with customers that are not using the pattern.
- CAPIS RegEX is not working in the current build.
- CIECA CAPIS format needs to be the standard that best works for the industry to send the data, we will not focus on how it is displayed to the user or the validations that a system will use.
- Send email to the CIECA Members asking them how they do the JSON phone numbers when integration with customers to get a bigger view on phone numbers.
ID Discussion - Do we want to have IDs broken into individual properties (User ID, Company ID, Account number) or Name Value Pairs?
- If we break out to individual properties, we will have 47 properties to include all the BMS name value pairs.
- If we convert from the BMS the way it is done, we will have the named value pairs.
  - In CAPIS we have both versions where we have the ID as a pair with ID properties Name and Value, but we also have Company ID.
- Different Types of IDs, we have reference ids that goes with the time of the document and the user sending the transaction,
  - Request UUID is used for the response to tie back to the request.
  - Partner Key is used to verify a partner for a transaction.
  - At this time, we don’t have a Document Info, but we may need things at this level.
Draw members to the Architecture team to get more involvement of setting up the standards for CAPIS on these topics.

Great Discussion everyone

Up Next

Network/Welcome
Antitrust
Review Meeting Minutes
Work on Email to call out to Tech Members

Action items

Decisions

Participants

Paulette Reed
Jeff Schroder
Mike Hastings
Dan Webster
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