HL7 Errors (as pertains to the Smart Suite module, not the RFC)
The following table lists the Smart Alert errors for the HL7 module.
|A required field from the segment is missing. Either make the field optional (O) or the sender needs to send the field value for it.
|A required segment is missing. Either make the segment optional ([segment_name]) or the sender needs to send the segment along with field values.
|The SQL statement for the message has error in it or correct data was not received. Check the SQL first. If no error, then check the field values assigned as bind variables.
|Header Message Missing
|MSH segment is required. If it is missing, no message will be processed. Make sure MSH is sent by the sender.
|Invalid Sequence Number
|If sequence numbering is used, then the rule for sequence numbering applies. If a message is received out of the order of sequence numbering, then either turn the sequence numbering off or adjust the sequence number accordingly.
|The message received is not a compatible version.
|Invalid Message Type
|The message received is not found in the message rules file.
|Record Not Found
|The requested record is not found in the database.
|Invalid Ini File
|The ini file is invalid, the section inside it not found, can not be opened, etc.
|Invalid Connection Type
|The connection type selected is not one of the following: DIRECT, MODEM, TCP/IP
|Invalid Segment Rules File
|The segment rules file can not be opened or has invalid segments in it. See more debug outputs.
|Invalid Message Rules File
|The message rules file can not be opened or has invalid messages format in it. See more debug outputs.
|The selected port is invalid. Adjust the port as desired.
|The message received has invalid data (for example, an invalid field separator). See debug output for more information.
|The message received is blank. Check with segment rules or the sender.
|Invalid Process ID
|The specified process ID is either less than 1 or is not found in the ini file. Please check the validity of the process ID.
|The specified connection type did not allow HL7 to connect to the ADT device. Please check the CONNECTION type, port, cables and other related connection components.
|The PDT (Production, Development, Test) flag defined in the initialization file did not match the flag received from the ADT system. Contact the ADT system administrator.
|The connection to the ADT system has been lost. Contact the ADT system administrator to re-establish the connection.
|Idle Link Timeout
|HL7 messages have not been received from the ADT system interface for the specified period of time. Contact the ADT system administrator.
|The specified login SQL is invalid. Please check LOGIN SQL in the initialization file.
|HL7 was unable to allocate memory. Please increase memory and/or reset HL7.
|Invalid Program Type
|The program type defined is not server or client. Please select either server or client.
|Invalid SQL File
|The SQL file has one or more invalid parameters. Please check the SQL file name, path, and content.
|Invalid Filter Rules File
|The filter rules file has one or more invalid parameters. Please check the filter rules file name, path, and content.
|Reconnected With ADT
|Often seen with 10618 or 10619, this is not an error. This is a notification message to notify operators that HL7 has reconnected with the ADT interface.