innovating healthcare

Innovating healthcare

Innovatiecafé IPS mrt 2013 Clark.nowack@han.nl

Innovation on demand

Participatory Healthcare InnovationPHI

>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 | PrivacyOrganisational | Regulations Jargon | Ethics |”Technology”

…and more

Business model healthcare

But, barriers to tackle:

are NOT technological

Participatory HealthcareInnovation

a Black&

White

Approach

Healthcare (needs) basicallydo(es) not change

Technology does,rapidly, so innovation is at hand

(just arround the corner)

Stat

emen

t

COUVEUSESint-Petersburg in 1835

http://www.io.tudelft.nl//fileadmin/Faculteit/IO/Actueel/Nieuws/Design_Etalage/Showcases/Babybloom/img/Babybloom1_web.jpg

Basic ‘need’ is keepingthe 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/wp-content/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 needNOT

the solution

‘Stakeholders are not capable to specifytheir needs unambiguous’.

“they preach their own jargon” “no standardization”

“mankind thinks in solutions”

• 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• …

…typical stakeholders...

Chicken story

Another chicken story

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

…mindshift in innovation...(vrij vertaald)

Requirements Engineering

Specifying reqcuirements

‘the’ V-model

Statementof needs

Stakeholderrequirement

Acceptance test

Systemtest

Systemrequirement

Prototype

Market

WHATHOW

Problem dom

ainSolution dom

ain

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

Source : www.systemsguild.com

“Good” practice examples

http://www.npl.co.uk/upload/img/good-practice-online-modules.jpg

Portable scanner

http:

//w

ww

.visi

onai

r.nl/i

deee

n/m

ensh

eid/

gene

esku

nde-

heeft

-goe

dkop

e-ui

tvin

ding

en-n

odig

/

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 leadsimply to an (already)existing

out of the context (box)solution

www.reqcare.com

18 min. TED talk