Biotech Strategy Blog

Commentary on Science, Innovation & New Products with a focus on Oncology, Hematology & Cancer Immunotherapy

Posts tagged ‘ASH16’

John P. Leonard, MD is the Richard T. Silver Distinguished Professor of Hematology and Medical Oncology at Weill Cornell in New York. He’s a Lymphoma specialist.

Dr John Leonard at ASH16

Like many hematologists, he’s embraced Twitter as way to share his expertise with others in the hematology community. You can follow him at @JohnPLeonardMD.

Over the last couple of years prior to the ASH annual meeting, Dr Leonard has highlighted 10 lymphoma abstracts that caught his attention. You can tell he gets excellent social media pickup by the fact he’s even generated a hashtag to make them easy to find: #Leonardlist and other hematologists generate conversations around his eagerly awaited picks:

In case you missed them on Twitter, and in the spirit of David Letterman, Dr Leonard took me through this year’s #LeonardList and thoughtfully explained in detail why each selection made the cut… for oncology watchers, the why is often more important than the what.

Subscribers can login to read more

San Diego – after “Flying Friday” where I flew from Munich to San Diego, Biotech Strategy Blog coverage of the 2016 annual meeting of the American Society of Hematology (ASH) is now done for another year.

Downtown San Diego during ASH 2016 With over 27,000 attendees – it’s the largest ASH annual meeting I’ve seen in 20 years of coming here!  ASH is definitely the pre-eminent global meeting for hematology and blood cancers.

As you might expect, the thought leaders at this event are super-busy, but we’ve already managed to catch up with a few, and we’ll be rolling out interviews in the “post-game show.”

Subscribers have been asking what’s really hot at ASH this weekend, so reflecting my interests and the sessions I went to, here are my seven highlights/learnings of ASH 2016 (so far). There’s a lot more data to come!

Subscribers can login to read more or you can purchase access…

error: Content is protected !!