1. MIBBI break out discussions Group “wet”

2. MI project overlap Population: MIQAS & MIMPP & TBC having the same name, but does it cover the same thing partial overlap Samples or specimens: MIQE & TBC STRENDA - MIAPE? PCR: MIQE & TBC Sample processing

3. MI project challenges Visibility - making people aware Convince people to follow the guidelines Convince journals / funding agencies Fear of loosing their scientific freedom IP vs free information Tools to make MI compliancy easier MIBBI should be in the protocol textbook

4. DOIs & ORCIDs requirement: MIBBI compliant db giving doi

5. Foundry Combination of domain specific MIs that take over bits and pieces from each other Cross referencing between multiple MIs may pose technical challenges Promoting open access will give advantages to Scientists: advances in science, repeatability Reviewers: easier to review Journals: higher impact Funding agencies: trace output – evaluation criteria Common language is not required Use version control to manage changes and updates

6. Vision Community specific checklists rather than modular MIBBI Driven by key opinion leaders in the community Different interests and opinions hamper pooling Communicate with and reuse elements from other MIs Role of MIBBI Guidance on what MI is about to promote high quality MIs Guide MI initiatives to be more successful No enforcement, no binding commitments MIBBI is umbrella organization, portal, creating public awareness for all MIs No need for MIBBI to provide stars or labels to individual MIs Work together based on a communicate and copy-paste system rather than a consensus model Is technical support possible? Minimal information about MIBBI

7. Side notes Basic criteria on which MI is built on Repeatability Assess quality Meta analysis Difference between scientist that use technology as Core for their research  easier MI adoption Just as one of the many tools to reach goal  more reluctant / difficult to adopt MI MI should be part of the workflow rather than something to adhere to at the time of writing  supported by tools