• RecurringMeetings
• 2015-10-20

Recurring Meeting of Cleveland Clinic Core Team

Date: October 20, 2015

Time: 2:00 PM EST

Means: In person meeting

Attendees:

1. Ahmet Erdemir
2. Tammy Owings
3. Robb Colbrunn
4. Tara Bonner
5. Callan Gillespie

Agenda:

1. Discuss immediate action items from last meeting.
2. Additional issues for ultrasound system-force transducer integration.
3. Details of in vivo testing protocol.
4. Decide immediate action items for next meeting.
5. Other.

Immediate Action Items:

• Ahmet
  • Send the group information on ultrasound related metadata in DICOM headers
  • Request mechanical drawings of ultrasound probes, specifically 14L5.
  • Request 3D ultrasound probe for evaluation.

• Tammy & Ahmet

  • Start documenting in vivo testing strategy in the Specifications/InVivoTesting wiki page.

• Robb
  • Talk to Barry Kuban from the Electronics Core of Cleveland Clinic on strategies to send signals through ECG channels.
• Tara
  • Continue interacting with Siemens to understand ultrasound triggering/gating through ECG.

• Tara & Robb

  • Start documenting ultrasound system and force transducer integration in the Infrastructure/InstrumentedUltrasound wiki page.

Notes:

1. Discuss immediate action items from last meeting.
   • Tammy and Callan provided Ahmet DICOM files with ECG data. Ahmet was able to open the DICOM files. ECG signal was displayed on the images. The metadata of the DICOM file did have some entries that may be relevant to R-wave. Yet, these did not seem to correspond to the actual value of the ECG signal. Ahmet went over DICOM images and metadata to describe various entries in the DICOM header, e.g. voxel information, frame time vector, etc. Ahmet also learned about ultrasound specific DICOM metadata and he will provide the group some links in this regard.
   • Tammy shared the presentation on subject positioning with John-Eric Jelovsek. His feedback was discussed in the meeting to finalize decisions on positioning. Tammy went over the procedure and the anticipated order of collecting ultrasound images on the extremities. The order may change if the ultrasound probe needs to be switched. In response to Robb's question, Ahmet noted that active data collection during imaging of each site should not take more than 10 seconds. Tammy will start documenting the in vivo testing strategy on the wiki.
   • Robb received quotes for the force transducers; for integration with ultrasound and with surgical tools. Tara ordered data acquisition system for the force transducer, which will be used with the ultrasound. The group also made a decision on which data acquisition system to purchase for the force transducers that will be used with surgical tools.
   • Tara also obtained a quote for a laptop to be used for data collection. Tara and Robb will star documenting the ultrasound system and force transducer integration on the wiki.
   • Tara learned the utility of the auxiliary ECG channel. It is used to feed ECG signal, i.e., when ECG connectors are not available. The group decided that either this channel or the ECG inputs can be used for time synchronization. Ahmet advised to start with the ECG inputs as these are likely to be available in other ultrasound systems. Nonetheless, he also mentioned to have the flexibility to use the auxiliary ECG channel, in case needed.
2. Additional issues for ultrasound system-force transducer integration.
   • Tara has not received from Siemens more information on ECG triggering/gating. This may be a good thing to know as a general knowledge on the use of the ultrasound system.
   • Ahmet noted that Siemens will send a 3D probe for evaluation.
   • Ahmet also mentioned that the team may have access to mechanical drawings of ultrasound probes' external casing. These will be useful to design holders. He will ask the drawings for the probe 14L5.
   • Robb and Ahmet discussed strategies to associate ultrasound image files with force data files. Robb has an initial approach to implement.
3. Details of in vivo testing protocol.
   • See relevant discussions on immediate action items from last meeting.
4. Decide immediate action items for next meeting.
   • See Immediate Action Items above.
5. Other.
   • None noted.