Error database tool
The Cloverleaf engine saves error messages in a SQLite database, to provide more ease of use and flexibility for users. The Error Database tool manages the error database for message search.
This is used similar to the SMAT Database tool, where you can do an HL7 smart search on the error database.
The Error Database tool contains all functions available in the SMAT Database tool, along with the ability to show the error state and error context. Transactions can be edited and resent, similar to the SMAT Database tool.
The auto-complete suggestion for the error database uses the same format/alias databases as the SMAT Database. The aliases that are configured in the Site Preferences dialog box, or the fields that are added/created in HL7 and HPRIM, are also shown in the error database.
Previously, if a message was sent to the error database, the user had no control over the processing of that event. The Error Database tool gives you a control point before the message is written to the error database. You can change the error message content or route the message to another context.
For example, you can:
- Change the message content to add information before the message goes to the error database.
- Stop the message so it does not go to the error database.
- Send a NAK to the source to notify there is an error when processing the message.
- Save the message to file or another external source, and resend the message that is based on it.
- Change the message and redo the step that cause the error.
This tool is similar to the SMAT Database, with these differences:
- There is no file tree list, since there is only one database for storing error messages.
- Support is provided for the
error-based metadata: state, last recovery state, error info, class, and owner
thread.
You can search using these metadata as part of the search criteria. The error state and last recovery state metadata are displayed in the search result by default. The error info, class, and owner thread are optional to display. This is specified in the Customize Columns dialog box.
- The Resend dialog box is the same as the one in the Database Administration tool.
- You can delete messages
using the
One button is located on the search result toolbar. When messages are marked in the search result, the button is enabled.
Another button is on the message viewer toolbar.
When
is clicked, a prompt opens for confirmation. After deleting, the current search is refreshed.
buttons.
For information on encrypting/decrypting the error database, see hcidbcrypt.
The elog.elogdb SQLite error database file is located in $HCISITEDIR/exec/databases.
The criteria definitions of error messages are saved in criteria_def_username.ini files. This is the same as the SMAT Database tool, except that these files are stored under %HCISITE%\exec\databases\ criteria_defs.