1. Manuals
  2. Brands
  3. SCHWIND Manuals
  4. Network Hardware
  5. MEDNET
  6. User manual

SCHWIND MEDNET User Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
USER MANUAL
Doc. V1.9.2.1 (2021-05-10)
Original Instruction for Use
MEDNET Manager V1.9.2
SCHWIND eye-tech-solutions GmbH
Mainparkstrasse 6-10 · D-63801 Kleinostheim

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the MEDNET and is the answer not in the manual?

Questions and answers

Summary of Contents for SCHWIND MEDNET

  • Page 1 USER MANUAL Doc. V1.9.2.1 (2021-05-10) Original Instruction for Use MEDNET Manager V1.9.2 SCHWIND eye-tech-solutions GmbH Mainparkstrasse 6-10 · D-63801 Kleinostheim...

  • Page 2: Table Of Contents

    Medical Network Statement ....................20 MANDATORY PREREQUISITES ....................21 Product Responsibilities – Overview ..................21 Process: Planning → Installation → First Operation..............22 Valid System Combinations with SCHWIND Medical Devices ............23 Network Characteristic, Requirement and Configuration ............24 4.4.1 Infrastructure Type: “Dedicated private LAN Network” ............25 4.4.2...
  • Page 3 Scenario 2: Generate PDF Files only .................74 10.1.3 Scenario 3: Printout on Printer in Clinic Network ..............75 10.1.4 Scenario 4: Printout on SCHWIND Printer within MEDNET Network ........76 10.2 Print-Setup: SCHWIND PanelPCs (Workstation, AMARIS PC) ............77 10.3 Print-Setup: MEDNET Print (SCHWIND PC or clinic PC) .............78 10.4...
  • Page 4 Negative status in Main View ..................108 12.2.2 Popup Notification ...................... 108 12.2.3 Diagnosis ......................... 109 12.2.4 MEDNET Manager: Processing takes much Time ............... 115 12.2.5 Logfile ........................115 12.3 Using fixed/static IP for Fileserver ..................116 12.4 Workstation – Diagnosis Database on Network ..............118 12.6...

  • Page 5: Pictogram Definition

    This symbol provides the user with useful or additional information. SCOPE OF USER MANUAL The purpose of the user manual is to familiarize operator(s) of the SCHWIND MEDNET with safety instructions, setup, handling, operation, and maintenance. The networking items are based on common network technology. This requires an IT-Admin (network responsible person) just to be familiar with basic network skills.

  • Page 6: General Information

    SCHWIND eye-tech-solutions offers a comprehensive warranty and service support program. Highly qualified representatives from our SERVICE and CUSTOMER SUPPORT departments are available to support you to solve operational questions. Notice the MEDNET responsibilities. This manual also includes a chapter on common network issues for consideration. Service Hotline...

  • Page 7: Declaration Of Manufacturer

    Delivery is accomplished by SCHWIND eye-tech-solutions or a distributor authorized by SCHWIND eye-tech-solutions; • The “MEDNET network compound” must be set up and operated in explicit accordance with the official MEDNET documentation. Abbreviations may induce hazard to the medical systems, patient and operator. See chapter “14 IEC 60601-1 3 Network FAQ”...

  • Page 8: Warranty

    Malfunctions not caused by improper use are repaired under warranty. Damage caused by abuse or improper use is not repaired under warranty. 4. The legal warranty applies only to parts that are replaced or repaired by SCHWIND eye-tech- solutions. Components contributed by the client are excluded from SCHWIND warranty (LAN cable, managed switch, …).

  • Page 9: License Agreement

    Quoting of product names is for information only and does not represent any trademark misuse. SCHWIND eye-tech-solutions is not liable for the performance or the use of these products. Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 9 of 135...

  • Page 10: Scope Of Delivery / Delivered Content

    User Manual General Information Scope of Delivery / Delivered Content MEDNET Package delivery is entirety annotated in the SCHWIND MEDNET packing list. Delivered components include: CAUTION All MEDNET devices are pre-configured by SCHWIND with factory settings for MEDNET. Do not alter the firmware version / configuration. Change is allowed when mentioned in a SCHWIND instruction only.

  • Page 11: Schwind Labelling

    User Manual General Information 1.10 SCHWIND Labelling The SCHWIND MEDNET components are labelled as follows: NAS server Router Galvanic LAN isolator (if available) Switch ** HW model of label position may differ due to product revisions. Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2...

  • Page 12: Hazards And Safety

    Medical Apparatus Book. (MEDNET is an add-on product for existing SCHWIND medical devices. They still can be used in its origin manner without the MEDNET functions as described in the regarding user manual of each medical device.) Service &...

  • Page 13: Virus Protection

    The PanelPC model AAEON Onyx 175 or Advantech must use an external galvanic LAN isolator. Never operate the system without this safety relevant part! This part is included in the MEDNET delivery. While the MEDNET is setting up, the service technician is responsible for proper galvanic LAN isolator installation.
  • Page 14 4. Put together the disassembled parts. Connect main cable. Power on AMARIS. Connect the (unconnected) LAN cable +MS-X3 behind the PanelPCs back side to LAN Port 1. Connect the MEDNET network LAN cable to the AMARIS LAN outlet. Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2...

  • Page 15: Dangers Resulting From Software Operation

    The corresponding chapters in the user manual(s) of the respective SCHWIND medical product(s) remain valid! Refer to this documentation. 2.11 Contraindications / Side Effects There are no known contraindications or side effects resulting from the use of the SCHWIND MEDNET. Regarding possible contraindications arising from the medical device(s) refer to the documentation of the respective medical device(s).

  • Page 16: Product Introduction

    MEDNET installation is realized very quickly and easily. A standardized installation procedure, together with SCHWIND or a Distributor provides fluent guidance for planning, installation and first startup. MEDNET is economic by providing a roundup set of features for best usability, clinical workflow optimization and easy use. Supreme advantages at a glance: •...
  • Page 17 User Manual Product Introduction Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 17 of 135...

  • Page 18: Intended Use & Reasonably Foreseeable Misuse

    MEDNET system running. Reasonably foreseeable misuse WARNING There are obvious possibilities for misuse of the MEDNET product. It must be ensured at all times not to modify or use the MEDNET product as followed: •...

  • Page 19: Addressed User Groups

    IT administration can be called for repairs before the problem escalates and negatively affects the current workflow. The MEDNET Manager gives intuitive tips on how to best deal with the situation and continuing work panic-free until the network is online again.

  • Page 20: Medical Network Statement

    Medical Network Statement Network + Medical = Medical Network The MEDNET product is not a medical product! But it adds network capabilities to the SCHWIND medical products: a “Medical Network” is realised. To avoid individual safety evaluation, all mandatory regulatory requirements and approvals are already included in the MEDNET product itself for all explicitly specified setups and system combinations listed in “4.3 Valid System Combinations with SCHWIND Medical Devices”!

  • Page 21: Mandatory Prerequisites

    The operator/client/clinic requires a responsible IT (IT Admin) for typical administrative IT subjects. The MEDNET product is engineered to provide even persons with “basic IT” skills the ability to fulfil that role! The network infrastructure remains in the responsibility of the client/clinic/institute! The operator must carry out all typical IT administration activities by himself.

  • Page 22: Process: Planning → Installation → First Operation

    Process: Planning → Installation → First Operation In cooperation with the clinic, SCHWIND is responsible for planning, installation and proper first use to achieve a safe, secured, reliable and compliant MEDNET eco- system. The procedure is standardized, very quick, easy and economically effective! A) SCHWIND authorized service personnel plan the network together with responsible IT personnel of the clinic.

  • Page 23: Valid System Combinations With Schwind Medical Devices

    (Information may be updated in the meanwhile. Ask Schwind if your system is not listed.) The used PC is different due to date of purchase and PC availability. When System is combined with medNet, PC type must be checked if compatible. (“PanelPC Onyx 175 / Onyx Zeus” are allowed)

  • Page 24: Network Characteristic, Requirement And Configuration

    Mandatory Prerequisites Network Characteristic, Requirement and Configuration The MEDNET is a dedicated (private) network for SCHWIND medical devices only. As an option, PCs or devices inside an attached clinic network can access the fileserver (treatment log files, treatment projects,..) for reading the content for own purpose processing.

  • Page 25: Infrastructure Type: "Dedicated Private Lan Network

    This is the default and easiest set up! The LAN cables have to be prepared for use exclusively for the SCHWIND devices only in the dedicated “MEDNET network”. NON-SCHWIND DEVICES / CLINIC PC DEVICES OR HARDWARE IS NOT ALLOWED WITHING THE MEDNET (SUB-)NETWORK.

  • Page 26: Infrastructure Type: "Lan Over Clinic Vlan With Managed Switch

    This type is intended for already existing advanced network infrastructure, especially when the cabling has to go through several floors with no additional LAN cable left for the MEDNET. It is possible to transmit encapsulated networks over one cable, for example, when several clinic floors are interconnected by one fibre channel cable transmitting several different networks.

  • Page 27: Wireless Infrastructure

    Wireless Infrastructure Use of WLAN/WIFI is not allowed. Wireless connection be guaranteed and has been tested as unreliable, which may result into connection loss, low transfer speed and data loss. Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 27 of 135...

  • Page 28: Infrastructure Online Remote Support / Clinic Network Access To Fileserver

    Customer Support or from Technical Service! A separate LAN cable must be connected from the MEDNET router to a Switch LAN Port from the clinic network. Over that LAN connection, addressing the internet must be provided by the clinic network.

  • Page 29: Satellite Clinic Infrastructure

    Each clinic location has one independent local MEDNET network. Now it is possible to transmit data between the MEDNET networks from location A to location B, applied by the clinic network. This chapter illustrates the required infrastructure. For a complete overview also refer to the following chapters: 7.4 Satellite Clinic –...
  • Page 30 PC in clinic network. with intercommunication over internet / Intranet VPN tunnel over Internet The clinic network accesses the medNet fileserver(s). Clinic must provide the infrastructure, without SCHWIND responsibility. Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 30 of 135...

  • Page 31: Physician's Best Practices

    The medical devices themselves can be powered off when not in use. Common rules for dealing with the MEDNET are essential for all users. Using the MEDNET will be part of your daily treatment procedure and therefore mandatory for all users.
  • Page 32 In the CAM software upon saving, the target location is opened automatically as configured. • In the other software products the last saving path location is remembered and opened automatically. Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 32 of 135...

  • Page 33: Fileserver Directory Structure

    User Manual Physician’s Best Practices Fileserver Directory Structure The MEDNET directory structure is product oriented. Relative to root, each subdirectory is named according a SCHWIND medical device or a software product. All devices can access the Server at the same time!
  • Page 34 Optionally, the Diagnostic device’s database can be shared on network. Multiple diagnosis devices of same type, can access simultaneously. Optionally, with MEDNET PRINT, printouts via PDF printer are automatically saved onto Server. Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 34 of 135...

  • Page 35: Dataflow

    MEDNET, changed and re-saved to the MEDNET. It is assumed that the saving syntax is the same on all devices, so re-saving to MEDNET will overwrite the older project state on the MEDNET with the new saved project state! 4.

  • Page 36: Saving/Loading Within Treatment Software

    The Server contains a special directory order, optimized for workflow and all treatment data. When MEDNET is not recognized or offline, the link is not available or will be removed. The link will be automatically available, when MEDNET Server is reachable.
  • Page 37 Access to “Delegate folder”. The delegate folder is an “outbox” (similar to email clients). All files, which shall be saved onto the MEDNET Server shall be saved in this folder. The folder is always available, located on the local harddisk.
  • Page 38 The target is already pre-configured in the pre-defined directory and the Loading dialog already points to “medNet Filestorage”. In case medNet is offline on the PC in use, the saving target “DELEGATE to medNet” remains available, whereas if the network link “medNet Filestorage” is removed, the loading dialog will fall-back to another local directory.

  • Page 39: Workstation: Phoenix Software - Schwind Export

    Variant 1 When you click <Export> (enabled standard path in settings, “delegate folder”), the export is directly saved into the MEDNET “delegate folder” without any saving dialog. Very easy, very fast and no need of manual path management. Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2...
  • Page 40 Diagnosis Images / SCHWIND Export – Variant 2 With right mouse button click on <Export>, popup “Save with copy” appears. You can choose the saving path manually in additional to any location. Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 40 of 135...

  • Page 41: Workstation: Scout Software - Schwind Export

    Diagnosis Images / SCHWIND Export Saving: Point to \medNet DELEGATE to SERVER\DIAGNOSTIC_Export Note: Saving path cannot be fixed to a specific folder. Each time of saving, check the addressed path is correct. Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 41 of 135...

  • Page 42: Workstation: Cam Software, Cam Projects

    Dialog uses file filter by extension. Only relevant file types will be displayed (according to the chosen image type) In CAM Settings, the default loading path can be defined. Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 42 of 135...
  • Page 43 (OPEN) SCHWIND CAM Projects LOADING/OPENING CAM Project Load the CAM Project from: \medNet SERVER\SCHWIND_CAM Choose the appropriate patient’s sub-folder (name/id) In CAM Settings, the default loading path can be defined. Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 43 of 135...

  • Page 44: Amaris: Application Software, Cam Projects / Treatment Log / Etc

    Data There is no Application Software - Save Dialog. Application Software saves the project automatically on local drive. MEDNET Manager detects the new data and transfers it automatically to SERVER without any user activity required. This is applied applies for all type of data from AMARIS, Application Software:...

  • Page 45: Mednet Manager - Overview

    MEDNET Manager - Overview MEDNET MANAGER - OVERVIEW The MEDNET Manager Software is a network management tool. It creates the “link” between users and the MEDNET network system including sophisticated functions guaranteeing a convenient user experience with more effectiveness in less time! The software is required to operate the SCHWIND medical devices (PanelPC) together with the SCHWIND MEDNET.

  • Page 46: Software Start-Up & Shutdown

    MEDNET Manager is started automatically with Windows and runs in the background. When Windows is shutting down, MEDNET Manager detects the shutting down event and safely exits. All pending or running actions are suspended and re-started when the MEDNET Manager starts again.

  • Page 47: Diagnosis View

    The complete network status is refreshed in periodic intervals (~1 Minute by default) even when MEDNET Manager is minimized. The status is displayed in near real time to give the user the best possible feedback! Use the status to solve network anomalies (failures).

  • Page 48: Quick Access Via F4 Hotkey

    When the Treatment Menu is left, the notification will appear again. Quick Access via F4 Hotkey Minimized run When MEDNET Manager is HIDE/MINIMIZED or auto-started with Windows, it appears in the tray area in the task bar. Click on the orange icon to show the program window. Global Hotkey <F4>...

  • Page 49: Software Configuration

    Go to the Settings screen (Tab: settings) 7.1.1 Autostart Autostart is required for enabling the MEDNET capabilities on the system. Default is ON. Use OFF temporarily only, for example with service or maintenance issues, if required. 7.1.2 Notification Popup The notification popup is essential for being informed about different types of network failures or MEDNET problems at the time they occur.

  • Page 50: Device Type And Name

    Press TEACH-IN to save the information! A system reboot is required afterwards! You can set other settings before the reboot. 7.1.4 Fileserver Address The MEDNET Fileserver (NAS) is addressed with this configured NetBIOS name OR entered IP- address: or abbreviated name if changed manually OR IP: MEDNET-SERVER 192.168.141.99...

  • Page 51: Internet Access & Proxy Settings

    Manager’s integrated online remote access. Refer to the respective chapter for prerequisites and for more background information. MEDNET Manager can disable and enable access to the “foreign attached network” as a safety feature for the PC and for the connected clinic network.

  • Page 52: Finishing The Configuration

    Finishing the Configuration When finished, reboot the system. You can use the REBOOT NOW button or shutdown Windows. When everything is correctly configured, MEDNET Manager will initialize successfully. Note: The verbose initialising text is removed after a few seconds when everything is fine. If errors are detected the text remains in the box.

  • Page 53: Treatment Software - Settings

    Phoenix and Scout: Set the saving path fix to DELEGATE folder. This ensures to always save onto the local DELEGATE folder, which content is automatically moved to mednet-Server. The user can just click “save/export” without remember any path and path does not fall back to other directory, for example after PC reboot or software restart.

  • Page 54: Workstation Cam Settings

    Delegate folder root, which holds data on the D:\FILES_DELEGATEtoMEDNET local drive, then copied to Server from mednet Manager Software. represents direct root address to the mednet Server, for loading data directly from Server. Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 54 of 135...

  • Page 55: Amaris Application Software Settings

    Delegate folder root, which holds data on the D:\FILES_DELEGATEtoMEDNET local drive, copied to Server from mednet Manager Software. represents direct root address to the mednet Server, for loading data directly from Server. Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 55 of 135...

  • Page 56: Workstation Phoenix Software Settings

    Ensure to point to “DELEGATE folder\DIAGNOSTIC_Export” Do NOT point to “mednet Server”. Important Setting in case the Phoenix Database is located on the MEDNET-SERVER: To get a good performance from the remote MEDNET-SERVER, set the following settings on all PHOENIX Software installations. •...

  • Page 57: Workstation Scout Software Settings

    WORKSTATION IRX3 Software Settings Saving path cannot be fixed to a specific folder. Each time of saving, check the addressed path is correct: DIAGNOSTIC_Export Point to \medNet DELEGATE to SERVER\DIAGNOSTIC_Export Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 57 of 135...

  • Page 58: Mednet Folder Structure Optimisation

    MEDNET Folder Structure Optimisation If you have a higher demand on structured saving, you can define own sub-directories. Example: To get this structure you have to change the medNet Manager’s “DelegatFolder_SubDirStructure_WORKSTATION” • Change must be equal on all SCHWIND WORKSTATIONS.

  • Page 59: Satellite Clinic - Fileserver Name

    MEDNET Manager Software configuration on all SCHWIND PCs in that network! For details see chapter: “7.1.4 Fileserver Address” The fileserver’s default factory set network name is “mednet-server”. When two or more fileservers are attached to the same clinic sub-network for date exchange (for example: subnet 192.168.123.X with mask 255.255.255.0), each fileserver name must be changed to something...

  • Page 60: Online Remote Services

    The well-known remote software “Team Viewer” is seamlessly integrated into MEDNET Manager. To establish the remote connection, just open MEDNET Manager, press the <start> button for remote connection and give your remote partner a connection number to control your computer! The reaction time of first service by third parties will be reduced to a minimum of time! Internet connection for MEDNET is required.
  • Page 61 Internet is always required to start the remote connection. The MEDNET PC will address a Team Viewer server on internet to get a unique ID for your session partner. (This is also required if you connect one of your clinic PCs to the MEDNET PC.) Safety and Security WARNING •...

  • Page 62: Starting A Remote Session On The Medical Pc

    The medical PC is the remote supported device. The remote connected device is the support assisting partner. The remote session must always be started with MEDNET Manager. Press the hotkey <F4> or the MEDNET Manager icon in the windows tray icon.
  • Page 63 User Manual Online Remote Services Close Enable/Disable/Settings Minimized/Maximize for Video/Chat/Voice Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 63 of 135...

  • Page 64: Connecting To The Schwind Medical Pc From Clinic Network

    Connecting to the SCHWIND Medical PC from Clinic Network The remote connection is mainly intended to be used by SCHWIND or a distributor, but it is also possible for the clinic to use the remote connection for own service purpose from the attached clinic network.

  • Page 65: Using Web Camera And Headset

    Green connector or plug with or plug with Mic Symbol Headphone Symbol Enable Video or Audio only. You can mute Microphone and set volume. The gear icon shows additional options. Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 65 of 135...

  • Page 66: Fileserver - Access From Clinic Network

    The infrastructure must be set up properly. Besides access to the corresponding fileserver from a MEDNET medical device, a PC within the clinic network will have the ability to connect to the MEDNET fileserver by several methods.

  • Page 67: Fileserver - Content

    • PDF printouts generated by MEDNET PDF printer Fileserver – Access MEDNET PDF Printouts The MEDNET Project share can contain a sub-directory for MEDNET PDF printer, containing the printout files. (see Chapter “10.4 Short Manual: MEDNET Print”) \\medNet_Projects\PDFPrint For security reason, the root projects folder (access to all project data) should not be mounted.
  • Page 68 Choose Drive letter as available. QNAP NAS Models: TS-253Be, TS-253D (MEDNET Revision since 2019) net use R: \\mednet-server\medNet_PDF T7bza8 /user:setsPDF /persistent:yes ReadWrite User “setsPDF” can be used for this SMB share only.

  • Page 69: Fileserver Access - Protocols & Accounts

    Windows Network (SMB) or FTP or Web Browser. Everything is running on the file server as a service. Please always use the NetBIOS name of your MEDNET fileserver instead of the IP! Addressing the file server There are two ways to address the device: •...
  • Page 70 Subfolder is optional. In you require just a certain sub-folder like “PDFprinter or Logfiles”, include the subfolder in the commandline. • For mednet-server address you may use fixed IP instead of netbios name. FTP protocol, Port: 21 User accounts for MEDNET_Projects as described and for MEDNET_PublicShare use Login: anonymous without a password.
  • Page 71 NetDrive is free for non-commercial use. You might buy a license from the vendor. Insert the NetBIOS name of the MEDNET-fileserver instead of IP address. Port 21 and Account details as described above. If everything is correct it should work immediately.

  • Page 72: Satellite Clinic - Best Practise

    “London”. The process is carried out from any clinic PC which is able to access all the MEDNET fileservers. In the example this would be possible by PC A; PC B or PC Due to the network architecture, this is not possible from a MEDNET PC, but instead only from a PC in the clinic network which is able to “reach”...

  • Page 73: Printing

    Compare the scenarios. Choose one that fits best to the clinic. The delivered SCHWIND Printer (Canon) cannot be attached into the MEDNET-network as regular network printer. SCHWIND does not (yet) offer a central network printer for MEDNET Network. Instead, consider: “Scenario 4: Printout on SCHWIND Printer within MEDNET Network”.

  • Page 74: Scenario 1: Printout On Usb Connected Printer

    Install the USB printer as regularly instructed in AMARIS or WORKSTATION manual(s). 10.1.2 Scenario 2: Generate PDF Files only The PDF files are generated on the SCHWIND PCs without a real paper printout required. The print tool “mednet print” is not involved. medNet network Print documents to printer “medNet PDF”...

  • Page 75: Scenario 3: Printout On Printer In Clinic Network

    Chapter “10.2 Print-Setup: SCHWIND PanelPCs (Workstation, AMARIS PC)” SETUP 2: Connect Clinic network to MEDNET Server LAN Port 2, IP shall be provided via DHCP Server in clinic; (mounting a shared directory is not necessary since MEDNET Print will handle server...

  • Page 76: Scenario 4: Printout On Schwind Printer Within Mednet Network

    Scenario 4: Printout on SCHWIND Printer within MEDNET Network The PDF files are generated on SCHWIND PanelPCs. The SCHWIND delivered (USB) printer is connected to a SCHWIND Workstation PanelPC or Standalone PanelPC. MEDNET Print – Tool prints out the PDF on real paper.

  • Page 77: Print-Setup: Schwind Panelpcs (Workstation, Amaris Pc)

    An authorized service technician should install the latest version. • If a clinic network is attached for printing to any clinic printer, the “MEDNET Print” Tool must be installed on a Windows PC. It runs with Win XP, Win Vista, Win7, Win8 and Win10 as a user program.

  • Page 78: Print-Setup: Mednet Print (Schwind Pc Or Clinic Pc)

    Version as noted above.) 10.3 Print-Setup: MEDNET Print (SCHWIND PC or clinic PC) Install “MEDNET Print” Tool on a Windows Clinic PC attached over Network to MEDNET for Scenario 2, or on Workstation PanelPC or Standalone PanelPC for Use Scenario 3.
  • Page 79 Go to the settings. It is recommended to set autostart to ON. (Autostart is written ▪ to the current user’s windows-registry). “MEDNET Print” will run persistent in the background to fulfil its tasks. Make a printer choice. ▪ The other settings don’t have to be changed! ▪...

  • Page 80: Short Manual: Mednet Print

    • When running, the program is always available in the tray bar. • Internally MEDNET Print connect to MEDNET Server by FTP. The Fileserver’s \PDFprinter root-directory involves three sub-directories: Note: The directories can be accessed directly from a SCHWIND PC running MEDNET.
  • Page 81 The selected files are deleted permanently from the fileserver. The selected files in the pending list are Skip Print not printed. Suspend the monitoring process first with button “running/stopped”. Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 81 of 135...

  • Page 82: Print-Setup: Additional Mednet Pdf Printers

    2. The SCHWIND devices print over their specific “MEDNET PDF printer” configuration: The new printer name shall get an increased count number in its name like “medNet PDF Printer 2” (or 3…) and will get a new independent PDF file directory on the Fileserver. The follow setup describes setup of a 2 printer.
  • Page 83 4. Select the new profile and <Add a new printer for this profile>. Exit the configuration. 5. A new windows printer with name of the profile is now present. Set it to default printer. Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 83 of 135...
  • Page 84 You can use a different clinic PC or the same PC with several instances. If the same PC is used, add a number “2” to the MEDNET Print directory name (i.e. “MEDNET_Print2”) and activate auto- start in settings. (V1.1.50 or higher)

  • Page 85: Access Or Print Pdf-Files From Mednet Fileserver

    …from SCHWIND PC (Workstation/AMARIS) over MEDNET Network • (If clinic network is connected to MEDNET Server) …from Clinic PC accessing clinic network, which is connected to MEDNET Server. See Chapter “9 Fileserver - Access from Clinic Network” for setup. 10.7 Printing Tips •...

  • Page 86: Workstation Diagnostic-Database On Mednet-Server

    PC. In combination with SCHWIND MEDNET, the database can be moved to the MEDNET Fileserver, as a shared database in the middle of other devices or software installations on other PCs. Example: The patient data is acquired in the diagnosis room by Sirius while the database is located on the network file server.

  • Page 87: Mdb Database

    All the planning actions can be performed again quickly without leaving the sterilized surgery room. The doctor can view the current patient’s eye scans and selecting another scan for the SCHWIND CAM export and CAM treatment planning. Then the CAM treatment planning can be performed on the Standalone PanelPC or on Amaris…...

  • Page 88: Shared Database

    IRX3 hardware→Scout Software→database engine→.mdb file based DB for IRX3 11.2.1 Shared Database, multiple Workstations • Each Diagnosis Software can use a “shared database” on the MEDNET SERVER. • Supported Software: PHOENIX (Sirius and Peramis device), SCOUT, IRX3 Example: Same database (concurrent access)

  • Page 89: Concurrent Database Access

    Data is update in the software when the database content is re-read. For example: Patient list is updated when letter is entered in the “search mask”. Displayed scans are updated when a patient is (re-) opened. Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 89 of 135...

  • Page 90: Phoenix (Sirius/Peramis)

    “SCHWIND Standalone PC” required the “review key license”. Diagnosis key and two review keys are free of charge. The requested P-number is the one of the workstation (see label at Panel-PC or SW, bottom left). The serial numbers are provided by SCHWIND. Please make send email when required.

  • Page 91: Create New Database On Network

    User Manual WORKSTATION Diagnostic-Database on MEDNET-Server COPY RENAME 11.3.3 CREATE new Database on Network 1. Go to the Settings then Miscellaneous, click the icon beside “Database”. Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 91 of 135...
  • Page 92 2. When the database window appears, change the database location. The Database type must be type: Access. Click YES to create a new database. 3. Now go to the Network Filestorage by pointing to: My Computer | medNet FileStorage | _DiagnosticDevice_Databases\Sirius and Create a new folder. Give it an unambiguous name.
  • Page 93 Time depends on your network speed and can take up to 30 seconds! The Sirius Software will come up when finished and the new DB is selected, but configuration is not yet fully finished! Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 93 of 135...

  • Page 94: Open/Change Database

    “Database” line to “Backup in” and remove the *.mdb filename. Example: Y:\DiagnosticDevices_Databases\Sirius\New Database 2012\MyDB2012.mdb Y:\DiagnosticDevices_Databases\Sirius\New Database 2012\ 11.3.4 OPEN/CHANGE Database 1. Go to the Settings then Miscellaneous and click the icon as shown above. Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 94 of 135...
  • Page 95 The Sirius Main Screen will appear, but you are not yet finished: Image root and Backup in directories are not yet set! 5. Open the settings again and set the other two paths! 6. After OK the database is ready to use. Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 95 of 135...

  • Page 96: Delete Database

    When a new patient is created or changed by a PC, all other PCs which are currently using this DB are automatically updated. The new data appears without manual actions required. 11.3.7 Important Settings To get a good performance from the remote MEDNET-SERVER, set the following settings on all PHOENIX Software installations. • Limit the...

  • Page 97: Scout

    The Software is already pre-installed on the SCHWIND PCs. Normally there are no additional steps required. But in case the SCHWIND CAM Export is not enabled, if the SCHWIND Icons are not displayed, please call SCHWIND for enabling instructions. 11.4.2 COPY/MOVE existing Database from Workstation to Network If you plan to move or copy an existing database located on your Workstation’s drive, follow this...

  • Page 98: Create New Database On Network

    11.4.3 CREATE new Database on Network 1. Click File | New DataBase 2. Now go to the Network Filestorage by pointing to: My Computer | medNet FileStorage | _DiagnosticDevice_Databases\Scout, then Create a new folder and give it an unambiguous name.

  • Page 99: Quick Change Database

    The deleted database can be recovered out of the “recycle bin” if necessary. 11.4.7 DELETE whole Database Use Windows file-explorer. Point to the MEDNET Scout database directory and delete the whole subfolder. 11.4.8 UPDATE Database after a Change by another Device...

  • Page 100: Irx3

    11.5.1 Preparation The Software is pre-installed on SCHWIND PCs. When the software will start with the following error message, a separate “calibration file” must be installed in additional. The calibration file is included separately with each IRX3 hardware device on a CD. (If your CD is missing, you can call SCHWIND for your individual File in accordance to your device serial number…)

  • Page 101: Create Database On Network

    RENAME 11.5.3 CREATE Database on Network Short description: A clean and new database must be created manually on the medNet Filestorage with Windows File-explorer. For each Database create an own subdirectory on the MEDNET-server path: \[Datgabase_Directory]\IRX3\[NewSubDir] and copy the database template file from: c:\Program Files\ImagineEyes\IRX3_V12\database\BD_Patients.mdb...
  • Page 102 2. Do right click and create a new subdirectory. Give it an unambiguous name. 3. Now copy the database template file C:\Program Files\ImagineEyes\IRX3_Vxy\database\BD Patients.mdb into that directory 4. Rename the database file to an unambiguous name if you want (=optional). Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 102 of 135...

  • Page 103: Open/Change Database

    3. “Data Link Properties” Dialog appears. Do not change any other settings. Just do the following. Go to Tab “Connection”. Click on “…” button. The open dialog will appear. Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 103 of 135...

  • Page 104: Delete Database

    “Open” 5. Click “OK” to use the Database in the IRX3 Software 11.5.5 DELETE Database Use Windows file-explorer. Point to the MEDNET IRX3 database directory and delete the whole subfolder. 11.5.6 UPDATE Database after a Change by another Device When a new patient is created or changed by a PC, all other PCs which are currently using this DB are automatically updated.

  • Page 105: Troubleshooting

    • MEDNET Manager has network diagnosis on board! Always refer to the Diagnostic Page on all the Schwind devices to “look on the network in view of that device”. This very first step will encircle affected devices and the respective infrastructure.
  • Page 106 If numbers of ports on the router are extended by a switch, check that the switch is properly connected. • The “LAN Ports” are only used for the “MEDNET network” and NOT connected to foreign devices or the clinic network. •...
  • Page 107 User Manual Troubleshooting Combine all “network views of the Schwind device” together for ideas on possible failure causes Example: No other devices visible medNet Router NAS/Fileserver In this example PC A and B “see” all other devices and Filestorage is available. PC C does not see any other devices and Filestorage is not available.

  • Page 108: Mednet Manager

    After a successful initialisation (everything works correctly) the box shows the headline only. In case of error, the information remains visible! An IT administrator can see the present MEDNET state of the PC by visiting the Main Display and the LED status indicator at the MEDNET Manager bottom.

  • Page 109: Diagnosis

    Common network analysation tools are available in MEDNET Manager. Status is refreshed immediately. This can take “a few seconds”. All MEDNET devices must be assigned to the displayed workgroup to operate properly! Information on the PanelPC itself. Type:...
  • Page 110 Overview of all “visible” medNet devices within the medNet Workgroup. →All properly configured and connected MEDNET devices must be listed here. The MEDNET Fileserver must always be visible! If a device is expected to be “visible” but it isn’t, the error cause should be searched and fixed.
  • Page 111 BROWSTAT network installations. ➔ Master browser and backup browser device must be a MEDNET device. If the listed device is NOT a MEDNET device, something with the network infrastructure might be improperly connected, i.e. the clinic network is directly attached…...
  • Page 112 The MEDNET-required user accounts and the network shared are tested for anomalies. Ensure that the MEDNET file storage (fileserver or NAS) is indicated as “online” before starting the test! After <start test> MEDNET manager is degraded into a “testing mode”. MEDNET-Manager or PanelPC must be re-started after the test! All tests result must be “OK.
  • Page 113 User Manual Troubleshooting Testing the connection to the MEDNET fileserver is most important. For all pre-defined tests, the MEDNET fileserver is always the test-target! Ensure the MEDNET is “online”. You can find out the network speed ability and thus the overall network quality and the reliability of network + fileserver under heavy transfer.
  • Page 114 If the transfer rate is bad, try a reboot of the fileserver and check the network infrastructure. Re-start the test while no other MEDNET device accesses the network. Network speed Expected transfer rates...

  • Page 115: Mednet Manager: Processing Takes Much Time

    12.2.4 MEDNET Manager: Processing takes much Time When delegating or syncing is preceded by MEDNET Manager, it can take a while depending on the amount of files and network speed. After duration of ~1 minute, an additional information field appears at the bottom of the MEDNET Manager.

  • Page 116: Using Fixed/Static Ip For Fileserver

    Depending on the MEDNET Revision, the Computers addresses the MEDNET Server by its NETBIOS NAME (mednet-server) or static IP address 192.168.141.99. Starting with MEDNET Revision of 2019 (NAS Model: QNAP TS-253Be), the addressing via fixed IP is pre-configured. For all older models, the IP change is also recommended and must be changed manually.
  • Page 117 Set IP 192.168.141.99 only. Gateway to 255.255.255.255. Do not use other IP and do not make other changes. All available SCHWIND PanelPCs must be configured to the new server IP address manually: 192.168.141.99 MEDNET Manager | SETTINGS: Set IP only.

  • Page 118: Workstation - Diagnosis Database On Network

    After PanelPC start wait 1 minute before start diagnosis software. MEDNET Manager requires this time to initialize the file-server connections…. • Keep an eye on the MEDNET Manager “notifications”. A message will pop-up when the file-server is detected being offline. Slow database Check Network speed;...
  • Page 119 Do not acquire patients, close the software immediately, and re-open the network database with via menu “File | recent database” Connection breaks during use Error message appears and software quits. Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 119 of 135...
  • Page 120 User Manual Troubleshooting IRX3 Software start with Network is offline database file is missing (network is online) connection breaks during use Error message is displayed and software quits. Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 120 of 135...

  • Page 121: Fileserver Maintenance - Status Check, Drive Replacement Or Upgrade

    Troubleshooting 12.6 Fileserver Maintenance – Status check, Drive replacement or upgrade It is recommended to check the MEDNET Server status in interval For example: every month, every 3 month… The NAS uses RAID1. The files are 1:1 stored on two drives simultaneously. If one drive failed (for example: electronic failure, head crash) the defective drive can be exchanged while the NAS is running.
  • Page 122 User Manual Troubleshooting Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 122 of 135...

  • Page 123: Fileserver Drive Replacement Or Upgrade

    IT Administration. 12.7.1 NAS is Defective – NAS Replacement It is assumed you have NAS exchange model ready, provided by Schwind, including new drives and pre-configuration for MEDNET. 1. Install the NEW NAS into the MEDNET.

  • Page 124: Drive Replacement / Expand Space

    After both drives have been exchanged with bigger ones and RAID synchronisation is finished, the <EXPAND> function is available. Use it to make the new space available. See following screenshots, considering the NAS Firmware Version Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 124 of 135...
  • Page 125 User Manual Troubleshooting QTS 4.2 and older – Change disk / Expand Capacity QTS 4.3 – Change disk / Expand Capacity Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 125 of 135...
  • Page 126 User Manual Troubleshooting QTS 4.4 – Change disk / Expand Capacity Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 126 of 135...

  • Page 127: Server-Data Maintenance

    • Store the backup data at different places, apart from MEDNET NAS, offline storage • The backup should be created when the SCHWIND devices do not access the data, e.g., during the night or weekend. • The data is saved on directories and files only. There is no SQL Server.
  • Page 128 USB disk also to other data media for offline storage. Example Screenshots of TS253Be, Backup Station: Options recommended: Disabled: Check file contents Enabled: Overwrite file if source file is newer or file size is different. Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 128 of 135...
  • Page 129 User Manual Server-Data Maintenance Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 129 of 135...

  • Page 130: Cleanup And Archive Work Folders

    (ie. thousands of entries). If you have a few hundred entries only, a “tidy up” is not (yet) necessary. PanelPC: D:\FILES_ARCHIVE\* All files, “delegated” to medNet are moved to this folder after copy to Server. This folder can be deleted, the files are stored on medNet Server anyway. MEDNET Fileserver: [medNet FileStorage]\\[working directories] Clean mednet SERVER working directories are always recommended.

  • Page 131: Iec 60601-1

    IEC 60601-1 3rd Network FAQ 14 IEC 60601-1 3 NETWORK FAQ The SCHWIND medical devices are allowed to be incorporated into a computer network by use of optional add-on product “SCHWIND MEDNET” only. Why is this important SCHWIND MEDNET includes HW, SW, specifications and instructions to create a “medical computer network”...
  • Page 132 MEDNET product and not allowed. If not otherwise mentioned in the SCHWIND medical product documentation, the product is not allowed to be connected into a medical IT-network system, different to SCHWIND MEDNET instructions or its individual instructions. Which cases may introduce new risk, requiring (additional) analysis For MEDNET, the abbreviation to the MEDNET instructions is not allowed.

  • Page 133: List Of Passwords

    ReadWrite access from external non-Schwind devices to MEDNET-Server content creates hazards. Clinic is responsible for all type of malfunctions caused by external (non-mednet) access to MEDNET-Fileserver. Clinic is strongly advised to take adequate countermeasures (temporarily access only, Server Backups, virus/malware protection on PC accessing the server; Trustworthy persons,… ) to guarantee data integrity at all the time.

  • Page 134: Contact Address

    SCHWIND eye-tech-solutions GmbH Mainparkstrasse 6-10 D-63801 Kleinostheim Tel.: +49-(0)6027-508-0 Fax: +49-(0)6027-508-208 info@eye-tech.net Email: http://www.eye-tech-solutions.com Service Hotline: Tel.: +49-(0)6027-508-333 Fax: +49-(0)6027-508-245 service@eye-tech.net Email: Customer Support: Fax: +49-(0)6027-508–208 Tel.: +49-(0)6027-508-350 Email: apm@eye-tech.net Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 134 of 135...
  • Page 135 User Manual Contact Address Your notes Doc. V1.9.2.1 (2021-05-10) | MEDNET Manager V1.9.2 Page 135 of 135...

Table of Contents