Radworks™ WorkGroup Server  v5.1®

Migrating film-based workflow to a PACS-workflow will determine the acceptance of softcopy reading.  It is vital to understand the way a department operates and how to translate it's way of working into a digital environment.  Such a task is, however, far from straightforward.  It requires a thorough knowledge of workflow concepts and demands extensive consultation with users.

The Answer

Workflow issues can be simplified if functional groups of user can be defined.  If there are user groups that share the dame data, the routing of data can be reduced to simply addressing a group instead of each user individually.  All users in such a workgroup would have access to the same data as if it were on their local system.  This functionality is provided through the Workgroup Server Module for Radworks Viewing Applications.

The Workgroup Server (WGS) allows the workgroup users to share the same data of the WGS.  In practice, this means that clients have simultaneous access to all studies routed to the server machine.  There is no need for them to import the studies to their local computer; the data appears as if it was local.  A straightforward file-locking  mechanism on the server prevents studies being opened by more than one client at the same time.  A client who attempts to open a study in use by a colleague will receive a message informing them of this.  The client will, however, be able to view the study with no options to save changes.

Configuration

The WGS is available as an option on Review and Diagnostic level software.  The server machine also can be used as one of the workgroup clients.  Standard, Review, and Diagnostic level software products can be used as clients.  The maximum number of clients is five, total (inclusive to the server).

In Practice

Users will hardly notice any difference between working on a stand-alone machine and on a workgroup client.  The clients are regular Software Viewing licenses except that all clients share the same data, centrally stored on the server. 


Integrity of User Settings

The WGS does not affect user settings.  All preferences remain intact as if it were a stand-alone machine.

Workflow Examples:

Group Reading

The WGS can simplify complex routing schemes.  Imagine, for example, a situation in which two modalities, a CT and a CR, route their studies to the same WGS.  In principle, every client on this server has access to all studies.  However, by applying appropriate database views, CT's can be shown to one user and CR's to another.  No further workflow rules are required; a simple definition of a database view will suffice.

Intensive Care Unit

In the ICU, only images of patients in the ICU ward are requested.  Doctors and nursing staff wish to see all newly created images plus relevant prior studies on a monitor alongside the patient's bed.  This can also be realized by using the WGS.  Creating a database view filtering on the patients name will result in only those studies belonging to the patient being shown.


Click to Enlarge

 

Features 

Performance Considerations

Performance  is of course an important issue in a Workgroup environment.  Several clients connected to one server and sharing network capacity can be expected to influence the system's overall performance.  Major points considered are:

  1. Machine speed.  The server in particular should be a fast machine with large memory capacity.
  2. Network throughput will directly improve overall performance.
  3. Network  architecture.  Using a dedicated network physically separated from the LAN will dramatically improve workgroup performance.  This will assist in handling large data volumes such as CR's.

Client

  • Maximum number of clients is limited to 5.  This includes the server in the event that it is used as a client.
  • Standard, Review or Diagnostic level software applications can be used as clients
  • LAN-based client is strongly suggested for performance reasons

 


Click to Enlarge

 

Click to Enlarge