Leica BIOSYSTEMS Aperio GT 450, Руководство администратора

Страница: 20 / 48

Aperio GT 450 IT Manager and Lab Administrator Guide, Revision E © Leica Biosystems Imaging, Inc. 2022 20
Chapter 2: Aperio GT 450 Network Architecture
Data Type Description Port
Image Data The Scanner sends DICOM image data to the DICOM Converter. The data is sent using
TLS encryption.
Configure the communication between the scanner and the DICOM converter using the
Hostname and Port settings on the
Images configuration page.
TCP 2762
The DICOM Converter sends the image data (either as a converted SVS file, or as raw
DICOM data) to the Image File System on the DSR Server. The data is sent using SMB3
Encryption.
Configure the communication between the DICOM converter and the DSR using the File
Location setting on the
Images page.
UDP 137,
138
TCP 139,
445
Scanner
Configuration
Data
The scanner sends a call to the SAM DataServer to request configuration data. The
SAM DataServer returns the configuration data to the scanner. The data is sent using
TLS Encryption. Communication between the scanner and the SAM DataServer is
configured on the scanner. 44386
The SAM DataServer stores the configuration data on the SQL Server Database on the
SAM Server.
The SAM DataServer displays the configuration data through the SAM web page.
Time
Synchronization Timeclock synchronization between SAM and Multiple Scanners is maintained using
network time protocol. UDP 123
Image Metadata The Scanner sends Image Metadata to the SAM DataServer. The data is sent using TLS
encryption. Communication between the scanner and the SAM DataServer is configured
on the scanner. 44386
The SAM DataServer sends image metadata to the Aperio eSlide Manager DataServer
located on the DSR. The data is sent using TLS encryption.
Configure the communication between the SAM DataServer and the scanner using the
Hostname and Port settings on the
DSR
page.
Messaging and
Event Data The scanner sends logs and event data to the Mirth Connect Server. No sensitive data
is transferred.
Configure the communication between the scanner and the Mirth Connect Server on the
Event Handling
configuration page.
6662,
6663
The Mirth Connect Server copies critical event and error data to the SAM DataServer
then the SAM DataServer sends this data to the SQL database. This is the data
reported out via the SAM Event Logs.
The SAM DataServer displays the event data through the SAM web page.
Mirth Connect Server processes the Log data and appends the Event Log, which resides
on the file system. The communication between Mirth and the Event Log is configured
within the Mirth Application setup. It is not accessible through SAM.
“Scanner Configuration Settings” on page 25 provides information on how to configure the various connections between
the components and services through the SAM interface.