This
page
is
part
of
the
FHIR
Specification
(v3.0.2:
STU
3).
The
current
version
which
supercedes
this
version
is
5.0.0
.
For
a
full
list
Continuous
Integration
Build
of
available
versions,
see
FHIR
(will
be
incorrect/inconsistent
at
times).
See
the
Directory
of
published
versions
.
Page
versions:
R5
R4B
R4
R3
R2
Responsible
Owner:
FHIR
Infrastructure
Work
Group
|
|
HL7 has produced a number of other standards that don't overlap with FHIR as closely as those listed above, primarily because they aren't focused solely on information exchange. However, they deserve a brief mention:
This specification defines a number of functional behaviors for Electronic Health Record systems. FHIR is a healthcare information exchange standard that can be used to satisfy some of these functional behaviors. Details on how FHIR fits into the EHR-FM can be found here
CCOW
is
a
standard
for
allowing
independent
systems
FHIRcast
synchronizes
healthcare
applications
in
real
time
to
show
the
same
clinical
content
to
synchronize
context
on
a
single
workstation,
providing
common
user.
For
example,
a
seamless
interface
for
radiologist
often
works
in
three
disparate
applications
at
the
user
same
time
(a
radiology
information
system,
a
PACS
and
a
dictation
system),
she
wants
each
of
that
workstation
(e.g.
ensuring
consistent
user
authentication,
these
three
systems
to
display
of
the
same
patient,
display
of
study
or
patient
at
the
same
order,
etc.)
In
theory,
FHIR
resources
could
be
used
as
time.
Note
that
HL7
had
an
alternative
earlier
specification
called
CCOW
implementation
technology,
however
the
business
case
(Clinical
Context
Object
Workgroup)
that
allowed
for
doing
this
is
not
clear.
CCOW
profiles
include
HL7
v2
mappings.
These
mappings
can
be
used
independent
systems
to
help
identify
the
equivalent
FHIR
data
elements
when
establishing
CCOW
linkages
in
FHIR-based
systems.
synchronize
context
on
a
single
workstation,
but
this
has
been
retired
and
replaced
by
FHIRcast.
Arden Syntax is a language for defining decision support rules. These rules reference data elements that are used as part of the decision making process. However, the specification does not define how these data elements are identified. FHIR element and extension identifiers would provide one mechanism for identifying the relevant data elements.
The Virtual Medical Record is a draft specification under development by HL7 that also serves the decision support space. It defines a logical medical record that decision support rules can be constructed against. At present, this model is a custom model created specifically for VMR. However, the Decision Support work group is evaluating the possibility of using FHIR as a structure for future versions of the specification.