Install and Verify Customer Imaging Options

• Send or “Push” images to another network device.

• Send or “Push” images to a DICOM Printer.

• Review image database on another device and retrieve or “Pull” selected images from that device (Query/Retrieve User).

• Send or “Push” images to a an image storage device and obtain confirmation that the images were archived (Storage Commitment).

• Obtain Patient Worklist Information from the Hospital HIS/RIS System.

• Store images on MOD media.

• Receive “Pushed” images from another network device.

• Allow another network device to review the image database and to retrieve or “Pull” selected images (Query/Retrieve Provider).

For each DICOM Service that the CT system is a User (except for storing images on MOD media), you must declare this device on the CT system using three menu selections. For some devices, you must declare not only the device, but each service (AE Title) that the device provides.

For example, you may need to declare a PACS System twice on the CT system: once as a destination to push images and, second, as destination that provides storage commitment capability after images have been pushed.

For each DICOM Service that the CT system is a Provider, you must declare the CT system on the network device that is using these services.

Information required to complete configuring a hospital DICOM network is provided by:

• The hospital network administrator (hostnames, IP Addresses)

• The DICOM Conformance Statement document (AE Titles, Port Numbers), provided with each DICOM compatible network device on the network.

Before setting up the CT scanner system on the hospital network, verify the following physical items are complete:

• Scanner console, monitor, keyboard, and mouse are installed and connected.

• CT system power is ON.

• Hospital Ethernet network RJ45 Class IV twisted pair cable is connected to the scanner console network receptacle.

• Hospital network connection is operational and is running 10baseT or 100baseT.

You need to gather network identity information to do the following tasks:

• Declare the CT system on the network

• Declare the DICOM remote hosts (PACS systems, archival devices, review workstations) on the CT system.

• Declare the DICOM Hospital HIS/RIS Interface devices (Mitra and others) on the CT system.

• Declare the DICOM on the CT System.

Ensure the following network identity information is available:

• From the Hospital Network Administrator:

  • Hostname (No more than 16 Characters).

  • Internet Protocol (IP) Address.

  • Subnet Net Mask IP Address (if applicable).

  • Broadcast Address (if applicable).

  • Network Protocol (DICOM for CT Systems)

• From the Remote Host Device DICOM Conformance Statement Document:

  • DICOM Application Entity Title or AE Title (DICOM service that remote host provides or uses).

  • DICOM Listening Port Number.

• From the HIS/RIS Interface Device DICOM Conformance Statement Document:

  • DICOM Application Entity Title or AE Title (DICOM Service that the HIS/RIS interface provides).

  • DICOM Listening Port Number.

• From the Printer DICOM Conformance Statement Document:

  • DICOM Application Entity Title or AE Title (DICOM service that remote host provides or uses).

  • DICOM Listening Port Number.

1. On the operator’s console, open a shell window.

2. Enter root as a superuser:

   At the prompt, type: su - ENTER

   At the password prompt: type the password; press ENTER

3. Change directory to scripts.

   Type: cd /user/g/scriptsENTER at the root prompt.

4. Launch the Install Utility:

   At the prompt, type: reconfigENTER

   The OC displays the Install Utility Window as shown in Figure 1.

   Figure 1. Install Utility Window

   

5. Enter the Configuration Routine:

   Click the CONFIG button.

   The OC displays the System Configuration - System Settings screen, as shown in Figure 2.

   Figure 2. System Settings Screen

   

This screen allows you to declare the CT system on a hospital network. Key information such as Host Name, IP Address, Net Mask (for CT systems on a subnet) must be obtained from the hospital network administrator.

1. Select the NETWORK button to display the Network Settings screen as shown in Figure 3.

   Figure 3. Networks Settings Screen

   

2. Enter the Suite Name.

   The Suite Name identifies this particular CT system as a part of a group of CT Systems in a suite configuration. This Suite Name appears on all image headers.

   The Suite Name must start with a letter, followed by three alphanumeric characters (total MUST be four characters long). The name of the OC interface is <Suite Name>_oc and the SBC interface is <Suite Name>_sbc.

3. Enter the hospital-provided Host Name.

   The Host Name identifies the network hostname and AE Title of the CT system.

   The Host Name:

   • MUST NOT be <Suite Name>_oc or <SUITE NAME>_OC

   • MUST NOT exceed 16 characters.

   • MUST only contain the following characters: A through Z, a through z, 0 through 9, - and _

4. Enter the hospital-provided IP Address.

5. Enter the hospital-provided Net Mask (if the CT system is on a subnet).

6. Enter the Broadcast Address

   The Broadcast Address should be the same as the IP Address, except for the bits of the host ID portion (last digit group) set to 1’s or 0’s, depending on the configuration of the network. The standard default is 1’s but older SunOS machines used 0’s.

   Example: If the IP Address is 192.100.9.17, the Broadcast Address should be 192.100.9.255 if the network is configured to use 1's to specify the broadcast address.

   If the network contains genesis-based scanners or other SunOS 3.5 or 4.1 computers, the Broadcast Address should be 192.100.9.0.

7. Enter the hospital-provided Default Gateway IP Address (if applicable). If the site network does not use a default gateway, leave the field blank.

8. Select NIS (Yellow Pages database) Advanced Option only if requested by the hospital network administrator as follows:

   • Select ADVANCED OPTIONS button on the Network Settings screen.

   • Select USE NIS? button.

   • Enter the hospital-provided Domain Name.

9. Record all the Network parameters in the Software Installation Procedures document, or on the worksheet in System Configuration Data Sheets.

1. Select ACCEPT on the System Configuration Screen.

   The system loads the application software, OS patches, and kernal changes, and configures the system on both the OC and the SBC.

   This loading process takes approximately 15 minutes. While the load is going on, the results are displayed in a shell window, which closes when the loading process is complete. All the window output is logged to a file named:

   /var/adm/install.log.YYYYMMDDWWWHHMMSS.

   (Where YYYYMMDDWWWHHMMSS is the Date/Time that the loading process was started.)

2. When the loading process and configuration changes are complete, the system displays a prompt to reboot. Click YES.

3. The system automatically logs in as ctuser after the reboot. Select OK on the Autostart Disabled popup message.

4. To startup Applications, in the console shell window, type: startupENTER.

1. On the OC, select the IMAGE WORKS icon.

2. Select NETWORK.

Use Advantage NET Protocol networks to communicate with older CT Systems (CT-HLA, CT/I Systems, and Workstations that support the Advantage NET protocol). Advantage NET Protocol does not offer full compatibility with LightSpeed DICOM formats.

Repeat the following procedure for each Advantage NET Remote Host device that the customer expects to have this CT system communicating with.

1. Select REMOTE HOSTS from the pull down menu. The system displays the Remote Host Parameter Screen as shown in Figure 4.

   Figure 4. Advantage Net Network Protocol Parameter Settings

   

2. Enter the hospital-provided Host name.

3. Enter the hospital-provided Network Address (IP Address).

4. Select ADVANTAGE NET as the Network Protocol.

   The system automatically removes the highlighting from the remaining parameter fields on the Remote Host parameter selection screen. These are dedicated DICOM protocol parameters and do not apply to Advantage NET type devices.

5. Select SAVE to store the parameter settings of the remote host.

Use DICOM protocol networks to communicate to DICOM devices such as CT/i, CT Synergy, DLX, MR Lx, and third party hosts.

Repeat the following procedure for each DICOM remote host device that the customer expects to have this CT system communicating with.

1. Select REMOTE HOSTS from the pull down menu. The system displays the Remote Host Parameter screen as shown in Figure 5.

   Figure 5. DICOM Network Setting Protocol Parameter Settings

   

2. Enter the hospital provided Host name.

3. Enter the hospital provided Network Address (IP Address).

4. Select DICOM as the Network Protocol.

   The system automatically highlights the remaining parameter fields on the Remote Host parameter selection screen. These are dedicated DICOM Protocol parameters.

5. Enter the TCP/IP Listening Port Number from the DICOM Conformance Statement provided with the device.

6. Enter the AE Title from the DICOM Conformance Statement provided with the device.

   Application Entity Titles (also known as ACR-Nema or Dicom Name) refer to the DICOM Network Services that a device provides to the CT System. For most devices, the AE Title is the same as the hostname (CT systems are equipped with this feature).

   However, some devices such as PACS systems may have separate AE Titles and port numbers for each of the services that the PACS system provides. In these cases, you must enter a separate remote host (same hostname and IP Address) for each of the independent AE Title Services that the host provides (one host as an image push-to destination, another host as a query/retrieve provider, and another host as a storage/commitment provider).

   Be sure to review the DICOM Conformance Statement for each device that will provide a remote host network service for the CT system (image push-to or store destination, Query/ Retrieve, and Storage Commitment) to ensure that each service is correctly configured.

7. Select the correct Archive Node choice for the device. The Archive Node selection field defines the ability of the remote host to act as a DICOM Storage/Commitment provider and indicate to the operator that a study/series/image was archived. Select:

   • AUTO to have the CT system automatically check to see if the designated remote host is a DICOM Storage/Commitment Provider.

   • YES if the device is the hospital designated DICOM Storage/Commitment Provider. During an Application Study Archive process, the local browser screen will indicate Archive Status = Y to the operator.

   • NO if the device is not a DICOM Storage/Commitment Provider.

8. Select the correct Access to local host: settings. These two selections allow you to selectively block the remote host from using the LightSpeed DICOM services as a provider (image push-to destination, and a Query/Retrieve provider).

   • Send Images? Set to YES if the customer wants the CT system to be able to have images pushed to the system from the applicable remote host. Set to NO if the customer wants to block an image push from the applicable remote host.

   • Query/retrieve images? Set to YES if the customer wants the remote host to be able to review the image database (query) and pull selected images from the database. Set to NO if the customer does not want the remote host to have this ability.

9. Select the correct Custom search? setting. This selection allows the CT scanner to selectively search through the remote host's image database when the operator is using remote browser screen to query the remote host. The search parameters that the CT system allows the customer to use are: last name contains, patient ID, exam number, accession number, and exam date.

   • Select ON if the device supports custom searches as part of the devices Query/Retrieve DICOM Provider service.

   • Select OFF if the device does not support custom searches.

10. Record all the remote host network parameters for each remote host in the Software Installation Procedures document.

11. Select SAVE to store the parameter settings of the remote host.