Open Insurance Data Standard White Paper Work Group - 3/3/25
- Nathan Southern
Attendees
Jim Bamberger
Jeff Braswell
Cory Isaacson
Lanaya Nelson
Ken Sayers
Nathan Southern
Jenny Tornquist
Opening Logistics
Nathan Southern opened the meeting by displaying and acknowledging the Linux Foundation Antitrust Policy
Central Discussion
The meeting proceeded without a set agenda; the central focus of the discussion concerned final updates on the white paper, in addition to minimal work on it that still needs to be done (see Action Items, below). The following high level points were made:
Regarding the title: Cory went with The Case for Open Insurance Data Standards
The abstract has not changed
The Introduction now contains the alternate passage by Lanaya that supplements the old text; Cory resolved it in the call.
Jim Bamberger’s question (in comments) about what is meant by “insights accuracy, risk management and regulatory compliance” has been resolved.
Everyone is in agreement on the content under ‘The Proprietary Data Format Problem' and no further work or revisions are warranted in this section.
The illustrations still need to be moved - per Jen’s request (see Action Items, below).
Sections on Lack of Interoperability, High Costs, Vendor Lock-In, Data Fragmentation are fine
There is a section of the document that discusses legislation and how legislators can do a better job if they have more current data (per Jen’s request earlier in meeting - stressing issues with data latency discussed in paper). This is also discussed in the section ‘Easier Regulatory Compliance.’ (Note: Jen said this isn’t quite there - instead of easy, she was thinking something along the lines of more responsive, and Lanaya suggested running through ChatGPT for help - see action items below).
The section titled ‘Managed by the Linux Foundation to be Forever Open’ needs no additional work
The section Open Insurance Data Standards (OIDS) needed simplification and Cory finished this; he also changed the opening statement to ‘OIDS is an evolving set of open data standards’ in meeting.
Cory also wrote ‘A Brief Overview of OpenIDS’
Cory also interpolated Jeff’s conclusion.
Bold modified in the conclusion.
ChatGPT content moved to very bottom
As a result the paper is much shorter
Much of Rob Clark’s content is being moved to a second, follow-up paper
Press Release Discussion
Lanaya informally proposed grouping the next white paper and Cloverleaf’s IP contribution together in a single press release.
It may also be an option to package the case studies with the second white paper.
Next Steps
Lanaya will talk to Josh to determine next steps, who needs to sign off on the paper, etc.
Action Items
Jenny Tornquist - Modify illustration order as needed in white paper.
Lanaya Nelson - Take the passages involving easier regulatory compliance in the white paper and run through chatGPT to come up with something closer to more responsive regulatory compliance, or more expeditious… Also consult with Josh (as a former regulator) on this point and get his feedback.
Working Group Members: Wait until Lanaya runs the paper through chatGPT and then review both versions (she will juxtapose both in the same document). Please have feedback ready by Wednesday 3/5 - review, comments, edits., etc. and go from there.
Lanaya: Circle back to Josh to get next steps (who paper needs to approve it, etc.) and report his response/comments back to group (perhaps in same email as chatGPT version).
Sean Bohan: Pull together stakeholders for Community Specifications Working Group and do doodle poll on the best day and time for this.
Nathan Southern: Set up new meeting series and corresponding specifications working group mailing list when Sean sends info about the new working group.
