►
From YouTube: Keeping Brazil’s Medical Industry Safe with MicroProfile and JakartaEE | Jakarta Tech Talks
Description
A case of migration to the cloud with MicroProfile in the Brazilian medical industry. It involves several challenges such as the fifth-largest population and largest territory in the world; complexity; and diversity, both geographic and economic. This session’s speakers discuss how they used MicroProfile projects such as Health Check, JWT Authentication, Metrics, OpenAPI, Rest Client, and Config to contribute to the success of the project; what benefits they saw; the challenges they faced; and how they solved them. Come see how MicroProfile played a critical role in creating a safe and scalable architecture and hear about lessons learned in the delivery of this mission-critical project.
A
Hi
everyone
and
welcome
to
this
week's
tech
talk
before
we
get
started.
I
just
wanted
to
give
a
little
to
the
Jakarta
on
the
livestream.
The
cloud
native
fridge
a
Java
license
nothing.
So
please
you
can
scan
your
QR
code
here
to
learn
more
about
that
and
also
we
recently
launched
the
Jakarta
EE
YouTube
channel,
so
there's
a
little
call
to
action
at
the
bottom
of
the
video,
but
you
can
also
scan
this
code
if
you
want
to
subscribe
and
stay
tuned
for
more
content
about
the
Jakarta
EE
community.
A
B
Let
me
share
my
screen
here,
so
thank
you.
Everybody
who's
watching
the
live
session
and
also
there
they're
recording
on
day
on
the
different
platforms,
thanks
to
you
at
presentation
and
a
the
Java,
the
Jakarta
community,
for
for
allowing
us
to
to
have
this
space
today,
traditional
screens
and
we
are
ready
to
start.
B
C
B
B
B
Do
you
have
two
options
in
the
platform
in
the
croc
has
platform
you
have
the
they
live,
the
the
right
side
panel
for
general
chat
among
the
participants,
but
there
is
also
a
section
just
beside
that,
one
that
you,
you
can
say
the
questions
and
answer
and
we
will
be
moderating
the
question
to
a
decision,
so
the
agenda
firfer.
For
today,
it's
pretty
straightforward.
We
are
gonna
review
with
the
help
of
Rafael
to
understand
the
Brazilian
healthcare
system.
B
The
overview
how
the
base
system
that
they
have
been
performance,
as
Rafael
mentions,
is
the
last
25
years
had
been
evolved
and
how?
What
was
the
main
reason
they
you
know.
Did
this
move
into
partial
ease?
Send
some
of
the
services
to
the
cloud
and
with
the
modern
technologies
was
approached
by
by
by
Raphael
and
his
team.
B
We
added
for
this
for
this
for
this
time,
for
this
presentation,
what
was
there
Colby
19
response
and
what
was
the
role
in
the
in
the
system
and
the
changes
that
they
need
to
made
or
system
that
they
need
to
create
in
a
very
short
period
of
time
in
order
to
respond
to
Brazilian
healthcare
system
needs?
And,
finally,
some
lesson
learned
we
don't
want
to.
B
C
So
this
is
important
information.
The
the
World
Health
Organization
recommends
one
doctor
per
a
thousand
people.
Only
sort
of
Brazil
has
this
indicator.
So
the
rest,
we
don't
have
this
situation,
so
our
health
care
system
is
very
difficult
to
maintain
and
we
have
to
deal
with
many
problems,
especially
now
in
Kavita
19,
Panda
Mia.
B
I
have
Rafael.
This
data
has
is
evolving
right
now,
with
the
current
situation
in
terms
of
be
translated
into
non-functional
requirements.
That
means
that
if
they
are
recruiting
more,
you
know,
doctors
and
so
on,
then
the
capacity
of
the
system
should
be
able
to
handle
these
are
used.
Are
you
already
have
seen,
and
it
spikes
in
the
performance
of
the
system
is
something
that
sir.
B
Don't
worry,
no
worry,
I
had
I
had
my
my
mute,
the
microphone
so
in
terms
of
not
fortunate
requirements
when
we
are
talking
about
the
system
capacity.
I
recall
that
you
were
mentioning
also
that
the
systems
artists
are
keeping,
are
keeping
a
and
not
common
growth
and
and
not
a
common
spikes
in
terms
of
usage
right.
So
right
now
are
uncommon
situations
in
the
systems,
and
you
you,
your
team,
has,
has
has
to
be
working
with
these
right.
Yes,.
C
I'm
gonna
show
at
the
end
the
solution
of
for
Covey's
19
in
response
and
Anna's
and
I
checked
now,
and
we
had
more
than
20,000
prescriptions
made
in
the
systems
in
two
weeks,
so
lots
of
doctors
using
the
system.
So
we
have
some
these
equalities
inequalities
here
when
the
the
budget
for
the
health
is.
C
C
So
I'm
gonna
show
here
the
main
actors
of
the
DOE
systems.
We
have
medicine
schools
and
read
residency
problems
that
the
people
becomes
doctors,
and
then
we
have
the
the
main,
the
main
practice
that
we
call
medical
practice.
Doctors
may
consultations
to
patients
in
some
place,
so
government
must
control,
regulates,
create
policies,
make
sanitary
surveillance
over
this
medical
price
practice
and
and
the
other
side
we
have
the
medicine
console.
A
C
A
C
C
C
C
C
So
our
our
base
system
is
at
the
Federal
Council,
with
the
national
special
special
inspections
platform
and
we
can
make
scheduling
and
control
execution.
We
have
dynamic
forms
with
checklists
images
for
notifications
and
can
make
reports
and
statistics
and
make
many
integrations
with
the
other
parts
of
the
government
and
at
the
rational
level
or
state
level.
We
deal
with
the
lifecycle
of
the
doctors
that
begins
when
they
start
to
practice
medicine
and
to
retirement.
C
C
A
C
B
This
this
dissection
about
I,
think
you
don't
see
that
the
last
two
two
bullet
points
because
of
the
images
but
one
of
the
newest
requirements,
because
you
know
this
is
a
living
system
that
has
been
evolved
over
the
over
over
the
past
more
than
10
years
or
so
initially,
when
the
requirement
started
and
to
to
to
to
to
migrate
to
the
cloud.
Without
this
cloud
native
approach,
I
would
say
that
the
requirement
came
like
two
years
ago,
but
it
actually
starts.
You
know
like
like
in
most
of
the
governments
in
Latin
America.
B
B
C
B
And
and
the
last
requirement
that
you
don't
you
don't
reach
to
you
to
to
read
in
the
presentation
ISM,
this
is
the
very
root
of
the
project
being
able
to
to
connect
with
different
third
party,
who
said
api's,
other
institutions,
banks
systems
and
so
on.
In
this
case,
firm
see
like
this
year
was
a
requirement
from
the
beginning
and
the
the
architecture
is.
You
are
seeing
here.
The
roadmap
allowed
to
have
easily
integration
and
which
and
with
security
in
mind,
so
that
is.
B
B
Okay,
in
terms
of
how
how
we
boost
as
we
like
to
call
in
the
team,
the
the
the
system
that
we
have
already
with
all
these
technologies
that
we
were
reading
here
for
all
of
those
that
is
maybe
the
first
time
that
are
joining
this
type
of
sessions.
I
think
you
all
have
hear
about
Java,
EE
and
since
the
last
two
years,
we
now
call
it
Jakarta
II.
B
B
So
every
time
you
hear
in
from
now
on
that
the
Jakarta
e
brand,
as
it
is,
we
are
talking
about,
as
we
informally
know,
as
Java
EE,
to
understand
why,
for
example,
in
this
case,
Rafael,
GVR
and
and
and
the
Brazilian
Hilliker
system
chooses
Jakarta
e
micro
profile
and
all
these
projects
patch
it
to
me,
we
need
to
understand
where
Jakarta
EE
is
in.
The
space
of
of
an
organization
in
this
case
is
under
the
umbrella
of
the
true
foundation.
B
B
If
you
want
more
information,
currently
it's
been
implemented
by
different
vendors
that
that
that
provide
support
in
this
case
to
to
some
of
the
ones
that
are
open
source,
most
of
them
open
source
projects
that
implement
this
I'm,
not
gonna,
go
directly
throughout
each
of
this
each
of
the
specification,
but
this
is
like
1,000
feet
of
where
it's
about
micro
file.
We
had
open
API
Rafael
mention
about
security.
We
have
JSON
web
token
propagation,
but
also
you
start
seeing
common
API
is
that
you
had
been
use.
B
If
you
had
been
a
Java,
EE
architect
developer
so
now,
which
are
cartel
you,
we
we
we,
we
base
the
foundation
of
the
community
by
definition
of
a
fifth
micro
file
on
Jakarta
ee,
so
we
have
CDI
Jason
P
Jackson
raised
a
zombie
and
obviously
you
can
put
this
on
top
of
JP
a
and
some
other
frameworks
that
and
other
api's
that
you
have
been
already
using.
So
this
is
how
the
pieces
of
the
entire
recipe
comes
together
and,
and
then
for
the
deployments
and
and
the
implementation
of
micro
file.
B
We
had
been
using
Apache
dummy
for
all
of
those
that
have
in
here
about
Apache
Tommy,
but
when
we
do
have
here,
Apache
Tomcat,
you
can
think
of
Apache
to
me,
like
Apache,
Tomcat,
plus
Java.
Ee
is
basically
built
from
our
patchy
components
and
microphone
compliant
is
what
profile
certified
in
version
6.
B
We
are
currently
working
on
the
Jakarta
ie9
and
you
can
follow
up,
contribute
and
consume
and
make
questions
be
at
the
open
channels
and
menu
list
on
the
Tommy,
dot,
Apache
dot
or
in
terms
of
the
technologies
of
the
of
this
application.
Server
that
we
are
using
in
the
project
we
have
the
jax-rs
Mike
profile,
flavor,
like
I,
will
say
it.
We
have
different
flavors
within
the
preg
and
all
these
api's
all
these
specifications.
If
you
have
been
developing
java
ee
now
with
jakarta
e,
we
have
the
same
right.
B
What
are
the
listeners
that
we
have
so
far?
Well,
I
can
give
you
examples
of
the
before
and
the
after
and
a
snip
of
code
about
a
couple
of
indicate
the
microphone
ones
which
are
the
newest
ones.
If
you
have
been
already
a
Java
developer
or
you
are
becoming
now
at
Jakarta
a
developer,
you
will
see
that
you
will
find
the
code
really
familiar
right.
B
So
that's
what
what
I
have
been
presenting
here
and
what
rafael
have
described
so
obviously
sensitive
information
with
the
project
files,
complex
customization,
I
have
the
properties
was
raided
by
the
by
by
the
system
and
also
how,
when,
when
you
start
thinking
about
how
to
migrate
some
of
some
part
of
your
system
to
the
cloud,
and
you
need
to
realize
that
you
will
have
changes
in
during
for
a
structured
workflow
as
Rafael
described.
Some
some
regions
are
the
plain
they're
on-premise
cloud
orders
are
opting
for
Google
or
Amazon
or
Oracle,
so
it
needs
in.
B
So
there
there
you
go
it's
it's
like
you
know,
it's
a
it's.
A
living
system
like
I,
think
most
of
the
system
nowadays
are,
and
they
have
require
lot
of
changes
depending
of
their
requirements.
Thank
You
Rafael
for
I
forgot
about
that
part.
Thank
you
much.
We
also
have
the
advantage
of
applying
micro
profile
config
what
we
ended
up
as
you're
reading
here
this
this
collation
of
the
system,
the
tracking
of
the
of
the
properties,
the
ability
that
you
can
change
configuration
and
the
server
pick
it
up
on
the
fly
starting
the
containers.
B
If
we
are
the
playing
on
the
cloud
thinking,
imagine
we
are
talking
about
a
docker
environment
variables.
We
can.
We
can
have
this
swimlanes
integration
between
what
they
currently
the
previous
system,
with
Java
EE
root
in
their
architecture,
took
advantage
now
with
microphone,
jack
art
IE.
As
we
were
mentioning.
This
is
the
small
snip
of
code.
You
will
see
a
couple
annotations
that
are
you
really
familiar
with
so,
for
example,
inject,
and
then
there
is
one
that
you
haven't
seen.
B
Yet
if
you
haven't
go
to
check
micro
profile
configuration,
which
is
the
app
config
property
which
basically
is
in
this
example,
show
you
how
easy
is
to
obtain.
Imagine
that
this
is
running
inside
of
a
docker
container.
You
will
pick
it
up
from
the
environment
variables
if
you
configured
that
to
work
to
enable
the
lock
and
you
can
change
that
on
the
fly.
There
is
also,
in
this
case
the
injection
of
the
JSON
web
tokens.
So
again,
this
allows
to
have
easy
the
development
and
take
advantage
of
all
that
to
standardization
and
integration.
B
Then
we
have
also
the
health
check
and
plus
metrics
before
this
modernization
process
is
start.
We
have
a
lot
of
manual
process
third-party
tools
that
were
implemented
by
different
deployments
of
the
solution.
That's
why
we
add
their
dispersed
monitoring,
so
it
was
really
hard
to
trace
and-
and
this
allow
us
to
be
more
reactive
instead
of
proactively
checking
the
status
of
the
of
the
overall
system,
with
the
health
check
and
metrics
from
from
micro
file
implementation
point
of
view.
Now
we
provide
a
centralized
JSON
base
alerts.
B
So,
even
though
we
as
Rafael
mention
is
Santa,
Catarina
have
to
want
to
have
their
own
dashboards
or
their
own
metrics.
The
main
source
of
data
is
coming
in
a
standardized
format,
in
this
case
JSON
JSON
and
then
kind
produced
the
debut
word
that
they
want
in
order
to
obtain
that
really
really
simplest.
B
So
that
is
something
that
application
is
delivering
without
impacting
the
performance
and
so
on
like
if,
instead,
you
need
to
install
agents
or
some
some
other
tools
that
are
outside
this
is
again
another
a
snip
of
code.
The
new,
the
new
annotation
that
you
are
seeing
here
is
the
health
in
this
case
and
then
the
definition
of
what
it
means
for
us.
B
As
a
user
of
or
administrated
ministration
of
the
system
to
this
to
say,
the
system
is
held,
it
doesn't
it's
not
just
the
common
okay
is
on
of,
but
actually
what
that
means
in
this
case,
you're,
seeing
how
we
can
define
custom
health
checks
like
checking
if
the
database
in
this
example
is
up
and
running
and
how
much
time
is
taking
is
taking,
and
we
can
also
aggregate
different
kind
of
office
status.
So,
for
example,
just
because
the
database
is
on
that
doesn't
mean
the
system
is
working
right.
B
If
we
depend
on
a
third
party
services,
we
can
extend
this,
and
maybe
two
or
three
more
health
checks
are
actually
will
give
you
an
OK.
If
they
evolve,
they
are
akai
returning.
Ok,
that
will
give
you
a
better
understanding
of
the
health
of
the
system.
So
is
very
extensible,
and
if
you
are
interesting
in
this
part
check
out
the
micro
file
he'll
check
an
API,
can
you
describe
it
a
little
bit
here?
Raphael
the
images
that
we
are
seeing
on
the
screen.
C
B
And,
as
you
can
see
here,
we
didn't
reinvent
the
wheel
in
sense
of
let's
build
everything
from
the
ground.
We
basically
leverage
them.
My
microphone
file,
health
check
to
provide
us
the
data,
and
in
this
case
the
UI
is
just
a
layer
that
allowed
to
create
custom
dashboard
based
on
the
current
ones
that
that
the
system
has
so
it's
extendable.
In
that
way,
astro
file,
where
mentions,
which
is
it
has
been
written,
has
had
a
really
great
impact
on
the
final
user.
B
There
was
a
questions
that
I
just
saw
from
Sergey
he's
asking
hi
there
I'm
really
interested
how
you
planning
to
implement
OAuth
2.0
with
Jakarta
in
your
system.
So
that
is
an
entirely
that
topic
is
really
a
topic
that
I
really
like
and
it's
for
an
entire
session,
but
we
actually
are
in
the
part
of
the
presentation
when
we
have
about
what
happened
with
Jade
ability
on
tin
education,
and
so
hopefully
that
will
help
you
to
to
better
understand
how
we
are
actually
enabling
these.
We
did
a
the
legacy
system.
B
Thank
you
for
the
question
Sergey
and
feel
free
to
send
more
questions
either
throughout
the
chat
or
the
dedicated
Q&A
sections
on
this
on
the
platform.
So
what
we
had
before
was
basic
health
entick
ation
with
session
management.
Obviously,
if
we
are
talking
about
cloud
deployment
and
all
that
you
know
we,
the
challenges
started
to
arise
a
roast
like,
for
example,
we
need
a
stable
security,
how
we
will
manage
the
authentication
even
between
micro-service
orca
stations.
B
You
know
when
we
are
talking
about
all
set
from
business
to
business,
point
of
view
and
in
terms
of
the
architecture.
That
was
something
that
was
our
requirement
and
I
start.
You
know:
stop
in
the
the
necessity
of
have
a
single,
a
single
point
of
failure,
so
go
out.
2.0
was
obviously
widely
adopted
by
that
time
and
the
industry,
so
we
need
from
the
beginning
of
the
break
that
we
have
to
do
to
find
something
that
will
allow
us
to
to
integrate
this.
This
type
of
security
in
the
system.
B
So
after
implementing
in
this
case
the
Micra
terminate
ability
specification
for
from
micro
profile,
I
think
that's
how
microphone
file
can
can
can
talk.
Each
other
and
integrate
with
jacquard
yeah
by
year,
jakarta
ii
applications.
We
ended
up
having
an
estate,
less
security,
we
managed
to
to
have
a
synchronous
integration
between
micro
services
and
and
also
you
know,
to
keep
the
load
of
and
all
the
benefits
of
all
2.0.
That
is
removing
that
single
point
of
failure,
disintegrate
also
simply
with
the
API.
You
get
way
that
we
mentioned
the
trash
from
API
gateway.
B
So
we
had
from
that
point
of
view
everything
that
we
need
to
allow
our
current
or
legacy
system
to
be
modernized
with
this
technology
or
our
2.0,
and
also
using
the
API
way
to
integrate
third
party
system,
as
Raphael
will
explain
later.
This
is
a
snippet
code
about
what
the
microf
well
JWT
specification
is.
You
still
have
you
know
the
common
jakarta
ee
java
java
ee
kind
of
annotations
@inject.
We
are
injecting
the
json
web
token
that
the
container
is
providing
that
to
us.
We
don't
need
to
do
any
other
heavy
code
integration.
B
Obviously,
you
can
configure
this
with
micro
program
with
micro
profile
config,
which
is
what
you
are
seeing
here,
for
example,
for
the
law
enable
and-
and
basically
then
you
use
the
token
servers
to
get
information
you
can.
In
this
example,
we
are
checking
one
of
the
claims
of
the
judge
that
we
are
obtained
in
this
case.
If
the
email
is
present
or
if
not,
we,
we
will
send
a
message
indicating
that
the
judge
is
lacking.
B
This
is
just
an
example,
but,
as
you
can
see,
is
it's
easy
to
read
Java
code
without
any
any
any
much
plumping?
The
configuration
is
pretty
straightforward
when
you,
when
you
start
utilizing
the
microphone
at
the
ability
and
again
this
is
this
is
the
specification
there
is
the
TCK.
It
has
compatibility
kit
and
you
have
the
different
open
source
projects
and
also
benders
who
support
those
breaks
to
to
implement
these
so
effectively.
B
Speaking
as
you
were
used
to
it
with
Java
EE
applications
Jakarta,
he
shares
the
same
concept
of
you
know,
deployed
on
different
application
servers
depending
on
your
needs.
Rafael
is
already
explain.
Different
different
consoles
have
different
requirements
and,
in
this
case,
micro
file
also
showed
that
that
integration
and
that
standardization
in
terms
of
security,
we
are
having
the
same
an
example
of
how,
with
the
code
VIN
19
response,
this
was
really
helpful.
Raphael.
C
The
our
client
has
subscription,
with
some
medical
knowledge,
databases
to
practice
a
clinic
practical
rehabilitation,
research
in
general,
and
then
they
wanted
to
to
deliver
to
their
doctors,
resister
doctors,
the
access,
but
they
have
only
one
password
for
the
systems,
and
then
we
will
hide
this.
The
real
endpoint
with
password
and
things
like
that
inside
gateway,
and
then
our
system
depends.
C
If
the
the
guy
is
logging
on
on
our
system,
authenticated,
they
can
access
or
don't
access
and
and
then
we
have
control
which
who
who's
the
guy
that
are
using
our
data,
the
the
subscription
who
is
the
guy,
who
is
the
doctor?
They
are
making
some
bridge
research
between
using
the
system
of
the
concept.
So
now
they
have
the
control
who
culture
of
the
use
of
this
subscription
and
and
their
doctors
with
one
more
one,
more
solution.
B
Yeah
and-
and
you
see
the
let's
repeal
mentioned
advantage
here-
is
that
old
all
this
specification
that
we
just
saw
they
name-
you
know
the
the
reporting
and
the
capability
of
scene,
health
checks
and
also
metrics.
All
that
is
integrated.
So
you
know
it's
not
just
the
fact
that
okay,
we
need
to
allow
their
power
integration,
so
people
can
kind
of
start
looking
at
this
with
your
existing
credentials
and
second
factor
authentication,
but
also,
let's
analyze,
how
these
being
used.
So
that
is.
C
A
B
B
So,
as
you
can
see,
well,
not
the
best
ability
of
code
and
I
think
most
of
you
sometimes
go
to
run
a
situation
where
you
are
actually
developing
the
service,
but
at
the
same
time,
do
you
need
to
create
the
consumer
of
that
service,
not
just
for
your
tests,
but
also
to
provide
not
just
the
API,
but
also
how
the
decline
and
the
consumer
API
will
interact.
So
so
we
needed
to
be
agile
in
order
to
not
redo
the
same
work
twice
so
with
with
the
rest,
client
API,
the
main
advantage.
B
If
that
is
types
of
it,
allow
us
to
have
a
types
of
approach.
We
basically
just
reuse
the
interfaces
or
we
create
interfaces
based
on
the
on
the
rest,
endpoints
code
that
we
already
have
so
that
allows
you
to
have
to
have
an
easy
change
in
your
between
the
updates
or
the
increase
of
rationality.
So
the
client
change
change.
B
At
the
same
time,
the
main
code
is
changing,
so
you
don't
need
to
keep
keep
try
to
keep
matching
what
the
client
shall
consume
if
you
have
any
feature,
but
because
they
are
really
close
together,
so
they
can
iterate
it
and
then,
as
a
collateral,
huge
benefit.
The
JWT,
propagation
and
integration
is
something
really
really
simple.
To
actually
add.
If
you
are
using
this,
let's
see
this
example.
In
this
case
we
have
this
interface,
sip
research,
client.
B
You
only
have
this
annotation,
then
you
want,
it
is
registered
rest
client,
which
actually,
we
literally
copy
our
endpoints.
We
convert
that
into
interface
and
just
by
added
an
annotation,
and
then
because
these
are
interface,
you
don't
have
the
the
main
logic,
but
just
the
signature
of
the
methods.
Just
with
this,
you
already
have
what
you
need
in
order
to
use
this
this
client
in
your
code,
so
the
next
slide
will
show
you
how
will
show
us
how
we
actually
use
this
interface
to
to
start
consuming
our
own
services
on
another
micro
service.
B
So
the
line
I,
don't
know
how
you
can
see
my
mouse,
but
yes,
I,
see
I,
think
you
can
see.
So
we
have,
for
example,
another
one,
the
doctor
resource
client,
this
is
very
familiar.
These
are
non-union.
Notation
is
the
ones
that
we
have
been
uses
in
the
last
20
years,
so
this
hasn't
changed.
Anything.
The
only
thing
here
is
that
we
are
adding
the
register.
Rest
client,
which
is
actually
saying,
and
you
can
see
the
package
or
eclipse
that
micro
profile
rest
client,
injection,
prehistoric,
client.
B
B
The
rest
client
annotation,
in
which
you
specify
the
previous
interface
that
we
define,
and
but
just
from
that,
the
you
would
liberate
the
container
the
ability
to
to
build
our
client
based
on
the
interface
and
then
we
kind
of
started
using
as
in
in
a
normal
Java,
natural,
workflow
and
and
and
code
will
flow.
The
interaction
with
that.
B
So
once
we
have
the
clear
here:
are
our
client
and
inject
the
reference
to
that
client,
which
basically,
we
just
say,
okay,
give
me
the
list
of
doctors,
and
he
knows
where
to
find
that,
because
if
we
go
back,
you
will
see
that
we
have
the
pads,
we
can
fire,
we
can
send
parameters
and
so
on.
So
it's
still
I'm.
Sorry,
it
still
is
it's
a
really
natural
I
will
say
a
step
for
our
developers.
How
we
can
approach
now
with
with
with
this
rest
client
capabilities,
how
to
persist
new
doctor.
B
A
new
example
is
as
simple
as
just
you
create
the
object.
You
maybe
power
process,
something
that
you
want,
and
then
you
send
that
in
a
not
type
save.
Let
me
check
if
we
have
other
questions.
Okay,
now
so
far,
we
in
terms
of
open
API.
This
is
really
common.
How
you
document
your
your
micro-services?
How
to
document
your
rest
services,
I,
will
say
we
also
needed
to
have
a
way
to
provide
documentation
for
third-party
integrations
that
wanted
to
consume
our
api's.
B
Before
we
have
the
legacy
system
didn't
have
well-documented.
It
was
not
so
standardized
so
remember.
This
is
was
more
than
10
years
ago,
so
yeah
we
were
coming
from
so
Web
Services
and
have
the
wisdom
files
and
all
that,
but
for
the
cloud
part
of
the
system
that
we
have
been
developing
and
migrating
from
the
main
monolithic.
B
Well,
we
needed
obviously
to
to
have
a
rest
approach
and
in
this
case,
open
api
was
the
response,
probably
now
as
swagger.
If
you
are
familiar
with
swagger,
well
open
api
from
version
triple
zero.
Is
is
the
standard
for
that
what
we
gained
after
that,
after
the
implementation
of
our
open
api?
Well,
first,
we
have
the
standardization.
B
We
were
worried
about
how
much
clomping
we
will
need
to
do
in
our
existing
code
to
allow
this
to
work,
but
we
were
really
surprised
to
find
that
the
change
it
was
was
not
something
ridiculous
with
our
munch
of
effort,
it
was
really
simple.
I
will
say
it.
Obviously,
when
you
are
extending
your
your
current
annotation
with
more
annotation,
sometimes
the
code
start
to
be
a
little
bit
bigger,
so
you
need
to
define
at
least
the
minimum
or
create
some
other
annotations
in
order
to
provide
that
automatically.
B
But
then
it
allow
us
to
to
have
an
API.
First
is
an
approach
which
is
something
that
most
of
companies
in
the
last
few
years
has
been
fighting
with.
This
is
not
simple
to
have
to
have
this
mind,
switch
about
okay,
let's
design,
first,
the
REST
API
and
then
just
develop
the
test,
and
finally,
we
actually
are
going
to
develop
the
API,
and
mainly
in
these
times,
when
three
three
months
ago,
Brazil
had
to
develop
a
couple
of
new
endpoints.
How
we
can
respond
to
that.
B
B
Just
by
having
that
we
can
send
already
the
API
the
open,
API
documentation
to
to
third-party
system
that
will
consume
our
API
s,
so
they
can
start
creating
their
clients
if
they
don't
if
they
are
in
different
programming
languages
and
in
the
case
when
they
are
using
Java
well,
remember
they
they
micro
micro
file
and
rest
client.
So
it's
really
easy.
At
the
same
time,
you
just
create
the
the
definition
of
what
are
the
inputs
of
your
service.
B
You
can
create
the
interface
and
create
from
that
API
that
we
give
to
these
third-party
services
the
documentation
with
open
API,
and
then
we
can
in
parallel,
we
can
start
to
actually
code
the
the
logic
of
what
the
end,
which
will
do.
We
can
just
mock
up
services
and
all
that,
but
again,
this
is
just
an
example
of
how
this
will
allow
us
to
easily
these
do
perform
this.
This
kind
of
migration
to
the
cloud.
B
If
you
are
familiar
with
open
API,
well,
it's
basically
what
you're
seeing
here
new
annotations
in
this.
This
is
nip
of
code,
for
example
the
operation,
the
description
of
the
operation.
What
this
API
is
intended
to
do,
where
are
the
codes
that
you're
gonna
have
and
descriptions
about
that,
and
we
can
define
a
schemas
classes
and
from
there
they
get
a
notation
that
produces
the
path
that
is
Jack's
rest,
so
that
hasn't
changed.
This
is
the
same.
B
This
is
just
a
screenshot
of
a
common
used,
open,
API
UI
when
you
can
actually
test
your
services,
while
you
are
coding
or
actually
you
can
publish
this
with
with
these
third
parties,
organizations
or
entities
who
wants
to
consumer
or
endpoints
Raphael
is
going
to
give
describers
a
little
bit.
We
have-we
have
been
mentioned
in
that
the
last
three
months.
We
have
been
able
to
create
new
systems,
new
API
in
really
short
period
of
time,.
C
Yes,
actually,
so
we
think
the
co
feed
quarantine,
quarantine
start
here
in
end
of
March
and
then
the
government
make
temporary
law
that
supports
telemedicine,
because
doctors
stay
at
home
in
home
office
and
can't
make
prescriptions
or
consultations
to
their
first
patients.
So
they
make
special
law
to
regulate.
And
then
we
receive
a
call.
C
B
C
Doctors
had
to
use
some
platform
some
system
that
they
can
make
prescription,
put
some
information
about
the
patients,
but
this
is
must
be
digital
online,
not
in
hand.
So
we
made
a
system
that
the
doctor
and
meet
at
least
a
prescription
to
the
patients
and
the
patient
received
is
in
whatsapp
or
email,
and
then
the
patient
go
to
the
pharmacy
and
present
the
prescription.
So
the
the
the
the
pharmacy
can
check
the
validation
if
it
that
prescription
is
real
and
this
the
whole
system.
We
made
it
in
five
days
why?
C
We,
because
we
we
had
a
platform
already
running
with
monitoring
with
all
those
stuff
that
Cesar
showed
to
us
and
we
make
integration
with
the
doctor
space.
So
the
doctor
used
the
logging
of
our
system
or
sister
we
can
check
in
the
federal
company's
database.
If
that
pharmacy
is,
is
good
and
the
the
special
dot
databases
of
pharmacy
database
we
can.
C
We
can
integrate
with
Google
Authenticator
to
put
more
secure
security
in
the
system
we
to
factor
out
education
and
we
put
encryption
of
sensitive
data,
because
now
we
are
dealing
with
some
some
medicine
very
strong
and
we
have
to
prevent
fraud.
We
have
to
prevent
the
data
of
the
the
patient's.
You
know
it's
very
very
danger
data
to
do.
B
Yeah
so
I
think
the
main
takeaway
here
is
that
you
know
the
the
response
needs
to
be
fast.
People
needed
their
medicines.
The
government
needed
to
be
sure
that
the
the
medicines
were
allocated
to
the
actual
patient
that
needed
and
at
the
same
time,
this
integration
with
the
pharmacy
didn't
exist
before
the
Hartmann
sees
had
their
own
system.
B
So
it
was
a
huge
effort,
previous
to
that
five
days
of
development,
in
terms
of
you
know,
I've
been
all
together
see
what
which
system
they
have
some
some
which
kind
of
integration
they
were
already
offering
to
us,
and
then
we
needed
to
present
to
them
the
integration,
the
documentation
and
all
that
I
see.
There
is
a
criminal's,
a
question
also
from
sir
Jim.
I
will
address
that
later.
It's
kind
of
relating
this
because
it
will
touch
the
risk
line.
B
But
but
yes,
as
you
know,
Raphael
already
described,
is
it's
a
sizable
workflow?
But
you
know
every
time
you
need
to
integrate
something
in
computer
science.
You
know
it's
gonna,
be
it's
gonna,
have
challenges,
and,
and
so
far
we
have
been
able
to
have
these
quick
response
due
to
current
circumstances
that
the
country
has.
C
This
is
this
is
how
we
encrypt
the
data
and
the
next
slide.
I'm
sure
we
we
made
it
almost
20,000
prescription
since
8th
of
April
wait.
So
the
system
is
where
is
Hackney
used
and
almost
65,000
validations,
so
the
patients
and
the
the
pharmacy
get
the
prescription,
use
the
prescription
in
May
and
need
to
validate
them.
B
Yeah,
so
they
use
a
cure
code
either.
You
know
you
go
to
the
pharmacy
and
in
the
pharmacy
they
read
this
QR
code
that
basically
validates
again
our
system
if
that
medicine
was
already
delivered
to
another
patient
or
if
it's
still
valid
of.
If
you
doctor,
prescribe
you
or
extend
you
the
amount
of
medicine
that
you
will
need,
so
we
have
a
thank
you
very
much.
We
are
just
at
the
edge
of
the
of
the
of
the
hour.
We
have
a
really
good
question
good
question
about
surgery.
B
Thank
you
much
for
the
question
about
GTOs
doctors,
for
example,
are
you
sure
DT
owes
between
services
or
keeping
separate
videos
for
client
and
server?
A
really
good
question,
so
basically
yeah
the
DTO
and
the
client
needs
to
be
on
a
separate,
API
or
jar
file.
I
will
say
because
eventually,
when
you
are,
if
you
are
delivering
your
client
API,
that
will
need
to
have
the
tto.
B
B
So
much
Thank,
You,
Rafael
I,
think
this
I
hope
this
session
will
allow
allow
you
to
to
the
viewers
to
do
not
understand
and
in
the
first
part
of
the
presentation,
the
complexity
that
we
deal
with
in
in
the
system
and
actually
also
within
the
current
needs,
Atika
the
Brazil
has
and
how
we
are
trying
to
keep
moving
forward
this
living
system
with
modern
technologies
that
we
just
saw
so
yeah.
That's
that's
pretty
much
from
my
part.