Skip to main content

Introducing MSKCC Team

MSKCC Team, Memorial Sloan Kettering Cancer Center

New York, NY

  • Yukako Yagi, PhD
  • Jo Sirintrapun, MD
  • Tom Fuchs, PhD
  • Peter Schueffler, PhD
  • Kazuhiro Tabata, !MD
  • Jamal Benhamida, !MD
  • Xiu-jun Fu, !MD
  • Martin dot Eber at is MSKCC Olympus rep
  • Takeo dot ogama at is MSKCC engineer

While we make no promises, here are our plans and objectives:

  • Generally, we would like to be involved to prove the value of WSI for pathology diagnoses and to standardize pathologic digital imaging.
  • We are not sure if we can buy the same stage and camera you have, but we would like to participate in an eeDAP reader study. It would be great if you could loan us a system for the study (1-2 months). At least 5 pathologists might be able to participate.
  • We would like to know if interpretations vary per scanner because of color or image quality. We have investigated differences with technical measurements, but we don’t know if these differences impact evaluations by pathologists.
  • For the study, we could use your slides and images or perhaps we could design a study using color charts or mouse embryos. I scan these regularly with many different scanners. We are not standardizing the color yet, but it is going to be available soon. We also have a variety of monitors that we could investigate.
  • We could also be interested in screening in cytology like thin preps where the cells are rather 2D and flat, might be amenable to this tasks since changes in magnification when screening are helpful but can be done without. I believe automated cytology screening machines do that currently. Another might be looking at peripheral smears for blasts, parasites. Acid fast smears for tuberculosis.
  • We have a Sakura Vision Tek digital microscope. Maybe we could design a study to include that in the comparison between the microscope and the WSI. It is not limited to VisionTek, we could use similar types of scanner like Aperio LV1 which has live mode and WSI mode to interface with the eeDAP software using API or command-line code.

Created on , Last modified on