Mit

1. Google
Health
and
Microso2
HealthVault
Launch
Individual
Assignment
Names
of
the
contributors:
Wiroon
Suptavonkul

2. Q.1
Explore
the
Google
Health
and
Microso2
HealthVault
Launch
case
from
the
user
/
consumer
side
and
list
the
issues
that
contributed
to
the
failure
of
the
two
ventures.
(Con%nue
…)
2
Issues
that
contributed
to
the
failure
• Usefulness
– Most
people
are
sFll
not
aware
of
the
importance
of
their
PHR,
and
also
why
it
should
be
available
at
anywhere,
anyFme
– For
those
who
are
aware
of,
according
to
the
IDC
survey,
consumers
found
that
they
finally
stopped
using
them
due
to
…1)
they
said
they
didn't
want
to
spend
Fme
entering
their
data
and
…2)
they
did
not
see
value
in
doing
so
– Also
no
facility
for
ongoing
monitoring
the
health
status
– There
are
so
many
features,
but
consumers
did
not
know.
For
those
who
knew,
they
also
don’t
see
value
of
those
features
as
such
data
did
not
provide
an
easy
to
understand
interpretaFon
– Not
enough
adverFse
their
features
and
value
to
public
/
poorly
marketed

3. Q.1
Explore
the
Google
Health
and
Microso2
HealthVault
Launch
case
from
the
user
/
consumer
side
and
list
the
issues
that
contributed
to
the
failure
of
the
two
ventures.
(Con%nue
…)
3
Issues
that
contributed
to
the
failure
(Con&nue
…)
• Privacy
concern
– Google
Health
did
not
value
the
privacy
concern
of
the
PHR
– While
Microso2
HealthVault
has
a
feature
to
allow
only
self
and
some
of
their
relaFves
to
access
to
the
data.
But
most
people
sFll
feel
uneasy
and
uncomfortable
to
have
their
data
available
on
the
Net.
– If
they
could
use
Marquee
strategy
to
partner
with
the
big
name
health-­‐care
insFtuFons,
they
would
gain
more
trust
of
having
such
PHR
on
the
Internet
– Not
covered
by
HIPAA
is
also
one
of
the
reason
those
who
understand
the
value
of
PHR
sFll
reluctant
to
pursue
– Do
not
know
what
to
input
and
reluctant
to
their
data
without
a
feeling
of
such
data
shall
be
truly
secure
…
I
don’t
have
any
informaFon
to
put
onto
Google
Health,
I
really
would
want
privacy
guarantees
before
pu[ng
my
informaFon
into
the
system
to
prevent
my
informaFon
ge[ng
public
on
the
internet.

4. Q.1
Explore
the
Google
Health
and
Microso2
HealthVault
Launch
case
from
the
user
/
consumer
side
and
list
the
issues
that
contributed
to
the
failure
of
the
two
ventures.
(Con%nue
…)
4
Issues
that
contributed
to
the
failure
(Con&nue
…)
• User
friendly
–
Expectancy
concern
– From
the
research,
I
found
that
many
web
sites
said
both
were
cumbersome
to
use,
not
friendly
enough,
and
no
base
set
to
start
(no
idea
where
to
start
from)
– the
informaFon
complexity
can
become
too
unwieldy
and
complicated
for
most
people
to
maintain
on
their
own
without
professional
input
– Though
both
applicaFons
allows
to
import
data
from
medical
devices
(including
gadgets
and
apps
from
IOS
&
Andriod)
and
3rd
party
providers,
and
even
input
manually
(Google’s
one),
but
consumers
sFll
feeling
of
having
no
idea
what
and
how
to
input.
Moreover,
Interface
is
a
lible
clunky
and
not
friendly
enough,
especially
in
terms
of
interpreFng
data
and
provide
useful
and
easy
to
understand
– Both
has
no
correlaFon
features
from
several
data
sets

5. Q.2
Explore
the
Google
Health
and
Microso2
HealthVault
Launch
case
from
the
partner
/
health
organizaFons'
side
and
list
the
issues
that
contributed
to
the
failure
of
the
two
ventures.
5
Issues
that
contributed
to
the
failure
• StandardizaFon
– There
is
no
common
standard
for
health
informaFon
among
different
health-­‐care
insFtuFons.
Hence,
making
different
systems
from
different
agencies,
hospitals,
etc.
to
record
and
store
data
are
one
of
the
big
challenge.
– Not
covered
by
HIPAA
– Including
the
authorizaFon
to
accessing
the
system
and
sharing
info
among
several
partners
–
this
is
a
problem
for
both
consumers
and
providers/partners
(Every
single
partner
service
you
chose
requires
an
iniFal
signup
and
then
subsequent
login.
Some
have
your
basic
login
data
passed
by
HealthVault,
others
will
force
you
to
start
from
scratch.
Of
course
you
will
use
your
Windows
Live
ID
(formerly
Passport)
to
log
in,
and
if
you
are
a
mere
mortal
like
I
am,
in
the
maddening
sequence
of
screens
you
o2en
won’t
know
whether
you’re
logging
in
to
HealthVault
or
a
partner
service.)

6. Q.2
Explore
the
Google
Health
and
Microso2
HealthVault
Launch
case
from
the
partner
/
health
organizaFons'
side
and
list
the
issues
that
contributed
to
the
failure
of
the
two
ventures.
(Con%nue
…)
6
Issues
that
contributed
to
the
failure
(Con&nue
…)
• Not
ge[ng
buy-­‐in
from
doctors
– From
the
research,
I
found
that
most
doctors
and
medical
offices
are
sFll
stuck
in
the
age
of
paper
and
fax.
They
don’t
see
value
of
having
e-­‐
health
record
–
maybe
providing
some
form
of
incenFve
may
abract
to
adopt
electronic
medical
records.
– Though
Google
Health
had
partnership
with
the
insurer
Blue
Cross
Blue
Shield,
but
turn
out
to
be
manually
enter
their
informaFon,
and
sFll
required
hard
copies
of
the
records.
– If
they
could
have
a
good
buy-­‐in
the
applicaFons
may
integrated
with
each
hospitals
and/or
health-­‐care
insFtuFons
to
provide
an
online
self
appointment
with
doctors.
As
such,
both
consumers
and
providers
may
see
more
value,
rather
than
only
focusing
on
the
data
storing
and
be
able
to
exchange
data
back
and
forth.

7. Q.3
Explore
the
Google
Health
and
Microso2
HealthVault
Launch
case
from
the
societal
side
and
list
the
issues
that
contributed
to
the
failure
of
the
two
ventures.
7
Issues
that
contributed
to
the
failure
• Not
interested
–
not
fun
– Both
only
provide
a
place
to
store
data,
but
there
is
no
fun
and
engaging
–
hence
not
interesFng
for
social
at
all
– They
could
have
some
form
of
only
sharing
certain
informaFon
such
as
number
of
kilometers
consumers
run,
or
daily
walk
steps
taking
from
the
gadget,
the
pressure
their
peers
to
exercise
more.
Make
it
fun,
with
some
contest,
or
games
to
gain
more
abracFon
to
social
– Not
understanding
the
importance
of
PHR

8. www.emeritus.org