Innovating healthcare
Innovation on demand
Innovatiecafé IPS mrt 2013 Clark.nowack@han.nl

Participatory Healthcare Innovation
PHI
>75% of ‘innovations’ fail… Why?
• Failed to meet “customer” needs
• Incorrect pricing
• To late/ early to market
• Supply chain issues
• No new unique vallue
• Technology driven/ push
• Change management issues
•…
Innovation barriers
Politics | Culture | Privacy
Organisational | Regulations
Jargon | Ethics |”Technology”
…and more
Business model healthcare
But, barriers to tackle:
are NOT technological
 Participatory Healthcare
Innovation
a Black
&
White
Approach
Statement
Healthcare (needs) basically
do(es) not change
Technology does,
rapidly, so innovation is at hand
(just arround the corner)
Sint-Petersburg in 1835
COUVEUSE
http://www.io.tudelft.nl//fileadmin/Faculteit/IO/Actueel/Nieuws/Design_Etalage/Showcases/Babybloom
/img/Babybloom1_web.jpg
Basic ‘need’ is keeping
the infant alive
(regulate damp and temperature)
Innovation by technology
Any idea?
Haertbeat
http://seniorennet.nl/Pages/Nuttige_telefoonnummers/images/hartslag4.jpg
Instant diagnose
http://www.diagnosetechnologie.nl/wpcontent/uploads/2012/03/logo_diagnose_technologie_280x150.png
Conclusion:
Explore WHAT to innovate
NOT HOW to innovate!
But, with whom?
All required Stakeholders
Patients | Family | Caretakers |
Researchers | Business | Consumers |
Developers | Engineers | End-users | IT
Professionals | Friends | Ensurers | ...
Stakeholders...
Requirements engineering
Engineer(specify) the need
NOT
the solution
‘Stakeholders are not capable to specify
their needs unambiguous’.
“they preach their own jargon”
“no standardization”
“mankind thinks in solutions”
…typical stakeholders...
•
•
•
•
•
•
•
•
don't understand what they want
won't commit to written requirements
insist on new requirements
communication is slow
do not participate in reviews
are technically unsophisticated
don't understand the development process
…
Chicken story
Another chicken story
…mindshift in innovation...(vrij vertaald)
The range of what we think and do is limited by
what we fail to notice.
And because we fail to notice that we fail to notice,
there is little we can do to change;
Until we notice how failing to notice shapes our
thoughts and deeds.
Ronald Laing
Requirements Engineering
Specifying reqcuirements
‘the’ V-model
Market
Stakeholder
requirement
Acceptance
test
System
requirement
System
test
Prototype
Solution domain
WHAT
HOW
Problem domain
Statement
of needs
A requirement and it’s attributes
• Description a one sentence statement of the intension of the
requirement
• Rationale a justification of the requirement (WHY!)
• Fit for use criteria a measurement of the requirement such that
it is possible to test if the solution matches the original requirement
• Originator person whom raised this requirement
• Event/ usecase / protocol the source of the requirement
“Good” practice examples
http://www.npl.co.uk/upload/img/good-practice-online-modules.jpg
http://www.visionair.nl/ideeen/mensheid/geneeskunde-heeft-goedkope-uitvindingen-nodig/
Portable scanner
Keuze om niet te innoveren?
Business model healthcare
INNOVATORS van de toekomst
Wat vind je van deze manier van
innoveren?
Wie zou de verantwoordelijkheid
voor deze manier van innoveren
moeten nemen?
It´s your turn…

Participatory Healthcare Innovation
Specifying the problem will lead
simply to an (already)existing
out of the context (box)
solution
www.reqcare.com
18 min. TED talk