Should we all do the same tasks and compare notes?
The task overview presented above is one way to collectively decide the most important tasks. Please vote on those and add tasks you see missing.
Should we focus on the tables we signed up to do?
The tables division was one way to divide the work. (besides tasks). My goal with the table “stewardship/babysitting” was to let folks think about quality of v1 mapping (2 years old) and suggest gaps. The posting by Michael Kallfelz presented a good overview for all tables. (but brief)
Are there any deadlines for deliverables?
No - because some folks are waiting for funds to cover their effort. Others are contributing some time (and not waiting). One deadline is to release v1 of OMOPed demo data by July 30th or sooner. (in a shape that MIT will approve; with release notes and their mandatory fields (see central notes for draft)). Nicolas promised to create the CSV files for that. I may have to look for other source since he may be busy.
Do we need to use BQ or not (I see that Jose did, but not you)?
Only for v2 - we may use BQ. I think a good plan is to make mapping platform independent so implementation in many flavors is possible. BQ has some advantages over current postgres. What do you think, Juan?
Here is the script to load in SQLite and later run ohdsi tools.
https://rpubs.com/vojtech_huser/OMOPedMIMIC1
Thank you all who responded on this forum publicly! This helps the momentum. We need more posts with questions like you posted. Ad meeting, I am fine with meeting. @parisni, we probably need time to accommodate EU time zone. To prepare for the meeting, can everyone vote and add tasks they see important. (spreadsheet file on google drive, same link as always)