ArgusConnect Pty Ltd ABN 63107558387 Suite 4, GreenHill Enterprise Centre University Drive, Ballarat Victoria 3353 Tel: (03)5335 2220 email: andrew.s@argusconnect.com.au Website: http://www.argusconnect.com.au

Using ArgusMessenger

Last Updated: October 2006

1 Introduction

1.1 Purpose of Document

This is a detailed guide outlining the features and use of ArgusMessenger. It is the first in a set of documents comprising:

• Using ArgusMessenger

• Using ArgusMail

• Using ArgusAgent

• Using ArgusWord Audiovisual Guide

• Using The Argus Token Selector

• Using The Argus Message Broker

• Address Management in Argus
  
  

This guide presupposes a high-level understanding of Argus, as described in detail on the ArgusConnect website.

1.2 Terms and Abbreviations

Term	Definition
Argus	The suite of programs that provides for the secure mail-exchange between health care providers (GPs, pathology labs, specialists etc.)
ArgusMessenger	This is a program that interacts with POP3/SMTP, IMAP and LDAP servers. It implements advanced HL7 handling and encryption via PKI. One instance of ArgusMessenger runs at each location.
ArgusMail	This is the ‘client’, a program that allows users to view and send email. An instance of ArgusMail runs on each user’s desktop.
ArgusAgent	This is a program that can be run in background mode to fire defined events at designated intervals. Tasks include the automatic sending of documents dropped into a directory, and polling for files to be printed automatically.
Argus Message Broker	The program that allows an administrator to review batches of messages before sending them, such as might occur in a radiology practice.
ArgusAPI	This is an API module that allows other applications to interact with Argus without using the Argus GUI. Non-windows applications can interact directly with a Java class in Argus itself, and Windows applications can use COM.
Message	A mail item, downloaded from the mail server and stored in an Interbase database. As with any email, messages often include attachments.
LDAP	Lightweight Directory Access Protocol is a client server protocol for accessing a directory service.
Folder	This does not refer to a file directory. It is used here to denote a mail folder in ArgusMail, such as the Inbox.
HQL	HL7 Query Language is a script language for retrieving data fields from an HL7 message.
XML	eXtensible Markup Language. A widely used standard from the World Wide Web Consortium (W3C) that facilitates the interchange of data between computer applications. Computer programs (such as the XMLUtiltiies module in Argus) can automatically extract data from an XML document, using its associated XSD as a guide.
XSD	XML Schema Definition. A file which defines the building blocks of an XML document, and which can be used a template when converting another format (in this case, HL7) to XML and vice versa.
XMLUtilities	A generic module which, when provided with an XSD, can convert HL7 messages into XML and vice versa. It makes use of the SAX Java library.
SAX	The Simple API for XML, a 'de-facto' standard for XML handling in Java. SAX is an event based API, which reports parsing events (such as the start and end of elements) directly to the application (in this case, to the XMLUtilities module.

2 Using ArgusMessenger

2.1 What is ArgusMessenger?

ArgusMessenger is the very core of Argus. It contains all the intelligence that makes Argus distinct from other email suites. The processes of downloading and processing email, performing encryption, digital signing and archiving are all controlled by ArgusMessenger – the other programs in the Argus suite merely have supporting roles, as clients.

Argus is not an email server, nor is it intended to replace existing mail products. It is designed to complement other mail programs, providing an invisible messaging infrastructure to facilitate secure message delivery between clinical applications. Argus can run side by side with programs like Outlook, while remaining predominantly invisible.

All of the Argus programs connect and communicate directly with the Argus database, but only ArgusMessenger has a link to the Internet. All the other programs in the Argus suite can thus be used without being on line. Obviously, no messages are sent or received until ArgusMessenger initiates a connection to the Internet.

In a nutshell then, ArgusMessenger has these distinct roles:

• facilitating the set up and configuration of Argus, such as for mail settings

• controlling the flow of emails (downloading and sending)

• tracking the progress of message delivery

• encryption of outgoing emails, decryption of incoming emails

• digital signing of outgoing emails, verification of incoming emails' signatures

• processing the contents of incoming emails, in order to convert and deliver information appropriately to locations from whence it can be uploaded into a clinical application

• keeping the address book up to date by means of an automated processing

• warning about errors

• archiving and backing up of data

2.1.1 Minimum Hardware Requirements

Argus can be run on a medium-range PC. At a minimum, it should have:

256Mb RAM (for Windows)

Pentium III 330MHz

10 Gb hard drive

CD drive

Internet / Intranet connection

For Win32

Interbase/Firebird Server (10MB)

Argus Suite including Java 1.5 and all Documentation (140MB)

For Linux

Java JRE 1.5 (68MB)

Interbase v6 Server(.rpm 3.15MB or .tar 3.19MB)

Interbase v6 Server (Source .tar.gz 7.2MB)

or

Interbase/Firebird Server (10MB)

Argus Suite including PKI (37MB)

For MAC OSX

Java JRE 1.5 (68MB)

Interbase v6 Server (N/A)

or

Interbase/Firebird Server (10MB)

Argus Suite (37MB)

2.1.2 Configuration

ArgusMessenger facilitates the necessary configuration that allows Argus to interact with an email server. ArgusMessenger needs to know the settings for the email servers, for the Argus Users Directory (an LDAP server), the PKI certificates for encryption and most importantly, what the mailbox details are for each of the email accounts accessible by Argus.

The process of defining the critical settings is presented in an easy-to-follow feature called the Settings Controller. This centralises all essential (and some non-essential) settings, allowing you to configure Argus step-by-step through the use of simple wizards, and is an easy way to see which settings you have already configured. Every settings page presented by the Settings Controller is also available elsewhere in ArgusMessenger (as long as you know where to look).

The categories listed immediately below in this section are all explained in detail later in this document.

2.1.3 Encryption And Digital Signatures

In order to encrypt, decrypt and digitally sign emails, ArgusMessenger uses PKI as mandated by the HeSA arm of the Australian Health Insurance Commission (HIC). See 2.10.2.2

2.1.4 The HL7 Engine and Guarantee of Delivery

An important aspect of messaging is the issue of guaranteed delivery; this needs to be carefully enforced in a store-and-forward environment, which Argus supports by following the protocols (rules) set out by the HL7 standard. Argus has an HL7 engine that allows it to construct and decompose HL7 data.

When ArgusMessenger sends an HL7 message it expects to receive an electronic acknowledgment (ACK) in return. If no acknowledgment is received after a number of retries, the message ‘fails’ and ArgusMessenger stops trying. The failure is logged, and a message about the failure is sent to the administrator’s email address.

Configuring ArgusMessenger for this feature and the handling of failed messages by the administrator is explained in section .

2.1.5 Mail Rules Engine

The rules that allow Argus to respond with automatic events in response to the receipt of particular kinds of emails are configurable using the Mail Rules wizard. These are much like the mail filters used by Outlook, but are more sophisticated. For more information see section 2.10.2.2.

2.1.6 Importing Templates

Many locations use the same Mail Rules. For example, a pathology lab that sends its results using Argus will want to set up Argus in exactly the same way at all its receiving sites, to drop the results into a directory where they can be detected and imported by a doctor's clinical software.

Rather than forcing the person who installs Argus to go through the long process of setting up the same Mail Rule at every doctor's site, Argus provides a system of 'templates' to make this process much quicker, easier to use and less prone to error.

The Argus template system uploads predefined settings into the Mail Rules engine that tell it how to filter and process incoming messages. These template-based rules identify a message by matching the contents of an HL7 attachment, so that the data can be exported for upload by clinical software.

Listed below are the templates currently shipped with Argus. This will grow as more 'standard' templates are defined.

• Export letters/reports received from other Argus users

  Specialist letters

  Radiology reports

  Pathology results as embedded PIT

  GP letters as embedded PIT

  Discharge notifications as embedded PIT

• Export Diabetes reports

• Export REF messages for TEDGP by type

• NID Report Template (I12 Event Type)
  Used by DHS to receive NID Reports from Labs (HL7 messages of type REF_I12), convert to XML (using an XSD schema defined in the Mail Rule Template), and export to a specified directory
  
  

• NID Report Template (I13 Event Type)
  Used by DHS to receive NID Reports from Labs (HL7 messages of type REF_I13), convert to XML (using an XSD schema defined in the Mail Rule Template), and export to a specified directory

• NID Acknowledgment Template (I12 Event Type)
  Used by Labs to receive NID Acknowledgments from DHS (HL7 messages of type RRI_I12), and export to a specified directory

• NID Acknowledgment Template (I13 Event Type)
  Used by Labs to receive NID Acknowledgments from DHS (HL7 messages of type RRI_I13), and export to a specified directory
  
  

• Export pathology reports prepared in Sonic format

In order to set up Argus to use these templates, it is necessary to activate the rules which correspond with the types of messages you would like to receive. Activating such rules is simplified by the Simple Export Wizard. This provides a quick and simple way to set up several template-based mail rules at once. For more information about the Simple Export Wizard, see section

2.1.7 The XMLUtilities Module

Argus can convert HL7 messages into XML format, and vice-versa, through the use of XML schema definition (XSD) files. Please contact ArgusConnect if you require a custom Mail Rule Template which makes use of this functionality.

Converting HL7 messages into XML using Mail Rule Templates
In order to convert incoming HL7 messages into XML format, a Mail Rule Template needs to be created. The XMLUtiltities Module requires XML schema definitions which define the structure and cardinality of the HL7 message type (for example, REF_I12). The Mail Rule Template contains the top-level schema definition which will be used to validate and convert HL7 messages matching the Mail Rule Template. Argus ships with one Mail Rule Template which makes use of this functionality. For more information on creating rules using Mail Rule Templates, please see section .

Converting XML messages into HL7 using Events
To convert messages in XML format back into HL7 format before sending, ArgusAgent can be configured using the Event “Convert XML To HL7”. This Event is generic in the sense that any well-formed XML message can be converted into HL7. ArgusAgent determines the sender by checking a certain field in the HL7 message (for example, MSH 6.1 – 'Receiving Facility') and matches the value found with an entry in the Argus Address Book in order to send the message. For more information on configuring events in ArgusAgent, refer to the document Using ArgusAgent.

2.2 Where to install the program

Only one copy of ArgusMessenger should be installed at a location (such as a general practice). The PC chosen should have a link to the Internet and to a local area network.

Never separate ArgusMessenger from its database, the file Argus.gdb

Usually, the entire Argus suite is used on one PC, though users who wish to use client programs like ArgusMail will want to install that program on several PCs. In the case where doctors will send letters directly from within the letter writer of their clinical application, an Argus module needs to be installed on the PC being used in this way.

For example, in a solo general practice with only one PC this is how the doctor would use Argus:

• Every morning ArgusMessenger would download messages from the mail account used for clinical messages. Argus can automatically dial out (under Windows) if an Internet connection needs to be established. See 2.10.2.2 for setting this up.

• If ArgusMessenger is configured to deliver incoming letters into a directory these can be viewed using the practice software. Specialists who have no clinical software can use ArgusMail to view their messages

• During the day the doctor can send letters by using the letter writer of the practice software. Argus can intercept calls to the default mail client and handle the letters appropriately for the data to be importable by the recipient of such letters. These messages are dropped into the Argus database for sending by ArgusMessenger

• Specialists who lack clinical software can use ArgusWord to generate letters

The process just outlined shows how Argus can be used on one PC in a practice. If a practice has several networked PCs the process is just the same, and still only one PC needs to have ArgusMessenger. That PC must be able to connect to the Internet. On other PCs doctors can use their practice software, ArgusMail, ArgusWord to read and create messages. These client programs do not need a connection to the Internet: all they need to know is where the Argus database is located. They all connect to the database, whereas ArgusMessenger connects both to the database and to the outside world.

2.3 Getting started

When a user registers and downloads Argus directly from the ArgusConnect website they are issued with a 30-day licence to use the product. The only reason for this limitation is that ArgusConnect wants users of its product to contact the ArgusConnect support staff. This direct contact allows ArgusConnect to ensure that the user's registration details have been captured correctly because they will be uploaded into a national 'address book' called the Argus Users Directory.

Furthermore, ArgusConnect support has experts who will assist users to install and configure Argus. The user can establish a real time connection to ArgusConnect so that Argus can be installed, configured and tested as quickly as possible.

Once the initial contact is complete, ArgusConnect support will issue a new licence key that will not expire.

Argus has the ability to be installed using an XML settings file, which can be preprepared on the ArgusConnect website. This XML settings file will configure the main settings within Argus.

2.4 Argus installation options

Using the ArgusConnect website it is possible to create an XML file containing the core settings for an installation. This XML file makes it quick to install Argus by allowing automatic upload of settings the very first time a new Argus installation is activated. This image shows the website where such a settings file can be configured:

Whenever these settings are modified in Argus, the XML settings file gets updated. If Argus were to be uninstalled for any reason, the core settings can easily be restored when Argus is reinstalled.

2.5 Logging In

Only one person in a practice should ever use ArgusMessenger; that person is designated the ‘administrator’. This person has the responsibility of seeing that the system settings are correct, and that new users of ArgusMail are entered onto the system. Unless programs like Medipak and Medtech32 are running on the machine, when ArgusMessenger is first run the default login is:

• Login ID – SYSDBA

• Password – masterkey

Important: As soon as possible, change the SYSDBA password from masterkey to something else. If you do not, anybody who is familiar with Interbase can log into your ArgusMessenger installation. You can change your password in 'Step 1 – System' in the Settings Controller, or Go to Configure -> Change Password in the menu, or press Alt+P.

Other programs may also use Interbase, and these programs may use their own SYSDBA password. Do not change it on such installations.

If the SYSDBA password is left unchanged, anybody familiar with Argus can log into ArgusMessenger, and thus learn what the login details are for all the Argus users at that site. Such a person could thus read everybody’s email.

The login screen will be expanded if the location of the Argus database is unknown. Once this is set, that part of the login dialog will be hidden (the next time ArgusMessenger is started). The database is called Argus.gdb and is located in the \Argus\Server\Database\ directory. e.g. c:\Program Files\Argus\Server\Database\Argus.gdb. The host field refers to the IP address of the PC where the database is located. localhost refers to the current PC. ArgusMessenger seeks Argus.gdb automatically.

2.6 Entering the licence key

Whenever ArgusMessenger has logged in it looks for the licence file. This is a .bin file that is emailed to a designated address upon registration, and which must be saved in the \Argus\ directory.

ArgusMessenger will not work without the licence file being present.

If the licence file has been saved somewhere on the computer, locate it when the 'Do you have a new Argus Licence?' dialog appears.

2.7 Automatic Database Upgrading

As Argus has evolved the structure of its database has changed. Argus detects if the version of Argus being used is incompatible with the database, and prompts the user to authorise an upgrade. This may cause some data to be lost, as the dialog explains:

Argus will determine the version of the existing database so that it can perform an incremental modification of the database so that it has an identical version number to the programs in the Argus suite.

2.8 Running ArgusMessenger for the first time

Before Argus can be used for downloading and sending mail, there are a number of settings which need to be completed. Argus will popup a dialog asking you to select one of three ways to configure Argus.

The Argus Installation Options dialog will be loaded automatically the first time Argus is run, or when it detects that no system settings have been configured yet.

Option 1: Install from Argus Via Argus Settings File (xml). This option allows you to configure Argus using an pre-configured Argus Settings xml file. The Settings File can be create on the Argus Website. Select the Settings file and confirm the settings file installation.

Figure 8: The Argus Settings File Selector

Option 2: Restore Argus from an Argus Backup File (zip). This option is mainly used to restore an Argus Installation. Select the Argus Backup File, and restore the Argus Settings.

Figure 9: The Argus Backup File Selector

Option 3: The Settings Controller, which includes wizards for each of these minimum required settings and guides the user step-by-step, in the correct order, through setting up Argus. Every settings page presented by the Settings Controller is also available elsewhere in ArgusMessenger (as long as you know where to look).

The Settings Controller has two distinct areas: the panel on the left shows those settings (System, Mail Server, Mail Accounts, etc) which can be configured. A green tick shows the steps already completed. The Required settings (the first three steps) must be completed in order, after which the optional settings can be completed at any time.

The panel on the right is used initially to show a full description of how the Settings Controller should be used, and subsequently to display the wizard for the step currently selected on the left.

To start a wizard, click on a step in the list. The selected step is then shown in bold. When a step is first selected, an information page (which explains the information required in each wizard) will appear in the right-hand panel. Press 'Continue' (for steps which also include a list of previously configured items e.g. the 'Mail Accounts' step) or 'Start Wizard' (for basic wizards e.g. the 'System' step). The wizard for the step you have chosen is loaded into the right-hand panel.

The rest of this section explains both the required and optional settings which can be configured in ArgusMessenger.

2.8.1 An overview of the Settings Controller

The Settings Controller can be accessed at any time through the toolbar ('Settings' button), menu item (Configure -> Settings Controller), or keyboard shortcut (Alt+S).

Upon completion of the required steps, the user can literally start downloading and sending encrypted messages at once.

The Settings Controller contains the following steps:

Required Settings

• System (includes setting up of institution name, security database, and option to change SYSDBA password)

• Mail Servers (configuration and setup of one or more mail servers, used when specifying mail settings for Argus users)

• Mail Accounts (configuration and setup of one or more Argus users)

Optional Settings

• Dial-Up (allows enabling of automatic dialup when Argus synchronises mail)

• Encryption (installation of PKI and option to export public certificate)

• Rules (activation of rules using pre-defined Mail Rule Templates, through the use of the Simple Export Wizard – for more information, see )

• AutoRun (setting up Argus to run in the background, as a service)

There is no need to show every screen in the Settings Controller wizards because every step is preceded by a help page that is shown in the right hand panel. Nevertheless, a few tips follow.

Both the 'Mail Servers' and 'Mail Accounts' steps include another screen after the information page is shown. This screen shows a list of previously configured mail servers or mail accounts. At this point it is possible to add, modify, or remove an existing item, which makes the Settings Controller useful even after initial configuration.

2.8.2 Step 1 - System

This is one of the two screens containing non-optional settings that allow Argus to function as an ordinary mail program (the other screen is Configure Argus Users). Required fields are always indicated by the text of their labels being blue, not black. For details, see 2.10.2.2.

2.8.3 Step 2 - Mail Servers

Argus can attach to more than one mail server. It is thus possible for the doctors in a practice to access their mailboxes from many different ISPs. The Mail Provider Label you enter will appear in the list. When setting up a person on the Configure Argus Users screen, each user must be associated with one of the servers entered here. The settings you require can be obtained from Netscape in Edit/Mail and Newsgroups Account Settings

and from Outlook in Tools/Accounts/Mail/Properties/Servers and …/Advanced

The POP3/IMAP and SMTP port numbers are usually (but not always) 110 and 25 respectively. The settings in this group are all mandatory. For further details, see 2.10.2.2.

2.8.4 Step 3 - Mail Accounts

Just as it is possible to set up links to more than one mail server, it is similarly possible to set up links to more than one email account. Once accounts have been created it is easier to edit them using the accounts screen. For further details, see 2.10.2.3.

2.8.5 Step 4 – Dial-up

When ArgusMessenger attempts to connect to a mail server it will dial out if it detects that no connection to the Internet has been established. This page detects all available connections on the PC, connecting and disconnecting automatically as required. Please note that the auto-dialup feature is currently only available for those running the Windows operating system. For further details, see 2.10.2.2.

2.8.6 Step 5 – Encryption

In order for ArgusMessenger to be able to send and receive encrypted and digitally signed messages you need to install a PKI. The terms certificate and key are interchangeable.

Argus requires the use of a 'site key pair' issued from the Health E-signature Authority.

After you receive a site key pair and password from HeSA you are ready to configure PKI.

After you have installed the Site Key pair it will ask you if you want to save a copy of your public key.

This key is used by others to send you encrypted messages. When you want to send an encrypted message you are also required to have the recipients public encryption key.

Whenever you send an encrypted message Argus will also digitally sign the message with your Site Key. For further details, see 2.10.2.2

2.8.7 Step 6 – Rules

Argus can be configured to execute a variety of actions automatically when certain conditions are met. For example, if a certain type of HL7 message is received,

1. Convert the message's HL7 attachment into a PIT file

2. Save the PIT file in a designated location

Whenever ArgusMessenger downloads a message from a POP3 or IMAP server automatic events can be activated according to:

• Who the message is addressed to

• Whether the message was signed by a sender in a trusted group

• Whether the message is encrypted

• Who the sender is

• What type of message it is (HL7 type)

Mail Rules can be configured manually using the 'complex' Mail Rule wizard on the Mail Rule page of the System screen. Refer to section 2.10.2.2. That page provides access to an advanced wizard for the configuration of sophisticated mail filters. Users are advised to contact ArgusConnect if they want to use this feature, because most mail rules have mail rule templates defined for them, and can hence be much more easily configured using step 6 of the Settings Controller.

This is why you should use the simple mail rules wizard in the Settings Controller: there is no such thing as a ‘typical’ HL7 message. In order for Argus to know how to convert a particular type of HL7 message it requires a template that tells it how to perform the conversion. Think of the template as a recipe for how to extract the data from the HL7 message. The ‘recipe’ is defined in a text file that can be imported into Argus.

Mail Rule templates provide nearly all of the information required to set up a rule (including the conditions, export action and output format details).

If such a template needs to be created, contact ArgusConnect for advice. Template creation requires a thorough understanding of HL7 and of the scripting language (HQL) that is used to define the templates, and a knowledge of the structure of the Argus Template files.

Setting up a Mail Rule using the Settings Controller is very easy because it only requires the entry of two pieces of information:

• an address to which an error notification will be sent if that rule fails to process correctly

• the directory into which data should be delivered

If more than one template has been selected in the right hand list all rules will export data to this same directory. Forcing one of the rules to save its data in a directory other than this default directory can be done by using the standard Rules Wizard on the System page. See section 2.10.2.2

All wizard generated rules will also be set with certain default values, e.g. whether the message only applies to encrypted messages The rule can be modified in the standard Rules Wizard to change any of these default settings.

2.8.8 Step 7 - AutoRun

ArgusMessenger can be configured automatically to activate at scheduled intervals for the purpose of processing email and conducting backups. Argus will create either a Scheduled Task (on computers running Windows 98) or a service on computers running Windows 2000/NT/XP, Linux or Mac OSX.

The SYSDBA password must be captured in order to activate the service.

Please Note: if you change your SYSDBA password after running the AutoRun wizard you will need to configure AutoRun again using your new password.

2.8.9 Step 8 – Automatic Updates

ArgusMessenger can be configured automatically to activate at scheduled intervals for the purpose of updating the software. Argus will create either a Scheduled Task (on computers running Windows 98) or a service on computers running Windows 2000/NT/XP, Linux or Mac OSX.

The SYSDBA password must be captured in order to activate the service.

Please Note: if you change your SYSDBA password after running the Automatic Update wizard you will need to configure Automatic Updates again using your new password.

2.9 The first screen you see after logging in

Upon logging in to ArgusMessenger you will see the screen ‘Acknowledgement Manager’. This shows various lists of messages that have been sent by Argus (filtered according to ACK status) and is the most useful screen to users of Argus who need to track their messages. In reality, as long as every message sent gets ACKed, there will seldom be any need to open ArgusMessenger. For further details, see 2.10.2.7.

If this is the first time you have run ArgusMessenger, or you have not completed basic system settings, the Installaton Options will load as soon as you have logged in. For further details, see 2.10.2.1

2.10 The main Toolbar and menu

The five buttons at the top of the ArgusMessenger screen are mentioned here in the order according to which they should be selected when you first start ArgusMessenger. All toolbar functions are also available through the menu at the top of the screen. A description of menu items follows in the next section.

2.10.1 Toolbar functions

2.10.1.1 Toolbar button - ACKs

This shows various lists of messages that have been sent by Argus (filtered according to ACK status) and is the most useful screen to users of Argus who need to track their messages. For further details, see 2.10.2.7.

2.10.1.2 Toolbar button - Progress

The ‘Progress’ page shows information relating to the download, sending and processing of messages. This page only displays progress information and has no editable fields. It can also be accessed through the menu (Show/Progress), or through the keyboard shortcut Alt+V. The list headed by ‘Message Download Log’ provides a log of what ArgusMessenger is doing. For further details, see 2.10.2.8.

2.10.1.3 Toolbar button - System

The System screen is split into a number of pages. Each page is described in greater detail in the next section, concerning menu items. This screen can also be accessed through the menu (Configure -> System). Most of these pages can be referenced using the Settings Controller. For further details, see 2.10.2.2.

2.10.1.4 Toolbar button - Configure Argus Accounts Details

This screen is where to set up the email accounts used by Argus. This page can also be accessed through the menu (Configure -> Accounts), or through the keyboard shortcut Alt+U. For further details, see 2.10.2.3.

2.10.1.5 Toolbar button - Logs

Every action performed is recorded in the database. This button allows viewing of the System (ArgusMessenger) log, ArgusAgent log and Address book update log. in order to track sent messages use the ACKs screen instead. This page can also be accessed through the menu (Show/Message Logs), or through the keyboard shortcut Alt+G. For further details, see 2.10.2.9.

2.10.1.6 Toolbar button - Open Settings Controller

This button opens the Settings Controller, a centralised location where all essential (and most non-essential) settings can be configured in one place. It can also be accessed through the menu (Configure -> Settings Controller) or through the keyboard shortcut Alt+S. For further details, see 2.10.2.1.

2.10.1.7 Toolbar button – View Address Book

This button opens the local Argus Address Book, which stores addresses that have been downloaded from a specified LDAP server (such as the Argus Users Directory), or manually added. It can also be accessed through the menu (Show/Address Book). For further details, see 2.10.2.10.

2.10.1.8 Toolbar button – Configure Address Udpate

This button opens the Configure Address Update screen, which includes a number of different tabs related to keeping your local Argus address book updated from an external LDAP server. It can also be accessed through the menu (Configure/Address Book Update). For further details, see 2.10.2.10.

2.10.2 Menu Functions

2.10.2.1 Menu Item – Configure/Settings Controller

This menu item opens the Settings Controller, a centralised location where all essential (and most non-essential) settings can be configured in one place. It can also be accessed through the keyboard shortcut Alt+S. For further details, see 2.8.1.

2.10.2.2 Menu Item – Configure/System

The System screen is split into a number of pages. Each page is described in greater detail in the next section, concerning menu items. This screen can also be accessed through the menu (Configure -> System). Most of these pages can be referenced using the Settings Controller. For further details, see 2.10.2.2.

The System Page

This page is divided into two sections. The top section shows all the mail servers that have been set up, usually by means of the Settings Controller. Some ISPs do not require authentication of SMTP calls, and these can have that feature switched off using the checkbox.

The bottom section contains a number of miscellaneous settings. Those which are mandatory will have been required fields in the equivalent screen in the Settings Controller.

Location Name: Argus requires a name for this installation of Argus. The location name is used when sending ACKs to HL7 messages it receives.

Site Monitor Signature Address: used when ArgusConnect is monitoring this site to check that it is running perfectly, by sending test messages from ArgusConnect support.

Log size(s): restricts the size of the various logs.

Interbase Security Database: Argus needs to know where its database programs are located. The directory is usually c:\Program files\Firebird\Bin or c:\Program files\Borland\Interbase\Bin or c:\Program files\Interbase\Bin. This setting is detected automatically by the Settings Controller.

Delete messages not able to be decrypted: if ArgusMessenger detects a message that cannot be decrypted when downloaded from the mail server, this Argus installation might perhaps not have been set up for PKI. In such a case, once the settings have been upgraded the ‘bad’ message can be downloaded (and decrypted) successfully. In most cases however, once PKI has been configured such messages are likely to be spam and should simply be removed from the mail server immediately.

Delete all unencrypted messages: This provides a very effective spam blocker, but can cause problems if recipients are returning unencrypted ACKs.

Restrict Saving Password on Registry: users of ArgusMail can have their Argus login password saved locally so that whenever ArgusMail is started it does not ask for the password to be entered. This check box prevents all users at a site from using this feature, thereby closing this security loophole.

The Encryption Page

This page provides access to advanced PKI functions (hidden from view) for advanced users. The best option for most users is to select the PKI wizard to open the Settings Controller.

The Dial-Up Page

This page provides access to advanced dial up functions (hidden from view) for advanced users. The best option for most users is to select the dial up wizard to open the Settings Controller.

The Mail Rules Page

As already explained in section 2.8.7, Argus can be configured to execute a variety of actions automatically when certain conditions are met. For example, if a certain type of HL7 message is received,

3. Convert the message's HL7 attachment into a PIT file

4. Save the PIT file in a designated location

Whenever ArgusMessenger downloads a message from a POP3 or IMAP server automatic events can be activated according to:

• Who the message is addressed to

• Whether the message was signed by a sender in a trusted group

• Whether the message is encrypted

• Who the sender is

• What type of message it is (HL7 type)

Mail Rules should be configured using step 6 of the Settings Controller.

By checking the ‘Re-process HL7 Messages not matching any rules’ checkbox, you can be sure that all the emails with HL7 message attachments are being processed by at least one rule. When a HL7 message is not processed correctly, Argus will send an error notification email to the system administrator. When a message is marked for reprocessing, the message will be reprocessed every time a mail synchronise is performed until the error has been corrected.

The Mail Rules page shows any previously configured rules, and allows users to add a new rule, or delete or modify an existing rule. Details of a rule can also be shown by selecting a rule and clicking the 'Preview' button.

The wizard explains each step, prompting the user for information that is appropriate to the action that will be performed when the rule is activated.

The Rules Wizard guides users step-by-step through configuring a rule. Many conditions, based on sender, HL7 type, or Mail Rule Template can be added and a specific action can be chosen. In addition, other rule options (such as whether the rule only applies to encrypted messages) can also be set.

Full details regarding the use of the complex Mail Rules wizard are purposely not made public because ArgusConnect wants to encourage users to contact ArgusConnect support for assistance if they decide to configure rules the hard way.

The Trusted Groups Page

Argus can be set up to reject messages that are not from users who belong to a trusted group of senders. For example, a general practice may want to block all incoming messages unless they have been sent by a trusted group of specialists. Argus can verify that incoming messages were digitally signed by the sender.

2.10.2.3 Menu Item – Configure/Accounts

Argus downloads emails from specific email accounts, and sends email on behalf of those accounts. An account or “mailbox” is uniquely identified by an email address.

This concept can best be explained by an example, using the image above that shows an installation of Argus in which one account has been set up.

When Dr Friedrich Hayek wants to use ArgusMail to browse his messages or to send new messages, he logs into ArgusMail with login name radio and password radio.

When ArgusMessenger attempts to synchronise with the mail servers, this is the procedure followed for Dr Friedrich Hayek, using the settings shown:

• ArgusMessenger connects to the ISP denoted by ArgusVoyager (which was set up on the Configure System Details screen

• ArgusMessenger logs into the incoming mail server using radiologist and ilovelinux

• ArgusMessenger downloads messages from the mailbox radiologist@argusconnect.com.au

• If the mail server ArgusVoyager was an IMAP server instead of being a POP3 server, Argus could be configured to download from a folder other than “INBOX” (the default)

• All the messages are deleted from the mail server after being downloaded

• Copies of these messages are saved in the Argus database

• Any messages that Dr Hayek created using ArgusMail, ArgusWord or his letter writer are waiting in his Outbox folder to be sent

• ArgusMessenger logs into the outgoing(SMTP) mail server using radiologist and ilovelinux

• ArgusMessenger sends messages in the Outbox for radiologist@argusconnect.com.au

The process is repeated for the other accounts, labeled 'Andrew Send' and 'Shroz'.

The fields labelled Archive ... Every: define how old a message must be before being labelled as 'archived'. Such messages will be removed from the database the next time Argus performs an archive of the data.

2.10.2.4 Menu item – Configure/Statuses

By using statuses a doctor can describe what has been done to a message or what still needs to be done. The doctors in a practice define a set of statuses they intend to apply to their messages. This definition process can be done in ArgusMail and in ArgusMessenger. The setting of statuses on a message is explained in detail in the document Using ArgusMail.

This page allows statuses to be defined and to have a colour assigned to them that will show up as a tag when messages are viewed in ArgusMail. The statuses that exist when Argus is first installed constitute statuses recommended by GPs who were consulted. An Argus user is free to delete them all and redefine new statuses deemed more appropriate.

2.10.2.5 Menu item – Configure/Address Book Update

Every email program requires an address book. Argus’ address book contains an important piece of data for every entry: an encryption certificate. When an Argus user tries to send an encrypted message to somebody whose address is chosen from the address book, the encryption certificate is retrieved at the same time (from the address book).

Maintaining the contents of the address book can be tedious if a user communicates with hundreds of people. If an Argus user were to set up every entry manually, he would need to fetch a copy of that person’s encryption certificate from the HIC’s server so that it could be saved in the local Argus address book. ArgusConnect therefore maintains an up-to-date address book centrally that contains all this recipient information. It is called the Argus Users Directory.

In order to download from any LDAP address book, you first need to enter the details of the LDAP server you wish to connect to.

Argus Users Directory Page

This allows users to define the location of the Argus Users Directory. For example, if the site knows that a new medical practice in their area is now using Argus, they can search for that practice and add the entry to their local Argus Address Book. This feature is available to all 'Silver' users, and allows copying into the local address book of only one item at a time. The difference between 'Gold' and 'Silver' is explained fully in the document 'Address Management in Argus.pdf'.

Public LDAP Page

As well as being able to update the local Argus address book with entries from the Argus Users Directory, Argus can also download from other LDAP servers which store entries using the standard iNetOrgPerson object type. Argus can also download from a secure LDAP Server using SSL (Secure Sockets Layer). For a standard LDAP download, only the host name, port and context are required.

For a secure LDAP server, as well as entering the default LDAP details listed above, select the 'Use Secure LDAP' checkbox to enter the user name and password used to access the server.

If you wish to download from a secure LDAP server, Argus also requires the location of the certificate used to trust the LDAP server, so that it can be loaded into a special keystore located in the Argus/Messenger directory called '.keystore'. The certificate must be DER-encoded using either binary or printable (Base64) encoding. Check with the LDAP administrator if you do not have this certificate file or you are unsure of your user name or password.

Auto Address Book Update Page

Users can configure Argus to automatically update addresses from any LDAP server, using a service that fires at a set interval.

In the case of 'Silver' users, every item already in the local address book will be refreshed from the Argus Users Directory. For 'Gold' users, the local address book will be updated to contain only the latest copies of entries on the Argus Users Directory that are covered by the profile defined for this site.

2.10.2.6 Menu item – Configure/Change Password

This menu item allows you to change your SYSDBA password used by the Argus administrator. It can also be accessed through the keyboard shortcut Alt+P.

2.10.2.7 Menu item – Show/ACK Manager

When ArgusMessenger sends an HL7 message it expects to receive an electronic acknowledgment If no acknowledgment is received after a number of retries, the message ‘fails’ and ArgusMessenger stops trying. The failure is logged, and a message about the failure is sent to the administrator email address specified on this page.

The administrator can browse all the messages that have failed in order to resend them once the reason for the acknowledgment failure has been resolved.

2.10.2.8 Menu item – Show/Progress

This menu item shows information relating to the download and synchronisation of messages. If a user initiates a synchronise manually, ArgusMessenger switches to this page automatically.

This page displays progress information only and has no editable fields. It can also be accessed through the keyboard shortcut Alt+V.

2.10.2.9 Menu item – Show/Message Logs

Argus keeps track of all the actions it performs, primarily because 99% of the time it is running as a background process. Users can view the System log, the ArgusAgent log and the Address Update log to see what Argus has done within a particular time frame.

The first log entry created when a synchronise begins is coloured grey, and errors are shown in a red font colour.

This page can also be accessed through the keyboard shortcut Alt+G.

2.10.2.10 Menu item – Show/Address Book

This opens the Argus Address Book, which stores addresses that have been:

• entered manually

• downloaded from the Argus Users Directory

• downloaded from a specified LDAP server

Usage of the Argus address book involves a combination of using ArgusMessenger and the ArgusConnect website, and is explained fully in the document 'Address Management in Argus.pdf'. Please refer to this guide to get a greater understanding of the address book services offered by ArgusConnect.

Both downloaded and manually configured sites can be viewed by selecting them from the drop-down list at the top of the page. Briefly, the address book is partitioned into 4 categories:

Argus Users Directory entries: these are uneditable items from the Argus Users Directory. Using the 'Add' button allows users to search the Argus Users Directory for recipients to add to the local address book.

Public LDAP entries: these uneditable items are from an LDAP server other than the Argus Users Directory

Locations: manually entered items that exist primarily for the purpose of storing a public encryption key. When many users exist at the same site, they will all share the same location (encryption) key. Hence they must be linked to the same location entry. This prevents the need to save the encryption key against every practitioner's address book entry, requiring instead that it be captured only once - for the location.

Users are encouraged to use only the Argus Users Directory, not to enter Location and Practitioner items manually.

A practitioner may have it's own email address, but if an email address has been saved for the site to which the account is linked, the account will use the site's email address.

Existing location entries are shown in the table. The details for the selected entry are shown below the table. To edit an existing entry select it from the list, make changes and confirm. Use the 'New' button to add a new site entry. All the fields shown in blue are mandatory. Click the 'Confirm' button to commit any changes, or 'Undo' to cancel. Use the 'Remove' button to delete the selected entry.

Location name: the name of the site, such as a general practice

Resend interval: when an HL7 message has been sent, how long should Argus wait before resending the message if an ACK is not received within the timeout period

Resends before timeout: how many times should a message be resent if an ACK is not received within the timeout period

Certificate: has an encryption certificate been captured for this location

Argus Enabled: Indicates that this recipient is using Argus on the receiving end and will create HL7 messages if possible.

Argus Version: Only enabled when the Argus Enabled radio button is selected. This will determine the type on HL7 message being sent to the recipient.

• If the version is 'Pre 4.2”, PIT messages wrapped inside a ORU_R01 HL7 message will be created.

• If the version is “4.2 or Greater”, all attachments will be wrapped inside a REF_I12 HL7 message will be created.
  
  
  

Practitioners: manually entered items representing individuals who work a location. These entries must be linked to a location otherwise they have no encryption key.

Users are encouraged to use only the Argus Users Directory, not to enter Location and Practitioner items manually.

Using the Address Book users can create new entries, modify or delete existing entries.

Existing entries are shown in the table. The details for the selected entry are shown below the table. To edit an existing entry select it from the list, make changes and confirm. Use the 'New' button to add a new address book entry. Common name, display name, email address, first name and last name (all fields shown in blue) must be entered before saving the entry. You may insert a photograph for each entry and also add encryption and signing certificates. Click the 'Confirm' button to commit any changes, or 'Undo' to cancel. Use the 'Remove' button to delete the selected entry.

A very important field is 'Location for Person'. Every practitioner entry should be linked to a location, but Argus allows for exceptions because it is possible to create a practitioner entry without linking it to a location.

If practitioner is linked to a location:

the practitioner entry uses the location's encryption certificate

if the location entry has an email address, the practitioner entry uses this address

if the location entry has no email address, the practitioner entry may use its own address

If practitioner is not linked to a location:

the practitioner entry may have its own encryption certificate

the practitioner entry may have its own email address

2.10.2.11 Menu item – Action / Send/Receive Mail

This menu item (which can also be accessed through the keyboard shortcut Alt+M) initiates the download of messages from the accounts defined on the Accounts screen. This process will fail if the mail settings for the mail servers and mail accounts have not been set up correctly.

As the download proceeds, ArgusMesenger will swap to the progress page to show what is happening.

This action is not normally done manually, except for the purposes of testing an Argus installation, because it runs as a background service at a preset interval. Refer to step 7 of the Settings Controller 2.8.8.

2.10.2.12 Menu item – Action/Archive Messages

Medico-legal demands may require the retrieval of all messages regarding a patient, even if those messages were sent or received long ago. Since Argus uses a powerful database to store all its data (most notably copies of all incoming and outgoing emails) it has very sophisticated archiving features.

No item of data used or created by Argus is ever deleted

Upon ‘deletion’, data is merely moved into the archive and is easily retrievable. The process of archiving the database creates a single, small file that can be copied on CD to be stored off-site or in a fireproof safe. Argus makes it very easy to retrieve messages from an archive by specifying detailed criteria for the data to be retrieved.

This menu item (which can also be accessed through the keyboard shortcut Alt+A) allows you to create an archive of the current Argus database. The entire database is stored in the archive, whereafter the process removes messages from the database which exceed their defined archive 'age' or have been deleted. Use the Restore feature to restore messages from an archive.

Archiving does not need to be done frequently for sites that send and receive fewer than 500 messages per day. For such sites, quarterly archiving is sufficient.

2.10.2.13 Menu item – Action/Restore Messages

Retrieving messages from an archive requires more information because the user is able to specify exactly which messages must be copied out of an archive and into the current database.

This menu item (which can also be accessed through the keyboard shortcut Alt+R) allows you to retrieve messages from a previously archived Argus database.

First, pick an archive file. Once this is open, specify search criteria for the messages to be retrieved (for example, retrieve all messages pertaining to a particular patient). Hitting the 'Search' button will populate the table at the bottom of the dialog with messages matching the search criteria. Select the messages to be restored and select 'Recover'. These old messages will be copied across into the Argus database and will appear beneath the folder 'Archived' in ArgusMail.

2.10.2.14 Menu item – Action/Back up Database

This menu item (which can also be accessed through the keyboard shortcut Alt+B) allows you to create a backup of your Argus database 'Argus.gdb', the PKI file 'store.psi' and the registry file 'serverregistry.txt'. The backup process will compress these into to a single .zip file.

2.10.2.15 Menu item – Action/Update from Public LDAP

This function allows you to update the 'Public LDAP' section of your local Argus address book with entries downloaded from an LDAP Server. This menu option will only be enabled if you have previously configured the details of an LDAP Server on the 'Public LDAP' tab of the Configure/Address Book Update screen. For more information, see section 2.10.2.5. Selecting the menu option will open the Address Download Stats screen, which provides detailed information on connecting, searching and downloading entries from the LDAP Server. The information displayed here is also saved in the Addresss Update Log (see section 2.10.2.9).

2.10.2.16 Menu item – Action/Update from Argus Users Directory

This function allows you to update the existing entries in the 'Argus Users Directory' section of your local Argus address book with entries downloaded from the Argus Users Directory. This menu option will only be enabled if you have previously configured the details of the Argus Users Directory server on the 'Upadte from Argus Users Directory' tab of the Configure/Address Book Update screen. For more information, see section 2.10.2.5. Selecting the menu option will open the Address Download Stats screen, which provides detailed information on connecting, searching and downloading entries from the Argus users Directory. The information displayed here is also saved in the Addresss Update Log (see section 2.10.2.9).

3 Hints, allegations and things left unsaid

If you have any suggestions for future versions or Argus, please feel free to send your suggestions to support@argusconnect.com.au or phone the ArgusConnect helpdesk on (03) 5335 2221 during business hours.

--- fin ---

Andrew Shrosbree, Rachel Naus

October 2006