Recurring Meeting of Cleveland Clinic Core Team

Date: November 24, 2015

Time: 2:00 PM EST

Means: In person meeting

Attendees:

Agenda:

  1. Discuss immediate action items from last meeting.
  2. Quarterly progress report.
  3. Decide immediate action items for next meeting.
  4. Other.

Immediate Action Items:

Notes:

  1. Discuss immediate action items from last meeting.
    • Ahmet sent an e-mail to Siemens engineers again to ask for the the drawings of external casing. He did not get a response yet. He will follow up.
    • Tammy collected sample ultrasound images on the lower extremity at all proposed locations and in a few places using multiple ultrasound probes. Tammy had concerns about her interpretation of the ultrasound images, in particular delineation of skin, fat, muscle and bone layers. Ahmet and Tammy decided to go over the images together. Tammy also requested to reach out John-Eric Jelovsek to help her get accustomed to understanding ultrasound images. Ahmet mentioned that our collaborators in other clinical departments may be useful in this regard. For training, Ahmet recommended Tammy to consider courses on musculoskeletal imaging that may be available through ultrasound system manufacturers.
    • Robb ordered the load cells for the ultrasound system - force transducer integration.
    • Robb started working on the design of software data structure and interface to collect force transducer data simultaneously with ultrasound imaging. Many issues were raised and discussed:
      • Robb described the initial data structure, including recording of patient id, segments, circumference and length measurements, and naming of protocols - in our case locations. The team confirmed that there would be three circumference measurements. Yet, Robb was advised to accommodate multiple length measurements as the total length of the segment needs to be measured along with the locations of circumference measurements. The workflow will likely start with the measurement of segment length and then circumference locations.
      • Ahmet recommended that an overall display in the interface indicating at which step the user is during the data collection worklow will be helpful.
      • Robb was reminded that all data will be collected, an protocol (in our case a location) will be repeated if the user rejects the data due to undesirable quality. The quality of the data can be assessed visually from a display providing the time history of force and synchronization signals. An automated workflow is anticipated with the data collection scheme moving from one protocol (location) to another after acceptance of data. A manual override may be necessary.
      • The need for a foot or hand switch to start and stop force transducer data collection was noted. This will help streamline user interaction, without the need to reach for a mouse and click buttons on screen. A hand switch may be preferable, allowing the foot to control the ultrasound start and stop and the other hand stabilize the probe. It is also possible to stop both systems (force transducer data collection and ultrasound imaging) automatically after a set amount of time.
    • The group still needs to document ultrasound system and force transducer in the relevant wiki page on infrastructure.
  2. Quarterly progress report.
    • The first quarterly report is coming up. Ahmet emphasized the importance of updating the wiki regularly. This will allow him to compile the information in the progress reports in a complete and expedited manner.
  3. Decide immediate action items for next meeting.
    • See Immediate Action Items above.
  4. Other.
    • None noted.

RecurringMeetings/2015-11-24 (last edited 2016-05-04 22:08:56 by localhost)