Deprecation
Comment:
Deprecated
as
per
11/2008
Harmonization
cleanup;
internal
and
obsolete
HL7
usage,
no
longer
used.This
isn't
referenced
in
the
RIM
and
is
a
copy
of
old
v2
codes.
It's
superseded
by
AcknowledgementDetailCode
|
Level
|
Code
|
Display
|
Definition
|
|
1
|
0
|
Message
accepted
|
Success.
Optional,
as
in
version
2.x
the
AA
conveys
success.
Used
for
systems
that
must
always
return
a
status
code.
|
|
1
|
100
|
Sequence
error
|
The
message
elements
were
not
in
the
proper
order,
or
required
elements
are
missing.
|
|
1
|
101
|
Missing
required
element.
|
A
required
message
element
is
missing.
|
|
1
|
102
|
Data
type
error
|
An
element
is
represented
by
a
data
type
that
is
not
compatible
with
that
which
is
allowable.
|
|
1
|
103
|
Table
value
not
found
|
The
value
received
for
a
common
HL7
or
user
defined
table
was
not
found
to
match
allowable
table
values.
|
|
1
|
200
|
Unsupported
message
type
|
The
message
type
is
not
supported.
|
|
1
|
201
|
Unsupported
interaction
|
The
identified
interaction
is
not
supported.
|
|
1
|
202
|
Unsupported
ProcessingID
|
The
ProcessingID
is
not
supported.
|
|
1
|
203
|
Unsupported
VersionID
|
The
VersionID
is
not
supported.
|
|
1
|
204
|
Unknown
key
identifier
|
The
identifier
for
a
patient,
order,
etc.
was
not
found.
Occurs
for
transactions
other
than
additions.
|
|
1
|
205
|
Duplicate
key
identifier
|
The
identifier
for
a
patient,
order,
etc.
already
exists.
Occurs
in
response
to
addition
transactions
(e.g.
new
Admit,
new
Order,
etc.).
|
|
1
|
206
|
Application
record
locked
|
The
transaction
could
not
be
performed
at
the
application
storage
level,
e.g.
database
locked.
|
|
1
|
207
|
Application
internal
error
|
A
catchall
for
internal
errors
not
explicitly
covered
by
other
error
codes.
|
|
Propose
a
change