Agent Backup Scheme

Due to the extremely varied capabilities of receiving clinical applications to accurately parse and display correspondence letters, it is strongly recommended that a secondary receive action be put in place to save these documents out to a supplementary folder location. In the event that the primary receiving clinical applications fails to appropriately display the corresponce document, the backup copy of the document can be located and viewed within the supplementary folder using the native application for its file type.

The filename convention used for the supplementary repository is as follows;

«patient name»+«space»+«(DOB dd-mm-yyyy)»+«space»+«from (sender name)» resulting in the following example;

• Test Patient (DOB 01-01-1980) (from Test Doctor).???

This file name convention should facilitate the simple identifictation of the file from within the supplementary folder location, and the associated manual attachment of the document to the relevant patient's clinical record.

Note: This pattern does impose a cost to the recipient in the context of disk space, the agent does not perform or supply any administration utilities to deal with the archiving of these files and it is left to the recipient to undertake their own maintenance plan.

There are currently two presets available to implement this backup scheme, one deals with extracting the embedded RTF letter out to a folder location, the other supports the ability to convert the RTF letter into a JPG and save to a specified folder location.

1. Simply saves the incoming RTF document out to disk, no additional processing required.

1. Microsoft Word required to guarantee the letter can be viewed correctly, WordPad does not have sufficient RTF capabilities to provide this safe guard.

Example

1. The correspondence document cannot be changed by the recipient, and hence, is similar to PDF in this regard.
2. Does not require an instance of Microsoft Word to view the document, any standard image viewing utility can be used at no cost.

1. The file size can be significantly larger than an RTF document, especially if it is a large document.
2. Relies on the RTF capabilities of the ReferralNet agent, which also suffers from some limitations, so it may provide mixed results for very complex RTF documents.

Example

• The NEHTA Electronic Referral Program