This
page
is
part
of
the
FHIR
Specification
(v3.0.2:
(v4.0.1:
R4
-
Mixed
Normative
and
STU
3).
)
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:
R4
R3
R4
R3
This
code
system
(http://hl7.org/fhir/v3/AcknowledgementDetailType)
(http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailType)
is
defined
as
part
of
HL7
v3.
A
code
identifying
the
specific
message
to
be
provided.
Discussion:
A
textual
value
may
be
specified
as
the
print
name,
or
for
non-coded
messages,
as
the
original
text.
Examples:
'Required
attribute
xxx
is
missing',
'System
will
be
unavailable
March
19
from
0100
to
0300'
OID:
2.16.840.1.113883.5.1082
(for
OID
based
terminology
systems)
This
Code
system
is
used
in
the
following
value
sets:
ValueSet:
v3
Code
System
AcknowledgementDetailType
(
A
code
identifying
the
specific
message
to
be
provided.
Discussion:
A
textual
value
may
be
specified
as
the
print
name,
or
for
non-coded
messages,
as
the
original
text.
Examples:
'Required
attribute
xxx
is
missing',
'System
will
be
unavailable
March
19
from
0100
to
0300')
4.3.2.1082.1
4.4.2.1082.1
Code
System
Content
Release
Date:
2016-11-11
2018-08-12
Level
Code
Display
Definition
1
E
Error
Definition:An
issue
which
has
prevented,
or
will
prevent
(unless
a
management
is
provided
for
the
issue
by
the
sender),
the
successful
processing
of
an
interaction.
Response
interactions
which
include
an
issue
which
is
an
Error
are
a
'rejection',
indicating
that
the
request
was
not
successfully
processed.
Example:Unable
to
find
specified
patient.
1
I
Information
Definition:
The
message
relates
to
an
issue
which
has
no
bearing
on
the
successful
processing
of
the
request.
Information
issues
cannot
be
overridden
by
specifying
a
management.
Example:
A
Patient's
coverage
will
expire
in
5
days.
1
W
Warning
Definition:
The
message
relates
to
an
issue
which
cannot
prevent
the
successful
processing
of
a
request,
but
which
could
result
in
the
processing
not
having
the
ideal
or
intended
effect.
Managing
a
warning
issue
is
not
required
for
successful
processing,
but
will
suppress
the
warning
from
being
raised.
Example:
Unexpected
additional
repetitions
of
phone
number
have
been
ignored.