Public Page

2023-08-22 Architecture Meeting Minutes

Owned by Paulette Reed
Last updated: Aug 29, 2023
3 min read

Public Page

Date: Aug 22, 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

  • 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

  • Review Mikes Work

Meeting Minutes

  • Antitrust Accepted

  • Meeting Minutes Reviewed Accepted

  • Review Mikes Work

    • In Party we removed/Flattened out the ID array into multiple properties

    • We have test driven development where we can run NPM test to find out the instance docs that needed to be changed and get everything passed.

    • Need to add new test instance documents for the two new properties we added to the claim object,

    • Ran Stoplight to update API (Interesting)

      • A new project was created, claim service version and it did not like our bundle schema.

      • The import and build worked but when it tried building it ran into trouble.

      • If we use the unbundled schemas and link the endpoints to them, everything is fine in stoplight.

        • Was able to Build the API using our standard schemas and then bundle it and everything was okay.

        • Stoplight has been acquired by Smart Bear.

    • We use the Jason schema rough parser

      • This lead to us having to investigate what was the competitor's hyper jump and that was a bridge

      • They were using the new ID references

      • Jason came up ref parser that wasn't particularly satisfactory and hyperjump wasn't satisfactory and it looks like the faced with the same issue.

    • Should we remove bundling from our release and let the tools the partners use handle the bundling?

      • We can move the bundling to the backburner so we can move forward rather than trying to make a big decision on it one way or the other.

      • Big benefit to bundled schema is smaller schema, if the tool does this it is better.

      • The big benefit really is the simplification not really the size they like your pointing out like the size.

      • Bundling is super important, so at least if we provide the unbundled schema and then a bundled schema, you know that we've and say here's an example of a bundled schema that it's accomplishing sort of what we're looking for.

      • Change the work to look at the standard schemas and not bundled ones for now.

    • Can we remove large code list

      • Country do we need every country or only the ones our industry uses?

    • Work on the build

  • CONNEX

    • We do not have to have the release completed for CONNEX, we can talk about the work we did and talk about how we are going to be able to implement.

  • Work meeting on Friday

Great Work everyone

Up Next

  • Network/Welcome

  • Antitrust

  • Review Meeting Minutes

  • Review Mike’s changes for next release.

Action items

Decisions

Reference

 

Participants

  • Paulette Reed

  • Andy Bober

  • Dan Webster

  • Mike Hastings

  • Paul Barry

  • Phil Martinez

  • 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