Public Page

2022-09-06 Architecture Meeting Minutes.

Owned by Paulette Reed
Last updated: Sept 20, 2022
2 min read

Public Page

Date: Sep 6, 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

  • Network/Welcome

  • Review Previous Meeting Minutes(s)

  • CONNEX Next Week

  • Review Homework

  • Review Jira Board

Meeting Minutes

  • Antitrust accepted

  • Meeting minutes reviewed and accepted

  • CONNEX is scheduled for next week and Dan, Mike and Andy will all present information about CAPIS at the Annual Meeting.

  • Reviewed Homework/Action Items

    • Dan showed his screen and the validation work that he completed.

    • Mike showed the work he did on part info (10 objects, 65 properties and 12 Code lists)

      • Worked on Phone Number

      • Changed instance docs to validate Dan’s scripts would work.

  • October API release

    • We need to focus on the priority for the release, we continue to add more to the code for review. An example is last week we added contact info, and there was time allocated to claim info that could have been used for the API work. We need to decide what is the minimal content that we can have in the release for October and be viable. This is the first iteration, there will be many updates and changes needed when more partners start working with the API standards.

    • Is schemas a minimum viable or do we need API spec?

      • We need to provide an Open API Specification, the first release could be a stair step, you know, steppingstone, but we need an API.

  • Decided to do Claims Save API

    • Looked at the BMS to see what was in Claims Save message and everyone aggreged that it had Claim, Parties and Vehicle and would be a good API with the schemas we worked on.

    • We write Jason schemas. We have the NPM package that turns that into a YAML schema that can be dropped right into a open API bag. So, to some extent you've got the skeleton of a open API spec right there, but it doesn't have any endpoints or Methods.

      • Claim Save has Add/Delete/Change for all the verbs of a rest API

  • Work Session

    • Last 20 minutes was spent reviewing the code and doing comparison of the work done and getting everything checked in and everyone in sync.

Up Next

  • Face to Face work Session at CONNEX

  • QA

Action items

Decisions

 

Participants

  • Paulette Reed

  • Dan Webster

  • Phil Martinez

  • Mike Hastings

  • Andy Bober

  • Paul Barry

  • Jeff Schroder

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