Page Comparison

Date

13 Jul 2021

Agenda

• Antitrust and Meeting minutes acceptance

• VIN examples longer than 17?

• Vehicle Info required fields discussion

• No Examples of FNOL, continue with FNOL API

• Fleet Info simplified

Meeting Minutes

• Antitrust Accepted

• Meeting Minutes Accepted

• The examples of VIN being longer than 17 were all error vin codes

  • Over a year worth of data was looked at and no valid VIN codes greater than 17

  • In 1980 the Government made the VIN Codes standard

    • Before that the VIN Codes were shorter

  • Boat Codes are shorter than 17

  • Late Model Vehicles are shorter than 17

  • Commercial Vehicles are shorter than 17

  • The BMS has VIN length of 30

• At this time we will have the VIN in the schema be 17, if a need comes up later for the length to be longer, it can be requested. The minimum value will be 1.

• Vehicle Info required fields

  • The BMS will allow a Vehicle Info without required fields as long as they do not select an aggregate like VINInfo that is required.

  • We want to have standards and have a valid vehicle. It would appear that you would know the VIN or the Year/Make/Model to put vehicle information into a messages

• The Required fields for Vehicle Info will be VIN or Year/Make/Model

• DocumentInfo

  • DocumentInfo was moved up and four fields were moved to the top of all messages in a previous meeting. We reviewed this and made the changes to the GitHub cieca_api_standard/json-test-instances/flattenedFnolReportAddRq_First_Report_Vehicle.json

• The four fields we keep from DocumentInfo to be rolled up are Version, CreateDateTime, PassTrhoughInfo and VendorCode.

• AdminInfo

  • AdminInfo is also flattened and in the capisCommonGlobalTypesSchema.json and it was reviewed as we discussed the Parties that were in the FNOL report.

• Parties in FNOL include:

  • Insurance agent

  • Insurance Company

  • Repair Facility

  • Tow

  • OEM

• Where can FNOL come from?

  • Could FNOL come from an app?

  • Examples of who is reporting the FNOL from the BMS, XML Schema Test Instances and the Mater Code List are

    • Agent

    • All Ways

    • Individual,

    • Info Req

    • TPA

    • Update

    • Vehicle

• BMS FNOL captures the sender in the documentSubType and the Committee is not sure that is the valid area for the information.

  • In the next meeting we would like to go over all the parties/Actors and determine which ones will be used (for example; would ambulance be a party) and determine how to incorporate this information in the FNOL schema.

• Schema Bundler

  • Dan provided a webpage to review structure of Complex Schemas. The main page is http://json-schema.org , but the information Dan wants to focus on with the structuring Complex types is found https://json-schema.org/understanding-json-schema/structuring.html#structuring

Great Meeting everyone

Up Next

• Antitrust and Meeting minutes acceptance

• Work on FNOL Parties/Actors

• Work on FNOL JSON message

• Discuss structuring Complex Schemas concepts and the bundling.