Advanced Interactive Sending

This version of the agent is no longer current.

Overview

In order for interactive sending to work correctly, the agent needs to determine which workstation to pick up and send the file generated by the clinical applications.

This requires either:

  • the clinical application is configured to save files to a different directory for each user

or

  • each user logs into Windows as a different account, and are the default owner of files which they create

Scenarios

Separate Physical Workstations

This scenario applies to situations where all the following conditions are matched:

  1. a shared desktop application is not being used (such as Terminal Services or Citrix)
  2. the clinical application is not configured to save to the same directory for each user

An example of this scenario is where each sender has their own workstation, with the clinical application installed locally. The clinical application is configured to save files to the workstation's C: drive.

Install the agent on each of the workstations, configured to monitor the appropriate C: directory.

Different Directory per User

This scenario applies to situations where all the following conditions are matched:

  1. the clinical application is configured to save files to a different directory for each user

For example, when User A is running the clinical application, their files are saved to \\SERVER\ReferralNet\UserA, and when User B is running the clinical application, their files are saved to \\SERVER\ReferralNet\UserB.

The agent can simply be configured to monitor different directories for each user.

Shared Directory by File Owner

This scenario applies to situations where all the following conditions are matched:

  1. the clinical application is configured to save files to the same directory regardless of user
  2. each user logs into Windows with a different account
  3. the files created by their accounts have their owner set to their account name

In this scenario, the Agent looks at the owner of each file, and will only prompt to send files created by the current user.

If two people are logged in at the same time using the same Windows account, this scenario will not work.

For non-administrators (Windows accounts which are not a member of any Administrators group), when a file is created, its owner is set to the current user's account. However should the account be a member of any of the Administrators groups (such as local administrators, or domain administrators), Windows will set owner of the files created to Administrators, not the current user. If this is the case, the agent is unable to uniquely identify the correct creator of the file and this scenario will not work.

Using Drive Mappings

You can use per-user mapped drives to allow saving of files to a different directory for each user, even if this isn't natively supported in the clinical application.

  1. create a directory under each user's profile (eg. \\SERVER\user$\ReferralNet_Outgoing)
  2. in the user's login script, map a network drive to the share (eg. map R: to \\SERVER\user$\ReferralNet_Outgoing)
  3. configure the clinical application to save to R:
  4. configure the agent to send from R:

Example login script extract:

IF EXIST R:\NUL.EXT NET USE R: /DELETE
IF NOT EXIST "%HOMESHARE%\ReferralNet_Outgoing\NUL.EXT" MKDIR "%HOMESHARE%\ReferralNet_Outgoing"
NET USE R: "%HOMESHARE%\ReferralNet_Outgoing"
 
agent/3.2/advanced_sending.txt · Last modified: 2011/01/20 14:14 (external edit)