This
is
5.0.0
.
For
a
full
list
the
Continuous
Integration
Build
of
available
versions,
see
FHIR
(will
be
incorrect/inconsistent
at
times).
See
the
Directory
of
published
versions
The
severity
of
the
audit
entry.
These
codes
are
derived
from
the
SysLog
header,
PRI.
http://tools.ietf.org/html/rfc5424#appendix-A.3
May be used to represent additional information that is not part of the basic definition
of the element. In order to make the use of extensions safe and manageable, there is a
strict set of governance applied to the definition and use of extensions. Though any
implementer is allowed to define an extension, there is a set of requirements that SHALL
be met as part of the definition of the extension.
There can be no stigma associated with the use of extensions by any application, project,
or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
The use of extensions is what allows the FHIR specification to retain a core level of
simplicity for everyone.
The definition may point directly to a computable or human-readable definition of the
extensibility codes, or it may be a logical URI as declared in some other specification.
The definition should be version specific. This will ideally be the URI for the Resource
Profile defining the extension, with the code for the extension after a #.
Value of extension - may be a resource or one of a constrained set of the data types (see
Extensibility in the spec for list).
</StructureDefinition>
Usage
note:
every
effort
has
been
made
This
case-sensitive
code
system
http://hl7.org/fhir/audit-event-severity
defines
the
following
codes:
Code
Display
Definition
Copy
emergency
Emergency
System
is
unusable.
e.g.,
This
level
SHOULD
only
be
reported
by
infrastructure
and
SHOULD
NOT
be
used
by
applications.
alert
Alert
Notification
SHOULD
be
sent
to
ensure
that
trigger
action
be
taken.
e.g.,
Loss
of
the
examples
are
correct
primary
network
connection
needing
attention.
critical
Critical
Critical
conditions.
e.g.,
A
failure
in
the
system's
primary
application
that
will
reset
automatically.
error
Error
Error
conditions.
e.g.,
An
application
has
exceeded
its
file
storage
limit
and
useful,
attempts
to
write
are
failing.
warning
Warning
Warning
conditions.
May
indicate
that
an
error
will
occur
if
action
is
not
taken.
e.g.,
A
non-root
file
system
has
only
2GB
remaining.
notice
Notice
Notice
messages.
Normal
but
they
significant
condition.
Events
that
are
unusual,
but
not
a
normative
error
conditions.
informational
Informational
Normal
operational
messages
that
require
no
action.
e.g.,
An
application
has
started,
paused,
or
ended
successfully.
debug
Debug
Debug-level
messages.
Information
useful
to
developers
for
debugging
the
application.
Explanation
of
the
specification.
columns
that
may
appear
on
this
page:
Level
A
few
code
lists
that
FHIR
defines
are
hierarchical
-
each
code
is
assigned
a
level.
See
Code
System
for
further
information.
Source
The
source
of
the
definition
of
the
code
(when
the
value
set
draws
in
codes
defined
elsewhere)
Code
The
code
(used
as
the
code
in
the
resource
instance).
If
the
code
is
in
italics,
this
indicates
that
the
code
is
not
selectable
('Abstract')
Display
The
display
(used
in
the
display
element
of
a
Coding
).
If
there
is
no
display,
implementers
should
not
simply
display
the
code,
but
map
the
concept
into
their
application