App Synch v4.3 Install - Service Manual (MAN-05940) English Rev - 002 10-2019

Application
Synchronization
Between Hologic and Third-Party Applications
Installation and Service Manual

For Software Version 4.3
Part Number MAN-05940
Revision 002
October 2019
Product Support
USA: +1.877.371.4372
Europe: +32 2 711 4690
Asia: +852 37487700
Australia: +1 800 264 073
All Other: +1 781 999 7750
Email: BreastHealth.Support@hologic.com
© 2019 Hologic, Inc. Printed in the USA. This manual was originally written in English.
Hologic, SecurView, MultiView and associated logos are trademarks and/or registered trademarks of Hologic, Inc., and/or its
subsidiaries in the United States and/or other countries. All other trademarks, registered trademarks, and product names are the
property of their respective owners.
This product may be protected by one or more U.S. or foreign patents as identified at www.Hologic.com/patents.
Application Synchronization 4.3 Installation and Service Manual
Table of Contents
Table of Contents
List of Tables __________________________________________________________________ ix
Chapter 1 Introduction __________________________________________________________ 1

1.1 About This Manual................................................................................................................................................. 1
1.2 Document Conventions ......................................................................................................................................... 2
1.3 Terms and Definitions............................................................................................................................................ 3
Chapter 2 Application Synchronization Description ________________________________ 5

2.1 Application Synchronization Overview .............................................................................................................. 5
2.1.1 Installation location guidelines for Hologic products and TPAs: ......................................................... 5
2.2 Third-Party Applications ....................................................................................................................................... 8
2.3 Notification Area Icon .......................................................................................................................................... 11
Chapter 3 Installing Application Synchronization _________________________________ 13

3.1 Required Tools and Materials ............................................................................................................................. 13
3.2 Pre-installation Checklist ..................................................................................................................................... 13
3.3 Recording Application Configurations ............................................................................................................. 15
3.4 Backing Up and Configuring Licenses on SecurView ..................................................................................... 15
3.5 Checking the System for Active Network Connections .................................................................................. 16
3.6 Upgrading Application Synchronization .......................................................................................................... 16
3.7 Installing Application Synchronization ............................................................................................................. 17
3.8 Configuring Application Synchronization Software ....................................................................................... 20
3.9 Completing the Installation ................................................................................................................................. 20
Chapter 4 Configuring Application Synchronization _______________________________ 21

4.1 Configuration Interface Overview ..................................................................................................................... 21
4.2 Application Sync Management........................................................................................................................... 22
4.2.1 Application Sync Config ........................................................................................................................... 22
4.2.2 Message Success Criteria .......................................................................................................................... 23
4.2.3 Licensing ..................................................................................................................................................... 24
4.2.4 Import Config ............................................................................................................................................. 27
4.2.5 Export Config ............................................................................................................................................. 29
4.2.6 Application Tester ..................................................................................................................................... 30
4.3 Application Management .................................................................................................................................... 32
4.3.1 Add /Edit Application............................................................................................................................... 32
4.3.2 Type ............................................................................................................................................................. 33
4.3.3 Comm .......................................................................................................................................................... 34
4.3.4 XML Mapping ............................................................................................................................................ 34
4.3.5 Message Type ............................................................................................................................................. 40
4.3.6 OpenPatient Data....................................................................................................................................... 42
4.3.7 OpenPatient Filters .................................................................................................................................... 44
4.3.8 Misc.............................................................................................................................................................. 46
MAN-05940 Revision 002 v

Table of Contents
4.3.9 Finish ........................................................................................................................................................... 47

4.3.10 Application List.......................................................................................................................................... 48
4.4 Log Management .................................................................................................................................................. 50
4.5 Supported Applications ....................................................................................................................................... 51
Chapter 5 Application Types ____________________________________________________ 63

5.1 Hologic Proxy Partner.......................................................................................................................................... 63
5.2 Hologic SharedFile Partner ................................................................................................................................. 65
5.3 Hologic TCP/IP Partner ....................................................................................................................................... 67
5.3.1 TCP/IP Communications Page................................................................................................................. 68
5.4 Application Types ................................................................................................................................................ 69
5.4.1 Agfa TalkStation ........................................................................................................................................ 71
5.4.2 Allscripts (Eclipsys) Sunrise Radiology .................................................................................................. 72
5.4.3 Amicas Vision Series v4.0-5.1 and v5.5 ................................................................................................... 73
5.4.4 Candelis ImageGrid RIS ........................................................................................................................... 74
5.4.5 Commit; Screening MIS ............................................................................................................................ 74
5.4.6 Crescendo CSCIntegration for DigiDictate-IP ....................................................................................... 75
5.4.7 Dataworxs AudioWav Mic ....................................................................................................................... 76
5.4.8 Dolbey FusionDictate ................................................................................................................................ 77
5.4.9 Dolbey FusionExpert ................................................................................................................................. 78
5.4.10 Epic Radiant RIS ........................................................................................................................................ 79
5.4.11 Euromed MedSpeech ................................................................................................................................ 81
5.4.12 G2 Speech MediSpeech ............................................................................................................................. 81
5.4.13 GE Centricity PACS ................................................................................................................................... 83
5.4.14 GE Centricity RIS-IC ................................................................................................................................. 84
5.4.15 GE/IDX Imagecast ..................................................................................................................................... 87
5.4.16 Insight OmniCare ...................................................................................................................................... 91
5.4.17 Intelerad InteleViewer .............................................................................................................................. 91
5.4.18 Lanier Serial ................................................................................................................................................ 92
5.4.19 M*Modal Fluency for Imaging Reporting .............................................................................................. 94
5.4.20 MagView (as Hologic SharedFile Partner) ............................................................................................. 95
5.4.21 MagView ..................................................................................................................................................... 96
5.4.22 MammaSoft ................................................................................................................................................ 97
5.4.23 MaSc RIS ..................................................................................................................................................... 98
5.4.24 Medicalis Professional .............................................................................................................................. 99
5.4.25 MedOutlook RIS ........................................................................................................................................ 99
5.4.26 MedQuist SpeechQ .................................................................................................................................. 100
5.4.27 MRS ........................................................................................................................................................... 104
5.4.28 MultiView or Aegis ................................................................................................................................. 104
5.4.29 peerVue qiVue ......................................................................................................................................... 106
5.4.30 PenRad ...................................................................................................................................................... 107
5.4.31 Philips iSite PACS .................................................................................................................................... 109
5.4.32 PowerScribe or EWS ................................................................................................................................ 111
5.4.33 PowerScribe bi-directional ..................................................................................................................... 114
5.4.34 QDoc Study Viewer ................................................................................................................................. 117
vi MAN-05940 Revision 002

Table of Contents
5.4.35 RadNet VDI .............................................................................................................................................. 117

5.4.36 ScImage Picom Client.............................................................................................................................. 119
5.4.37 SecurView ................................................................................................................................................. 119
5.4.38 SecurView Serial Partner ........................................................................................................................ 121
5.4.39 Selenia AWS ............................................................................................................................................. 122
5.4.40 Softek Illuminate InSight ........................................................................................................................ 123
5.4.41 Spantel Audio Recorder .......................................................................................................................... 124
5.4.42 syngo Workflow Portal Radiologist ...................................................................................................... 125
5.4.43 syngo Workflow ReadExam................................................................................................................... 126
5.4.44 WinScribe Internet Author ..................................................................................................................... 127
Chapter 6 Configuring Study List Manager (SLM) ________________________________ 129

6.1 Enabling SLM Service ........................................................................................................................................ 130
6.2 Changing SLM Port Assignment ...................................................................................................................... 130
6.3 Configuring SLM ................................................................................................................................................ 131
6.4 Configuring HTTPS Support ............................................................................................................................ 132
6.5 Managing SLM Database................................................................................................................................... 134
Chapter 7 Service Procedures ___________________________________________________ 135

7.1 Modifying Application Synchronization......................................................................................................... 135
7.2 Uninstalling Application Synchronization ..................................................................................................... 136
7.3 Setting a Windows User to Administrator ...................................................................................................... 136
7.4 Adding Users on a Windows 10 Computer .................................................................................................... 137
7.5 Configuring the SecurView Keypad ................................................................................................................ 137
7.6 Using Windows File Sharing and Drive Mapping ......................................................................................... 138
7.6.1 Configuring the Application Synchronization Computer for File and Printer Sharing ................ 138
7.7 Troubleshooting Application Synchronization .............................................................................................. 140
7.8 Install/Uninstall Separate Proxy Application ................................................................................................. 143
7.9 Configuring and Troubleshooting Proxy Applications................................................................................. 145
7.9.1 Troubleshooting Proxy Application to Application Synchronization Communication ................ 147
MAN-05940 Revision 002 vii

Table of Contents
List of Tables
Table 1: Third-Party Applications ................................................................................................................................... 9

Table 2: Application Synchronization Icon Shortcuts ................................................................................................. 11
Table 3: Application Configurations for Connected Applications............................................................................ 15
Table 4: Add/Edit Application Pages ............................................................................................................................ 32
Table 5: Partner Interfaces .............................................................................................................................................. 59
Table 6: Hologic SharedFile Partner Communications Page Defaults ..................................................................... 66
Table 7: Amicas Vision Series Communications Page Default Settings ................................................................... 73
Table 8: Dolbey Communications Page Default Settings .......................................................................................... 78
Table 9: Program IDs and Versions ............................................................................................................................... 80
Table 10: GE Centricity RIS-IC Communications Page Settings ............................................................................... 86
Table 11: GE/IDX Imagecast Communications Page Settings ................................................................................... 89
Table 12: PenRad Communications Page Default Settings ...................................................................................... 108
Table 13: PowerScribe or EWS Communications Page Default Settings .............................................................. 112
Table 14: PowerScribe bi-directional Communications Page Default Settings ..................................................... 115
Table 15: syngo Workflow ReadExam Communications Page Default Settings .................................................. 127
MAN-05940 Revision 002 ix

Chapter 1—Introduction
Chapter 1
Introduction
• About This Manual on page 1
• Document Conventions on page 2
• Terms and Definitions on page 3
1.1 About This Manual

This manual provides installation, configuration, and troubleshooting procedures for the
Application Synchronization option.
• Introduction on page 1 describes the purpose of the manual and document
conventions. It also provides a list of terms and definitions.
• Application Synchronization Description on page 5 provides an overview of
Application Synchronization, describes third-party applications, and details the
notification area.
• Installing Application Synchronization on page 17 provides a pre-installation
checklist and includes all the information needed to install and upgrade
Application Synchronization.
• Configuring Application Synchronization on page 21 describes application
configuration procedures and the various supported applications. This chapter
also provides a range of procedures including Application Synchronization
management and application and log management.
• Application Types on page 69 provides configuration instructions for each
application type, including each communications page.
• Configuring Study List Manager (SLM) on page 129 provides instructions on
configuring the Study List Manager.
• Service Procedures on page 135 provides supplemental procedures including
modifying and troubleshooting Application Synchronization. The chapter also
provides information on Windows file sharing, drive mapping, and
installing/uninstalling a separate proxy application. The chapter follows up with
details on configuring and troubleshooting proxy applications.
MAN-05940 Revision 002 Page 1

1.2 Document Conventions

Type text is written in monospaced font exactly as shown.
This manual uses the following conventions to provide technical and safety information
of special interest.
Warning:
An instruction that, if not followed, can result in a hazardous condition.
Caution
An instruction that, if not followed, can result in damage to the system.
Important
An instruction provided to ensure correct results and optimal performance, or to clarify
limitations of the device.
Note
Information provided to clarify a particular step or procedure.
Page 2 MAN-05940 Revision 002

1.3 Terms and Definitions

Application Type A description of the communication protocol and types of
messages exchanged between a connected application and
API Application Programming Interface
AS Application Synchronization
Comm Port Communication port used for serial communications.

Connected Application One instance of an application type that is ready to
send/receive messages.
HIS/RIS Hospital Information System / Radiology Information
System.
DICOM Digital Imaging and Communications in Medicine – an
international standard for the exchange of imaging and
related information.
HTTP Hypertext Transfer Protocol. A communications protocol
used to transfer or convey information on the World Wide
Web.
License Dongle An electronic device that plugs into a computer and serves
as a security measure to enable the use of certain software.
PACS Picture Archiving Communications System. A device used
to store DICOM images long-term.
SDK Software Development Kit
SLM Study List Manager. A database to store study information
to support shared patient list.
Study A specific instance of a procedure consisting of a set of
images and/or series, that has been performed on a specific
patient, and is usually identified in some locally unique
way.
TCP/IP Transmission Control Protocol/Internet Protocol. A
communications protocol for computer networks.
Third-Party Application A third-party application (TPA) is a non-Hologic
application such as RIS, reporting, dictation, or voice
recognition system that is approved by Hologic for use
with Application Synchronization.

Chapter 2—Application Synchronization Description
Chapter 2
Application Synchronization Description
Chapter 2
• Application Synchronization Overview on page 5

• Third-Party Applications on page 8
• Notification Area Icon on page 11
2.1 Application Synchronization Overview

The Hologic Application Synchronization (AS) option allows for run-time user and
patient context synchronization between Hologic products and independent third-party
applications (TPAs). Currently, Hologic products include SecurView®, MultiView™
Multimodality (MM), and MultiView MR Breast workstations. MultiView references in
this document also apply to Aegis 3.2. Third-party applications can be run on a separate
computer or as a thin client on the Hologic workstation.
2.1.1 Installation location guidelines for Hologic products and TPAs:

• SecurView application must be installed on a dedicated computer.
• MultiView MM application can be run on the SecurView workstation or a
separate computer (where non-Hologic TPAs may be installed also).
• Non-Hologic TPAs can be run on the SecurView workstation or a separate
computer.
• Any non-Hologic TPA that has been approved to run on the SecurView
workstation can be run on a MultiView workstation.
• Application Synchronization can be installed on the SecurView workstation,
MultiView workstation, or a separate computer.
AS and TPA on SecurView Workstation

SecurView and AS on Workstation, TPA on a Separate Computer
SecurView with AS and TPA on a Separate Computer

AS and MultiView MM on SecurView Workstation
MultiView and AS on Workstation, TPA on a Separate Computer

MultiView with AS and TPA on a Separate Computer

Application Synchronization has the ability to communicate with each application in its
preferred communication method (such as TCP/IP, shared file, etc.) and knows which
message types each application type supports.
Application Synchronization operates such that synchronization with local applications
(e.g., thin client of third-party application running on Hologic products) or applications
running on a separate computer are handled transparently.
2.2 Third-Party Applications

A third-party application can be viewed on the SecurView workstation with one or two
additional monitors (e.g., Multimodality and/or additional monitor) or a separate
computer. If MultiView MM application is running on a SecurView workstation with
Application Synchronization, it will run on a single, color display. An additional color
display can be configured for display of Patient List, additional TPAs, or the SecurView
Multimodality option.
The configuration used is dependent on the third-party application being installed.
Application Synchronization supports the following third-party applications.
Note
Application Synchronization supports specific versions and releases of the
applications listed below. For more information, see Supported Applications on
page 51.

Table 1: Third-Party Applications

Third-Party Applications Partner Type
3M Radiology Link Software version 2.0.0.15 or higher SharedFile
Agfa TalkStation version 3.2 or higher COM API
Allscripts (Eclipsys) Sunrise Radiology version 5.6 w/SP3 or higher TCP/IP
Amicas Vision Series PACS version 4.0–5.1 XML file
Amicas Vision Series PACS version 5.5 or higher XML file
Avreo InterWorks PACS version 4.6 or higher TCP/IP
Candelis ImageGrid RIS version 2.0.3 or higher SharedFile
Carestream RIS (2010) version 10.x, 11.x TCP/IP
CDI Multifondacs MF-SIS version 4.3.2 or higher TCP/IP
Commit; Screening MIS version 2.2.4 or higher TCP/IP
Compressus VM2 version 2.0.0 or higher TCP/IP
Crescendo CSCIntegration version 3.8.2134.0 or higher SharedFile
Dataworxs AudioWav Mic version 2.00.017 or higher SharedFile
Dolbey FusionDictate version 1.4.28 (a.k.a. version 8) or higher XML file
Dolbey FusionExpert version 5.1.30 or higher XML file
DR Systems Send ID XML Interface version 8.2 or higher SharedFile
Epic Radiant RIS version Spring 2006 or higher COM API
Euromed MedSpeech version 3.0 rev 10 or higher TCP/IP
G2 Speech MediSpeech version 5.0 or higher COM API
GE Centricity PACS version 3.2 COM API
GE Centricity RIS-IC version 10.5 SP25 or higher COM API
GE/IDX Imagecast version 10.3.9 or higher COM API
HSS CRIS version 1.06.12n or higher TCP/IP
Ikonopedia Breast Imaging Suite version 1.0 or higher SharedFile
Infinitt G3 PACS version 3.0.11.4 BN2 or higher TCP/IP
Insight OmniCare version 7.5.2 or higher SharedFile
Intelerad InteleViewer version 4.6.1 or higher SharedFile
(MedQuist/)Lanier VoiceWriter Digital Stations and Serial
MedQuist DocQvoice Workstation version 1.1.5 or higher
M*Modal Fluency for Imaging Reporting version 3.3.0 or higher SharedFile
MagView version 6.3 or higher SharedFile
MagView version 5.3.500 or higher Cust TCP/IP
(KVB) MammaSoft (Germany) version 1.0 or higher Cust Proxy
(KVWL) MaSc RIS (Germany) version 2.0 or higher HTTP
Medicalis Professional version 2.4.2.15 or higher TCP/IP
(Keymind Computing) MedOutlook RIS (Norway) version 1.0.0.1 or Cust TCP/IP
higher
MedQ Dictation 5.0.x or higher SharedFile
MedQuist SpeechQ for Radiology version 1.2 or higher COM API
MRS Mammography Reporting System version 6.6.46 or higher Cust TCP/IP
MultiView version 4.0 or higher and Aegis version 3.2 Cust TCP/IP

Third-Party Applications Partner Type

NBSS British Screening RIS version 3.0.0 or higher Proxy
peerVue qiVue version 6.3.3 or higher and QICS version 7.0.2 or higher TCP/IP
PenRad version 5.1.84 or higher (Note: Use instead of the serial XML file or
interface.) SharedFile
Philips iSite PACS Radiology Client version 3.6 or 4.1, IntelliSpace HTTP plug-in
version 4.4
(Nuance/Dictaphone) PowerScribe version 4.6 or higher (with XML file
PACSBridge) and Nuance Enterprise Workstation (EWS) version 3.0 or
higher (with PACSBridge)
(Nuance/Dictaphone) PowerScribe version 4.7 or higher (with XML file
PACSBridge) supports bi-directional open patient and
Nuance RadWhere version 3.0.18.14 or higher and
PowerScribe 360 version 1.0 or higher
(Agfa) QDoc StudyViewer version 5.5.1 or higher COM API
(Cerner Millenium) RadNet VDI version 2007.18 or higher COM API
(Cerner Millenium) RadNet VDI versions prior to 2007.18 COM API
(Cerner) RadNet VDI version 2004.03 or higher, customized for Orange COM API
Regional Medical Center
ScImage Picom Client version 3.03.059 or higher SharedFile
SecurView DX version 5-0-0 or higher Cust TCP/IP
SecurView Serial Partner (currently, these partners include PenRad, Serial
MRS, MagView)
(Hologic) Selenia® Acquisition Workstation version 3.3 or higher Cust TCP/IP
SERGAS SIDI (Spain) version 2.10 or higher TCP/IP
SESCAM Dulcingest RIS version 7.8.3.1 or higher TCP/IP
Softek Illuminate InSight version 2.12 or higher SharedFile
Spantel Audio Recorder version 2.0 or higher COM API
(Siemens) syngo Workflow (Europe) browser version VB30 or higher Proxy
(Siemens) syngo Workflow Portal Radiologist version 30 or higher HTTP
(Siemens) syngo Workflow (formerly Novius RIS) ReadExam version XML file
27.1 or higher
WinScribe Internet Author version 3.8 or higher SharedFile
For more information regarding the configuration of specific application types, see
Application Types on page 69.

2.3 Notification Area Icon

Application Synchronization will start automatically when the Windows operating
system starts up. There will be an Application Synchronization icon displayed in

the notification area when Application Synchronization is running.
You can move the pointer over the icon to confirm the application is running. The
message will display ‘Hologic Application Synchronization’ with ‘Status: Started’ or
‘Status: Stopped’.
You can also right-click the icon to view the Application Synchronization shortcut menu
as shown in the table below.
Table 2: Application Synchronization Icon Shortcuts
About Displays the AS version and copyright information.
Connected Displays the list of connected applications within the AS
Applications Configuration Interface.
Configure… Displays the AS Configuration Interface main window.
Log Viewer… Displays the AS Log Viewer.
Start Starts Application Synchronization messaging.
Stop Stops Application Synchronization messaging.
Exit Exits Application Synchronization.

Chapter 3—Installing Application Synchronization
Chapter 3
Installing Application Synchronization
Chapter 3
• Required Tools and Materials on page 13

• Preinstallation Checklist on page 13
• Recording Application Configurations on page 15
• Backing Up and Configuring Licenses on SecurView on page 15
• Checking the System for Active Network Connections on page 16
• Upgrading Application Synchronization on page 16
• Installing Application Synchronization on page 17
• Configuring Application Synchronization on page 21
• Completing the Installation on page 20
3.1 Required Tools and Materials

You will need this manual, the Application Synchronization Installation DVD, and the
Hologic passwords.
For passwords, log into the SFTP server (https://drftp.hologic.com) and navigate to the
/shared software/Password folder, which contains the password file. Dealers can access
the password file by logging into dicom@hologic on the https://drftp.hologic.com SFTP
server. For further assistance, contact Hologic Technical Support.
3.2 Pre-installation Checklist

Before installation, discuss the following information with personnel at the customer site.
• Application Synchronization requires a license in order to work with
non-Hologic third-party applications. (See Licensing on page 24.)
• Application Synchronization 4.3 does not apply to Selenia AWS synchronization
with SecurView RT or TechMate. For those products, continue to use Application
Synchronization version 2.1.
• This document includes instructions for installing Application Synchronization
on a system where it was not installed previously. This document also describes
how to upgrade an existing version of Application Synchronization. (See
Upgrading Application Synchronization on page 16.)
• Application Synchronization versions earlier than 2.1 are not supported with
SecurView 7.2 or later.
• Application Synchronization 4.2 and earlier are compatible with SecurView 10.3
and earlier on Windows 7 or Windows Server 2008
• Application Synchronization 4.3 is required when installed on SecurView 10.3 or
later on Windows 10 or Windows Server 2016.

• Application Synchronization 4.3 is compatible with MultiView 4.1 or later.

• Application Synchronization 4.3 is compatible with Windows 10 operating
systems.
• Record all configurations for connected applications before performing an
Application Synchronization upgrade or modification. Connected application
settings are not migrated to the new install during an upgrade.
For a table to record and review these settings see Recording Application
Configurations on page 15.
• Work with the site to determine the third-party applications that must be
configured. Consult the appropriate sections for each application type to see if
additional information is required during installation. You may need to
coordinate with a technical support representative from the third-party vendor
to complete the configuration.
• Determine if any third-party applications will be run on a separate computer,
and if Application Synchronization must be installed on the same computer as
the third-party application due to the API protocol used for that application type.
For a list of these third-party applications, see table Partner Interfaces on page 59.
• If installing Application Synchronization software with an additional monitor
option, you must install the additional monitor first.
• If installing a new serial interface with a SecurView Serial Partner, you will need
a 9-pin female/female null-modem serial cable. (Part Number CBL-00588)
• If installing a new serial interface with a MedQuist/Lanier VoiceWriter Digital
Station, you will need a specific serial cable. Check with the customer or
MedQuist/Lanier technical support to obtain the correct serial cable.
• Installing the Application Synchronization software requires an active network
card and an assigned TCP/IP address. Do not use ‘127.0.0.1’ or ‘localhost’ as the
IP address.
• Installing and configuring Application Synchronization software will take a Field
Engineer up to 1½ hours depending on the applications being installed or
configured.
• Ensure that you have the latest Application Synchronization Release Notes
available for information on known configuration or installation issues.
• Ensure that the applicable and preferred options for ‘Synchronize with External
Application’ within SecurView are selected for each SecurView user. See the
SecurView DX/RT Workstation User Guide for more information.
• Ensure that you have the SecurView DX/RT Workstation Installation and Service
Manual and MultiView Multimodality User Guide readily available for reference.

3.3 Recording Application Configurations

Prior to beginning the installation, record the configuration information for all connected
applications, to use during configuration.
Caution
You must record all configurations for the connected applications before
performing an Application Synchronization upgrade. Connected applications
settings are not migrated to the new install during an upgrade
For each application, refer to the specific application information in this installation
manual, and verify the application configuration information you will need to install this
software. For instance, if you are configuring a Hologic SharedFile Partner, you will need
the following information: Directory, Inbound File Name, Outbound File Name,
Encryption Type, and Encryption Key.
Table 3: Application Configurations for Connected Applications
Application Configuration
3.4 Backing Up and Configuring Licenses on SecurView

Refer to the SecurView DX/RT Workstation Installation and Service Manual for instructions
on backing up the SecurView settings (standalone) and for configuring licenses on
SecurView (Client and Standalone).
Label the backup disk as ‘SecurView x.x.x Backup, Pre App Sync Install’ where x.x.x
refers to the currently installed SecurView software version. Record the station name.
Note
Performing a SecurView backup is required only if SecurView DX is one of the
connected applications and Application Synchronization is installed on a
SecurView computer.

3.5 Checking the System for Active Network Connections

1. Log into Windows as a user with administrator rights on the computer where
Application Synchronization is to be installed.
2. Press Windows + [R].
3. In the Run dialog, type cmd and press [Enter].
4. In the command window, type the following information to determine your
computer’s basic TCP/IP settings: ipconfig
A command window appears that displays the IP address, subnet mask, and default
gateway.
5. Check the IP address.
• Ensure that the Ethernet adapter has an assigned IP address. Close the command
window.
• If the system does not have an assigned IP address you will see a ‘Media
disconnected’ message. Ensure this system has a valid TCP/IP address, assigned
by the PACS administrator, before going any further.
6. Once you confirm a TCP/IP address, close the command window.
3.6 Upgrading Application Synchronization

Upgrading Application Synchronization requires uninstalling the existing version
followed by installing the new version. The instructions in this section describe how to
uninstall Application Synchronization. For instructions on installing Application
Synchronization, see Installing Application Synchronization on page 17.
The installer’s Remove mode can be used to uninstall Application Synchronization and
all its components.
Note
Make sure you have recorded all connected application configurations before
uninstalling Application Synchronization. See Recording Application Configurations
on page 15.
If error message boxes are displayed during uninstall of the Application Synchronization
software, please take note of the errors and report them to Hologic Technical Support.
1. Log into Windows as Administrator.
2. On Windows 10, select Start > Settings > System > Apps & features.
3. Select Application Synchronization from the list and select Uninstall. After you
confirm, the InstallShield window appears.
4. Select Remove to remove all installed features. Follow the prompts to remove the
Application Synchronization software.

Note
If a dialog appears that states, ‘XXXXXX is being uninstalled. It is a proxy adapter
and requires the uninstall of a separate package’, select OK. Proxy adapters have
a separate installation package that will need to be uninstalled after completing
the Application Synchronization uninstall. For instructions, see Install/Uninstall
Separate Proxy Application on page 143.
Note
If Philips iSite PACS is one of the connected applications, the Philips iSite plug-in
must be uninstalled. To uninstall Philips iSite plug-in, see section Philips iSite
PACS on page 109.
5. Select Yes, I want to restart my computer now. Select Finish. The system will restart.
3.7 Installing Application Synchronization
Note
If you are installing Application Synchronization on a non-Hologic provided
computer, ensure that at least 1GB of disk space is available on the C: drive before
performing the installation.
Note
Study List Manager(SLM) is automatically installed during the installation of
Application Synchronization. See Configuring Study List Manager (SLM) on page
129 for guidelines on SLM configuration.
Note
If Application Synchronization 4.3 is installed on a non-Hologic Windows 10
computer, it is necessary to set permissions for Windows user accounts other
than Administrator or SCR that may be used to configure or run Application
Synchronization. See Adding Users on a Windows 10 Computer on page 137 for
instructions.


2. Load the Application Synchronization Installation DVD. First a command window,
and then the Application Synchronization InstallShield Wizard window appears.
Figure 1: The Command Window
Note
If the InstallShield Wizard does not automatically run, open Windows File
Explorer. Navigate to the disk drive, double-click setup.bat, then follow the
on-screen instructions.
3. In the Application Synchronization InstallShield Wizard window, select Next.

4. Follow the prompts to install Application Synchronization.
5. If the Application Synchronization software is being installed on a non-SecurView
system, a Choose Destination Location window will appear. Keep the default
installation location or select Change to select a different path.
6. Select Next to continue. The Installation Components window appears.

7. In the Installation Components window, select the installation components that are
required for the site. When you are satisfied with the settings, select Next. The Start
Copying Files window appears.
Note
If a connected application with multiple versions available for install is selected, a
‘Select Version’ dialog will appear. Select the correct version to be installed and
select Next. Perform this instruction step for all dialogs of this type that appear
(e.g., Amicas Vision Series, PowerScribe/EWS, RadNet VDI, Dolbey).
Note
If you select Cancel in the Installation Components window to quit the
installation process, you may see an error message: "ABORTING: Failed to install
DLL file." Select OK to close this error message. You can restart the installation
process after waiting for about a minute.
8. In the Start Copying Files window, confirm the components being installed. When
you are satisfied with the settings, select Next.
The Setup Status window appears and installs the software.
Note
If a dialog appears stating ‘XXXX has been selected for installation. It is a proxy
adapter and requires the installation of a separate install package. Please
install the proxy adapter package from ‘C:\AppSyncInstaller\HologicASProxy\
XXXXInstallShield’ after completing this Application Synchronization
installation.’ select OK. Proxy adapters have a separate installation package that
will need to be installed after completing the Application Synchronization
installation. See Install/Uninstall Separate Proxy Application on page 143 for
instructions.
Note
If Philips iSite PACS is one of the connected applications, the Philips iSite plug-in
must be installed. To install Philips iSite plug-in, see section Philips iSite PACS on
page 109.
9. When the installation is complete the InstallShield Wizard Complete window

appears.
10. Select the Yes, I want to restart my computer now option and then select Finish.
Note
Hologic.SecurView.AppSync.Synchronizer.exe is added under Allowed
programs and features in the Windows Allow Apps to Communicate through
Windows Firewall window.

3.8 Configuring Application Synchronization Software

2. If Application Synchronization does not start automatically, navigate to the folder
where Application Synchronization is installed (for SecurView systems
E:/HologicAppSync\Synchronizer), then double-click
Hologic.SecurView.AppSync.Synchronizer to start Application Synchronization.
3. Right-click the Application Synchronization icon in the notification area and

then select Configure. The Hologic Application Synchronization Configuration
Interface main window appears (See Configuration Interface Overview on page 21).
4. Add the required connected applications using the online Help and instructions in
Configuring Application Synchronization on page 21 and Application Types on page 69.
Upon completing the configuration, return here to complete the installation.
5. Access the connected applications and make sure that messages are being sent
correctly (e.g., check that when the displayed patient is changed in one application,
the displayed patient changes on the other connected applications, according to
configurations). Use the Connected Application Tester described in Application Tester
on page 30 if matching user accounts and/or patients and studies are not available on
SecurView, MultiView and the other connected application(s).
6. If the connected applications are capable of using Study List Manager (SLM) to share
patient lists (e.g., SecurView and MultiView), follow the instructions in Configuring
Study List Manager (SLM) on page 129.
3.9 Completing the Installation

Service Engineers who have access to the Hologic intranet (https://my.hologic.com)
should complete this online report:
1. From MyHologic, select Divisions > Breast & Skeletal Health Solutions > BSH
Customer Experience and Service > Imaging Field Service Team Site.
2. On the Imaging Field Service web page, locate and select the Installation Report
button.
3. Fill out all required fields and select Submit.
Authorized dealers who have access to the Hologic extranet (The WIRE) should complete
this online report:
1. Navigate to https://thewire.hologic.com/installation-form to access the installation
report.
2. Fill out all required fields and select Submit.

Chapter 4—Configuring Application Synchronization
Chapter 4
Configuring Application Synchronization
Chapter 4
• Configuration Interface Overview on page 21

• Application Sync Management on page 22
• Application Management on page 32
• Log Management on page 50
• Supported Applications on page 51
4.1 Configuration Interface Overview

The Hologic Application Synchronization Configuration Interface shows a menu of
management options on the left side. Each page contains fields or options used to configure
the application.
Note
Application Synchronization messaging must be stopped to make configuration
changes.

4.2 Application Sync Management

The Application Sync Management menu lets you view and enter Application
Synchronization networking settings, configure licensing, import and export configuration
files, and test each connected application.
• Application Sync Config on page 22
• Message Success Criteria on page 23
• Licensing on page 24
• Import Config on page 27
• Export Config on page 29
• Application Tester on page 30
4.2.1 Application Sync Config

The Application Sync Config page lets you enter networking information for Application
Synchronization. You can also view the hosting computer’s TCP/IP addresses. Enter the IP
address for the hosting computer and the Hologic Protocol Port number, which is the port on
which Application Synchronization listens for messages and responses. By default, this port
is 5100.
Note
The SecurView application uses ports 4700 and 65000-65500, so do not use any of
those values as the listening port for Application Synchronization on a SecurView
Workstation. The default port for the MultiView application is 5102.

To enter the Application Synchronization Listener Configuration:

1. Select Application Sync Config. The Application Synchronization Config page appears.
2. Enter (or confirm) the IP Address and Hologic Protocol Port.

3. Select (Save) to validate the IP address and Hologic protocol port number.
4.2.2 Message Success Criteria

The Message Success Criteria page sets the success criteria for each message type. When
more than two connected applications are configured, Application Synchronization collects
the responses from the receiving applications and returns one response to the message
originator.
The Message Success Criteria page has drop-down lists that let you select an ‘All Successful’
or ‘Any Successful’ for the following message types: Login, Logout, OpenPatient, and
UpdatePatientState.
• Any Successful. If at least one successful response is received, then Application
Synchronization will return a Success back to the message originator.
• All Successful. All applications receiving the message must return successful
responses for Application Synchronization to return a Success back to the message
originator.

To set the Message Success Criteria:

1. Select Message Success Criteria. The Success Criteria page appears.
2. Select the correct success criteria for each message type.

3. Select (Save) to commit the changes made to the settings.
4.2.3 Licensing
The Licensing page allows you to obtain the request code and install the license file for
Application Synchronization. You do not need a license if only Hologic products are being
configured (for example, SecurView and/or MultiView).
Note
Application Synchronization can be used with non-Hologic TPAs without a
license for a 7-day trial period. Be sure to obtain a license within 7 days after
installation.

To obtain and install a license key for non-Hologic TPAs:

1. Select Licensing. The Licensing page appears.
2. In the ‘This Computer’s Fingerprint’ section, select Copy to Clipboard and send the
computer’s fingerprint in an email to 3D@hologic.com. The email should have the
following information:
• Subject line titled App Sync License.
• The site name.
• The serial number on the Hologic License Certificate. The Hologic License Certificate
is provided to the customer at the time of purchase.
3. Access your email, retrieve the license.zip file, and save it to a desired location on the
computer.
4. Unzip the license.zip file and place the license key file on the computer at a desired
location.

5. Select Install License in the Licensing page, navigate to the license key file, and open it.
The license status changes to Any TPA.
If only Hologic connected applications are configured:

If only Hologic connected applications are configured and you access the Licensing page, you
will see the following screen:

4.2.4 Import Config

The Import Configuration page lets you import a configuration file (.hlx) from the same
Application Synchronization version and overwrite the existing configuration.
To import a configuration file:
1. Select Import Config. The Import Configuration page appears.

2. Select Browse. A Select a Devices.hlx file dialog appears.
3. In the ‘Select a Devices.hlx file’ dialog, navigate to the location of the configuration file to
be imported.
C:\ProgramData\Hologic\AppSync\Configuration
4. Select Open. The Import Configuration page displays the full path of the file to be
imported.
5. Select (Commit Import). A Save Successful message displays.
Note
Application Synchronization automatically creates a backup of the existing
configuration file before the imported file overwrites it.

4.2.5 Export Config

The Export Config page lets you export and save a configuration file (.hlx).
To export a configuration file:
1. Select Export Config. The Export Config page appears and displays a list of connected
applications with the following information: Application ID, Alias, Application Type,
Communication Type, and Description.

2. Select (Export Configuration). The ‘Save Devices.hlx File’ dialog appears.
3. Navigate to a location to save the file and select Save. All connected application
information is exported in the saved configuration file.
4.2.6 Application Tester

The Connected Application Tester page provides the capability to test sending and receiving
message transactions between Application Synchronization and one selected connected
application.

To test sending and receiving messages with a connected application:

1. Select Application Tester. The Connected Application Tester page appears. The page
displays a drop-down list containing connected applications.
2. In the Connected Applications drop-down list, select an application.

3. Select Start Tester. The Connected Application Tester will automatically enable or
disable fields in the Send Message group box according to the capabilities of the selected
application.
Note
The Connected Application Tester can receive request messages from the selected
connected application, however it does not have the ability to send
corresponding response messages.
Note
To access any other page of the Application Synchronization Configuration
Interface, select Stop Tester.
4. You can review the messages that are sent and received by the Connected Application
Tester in the Tester Log.
Note
To assist you in debugging configuration issues, unencrypted user name and
password information are shown in the Tester Log.

4.3 Application Management

The Application Management menu provides you with a way to manage connected
applications. You can configure new connected applications, edit and delete existing
connected applications, and view the list of connected applications.
• Add /Edit Application on page 32
• Type on page 33
• Comm on page 34
• XML Mapping on page 34
• Message Type on page 40
• OpenPatient Data on page 41
• OpenPatient Filters on page 44
• Misc on page 46
• Finish on page 47
• Application List on page 48
4.3.1 Add /Edit Application

The Add Application interface provides you with a way to step through a series of pages to
add and configure a new connected application.
To navigate through the pages use the (Next), (Finish), (Previous), and
(Start) buttons, or select a tab to navigate to a specific page.
You can also edit connected applications using these pages.
Table 4: Add/Edit Application Pages
Type Select the application type and assign a unique Alias.
Comm Configure the communication properties of the selected application
type (e.g., serial, TCP/IP, shared file).
XML Mapping For the Hologic SharedFile Partner application type, configure
mapping of XML fields between a TPA XML format and Hologic’s
XML format.
Message Type Configure the Accepted Messages and Sent Messages.
OpenPatient Data Add and/or remove specific leading and/or trailing characters in the
Patient ID or Accession Number field of the OpenPatient message.
OpenPatient Filters Configure five study filtering parameters for the OpenPatient
message, to constrain the study information passed on to the
connected application, whether or not to pass on a Clear message,
and which Match Keys to pass on.
Misc Configure the Response Timeout (in seconds) and Request Delay (in
seconds), if applicable, for the connected application.
Finish Confirm the connected application settings, and complete the
connected application configuration.

4.3.2 Type
The Type page provides a field to enter a new Application Alias. The alias must be unique
(not already used by another connected application). The page also provides a list of
application types from which to select. The page will display a description after you select an
application type from the drop-down list.
Note
The next few examples regarding Add Application will feature the PowerScribe
bi-directional application type.
To add an approved application type:

1. Select Add Application. The Type page appears.
2. In the Application Type drop-down list, select the appropriate application.

Note
Some application types are limited to a single instance, and the Wizard will not
allow a second instance to be created. For more information, see Application Types
on page 69.
3. In the Application Alias field, enter the application alias and select (Next) or any of
the tabs.
Note
If the alias in the field is already in use, an error message will appear stating ‘This
name already exists. Please use another one’.
If all the validations are successful, the next or selected page will be displayed.

4.3.3 Comm
The Comm page allows you to configure the application communication properties (e.g.,
serial, TCP/IP, shared file, etc.) based on the application type communication method. The
Comm page content varies per application type. See Application Types on page 69 for the
Comm page definition for each supported application type.
4.3.4 XML Mapping

The XML Mapping page contains settings that allow you to configure the mapping of XML
fields between a TPA XML file format and Hologic’s XML file format. This configuration
applies only to the Hologic SharedFile Partner application type.
The XML Mapping option is available only for OpenPatient and UpdatePatientState
Messages. Both OpenPatient and UpdatePatientState can be configured for inbound
messages. However, outbound messages are limited to either OpenPatient or
UpdatePatientState, not both.
XML Mapping does not apply to Login and Logout messages.
By default, the Hologic SharedFile Partner application type uses the Hologic XML file format
defined in the Hologic SharedFile Partner Guide. If a TPA has its own XML file format and is
not able to conform to the Hologic XML file format, the XML Mapping page may be used to
configure a mapping between the two formats.
To configure XML mapping (same Inbound and Outbound):
If the TPA uses the same XML file format for reading (receiving a message from Application
Synchronization) and writing XML files (sending a message to Application Synchronization),
or only one direction (inbound or outbound) is being used, one mapping (template) can be
configured.

1. In the XML Mapping window, select the ‘Use XML Template’ check box.
2. Enter the TPA XML file format in the text box. There are three ways to do this:
• If a mapping (template) was saved previously for the connected application, it will
be read from Devices.hlx and loaded to the text box automatically, or
• Select Import and navigate to the sample .xml file (Import is the preferred method
for initial loading), or
• Manually type or copy and paste the TPA’s XML file format.

3. Double-click the value within the XML tag. The <Select One> drop-down menu appears.
Important
If you select anywhere outside the value, an error occurs and you must re-import
the XML file.
4. Select a mapping for each value.

• No Match. Use this option when there is no matching tag in the Hologic XML, and
the TPA does not require a value in XML files that it reads. The value will be
replaced with an empty string.
• Pass Through. Use this option when there is no matching tag in the Hologic XML,
and the TPA requires the tag to be present in XML files that it reads, with the value
included in the template.
• Patient ID
• Accession Number
• Study Instance UID
• Study ID
• Status. Use this option to identify the tag used to indicate an inbound
UpdatePatientState (or OpenPatient) message.

5. UpdatePatientState Status Values. By default the values used in the mapped Status tag
to indicate an inbound UpdatePatientState message are Complete, Dictated or Finished
(case insensitive matching). If the TPA uses different values in the mapped Status tag to
indicate UpdatePatientState, add to or replace the default values as needed, comma
delimited.
6. Use Status Values to Identify OpenPatient. Select this check box only if the TPA also
uses values in the mapped Status tag to identify OpenPatient messages. Do not select this
check box if the TPA does not include the mapped Status tag in OpenPatient messages.
7. OpenPatient Status Values. If Use Status Values to Identify OpenPatient is checked, add
comma delimited values that the TPA uses in the mapped Status tag to indicate an
inbound OpenPatient message.
8. Ignore Other Status Values. Select this check box if the TPA may send other values in
the mapped Status tag (such as Paused, Aborted, Deleted) that should not be mapped to
UpdatePatientState (or OpenPatient if Use Status Values to Select OpenPatient is
checked).
9. Select Check. The updated XML template is checked for conformity. If there is a problem
with the XML syntax, an error message alerts you to what needs to be addressed.

To configure XML mapping (different Inbound and Outbound):

If the TPA uses a different XML file format for writing XML files (inbound to Application
Synchronization) versus reading XML files (outbound from Application Synchronization), if
UpdatePatientState is being used in both the inbound and outbound directions, or if
OpenPatient is being used outbound with UpdatePatientState inbound, follow these
instructions.
1. In the XML Mapping window, select the ‘Use XML Template’ check box.
2. Select the ‘Different Inbound and Outbound XML Template’ check box. The following
window appears:
3. Enter each TPA XML file format in the appropriate text box. There are three ways to do
this:
• If mappings (templates) were saved previously for the connected application, they
will be read from Devices.hlx and loaded to the text boxes automatically, or
• Select Import and navigate to the sample .xml file (Import is the preferred method
for initial loading), or
• Manually type or copy and paste the TPA’s XML file format.

4. Double-click the value within the XML tag. The <Select One> drop-down menu appears.
Important
If you select anywhere outside the value, an error occurs and you must re-import
the XML file.
5. Select a mapping for each value in the Inbound and Outbound templates.
• No Match. Use this option when there is no matching tag in the Hologic XML, and
the TPA does not require a value in XML files that it reads. The value will be
replaced with an empty string.
• Pass Through. Use this option when there is no matching tag in the Hologix XML,
and the TPA requires the tag to be present in XML files that it reads, with the value
included in the template. For outbound UpdatePatientState, the tag that identifies the
message as UpdatePatientState must be mapped as Pass Through.
• Status. Use this option to identify the tag used to indicate an inbound
UpdatePatientState (or OpenPatient) message.
The additional mapping options for the Inbound template are Patient ID, Accession
Number, Study Instance UID, Study ID.
The additional mapping options for the Outbound template are based on the
OpenPatient Fields selected on the Comm page.

6. UpdatePatientState Status Values (Inbound template only). By default the values used
in the mapped Status tag to indicate an inbound UpdatePatientState message are
Complete, Dictated or Finished (case insensitive matching). If the TPA uses different
values in the mapped Status tag to indicate UpdatePatientState, add to or replace the
default values as needed, comma delimited.
7. Use Status Values to Identify OpenPatient (Inbound template only). Select this check
box only if the TPA also uses values in the mapped Status tag to identify OpenPatient
messages. Do not select this check box if the TPA does not include the mapped Status tag
in OpenPatient messages.
8. OpenPatient Status Values (Inbound template only). If Use Status Values to Identify
OpenPatient is checked, add comma delimited values that the TPA uses in the mapped
Status tag to indicate an inbound OpenPatient message.
9. Ignore Other Status Values (Inbound template only). Select this check box if the TPA
may send other values in the mapped Status tag (such as Paused, Aborted, Deleted) that
should not be mapped to UpdatePatientState (or OpenPatient if Use Status Values to
Select OpenPatient is checked).
10. Select Check for the Inbound template, then for the Outbound template. Each updated
XML template is checked for conformity. If there is a problem with the XML syntax, an
error message alerts you to what needs to be addressed.
4.3.5 Message Type

The Message Type page allows you to select the accepted and sent messages to be used with
the connected application.
Note
The next few examples will feature the PowerScribe bi-directional application
type.
The Message Type page contains two groups: Accepted Messages and Sent Messages.
• Accepted Messages. The messages accepted by the application.
• Sent Messages. The messages that the application can send.
Depending on the selected application type, the check boxes available in each group will vary
(see table Partner Interfaces on page 59).
Within the Accepted Messages group, select one of the two OpenPatient message options
that are enabled only when OpenPatient is checked:
• Auto and Manual (default): Application Synchronization will send all received
OpenPatient messages to this connected application, or
• Manual Only: Application Synchronization will send only OpenPatient messages
received from SecurView that were triggered using a manual method to this connected
application.

To configure the application type message definitions:
1. Select (Next) from the previous page or select the Message Type tab. The Message
Type page appears.
2. In the Message Definitions area, verify the messages accepted by or that can be sent by
the selected application type. At least one check box must be checked in order to proceed
to the next or another page. After confirming that the messages used in this instance are
checked, select (Next) or any of the tabs.

4.3.6 OpenPatient Data
Note
When a Hologic product and a non-Hologic TPA are the connected applications,
configure this page as needed for the non-Hologic connected application. This
page is not available for the SecurView application type. However, this page is
available for the MultiView application type, to be used only if SecurView, and
MultiView are the connected applications and there is a difference in Patient ID
or Accession Number values between them.
The OpenPatient Data page contains the settings that allow you to modify the value of the
Patient ID or the Accession Number field in the OpenPatient messages passed to and from
the connected application being configured. Make changes on this page only if the values do
not match. For instance, the values of this connected application may always have the same
specific leading or trailing characters that another connected application does not (e.g.,
B12345 vs. 12345).
Note
If the leading and/or trailing characters differ in value or length from one patient
to another (e.g. sometimes three leading zeros, sometimes four), this
configuration option will not resolve the issue.

To configure OpenPatient Data:
1. Select (Next) from the Message Type page or select the OpenPatient Data tab. The
OpenPatient Data page appears.
2. In the Data Field drop-down list, select Accession Number or Patient ID. Enter leading
characters to be removed or added. Enter trailing characters to be removed or added.
3. In the Sample CA Value field, enter a sample value known to the connected application
to check your work. The corresponding value known to the SecurView or MultiView
application should be displayed.

4.3.7 OpenPatient Filters

If the Accepted Messages OpenPatient check box is selected in the Message Type page, the
OpenPatient Filters tab will be present. The OpenPatient Filters page has three configurable
settings.
OpenPatient Study Filter: contains the configurable study filtering parameters for the
OpenPatient message, and will initially display the default settings for the selected
application. If an option is not configurable for the selected application type, the option will
be read-only.
A site may choose to change the defaults to alter how study information is passed in the
OpenPatient messages sent to the connected application. These settings tell Application
Synchronization what the connected application will accept. Application Synchronization
will filter the study content of the OpenPatient messages appropriately to comply with the
settings. For example, if the site wants their dictation system to receive only messages for
Mammography (MG) Studies, and ignore other modalities (such as Ultrasound or MRI),
select Accept Only MG Studies. If a message from the SecurView contains studies for
multiple modalities, Application Synchronization will filter the message and send only the
MG study information to the dictation system.
If the site’s preferences are unknown at the time of installation, leave the default settings, and
confirm with the customer later.
OpenPatient Clear Message: The only application types that have ‘Accept Clear Request’
checked by default are SecurView and MultiView. Do not check it for a specific application
type unless the connected application can accept an OpenPatient message where the patient
and/or study fields have the value ‘CLEAR’, which indicates to close the currently open
patient. If the connected application does not accept this type of OpenPatient message,
checking the setting may cause unexpected behavior in the connected application.
OpenPatient Match Keys: The fields that are checked by default are the only fields that the
connected application uses for matching in received OpenPatient messages. Do not check any
match key settings that are unchecked by default. If the connected application uses multiple
fields in a received OpenPatient message to determine whether a patient/study match is
found and a different value in one field results in no match, this setting can be used to
eliminate the field that is known to be different. For example, it may be necessary to uncheck
Patient ID for the SecurView application type in a TPA-driven workflow if Accession
Number values match between the connected applications but Patient ID values do not (e.g.,
local vs. enterprise MRN).

To configure OpenPatient Filters:
1. Select (Next) from the OpenPatient Data page or select the OpenPatient Filters tab.
The OpenPatient Filters page appears.
2. Review the ‘Configure OpenPatient Study Filter’ default settings and make changes if
necessary. For example, if the connected application expects only one study, uncheck
Accept More Than One Study. To prevent Read or Old studies from being sent to the
connected application, select Accept Only Unread Studies. If only Unread studies are
being sent, in If No Unread Studies Are Available select whether any studies should be
sent if only Read or Old studies are available (None, One Read, All Read).
3. Review the ‘Configure OpenPatient Clear Message’ setting. The default setting should be
sufficient.
4. Review the ‘Configure OpenPatient Match Keys’ settings. The default settings should be
sufficient unless there is a conflict with one of the default match keys.
Note
If more than one connected application is sending OpenPatient messages to this
connected application, before unchecking one of the default match keys, make
sure that all sending applications provide at least one alternate match key that is
still checked.

4.3.8 Misc
If any of the Accepted Messages check boxes are checked on the Message Type page, the
Misc (miscellaneous) tab will be present. The Misc page allows you to configure an
application response timeout and request delay.
If the application being configured cannot respond to a message then the Response Timeout
(Sec) field will be read-only. If the application being configured does respond, enter the
number of seconds to wait for a response before reporting failure. The default is 5 seconds.
The Request Delay (Sec) drop-down list allows you to delay distributing a message received
from the application being configured by up to 10 seconds. The default is Disabled, which
means all messages are sent immediately.
To configure a response timeout and request a delay:
1. Select (Next) from the previous page or select the Misc tab. The Misc page appears.
2. In the Response Timeout (Sec) field, enter a response timeout value.

3. In the Request Delay (Sec) drop-down list, select a delay time or disable the delay
feature.

4.3.9 Finish
The Finish page displays a confirmation prompt to confirm the settings for the connected
application. Confirm the information, and then select (Save). You must be on the Finish
page to save changes and return to the Application List. You may select (Cancel) and
return to the Application List from any page. You can also select (Previous) to edit any of
the previous settings or select any tab.

4.3.10 Application List

The Connected Application List page displays a list of connected applications. This list
contains the following information: Application ID, Alias, Application Type, Communication
Type, and Description.
When you select Application List, a screen similar to the following appears.
You can use the Application List page to:

View Connected Application Summary - View a configuration summary
for each application.
Edit Connected Application – Edit a connected application.
Delete Connected Application – Delete a connected application.

To view a connected application summary:
1. Select a connected application in the Connected Application List and then select
(View Connected Application Summary). A connected application configuration
summary appears.
2. Select (next arrow) to move through the summary. The summary displays the
following information for the connected application: Application Definition,
Communications Definition, Message Definitions, OpenPatient Data, OpenPatient Filters,
and Misc.
To edit a connected application:
(Edit Connected Application). The Edit Application Type page appears.

2. You can now edit the connected application by following the instructions for Add
Application starting in Add /Edit Application on page 32.
To delete a connected application:
(Delete Connected Application). A Deleting Connect Application confirmation dialog
appears.
2. Select Yes to continue and delete the application or select No to cancel the delete and
return to the Connected Application List.

4.4 Log Management

The View Log File page provides you with a way to view the Application Synchronization
log file. The page provides the following information for each log file entry: Date/Time,
Level, Code, and Message.
To view log details:

1. You can view a tool tip containing the entire text of a log entry that is longer than one
line by pointing the cursor at that entry.
2. To view the log details page, select (Details). The log details page appears and you
can view additional details for the log.
3. You can search for specific text, filter the log by log level or date range, clear the log
directory, wrap text so that the each complete entry is displayed on multiple lines if it is
longer than one line, or enable tailing so that the Log Viewer page is updated
dynamically as new entries are added.

4.5 Supported Applications

Hologic Application Synchronization has the ability to communicate with each application in
the application’s preferred communication method.
Hologic partners are applications that have implemented one of the three available Hologic
partner interfaces (Command Line Proxy, SharedFile, or TCP/IP), and use the corresponding
general application type.
Each non-Hologic partner interface has its own specific application type, with a default
configuration that matches the implementation.
Hologic Proxy Partner
A Hologic Proxy Partner is one that uses the Hologic Command Line Proxy interface.
Hologic SharedFile Partner
A Hologic SharedFile Partner is one that uses the Hologic XML SharedFile interface.
Hologic TCP/IP Partner
A Hologic TCP/IP Partner is one that has implemented the Hologic TCP/IP AS Adapter
interface.

• 3M Radiology Link Software (Hologic SharedFile Partner)

– 3M Radiology Link Software version 2.0.0.15 or higher for VoiceScript Recorder and
ChartScriptMD Document Builder Platform 7, feature pack 2 with 3rd service pack or
higher
– 3M Radiology Link Software, VoiceScript, and ChartScriptMD can run only on a
separate computer.
• Agfa TalkStation (Custom: COM API)
– Agfa TalkStation version 3.2 or higher
– TalkStation can be run on the SecurView workstation or a separate computer.
• Allscripts (Eclipsys) Sunrise Radiology (Hologic TCP/IP Partner)
– Sunrise Radiology version 5.6 w/SP3 or higher
– Sunrise Radiology can be run on the SecurView workstation or a separate computer.
• Amicas Vision Series v4.0-5.1 (Custom: XML file)
– Amicas Vision Series PACS version 4.0 - 5.1
– Vision Series can run only on a separate computer.
• Amicas Vision Series v5.5 (Custom: XMLfile)
– Amicas Vision Series PACS version 5.5 or higher
– Vision Series can run only on a separate computer.
• Avreo InterWorks PACS (Hologic TCP/IP Partner)
– Avreo InterWorks PACS version 4.6 or higher
– Avreo InterWorks can run only on a separate computer.
• Candelis ImageGrid RIS (Hologic SharedFile Partner)
– Candelis ImageGrid RIS version 2.0.3 or higher
– ImageGrid RIS can run only on a separate computer.
• Carestream RIS (Hologic TCP/IP Partner)
– Carestream RIS (2010) version 10.x, 11.x
– Carestream RIS can be run on the SecurView workstation or a separate computer.
• CDI Multifondacs (Hologic TCP/IP Partner)
– CDI Multifondacs MF-SIS version 4.3.2 or higher
– CDI Multifondacs can be run on the SecurView workstation or a separate computer.
• Commit; Screening MIS (Hologic TCP/IP Partner)
– Commit; Screening MIS version 2.2.4 or higher
– Commit; Screening MIS can be run on the SecurView workstation or a separate
computer.
• Compressus VM2 (Hologic TCP/IP Partner)
– Compressus VM2 version 2.0.0 or higher
– VM2 can be run on the SecurView workstation or a separate computer.

• Crescendo CSCIntegration (Hologic SharedFile Partner)

– Crescendo CSCIntegration version 3.8.2134.0 or higher for DigiDictate-IP version
3.6.287.12 or higher
– CSCIntegration and DigiDictate-IP can run only on a separate computer.
• Dataworxs AudioWav Mic (Hologic SharedFile Partner)
– Dataworxs AudioWav Mic version 2.00.017 or higher
– AudioWav Mic can be run on the SecurView workstation or a separate computer.
• Dolbey FusionDictate (Custom: XML file)
– Dolbey FusionDictate version 1.4.28 (a.k.a. version 8) or higher
– FusionDictate can be run on the SecurView workstation or a separate computer.
• Dolbey FusionExpert (Custom: XML file)
– Dolbey FusionExpert version 5.1.30 or higher
– FusionExpert can be run on the SecurView workstation (with or without front-end
speech recognition module) or a separate computer.
– Fusion Text version 8.6.13 or higher is required for Windows 10 (Pro, Enterprise,
Enterprise LTSB).
– The current released version is Fusion Text 9.0.7.
• DR Systems Send ID XML Interface (Hologic SharedFile Partner)
– DR Systems Send ID XML Interface version 8.2 or higher and AppLink version 10.0 or
higher
– DR Systems web application can be run on the SecurView workstation or a separate
computer.
• Epic Radiant RIS (Custom: COM API)
– Epic Radiant RIS version Spring 2006 or higher
– Radiant RIS can be run on the SecurView workstation or a separate computer.
– Version 2015 or higher is required for Windows 10 with IE 11.
– The current released version is Epic 2018.
• Euromed MedSpeech (Hologic TCP/IP Partner)
– Euromed MedSpeech version 3.0 Rev 10 or higher
– MedSpeech can be run on the SecurView workstation or a separate computer.
• G2 Speech MediSpeech (Custom: COM API)
– G2 Speech MediSpeech version 5.0 or higher
– MediSpeech client can be run on the SecurView workstation or a separate computer.
• GE Centricity PACS (Custom: COM API)
– GE Centricity PACS version 3.2
– Centricity PACS can run only on a separate computer.

• GE Centricity RIS-IC (Custom: COM API)

– GE Centricity RIS-IC version 10.5 SP25 or higher
– Centricity RIS-IC client can be run on the SecurView workstation or a separate
computer.
• GE/IDX Imagecast (Custom: COM API)
– GE/IDX Imagecast (a.k.a. Centricity RIS-IC) version 10.3.9 or higher
– Imagecast client can be run on the SecurView workstation or a separate computer.
• HSS CRIS (Hologic TCP/IP Partner)
– HSS CRIS version 1.06.12n or higher
– HSS CRIS can be run on the SecurView workstation (without Speech Recognition or
Digital Dictation) or a separate computer (with Speech Recognition or Digital
Dictation).
• Ikonopedia Breast Imaging Suite (Hologic SharedFile Partner)
– Ikonopedia Breast Imaging Suite version 1.0 or higher
– Breast Imaging Suite can be run on the SecurView workstation or a separate computer.
• Infinitt G3 PACS (Hologic TCP/IP Partner)
– Infinitt G3 PACS version 3.0.11.4 BN2 or higher
– Infinitt G3 PACS web viewer can be run on the SecurView workstation or a separate
computer.
• Insight OmniCare (Hologic SharedFile Partner)
– Insight OmniCare version 7.5.2 or higher
– OmniCare can be run on the SecurView workstation or a separate computer.
• Intelerad InteleViewer (Hologic SharedFile Partner)
– Intelerad InteleViewer version 4.6.1 or higher
– InteleViewer can run only on a separate computer.
• Lanier Serial (Custom: Serial)
– MedQuist/Lanier VoiceWriter Digital Stations
– Application runs on separate hardware, with a serial cable connecting the SecurView
workstation and the Lanier station.
– MedQuist DocQvoice Workstation (formerly DocQment Ovation) version 1.1.5 or
higher
– DocQvoice can be run on the SecurView workstation or a separate computer.
• M*Modal Fluency for Imaging Reporting (Hologic SharedFile Partner)
– M*Modal Fluency for Imaging Reporting version 3.3.0 or higher
– Fluency for Imaging Reporting can be run on the SecurView workstation or a separate
computer.
– Version 4.0 or higher runs on Windows 10 with IE 11.
– The current released version is 4.9.

• MagView (Hologic SharedFile Partner)

– MagView version 6.3 or higher
– MagView can be run on the SecurView workstation or a separate computer.
– MagView version 6.x or higher runs on Windows 10.
– The current released version is MagView Luminary (8.x).
Note
This interface is preferred to use instead of the MagView TCP/IP interface.
• MagView (Custom: TCP/IP)

– MagView version 5.3.500 or higher
– MagView can be run on the SecurView workstation or a separate computer.
• MammaSoft (Custom: Proxy TCP/IP)
– KVB MammaSoft (Germany) version 1.0 or higher
– MammaSoft can be run on the SecurView workstation or a separate computer.
• MaSc RIS (Custom: HTTP)
– KVWL MaSc RIS (Germany) version 2.0 or higher
– MaSc RIS can be run on the SecurView workstation or a separate computer.
• Medicalis Professional (Hologic TCP/IP Partner)
– Medicalis Professional version 2.4.2.15 or higher
– Professional can be run on the SecurView workstation or a separate computer.
• MedOutlook RIS (Custom: TCP/IP)
– Keymind Computing MedOutlook RIS (Norway) version 1.0.0.1 or higher
– MedOutlook can run only on a separate computer.
• MedQ Dictation (Hologic SharedFile Partner)
– MedQ Dictation version 5.0.x or higher
– Dictation can be run on the SecurView workstation or a separate computer.
• MedQuist SpeechQ (Custom: COM API)
– MedQuist SpeechQ for Radiology version 1.2 or higher
– SpeechQ can be run on the SecurView workstation or a separate computer.
• MRS (Custom: TCP/IP)
– MRS Mammography Reporting System version 6.6.46 or higher
– MRS Aspen version 8.0 or higher
– MRS client can be run on the SecurView workstation or a separate computer.
– MRS version 7.1 or higher is required for Windows 10 (Pro).
– MRS Aspen runs on Windows 10 (Pro).
– The current released versions are MRS 7.3.025, Aspen Breast 8.0.2548.

• MultiView or Aegis (Custom: TCP/IP)

– Hologic MultiView version 4.0 or higher and Hologic Aegis version 3.2
– MultiView can be run on the SecurView workstation or a separate computer.
• NBSS British Screening RIS (Hologic Proxy Partner)
– NHSBSP NBSS British Screening RIS can be run on the SecurView workstation or a
separate computer.
• peerVue qiVue (Hologic TCP/IP Partner)
– peerVue qiVue version 6.3.3 or higher and QICS version 7.0.2 or higher
– qiVue can run only on a separate computer.
• PenRad (Custom: XML file or Hologic SharedFile Partner)
– PenRad version 5.1.84 or higher
– PenRad can be run on the SecurView workstation or a separate computer.
– Version 5.7.76 or higher runs on Windows 10 (Pro) with IE 10 or 11, Edge, Chrome.
– The current released version is Series 7.
Note
This interface is preferred to use instead of the serial interface.
• Philips iSite PACS (Custom: HTTP plug-in)

– Philips iSite PACS plug-in for iSite Radiology Client version 3.6 and 4.1
– Philips IntelliSpace version 4.4
– iSite PACS can run only on a separate computer.
• PowerScribe or EWS (Custom: XML file)
– Nuance/Dictaphone PowerScribe version 4.6 or higher with PACSBridge 4.7 1009
– Nuance Enterprise Workstation (EWS) version 3.0 with PACSBridge 6.5.1
– PowerScribe or EWS client can be run on the SecurView workstation or a separate
computer.
• PowerScribe bi-directional (Custom: XML file)
– Nuance/Dictaphone PowerScribe version 4.7 or higher with PACSBridge 4.7 1021
supports bi-directional open patient
– PowerScribe client can be run on the SecurView workstation or a separate computer.
– Nuance RadWhere version 3.0.18.14 or higher
– RadWhere client can be run on the SecurView workstation or a separate computer.
– Nuance PowerScribe 360 version 1.0 or higher
– PowerScribe 360 (including Dragon SDK client edition 10) can be run on the SecurView
workstation or a separate computer.
– Version 4.0 or higher runs on Windows 10.

• QDoc StudyViewer (Custom: COM API)

– Agfa QDoc StudyViewer version 5.5.1 or higher
– StudyViewer client can be run on the SecurView workstation or a separate computer.
• RadNet VDI (Custom: COM API)
– Cerner Millenium RadNet VDI version 2007.18 or higher
– RadNet VDI can be run on the SecurView Workstation or a separate computer.
– Version 2015.01.22 or higher is required for Windows 10.
• RadNet VDI prior to 2007.18 (Custom: COM API)
– Cerner Millenium RadNet VDI versions prior to 2007.18
– RadNet VDI can be run on the SecurView Workstation or a separate computer.
• RadNet VDI for ORMC (Custom: COM API)
– Cerner RadNet VDI version 2004.03 or higher, customized for Orange Regional Medical
Center
– RadNet VDI can be run on the SecurView workstation or a separate computer.
• ScImage Picom Client (Hologic SharedFile Partner)
– ScImage Picom Client version 3.03.059 or higher
– Picom Client can be run on the SecurView workstation or a separate computer.
• SecurView (Custom: TCP/IP)
– SecurView DX Diagnostic Workstation version 5-0-0 or higher and SecurView RT
Technologist Workstation version 6-0-0 or higher
• SecurView Serial Partner (Custom: Serial)
– Currently, these partners include PenRad, MRS, MagView
– Third-party application runs on a separate computer, with a serial cable connecting the
SecurView workstation and the third-party application computer.
• Selenia AWS (Custom: TCP/IP)
– Hologic Selenia Acquisition Workstation version 3.3 or higher
– Selenia AWS can run only on a separate computer.
• SERGAS SIDI (Hologic TCP/IP Partner)
– SERGAS SIDI (Spain) version 2.10 or higher
– SERGAS SIDI can run only on a separate computer.
• SESCAM Dulcingest RIS (Hologic TCP/IP Partner)
– SESCAM Dulcingest RIS version 7.8.3.1 or higher
– Dulcingest RIS can be run on the SecurView workstation or a separate computer.
• Softek Illuminate InSight (Hologic SharedFile Partner)
– Softek Illuminate InSight version 2.12 or higher
– Illuminate InSight can be run on the SecurView workstation or a separate computer.

• Spantel Audio Recorder (Custom: COM API)

– Spantel Audio Recorder version 2.0 or higher
– Audio Recorder can be run on the SecurView workstation or a separate computer.
• syngo Workflow MLR (Europe) (Hologic Proxy Partner)
– Siemens syngo Workflow MLR (Europe) browser version VB30 or higher
– Siemens syngo Workflow MLR (Europe) can be run on the SecurView workstation or a
separate computer.
• syngo Workflow Portal Radiologist (Custom: HTTP)
– Siemens syngo Workflow Portal Radiologist (with optional Voice) version 30 or higher
– Portal Radiologist can be run on the SecurView workstation or a separate computer.
• syngo Workflow ReadExam (Custom: XML file)
– Siemens syngo Workflow (formerly Novius RIS) ReadExam (with optional Voice)
version 27.1 or higher
– ReadExam can be run on the SecurView workstation or a separate computer.
• WinScribe Internet Author (Hologic SharedFile Partner)
– WinScribe Internet Author version 3.8 or higher
– WinScribe Internet Author can be run on the SecurView workstation or a separate
computer.

Table 5: Partner Interfaces

Partner Receives Sends
Type
Open Update Open Update
Login Logout Patient Patient Responds Login Logout Patient Patient
Hologic Proxy Partner+ Proxy - - - - No    -
Hologic SharedFile Partner+ SharedFile     No    
Hologic TCP/IP Partner+ TCP/IP     Yes    
Hologic TCP/IP Partner (no TCP/IP
    No    
response)+ (no response)
3M Radiology Link
SharedFile    - No - - - -
Software
Agfa TalkStation* COM API    - Yes - - - -
Allscripts (Eclipsys) Sunrise TCP/IP
- - - - No    -
Radiology (no response)
Amicas Vision Series
XML file - - - - No - -  -
(v4.0-5.1, v5.5)
TCP/IP
- - - - No    -
Avreo InterWorks PACS (no response)
Candelis ImageGrid RIS SharedFile - -  - No - -  -
TCP/IP
- - - - No    -
Carestream RIS (no response)
CDI Multifondacs TCP/IP - - - - Yes - -  -
TCP/IP
- - - - No - -  -
Commit; Screening MIS (no response)
Compressus VM2 TCP/IP - - - - Yes    
Crescendo CSCIntegration SharedFile  -  - No - - - -
Dataworx AudioWav Mic SharedFile - -  - No - - - -
Dolbey FusionDictate XML file - -  - No - - - -
Dolbey FusionExpert XML file - -  - No - - - -
DR Systems Send ID SharedFile - - - - No - -  -
Epic Radiant RIS* COM API    - No - -  
Euromed MedSpeech TCP/IP - -  - Yes - - - -
G2 Speech MediSpeech* COM API    - No - - - -
GE Centricity PACS COM API - - - - No - -  -
GE Centricity RIS-IC* COM API    - No - -  -
GE/IDX Imagecast* COM API    - Yes - - - -
HSS CRIS TCP/IP    - Yes    -
Ikonopedia Breast Imaging
SharedFile - -  - No - -  -
Suite
Infinitt G3 PACS TCP/IP    - Yes    -
Insight OmniCare SharedFile - - - - No - -  -
Intelerad InteleViewer SharedFile - - - - No    -
Lanier Serial Serial - -  - No - - - -
MedQuist DocQvoice Serial - -  - No - - - -

Partner Receives Sends

Type
Open Update Open Update
Login Logout Patient Patient Responds Login Logout Patient Patient
M*Modal Fluency for SharedFile    - No - -  
Imaging Reporting
MagView SharedFile  -  - No - -  
MagView Cust TCP/IP - -  - No - -  -
MammaSoft Cust Proxy - - - - No - -  -
MaSc RIS HTTP - - - - No - -  -
Medicalis Professional TCP/IP -    Yes    
MedOutlook RIS Cust TCP/IP - -  - No - -  -
MedQ Dictation SharedFile - -  - No - -  -
MedQuist SpeechQ* COM API    - No - -  -
MRS Cust TCP/IP    - Yes    -
MultiView or Aegis Cust TCP/IP     Yes    -
NBSS British Screening RIS Proxy - - - - No - -  -
peerView qiVue TCP/IP    - Yes - -  -
PenRad XML file - -  - No - -  -
PenRad SharedFile - -  - No - -  
Philips iSite PACS HTTP plug-in - - - - No - -  -
PowerScribe or EWS XML file    - No - - - -
PowerScribe bi-directional XML file    - No - -  
Nuance RadWhere XML file    - No - - - -
PowerScribe 360 XML file    - No - -  
QDoc StudyViewer COM API    - No    -
RadNet VDI* COM API    - No - - - -
RadNet VDI prior to version
COM API    - No - - - -
2007.18*
RadNet VDI for ORMC* COM API    - No - - - -
ScImage Picom Client SharedFile - - - - No    -
SecurView Cust TCP/IP     Yes    
SecurView Serial Partner Serial - -  - No - - - -
Selenia AWS Cust TCP/IP - - - - No - -  -
TCP/IP
- - - - No  -  -
SERGAS SIDI (no response)
SESCAM Dulcingest RIS TCP/IP - - - - Yes    -
Softek Illuminate Insight SharedFile    - No - - - -
Spantel Audio Recorder* COM API - -  - Yes - - - -
syngo Workflow (Europe) Proxy - - - - No - -  -
syngo Workflow Portal
HTTP - - - - No - -  -
Radiologist*
syngo Workflow ReadExam XML file - - - - No - -  -
WinScribe Internet Author SharedFile    - No - - - -
+ Denotes available functionality
*Application Synchronization must be installed on the same computer as this third-party
application. Application Synchronization can be installed and configured on a computer

other than SecurView or MultiView if necessary using the instructions in Installing Application
Synchronization on page 17.
Note
Third-party application versions listed are the earliest versions of software
validated by Hologic, usually the earliest version of the third-party application
that supported the interface.
If you have questions regarding support of a particular third-party application, call Hologic
Technical Support.
Note
Contact Hologic Technical Support to check on a third-party application that is
not shown above.

Chapter 5—Application Types
Chapter 5
Application Types
Chapter 5
• Hologic Proxy Partner on page 63

• Hologic SharedFile Partner on page 65
• Hologic TCP/IP Partner on page 67
• Application Types on page 69
5.1 Hologic Proxy Partner

Note
Only one instance of Hologic Proxy Partner can be configured per Application
Synchronization instance.
Third-party vendors may choose to implement the Hologic Proxy Partner interface. This
interface is a command line driven proxy application provided by Hologic that uses the AS
Adapter. These vendors are referred to as Hologic Proxy Partners.

See TCP/IP Communications Page on page 68 for instructions regarding the Hologic Proxy
Partner Communications page, which is a TCP/IP Communications page.
Any partner that has been validated by Hologic prior to this document’s release will be
listed. Customers may use new partners of this application type as soon as the partner
completes validation with Hologic. The application type default settings support all message
types of the Hologic Proxy Partner interface; however some partners may not choose to
implement all message types. The sent messages configuration may need to be adjusted. See
table Partner Interfaces on page 59 for more information.
The customer is responsible for arranging for a TPA technical representative (or on-site IT
person) to be available during the integration set up with the TPA. This representative must
install and configure the TPA software.
The HologicASProxy intermediary program is required. This program is included on the
Application Synchronization installation disk. This executable must be installed on the same
computer where the TPA software is installed.
For HologicASProxy installation instructions, see Install/Uninstall Separate Proxy Application
on page 143 Use the installer within the HologicASProxyInstallShield folder.
After HologicASProxy is installed, the TPA representative will be able to configure the TPA
to communicate with the HologicASProxy application. The HologicASProxy application
communicates directly with Application Synchronization.
See Configuring and Troubleshooting Proxy Applications on page 145 for instructions on how to
reconfigure and troubleshoot Hologic Proxy Partner applications.

5.2 Hologic SharedFile Partner

Third-party vendors may choose to implement the Hologic SharedFile Partner interface
(XML file drop). These vendors are referred to as Hologic SharedFile Partners.
The XML Mapping option allows TPAs to use the Hologic SharedFile Partner interface
without having to implement Hologic’s XML format. See XML Mapping on page 34 for more
information.

Table 6: Hologic SharedFile Partner Communications Page Defaults

Field Default Description
Inbound File Name TPARequest.xml The file that the TPA writes for
Application Synchronization to
read.
Delete On Read Not checked Whether or not Application
Synchronization deletes a received
XML file after reading it.
Directory C:\HologicXmlShare\ The mutually shared directory.
Outbound File HologicRequest.xml The file that Application
Name Synchronization writes for the
TPA to read.
Encryption Type XOr or Blowfish The encryption algorithm that will
be used to encrypt user
credentials.
Encryption Key holx The encryption code used for the
Blowfish Encryption Type only.
OpenPatient Fields At least one of these fields Use this area to configure which
is required: Patient ID, fields are included in the
Accession Number, Study outbound file. The default settings
Instance UID, Study ID are recommended.
types of the Hologic ShareFile Partner interface; however some partners may not choose to
implement all message types. The accepted messages and sent messages configuration may
need to be adjusted. See table Partner Interfaces on page 59 for more information.
person) to be available during the set up with the TPA. This representative must install and
configure the TPA software.
The Hologic SharedFile Partner application can potentially send and receive messages with
Application Synchronization by placing and reading XML files in a mutually shared
directory (folder). The mutually shared directory must be created manually if it does not
already exist.
To test the Application Synchronization configuration for sending messages to a Hologic
SharedFile Partner without the Hologic SharedFile Partner application installed, just confirm
that the XML files are being created in the configured directory.

Installing Hologic SharedFile Partner Application on a Separate Computer

It is recommended that you configure and share a directory on the computer where
Application Synchronization is installed rather than the TPA workstation. You will then map
a drive letter on the Hologic SharedFile Partner application workstation to the shared
directory on the Application Synchronization computer. For instructions, see Using Windows
File Sharing and Drive Mapping on page 138.
5.3 Hologic TCP/IP Partner

Third-party vendors may choose to implement the Hologic TCP/IP Partner interface (AS
Adapter). These vendors are referred to as Hologic TCP/IP Partners.
types of the Hologic TCP/IP Partner interface; however some partners may not choose to
implement all messages types and responses. The accepted messages and sent messages
configuration may need to be adjusted. See table Partner Interfaces on page 59 for more
information.
Third-party vendors have the option to implement sending or receiving a Response (success
or failure) to each synchronization request (e.g. login, logout, open patient). If the third-party
vendor has implemented responses, use the Hologic TCP/IP Partner application type. If the
third-party vendor has not implemented Responses, use the Hologic TCP/IP Partner (no
response) application type. See the ’Partner Type’ and ‘Responds’ columns in table Partner
Interfaces on page 59.
person) to be available during the set up with the TPA. This representative must install and
configure the TPA software.

5.3.1 TCP/IP Communications Page

This configuration page has a read-only display for Application Synchronization’s IP address
and port number. Below that are the fields for entering the connected application’s IP address
and port number. An error message is displayed upon attempting to move to another page if
the IP address is not a valid IP format.
Note
The SecurView application uses ports 4700 and 65000-65500, so those values
should never be used as the listening port for a connected application that is
running on a SecurView Workstation.
Note
The default listening port for the MultiView application is 5102.
Select (Ping IP Address) to test the IP address. A failure will result in a red error
message (Failed to ping the IP (X.X.X.X).) and a success will result in a blue message
(Successfully pinged the IP (X.X.X.X).).

5.4 Application Types

This section provides configuration instructions for the supported TPAs.
• Agfa TalkStation on page 71.
• Allscripts (Eclipsys) Sunrise Radiology on page 71.
• Amicas Vision Series v4.0-5.1 and v5.5 on page 73.
• Candelis ImageGrid RIS on page 74.
• Commit; Screening MIS on page 74.
• Crescendo CSCIntegration for DigiDictate-IP on page 75
• Dataworxs AudioWav Mic on page 76.
• Dolbey FusionDictate on page 77.
• Dolbey FusionExpert on page 78
• Epic Radiant RIS on page 79
• Euromed MedSpeech on page 81
• G2 Speech MediSpeech on page 81
• GE Centricity PACS on page 83
• GE Centricity RIS-IC on page 84
• GE/IDX Imagecast on page 87
• Insight OmniCare on page 91
• Intelerad InteleViewer on page 91
• Lanier Serial on page 92
• M*Modal Fluency for Imaging Reporting on page 94
• MagView (as Hologic SharedFile Partner) on page 95
• MagView on page 96
• MammaSoft on page 97
• MaSc RIS on page 98
• Medicalis Professional on page 99
• MedOutlook RIS on page 99

• MedQuist SpeechQ on page 100

• MRS on page 104
• MultiView or Aegis on page 104
• peerVue qiVue on page 106
• PenRad on page 107
• Philips iSite PACS on page 109
• PowerScribe or EWS on page 111
• PowerScribe bi-directional on page 114
• QDoc Study Viewer on page 117
• RadNet VDI on page 117
• ScImage Picom Client on page 119
• SecurView on page 119
• SecurView Serial Partner on page 121
• Selenia AWS on page 122
• Softek Illuminate InSight on page 123
• Spantel Audio Recorder on page 123
• syngo Workflow Portal Radiologist on page 125
• syngo Workflow ReadExam on page 126
• WinScribe Internet Author on page 127

5.4.1 Agfa TalkStation

The customer is responsible for arranging for an Agfa technical representative (or on-site IT
person) to be available during the integration set up with Agfa TalkStation. This
representative must install and configure Agfa TalkStation Client.
There are a few items to keep in mind when installing Agfa TalkStation as a connected
application:
• Only one instance of Agfa TalkStation can be configured per Application
• Agfa TalkStation Client can be installed on the SecurView workstation or a separate
computer.
• Application Synchronization must be installed on the same computer where the Agfa
TalkStation Client is running.
• The Server Name to enter on the Comm page is the name of the device on which
Agfa TalkStation Server is installed.
• The Agfa technical representative (or on-site IT person) will provide the value to
configure.
• There is no default setting for Server Name on the Comm page.

5.4.2 Allscripts (Eclipsys) Sunrise Radiology

To configure Application Synchronization to interface with Sunrise Radiology, select the
Hologic TCP/IP Partner (no response) application type when installing Application
Synchronization.
To configure Sunrise Radiology as a Hologic TCP/IP Partner (no response) connected
application:
1. On the Type page in the Application Alias field, enter the same name that is configured
for Sunrise Radiology in the AS Adapter configuration file.
2. On the Comm page in the IP Address field, enter the IP address of the computer where
Sunrise Radiology is running (e.g. either on SecurView or a separate computer), and in
the Port Number field enter 5102.
3. On the Message Type page, clear the messages that Sunrise Radiology does not support.
To install Sunrise Radiology:
Allscripts deploys the AS Adapter files with the Sunrise Radiology installer. The RIS wrapper
program must be installed in C:\Program Files\Internet Explorer. Visual Basic Runtime is
installed with RIS Web Utils. The user requires Active X permission (with RIS permissions) to
run Sunrise Radiology.

5.4.3 Amicas Vision Series v4.0-5.1 and v5.5

The customer is responsible for arranging for an Amicas technical representative (or on-site
IT person) to be available during the integration set up with Amicas.
Note
The Amicas representative must install and configure Amicas Vision Series PACS
client software on a separate computer.
Table 7: Amicas Vision Series Communications Page Default Settings

Directory C:\Amicas\ This is the mutually shared directory.
Inbound File Name AmicasRequest.xml This is the file that the Amicas Vision
Series client software writes and
Application Synchronization reads.
The Amicas Vision Series application sends messages to Application Synchronization by
placing XML files in a mutually shared directory (folder). Amicas provided the XML file
format to Hologic. The mutually shared directory must be created manually if it does not
already exist.
Installing Amicas Vision Series on a Separate Computer
It is recommended to configure and share a directory on the computer where Application
Synchronization is installed rather than the TPA workstation. You will then map a drive
letter on the Amicas Vision Series workstation to the shared directory on the Application
Synchronization computer. For instructions, see Using Windows File Sharing and Drive
Mapping on page 138.

5.4.4 Candelis ImageGrid RIS

Candelis is a Hologic SharedFile Partner. To configure integration with Candelis ImageGrid
RIS, you should be familiar with the procedures in the Hologic SharedFile Partner section
(see Hologic SharedFile Partner on page 65).
There are a few items to keep in mind about the Candelis ImageGrid RIS application:
• Supports sending the OpenPatient CLEAR message
• Sends only Patent ID in OpenPatient messages
• Uses only Accession Number in received OpenPatient messages
• The preferred OpenPatient Study Filter settings are:
• Accept More than One Study: Unchecked
• Accept Only MG Studies: Unchecked
• Study Date Sorting Direction: Newest first
• Accept Only Unread Studies: Unchecked
5.4.5 Commit; Screening MIS

To configure Application Synchronization to interface with Commit; Screening MIS, select
the Hologic TCP/IP Partner (no response) application type when installing Application
Synchronization.
To configure Commit; Screening MIS as a Hologic TCP/IP Partner (no response) connected
application:
1. On the Type page in the Application Alias field, enter COMMIT.
2. On the Comm page in the IP Address field, enter the IP address of the computer where
Commit; Screening MIS is running (e.g., either on SecurView or a separate computer),
and in the Port Number field enter 5101.
3. On the Message Type page clear the messages that Commit; Screening MIS does not
support.
To install AS Adapter components for Commit; Screening MIS:
The Commit; Screening MIS installer does not install the necessary AS Adapter components.
Commit will provide a ZIP file containing the AS Adapter 1.4 files.
1. Unzip the AS Adapter 1.4 files.
2. Place the unzipped files in C:\Program Files\Internet Explorer on the computer where
Commit; Screening MIS is running.

3. Open the Hologic.SecurView.AppSync.Adapters.dll.config file in C:\Program

Files\Internet Explorer.
a. Set the IP address in the APPLINKER_PROPERTY_DEFINITION section to the IP
address of the SecurView where Application Synchronization is installed.
b. Set the Hologic Bridge Port in the APPLINKER_PROPERTY_DEFINITION section to
5100.
c. Set the DEVICE section name to COMMIT.
d. Set the IP address in the DEVICE section to the IP address of the computer where
Commit; Screening MIS is running (e.g. either on SecurView or a separate computer).
e. Set the COMMIT port in the DEVICE section to 5101.
f. Save and close the Hologic.SecurView.AppSync.Adapters.dll.config file.
4. Restart both Commit; Screening MIS and Application Synchronization.
5.4.6 Crescendo CSCIntegration for DigiDictate-IP

Crescendo is a Hologic SharedFile Partner. To configure integration with Crescendo
CSCIntegration you should be familiar with the procedures in the Hologic SharedFile Partner
section (see Section Hologic SharedFile Partner on page 65).
There are a few items to keep in mind about the Crescendo CSCIntegration application:

5.4.7 Dataworxs AudioWav Mic

A Dataworxs AudioWav Mic representative is responsible for configuring their system for
integration with Hologic products. Dataworxs AudioWav Mic can be run on the SecurView
Dataworxs AudioWav Mic is a Hologic SharedFile Partner. To configure integration with
Dataworxs AudioWav Mic you should be familiar with the procedures in the Hologic
SharedFile Partner section above (see Section Hologic SharedFile Partner on page 65).
The default Directory for Dataworxs AudioWav Mic is C:\Dictate.
The preferred OpenPatient Study Filter settings are:
• Accept Only MG Studies: Checked
• If No Unread Studies Are Available, Accept: One Read
Permissions for AudioWav Mic: Right-click the file name C:\Windows\AWCMIC.ini, select
Properties, and set Security > Full Control (for all users/groups).
Permissions for C:\Dictate folder: Right-click the folder name C:\Dictate, select Properties,
and set Security > Full Control (for all users/groups).
Permissions in Registry: HKLM\SOFTWARE\Dataworxs Systems: Security > Full Control
(for all users/groups).
The radiologist user launches the AudioWav Mic application with the required log in. When
an OpenPatient message is triggered to AudioWav Mic, the application reads the file and
populates the demographic data in the appropriate fields. The radiologist uses a DR2000
microphone to record the dictation. When finished, the radiologist puts the microphone in
the stop position and presses the New button on the microphone to save the dictation. The
.wav and .xml dictation file pair is imported to the dictation system file server via socket
transfer (port 1702).

5.4.8 Dolbey FusionDictate

The customer is responsible for arranging for a Dolbey technical representative (or on-site IT
person) to be available during the integration set up with Dolbey FusionDictate. This
representative must install and configure the Dolbey FusionDictate client software and
microphone on the SecurView workstation or a separate computer.
Note
When installing FusionDictate on a SecurView workstation, set the Windows SCR
user with permission to access all files/folders of FusionDictate. (e.g., Program
Files, hidden program data folders).
The Dolbey FusionDictate application receives messages from Application Synchronization

by reading XML files from a mutually shared directory (folder). Dolbey provided the XML
file format to Hologic. The mutually shared directory must be created manually if it does not
already exist. To test the Application Synchronization configuration without Dolbey
FusionDictate installed, confirm the XML files are being created in the configured directory.

Installing Dolbey FusionDictate on the Application Synchronization Computer

If the Dolbey FusionDictate application is being installed on the same computer as
Application Synchronization, the defaults are acceptable in most cases. Give the information
below to the Dolbey technical representative. If necessary, this information can be changed to
match the Dolbey settings.
Table 8: Dolbey Communications Page Default Settings
Directory C:\Dolbey\ This is the mutually shared directory.
Root File Name request This is the file that Application Synchronization
writes and the Dolbey client software reads.
Installing Dolbey FusionDictate on a Separate Computer

It is recommended that you configure and share a directory on the computer where
Application Synchronization is installed rather than on the TPA workstation. You will then
map a drive letter on the Dolbey FusionDictate workstation to the shared directory on the
Application Synchronization computer. For instructions, see Using Windows File Sharing and
Drive Mapping on page 138.
5.4.9 Dolbey FusionExpert

The customer is responsible for arranging for a Dolbey technical representative (or on-site IT
person) to be available during the integration set up with Dolbey FusionExpert. This
representative can install and configure the Dolbey FusionExpert client software and
microphone on the SecurView workstation (with or without the front-end speech recognition
module) or a separate computer.
The Dolbey FusionExpert application receives messages from Application Synchronization
by reading XML files from a mutually shared directory (folder). Dolbey provided the XML
already exist. To test the Application Synchronization configuration without Dolbey
FusionExpert installed, confirm the XML files are being created in the configured directory.
Installing Dolbey FusionExpert on the Application Synchronization Computer
If the Dolbey FusionExpert application is being installed on the same computer as
Application Synchronization, the defaults are acceptable in most cases. Give the information
from table Dolbey Communications Page Default Settings on page 78 to the Dolbey technical
representative. If necessary, this information can be changed to match the Dolbey settings.
Installing Dolbey FusionExpert on a Separate Computer
It is recommended to configure and share a directory on the same computer as Application
Synchronization rather than the TPA workstation. You will then map a drive letter on the
Dolbey FusionExpert workstation to the shared directory on the Application Synchronization
computer. For instructions, see Using Windows File Sharing and Drive Mapping on page 138.

5.4.10 Epic Radiant RIS

The customer is responsible for arranging for an Epic technical representative to be available
during the integration set up with Radiant RIS. This representative must install and configure
Radiant RIS client software.
There are a few items to keep in mind when installing Radiant RIS as a connected
application:
• Only one instance of Radiant RIS can be configured per Application Synchronization
instance.
• The Radiant RIS Client can be installed on the SecurView workstation or a separate
computer.
• Application Synchronization must be installed on the same computer where the Epic
Radiant RIS is running.
• Sending the Login message from SecurView to Epic Radiant RIS is mandatory in
order for OpenPatient to work correctly from SecurView to Epic. In the Application
Synchronization configuration for the Epic Radiant RIS connected application, on the
Message Type page make sure Login and Logout in the Accepted Messages section
are checked. On the SecurView make sure each user has the user preference ‘On
login and logout’ checked in the User Profile tab. Application Synchronization
obtains an authentication challenge string from Epic, and then provides the
username, password and authentication challenge string to Epic for Login.

Application Synchronization Configuration for Epic Radiant RIS

UpdatePatientState
Application Synchronization listens for ClosePatient and CloseStudy events from Epic to
interpret as UpdatePatientState messages to send to other connected applications. Select
(check) the Epic event/reason values to interpret as UpdatePatientState. The unchecked Epic
event/reason values will be ignored. At least one CloseStudy Reason value must be checked.
Program ID
On the Communications page for the Epic Radiant RIS application type, there is a ‘Program
ID’ edit field. Fill in the edit field with the appropriate Epic Hyperspace ProgId information
that the facility’s RIS/PACS administrator or Epic technical representative will supply.
Table 9: Program IDs and Versions
Version ProgId
Prior to Spring 2006 ERISPACSLink70.RISPACSDefaultBridge
Spring 2006 ERISPACSLink74.RISPACSDefaultBridge
Summer 2010 ERISPACSLink78.RISPACSDefaultBridge
Epic 2012 ERISPACSLink79.RISPACSDefaultBridge
Epic 2014 Workflow Conductor ERISMiddleware81.RISMidwareCOM
Epic 2016, 2017 ERISPACSLink83.RISPACSDefaultBridge
Epic 2016, 2017 Workflow Conductor ERISMiddleware83.RISMidwareCOM
Epic Integration ID (FDI ID)
Epic Integration ID (FDI ID) is a value that Epic uses to determine which workstation it is
talking to (in this case SecurView) and must match the set-up of the Epic system. Typically
this is the .1 of the FDI record number in Epic for the SecurView.
The facility’s RIS/PACS administrator or Epic technical representative will provide the Server
Name that will be configured.
There is no default setting for the Epic Integration ID (FDI ID).
Close Open Studies on OpenPatient
If Close Open Studies on OpenPatient is checked (default), Application Synchronization will
attempt to close all open studies in Epic Radiant RIS before requesting to open a different
patient/study.

5.4.11 Euromed MedSpeech

To configure Application Synchronization to interface with Euromed MedSpeech, select the
Hologic TCP/IP Partner application type when installing Application Synchronization.
EuroMed receives Open Patient messages and sends responses. Upon receiving an Open
Patient message, MedSpeech opens a new dictation window.
MedSpeech uses a SpeechMagic 6.1 recording microphone.
The preferred OpenPatient Study Filter settings are:
• Accept More than One Study: Checked
• Accept Only MG Studies: Checked
• If No Unread Studies Are Available, Accept: All Read
5.4.12 G2 Speech MediSpeech

The customer is responsible for arranging for a G2 Speech technical representative to be
available during the integration set up with MediSpeech. When installing MediSpeech on
SecurView, this representative must install and configure the MSIT COM object and any
required drivers on SecurView as the Windows user Administrator.

There are a few items to keep in mind when installing G2 Speech MediSpeech as a connected
application:
• Only one instance of G2 Speech MediSpeech can be configured per Application
• The G2 Speech MediSpeech interface can be installed on the SecurView workstation
or a separate computer.
• Application Synchronization must be installed on the same computer where G2
Speech MediSpeech is running.
Application Synchronization Configuration for G2 Speech MediSpeech

Application Synchronization relies on the G2 Speech MediSpeech MSIT COM object to be
installed for this integration to work.
If the MSIT COM object is not installed and Application Synchronization is configured to
have a G2 Speech MediSpeech application type, Application Synchronization will fail at start
up. Once the MSIT COM object is installed, Application Synchronization will start up
successfully.
G2 Speech must provide the following information for connectivity:
OpenPatient Module – G2 Speech module opened when an OpenPatient message is
received: Dictation Batch or Dictation Interactive

5.4.13 GE Centricity PACS

The customer is responsible for arranging for a GE technical representative (or on-site IT
person) to be available during the integration set up with GE Centricity PACS. Application
Synchronization uses the GE Generic Extend API to communicate with GE Centricity PACS
via a WCF Client.
There are two methods to setup GE Centricity PACS for integration with Application
Synchronization:
Method One: Modify Extend.properties and Extend_string_properties.
1. In Extend.properties under Properties for Extend 1 add the following (the number after
‘extend’ in the commands may differ depending on the number of integrations)
Increment the value in the following line by 1:
com.ge.med.platinum.extend.numberOfThirdPartyApplications=1
# name
com.ge.med.platinum.extend.extend1.name=HologicAppsync
# name of each of the applications

com.ge.med.platinum.extend.extend1.application1.name=Hologic
Appsync
com.ge.med.platinum.extend.extend1.worklist.numberOfUIComponents=
1
com.ge.med.platinum.extend.extend1.worklist.component1.enable=tru
e
Note
The path is dependent on where Application Synchronization is installed. Double
backslash is required in the path.
com.ge.med.platinum.extend.extend1.worklist.component1.command="c
:\\Progra~2\\Hologic\\HologicAppSync\\Synchronizer\\Hologic.Secur
View.AppSync.ConnectedApplications.AppGePacsWcfClient.exe" <PATID>
# application launched whenever a context change on the view tab occurs.

\\com.ge.med.platinum.extend.extend1.contextApp="c:\\Progra~2\\Ho
logic\\HologicAppSync\\Synchronizer\\Hologic.SecurView.AppSync.Co
nnectedApplications.AppGePacsWcfClient.exe" <PATID>
2. In Extend_string.properties under Properties for Extend 1 add the following:
com.ge.med.platinum.extend.extend1.worklist.component1.label=Holo
gic Appsync
com.ge.med.platinum.extend.extend1.worklist.component1.buttonlabe
l=Hologic AppSync

Method Two: Modify the platinum_custom.properties configuration file

1. Modify the platinum_custom.properties configuration file in order to add a Hologic
AppSync button to the configuration.
com.ge.med.platinum.extend.extend3.application5.name=Hologic
AppSync
com.ge.med.platinum.extend.extend3.worklist.component5.enable=tru
e
com.ge.med.platinum.extend.extend3.worklist.component5.command=C:
\Program
Files\Hologic\HologicAppSync\Synchronizer\Hologic.SecurView.AppSync.C
onnectedApplications.AppGePacsWcfClient.exe <PATID>
com.ge.med.platinum.extend.extend3.worklist.component5.label=Holo
gic AppSync
com.ge.med.platinum.extend.extend3.worklist.component5.buttonlabe
l=Hologic AppSync
2. Ensure that the line in step 1 containing the following file name points to the directory
where this file is located:
Hologic.SecurView.AppSync.ConnectedApplications.AppGePacsWcfClient.exe.
This file is installed during Application Synchronization installation.
5.4.14 GE Centricity RIS-IC

There are a few items to keep in mind when installing GE Centricity RIS-IC as a connected
application:
• Only one instance of GE Centricity RIS-IC can be configured per Application
• Starting with version 10.5, GE Imagecast is renamed GE Centricity RIS-IC.
• The GE Centricity RIS-IC interface can be installed on the SecurView workstation or
a separate computer.
• Application Synchronization must be installed on the same computer where the GE
Centricity RIS-IC is running.
• Certain GE modules (e.g., Precision Reporting) require Microsoft .NET Framework
4.0 installed on the same computer as Application Synchronization and GE Centricity
RIS-IC.
• The Application Synchronization installer does not install GE’s COM Object
ImagecastInterface.exe. There are two ways to install ImagecastInterface.exe:
• GE installs this on the same computer as Application Synchronization and GE
Centricity RIS-IC, or
• Work with the site PACS administrator to download the GE clientcontrols.msi
file. Running clientcontrols.msi installs ImagecastInterface.exe and registers the
ActiveX controls used by the Centricity RIS-IC web application.

• When run on the SecurView workstation, the GE Centricity RIS-IC web interface
displays on the SecurView additional monitor using Internet Explorer. If SecurView
is using a newer version of Internet Explorer than is supported by Centricity (e.g.,
IE 11.0), run Internet Explorer in Compatibility View.
• Sending the Login and Logout messages from SecurView to GE Centricity RIS-IC is
mandatory for OpenPatient to work correctly from SecurView to Centricity RIS-IC.
In the Application Synchronization configuration for the GE Centricity RIS-IC
connected application, on the Message Type page make sure Login and Logout in the
Accepted Messages section are checked. On the SecurView make sure each user has
the user preference 'On login and logout' checked in the User Profile tab.
• Sending a Login mesage to Centricity RIS-IC no longer opens the Centricity RIS-IC
main menu. It only sets the user context. Sending a Logout message to Centricity
RIS-IC performs a Logout to release the user context.
Note
A RIS-driven workflow is no longer possible with Centricity RIS-IC 10.7 and
later. Centricity RIS-IC now requires Application Synchronization to initialize
listening for OpenPatient messages (RIS-IC context change events) after each user
has logged into Centricity RIS-IC. Application Synchronization does not have a
way to receive an indication that a user has logged into Centricity RIS-IC.

Application Synchronization Configuration for GE Centricity RIS-IC

The GE Centricity RIS-IC administrator must provide the following information to configure
on the Application Synchronization Communications page for GE Centricity RIS-IC:
Table 10: GE Centricity RIS-IC Communications Page Settings
DSN idxrad, imagecast or RISDB
If the facility’s RIS/PACS administrator or GE
technical contact cannot provide the DSN, try
‘idxrad’ first, as it the most commonly used DSN by
Centricity RIS-IC.
WebRoot http://xxx.xxx.xxx.xxx/imagecast/
RIS-IC Normal Defines the window state assigned to an opened
Window Centricity RIS-IC module. The drop-down list
Location contains: Normal, Maximized, Minimized, OnTop,
TopMost.
RIS-IC Clinical Defines the Centricity RIS-IC module to be opened
Module Information on OpenPatient. The drop-down list contains
Notes (CLIN) Results Reporting and Clinical Information Notes
(CLIN).
To Install GE Centricity RIS-IC on the SecurView Workstation
1. Open Internet Explorer on the SecurView workstation. The Windows Internet Explorer
application appears.
2. On the Tools menu, select Internet Options. The Internet Options window appears.
3. Select the Security tab. The Security window appears.
4. Select (Internet), and then select Custom Level. The Security Settings window
appears.
5. Make the following settings changes:
a. Download signed ActiveX controls: Enable
b. Download unsigned ActiveX controls: Enable
c. Initialize and script ActiveX controls not marked as safe: Enable
d. Use Pop-up Blocker: Disable

6. Select OK to close the Security Settings window. A Warning window appears.

7. In the Warning window, select Yes.
8. In the Security tab, select (Local intranet), and then select Custom Level. Repeat
steps 5, 6, and 7.
9. In the Internet Options window, select OK.
10. Log into the SecurView application as a radiologist user.
11. Trigger an open patient event on SecurView by opening a patient that is available in the
GE Centricity RIS-IC database.
• If the user preference to synchronize open patient automatically is enabled, the
configured Centricity RIS-IC Module for the same patient displays on the screen.
• If an Internet Explorer ‘Information Bar’ message appears, select the Do not show
this message again check box, and select OK. A message may appear that states that
your session has timed out. Select OK.
12. Close the Centricity RIS-IC Module.
13. Trigger another open patient event on SecurView by opening another patient that is also
available in the GE Centricity RIS-IC database.
GE Centricity RIS-IC Precision Reporting
It is not possible to launch Precision Reporting via Application Synchronization.
5.4.15 GE/IDX Imagecast

There are a few items to keep in mind when installing GE/IDX Imagecast as a connected
application:
• Only one instance of GE/IDX Imagecast can be configured per Application
• Starting with version 10.5, GE/IDX Imagecast is renamed GE Centricity RIS-IC. Use
the GE Centricity RIS-IC application type if the customer has version 10.5 SP25 or
higher.
• The GE/IDX Imagecast interface can be installed on the SecurView workstation or a
separate computer.
• Application Synchronization must be installed on the same computer where the
GE/IDX Imagecast is running.
• The Application Synchronization installer does not install GE’s COM Object
ImagecastInterface.exe. GE must install this on the same computer as Application
Synchronization and GE/IDX Imagecast.
• When run on the SecurView workstation, the GE/IDX Imagecast web interface
displays on the SecurView additional monitor using Internet Explorer. If SecurView
is using a newer version of Internet Explorer than is supported by Imagecast (e.g.,
IE 11.0), run Internet Explorer in Compatibility View.

Note
On the Application Messages Page for Imagecast, accepting the Login and Logout
messages will not be selected by default, because Login launches the Imagecast
main menu. The OpenPatient message authenticates the user, so most users do
not need to open the Imagecast main menu. Do not enable acceptance of these
messages, and do not enable the SecurView user preference for automatic
synchronization of login and logout, unless the customer wants to launch the
Imagecast main menu upon SecurView login.

Application Synchronization Configuration for GE/IDX Imagecast

The GE/IDX Imagecast administrator must provide the following information to configure on
the Application Synchronization Communications page for GE/IDX Imagecast:
Table 11: GE/IDX Imagecast Communications Page Settings
DSN idxrad or imagecast
If the facility’s RIS/PACS administrator or GE
technical contact cannot provide the DSN, try
‘idxrad’ first, as it the most commonly used
DSN by Imagecast.
WebRoot http://xxx.xxx.xxx.xxx/imagecast/
Imagecast Normal Defines the window state assigned to an
Window opened Imagecast Module. The drop-down
Location list contains: Normal, Maximized, Minimized,
OnTop, and TopMost
Imagecast Clinical Defines the Imagecast Module to be opened
Module Information Notes on OpenPatient. The drop-down list contains:
(CLIN) Results Reporting, Clinical Exam Notes (CEN)
or Clinical Information Notes (CLIN).
CLIN requires Imagecast/Centricity RIS-IC
10.5 or later, and replaces CEN.
Window Title imagecast;centricit Defines the search strings used to identify
Strings y;ris-ic;oneview open Imagecast Module windows. This is a
semi-colon delimited text string.

To Install GE/IDX Imagecast on the SecurView Workstation

1. Open Internet Explorer on the SecurView workstation. The Windows Internet Explorer
application appears.
2. On the Tools menu, select Internet Options. The Internet Options window appears.
3. Select the Security tab. The Security window appears.
4. Select (Internet), and then select Custom Level. The Security Settings window
appears.
5. Make the following settings changes:
a. Download signed ActiveX controls: Enable
b. Download unsigned ActiveX controls: Enable
c. Initialize and script ActiveX controls not marked as safe: Enable
d. Use Pop-up Blocker: Disable
6. Select OK to close the Security Settings window. A Warning window appears.
7. In the Warning window, select Yes.
8. In the Security tab, select (Local intranet), and then select Custom Level. Repeat
steps 5, 6, and 7.
9. In the Internet Options window, select OK.
10. Log into the SecurView application as a radiologist user.
11. Trigger an open patient event on SecurView by opening a patient that is available in the
GE/IDX Imagecast database.
• If the user preference to synchronize open patient automatically is enabled, the
configured Imagecast Module for the same patient displays on the screen.
• If an Internet Explorer ‘Information Bar’ message appears, select the Do not show
this message again check box, and select OK. A message may appear that states that
your session has timed out. Select OK.
12. Close the Imagecast Module.
13. Trigger another open patient event on SecurView by opening another patient that is also
available in the GE/IDX Imagecast database.

5.4.16 Insight OmniCare

An Insight Healthcare representative is responsible for configuring their system for
integration with Hologic products. OmniCare can be run on the SecurView workstation or a
separate computer.
Insight Healthcare is a Hologic SharedFile Partner. To configure integration with Insight
OmniCare you should be familiar with the procedures in the Hologic SharedFile Partner
section above (see Hologic SharedFile Partner on page 65). The directory and file name are
configurable in OmniCare, but by default OmniCare uses the Hologic default directory and
inbound file name.
There are a few items to keep in mind about the Insight OmniCare application:
• OmniCare requires .NET 4.0 or higher.
• OmniCare requires Crystal Reports DLLs that are installed by Insight.
• OmniCare triggers an OpenPatient message when the user double-clicks an exam
from the OmniCare Radiologist Worklist.
• OmniCare provides Patient ID and Accession Number.
5.4.17 Intelerad InteleViewer

An Intelerad representative is responsible for configuring their system for integration with
Hologic products.
Intelerad is a Hologic SharedFile Partner. To configure integration with Intelerad
InteleViewer you should be familiar with the procedures in the Hologic SharedFile Partner
section above (see Hologic SharedFile Partner on page 65). The directory and file name are
configurable in InteleViewer.
There are a few items to keep in mind about the Intelerad InteleViewer application:
• InteleViewer uses XOr encryption.
• InteleViewer requires Delete on Read to be enabled.
• InteleViewer provides Patient ID, Accession Number, and Study Instance UID in
OpenPatient messages.

5.4.18 Lanier Serial

The Lanier application is a standalone application that resides on its own hardware. The
Lanier station receives messages from Application Synchronization over a serial connection.

Application Synchronization Configuration for Lanier Serial

Use the default configuration on the Application Synchronization Communications page for
Lanier Serial.
Note
The Comm Port should be set to the port to which the null serial cable is
connected.
The default behavior is to send Accession Number only. If Lanier requires Patient ID only or
both Accession Number and Patient ID, select the appropriate option in the ‘Data String’
field.
The Lanier Serial interface as defined by MedQuist expects the Accession Number and
Patient ID fields to be concatenated with no delimiter when both are sent. The expected
length of each field must be configured in the Lanier device. Therefore, sending both values
in either order can be selected only if each value is of a fixed length for the customer site.
MedQuist DocQvoice Workstation
DocQvoice can be configured by selecting the Lanier Serial application type during
Application Synchronization installation. Follow the instructions for the Lanier Serial
configuration to enable synchronization with DocQvoice.
DocQvoice can be run on the SecurView workstation or a separate computer. A MedQuist
technical representative must install DocQvoice. When DocQvoice is run on the same
computer as Application Synchronization, a serial loop back device must be used, such as a
USB cable that has two Serial ports on it that comes with a small application to install. You
may also need a null modem adapter and a gender changer. Connect the two serial ports
(COM3 and COM4) from the USB Y adapter 1 (COM3) to a Null Modem to a gender changer
to USB Y adapter 2 (COM4). Be sure to set the Comm Port correctly in the Application
Synchronization configuration. Otherwise use the default configuration settings (e.g. Data
String = Accession Num Only).

5.4.19 M*Modal Fluency for Imaging Reporting

An M*Modal representative is responsible for configuring their system for integration with
Hologic products.
M*Modal is a Hologic SharedFile Partner. To configure integration with M*Modal Fluency
for Imaging Reporting you should be familiar with the procedures in the Hologic SharedFile
Partner section above (see Hologic SharedFile Partner on page 65). The directory and file names
are the Hologic defaults.
There are a few items to keep in mind when installing M*Modal Fluency for Imaging
Reporting as a connected application:
• Fluency uses XOr encryption.
• Fluency provides and matches on Patient ID and Accession Number in OpenPatient
messages.
• The Fluency DesktopClientIntegrationEngine folder must reside under
C:\MModal\FluencyForImaging\Reporting\Bin
• The Fluency configuration file
C:\MModal\FluencyForImaging\Reporting\FluencyReporting.ini must include the
following line:
Integrationpoint=/ClinicalWorkflow/MModalServices/FluencyWeb/S
tatic/Integrations/JsXml/JsXmlIntegrationPoint.htm
or (previously)
Integrationpoint=/ClinicalWorkflow/MModalServices/FluencyWeb/S
tatic/Integrations/XmlForDesktopClient/XmlIntegrationPoint.htm
Note
Fluency may terminate upon receiving a Logout message, and may need to be
restarted manually. M*Modal may modify the logout behavior to prevent
termination.

5.4.20 MagView (as Hologic SharedFile Partner)

A MagView representative is responsible for configuring their system for integration with
Hologic products. MagView can perform installation and configuration remotely. If there are
questions regarding MagView installation or configuration, contact MagView technical
support at 800.553.8996, option 2. MagView can be run on the SecurView workstation or a
separate computer.
MagView is a Hologic SharedFile Partner. To configure integration with MagView you
should be familiar with the procedures in the Hologic SharedFile Partner section above (see
Hologic SharedFile Partner on page 65).
There are a few items to keep in mind about the MagView application:
• When the MagView application receives an OpenPatient message, it automatically opens
the identified patient’s record, and selects the newest study identified in the message in
the application’s reporting tab.
• With version 6.7 and later, MagView accepts a Login message, but does not support
Logout. When MagView receives a Logout message the user will not be logged out.
When MagView receives the next Login message it will be prompted to login as another
user.
• Even though MagView does not support Logout, if Login is used it is important to check
both Login and Logout in Accepted Messages on the Message Type page.

5.4.21 MagView
There are a few items to keep in mind when installing MagView as a connected application:
• Hologic SharedFile Partner is the preferred application type to use with MagView.
• The MagView application can be installed on the SecurView workstation or a separate
computer.
• MagView uses a TCP/IP interface to communicate with Application Synchronization. See
TCP/IP Communications Page on page 68 for the TCP/IP Communications page
instructions.
• If the MagView Client is deployed through Citrix or another thin client system, the
MagView side of the Synchronization will not function.
• When configuring a MagView application, the application Alias must be ‘MagView’.
• MagView has a maximum of 15 characters for Patient ID and 20 characters for Accession
Number. If a site exceeds this limit, a workaround must be performed by MagView to
create larger Patient ID and Accession number fields. This action requires additional
configuration in the MagView software to create a custom primary field at runtime.
• MagView always has the Patient ID and Accession Number in upper case characters. If
these fields on the Hologic connected application have lower case characters, when
Application Synchronization sends an OpenPatient message it will not correspond on the
Hologic side. The only workaround is to have the site use only upper case characters for
Patient ID and Accession Number.

5.4.22 MammaSoft
The customer is responsible for arranging for a MammaSoft technical representative (or
on-site IT person) to be available during the integration set up with MammaSoft. This
representative must install and configure the MammaSoft Digital Screening software.
There are a few items to keep in mind when installing MammaSoft Digital Screening as a
connected application:
• Only one instance of MammaSoft can be configured per Application Synchronization
instance.
• A ‘MammaSoft Proxy’ intermediary application must be installed on the computer
where the MammaSoft Digital Screening software is installed. This program is on the
Application Synchronization installation disk. For installation instructions, see
Install/Uninstall Separate Proxy Application on page 143. Use the installer within the
MammaSoftInstallShield folder.
• After MammaSoft Proxy is installed, the MammaSoft representative will be able to
configure the MammaSoft Digital Screening application to communicate with the
MammaSoft Proxy application. The MammaSoft Proxy application is what will
communicate directly with Application Synchronization.
• The MammaSoft Proxy application uses a TCP/IP interface to communicate with
Application Synchronization. See TCP/IP Communications Page on page 68 for the
TCP/IP Communications page instructions.
• To reconfigure and troubleshoot proxy applications, see Configuring and
Troubleshooting Proxy Applications on page 145.
• The MammaSoft representative must load Java 1.5 on the computer where
MammaSoft is being installed. This software can be found on the Oracle website.

5.4.23 MaSc RIS

There are a few items to keep in mind when installing MaSc RIS as a connected application:
• A MaSc RIS technical representative may be required to install and configure the
MaSc RIS application.
• The MaSc RIS application initiates image reviewing requests (OpenPatient) by
sending HTTP-GET messages to Application Synchronization’s HTTP listening port.
• The HTTP query URL stored on the MaSc RIS must be configured as follows:
http://<host>:<port>/viewcontrol?<searchpart>
In the URL, <host> shall be IP address (or machine name if the name can be resolved
properly) of Application Synchronization. The port <port> must be supplied for the
Application Synchronization configuration.
• For MaSc to connect to Application Synchronization, the Windows user that starts
Application Synchronization must have Administrative privileges. To give
Administrative privileges to this user, see Setting a Windows User to Administrator on
page 136.
On the Communications page for the MaSc RIS application type, fill in the ‘HTTP port’
with the information supplied by the MaSc RIS representative.

5.4.24 Medicalis Professional

To configure Application Synchronization to interface with Medicalis Professional, select the
Hologic TCP/IP Partner application type when installing Application Synchronization.
There are a few items to keep in mind about the Medicalis Professional application:
• Medicalis Professional requires .Net 3.5.
• All the AS Adapter settings (which must match Hologic Application Synchronization
settings) are stored in the Medicalis SecurView plug-in XML configuration file.
• When the SecurView plug-in is selected on login,
"Hologic.SecurView.AppSync.Adapters.dll.config" is updated to those settings.
5.4.25 MedOutlook RIS

There are a few items to keep in mind when installing MedOutlook RIS as a connected
application:
• Only one instance of MedOutlook RIS can be configured per Application
• A MedOutlook RIS technical representative must install and configure the
MedOutlook RIS application.
• A ‘MedOutlook RIS Proxy’ intermediary application must be installed on the
computer where the MedOutlook RIS software is installed. This program is on the
Application Synchronization installation disk. For installation instructions, see
Install/Uninstall Separate Proxy Application on page 143. Use the installer within the
MedBrokerInstallShield folder.
• After MedOutlook RIS Proxy is installed, the MedOutlook RIS representative will be
able to configure the MedOutlook RIS application to communicate with the
MedOutlook RIS Proxy application. The MedOutlook RIS Proxy application is what
will communicate directly with Application Synchronization.
• The MedOutlook RIS Proxy application uses a TCP/IP interface to communicate with
Application Synchronization. See TCP/IP Communications Page on page 68 for the
TCP/IP Communications page instructions.
• To reconfigure and troubleshoot proxy applications, see Configuring and
Troubleshooting Proxy Applications on page 145.

To Configure the MedOutlook RIS Application (Optional)

The MedOutlook RIS application will be configured already upon deployment. This
connected application will not require additional configuration once deployed.
The MedOutlook RIS representative may need to perform the following additional
configurations:
2. Start WordPad.
3. On the WordPad File menu, select Open. Navigate to the following directory and file.
The path will be similar to the example below.
(Installation Path)\MedBrokerApplication\MedBrokerToAppSyncConfig.xml
4. Select the file and then select Open.
5. Allow the Keymind Computing engineer to configure this file, and then select File >
Save.
5.4.26 MedQuist SpeechQ

There are a few items to keep in mind when installing MedQuist SpeechQ as a connected
application:
• Only one instance of MedQuist SpeechQ can be configured per Application
• The MedQuist SpeechQ client software can be installed on the SecurView
MedQuist SpeechQ client is running.
• A MedQuist technical representative must install and configure the MedQuist
SpeechQ client software. The Application Synchronization will not start up until the
MedQuist SpeechQ Desktop Integration SDK has been installed on the computer
where Application Synchronization is installed.
• The MedQuist SpeechQ Desktop Integration SDK is not part of the SpeechQ client
software. It must be deployed, installed and registered by a MedQuist technical
representative.
• MedQuist SpeechQ requires Microsoft Office Word 2000 or later. It is the MedQuist
representative’s responsibility to install all third-party software required for their
operation. Ensure that the MS Toolbar does not start up automatically.
• MedQuist SpeechQ log files are written to the following directories:
C:\Documents and Settings\All Users\Application Data\Speech\Integrations
C:\Documents and Settings\All Users\Application Data\Speech\Client\Trace
• There is one configurable option on the MedQuist SpeechQ Communications page,
to select the SpeechQ OpenPatient Action. The drop-down list choices are
Create/Add to Report (default) and Order Selection. This should be set according to
the customer’s preference.

If there is an issue connecting to MedQuist SpeechQ V1.2, check the identification in

Note
Perform these steps only for SpeechQ V1.2. These steps are not necessary for
SpeechQ V1.3.

2. In the Run dialog type cmd and press [Enter].
3. In the command window, navigate to the following directory:
C:\WINDOWS\assembly\GAC\ReportStationSDK
Note
In case this directory is not found, previously the directory was reported as
C:\WINDOWS\assembly\GAC\RSDesktop.
4. Enter the dir command to get the directory listing.

5. The directory listing is encoded as ‘version number’__’public token key’
Example:
05/16/2007 11:45 AM <DIR> 1.2.115.0__4912b0c373c7a4c0
In this case the version is 1.2.115 and the public token key is 4912b0c373c7a4c0.

6. Locate the following file:

E:\HologicAppSync\Synchronizer\Hologic.SecurView.AppSync.Synchronizer.exe.config
7. Open the file and add the following text, if not present already.
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<runtime>
<assemblyBinding
xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="ReportStationSDK"
publicKeyToken="4912b0c373c7a4c0" />
<bindingRedirect oldVersion="1.2.115.0"
newVersion="1.2.115.0" />
</dependentAssembly>
</assemblyBinding>
</runtime>
</configuration>
8. Confirm that all values within the <runtime> </runtime> tags appear in the file.
9. Make sure the newVersion="1.2.xxx.x" matches the version shown in the directory
listing. Save the file and restart the workstation.
Note
If the target system has: 1.2.234.0__4912b0c373c7a4c0, then newVersion may
need to be changed to 1.2.234.0.
10. If SpeechQ shuts down each time a study is closed or saved in SpeechQ, check the
AlwaysHideByPacs setting in ReportStation.exe.ini.
a. Open and edit the file C:\ProgramFiles\SpeechQ Client\ReportStation.exe.ini
b. Confirm AlwaysHideByPacs=1

To check MedQuist SpeechQ SDK configuration file:

1. The MedQuist SpeechQ Desktop Integration SDK requires the configuration file
ReportStationSDK.xml.
2. When the MedQuist representative installs the SpeechQ Desktop SDK on the same
computer as Application Synchronization, select ‘one box’.
Note
Application Synchronization must be installed on the same computer as the
SpeechQ client. Since Application Synchronization is always on the same
computer as the SpeechQ client and the SpeechQ Desktop SDK, this is a 'one box'
solution from the MedQuist perspective.
The ReportStationSDK.xml file will have the following configuration:

<?xml version="1.0"?>
<RSDesktop xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="RSDesktop">
<ReportStationPath>C:\Program Files\SpeechQ
Client\</ReportStationPath>
<IntegrationReportStationPort>8192</IntegrationReportStationPort>
<IntegrationReportStationSDKPort>8193</IntegrationReportStationSD
KPort>
<IntegrationReportStationHostIP>tcp://127.0.0.1</IntegrationRepor
tStationHostIP>
</RSDesktop>
Note
ReportStationPath is the path to Reportstation.exe that is configured on install
and may be different. For example:
<ReportStationPath>C:\Program Files (x86)\SpeechQ

Client\</ReportStationPath>
Note
The IntegrationReportStationPort value may be 5100.
In ReportStation.exe.ini, the line containing IntegrationSQPort = 8192 may need to

change to IntegrationSQPort = 5100.

5.4.27 MRS
There are a few items to keep in mind when installing MRS as a connected application:
• The MRS application can be installed on the SecurView workstation or a separate
computer.
• To integrate with Application Synchronization, the site must have at least the
minimum MRS software version 6.6.46, or MRS Aspen Breast.
• MRS uses a TCP/IP interface to communicate with Application Synchronization. See
TCP/IP Communications Page on page 68 for the TCP/IP Communications page
instructions.
• A MRS technical representative must install and configure the MRS client software.
• If the site wishes to install the MRS client software on the SecurView workstation,
then allow the MRS representative to install the client software under the Windows
Customer user.
• After the MRS software is installed and configured, perform the following steps to
ensure that the MRS application starts up under the Windows user "username"
where MRS will be used upon system boot.
To ensure that the MRS application starts up automatically:
1. Open Windows File Explorer and enter the following in the search bar:
C:\Users\<user>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\
2. On the desktop, locate and copy the MRS shortcut link.
3. Paste this link into the Startup folder.
5.4.28 MultiView or Aegis

There are a few items to keep in mind about the MultiView connected application:
• When configuring the MultiView connected application, the application alias must
match the 'MultiView Adapter Name' on the MultiView Application Synchronization
configuration page. Otherwise, MultiView will not function with Application
Synchronization. The default MultiView Adapter Name is MV AppSync Adapter.
• MultiView MM can be installed on SecurView or a separate computer.
• MultiView uses a TCP/IP interface to communicate with Application
Synchronization. See TCP/IP Communications Page on page 68.
• The default listening port for MultiView is 5102.
• When sending an OpenPatient message, MultiView can be configured to include
Patient ID, Study Instance UID and/or Accession Number from the MultiView
application from Match Keys on the MultiView Application Synchronization
configuration page.

• Upon receiving an Open Patient message, MultiView checks the following fields,
using case-sensitive matching: Patient ID, Study Instance UID, and Accession
Number. MultiView can be configured to control which of these fields are used for
matching from Match Keys on the MultiView Application Synchronization
configuration page.
• MultiView to MultiView synchronization is not supported in Application
Synchronization.
To configure MultiView with Application Synchronization:
1. In the MultiView application, navigate to Tools > Options > Application
Synchronization. The Application Synchronization page appears.
2. In the Match Keys section of the Application Synchronization page, select the Match Keys
that you want to configure. The Match Keys are Patient ID, Study Instance UID, and
Accession Number. The selected fields will be used for matching when received in
OpenPatient messages, and will be the fields included in sent OpenPatient messages.
Note
At least one Match Key must be selected.
3. Select the Manual Sync Open Patient check box to enable manual synchronization with
connected applications when opening a patient on MultiView. If this box is checked,
press the Manual Sync button on MultiView to send an Open Patient request to
4. The Manual Sync Open Patient check box is unchecked by default. If Application
Synchronization is configured on MultiView, opening a study from the MultiView Study
List triggers an Open Patient request.

5. To add/edit Application Synchronization:

Note
For MultiView MM standalone add one Application Synchronization instance.
For MultiView Web add one Application Synchronization instance per
MultiView Web client.
a. Select in the Application Synchronization Servers section. The Add Server

dialog appears.
b. Keep the default name (Hologic Bridge) and port number (5100). Enter the IP address
for Application Synchronization.
c. For MultiView MM standalone enter LOCAL for the Client Hostname. For
MultiView Web client enter the hostname of the computer where MultiView Web
client is running. Then select OK.
d. Select to edit the server IP address or to delete a server.
6. Select OK to save the changes and exit the page.

7. Restart MultiView services for the changes to take effect.
5.4.29 peerVue qiVue

To configure Application Synchronization to interface with peerVue qiVue, select the Hologic
TCP/IP Partner application type when installing Application Synchronization.
The typical peerVue installation folder is C:\Program Files (x86)\peerVue\pvmonitor. The
Hologic.SecurView.AppSync.Adapters.dll.config file can be found there.
The peerVue client application must have full read/write access to all files in C:\Program
Files (x86)\peerVue\pvmonitor and C:\Program Files\peerVue\pvmonitor (specific
directory will depend on whether the workstation is 32-bit or 64-bit). The peerVue client
application requires .NET 3.5 SP 1, and it requires access to the Registry to read/write its
settings.

5.4.30 PenRad
The customer is responsible for arranging for a PenRad technical representative (or on-site IT
person) to be available during the integration set up with PenRad. This representative must
install and configure the PenRad client software, either on the SecurView workstation or a
separate computer.
The PenRad application sends and receives messages with Application Synchronization by
placing and reading XML files in a mutually shared directory (folder). PenRad provided the
XML file format to Hologic. PenRad can be configured to support the Hologic SharedFile
Partner XML format. The mutually shared directory must be created manually if it does not
already exist. To test the Application Synchronization configuration for sending messages to
PenRad without PenRad installed, just confirm that XML files are being created in the
configured directory.
Regardless of which PenRad software version the customer has, PenRad must install a
special software patch in order for the PenRad application to be able to send OpenPatient
messages to Application Synchronization.

Installing PenRad on the Application Synchronization Computer

If the PenRad application is being installed on the same computer as Application
Synchronization, the defaults are acceptable in most cases. Give the information below to the
PenRad technical representative. If necessary, this information can be changed to match the
PenRad settings.
Table 12: PenRad Communications Page Default Settings
Inbound File PenRadRequest.xml This is the file that the PenRad client
Name software writes and Application
Synchronization reads.
Directory C:\PenRad\ This is the mutually shared directory.
Outbound File HologicRequest.xml This is the file that Application
Name Synchronization writes and the PenRad
client software reads.
To ensure that the PenRad application starts up automatically:
To have PenRad start automatically when the system starts, copy a shortcut to the PenRad
application into the startup directory of the Windows user <user> where Penrad will be used.
Perform the following steps:
2. Copy and paste a shortcut link to the PenRad application into the Startup folder.
Installing PenRad on a Separate Computer

In general it is recommended to configure and share a directory on the computer where
Application Synchronization is installed rather than the TPA workstation. You will then map
a drive letter on the PenRad workstation to the shared directory on the Application
However, if the customer wants to use a PenRad-driven workflow at all, configure the shared
directory on the PenRad workstation rather than the Application Synchronization computer.
Another option is to install Application Synchronization on the PenRad workstation.
When the PenRad application is running on a separate computer, you must map a network
drive on the PenRad computer that will apply to all users. This is needed because every
PenRad user has a separate Windows login/user. Create a batch file containing the following
single line and place it in the ‘all users’ startup folder on the PenRad computer.
net use z: \\holx_hostname\penrad /USER:workgroup\username password
Where ‘z’ represents the mapped drive letter, ‘holx_hostname’ represents the hostname of the
Application Synchronization computer, and ‘username’ and ‘password’ represent a user with
administrative privileges (e.g., customer and Simply-the-Best on SecurView).

5.4.31 Philips iSite PACS

On the Communications page for the Philips iSite PACS application type, fill in the ‘HTTP
Port’ with the default value 4870. Ensure that this port number is also configured in Philips
iSite PACS for the Hologic plug-in, and ensure that this port is not blocked.
In order for a Philips iSite PACS Radiology Client to trigger OpenPatient messages to
Application Synchronization, a plug-in must be added to the Philips iSite application and
configured to communicate with Application Synchronization.
Insert the Application Synchronization Installation DVD to the computer where the Philips
iSite PACS Radiology Client is running. Philips iSite plug-in files are located under
AppSyncFullInstallation\AppSyncInstaller\HologicASProxy\PhilipsISitePlugin.

To install Philips iSite plug-in:

1. Copy the Philips iSite plug-in folder to the desired installation location.
2. Open the Philips iSite Radiology client.
3. Select the P icon in the top right to set the preferences.
4. Expand the Machine Preferences sub-menu.
5. Select the Plug Ins element > Add.
6. Enter a name in the Name text box.
7. Type the full path to the AppSynciSiteRadiologyPlugIn.htm file in the URL text box.
8. Check the Enable in iSite Radiology check box.
9. Uncheck the Disable API check box and select OK.
10. Select Apply and then select OK.
11. Restart the Philips iSite Radiology client. The plug-in will be located in the iSite Tools
folder in the folder list on the left part of the screen.
12. Double-click ConfigureIsiteNetworkSettings.exe in the Philips iSite plug-in folder.
13. Enter the IP address of the computer on which Application Synchronization is installed.
14. Enter the HTTP Port number that Application Synchronizaton is listening on. This port
number should match the HTTP Port number entered on the Application
Synchronization Communications page for Philips iSite PACS. Select OK.
15. Restart the Philips iSite Radiology client.
To ensure that Philips iSite PACS is compatible with Internet Explorer 8 and later, a
security setting must be changed.
To change security settings to make iSite compatible with IE8 and later:
1. In the IE8 browser, select Tools>Internet Options.
2. Select the Security tab.
3. Select Custom level…..
4. Scroll down to Allow Data Sources Across Domains and change to Enable.
5. Select OK. Restart the browser and the Philips iSite Radiology client.
To uninstall Philips iSite plug-in:
1. Open the Philips iSite Radiology client.
2. Select the P icon in the top right to set the preferences.
3. Expand the Machine Preferences sub-menu.
4. Select the Plug Ins element > Remove.
5. Select Apply and then select OK.
6. Restart the Philips iSite Radiology client.

5.4.32 PowerScribe or EWS

The customer is responsible for arranging for a Nuance technical representative (or on-site IT
person) to be available during the integration set up with PowerScribe or Enterprise
Workstation (EWS). This representative must install and configure the PowerScribe or EWS
client software and microphone, either on the SecurView workstation or a separate computer.
If there are issues with the PowerScribe or PACSBridge configuration or operation that are
beyond the expertise of the local support personnel, call Nuance support at 1-800-833-7776
Monday–Friday, 8:00am – 8:00pm EST, or submit a web ticket via
http://isupport.nuance.com. The customer’s Nuance account number is needed to validate
maintenance is active. If further escalation is required, you may request to speak with a
support manager (e.g. Brian Wirkus).
Note
To avoid timeout issues, Nuance recommends a daily restart of any workstation
running PACSBridge. This action may not be necessary as timeout issues are rare.
However, if timeout issues occur, inform the customer that Nuance recommends
a daily reboot of the workstation, and direct them to the Nuance customer help
desk if they have additional questions.
5.4.32.1 PowerScribe
A PowerScribe client will accept messages from only one source (e.g. SecurView or a PACS
workstation, but not both). The customer also must have PACSBridge 4.7 1009 installed on a
server. If the customer has an earlier version of PACSBridge, or does not have PACSBridge,
do not proceed until the correct version is installed.
The PowerScribe application receives messages from Application Synchronization by reading
XML files from a mutually shared directory (folder). Nuance/Dictaphone provided the XML
already exist. To test the Application Synchronization configuration without PowerScribe
installed, just confirm the XML files are being created in the configured directory.

Installing PowerScribe on the Application Synchronization Computer

If the PowerScribe application is being installed on the same computer as Application
Synchronization, the defaults are acceptable in most cases. Give the information below to the
PowerScribe technical representative. If necessary, this information can be changed to match
the PowerScribe settings.
Table 13: PowerScribe or EWS Communications Page Default Settings
Directory C:\Dictaphone\ This is the mutually shared directory.
File Name study.xml This is the file that Application
Synchronization writes and the
PowerScribe or EWS client software
reads.
Encryption holx for PowerScribe This is the encryption code that must be
Key FFF-Dictaphone for configured on both sides.
EWS

To ensure that the PACSBridge application starts up automatically:

To have PACSBridge start automatically when the system starts, copy a shortcut to the
PACSBridge application into the startup directory of the windows user name <user> where
PowerScribe or EWS will be run. Perform these steps:
2. Copy and paste a shortcut link to the PACSBridge application into the Startup folder.
Installing PowerScribe on a Separate Computer

letter on the PowerScribe workstation to the shared directory on the Application
5.4.32.2 EWS
The Enterprise Workstation (EWS) can be configured by selecting the PowerScribe or EWS
application type during Application Synchronization installation. The customer must have
PACSBridge 6.5.1.0 installed on a server. If the customer has an earlier version of
PACSBridge, or does not have PACSBridge, do not proceed until the correct version is
installed. The Enterprise Workstation does not have the same flexibility for changing the
Encryption key as the rest of the Nuance product line does. The Encryption key for
Enterprise Workstation should always be set to FFF-Dictaphone. See table PowerScribe or
EWS Communications Page Default Settings on page 112 for additional information on
configuring the PowerScribe or EWS application type.
Note
EWS requires Microsoft Word. It is the Nuance representative’s responsibility to
install all third-party software required for their operation. Ensure that the MS
Toolbar does not start up automatically.

5.4.33 PowerScribe bi-directional

The customer is responsible for arranging for a PowerScribe technical representative (or
on-site IT person) to be available during the integration set up with PowerScribe. This
representative must install and configure the PowerScribe client software and microphone,
either on the SecurView workstation or a separate computer.
If there are issues with the PowerScribe or PACSBridge configuration or operation that are
beyond the expertise of the local support personnel, call Nuance support at 1-800-833-7776
Monday–Friday, 8:00am – 8:00pm EST, or submit a web ticket via
http://isupport.nuance.com. The customer’s Nuance account number is needed to validate
maintenance is active. If further escalation is required, you may request to speak with a
support manager (e.g. Brian Wirkus).
A PowerScribe client will accept messages from only one source (e.g. SecurView or a PACS
workstation, but not both). For PowerScribe version 4.7 or 4.8, the customer also must have
PACSBridge 4.7 1021 installed on a server. For PowerScribe version 5.0, the customer also
must have PACSBridge 5.0 1003. If the customer has an earlier version of PACSBridge, or
does not have PACSBridge, do not proceed until the correct version is installed.
The PowerScribe application sends and receives messages from Application Synchronization
by placing and reading XML files in a mutually shared directory (folder).
Nuance/Dictaphone provided the XML file format to Hologic. The mutually shared directory
must be created manually if it does not already exist. To test the Application Synchronization
configuration for sending messages to PowerScribe without PowerScribe installed, just
confirm the XML files are being created in the configured directory.

Installing PowerScribe on the Application Synchronization Computer

If the PowerScribe application is being installed on the computer where Application
Synchronization is installed, the defaults are acceptable in most cases. Give the information
below to the PowerScribe technical representative. If necessary, this information can be
changed to match the PowerScribe settings.
Table 14: PowerScribe bi-directional Communications Page Default Settings
Status File Name status.xml This is the file that PowerScribe client
software writes and Application
Synchronization reads.
Directory C:\Dictaphone\ This is the mutually shared directory.
File Name study.xml This is the file that Application
Synchronization writes and the PowerScribe
client software reads.
Encryption Key holx This is the encryption code that must be
configured on both sides.
To ensure that the PACSBridge application starts up automatically:
To have PACSBridge start automatically when the system starts, copy a shortcut to the
PACSBridge application into the Startup directory of the Windows user <user> where
PowerScribe will be run. Perform these steps:
2. Copy and paste a shortcut link to the PACSBridge application into the Startup folder.
Installing PowerScribe on a Separate Computer

letter on the PowerScribe workstation to the shared directory on the Application

5.4.33.1 Nuance RadWhere

Nuance RadWhere can be configured by selecting the PowerScribe bi-directional application
type during Application Synchronization installation. Follow the instructions for the
PowerScribe bi-directional configuration to enable the synchronization with RadWhere. Keep
in mind that RadWhere does not use PACSBridge. If there are issues with the RadWhere
configuration or operation that are beyond the expertise of the local support personnel, use
the same escalation procedure as for PowerScribe bi-directional.
Note
Set the Directory field to C:\RadWhere\.
Note
RadWhere supports only receiving Login, Logout, and OpenPatient messages.
Update the Application Messages page for the PowerScribe bi-directional
connected application accordingly by clearing the OpenPatient check box under
’Sent Messages’.
5.4.33.2 PowerScribe 360

PowerScribe 360 can be configured by selecting the PowerScribe bi-directional application
type during Application Synchronization installation. Follow the instructions for the
PowerScribe bi-directional configuration to enable the synchronization with PowerScribe 360.
Keep in mind that PowerScribe 360 does not use PACSBridge.
The Nuance field engineer must configure the PowerScribe 360 integration API via the
PowerScribe portal with base64 coding disabled (false). If there are issues with the
PowerScribe 360 configuration or operation that are beyond the expertise of the local support
personnel, use the same escalation procedure as for PowerScribe bi-directional.
Example PowerScribe 360 configuration for PACS, where Application Synchronization is
considered a PACS:
Type = PowerScribe XML
Mode = Slave:C:\PS360\study.xml;C:\PS360\status.xml;password=holx;base64=false
Note
Mode should not include FieldName.

5.4.34 QDoc Study Viewer

There are a few items to keep in mind when installing QDoc Study Viewer as a connected
application:
• Only one instance of QDoc Study Viewer can be configured per Application
• The QDoc Study Viewer software can be installed on the SecurView workstation or a
separate computer.
• An Agfa technical representative must install and configure the QDoc Study Viewer
client software.
• Desktop integration between both applications is accomplished using Agfa’s
‘Context Server’.
• Agfa’s ‘Context Server’ as well as agfa_crypto.dll that the Context Server is using for
communication of the password must be installed and registered by the Agfa
technical representative.
5.4.35 RadNet VDI

There are a few items to keep in mind when installing Cerner RadNet VDI as a connected
application:
• Only one instance of Cerner RadNet VDI can be configured per Application
• The Cerner RadNet VDI client software can be installed on the SecurView
Cerner RadNet VDI client software is running.
• This application type will work only with Cerner RadNet VDI version 2007.18 or
higher that supports receiving an accession number that is less than 18 characters.
• A Cerner technical representative must install and configure the Cerner Radiology
Desktop client software.
• On the Application Communication page for the RadNet VDI application type, there
is one edit field ‘CernerDomain’. Fill in the edit field with the appropriate Cerner
domain information that the facility’s RIS/PACS administrator will supply.
• The Cerner RadNet VDI client software requires access to a Cerner authentication
server, which resides on a separate computer in a facility’s network. If RadNet VDI is
running on SecurView, the Windows SCR user on the SecurView computer must be
registered on the facility domain in order for Cerner RadNet VDI to map the
authentication server drive and access the server.
The facility’s network administrator must perform the SCR user domain registration.
The Cerner technical representative must perform the Cerner Authentication Server
drive mapping.

• If RadNet VDI is running on SecurView, the Cerner RadNet VDI client software
requires write access to the HKLM\Software\Cerner registry key and its sub-keys.
The Cerner technical representative will enable write access to that registry key when
installing the Cerner RadNet VDI client software.
• If Cerner RadNet does not function on Windows 10, additional registry settings may
need to be modified. The Visual Desktop Integration Registry must be set at each
workstation.
For example, log in as Administrator and modify the following portion of the file
C:\Program Files\Cerner\vdiconfigureregistry.exe as follows:
Unidirectional
Accession
________89ABC_EFGHI (8 underscore (_) before the 8)
Resize Ratio: 1.0
5.4.35.1 RadNet VDI (Prior to 2007.18)

Only one instance of Cerner RadNet VDI can be configured per Application Synchronization
instance.
This application type is for RadNet VDI versions prior to 2007.18, which require receiving an
18-character accession number. Application Synchronization adds five (5) leading zeros to
the 13-character accession number value that it receives from the Hologic connected
application. Be sure that the DICOM images sent to SecurView contain a 13-character
accession number value produced by Cerner or a related Modality Worklist broker. The
configuration instructions are the same as for RadNet VDI.

5.4.35.2 RadNet VDI for ORMC

Only one instance of Cerner RadNet VDI can be configured per Application Synchronization
instance.
This application type was customized specifically for Orange Regional Medical Center
(ORMC) in Middletown, NY, which used a version of RadNet VDI that preceded 2007.18,
and a customized 11-character accession number value in DICOM images sent to SecurView.
RadNet VDI is running on SecurView. The configuration instructions are the same as for
RadNet VDI.
5.4.36 ScImage Picom Client

A ScImage representative is responsible for configuring their system for integration with
Hologic products. Picom Client can be run on the SecurView workstation or a separate
computer.
ScImage is a Hologic SharedFile Partner. To configure integration with Picom Client you
Hologic SharedFile Partner on page 65). Picom Client uses the default directory, file name, and
encryption.
5.4.37 SecurView
There are a few items to keep in mind for the SecurView connected application:
• When Application Synchronization is installed on a SecurView workstation, the
InstallShield will configure a SecurView connected application automatically during
installation. SecurView uses a TCP/IP interface to communicate with Application
Synchronization. The default listening port for the SecurView application is 4700. See
TCP/IP Communications Page on page 68.
• When configuring Application Synchronization in the SecurView application via the
Settings tab as the service user, the IP address and port entered should be that of
Application Synchronization and not the actual third-party application. The
Application Synchronization Installation program should configure these settings
correctly and generally they will not need to be changed.

• To access the Synchronization Settings dialog, under Synchronization Interface, select

Configure.
• During the first login to the SecurView application as the service user after a reboot,
if the Configure button on the Settings tab is used to open the Application
Synchronization Configuration Interface, the interface will be hidden behind the
SecurView application. Select OK at the bottom of the SecurView Settings tab to
bring the interface to the forefront.
• If another connected application is capable of sending OpenPatient CLEAR messages
to close the viewer on SecurView, enable the XAppCloseViewersID:CLEAR and
XAppCloseViewersUID:1.2.276.0.28.3.9.99999 settings in lightbox.ini by removing the
# at the beginning of the line (this is enabled by default on SecurView 8.1 and later).
• There are several ways for a SecurView user to initiate a Synchronization message to
a connected application that is capable of receiving the message. For testing, do the
following:
a. Log on to SecurView as a radiologist user, and then select Administration to
open the Patient list.
b. Select a patient and right-click on the patient name.
c. Select Synchronize to send an OpenPatient message to the configured connected
applications via Application Synchronization. If the option is disabled,
Synchronization has not been properly licensed or configured. Sending of Login
and Logout messages must be configured in each user’s preferences.
• Refer to the SecurView DX/RT Workstation User Guide for additional information on all
the different ways a user can synchronize with the connected applications.
• To configure the keypad for SecurView, see Configuring the SecurView Keypad on page
137.

5.4.38 SecurView Serial Partner

When the SecurView Serial Partner application type is selected, the Communications page
contains the settings to configure the serial port on the Application Synchronization
computer to which the serial cable is connected.
The Communications page consists of six different drop-down lists: Comm Port, Baud Rate,
Data Bits, Stop Bit, Parity, and End Marker. The common default values are pre-selected.
5.4.38.1 PenRad (as SecurView Serial Partner)

Prior to Application Synchronization 1.4, a serial connection was the only interface offered
with PenRad. The latest PenRad interface (see PenRad on page 107) is bi-directional, and it
allows PenRad to run on SecurView.
When configured using the SecurView Serial Partner application type the PenRad application
is a standalone application that resides on its own hardware. The PenRad software receives
messages from Application Synchronization over a serial connection. For Application
Synchronization to correctly interface with a PenRad application some additional steps must
be performed. In most cases, the same serial interface settings used with SecurView DX 3-x or
earlier will not work and must be altered on the PenRad software. At the customer site, the
local PenRad engineer must be contacted to alter these settings. The PenRad engineer should
use the following settings to configure PenRad.

PenRad Configuration:
[Hologic]
Enabled=YES
SerialPortInfo=COM1: baud=4800 parity=N data=8 stop=2 xon=off odsr=off octs=off dtr=off
rts=off idsr=off ReadTimeOut=300
Application Synchronization Configuration:
Use the following application type and communication configuration:
Select the application type: SecurView Serial Partner
Comm Port: (The comm port will need to be set to the port to which the null serial cable is
connected.)
Baud Rate: 4800
Data Bits: 8
Stop Bits: 2
Parity=no
End Marker: #
5.4.39 Selenia AWS

Note
Application Synchronization 4.3 does not apply to Selenia AWS synchronization
with SecurView RT or TechMate. For those products continue to use Application
Synchronization 2.1.
Only one instance of Selenia AWS can be configured per Application Synchronization
instance.
Hologic Selenia AWS has an interface that sends an OpenPatient message only. This is used
primarily to synchronize the Selenia AWS to the SecurView RT TechMate, or a Selenia AWS
to a SecurView RT workstation that is in the same room as the Selenia AWS. Within
Application Synchronization, there is no IP address or port to configure for the Selenia AWS
application type (i.e. no Communications page).
To configure the Selenia AWS:
1. Log off from the root user. Log into OS as apps.
2. Minimize the Selenia AWS application window.
3. Double-click the Netscape icon.
4. Log in with service name and password.
5. Select DROC.
6. Select Software Configuration.

7. Select /installed/apps.
8. Select Edit Direct Ray Operator console application.
9. Scroll until you locate site configuration and then select Edit Configuration File for
siteconfig.cfg.
a. Change tws sync enabled to true.
b. Set the tws IP address to the SecurView RT TechMate IP address.
c. Set the tws port to 5100.
10. Select Update to save changes.
5.4.40 Softek Illuminate InSight

A Softek representative is responsible for configuring their system for integration with
Hologic products. Illuminate InSight can be run on the SecurView workstation or a separate
computer.
Softek is a Hologic SharedFile Partner. To configure integration with Illuminate InSight you
Hologic SharedFile Partner on page 65). The directory, file name and encryption settings are
configurable in Illuminate InSight.
There are few items to keep in mind about the Illuminate InSight application:
• Accept Only Unread Studies: Checked
• If No Unread Studies Are Available, Accept: One Read
• A small Softek application (Automation.exe) runs in the background, watching for
messages in the shared folder.
• When the Illumuniate InSight application receives a Login message, it displays a
login screen. An identified user is not automatically logged into the application. The
Login message is required to be enabled in order to launch Illuminate InSight.
• When the Illumuniate InSight application receives a Logout message, it closes. The
next Login message restarts the Illuminate InSight application.
Important
Synchronization will not occur if the Illuminate InSight application is launched
manually.

5.4.41 Spantel Audio Recorder

Only one instance of the Spantel Audio Recorder application can be configured per
Application Synchronization instance.
The customer is responsible for arranging for a Spantel technical representative (or on-site IT
person) to be available during the integration set up with Spantel Audio Recorder. This
representative must install and configure the Audio Recorder client software, either on the
SecurView workstation or a separate computer.
There are a few items to keep in mind when installing Spantel Audio Recorder as a connected
application:
Audio Recorder client software is running.
• If the Philips SpeechMike drivers are not installed, both Spantel Audio Recorder and
Application Synchronization will fail to launch.
• When sending an OpenPatient message to the Spantel Audio Recorder, a Spantel
Author ID will have to be mapped to the sending application’s username. Refer to
the SecurView DX/RT Workstation User Guide for additional information on how to
map user information for connected applications.
Spantel Audio Recorder Communications page

There are two configurable check boxes on the Spantel Audio Recorder Communications
page.
• Hide Recorder on Dictate Complete: If this option is checked, the Spantel Audio
Recorder is minimized after a completed dictation.
• Deactivate Recorder on Dictate Complete: If this option is checked, the recorder will
be deactivated when a dictation is completed.

5.4.42 syngo Workflow Portal Radiologist

The customer is responsible for arranging for a Siemens syngo Workflow Portal Radiologist
technical representative (or on-site IT person) to be available during the integration set up
with syngo Workflow Portal Radiologist. This representative must install and configure the
Siemens syngo Workflow Portal Radiologist (with optional Voice feature) either on the
SecurView workstation or a separate computer.
There are a few items to keep in mind when installing Siemens syngo Workflow Portal
Radiologist as a connected application:
Siemens syngo Workflow Portal Radiologist client software is running.
• The Siemens syngo Workflow Portal Radiologist application sends messages to
Application Synchronization by HTTP-POST over TCP/IP.
On the Communications page for the syngo Workflow Portal Radiologist application type,
fill in the ‘HTTP port’ with the information supplied by the Siemens representative.

To install syngo Workflow Portal Radiologist on the SecurView Workstation

The following steps must be completed before the syngo Workflow Portal Radiologist client
can be run successfully on the SecurView workstation (All but step 1 should be completed by
the Siemens representative or on-site IT person):
1. The Windows SCR user must be changed to have Administrator Access (see Setting a
Windows User to Administrator on page 136).
2. The Siemens Web Server should be added to trusted sites in Internet Explorer.
3. The XML launch document on the Siemens Server should be configured to use localhost
as the address.
4. Permissions to allow ActiveX and scripts must be changed to ‘enabled’ or ‘allowed’ in
Internet Explorer.
5. The Siemens syngo Workflow Portal Radiologist client must be installed under the
Windows SCR user.
5.4.43 syngo Workflow ReadExam

The customer is responsible for arranging for a Siemens syngo Workflow ReadExam
technical representative (or onsite IT person) to be available during the integration set up
with syngo Workflow ReadExam. This representative must install and configure Siemens
syngo Workflow ReadExam (with optional Voice feature) either on the SecurView
The Siemens syngo Workflow ReadExam application sends messages to Application
Synchronization by placing XML files in a mutually shared directory (folder). Siemens
provided the XML file format to Hologic. The mutually shared directory must be created
manually if it does not already exist.

Installing ReadExam on the Application Synchronization Computer
If the syngo Workflow ReadExam application is being installed on the same computer where
Application Synchronization is installed, the defaults are acceptable in most cases. Give the
information below to the Siemens syngo Workflow technical representative. If necessary, this
information can be changed to match the syngo Workflow ReadExam settings.
Table 15: syngo Workflow ReadExam Communications Page Default Settings
Directory C:\NoviusReadExam\ This is the mutually shared directory.
File Name message.xml This is the file that the syngo Workflow
ReadExam client software writes and
Application Synchronization reads.
Installing ReadExam on a Separate Computer

letter on the syngo Workflow ReadExam workstation to the shared directory on the
Application Synchronization computer. For instructions, see Using Windows File Sharing and
Drive Mapping on page 138.
5.4.44 WinScribe Internet Author

A WinScribe representative is responsible for configuring their system for integration with
Hologic products. WinScribe Internet Author can be run on the SecurView workstation or a
separate computer.
WinScribe is a Hologic SharedFile Partner. To configure integration with WinScribe Internet
Author you should be familiar with the procedures in the Hologic SharedFile Partner section
(see Hologic SharedFile Partner on page 65).
When WinScribe Internet Author is installed on a system it adds two entries (NewExamPath,
NewExamXMLFile) to the Windows registry.
• NewExamPath. The setting that tells the Internet Author where to look for the XML
file that Application Synchronization generates. By default, this location is set to
C:\HologicXmlShare.
• NewExamXMLFile. The setting that tells the Internet Author the name of the file to
search for. By default, this name is set to HologicRequest.xml.
If the instructions from the Hologic SharedFile Partner section above are followed and
Internet Author is installed on the same computer as Application Synchronization, the
default settings for WinScribe will work.
If Internet Author is installed on a computer other than where Application Synchronization is
installed, then the NewExamPath setting will need to be changed to the path of the mutually
shared directory. A WinScribe representative is responsible for making this change.

If a WinScribe representative is unavailable, follow the steps below to change the

NewExamPath setting.
To change the NewExamPath setting:
2. In the Run dialog, type regedit and press [Enter]. The registry window appears.
3. Navigate to the following directory:
HKEY_LOCAL_MACHINE > SOFTWARE > WinScribe > Hologic Integration
4. Double-click the NewExamXMLFile entry and change the data value to match the
mutually shared directory that was created. In the figure below, for example, the
directory created and mapped was to the drive letter M:
WinScribe Windows Registry Setting

5. Once the setting has been changed, exit the registry and restart the Internet Author
interface for the changes to take effect.

Chapter 6—Configuring Study List Manager (SLM)
Chapter 6
Configuring Study List Manager (SLM)
Chapter 6
• Enabling SLM Service on page 130

• Changing SLM Port Assignment on page 130
• Configuring SLM on page 131
• Configuring HTTPS Support on page 132
• Managing SLM Database on page 134
Note
This section should be performed only on a system that has Application
Synchronization already installed and where SLM is intended to run.
Note
If the host computer is outside the domain, Hologic personnel must work with
the hospital IT team to install their certificates. If SLM Clients on multiple remote
systems need to be configured to communicate with a SLM Server using HTTPS
Anonymous Client, Hologic personnel must work with the hospital IT team to
ensure that certificates are imported to each computer (client and server). Follow
steps 4 to 15 in section Configuring HTTPS Support on page 132.
Note
SLM logs can be found at E:/HologicAppSync/StudyListManager/Logs.
Configuration Location Guidelines for SLM:

• SecurView must be at version 8.3 or later and MultiView must be at version 4.0 or
later in order to use SLM.
• For the SecurView multiworkstation configuration, SLM should be configured on the
SecurView Manager.
• For SecurView Standalone with MultiView, SLM should be configured on the
SecurView system.
Note
When the SLM Server is being configured on a computer where Application
Synchronization is not being used with connected applications (e.g., SecurView
Manager), install Application Synchronization without configuring any
application type components (be sure to deselect any preselected application
types, such as SecurView).

6.1 Enabling SLM Service

2. Select Start. Right-click This PC and select Manage.
3. In Server Manager > Services, select Study List Manager.
4. Change Startup type to Automatic. This will allow the service to start automatically after
each restart.
5. Select Apply and then select Start.
6. Select OK to close the Study List Manager Properties (Local Computer) window.
6.2 Changing SLM Port Assignment

1. Navigate to the folder where Application Synchronization SLM Server is installed (on
SecurView the path is E:\HologicAppSync\Study List Manager\Open Port ).
2. Start OpenPortGUI.
3. Enter the Port number for SLM for any or all port configurations.
The default values of the Port numbers are:
• 4697 (WindowsAuth)
• 4698 (HTTPS)
• 4699 (No Security)

4. Select the corresponding buttons as required to change the port or ports. This will change
the default ports and open Windows Firewall exceptions.
6.3 Configuring SLM

• To configure SLM on SecurView, refer to Chapter 8 of the SecurView DX/RT
Workstation User Guide.
• To configure SLM on MultiView, refer to Chapter 2 of the MultiView Multimodality
User Guide.

6.4 Configuring HTTPS Support

Note
HTTPS Support needs to be configured only when HTTPS Anonymous Client
security settings are selected on SecurView or MultiView.
If the host computer is in a domain:

2. Press Windows + [R] , then enter MMC in the Run dialog and select OK. The
Console 1 –(Console Root) window opens.
3. Select File > Add/Remove Snap-in.
4. Select Certificates from the Add or Remove Snap-ins window and select Add.
5. Select Computer Account from the Certificates Snap-in window and select Next.
6. Keep the default settings in the Select Computer window. Select Finish and then select
OK.
7. From the Console Root window, select the Certificates (Local Computer) node.
8. Select the Personal node and select Certificates.
9. Double-click the certificate issued to {machinename}.{domain}.

10. In the Certificate dialog, select the Details tab.
11. Select Thumbprint and copy the values of Thumbprint that display in the bottom of the
screen.
12. Open Notepad on your computer and paste the values of Thumbprint.
13. In Notepad, press [Ctrl] + [H]. Enter one space (by pressing the Space bar one time) in the
Find What field, and select Replace All. This removes spaces between the characters.
14. Press Windows + [R] , then enter CMD in the Run dialog.

15. In the Command window, type the command:

netsh http add sslcert ipport=0.0.0.0:4698 certhash=?(thumbprint from
Certificate Store) appid={62ab33a0-3078-4a3c-a9d2-1dc9424b109f}
In the above example:
• 0.0.0.0 - is the IP address of the server
• 4698 - is the port
• (thumbprint from Certificate Store)- is the certificate name. The certificate
name is unique for each computer.
16. Replace (thumbprint from Certificate Store) with the value from Thumbprint in
Notepad. Press [Enter].
Note
If you get the error "The parameter is incorrect" from the Command window,
remove the question mark character ‘?’ that appears after certhash=.
Note
Replace the port number if the default port is not being used.
Note
For SecurView, the server address must match the certificate name, e.g.,
{machinename}.{domain}.
6.5 Managing SLM Database

To delete entries received from a SLM client workstation:
1. Press Windows + [R] and type CMD in the Run dialog.
2. Type the following in the Command window: E > CD e:\HologicAppSync\Study List
Manager > DeleteWorkstationStudies.exe WorkstationName
In the above example, WorkstationName is the name of the SLM Client Workstation.
To reset to an empty database:
1. Navigate to the folder where Application Synchronization SLM Server is installed (on
SecurView the path is E:\HologicAppSync\Study List Manager).
2. Rename slm.sdf (database file) to slm.sdf.old.
3. Copy empty_slm.sdf to slm.sdf.

Chapter 7—Service Procedures
Chapter 7
Service Procedures
Chapter 7
• Modifying Application Synchronization on page 135

• Uninstalling Application Synchronization on page 136
• Setting a Windows User to Administrator on page 136
• Adding Users on a Windows 7 Computer on page 137
• Configuring the SecurView Keypad on page 137
• Using Windows File Sharing and Drive Mapping on page 138
• Troubleshooting Application Synchronization on page 140
• Install/Uninstall Separate Proxy Application on page 143
• Configuring and Troubleshooting Proxy Applications on page 145
7.1 Modifying Application Synchronization

This section should be performed only on a system that has Application Synchronization
already installed. The installer’s Modify mode can be used to add or remove application
types. Configuration is preserved when modifying Application Synchronization.
However, it is recommended to backup the Application Synchronization configurations
using the Export menu. Connected application configurations are preserved for
application types that remain selected after Modify. Configurations are deleted for
application types that are removed during Modify.
If error message boxes are displayed during modification of the Application
Synchronization software, take note of the error and report it to Hologic Technical
Support.
2. Select Start and type ‘Control Panel’ in the search bar. Select Control Panel and then
select Programs > Programs and Features.
Note
In the Control Panel, make sure the View by: button is set to Category.
3. Select Application Synchronization from the list and select Change. The
InstallShield window appears.
4. Select Modify and then select Next.
5. In the Installation Components window, select/deselect the installation components
that are to be added or removed. Select Next.
Note
The SecurView or MultiView application is required. SecurView is selected by
default when Application Synchronization is installed on a SecurView
workstation.

6. If a connected application with multiple versions available for install is selected, a

‘Select Version’ dialog will appear. Select the correct version to be installed and select
Next. Perform this step for all similar dialogs that appear.
7. If a dialog is presented that states, ‘XXXXXX has been selected for installation. It is a
proxy adapter and requires the installation of a separate install package’, select OK.
Note
Proxy adapters have a separate installation package that will need to be installed
after completing the Application Synchronization installation. For instructions, see
Install/Uninstall Separate Proxy Application on page 143.
8. If a dialog is presented that states, ‘XXXXXX is being uninstalled. It is a proxy

adapter and requires the uninstall of a separate package’, select OK.
Note
Proxy adapters have a separate installation package that will need to be
uninstalled after completing the Application Synchronization installation. For
instructions, see Install/Uninstall Separate Proxy Application on page 143.
9. Select ‘Yes, I want to restart my computer now.’ Select Finish. The system will
restart.
7.2 Uninstalling Application Synchronization

To uninstall Application Synchronization, see the instructions on how to uninstall
Application Synchronization in Upgrading Application Synchronization on page 16.
7.3 Setting a Windows User to Administrator

This section should be performed only as directed for specific non-Hologic TPAs.
1. On the computer where Application Synchronization is installed, log into Windows
as Administrator.
2. Select Start and type ‘Control Panel’ in the search bar. Select Control Panel and select
User Accounts > Manage User Accounts.
3. Highlight the user that starts Application Synchronization, and then select
Properties.
4. Select the Group Membership tab and then select Administrator.
5. Select Apply, then OK.
6. Select OK again, then close the User Accounts window.

7.4 Adding Users on a Windows 10 Computer

This section should be performed only if Application Synchronization is installed on a
non-Hologic Windows 10 computer and Windows user accounts other than
Administrator or SCR are used to configure Application Synchronization.
2. Select Start. Right-click This PC and select Manage. The Computer Management
window appears.
3. Select Local Users and Groups and open the Users folder.
4. Double-click the user name you wish to add. The Properties window appears.
5. Select the Member Of tab and select Add. The Select Groups window appears.
6. Enter Power Users in the Enter the object names to select (examples): field.
7. Select Check Names.
8. Select OK to save changes.
7.5 Configuring the SecurView Keypad

You should use the current SecurView keypad in game controller mode when
Application Synchronization is installed on SecurView and the third-party application is
running on the SecurView workstation. You can switch to the game controller mode
referencing the instructions found in the SecurView DX/RT Workstation Installation &
Service Manual.
The current keypads began shipping in March 2007 and can be distinguished by the
scroll wheel at the top above the trackball.
Using of the older version of the SecurView keypad or the current keypad in keyboard
mode may interfere with the third-party application because it behaves like a standard
keyboard.
In the event the third-party application running on SecurView has the focus, using the
old keypad may result in extra characters added to selected text input fields. To avoid
such interference, switch focus to the SecurView application prior to using the old
keypad. The customer can also purchase the current SecurView keypad to eliminate this
potential risk.

7.6 Using Windows File Sharing and Drive Mapping

When installing a XML file sharing application, it may be required to use Windows file
sharing and drive mapping to allow two computers to share a common directory. If it is
possible, it is recommended to have this drive shared from the Application
Synchronization computer rather than the TPA workstation and mapped on the
computer where the connected application is installed. The following instructions are a
guideline for setting up this scenario.
Note
Hologic recommends that the Application Synchronization computer host the
shared drive. When Application Synchronization starts up, it needs the shared
directory to be available to post its File System Watcher. If the shared directory is
on another computer, Application Synchronization’s startup will be delayed until
Windows maps the drive letter. This is a very precarious state that is to be avoided.
Application Synchronization will terminate if Windows fails to map the drive.
7.6.1 Configuring the Application Synchronization Computer for File and

Printer Sharing
For Windows 10
1. Log into the Application Synchronization computer as the Windows Administrator
user.
2. Open Windows File Explorer. Right-click Network and then select Properties. The
Network and Sharing Center window appears.
3. Select Ethernet. The Ethernet Status window appears.
4. Select Properties. The Ethernet Properties window appears.
5. If the ‘File and Printer Sharing for Microsoft Networks’ item is not available in the
This connection uses the following items: list, perform the following steps:
a. In the Ethernet Properties window, select Install.
b. Select Service and select Add.
c. Select File and Printer Sharing for Microsoft Networks and select OK.

To configure a Shared Directory:

1. In the Ethernet Properties window, select OK.
2. Create the desired shared folder in Windows File Explorer. This is the folder or
directory for Application Synchronization that has been agreed upon with the
third-party application representative for this connected application.
3. In Windows File Explorer, right-click on the directory to be shared (identified here as
XXXXXXXX) and select Properties. The XXXXXXXX Properties window appears.
4. Select the Sharing tab, select Advanced Sharing…, then select the Share this folder
option. Select Permissions.
5. If the Everyone group is not available perform the following steps:
a. In the Permissions for XXXXXXX window, select Add.
b. In the Select Users, Computers, or Groups window, enter Everyone in the Enter
the object names to select field.
c. Select OK.
6. Select the Everyone group. Make sure all check boxes are selected for the Allow
column.
7. In the Permissions for XXXXXXX window, select OK.
8. In the XXXXXXXX Properties window, select OK.
To map a Shared Drive from Third-Party Application Computer:

1. On the Third-Party Application computer, open Windows File Explorer. Then
right-click This PC.
2. Select Map Network Drive…
3. You may be prompted to enter a Windows user and password for the Application
Synchronization computer that has access to the mapped resource.
Note
When mapping a shared drive from the Third-Party Application’s computer, a
Windows user account and password for the Application Synchronization
computer may be required. If the Application Synchronization is installed on
SecurView, it is recommended that you use either the Windows user customer
password, or follow the instructions in the SecurView DX/RT Workstation
Installation & Service Manual for increasing security on the SCR user account to
add a password to the Windows user SCR.

4. In the Map Network Drive window, select an unused drive letter in the Drive
drop-down list. In the Folder drop-down list, enter the path of the network share
using the following entries as a guide:
Network Share Path: \\[Computer Name]\[Share Name]
Example: \\DWS01\MySharedFolder
Or, select Browse and select a network computer or server and then a shared folder.
5. Select the Reconnect at sign-in check box, and select Finish. The drive should now
be mapped. The third-party application must be configured with this new drive
letter.
6. Log into Windows as the designated Windows user on the Application
Synchronization computer.
7. Make sure that both computers have proper permissions by copying files manually
into the shared folder.
8. Remove these test files and continue the installation process.
7.7 Troubleshooting Application Synchronization

Use the following troubleshooting procedure if Application Synchronization is installed
on SecurView, and the ‘Configure’ button on SecurView does not launch the Application
Synchronization Configuration Interface.
To ensure SecurView is configured correctly:
1. Log into the SecurView application as the service user.
2. Select the Settings tab.

3. In the group Configure Synchronization Interface (group name varies in older
SecurView versions) ensure the following:
a. Synchronization is On.
b. The ‘Application Synchronization’ is configured with the IP address of this
SecurView computer.
c. The Port is set to 5100.
4. Select the Configure button again. If the Application Synchronization Configuration
Interface window fails to open, proceed to the next section.
Note
To ensure that MultiView is configured correctly, refer to MultiView or Aegis on
page 104.

To ensure Application Synchronization is running:

Perform steps 1–4 only if Application Synchronization is installed on the SecurView
computer. Steps 5–7 can be used for troubleshooting regardless of where Application
Synchronization is installed.
1. Log into the SecurView application as the service user.
2. Select the Exit to Windows tab.
3. Select OK to confirm.
4. On the desktop, double-click the tbon (toolbar on) icon. The Windows toolbar
appears.
5. If Application Synchronization is running, an icon will be displayed in the
notification area. For more information, see Notification Area Icon on page 11.
6. If the Application Synchronization software is not running, attempt to start it by
double-clicking the Application Synchronization icon on the desktop. If after
attempting to start Application Synchronization, it immediately exits or the
messaging service fails to start, one of the following problems may exist:
• One of the requirements for a connected application is not being satisfied. Check
the installation instructions for the installed application types in Application Types
on page 69.
• Application Synchronization is not configured correctly. If Application
Synchronization is running but stopped, right-click the icon and select
Configure. Configure/check the settings for Application Synchronization and/or
the connected applications. Make any necessary changes and try to start
Application Synchronization again using the Start button.
7. If the Application Synchronization software continues to fail to start, use the View
Log File page of the Configuration Interface to view the startup failure.
All logging levels, including Debug, are included in the Application Synchronization
log file by default. If you cannot determine the reason for failure or corrective
measures, call Hologic Technical Support for assistance.

To get Application Synchronization logs:

Perform steps 1–3 only if Application Synchronization is installed on the SecurView
computer. Steps 4–8 are general instructions that you can use to get Application
Synchronization logs.
Note
If Application Synchronization is installed on a non-SecurView computer, the path
to HologicAppSync\Service in step 4 and step 8 will be different. Use your best
judgment in locating and getting these logs.
Note
Application Synchronization log files can be 21 MB. Up to 21 files at 1 MB each are
maintained.
1. If SecurView is running, log into the SecurView application as the service user.
2. Select the Exit to Windows tab.
3. Select OK to confirm.
4. Display the Computer window by pressing Windows + [E].
5. Navigate to E:\HologicAppSync\Service.
6. In the Service directory, double-click getlogs.bat. A command window opens.
7. At the prompt to continue, press [C] and [Enter]. Log files and application folders
will be automatically packaged into a ZIP format.
8. When the command window prompts you, press any key to exit the command
window.
9. The created ZIP package can be found in the E:\HologicAppSync\Service folder as
ASlogfiles.zip.
To manually get Application Synchronization logs:
1. Display the Computer window by opening Windows File Explorer.
2. Navigate to the C:\ root directory.
3. Create a new folder and name it AppSyncLogs.
4. Copy the following folders and files to the C:\AppSyncLogs folder.
E:\HologicAppSync\Synchronizer\Logs
E:\SecurView\XAppSettings.xml
E:\SecurView\Log\XAPPINTERFACE.log
E:\HologicASProxy\ (exists only if a proxy application is installed on SecurView
along with Application Synchronization)
Note
If Application Synchronization is installed on a non-SecurView computer, the path
to the log files in \HologicAppSync\Synchronizer\Logs and \HologicASProxy
will be different. Use your best judgment in locating and getting these logs.

5. Copy the Devices.hlx file to the C:\AppSyncLogs folder. You can find this file in the
following directory:
C:\ProgramData\Hologic\AppSync\Configuration\Devices.hlx
6. In Windows Explorer, right-click the C:\AppSyncLogs folder, point to Send To…,
and then select Compressed (zipped) Folder. A file will be created named
AppSyncLogs.zip. This is the file you will need to send for debugging issues.
7. Delete the following folder and zip file once you have sent the logs to the appropriate
person (for example, Hologic Technical Support or Engineering):
C:\AppSyncLogs
C:\AppSyncLogs.zip
7.8 Install/Uninstall Separate Proxy Application

To Install the Proxy Application
Some TPAs (Hologic Proxy Partner, MammaSoft, and MedOutlook RIS) depend on an
intermediary application called a Proxy application for communicating with Application
Synchronization, which is contained on the Application Synchronization installation
disk. This executable must be installed on the same computer where the TPA software is
installed. To install the Proxy application, follow the steps below.
Note
If the Proxy application is being installed on a computer other than Application
Synchronization, the .NET Framework 3.5 SP1 must be confirmed and/or installed
manually before continuing. To check this, confirm that the following folder exists:
C:\WINDOWS\Microsoft.NET\Framework\v3.5
1. Complete the Application Synchronization installation first.

2. Log into the system containing the TPA software as any user with Administrator
rights.
3. To install Proxy application on the same computer as Application Synchronization:
Navigate to C:\AppSyncInstaller\HologicASProxy\xxxxInstallShield (xxxx refers to
the name of the Proxy application type e.g., HologicASProxyInstallShield,
MammaSoftInstallShield, or MedBrokerInstallShield).
To install Proxy application on a different computer:
Insert the Application Synchronization disk and navigate to the following directory:
\AppSyncFullInstallation\AppSyncInstaller\HologicASProxy\xxxxInstallShield
(xxxx refers to the name of the Proxy application type).
4. Double-click setup.exe.

5. In the Welcome dialog, select Next.

6. If the Proxy Application Installer is run on a non-SecurView system, an Installation
Path dialog will appear. Enter the appropriate install path or leave the default and
select Next.
7. In the Ready to Install dialog, select Install.
8. If the Proxy Application Installer is run on a system with a detected Application
Synchronization installation, a ‘Local Application Synchronization installation
detected’ prompt will appear. If the Proxy application will be communicating with
the detected installation, select Yes. Otherwise, select No.
Note
The Adapter Name, IP address, and port entered into the Adapter Configuration
Tool in the following step must match the settings configured for the TPA in the
Application Synchronization Configuration Interface.
9. If the Proxy Application Installer is run on a system without a detected Application

Synchronization installation or ‘No’ was selected in the previous step, a Hologic
Adapter Configuration dialog is displayed. Note that default values have been set to
match the default values for the Application Synchronization software. Provide an IP
address for the computer where the Hologic Application Synchronization software is
installed. The other values normally do not need to be altered. Select Save.
10. In the Finish dialog, select Yes, I want to restart my computer now and then select
Finish.
11. The system will restart.
Upon completion of these instructions, the TPA representative will be able to
configure the TPA to communicate with the Proxy application. The Proxy application
is what will communicate directly with Application Synchronization.
See Configuring and Troubleshooting Proxy Applications on page 145 if you experience
communication issues between Application Synchronization and the Proxy
application.
To Uninstall the Proxy Application
1. Log into the computer where Proxy application is installed as any user with
Administrator rights.
2. Select Start and type ‘Control Panel’ in the search bar. Select Control Panel and then
select Programs and Features.
3. Select the Proxy application and select Uninstall.
4. Select Yes to confirm the uninstall.
5. In the InstallShield Wizard Complete window, select Finish to restart the computer.

7.9 Configuring and Troubleshooting Proxy Applications

There are three main areas of focus required to ensure successful communication
between a TPA that uses a Proxy application and Application Synchronization.
1. Application Synchronization settings for the TPA
2. Proxy application settings for the AS Adapter
3. TPA settings
Items 1 and 2 above are within the control of Hologic and item 3 is the responsibility of
the TPA representative. The TPA communicates with Application Synchronization via a
Hologic-provided Proxy application. Application Synchronization must be configured
with the Application Alias, IP address, and port of the Proxy application. The Proxy
application must be configured with its own Adapter Name (Application Alias), IP
address, and port. The Proxy application must also be configured with the Application
Synchronization Name, IP address, and port. It is important to note that if the settings do
not match, the connection will not be made.
Note
Use the Application Tester described in Application Tester on page 30 to test
receiving messages from the connected application that is using a Proxy
application.
Note
By default the Hologic Adapter Configuration window for Proxy application
configuration will display a MAC address in the Adapter IP field instead of the IP
address of the Proxy application. You must enter the correct Adapter IP address in
this field and select Save.

Application Alias Matches (Case Sensitive)
IP Address and Port Number Match

7.9.1 Troubleshooting Proxy Application to Application Synchronization

Communication
If the Proxy application is having trouble communicating with Application
Synchronization, perform the following steps:
1. Check connectivity between the Application Synchronization system and the
(possibly separate) system where the Proxy application is installed.
a. Log into Windows as a user with administrator rights.
b. Press Windows + [R].
c. In the Run dialog, enter cmd and press [Enter].
d. In the command window that appears, enter ping <system ip> where <system
ip> is the IP address of the system where the Proxy application is installed.
e. If a timeout is reported and no reply received, then a connectivity problem has
been identified.
2. Record the TPA’s communication settings configured in the Application
Synchronization Configuration Interface.
a. Access the Configuration Interface.
b. Navigate to the Application Management Application List.
c. Within the list of connected applications, locate and select the item that
represents the TPA that is using a Proxy application.
d. Select Edit.
e. Select the Comm tab and record the Application Alias, IP address, and port that
have been configured.
f. The Application Alias, IP address, and port recorded in the steps above should
match what is configured in the Hologic Adapter Configuration for the Proxy
application.
3. Confirm that the recorded IP address matches the actual system IP address where the
Proxy application is installed.

4. Configure the Proxy application with settings gathered in previous steps.

a. Log into the system where the Proxy application is installed as a user with
Administrator rights.
b. Navigate to the directory where the Proxy application is installed.
c. Double-click AdapterConfigTool.exe.
d. Enter the recorded Application Alias, IP address, and port in the Adapter
Configuration section of the Hologic Adapter Configuration user interface.
e. Enter the IP address of the system where Application Synchronization is
installed into the AppSync IP field in the AppSync Configuration section of the
Hologic Adapter Configuration user interface. The AppSync Name and port
fields should be filled out with defaults.
f. Select Save.
g. Close all open windows.
Test connectivity between the TPA and Application Synchronization.

App Synch v4.3 Install - Service Manual (MAN-05940) English Rev - 002 10-2019

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

App Synch v4.3 Install - Service Manual (MAN-05940) English Rev - 002 10-2019

Uploaded by

Copyright:

Available Formats

Application

Installation and Service Manual

List of Tables __________________________________________________________________ ix

Chapter 1 Introduction __________________________________________________________ 1

Chapter 2 Application Synchronization Description ________________________________ 5

Chapter 3 Installing Application Synchronization _________________________________ 13

Chapter 4 Configuring Application Synchronization _______________________________ 21

MAN-05940 Revision 002 v

4.3.9 Finish ........................................................................................................................................................... 47

Chapter 5 Application Types ____________________________________________________ 63

vi MAN-05940 Revision 002

5.4.35 RadNet VDI .............................................................................................................................................. 117

Chapter 6 Configuring Study List Manager (SLM) ________________________________ 129

Chapter 7 Service Procedures ___________________________________________________ 135

MAN-05940 Revision 002 vii

Table 1: Third-Party Applications ................................................................................................................................... 9

MAN-05940 Revision 002 ix

1.1 About This Manual

MAN-05940 Revision 002 Page 1

1.2 Document Conventions

Page 2 MAN-05940 Revision 002

1.3 Terms and Definitions

Comm Port Communication port used for serial communications.

MAN-05940 Revision 002 Page 3

• Application Synchronization Overview on page 5

2.1 Application Synchronization Overview

2.1.1 Installation location guidelines for Hologic products and TPAs:

AS and TPA on SecurView Workstation

MAN-05940 Revision 002 Page 5

SecurView and AS on Workstation, TPA on a Separate Computer

SecurView with AS and TPA on a Separate Computer

Page 6 MAN-05940 Revision 002

AS and MultiView MM on SecurView Workstation

MultiView and AS on Workstation, TPA on a Separate Computer

MAN-05940 Revision 002 Page 7

MultiView with AS and TPA on a Separate Computer

2.2 Third-Party Applications

Page 8 MAN-05940 Revision 002

Table 1: Third-Party Applications

MAN-05940 Revision 002 Page 9

Third-Party Applications Partner Type

Page 10 MAN-05940 Revision 002

2.3 Notification Area Icon

system starts up. There will be an Application Synchronization icon displayed in

MAN-05940 Revision 002 Page 11

• Required Tools and Materials on page 13

3.1 Required Tools and Materials

3.2 Pre-installation Checklist

MAN-05940 Revision 002 Page 13

• Application Synchronization 4.3 is compatible with MultiView 4.1 or later.

Page 14 MAN-05940 Revision 002

3.3 Recording Application Configurations

3.4 Backing Up and Configuring Licenses on SecurView

MAN-05940 Revision 002 Page 15

3.5 Checking the System for Active Network Connections

3.6 Upgrading Application Synchronization

Page 16 MAN-05940 Revision 002

3.7 Installing Application Synchronization

MAN-05940 Revision 002 Page 17

1. Log into Windows as Administrator.

Figure 1: The Command Window

3. In the Application Synchronization InstallShield Wizard window, select Next.

Page 18 MAN-05940 Revision 002