|
ArgusConnect
Pty Ltd |
Using ArgusMail
Last
Updated:
Table of Contents
2.2 The ArgusMail Main Screen 3
2.3 Folders - organising your data 4
2.3.3 The ‘Redirected’ folder 6
2.3.5 The ‘Outbox’ and ‘Sent’ folders 7
2.3.6 The ‘Acknowledgements’ folder 7
2.4 The Message Pane – viewing more than headers 7
2.4.1 Viewing information without opening a message 8
2.4.3 Editing a comment without opening a message 10
2.4.4 Editing a status without opening a message 10
2.4.8 Save 11
2.4.9 Delete 11
2.4.10 Print 12
2.5.1 View 12
2.5.2 Export 12
2.5.3 Save 12
2.6 Attachment Viewer Pane: viewing HL7, RTF, PIT as HTML 13
2.7.2.1 Configuring Argus for MAPI 17
2.7.2.2 Configuring Medical Director or MedTech32 to use Argus MAPI 17
2.7.2.3 Using the MAPI interface in MedTech32 and Medical Director 22
2.7.2.4 Confirming the message 24
This is a detailed
guide outlining the features and use of ArgusMail.. It is the
second in a set of documents comprising:
Using ArgusMessenger
Using ArgusMail
Using ArgusAgent
Using ArgusWord
Using 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.
|
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
|
|
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. |
ArgusMail is the client application – a sophisticated message viewer designed specifically to facilitate the viewing of clinical messages in a meaningful way. It hides raw HL7 data by presenting clinical information neatly formatted. Before opening ArgusMail you will need to login, using the details your Argus administrator has set up for you in ArgusMessenger.
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 ArgusMail is started).
|
|
|
Figure 1: The ArgusMail login dialog, showing database location information |
The database is called Argus.gdb and is located in the \Argus\Database\ directory. e.g. c:\Program Files\Argus\Database\Argus.gdb. In the installation shown in the screenshot below, the database is location is C:\Argus\Database\ArgusBackup.gdb. The host field refers to the IP address of the PC where the database is located. localhost refers to the current PC. ArgusMail seeks Argus.gdb automatically.
After logging in you will see the main screen of ArgusMail. Each of the areas labelled in the figure below is described in greater detail in the following sections.
|
|
|
Figure 2: The ArgusMail main screen |
2.3 Folders - organising your data
All messages downloaded from the mail server into the Argus database are shown in folders.
Users can manage their messages by moving them between folders, creating private folders, sharing folders to other doctors and looking at the messages in folders belonging to other doctors. ArgusMail can also be configured to automatically ‘redirect’ (share) messages to other doctors. In the examples shown here, a practice has three doctors: Bill Brown, John Green, Greg Black, and Sally Grey.
When Bill Brown logs into ArgusMail, the folder tree shows this information:
|
|
|
|
Figure 3: The Folder Tree, showing popup menu |
|
Basic Folder Usage:
Users can create new folders at any level.
Folders can be renamed, deleted and moved (except for the Inbox, Redirected, Shared, Archived, Sent, Outbox, and Acknowledged folders which cannot be renamed or deleted).
Folder editing operations can be accessed via a popup menu, or from the toolbar.
Folders containing unread messages are shown in bold.
A folder shows how many messages it contains e.g. “Inbox (5)”. A folder which contains unread messages will display the number of unread messages also e.g. “Inbox (1/5)”.
Users can share their messages, i.e. allow other users access to the contents of specific folders. The message itself is not duplicated – it is simply shared between more then one user. When the user wants to share a folder, this screen appears:
|
|
|
Figure 4: The Share Folders dialog |
After sharing the Referrals folder to Greg Black and Sally Grey, Bill Brown's folder tree now shows this information:
|
|
|
|
Figure 5: Showing shared folders |
|
The images above show what Bill Brown will see if he has shared his Inbox to Greg and Sally. When Greg or Sally log into ArgusMail they will see Bill’s 'Referrals' folder under their Shared folder.
|
|
Both Greg and Sally:
|
|
Figure 6: Viewing somebody else's folders |
|
All incoming messages go into the doctor’s Inbox. If a doctor is unable to read his messages because he is away from the practice, ArgusMail can be configured to put all messages into his Redirected folder instead. Another user in the practice will be designated to read his incoming messages. When selecting a person to whom mail must be redirected, the Redirected folder is simply shared to that person.
|
|
|
Figure 7: Configuring redirection |
The Redirected folder is like any other folder: a user could share it with more than one person. Redirection merely allocates one user by default to see the redirected messages. This process can also be accomplished by having the doctor who will be away share his Inbox to somebody else. The idea of ‘redirection’ is simply to help him keep track of which messages arrived while he was away.
Shows messages that have been restored from an archive.
2.3.5 The ‘Outbox’ and ‘Sent’ folders
When a message is ‘sent’ by ArgusMail the message is not physically sent, but placed in the Outbox (recall that ArgusMessenger actually sends messages). An ordinary message (has no HL7 attachment) for which no ACK is required to be returned is copied into the Sent folder as soon as ArgusMessenger has sent the message. By contrast, if a message has an HL7 attachment it is only moved to the Sent folder when a matching ACK is received, or when ArgusMessenger counts the preset number of resends down to zero.
2.3.6 The ‘Acknowledgements’ folder
All ACKs received by Argus in acknowledgement of HL7 messages that were sent by Argus are dropped into this folder. It is emptied once the database has been archived.
2.4 The Message Pane – viewing more than headers
When a folder is selected, all messages in that folder are shown in the message pane. In addition to the standard header and date information, the first three columns and the last two columns display icons. From left to right, they convey the following information:
icon 1 is shown if the message has an attachment
icon 2 is shown if comments have been added to the message
icon 3 is shown once somebody has allocated a status flag to the message
icon 4 shows an icon with a blue arrow if a message has been sent encrypted; a green arrow if the message was received received; and no icon if the message was not encrypted
icon 5 in the 'Outbox' indicates if an acknowledgement is pending; in 'Sent' indicates whether the message has been acknowledged; in all other folders indicates if there has been an export error
For confidentiality reasons patient names are unlikely to appear in either the header or body of a message. Such information should be embedded inside HL7. If the attachment to a message contains HL7 data, Argus shows the names of any patients it finds embedded in the HL7. Having extracted patient data from the message allows Argus to offer a sophisticated search facility that allows a doctor to search for all messages relating to a particular patient.
Multiple discontinuous selections are allowed for facilitating multiple deletions, moves, copies, etc. Drag and drop is supported so that messages can be easily moved between folders. Unread messages are shown in bold.
|
|
|
Figure 8: The Message Pane |
Columns can be moved and sorted by clicking on the column headers. The direction of sorting is shown with an icon indicating the sorting direction.
2.4.1 Viewing information without opening a message
Viewing the message and all its associated data such as comments and statuses does not require it to be opened (see later). Colour coding is used to show the most recent status added to a message. In other words, the current status of all messages will be easy to tell by looking at the message list. A message need only be opened for the editing of comments and statuses. When these have been edited it is possible to see their contents by floating the mouse cursor over the icons shown above. The comment/status pops up in a yellow box:
|
|
|
Figure 9: Message Popups - Statuses |
The image above shows a message that has a status of “Follow Up Complete”. The pop up shows:
This message has a status (messages without statuses have no coloured square next to them)
The status was Added by Bill Brown
The exact timestamp was recorded.
Statuses describe what has been done to a message, not 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.
In a similar way to showing statuses, comments can be shown without opening a message:
|
|
|
Figure 10: Message Popups - Comments |
A message need only be opened for the editing of comments and statuses. The message window shows everything visible on the front screen, but has additional fields to allow the setting of the status, addition of comments and to flag the message for archiving.
To change the status, select a status from the statuses list and select the Add button. The new status is appended to the list of previous statuses, thus defining a sequence of events. A status is recorded with a date and the name of the person who set the status.
The user can load the next/previous message without closing the window.
|
|
|
Figure 11: The Message Window |
The current status of a message can be changed. A new status can be selected from the status list, after which the Add button appends the new status to all previously selected statuses.
2.4.3 Editing a comment without opening a message
Comments can be edited without opening a message, simply by clicking on the post-it icon.
|
|
|
Figure 12: Editing comments |
2.4.4 Editing a status without opening a message
Comments can be edited without opening a message, simply by clicking on the coloured status icon.
|
|
|
Figure 13: Editing statuses |
The body of the message is shown with its header information. This can be printed out and saved.
|
|
|
Figure 14: The message body (showing popup menu) |
These are standard mailing operations that will show the ‘create message’ dialog (explained later).
The body can be opened in an independent window.
The user can choose a file name for the body to be saved as a text file.
The message is marked for removal to the archive and hidden from view.
Shows the standard printing dialog for the user to print as many copies as required.
Attachments are shown in a list on the right bottom corner of the main panel. Some types of attachments can have their (reformatted) content shown in the HTML pane. Refer to section 2.6 for a description of the attachment viewer pane.
|
|
|
Figure 15: The attachment list (showing poup menu) |
The attachment is opened in a separate window if it contains ordinary text, RTF text, HTML or HL7 for which ArgusMail has been configured. ArgusMail can be configured to open attachments with a specific program. Thus DOC files can be opened in WordPerfect, BMP files in Paintshop. Follow the main menu to Tools/Configure/File Associations and see section 2.6.1.4 for more details.
The concept of an “export” has a very specific meaning in Argus. Each user can configure an export directory (Follow the main menu to Tools/Configure/Personal Settings/Messages/Export Directory and see section 2.6.1.1 for more details). When ‘export’ is requested, the relevant document, attachment or message is saved into the export directory, without asking the user where it should be saved. A ‘tick’ icon next to the file name indicates that the attachment has been exported.
Saving has the same outcome as an export, but the user is asked to specify where the file should be saved.
2.6 Attachment Viewer Pane: viewing HL7, RTF, PIT as HTML
ArgusMail offers a friendly way to view not only the contents of a message body, but also the contents of attachments without the user having to open them. The panel at the bottom of the ArgusMail window does more than display the contents of standard text, RTF, or HTML attachments.
|
|
|
Figure 16: The attachment viewer pane (showing popup menu) |
For legal reasons, whatever the doctor sees in the attachment viewer pane is an image of a document which has been saved ONCE on the database. Since there is no run-time merging or conversion happening when the doctor selects the message, any investigation will reveal precisely what the doctor saw.
If an attachment contains an HL7 message ArgusMail converts the HL7 into plain HTML. The raw HL7 data in the attachment stays hidden (unless the user specifically wishes to see it). ArgusMail can correctly be described as an “HL7 viewer”.
Technical aside: Using its configurable HL7 engine ArgusMail converts the HL7 into XML, runs it through an XSL translator and saves the result as plain HTML. This happens once, when the message is first downloaded from the mail server.
ArgusMail can also display RTF attachments in the HTML pane. This requires no conversion.
HTML attachments can also be viewed in the attachment viewer pane. This requires no conversion.
In some cases where the senders of clinical messages insist on embedding formatted text (RTF, PIT) in the OBX segment of an HL7 message, ArgusMail can strip out the formatted text and present it superimposed on a GIF background.
The CCeH, the Health OpenWare Foundation and ArgusConnect do not endorse the use of PIT.
|
|
|
Figure 17: The Attachment viewer pane (shwoing PIT that has been extracted from a HL7 message) |
This is the same as for the attachment list.
|
|
|
Figure 18: The Tools menu (expanded) |
Each user is able to configure ArgusMail to their specific needs. Some of these settings are controlled centrally, via ArgusMessenger, but the user can override the defaults.
The administrator can configure most of these settings in ArgusMessenger.
|
|
|
Figure 19: The configure dialog (showing the personal settings page) |
Mail login details – users should change only their password. Their administrator is able to see the password in ArgusMessenger if the user has forgotten it.
Redirect incoming messages - is explained in section 2.3.3 and can be done with the Folders popup menu.
Export directory - is explained in section 2.5.2. Enter any valid directory that will not be removed.
Signature – select a text file for text to be added to the foot of any message you send.
Saving password at login – asks ArgusMail to save the login details in the local (encrypted) registry file so that the user does not need to log in every time ArgusMail is run. This makes ArgusMail insecure because anybody can run ArgusMail to read this person’s email.
Save program log file – assists programmers to track errors by producing a trace of every statement being executed within Argus.
Statuses should be defined by the administrator, in ArgusMessenger. Refer to the document “Guide C - how to use ArgusMessenger”
This allows attachments to be opened using a specific program. For instance, to open all WRI attachments with Ms Word:
File Type =
wri
Program = c:\Program Files\Microsoft Office\Office\Winword.exe
Argus has the ability to function as the default mail client. This means that in any Windows program, if you click a button labelled 'Send Email' or select the menu File\Send To\Mail Recipient (as attachment) then instead of having Outlook (for example) pop up its send dialog, the Argus send dialog appears instead. The document you are busy with will be attached to the new email message.
What makes Argus' handling of MAPI different is this: if you try to send a referral letter that contains a few specific text labels that Argus can recognise, Argus will not simply attach your letter. Argus will instead create a PIT file that it can embed inside an HL7 message. This enables a receiver of your email message to have a PIT file dropped into a practice software directory in the same way that results can be received. The PIT file will be uploaded into the patient record, in either the Results or the Letters section. Another advantage of using Argus is that an acknowledgement message will be returned providing a guarantee of delivery.
If Argus does not recognise your document because it cannot find the text labels, or because it is something like a Powerpoint slide, the document is attached as is.
In order to use the MAPI interface with Argus you will need to configure your copy of Argus to Send Mail using MAPI. You can then use Argus MAPI to send HL7 or PIT files from within Medical Director or MedTech32.
2.7.2.1 Configuring Argus for MAPI
Configuring Argus for MAPI involves the following steps:
1. Create an address book entry for the Receiver of the email
You will need to create a Site address book entry (see section ) and a practice address book entry (see section ). The practice address will need to associated with a Site Address.
The Site address book entry will allow Argus to determine if the user can receive "Wrapped Messages". These are PIT files wrapped in HL7. If the site can not receive "Wrapped Messages" a PIT message will be created.
2. Set Argus as the default MAPI client
Using ArgusMail select the menu option Tools->Set as Default Mail client. NOTE: Medical Director Users will need to specify to use 'Simple MAPI'. This is done by opening the Letter Writer from the main menu in Medical Director (Tools -> Letter Writer), then opening the preferences dialog from the Letter Writer menu (File -> Preferences) then selecting the 'Advanced' tab and choosing the 'Simple MAPI' radio button.
2.7.2.2 Configuring Medical Director or MedTech32 to use Argus MAPI
To use Argus MAPI to send HL7 or PIT files using Medical Director or MedTech32 you need to create a new letter which includes at least the following two lines of information, which can appear anywhere in the document:
Patient Name: “Last Name, First Name” DOB: “Patient Date of Birth”
Referred By: “Referring Doctor Name” Date of Report: “Current Date”
For example (simplest):
Patient Name: MOORE, Mr Anthony DOB: 05/06/59
Referred By: Dr D Cossetto Date of Report: 12/12/2006
or (with line and tab spacing)
Patient Name: MOORE, Mr Anthony DOB: 05/06/59
Referred By: Dr D Cossetto Date of Report: 12/12/2006
or(with line and tab spacing and 'Referred By:' at the top)
Referred By: Dr D Cossetto Date of Report: 12/12/2006
Patient Name: MOORE, Mr Anthony DOB: 05/06/59
or(with lines reversed and separated by text)
Regarding:
Patient Name: MOORE, Mr Anthony DOB: 05/06/59
Dear David
Please investigate the upper thoracic region on Mr Moore.
Yours sincerely,
Dr Katherine Janeway
Referred By: Dr D Cossetto Date of Report: 3rd June 2004
and so on.
There are many different combinations of lines that can be used to create a HL7 message depending on the level of information that is to be placed in the HO7 message to be created. The following are examples of lines you can use to create a HL7 message.
Receiving doctor lines:
Referred By: Dr D Cossetto Provider No: Q1234567 Date Of Report: 12/12/2006
Recipient By: Dr D Cossetto Provider No: Q1234567 Date Of Report: 12/12/2006
Referred By: Dr D Cossetto Date Of Report: 12/12/2006
Recipient By: Dr D Cossetto Date Of Report: 12/12/2006
N.B. The “Provider No:” tag is an optional tag
Patient Details
Patient Name: MOORE, Mr Anthony DOB: 05/06/59 Sex: M
RE: MOORE, Mr Anthony DOB: 05/06/59 Sex: M
Patient Name: MOORE, Mr Anthony DOB: 05/06/59
RE: MOORE, Mr Anthony DOB: 05/06/59
N.B. The “Sex:” tag is an optional tag
Reference and Medicare Number
Reference: 1234567 Medicare No: 1234 1234 1324 4
Reference: 1234567
N.B. The tags “Reference:” and “Medicare No” are both optional tags
Report Type
Report Type: Letter
N.B. The tag “Report Type:” and is an optional tag. This tag indicates the report type inside a PIT message. Will be 'LETTER' if any index of 'Letter' is found in the report type tag.
Obviously, the easiest way to automate this process is to create a template in which the labels exist already.
Creating a template with Medical Director
Using the Tools Menu from the Mail Screen Open the Letter Writer (F8).
|
|
|
Figure 20: Opening the Letter Writer in Medical Director |
Next Select the File menu then the Modify Template menu option.
A Dialog will then be presented allowing you to modify an existing template or to create a new one.
To create a new template select “Blank Letter” from User defined Templates list then click Open.
Create the following two lines of text, by typing in the field names (e.g. 'Patient Name:') and then inserting the field (e.g. '<<Patient Demographics:Surname>>') from the Template Fields list on the right. Your template should include the following information:
Patient Name:<<Patient Demographics:Surname>>, <<Patient Demographics:First Name>> DOB: <<Patient Demographics:DOB>>
Referred By: <<Addressee:Name>> Date of Report: <<Miscellaneous:Date>>
Note: You can change the font but:
the labels 'Patient Name:' and 'DOB:' must be on the same line.
the labels 'Referred By:' and 'Date of Report:' must be on the same line.
The fields must be added in exactly the order as shown above.
|
|
|
Figure 21: Creating the MAPI template in Medical Director |
Add any other text (including fields if required) that you would like to appear in your template.
Select the File Menu then select “Save as Template”
Choose a Name for the new Template then click the save button.
Creating a template with MedTech32
Using the Setup Menu Select the “Inbox/Outbox” Sub Menu then select the “Outbook Document” menu.
|
|
|
Figure 22: The 'Outbox Document' menu item in MedTech32 |
This will open the Document Designer window.
Click the top left button in the Document Designer “Add a new Document”.
|
|
|
Figure 23: Creating a new Document in MedTech32 |
Fill in the Template Code, Description and any other relevant information. Click on the Document tab.
Create the following two lines of text, containing the labels (e.g. 'Patient Name:') and then insert the fields (e.g. '[PAT_SURNAME]') from the 'Merge Symbol' list (shown by selecting the 'Insert' button on the toolbar. Your template should include the following information:
Patient Name: [PAT_SURNAME], [PAT_FIRSTNAME] DOB: [PAT_DOB]
Referred By:[GP_SURNAME], [GP_GIVENNAME] Date of Report:[MIS_TODAY]
Note: You can change the font but:
the labels 'Patient Name:' and 'DOB:' must be on the same line.
the labels 'Referred By:' and 'Date of Report:' must be on the same line.
The fields must be added in exactly the order as shown above.
|
|
|
Figure 24: Creating the template in MedTech32 |
Add any other text (including fields if required) that you would like to appear in your template.
Next click on the OK button on the bottom of the window.
2.7.2.3 Using the MAPI interface in MedTech32 and Medical Director
How to Email a letter with Medical Director
Ensure you have a patient record open.
Press Ctl+T or select the “Letter Writer” option from the tools menu.
Select the “New” menu option from the File Menu.
Select the Template you created in the previous step then click OK.
|
|
|
Figure 25: Selecting the template in Medical Director |
You will then be asked to select a recipient for the message.
If the intended recipient is not in the address book you can add them using the add button. The email address must match an item in the Argus address book.
After you have selected the recipient click OK.
|
|
|
Figure 26: Selecting an address for the letter in Medical Director |
After you have finished creating the letter select the File -> E-mail -> Send... menu option to send the Message. The 'Send Letter As' radio button must be set to 'Attachment (Rich Text Format)' unless you want the letter to appear in the body of the email instead of as an attachment.
See the next section (2.7.2.4) to continue.
How to Email a letter with Medtech32
Ensure you have a patient record open.
Select the Module Menu then the “Outbox” sub menu option then select the “New Document” option.
You will then be presented with the “New Patient Document” window.
Select the template you created above using the document drop down combo box.
|
|
|
Figure 27: Selecting the template in MedTech32 |
Next Select the button next to the to address text box labeled “...” to open the address book.
If the intended recipient is not in the address book you can add them using the add button (Only after searching for them). The email address must match an item in the Argus address book
After you have finished creating the letter select the “Send Via” Button then select the “email” option.
See the next section (2.7.2.4) to continue.
2.7.2.4 Confirming the message
When you choose to send the letter the Argus Login Dialog will appear. The first time you send a letter after you open your Clinical Desktop System you will be asked for your Argus Mail login details.
Note: this is not SYSDBA, which is used for logging into ArgusMessenger. It is an Argus account login ID. Refer to the 'Accounts' page in ArgusMessenger if you are unsure of your login ID.
After you have logged into ArgusMail as an Argus User the New Message Dialog will appear allowing you to make any further alterations to the new Message before sending it.
If the message can be sent as PIT embedded inside HL7, an attachment with an HL7 extension will be visible.
|
|
|
Figure 28: Viewing the newly-created email message in ArgusMail |
When a message is downloaded from the mail server, if it contains an HL7 attachment Argus retrieves data from the HL7 code. This data is stored in fields separate to the attachment itself (which is stored as an unreadable blob). A user can thus search for information that may not have been in the header or body of the message. The search dialog is used to specify a number of attributes of sought messages, such as the patient name or the date of receipt.
|
|
|
Figure 29: The search dialog |
The search shown above was for any messages which where the sender of the message contains 'argus5'. As you can see, three messages were returned. These messages can be opened (by double-clicking on them) and edited in the same manner as on the main ArgusMail screen.
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
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
Can wrapped messages
can be received: does this recipient have the ability to receive PIT
messages wrapped inside HL7 (yes, if the receiving location is using
Argus)
|
|
|
Figure 30: The Address Book showing preconfigured locations |
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 and email address (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.
|
|
|
Figure 31: The Practice Address Book |
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.7.4.1 Using an address in a new message
When the Address Book is opened from the New Message dialog, two extra toolbar buttons are available.
|
|
|
Figure 32: The Address Book toolbar, showing extra buttons for using an address in a message |
The 'Use' button simply adds the selected address(es) to the 'To' field of the current message, and keeps the Address Book open. This feature is helpful if the message has multiple recipients. The 'Use now' button adds the selected address to the 'To' field of the current message and closes the Address Book.
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