Recurring Meeting of Cleveland Clinic - Stanford University

Date: November 3, 2015

Time: 1:00 PM EST

Means: Conference Call

Attendees:

1. Ahmet Erdemir (Cleveland Clinic)
2. Joy Ku (Stanford University)

Agenda:

1. Specifications for data management and databases.

   • http://wiki.simtk.org/multis/Specifications/DataManagement

2. Timeline for delivery of data management and databases.

   • http://wiki.simtk.org/multis/FrontPage (see roadmap for web based interfaces)

3. Other.

Immediate Action Items:

• Ahmet (Cleveland Clinic)

  • Provide an illustration of the modeling & simulation workflow.

• Joy (Stanford University)
  • Document available systems for data management and databases.
  • Identify and document desirable features of an initial system based on workflow and presentation provided by Ahmet.

Notes:

1. Specifications for data management and databases.

   • Ahmet went over the Specifications/DataManagement wiki page to discuss needs for data management and databases. Ahmet uploaded two documents on that page - a presentation on the anatomy of finite element analysis for musculoskeletal joints and an itemized workflow for finite element analysis in biomechanics. Going over the workflow, Ahmet described various needs for a data management system and for databases, including users and developers perspectives. Joy will break down these documents into details to see how we would want an initial system look like. She will document these efforts in the relevant specifications wiki page.

   • Joy wondered how much the data management and database systems need to know about the nature of data sets, i.e. how much meta data are needed. Ahmet emphasized the importance of flexibility. It maybe possible to complement the raw or derivative data with pre/post-processors (workflows) to automatically populate meta data. Nonetheless, manual entry of meta data should be allowed.
   • Ahmet and Joy discussed the subcomponents of the models, i.e. a ligament model, which has its own anatomical and material properties, is a subcomponent of a knee joint model. Ahmet noted that spatial constraints, i.e. necessity to describe these components in the same coordinate system, challenge modularity. He also mentioned product life cycle management tools used in industry, i.e. automotive, for compartmentalization.
   • Ahmet guided Joy to a recently disseminated data set for the knee joint to let her evaluate what types of data the data management system and databases should expect.
2. Timeline for delivery of data management and databases.
   • Ahmet mentioned the documentation of the timeline for web based infrastructures in the main wiki page. Joy confirmed.
3. Other.
   • None noted.