Tabela 0357 - Message error condition codes*
Item# | Descrição |
---|---|
0 | Message accepted: Success. Optional, as the AA conveys success. Used for systems that must always return a status code |
100 | Segment sequence error: Error: The message segments were not in the proper order, or required segments are missing |
101 | Required field missing: Error: A required field is missing from a segment |
102 | Data type error: Error: The field contained data of the wrong data type, e.g. an NM field contained "FOO" |
103 | Table value not found: Error: A field of data type ID or IS was compared against the corresponding table, and no match was found |
200 | Unsupported message type: Rejection: The Message Type is not supported |
201 | Unsupported event code: Rejection: The Event Code is not supported |
202 | Unsupported processing id: Rejection: The Processing ID is not supported |
203 | Unsupported version id: Rejection: The Version ID is not supported |
204 | Unknown key identifier: Rejection: The ID of the patient, order, etc., was not found. Used for transactions other than additions, e.g. transfer of a non-existent patient |
205 | Duplicate key identifier: Rejection: The ID of the patient, order, etc., already exists. Used in response to addition transactions (Admit, New Order, etc.). |
206 | Application record locked: Rejection: The transaction could not be performed at the application storage level, e.g., database locked |
207 | Application internal error: Rejection: A catchall for internal errors not explicitly covered by other codes |
* Em desenvolvimento