Public Page

2021-06-8 Architecture Meeting Minutes

Owned by Paulette Reed
Last updated: Jul 13, 2021
3 min read

Public Page

 

      
   CIECA 500 Westover Dr  #11617; Sanford,  NC  27330 

 

Date

Jun 8, 2021

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 and Meeting minutes acceptance

  • Review Simplified Claim Info.

  • Work on FNOL JSON messages

  • Versioning CIECA API

Meeting Minutes

  • Antitrust accepted

  • Meeting minutes accepted

  • Reviewed the documentation being moved to GitHub so everyone could see the documentation that has been worked on so far. Mike recommended moving the VehicleInfo and DocumentInfo into another folder and getting these into common global types. He will help move these items around in GitHub.

  • ClaimInfo was reviewed by the team.

    • In the last meeting the PolicyInfo was said it could move up a level, however, it is a repeating element and was left at its level. The CoverageInfo is a repeating element of policyInfo.

      • PolicyInfo will be changed to plural

      • We have also started removing the info from the names, so policy and coverage will be policies and coverages.

  • Address here, can the sublet Address info be removed? Address should use the Common Type

  • Additional Info was removed

    • The question of why did we remove additional information? Last week it was decided that these elements were no longer needed.

    • We need to decide if we need named valued pairs, additional properties added to our overall schema so it does not break our code if someone needs to implement new data elements.

      • Everyone is good with allowing the schemas to allow additional elements.

  • DocumentInfo does not need object in schema, these 4 do not need wrapped

    • What is version? Version is previous BMS Version and may not be needed in the Json Schmea

    • documentInfo would be the top level of each JSON schema, the four values do not need to be wrapped.

    • Document version is still needed, but its not needed for FNOL, but it will be required in the estimate.'

    • Does Version need more documentation, since it is version. Should it be capisVersion? We may be able to remove version and just use path. Rest uses versions in the URL path.

    • Next week we need to look at the version Api

    • Document info promoted p and admin info has been flattened

  • We looked at the FNOL test instances and they are all values populated and not realistic; Paulette will look to the FNOL team this week to get examples of FNOL.

Great Job

Up Next

  • Antitrust and Meeting minutes acceptance

  • Review FNOL Examples and Dan’s FNOL

  • Work on FNOL JSON messages

  • Versioning CIECA API

  1. DocmentInfo does not need object in schema
  2. BMS Version will not be needed in JSON and do not see a Version being needed in JSON Schema, may just be able to use URL path
  3. Document Version is still needed, but not needed for FNOL; it would be required for estimate

Participants

  • Paulette Reed

  • Phil Martinez

  • Joshi Hemant

  • Mike Hastings

  • Manjusha Khaire

  • Dan Webster

  • Brad Broerman

  • Chrisa Hickey

  • Andy Bober

  • Paul Barry

 

Participants in the meetings are noted for your information.  If you have questions on the committee’s activities, please contact a recent attendee. Architecture Committee