Table of Contents
Advertisement
Quick Links
Advertisement
Table of Contents
Summary of Contents for Numa NumaLink-3.0
- Page 1 NumaLink-3.0™ Version 2 Users Guide and Service Manual April 2004...
- Page 2 TRADEMARKS Numa and the Numa logo are registered trademarks of Numa Inc. NumaStation, NumaLink-3.0 and NumaStore are trademarks of Numa, Inc. Microsoft, Windows 2000 and Windows XP are registered trademarks or trademarks of Microsoft Corporation. pcAnywhere is a trademark of Symantec Corporation.
-
Page 3: Table Of Contents
3. Product Overview... 8 3.1 A T ... 9 YPICAL RANSLATION 4. Configuration... 11 4.1 G ... 11 ENERAL 4.1.1 NumaLInk-3.0 DICOM Application Entity Information ... 12 4.2 T ... 13 RANSLATIONS 4.2.1 Customization... 15 4.2.2 DICOM... 15 4.3 S ... 17 TATUS 5. -
Page 4: Introduction
DICOM 3.0 compliant applications (DICOM by Merge). A translation type is defined as a translation from one specified OEM format to another. NumaLink-3.0 will support one or more translation types, as specified in a customer-modifiable configuration. Data paths are specified for each defined translation type;... -
Page 5: Installation And Getting Started
2. Installation and Getting Started 2.1 Hardware Your NumaLink-3.0 system hardware should be installed by an authorized service engineer. Please contact Numa for more information. Typical hardware for a NumaLink-3.0 system is shown in Figure 1. Figure 1 – NumaLink-3.0 Hardware Configuration... -
Page 6: Startup
2. The monitor is turned on. 3. The surge suppressor power strip is turned on. To start the NumaLink-3.0 system, locate the power button on the front of the machine and press it. The computer will begin its boot sequence. -
Page 7: Software
C:\Program Files\Numa\NumaLink 2.2.2 License A license, provided by Numa either as a text file or in hardcopy, is required to run NumaLink-3.0. An example license is shown in Error! Reference source not found.. The license provided by Numa must be placed in the following file: <system-disk>\Program Files\Numa\Licenses\NumaLink-3.0.lic... -
Page 8: Removing Numalink-3.0
Numa license ends If an appropriate license cannot be found, a message is displayed as shown in Figure 3. Contact Numa immediately if you have any problems with your NumaLink-3.0 licenses. Figure 3 – License Error Message NLF_NoLicense: No valid NumaLink-3.0 license found (5) 2.2.3 Removing NumaLink-3.0... -
Page 9: Product Overview
3. Product Overview In general, NumaLink-3.0 discovers nuclear medicine image files in one OEM format that are placed in a configured input directory, and translates them to image files in another OEM format in a configured output directory. While performing this translation, it makes use of various directories in a work directory tree. -
Page 10: A Typical Translation
As a rule, NumaLink-3.0 does not specify how the image files get to the input directory, or what happens to them after they are written to the output directory. (In many cases, Numa can provide utilities that facilitate or automate the transfer of files from and to various OEM systems;... - Page 11 2. If one or more input files are found, NumaLink-3.0 schedules a file stability check, sleeps for a file stability delay period and proceeds to step 3. 3. If the input files are stable, NumaLink-3.0 proceeds to step 4; if not, it schedules a directory check, then sleeps and goes to step 1.
-
Page 12: Configuration
To start the NumaLink-3.0 GUI, double-click on the following executable image: <system-disk>\Program Files\Numa\NumaLink\NumaLink.exe 4.1 General Figure 6 shows the NumaLink-3.0 Graphic User Interface (GUI) with its General configuration tab. Each configuration item is described in Table 4-1 – General Configuration Settings Figure 6 – General Configuration Tab Table 4-1 –... -
Page 13: Numalink-3.0 Dicom Application Entity Information
Error! Reference source not found.). This file is best left under control of Config. File the NumaLink-3.0 GUI; in some circumstances, you may need to modify it manually to access features that are not yet supported by the GUI (see section 7). -
Page 14: Translations
AE_Title=NumaLink_3_0 ListenPort=104 (In a future release, these modifications will be supported directly in the NumaLink-3.0 GUI.) (DICOM by Merge) 4.2 Translations Figure 7 shows the Translations tab, through which you can add, delete and modify translation definitions. - Page 15 Output path translation will be written to this directory. (See also the DICOM button, below.) Directory path of a work directory; this directory is used by NumaLink-3.0 Work path while performing work for this translation. NumaLink-3.0™ Users Guide and Service Manual...
-
Page 16: Customization
If DICOM AE information is provided for an output format, the translation includes a DICOM request to store the translated data to one or more specified AEs. Each DICOM configuration item is described in Table 4-3. NumaLink-3.0™ Users Guide and Service Manual Page 15 of 33... - Page 17 Copy to New Copy the selected AE entry to a new entry Delete Delete the selected AE entry Exit the dialog and apply any changes to the translation NumaLink-3.0™ Users Guide and Service Manual (NT, 2000, XP) C:\WINNT\system32\drivers\etc\Hosts (95, 98) C:\Windows\Hosts...
-
Page 18: Status
Error! Reference source not found. shows the Status tab, which displays the current status of the NumaLink-3.0 translator. The Status tab reflects the latest entries in the NumaLink-3.0 audit log. The NumaLink-3.0 GUI switches to the Status tab automatically when you start the translator. - Page 19 NumaLink-3.0™ Users Guide and Service Manual The Clear Status Window button clears existing messages form the Status window; it does not affect the audit log. Page 18 of 33...
-
Page 20: Technical Support
2. Messages from all sessions are appended into log files that, by default, are stored in C:\Program Files\Numa\Logs The full paths to the log files are displayed in the General tab of the NumaLink-3.0 GUI, as shown in section 4.1. -
Page 21: Troubleshooting
Before placing a service call to Numa, please run through the following troubleshooting checklist and FAQ. 1. Are all cables plugged into the appropriate ports? (See section 2.1.1.) 2. Are the computers and monitors of the NumaLink-3.0 system, the source system and the destination system turned on? (See section 2.1.2. Page 20 of 33... -
Page 22: Frequently Asked Questions
3. If the systems are powered on, have you rebooted the NumaLink-3.0 system, the source system, and the destination system? (See section 2.1.3.) 4. Have you properly transferred a file from the source system? (See sections 5.4 and 6.) 5.4 Frequently Asked Questions What types of data can I send through my NumaLink-3.0 system? - Page 23 NumaLink-3.0™ Users Guide and Service Manual How do I know that a study I sent has been translated? You can check the NumaLink-3.0 status window. Figure 13 shows a typical status window after a successful translation. Figure 13 – Example of Successful Translation A study that I sent did not show up on the destination system.
- Page 24 Reboot the NumaLink-3.0 computer. If the studies still do not come over, reboot the source and destination systems as well. Try to determine if the data comes over to the NumaLink-3.0 system, and also if it leaves the Numa system, but cannot be seen or processed at the destination. Check the following: •...
-
Page 25: Oem Setup Information
Left click on “Transfer Native Pegasys Files”. This will open the patient selection utility. d. Select the patients you wish to transfer and click the “Proceed” button. 2. Numa Pull transfers the files to a local directory on the NumaLink-3.0 system; this directory is configured as a translation input directory in NumaLink-3.0. -
Page 26: Ge Starcam
1. Completing a translation, NumaLink-3.0 writes Pegasys files to a configured output directory. 2. AutoFTP transfers the Pegasys files to a local directory on the Pegasys system. 3. AutoFTP shells a procedure on the Pegasys to add the transferred file to the Pegasys database. -
Page 27: Siemens Icon
4. When you are ready to transfer the patients to the Numa computer, click on the Utilities menu and select “Copy”. 5. Select the volume corresponding to the NumaLink-3.0 computer (usually “sendpatientsto…) and click the “Copy” button. You should see a file transfer status indicator appear. When this closes, all patient files should be on the Numa computer. -
Page 28: Command Line Interface And Configuration File
7. Command Line Interface and Configuration File The NumaLink-3.0 translator can be run without the GUI, by making use of its command line interface, which is augmented by an editable configuration file. In this manner, a specific translation can be scripted to execute in response to another system event. -
Page 29: Configuration File
Comment – everything to the right on the same line is ignored. ; (semicolon) ! (exclamation) The semicolon delimiter may be used freely to mark comments; the exclamation delimiter is reserved for use by Numa, Inc. NumaLink-3.0™ Users Guide and Service Manual –v is specified. –b –q... -
Page 30: The Translate Directive
Output file path – specifies the directory to which the translator writes output-path its translation results. The process must have write and file create access to this directory. NumaLink-3.0™ Users Guide and Service Manual work-path [ stability-delay ] Page 29 of 33... - Page 31 For each translation type, the data flows from the specified input to the specified output path. There is no limit on the number of translation types that can be specified in a configuration file. NumaLink-3.0™ Users Guide and Service Manual arguments, it is assumed that a trailing path...
-
Page 32: The Out_Remote_Ae Directive
If a transfer syntax is not provided, this argument must be "", and the transfer syntax defaults to implicit little endian. The following is an example of a valid configuration file including an out_remote_ae directive: NumaLink-3.0™ Users Guide and Service Manual port { friendly-name | "" }... -
Page 33: The Control_* Directives
NumaLink-3.0™ Users Guide and Service Manual ; nmtrans_config.dat – sample configuration file translate AtoD ADAC c:\trn\ADC_in DICOM c:\trn\DCM_out c:\trn\tran1 out_remote_ae numastore remnode "" "" This configuration file will invoke a translation of input files in ADAC Pegasys format to DICOM format, followed by a request to remote AE "numastore"...
Need help?
Do you have a question about the NumaLink-3.0 and is the answer not in the manual?
Questions and answers