This
is
the
FHIR
R4
Mixed
Normative/Trial
Use
Ballot
#1,
and
the
version
for
the
Cologne
Connectathon
in
May
2018.
The
current
version
is
R3
.
See
the
ballot
introduction
for
details
about
the
ballot.
For
a
full
list
of
available
versions,
see
the
Directory
of
published
versions
and
Timelines
for
an
explanation
of
STU
and
other
statuses.

1.3
Profiles
defined
as
part
of
FHIR

This
specification
is
a
common
platform
standard
that
must
be
adapted
to
particular
use
cases
.
Some
particular
use
cases
are
common
or
important
enough
to
be
described
as
a
part
of
the
specification
itself.
These
are
published
as
a
"Profile"
-
a
groups
of
Structure
Definitions
(Constraints,
(profiles
or
an
Extension
definition),
extensions),
which
are
often
found
in
implementation
guides,
along
with
Value
Sets
,
newly
defined
search
parameters
and
examples
that
are
all
defined
with
a
common
purpose.
Additional
profiles
and
extensions
may
be
registered
on
the
HL7
FHIR
registry
at
http://hl7.org/fhir/registry
http://registry.fhir.org

This
profile
defines
extensions
that
can
be
used
to
provide
alignment
with
the
Event
workflow
pattern
data
elements
for
concepts
that
may
be
generally
applicable
but
may
be
sufficiently
uncommon
that
they
are
more
appropriate
to
include
as
extensions
than
as
core
properties
of
the
resource.
See
the
workflow
module
for
more
discussion
about
this
specification
that
are
typically
involved
in
workflow.

This
profile
defines
extensions
that
can
be
used
to
provide
alignment
with
the
Event
workflow
pattern
data
elements
for
concepts
that
may
be
generally
applicable
but
may
be
sufficiently
uncommon
that
they
are
more
appropriate
to
include
as
extensions
than
as
core
properties
of
the
resource.
See
the
workflow
module
for
more
discussion
about
this
specification
that
are
typically
involved
in
workflow.

This
profile
defines
extensions
that
can
be
used
to
provide
alignment
with
the
Event
and
Request
workflow
pattern
data
elements
for
concepts
that
may
be
generally
applicable
but
may
be
sufficiently
uncommon
that
they
are
more
appropriate
to
include
as
extensions
than
as
core
properties
of
the
resource.
See
the
workflow
module
for
more
discussion
about
this
specification
that
are
typically
involved
in
workflow.

The
CDA-in-FHIR
Clinical
Document
profile
constrains
Composition
to
match
CDA
and
specify
a
clinical
document.
document
(matching
CDA).
The
base
Composition
is
a
general
resource
for
compositions
or
documents
about
any
kind
of
subject
that
might
be
encountered
in
healthcare
including
such
things
as
guidelines,
medicines,
etc.
A
clinical
document
is
focused
on
documents
related
to
the
provision
of
care
process,
where
the
subject
is
a
patient,
a
group
of
patients,
or
a
closely
related
concept.
A
clinical
document
has
additional
requirements
around
confidentiality
that
do
not
apply
in
the
same
way
to
other
kinds
of
documents
documents.

Adds
additional
information
to
a
family
member
history
supporting
both
the
capture
of
mother/father
relationships
as
well
as
additional
observations
necessary
to
enable
genetics-based
risk
analysis
for
patients