<del class="diff-old">
This
page
is
part
of
the
FHIR
Specification
(v0.0.82:
DSTU
1).
The
current
version
which
supercedes
this
version
is
5.0.0
.
For
a
full
list
of
available
versions,
see
the
Directory
of
published
versions
2.0
Implementation
Exchange
Frameworks
Define
how
Resources
are
exchanged.
RESTful
API
(HTTP)
Search
/
Query
Documents
Messaging
Services
(SOA)
Support
Implementation
Support.
Downloads
-
Schemas,
Code,
Tools
Managing
Resource
Identity
Push
vs
Pull
Support
Links
Using
FHIR
Making
use
of
FHIR.
Common
Use
Cases
Profiles
Defined
as
part
of
FHIR
Security
&amp;
Security
Labels
Integrated
Examples
2.0.1
Implementers
Safety
Check
List
FHIR
is
as
simple
to
implement
as
we
know
how
to
make
it.
However,
due
to
the
nature
of
healthcare,
and
healthcare
processes,
and
cultural
concerns,
there
are
a
number
of
features
in
FHIR
that
implementers
are
obliged
to
consider
in
order
to
implement
safe
systems.
This
section
is
a
check
list
to
help
implementers
be
sure
that
they've
considered
all
the
parts
of
FHIR
that
impact
on
their
system
design
with
regard
to
safety.
Production
exchange
of
patient
or
other
sensitive
data
will
always
use
some
form
of
encryption
on
the
wire
For
each
resource
that
my
system
handles,
I've
reviewed
the
Modifier
elements
My
system
checks
for
modifierExtension
elements
My
system
supports
elements
labelled
as
&quot;must-support&quot;
in
the
Profiles
that
apply
to
my
system
My
system
can
render
narratives
properly
(if/when
they
are
used)
My
system
has
documented
how
distributed
resource
identification
works
in
it's
relevant
contexts
of
use
My
system
uses
the
right
security
labels
where
appropriate
When
other
systems
return
http
errors
from
the
RESTful
API
or
from
the
Mailbox
(perhaps
using
Operation
Outcome
),
my
system
checks
for
them
and
handles
them
appropriately
My
system
publishes
a
conformance
statement
so
other
implementers
know
what
it
does
My
system
displays
narrative
safely
with
no
security
issues
(if
it
displayz
it
at
all)
Obviously
this
list
is
only
a
small
part
of
the
overall
safety
check
list
for
an
application,
which
will
have
checks
regarding
jurisdictionally
mandated
policies,
internal
integrity,
etc.
&copy;
HL7.org
2011+.
FHIR
DSTU
(v0.0.82.2943)
generated
on
Tue,
Sep
30,
2014
18:10+1000.
Links:
What's
a
DSTU?
|
Version
History
|
|
Propose
a
change
var
disqus_shortname
=
'fhirdstu';(function()
{var
dsq
=
document.createElement('script');
dsq.type
=
'text/javascript';
dsq.async
=
true;dsq.src
=
'//'
+
disqus_shortname
+
'.disqus.com/embed.js';(document.getElementsByTagName('head')[0]
||
document.getElementsByTagName('body')[0]).appendChild(dsq);
})();
Please
enable
JavaScript
to
view
the
comments
powered
by
Disqus.
comments
powered
by
Disqus
var
_gaq
=
_gaq
||
[];
_gaq.push(['_setAccount',
'UA-676355-1']);
_gaq.push(['_setDomainName',
'.hl7.org']);
_gaq.push(['_trackPageview']);
(function()
{
var
ga
=
document.createElement('script');
ga.type
=
'text/javascript';
ga.async
=
true;
ga.src
=
('https:'
==
document.location.protocol
?
'https://ssl'
:
'http://www')
+
'.google-analytics.com/ga.js';
var
s
=
document.getElementsByTagName('script')[0];
s.parentNode.insertBefore(ga,
s);
})();
</del>