Skip to main content

Stanford Biodesign Colloquium

 

Last week, I forget which day it was, some folks at office invited two academicians / entrepreneurs from Stanford to talk about Biodesign – essentially the science and art of developing medical technology and products.

An occasional sift from my lazy self, I took some notes. And so I thought I will put this out on the net, since it does not contain any hush-hush secrety stuff. Needless to say, if there is something inaccurate in the notes below, it is most likely the manifestation of my ignorance and consequential misinterpretation.

 

The presentation was divided into two parts, one part by each speaker. The first speaker, Dr. Anurag Mairal further broke it into two pieces of his own. He spoke on Medical Technology in India and China. He offered the hypothesis that while there were some similarities because of the emergent nature of technology and economy between the two countries, they were fundamentally very different (and hence the need to tackle them separately).

    • Medical Technology in India and China
      • India: A breeding ground for disruptive, quality innovation
      • China: A device exporter in the making ?

The other speaker, Dr. Rajiv Doshi spoke about the Stanford Biodesign Process, what it is and what kind of results it has yielded.

India: A breeding ground for disruptive, quality innovation

  • India has always tried to be innovative with medical technology, but successful only in small scale and the number of successes are few. Spoke about Jaipurfoot (jaipurfoot.org, product innovation) and Aravind Eyecare system (process innovation).

Challenges

  • Actual spend in healthcare as % of GDP has always remained lower than what is considered as optimal spend (~10%) in the western world
  • Indian industry not very innovative
    • 65% are low end medical suppliers
    • Few class III devices
    • Only 1% of revenue ploughed back into R&D, c.f 11% in the west
  • Very little venture capital in this industry
  • Low physician-industry collaboration
    • This is considered "unethical" (unlike the west)
    • In the other part of the talk, Rajiv Doshi mentioned (quite strongly and by self-admission, provocatively) that he considered working with doctors is NOT the right way to innovate
      • Doctors in India consider themselves as gods. Not ready to listen
      • They are so much into what they do and justify it, unable to see potential change in workflow etc
    • Zero to little animal testing facilities
    • Talent pipe-line non-existent
      • Stressed that while people in themselves are intelligent and entrepreneurial, there is an acute lacuna in course structure and formal ecosystems

Reasons for Optimism

  • Disease pattern shift: More of chronic lifestyle diseases, diabetes, cardiac etc, less of actue (infections) - malaria, pox etc ==> general healthcare apparatus improvement
  • Emerging middle class: demand for better healthcare service, outcomes and devices
  • Resurgence in rural healthcare:
  • clip_image001

China: A device exporter in the making ?

Primary thought was that China is good at manufacturing things, not necessary at inventing things

  • 1.3 B people. 80% healthcare is urban
  • 60% demand for imported western medicine
  • Very costly to get sick, even with government support for healthcare - which does not advance beyond basic care
  • People in china save for 3 things: Child education, healthcare, and if money is left a house
  • China spends less that India on healthcare as a % of GDP (which was surprising to me)
  • But significant government investment in healthcare infrastructure, but not enough training - the speaker cited examples he personally saw of floor cleaning machines in rural hospitals lying unpacked

Principle challenges

  • Insufficient capacity - everyone prefers to go to cities for healthcare
  • Lack of high quality patient care

What China needs:

  • Affordable technology
  • Devices or solutions that require less training, ease of use
  • Better clinical outcomes (patient care quality is not high)

 

Jugaad is also prevalent in China; the people are very pragmatic and worry about "today's problems and solution". Unlikely to come up with technologies for problems that do not exist today

 

Second part of the talk was by Rajiv Doshi on the Stanford Biodesign Process. The Biodesign course taught in Stanford takes interns for 6 months, trains them at Stanford and then sends them back to India (or Singapore); depending on the country of the individual for 6 months to work on a project. Primarily the biodesign process, or the science/art of making medical technology products is based on this following book.

http://www.amazon.com/Biodesign-ebook/dp/B0056XNLRU/ref=tmm_kin_title_0?ie=UTF8&m=AG56TWVU5XWC2&qid=1311283533&sr=8-1

clip_image002

Principle philosophy is

  • Identify (the need)
  • Invent (the solution)
  • Implement (the product)

clip_image003

This is a pretty well structured and involved methodology, I would highly encourage the reader to visit : http://www.stanford.edu/group/biodesign/cgi-bin/ebiodesign/

He spoke about a few key themes (in addition to describing the course)

  • Engineers tend to focus on the solution rather than the problem. They fit technology to a solution, not the other way around (which we need to do)
  • It is not difficult to find a problem to tackle; there are many. But the challenge is to prioritize which one(s) need to be solved. This lack of clear judgment is causing many startup to derail.

Comments

  1. I am glad I read this. Thank you for sharing Shourya.
    Check this out too:
    Medisoft Software

    ReplyDelete

Post a Comment

Popular posts from this blog

Barcamps over the world: BCB3/Minnebar

I think I am kinda special. Not quite like Paris Hilton special, but getting a  chance to attend two Barcamps separated by 8000 miles in a span of 3 weeks has got to be some kind of special stuff. I think the big guy above is smiling at me. Invest in my equity. This is an article outlining some of the interesting differences I saw between the barcamps in Bangalore (BCB3, 31 March -April 1, 2007 ) and Minnesota(Minnebar 2007, 21 April). This is not an article intended to compare or pass a judgement. Just throwing up some observations, fwiw . I am not offering explanations, I am not a socio-anthropology by training. Some of these do not require a degree to arrive at the reason of causation, but I want to keep this blog close to what I saw, not what I think. At most, some "could-be"s. Both the barcamps have a local flavour and preservation of local flavour to me, is inherently good.  Consider food, for example.  A predominantly South Indian buffet spread for lunch ...

Bambi 2.0

Bambi is a small coding-fest that we organise in our group at GE Healthcare. It was inspired by Yahoo Hackday after I heard about it at BarCamp Bangalore last year. I still remember, I came back all charged up after BarCamp and with some help from Arun B, we put together the first version of Bambi. Ours was a small team, roughly about 60 people, so spreading the news was not much of a problem. Getting people out of their workload was a bigger problem. The load is high and the work is, I guess, somewhat exciting ;-)  It is sometimes tough to lure people out of writing indexing algorithms for proprietary image databases or mitral-valve plane adjusters for segmentation of the human heart.     Today we had the demos for Bambi 2.0 The quality of demos were much improved and people came on the last day with some utterly cool demos. Unfortunately, I do not think I can write about them in detail owing to Intellectual Property issues but a mash of  Biometrics, Blue...

5 Ways to Kill a Post-Mortem

Software projects fail. One of the techniques you could apply to a project not going well is a post-mortem. A meeting where the critical participants meet to discuss what is going wrong. Preferably when there is still time to salvage things. But before you run a post-mortem of a project, here are some things you would want to consciously avoid. Hopefully as a project lead or in similar capacity, this will help you facilitate the meeting and shape positive outcomes. It starts with you.  The Final Blame-Game The idea of a post-mortem is to take an earnest look at some of the things that went wrong and understand why and how to avoid them. In brief, make mistakes, but please make new mistakes . If the meeting degenerates into blame-fixing, then you are headed in the wrong direction. Rule the meeting politely but iron glove. Don't let it become a mudslinging match. If you have been deeply involved in the project, chances are high that you would have your own frustr...