►
Description
In this lightning talk, Stefan Adolf introduces an ideal situation for decentralization: saving encrypted, centralized health records in order to create a decentralized medical health record in Germany.
For more information on IPFS
- visit the project website: https://ipfs.io
- or follow IPFS on Twitter: https://twitter.com/IPFS
Sign up to get IPFS news, including releases, ecosystem updates, and community announcements in your inbox, each Tuesday: http://eepurl.com/gL2Pi5
A
The
first
thing
is
the
app
for
the
patients
and
they
are
creating
the
record
on
themselves.
Everything
is
based
on
IP
address
and
on
Nigeria,
and
what
I
would
like
to
do
is
I'm
just
creating
a
medical
health
record
here.
This
takes
some
seconds
because
we're
now
anchoring
the
identity
of
the
user
that
we
created
here
in
the
browser
onto
the
blockchain
and
let's
give
them
some
name.
A
They're
so
jolly
and
I
think
my
brother
crashed
it's
just
slow,
I'm.
Sorry
and
you
can
also
choose
your
birthday,
which
is
quite
ridiculous,
because
I
think
never
no
one
wants
to
change
your
birthday,
but
this
is
just
just
the
demo
rate.
So
once
you
created
this,
this
entry,
this
is
stored,
is
an
encrypted
ipfs
file
and
ipfs,
and
the
the
record
root
is
anchored
on
the
blockchain
I
mean
many
of
you.
People
will
know
what
I'm
talking
about
anchoring
theories
on
the
blockchain
is
not
like
the
biggest
thing
do,
but
what's
important.
A
A
And
our
idea
is
if
you're
practitioners
you're
trusting,
so
we
have
a
second
application
here.
This
is
the
application
of
the
practitioner
and
you
must
imagine
if
the
patient
goes
to
the
practitioners
place,
whereas
practicing
there
is
this
QR
code
and
the
patient's
can
stick
to
our
code,
so
it
gets
into
some
kind
of
trust
relationship
with
a
practitioner.
This
is
what
I'm
doing
here
as
soon
as
I.
Do
this
we're
anchoring
the
trust
relationship
between
the
practitioner
and
the
patient
on
the
blockchain?
But
what
we're
not
doing?
We
are
not
say.
A
Ending
an
event
on
the
build-up
sub
to
notify
the
practitioner
that
he
has
received
a
new
patient
and,
as
you
can
see-
and
this
is
also
a
question
for
you-
guys-
okay,
it
took
just
a
while.
This
was
idea
cos
pops
up.
So
there
was
a
recruit
so
of
the
tops
of
message
from
one
browser
window
to
another
browser
window.
A
There
is
no
server
in
between
this
is
just
IP
fizz
pops
up
and
from
from
from
that
point,
the
practitioner
can
see
the
patient's
record
and
I
said
this
has
been
encrypted
on
the
patient
side,
with
the
public
key
of
the
patient.
But
as
soon
as
you
as
a
patient
decide
to
share
the
direct
code
with
your
with
your
practitioner,
you
send
an
encrypted
on
you,
send
the
CID
or
the
encrypted
file
for
the
practitioner
to
the
practitioner
and
just
to
show
you
that
this
is
really
working.
A
Our
the
practitioner
can
do,
let's
put
in
some
data,
yeah
and
I.
Think
sharing
is
not
the
best
thing
to
do
on
Ubuntu.
I'm.
Sorry
hope
that
you
can
still
hear
me
so,
let's
just
put
in
some
fake
data
and
now
the
practitioner
is
creating
a
so-called
proposal
document
which
is
encrypted
for
the
patient
and
he's
now
anchoring
that
you
see
ID
for
you
that
you
might
consider
putting
into
your
medical
health
record.
And
you
see
it
should
be
mined
very
fast.
A
A
It's
working,
no,
it's
not
not
that
this
entry
here
it
is
okay
that
this
practitioner
is
sent
to
him
is
already
automatically
accepted
because
you
trusted
the
professional
reforms
so
from
from
in
terms
of
user
experience.
This
is
quite
great
because
it
feels
like
that
the
practitioner
can
really
write
into
your
record,
which
he
cannot
he
can
just
propose,
and
we
are
accepting
all
these
things
automatically
if
there
is
some
trust
enabled
and
just
to
show
you
that
this
was
really
running
on
ipfs.
I
hope
that
this
note
is
responding
fast
enough.
A
All
these
documents,
of
course,
thought
decentralized,
and
sometimes
as
fast.
Sometimes
not
you
know
the
game
right.
What's
interesting,
of
course,
all
these,
so
both
applications
are
running
in
a
J's,
ipfs
nodes
inside
the
process
and
yeah.
It's
always
a
matter
of
reach
ability
if
you
can
find
the
records
as
soon
as
if
you
click
on
that
this
is
our
biggest
issue,
so
we're
putting
a
pinning
node
in
between
which
is
reading
the
blockchain
along
pinning
all
the
documents
that
have
been
proposed
or
changed,
so
we
are
able
to
serve
them
rather
quickly
hope.