This
page
is
part
of
the
FHIR
Specification
(v4.0.1:
R4
(v5.0.0:
R5
-
Mixed
Normative
and
STU
)
).
This
is
the
current
published
version
in
it's
permanent
home
(it
will
always
be
available
at
this
URL).
The
current
version
which
supercedes
this
version
is
5.0.0
.
For
a
full
list
of
available
versions,
see
the
Directory
of
published
versions
.
Page
versions:
R5
R4B
R4
FHIR
Management
Group
|
Maturity Level : N/A | Standards Status : Informative |
FHIR
Release
5
will
not
be
submitted
to
ANSI
Accredited
Standards
Development
Organization.
As
such,
ANSI
reviews
HL7
processes
both
in
general,
and
also
specifically
with
regard
to
each
standard.
ANSI
has
certified
that
portions
of
this
release
of
FHIR
(Release
4)
met
its
requirements
for
development
of
a
formal
standard.
Given
that
many
areas
of
the
FHIR
specification
are
still
undergoing
Trial
Use
by
the
HL7
Community,
and
hence
are
not
ready
for
balloting
consideration
as
a
formal
ANSI
standard,
and
in
order
to
manage
the
processes
around
the
ballot
process,
four
different
portions
of
this
specification
were
balloted
as
ANSI
Normative
Specifications:
Infrastructure
The
core
framework
on
which
FHIR
solutions
depend
(Abstract
base
types,
data
types,
formats,
standard.
None
of
the
RESTful
API,
and
new
content
and
typing
rules)
Conformance
The
terminology
infrastructure
and
the
base
resources
that
define
FHIR
implementations
and
that
represent
how
the
specification,
and
conformance
to
it,
in
R5
is
defined
Patient
The
Patient
resource
and
related
content
Observation
The
Observation
resource
considered
Normative,
and
related
content
For
will
be
subject
for
futher
review
during
the
purposes
of
American
National
Standards,
each
of
these
is
an
independent
standard,
review
and
the
other
parts
of
the
specification
do
not
contain
requirements
necessary
ballot
process
for
conformance
to
the
formal
standard.
Given
Release
6.
Note
that
the
Normative
parts
of
the
standard
are
still
a
subset
of
what
implementers
need
to
use,
implementers
are
generally
focusing
on
conforming
to
FHIR
R4
as
a
whole
rather
than
the
formal
standards.
Future
versions
of
this
specification
content
that
was
normative
for
Release
4
remains
in
effect
normative,
and
will
extend
be
treated
accordingly
during
the
coverage
of
format
standards.
R6
process.