User Manual

USER MANUAL
for MEDNET MANAGER V1.9

Original Instruction for Use
Document version 1.9.2, dated 2020-04-20
SCHWIND eye-tech-solutions GmbH

Mainparkstrasse 6-10 · D-63801 Kleinostheim
User Manual
TABLE OF CONTENTS
PICTOGRAM DEFINITION ...................................................................................................................................5
SCOPE OF USER MANUAL ....................................................................................................................................5
USER MANUAL STORAGE LOCATION .................................................................................................................5
1 GENERAL INFORMATION .........................................................................................................................6
1.1 System Identification Data .......................................................................................................................6
1.2 Technical Assistance / Application Support ..............................................................................................6
1.3 Declaration of Manufacturer.....................................................................................................................7
1.4 Liability Exclusions ...................................................................................................................................7
1.5 Warranty ..................................................................................................................................................8
1.6 License Agreement...................................................................................................................................9
1.7 Copyright .................................................................................................................................................9
1.8 Trademarks ..............................................................................................................................................9
1.9 Scope of Delivery / Delivered Content ...................................................................................................10
1.10 SCHWIND Labelling................................................................................................................................11
2 HAZARDS AND SAFETY ...........................................................................................................................12
2.1 Restrictions of Use .................................................................................................................................12
2.2 Training of Operator’s Personnel............................................................................................................12
2.3 Protection from Unauthorized Use .........................................................................................................12
2.4 Data Protection and Data Privacy ..........................................................................................................12
2.5 Virus Protection......................................................................................................................................13
2.6 Electronic Safety on the Medical Device .................................................................................................13
2.7 Dangers Resulting from Software Operation ..........................................................................................15
2.8 Dangers resulting from Network Failure ................................................................................................15
2.9 Interruptions from Network Operation Failure .......................................................................................15
2.10 In Case of Emergency ............................................................................................................................15
2.11 Contraindications / Side Effects .............................................................................................................15
3 PRODUCT INTRODUCTION ....................................................................................................................16
3.1 Overview ................................................................................................................................................16
3.2 Intended Use & Reasonably Foreseeable Misuse ...................................................................................18
3.3 Addressed User Groups ..........................................................................................................................19
3.4 Medical Network Statement ...................................................................................................................20
4 MANDATORY PREREQUISITES ..............................................................................................................21
4.1 Product Responsibilities – Overview .......................................................................................................21
4.2 Process: Planning  Installation  First Operation...............................................................................22
4.3 Valid System Combinations with SCHWIND Medical Devices .................................................................23
4.4 Network Characteristic, Requirement and Configuration........................................................................24
4.4.1 Infrastructure Type: “Dedicated private LAN Network” ....................................................................25
4.4.2 Infrastructure Type: “LAN over Clinic VLAN with managed Switch” .................................................26
4.4.3 Wireless Infrastructure .....................................................................................................................27
4.4.4 Infrastructure Online Remote Support / Clinic Network Access to Fileserver ...................................28
4.4.5 Satellite Clinic Infrastructure ............................................................................................................29
5 PHYSICIAN’S BEST PRACTICES ............................................................................................................31
5.1 Fileserver Directory Structure ................................................................................................................33
5.2 Dataflow.................................................................................................................................................35
5.3 SAVING/LOADING within Treatment Software.......................................................................................36
5.3.1 WORKSTATION: PHOENIX Software – SCHWIND Export .................................................................39
5.3.2 WORKSTATION: Scout Software – SCHWIND Export .......................................................................41
5.3.3 WORKSTATION: IRX3 Software – SCHWIND Export ........................................................................41
5.3.4 WORKSTATION: CAM Software, CAM Projects .................................................................................42
5.3.5 AMARIS: Application Software, CAM Projects / Treatment log / etc .................................................44
6 MEDNET MANAGER - OVERVIEW ..........................................................................................................45
Document version 1.9.2, dated 2020-04-20 | for MEDNET Manager V1.9.2 Page 2 of 135
User Manual
6.1 Software Start-up & Shutdown ..............................................................................................................46

6.2 User Interface & Status View .................................................................................................................46
6.3 Diagnosis View .......................................................................................................................................47
6.4 Popup Notifications ................................................................................................................................47
6.5 Quick Access via F4 Hotkey ...................................................................................................................48
7 SOFTWARE CONFIGURATION ...............................................................................................................49
7.1 MEDNET Manager - Settings ..................................................................................................................49
7.1.1 Autostart ..........................................................................................................................................49
7.1.2 Notification Popup ............................................................................................................................49
7.1.3 Device Type and Name ....................................................................................................................50
7.1.4 Fileserver Address ............................................................................................................................50
7.1.5 Internet Access & Proxy Settings .....................................................................................................51
7.1.6 Finishing the Configuration ...............................................................................................................52
7.2 TREATMENT Software - Settings ...........................................................................................................53
7.2.1 WORKSTATION CAM Settings ..........................................................................................................54
7.2.2 AMARIS Application Software Settings .............................................................................................55
7.2.3 WORKSTATION Phoenix Software Settings ......................................................................................56
7.2.4 WORKSTATION Scout Software Settings..........................................................................................57
7.2.5 WORKSTATION IRX3 Software Settings ...........................................................................................57
7.3 MEDNET Folder Structure Optimisation..................................................................................................58
7.4 Satellite Clinic – Fileserver Name ...........................................................................................................59
8 ONLINE REMOTE SERVICES ...................................................................................................................60
8.1 Starting a Remote Session on the Medical PC ........................................................................................62
8.2 Connecting to the SCHWIND Medical PC from Clinic Network ...............................................................64
8.3 Using Web Camera and Headset ...........................................................................................................65
9 FILESERVER - ACCESS FROM CLINIC NETWORK ...............................................................................66
9.1 Fileserver - Content................................................................................................................................67
9.2 Fileserver – Access MEDNET PDF Printouts ...........................................................................................67
9.3 Fileserver Access – Protocols & Accounts ..............................................................................................69
9.4 Satellite Clinic – Best Practise ................................................................................................................72
10 PRINTING .................................................................................................................................................73
10.1 Printing scenarios ...................................................................................................................................73
10.1.1 Scenario 1: Printout on USB connected Printer ................................................................................74
10.1.2 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 Short Manual: MEDNET Print .................................................................................................................80
10.5 Print-Setup: Additional MEDNET PDF Printers ........................................................................................82
10.6 Access or Print PDF-files from MEDNET Fileserver .................................................................................85
10.7 Printing Tips ...........................................................................................................................................85
11 WORKSTATION DIAGNOSTIC-DATABASE ON MEDNET-SERVER ....................................................86
11.1 .mdb Database .......................................................................................................................................87
11.2 Shared Database ....................................................................................................................................88
11.2.1 Shared Database, multiple Workstations ..........................................................................................88
11.2.2 Separate Databases for each Workstation Instance .........................................................................88
11.2.3 Concurrent Database Access ............................................................................................................89
11.3 PHOENIX (SIRIUS/PERAMIS) .................................................................................................................90
11.3.1 Preparation .......................................................................................................................................90
11.3.2 COPY/MOVE existing Database from Workstation to Network..........................................................90
11.3.3 CREATE new Database on Network..................................................................................................91
11.3.4 OPEN/CHANGE Database .................................................................................................................94
11.3.5 DELETE Database .............................................................................................................................96
11.3.6 UPDATE Database after a Change by another Device ......................................................................96
User Manual
11.3.7 Important Settings ...........................................................................................................................96

11.4 SCOUT ...................................................................................................................................................97
11.4.1 Preparation .......................................................................................................................................97
11.4.2 COPY/MOVE existing Database from Workstation to Network..........................................................97
11.4.3 CREATE new Database on Network..................................................................................................98
11.4.4 OPEN/CHANGE Database .................................................................................................................98
11.4.5 QUICK CHANGE Database ................................................................................................................99
11.4.6 DELETE Database Content ...............................................................................................................99
11.4.7 DELETE whole Database ..................................................................................................................99
11.4.8 UPDATE Database after a Change by another Device ......................................................................99
11.5 IRX3 ..................................................................................................................................................... 100
11.5.1 Preparation ..................................................................................................................................... 100
11.5.2 COPY/MOVE existing Database from Workstation to Network........................................................ 100
11.5.3 CREATE Database on Network ....................................................................................................... 101
11.5.4 OPEN/CHANGE Database ............................................................................................................... 103
11.5.5 DELETE Database ........................................................................................................................... 104
11.5.6 UPDATE Database after a Change by another Device .................................................................... 104
12 TROUBLESHOOTING ............................................................................................................................. 105
12.1 Tips for Failure Cause Research ........................................................................................................... 105
12.2 MEDNET Manager ................................................................................................................................ 108
12.2.1 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 Fileserver Maintenance – Status check, Drive replacement or upgrade ............................................... 121
12.7 Fileserver Drive Replacement or Upgrade ............................................................................................ 123
12.7.1 NAS is Defective – NAS Replacement ............................................................................................. 123
12.7.2 Access Drives Filesystem via Windows ........................................................................................... 123
12.7.3 Drive Replacement / Expand Space................................................................................................ 124
13 SERVER-DATA MAINTENANCE ............................................................................................................ 127
13.1 Backup & Recovery .............................................................................................................................. 127
13.2 Cleanup and archive Work Folders ....................................................................................................... 130
14 IEC 60601-1 3RD NETWORK FAQ ......................................................................................................... 131
15 LIST OF PASSWORDS ............................................................................................................................ 133
CONTACT ADDRESS .......................................................................................................................................... 134
User Manual
PICTOGRAM DEFINITION
The following conventions are used in this manual.
WARNING
This symbol advises the user of serious danger for the patient and the user.
CAUTION
The symbol informs the user that particular care is required for safe and efficient
operation of the system.
IMPORTANT NOTE
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.
CAUTION
Read this User Manual carefully before starting operation of the SCHWIND MEDNET
Solution software.
The present manual is the ORIGINAL INSTRUCTION, which is legally binding.
WARNING
This product is used in combination with other SCHWIND medical products! The
instruction of each product remains valid and is extended by the medNet
documentation.
USER MANUAL STORAGE LOCATION
CAUTION
Please choose an adequate storage location for this user manual when not in use.
All users (“physician” and “IT Administrator”) shall be able to access it at any time
for reading.
Document version 1.9.2, dated 2020-04-20 Page 5 of 135

User Manual 1. General Information
1 GENERAL INFORMATION
1.1 System Identification Data
Product name: SCHWIND MEDNET

Software version: MEDNET Manager V1.9.2
Product description: Network infrastructure platform and software assisted network
management to be used in combination with approved
SCHWIND devices.
Medical device class: - n/a -
see chapter: “3.4
Medical Network Statement”
CE labelling: - n/a -
Allowed device see chapter “System Combinations”
combination:
Manufacturer: SCHWIND eye-tech-solutions GmbH
Mainparkstraße 6 – 10
D-63801 Kleinostheim
Delivery: SCHWIND eye-tech-solutions GmbH, or distributor
Current document status: Document version 1.9.2, dated 2020-04-20
Author: SST
1.2 Technical Assistance / Application Support
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 Application Support

SCHWIND Service Hotline:
SCHWIND Customer Support:
Tel.: +49-(0)-6027-508–333
Fax: +49-(0)-6027-508–245 Tel.: +49-(0)-6027-508–350
Fax: +49-(0)-6027-508–208
Email: service@eye-tech.net
Email: apm@eye-tech.net
Our customers outside of Germany should use the service hotline provided by our local
distributor or authorized service representative first.
1.3 Declaration of Manufacturer
SCHWIND MEDNET has been developed for use in several system combinations with SCHWIND
medical products. For conformity, the “medical network compound” observes relevant
regulations from MDD 93/42/EWG, IEC 60601-1 (edition 3.1).
The conformity with the “medical network compound” is ensured under the following
preconditions:
 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 3rd Network FAQ” for more
information.
1.4 Liability Exclusions
SCHWIND eye-tech-solutions does not assume any liability for:

 Injuries to persons, unless caused by gross negligence of the manufacturer
 Damages of properties
 Damages / destruction of equipment or software.
 Improper use
 Data loss. User is responsible for data backup.
 Financial, legal, commercial and productivity-related disadvantages for the company
and the personal user.
…due to…
 Lack of reading the MEDNET documentation completely and carefully before
starting operations with MEDNET
 Any attempt to alter, modify or manipulate the product in a way not stipulated in the
user manual(s) of SCHWIND eye-tech-solutions
 Lack of understanding the instructions provided in the user documentation, and the
explanations provided by SCHWIND’s application specialists (otherwise contact
SCHWIND’s application specialists for further details)
 Lack of observation of any other instructions and safety requirements provided by
the user information of compatible devices and accessories for ensuring
compatibility and safe operation of the combination between devices
 Use of any compatible device or accessory without having received adequate
inspections
 Insufficient training of the user, which can give rise to human errors when using the
device with the consequent risk of injury to the patient
 Use of the equipment by not suitably trained personnel
 Use of the product for purposes different than its intended use
 Manipulation, alterations or damages by non-authorized person(s)
 Non-observance of the operating notes, warning symbols and safety instructions in
this manual
 Operational error of user
 Computer Mal ware: Virus, Worm, Trojan horse, Spy ware, Backdoor, Ad ware,
Scare ware, Root kit and so on
 Excessive force
 Power failure, voltage fluctuations, electromagnetic interference
 Inappropriate storage of the data medium (i.e. extreme temperature)
 Erroneous deletion of data by the user
 Negligence by the user
 Operating the MEDNET in any configuration not explicitly allowed in the MEDNET
documentation
 Wrong, incorrectness, failure, or missing common security & safety of the “client’s
contributions to MEDNET” (infrastructure/hardware/internet access/LAN cables/…)
 Wrong, incorrectness, failure of network related hardware/software
 Non-observance of the MEDNET workflow or network maintenance
 Acts of nature
The above liability is not valid for damages caused by SCHWIND personnel.
1.5 Warranty
Also refer to General Warranty Regulations of SCHWIND eye-tech-solutions GmbH.

1. Duration of the warranty period for the product is 12 months.
2. The warranty period begins with the first startup of the device after signing of the delivery
note by the client.
3. Warranty includes all defects of the device caused by defective parts or manufacturing faults.
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, …).
5. Damages or malfunctions have to be reported to SCHWIND eye-tech-solutions or to the

representative immediately.
6. The damaged parts have to be sent back to SCHWIND eye-tech-solutions. When returning
defective parts, please use the original packing or coordinate alternate packing with
SCHWIND eye-tech-solutions.
7. Deficiencies that arise from the following will void the guarantee and will relieve SCHWIND
eye-tech-solutions from any responsibility:
 Non-standard or extraordinary use
 Repairs with not allowed parts / Repairs without original parts
 Incorrect treatment of the device
 Inspections, services, device modifications or any form of manipulation of the system
performed by unauthorized personnel
8. SCHWIND grants no other warranty, either express or implied, concerning the above-
mentioned parts and their documentation. Any implied warranties of merchantability and
fitness for the particular purpose are disclaimed.
9. SCHWIND shall not be liable for incidental, consequential, indirect, or special damages of any
kind, loss of information or data, or other financial loss arising from or in connection with the
sale or use of the product, whether based in contract, tort (including negligence) or any other
theory.
10. The above-mentioned exclusion of liability is void if the cause of damage is based on intent
or gross negligence. Furthermore, it does not apply to damage due to lack of warranted
quality and claims under product liability. …
11. Product improvement initiatives based on technological development are not grounds for
free-of-charge system upgrades.
12. The General Conditions for Sale, Delivery and Payment of SCHWIND eye-tech-solutions are
generally to be considered.
1.6 License Agreement
The license agreements realized between the licensee and SCHWIND eye-tech-solutions GmbH
are binding.
1.7 Copyright
Copyright © 2011-2020 SCHWIND eye-tech-solutions GmbH, Kleinostheim

All rights reserved.
The product or pages or parts of this document may not be reproduced or passed to third parties
in any form, i.e. either electronically, mechanically or by any other means without prior written
authorization by SCHWIND eye-tech-solutions.
1.8 Trademarks
All names of other companies and their products mentioned in this manual could be trademarks
or registered trademarks.
Quoting of product names is for information only and does not represent any trade mark misuse.
SCHWIND eye-tech-solutions is not liable for the performance or the use of these products.
1.9 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.
MEDNET NAS Fileserver including 2x drives (HDD or SSD)
MEDNET Router/Switch/Gateway/IP-Server
GBit Switch
Galvanic LAN isolators

(available for for old PanelPC models only)
MEDNET Software Package: MEDNET Manager, MEDNET Print
Webcam and Headset (if available) for Remote Support
*Symbol photo
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
User Manual 2. Hazards and Safety
2 HAZARDS AND SAFETY
2.1 Restrictions of Use
WARNING
Use and operation by trained personnel only!

Only authorized and suitably trained personnel should use SCHWIND MEDNET. The
received training is annotated and must be signed in the 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 & maintenance by authorized personnel only!

Only authorized personnel may perform initial installation, modification, and service.
Room conditions
The respective medical device(s) shall not be installed and operated in locations
where danger of explosion exists or in damp rooms.
Software messages
During operation of the system pay attention to warnings and error messages
displayed on the computer screen.
2.2 Training of Operator’s Personnel
As with any technological highly-developed product, operation requires special training and
abilities of the Operator’s personnel.
SCHWIND eye-tech-solutions or authorized representative will instruct and train the user’s
personnel.
The completion of training for the responsible SCHWIND MEDNET operators and other persons
involved in operation of the SCHWIND MEDNET must be documented in the Medical Apparatus
Book in the accompanying documentation. The Medical Apparatus Book is a part of the
equipment documentation provided by SCHWIND eye-tech-solutions with the device(s).
2.3 Protection from Unauthorized Use
The operator (clinic) is advised to protect all medical devices from unauthorized use, for security,
safety and data privacy reason.
 Security and safety mechanisms of the MEDNET system shall not be bypassed or
removed (software access restrictions; internet control; network infrastructure measures
such as firewall, gateway; …)
 Prevention of unauthorized use of clinic networking devices with network access to the
MEDNET Fileserver.
 For security reason prevent physical access to the MEDNET devices and SCHWIND
medical devices when not in use (security doors; …).
2.4 Data Protection and Data Privacy
The user is obliged to comply with any valid data protection acts, particularly regarding data
transmission to third parties.
When using the Online Remote Services, the connected party will be able to access the PCs
without access restriction. Therefore the client must take care in the decision to grant remote
access or not. The client will be reminded of that issue just before starting the remote connection.
2.5 Virus Protection
The manufacturer guarantees that all SCHWIND products are delivered free of malicious
software.
Use of virus- or other malware-infected media (USB-Sticks, SD-cards, etc.), which could spread
malware to the SCHWIND systems must be avoided.
The user is obliged to regularly check their own computer systems (non-SCHWIND provided
hardware) for possible viruses, Trojans, worms or any other type of malicious software.
The user is obliged to make updates of their malware-protection software on his (own, non
SCHWIND) computer systems on a regular basis.
In this regard, SCHWIND eye-tech-solutions will not assume any responsibility for consequential
damages caused by intrusion of malware to SCHWIND systems.
In case of known infection of respective medical device(s), the user shall inform their authorized
local SCHWIND representative or SCHWIND eye-tech-solutions promptly.
2.6 Electronic Safety on the Medical Device
For electronic safety each MEDNET connected LAN adapter on the SCHWIND medical device
must include a galvanic LAN isolation.
AAEON ONYX 175 (2009-2014)

Advantec POC-174 (2007-2009)
Use the separate galvanic LAN isolator between PC Lan

Port and clinic LAN connection
(P/N: 18800), must be provided for each Panel-PC!
ONYX ZEUS (since 2013)

Separate LAN isolator is not required, because PC has
been build-in galvanic LAN isolation.
WARNING
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.
Note: In case the LAN isolator is missing, check the user manual to determine whether
or not the LAN has a built-in isolator inside the PanelPC. If not, please contact
SCHWIND to obtain this part!
 Workstation with ZEUS PanelPC: Connect the MEDNET network LAN cable directly to
the PanelPC LAN Port 1.
 If AMARIS has a LAN Port at the MAIN SUPPLY UNIT (back side of AMARIS), the
internal LAN cable is not yet connected by factory default. It has to be connected
manually:
1. Power OFF AMARIS and detach from main power cord.

2. Remove cover from MAIN SUPPLY UNIT to reach the LAN Port.
3. Connect the MEDNET LAN cable to the internal +MS-X3 LAN outlet.
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.
2.7 Dangers Resulting from Software Operation
To ensure safe operation of the medical network compound and the medical devices, operate
MEDNET and the SCHWIND medical devices in accordance with their respective documentation!
2.8 Dangers resulting from Network Failure
Dangers resulting of MEDNET network failure are not known.
2.9 Interruptions from Network Operation Failure
In case of network failure, data transfer may not be possible, work on medical device may not be
continued. In most situations, the user can fallback to SD Card instead of network data transfer.
In case the data integrity may be violated in case of network failure, the software would detect
data corruption and does not allow to use the data.
2.10 In Case of Emergency
A case of emergency arising from MEDNET is not known.

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).
User Manual 3. Product Introduction
3 PRODUCT INTRODUCTION
3.1 Overview
SCHWIND MEDNET adds outstanding networking features to the SCHWIND refractive eco-
system.
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:

 Smart network solution: optimum results with minimum effort
 Improved SCHWIND refractive eco-system workflow
 All planning and treatment data is centrally available
 Diagnosis Systems Database stored on the network
 Secure, simple and reliable data storage
 Able to incorporate into existing network infrastructures
 System is quick and simple to install and is easy to operate
 Online remote services are available upon request
 Improved print solution
As an essential core element, the “MEDNET Manager Software” controls and monitors
networking activities while providing users maximum efficiency and convenience in their daily
work.
3.2 Intended Use & Reasonably Foreseeable Misuse
Intended use
IMPORTANT NOTE
 The MEDNET product provides a network platform for SCHWIND medical
devices.
In combination with the SCHWIND medical devices, a “medical Network
environment” has been created.
 The resulting MEDNET eco-system offers sophisticated networking features for

the connected SCHWIND medical devices.
 Central fileserver stores treatment data, system log data and diagnosis system
databases.
 Online remote service for SCHWIND or authorized partners.
 Fileserver data content access for “other” networks, the clinic network, is
allowed by following safety & security restrictions.
 The MEDNET network environment is intended to be a “private” network,

exclusive use for SCHWIND devices.
 The product is operated by the clinic or institution including common service &
maintenance actions to keep the 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:
 It is not allowed to operate non-SCHWIND devices within the MEDNET sub-
net area.
 It is not allowed to install or change the network set up outside the explicit
mentioned system combinations in the MEDNET documentation.
Abbreviating system combination must be approved separately. See chapter
“14 IEC 60601-1 3rd Network FAQ” for more information.
 It is not allowed to use the MEDNET environment (medical PanelPC) for
activities not covered by the intended use. (i.e. internet surfing for reading
news or network games,…)
 It is not allowed to install software not permitted by SCHWIND on the
SCHWIND devices.
3.3 Addressed User Groups
Physicians stay focused on the daily practical work with patients. Technical
aspects on network IT can be put aside.
Users only need to know how to access MEDNET with medical software,
not how it works!
The MEDNET Manager Software facilitates supreme usability covered by

effective & convenient networking functions.
The patient chain: from evaluate  plan  and treat is completely

transacted over the network.
Physician
When critical network anomalies arises, the physician on the PC is
informed immediately and 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.
The MEDNET network is intended to be maintained by the clinic’s own IT

Administrator.
The system is designed for commonly-known infrastructures and

hardware components, serviceable by persons with even basic IT network
skills.
IT Administration The MEDNET Manager includes a real-time network check, displaying all
relevant information at a glance. In the worst-case occurrence of a
“network failure”, it supports fast and easy troubleshooting and problem
solving so physicians can continue with their regular work procedures with
the network use as soon as possible.
3.4 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”!
IMPORTANT NOTE
MEDNET network includes network security measures (firewall, routing, gateway,

NAT, device security settings):
 Within the MEDNET network between the connected SCHWIND medical

devices among themselves
 From external network (clinic-network, internet gateway)
 To external networks (if connected), clinic-network/internet access
Do not violate the following rules, to stay safe and secure:
WARNING
To protect patient/physician and to avoid a re-evaluation of the system compound,

the operator/client easily maintains the overall conformity by following some rules:
 Only the MEDNET specification is explicitly allowed to operate the system.

Implicit derived combinations are strictly forbidden (danger!).
 Combinations are listed in chapter: 4.3 Valid System Combinations with SCHWIND
Medical Devices.
 Combinations are also noted in the respective Medical Apparatus Book of the
SCHWIND medical device.
 Never operate the medical network compound outside the MEDNET

specification. In case, MEDNET is changed (abbreviated to MEDNET/medical
device instructions), new hazards and risk may arise
 The operator/client can change the medical network compound according to the
MEDNET specification in “do-it-yourself manner”, but then he is self-responsible
to maintain the MEDNET specifications.
 The operator/client is advised to check this user manual when maintaining the
network connectivity.
See chapter “14 IEC 60601-1 3rd Network FAQ” for more information.
User Manual 4. Mandatory Prerequisites
4 MANDATORY PREREQUISITES
4.1 Product Responsibilities – Overview
OPERATOR/CLIENT
(or distributor)
Client is IT responsible for network
administration & maintenance of
SCHWIND is Technology his medNet installation:
Together
provider, not IT administrator and
not IT service provider for the Client is responsible keeping the
clinic’s medNet installation network infrastructure running.
Planning,
Installation
Service technical check (safety & Client performs typically required
components, reliability of network maintenance issues on his
First Operation
Fileserver,..) own.
Technical support when operator Client is responsible for “Do it

gets “stuck”; by email, phone, yourself” failure troubleshooting
online remote support and problem solving.
CAUTION
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.
SCHWIND is not IT administrator for MEDNET!
All relevant service and maintenance activities for the involved medical
devices remain valid! MEDNET does not replace them! The actions are
described in the respective medical device user manual.
4.2 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.
The clinic will receive an “Installation requirements document”
containing planning options and contribution requirements to be
fulfilled by the clinic.
B) SCHWIND authorized service personnel approves the “Installation

requirements document”. All remaining open issues must be discussed
and solved.
C) Now it’s time for the clinic to fulfil the requirements in the “Installation
requirements document” till the day of installation.
D) On day of installation SCHWIND authorized service personnel install the

MEDNET together with the clinic’s responsible IT admin person(s).
E) When the network is ready to operate productively in the clinic,

responsibility for the system is handed over to the clinic.
4.3 Valid System Combinations with SCHWIND Medical Devices
WARNING
The MEDNET system combination must maintain its conformity at all times:
Therefore only explicitly allowed and specified system combinations are valid!
Third party devices within the MEDNET network area are not allowed without
additional and individual approval!
MEDNET is allowed to be run with following systems:

(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)
AMARIS Laser System

All Models (A, E, M, S, RS)
Single Workstation
Art. No. 13002 – Corneal WS 230V / Scout
Art. No. 13003 – Corneal WS 120V / Scout
Art. No. 13656 – Ocular WS 230V / Aberrometer (IE)
Art. No. 13657 – Ocular WS 120V / Aberrometer (IE)
Art. No. 13765 – Corneal WS 230V / SIRIUS
Art. No. 13766 – Corneal WS 120V / SIRIUS
Art. No. 13816 – WS PERAMIS 230V
Art. No. 13907 – WS PERAMIS 120 V
Combi Workstation
Art. No. 13008 – COMBI Workstation für Wavefront (SH-OnyxPC) 230V OHNE INSTRUMENT
Art. No. 13009 – COMBI Workstation für Wavefront (SH-OnyxPC) 110V OHNE INSTRUMENT
Art. No. 13626 – COMBI Workstation für Scout/SIRIUS/Keratron 230V OHNE Instrumente
Art. No. 13627 – COMBI Workstation für Scout/SIRIUS/Keratron 110V OHNE Instrumente
Art. No. 13636 – COMBI WS 230V / Scout + Aberrometer (IE)
Art. No. 13637 – COMBI WS 120V / Scout + Aberrometer (IE)
Art. No. 13731 – COMBI WS 230V / SIRIUS + Aberrometer (IE)
Art. No. 13732 – COMBI WS 120V / SIRIUS + Aberrometer (IE)
Art. No. 13908 – COMBI WS 230V / PERAMIS + SIRIUS
Art. No. 13909 – COMBI WS 120V / PERAMIS + SIRIUS
Art. No. 13910 – COMBI WS 230V / PERAMIS + Scout
Art. No. 13911 – COMBI WS 120V / PERAMIS + Scout
Standalone PanelPC
Art. No. 18800
4.4 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.
Several types of network infrastructure are specified by SCHWIND to be chosen by the customer
for best fit into the clinic/practise building. The next chapters will describe possible infrastructure
types and shows generalized examples.
See chapter “4.2 Process: Planning  Installation  First Operation” for the process steps.
IMPORTANT NOTE
Responsibility for the network infrastructure will remain with the operator/clinic.
SCHWIND does not provide IT administration services for the MEDNET.
WARNING
Safety & Security
 Third party network devices (for example “clinic PCs”) are not allowed
inside this MEDNET network.
 It is not allowed to abbreviate the network setup in such a way which is not
explicitly mentioned in this manual or otherwise officially approved!
Network technologies
 Physical connections LAN with patch cable RJ45
 Router/Switch/Gateway Device
 Own subnet; IP via DHCP Server assigned
 File Server NAS: RAID1 (Mirroring. If one HD crashes, the other HD still contains all
data)
 A 1Gbit network infrastructure is required for the Diagnosis Database on the File-Server.
4.4.1 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.
The client’s required effort for preparing the cables depends on the number of devices and rooms.
Example 1
LAN cable
Floor 2 Floor 2
„Treatment Room“ „Server Room“ “medNet Router/Switch”
+DHCP Server
SCHWIND LAN Port LAN Port LAN Port LAN Port

AMARIS
SCHWIND
NAS (Fileserver)
Floor 1
SCHWIND SCHWIND
„Diagnostic Room“ device xy
Workstation #1
Example 2
LAN cable
Floor 3 Floor 3
„Treatment Room“ „Server Room“ “MEDNET Router/Switch”
+DHCP Server
LAN Port LAN Port LAN Port LAN Port
SCHWIND
SCHWIND
AMARIS
NAS (Fileserver)
Switch
Floor 1 Floor 1
„Diagnostic Room 1“ „Diagnostic Room 2“
SCHWIND SCHWIND SCHWIND

Workstation #1 Workstation #2 device xy
4.4.2 Infrastructure Type: “LAN over Clinic VLAN with managed Switch”
The VLAN type requires professional planning by the clinic IT.
If you are not familiar with “VLAN” or you cannot assure the correct configuration of your
managed switches (or layer 3 switch), do NOT choose this type!
The VLAN enabled switch virtually encapsulates different sub-networks using the same VLAN
switch hardware. The networks are not able to reach the other networks running over that VLAN
switch.
SCHWIND does not provide managed switches. The MEDNET connections can be established by
using the clinic’s own managed switches.
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.
The clinic IT responsible person(s) must take care for correct VLAN configuration. It must be
assured at all times that the MEDNET network and clinic network remain separated by VLAN
capability, not reaching the other network.
It is recommended to the clinic to try out a test VLAN network to assure correct operation before
deciding for that connectivity type. There are some VLAN routers on the market which are not
fully compliant to VLAN standard, thus causing problems. If the VLAN does not work for some
reason the MEDNET installation will be aborted by the service technician.
VLAN requirements:
 VLAN switch/ cables/configuration must be contributed and prepared by the clinic!
 Strict encapsulation of the MEDNET network from other networks
 Unique VLAN ID Number reserved for MEDNET
 Port configuration “untagged”
 DHCP is provided by the MEDNET Router (existing dhcp server of the clinic must be
deactivated for the MEDNET VLAN)
 No Port blockings in MEDNET VLAN
Example 1:
LAN cable
SCHWIND Clinic device SCHWIND
Workstation #1 XX AMARIS
LAN Port LAN Port LAN Port LAN Port LAN Port LAN Port
VLAN 3 VLAN 2 VLAN 3
Managed SWITCH clinic
VLAN 3 VLAN 3 VLAN 3 VLAN2 VLAN 3
SCHWIND Clinic device

device xy YY
SCHWIND SCHWIND “MEDNET Router/Switch”

Workstation #2 NAS (Fileserver) +DHCP server
Example 2:
There is only one cable connection between the two floors. New cable installation between the
floors can be avoided by using VLAN.
LAN cable
SCHWIND Clinic device SCHWIND
Workstation #1 XX AMARIS
VLAN 3 VLAN 3
Connection to other
Managed SWITCH #1 clinic

Floor2
floor(s):
Managed SWITCH #2 clinic Floor1
VLAN 3 VLAN 3 VLAN 3 VLAN 3
SCHWIND clinic device

device xy YY
SCHWIND SCHWIND “MEDNET Router/Switch”

Workstation #2 NAS (Fileserver) +DHCP server
4.4.3 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.
4.4.4 Infrastructure Online Remote Support / Clinic Network Access to

Fileserver
MEDNET network infrastructure
LAN Port LAN Port LAN Port LAN Port LAN Port
LAN Port1 LAN Port

SCHWIND SCHWIND SCHWIND SCHWIND MEDNET Router
Workstation X device xy AMARIS NAS (Fileserver) network Gateway
LAN Port2 WAN Port
FILESERVER INTERNET
LINE LINE
LAN Port LAN Port
Clinic network
LAN Port
Internet
Gateway
LAN cable Clinic
PC XYZ
Internet Access for ONLINE REMOTE SUPPORT

The SCHWIND medical devices will have the ability to access the internet. Internet access is
required for online remote support in order to obtain fast response and assistance from
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. (This is normally the case when network PCs are able to access the internet). The
MEDNET router’s Gateway WAN Port must get an IP address from a DHCP Server in the clinic
network.
IMPORTANT NOTE
The SCHWIND medical devices do not offer any type of permanent server capabilities
to the internet. When the online remote support session is initiated the internet
capability is enabled automatically and disabled after stopping. Remote connections
are possible in that timeframe only.
Access to Fileserver from the clinic network

The NAS fileserver centrally stores all treatment relevant files. This includes diagnostic data,
treatment planning and treatment log files from the laser.
The clinic can access the files for its own use and processing (for example, adding to an own
database patient management system for treatment records).
 Separate LAN cable is connected from fileserver to the clinic network.
 The connected fileserver’s LAN Port to clinic should get an IP address from a DHCP
server in the connected clinic network.
 Fileserver Network service by Microsoft File sharing/SMB or FTP to be connected from
the clinic network.
4.4.5 Satellite Clinic Infrastructure
Satellite clinics spread over several locations are connected together into one huge clinic intranet.
This is typically established by connecting all the clinic networks together via a VPN over internet.
Another short description is “one large clinic intranet including all clinic locations” or “Intranet
with different locations spanned together” and sometimes “Extranet” (word is not fully correct
in this purpose).
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 – Fileserver Name
9.4 Satellite Clinic – Best Practise
CAUTION
If the clinic is planning some sort of satellite clinic connection without having the
technical infrastructure available, consult an external IT service provider for planning
and installation. SCHWIND cannot assist you here and can only provide the
technological instructions. It depends completely on the clinic to fulfil the technology
requirements.
If the clinic’s IT administration is not able to manage the technical and operational
fields, do not use satellite connections.
Satellite clinic connections are possible as follows:
 The MEDNET Fileserver must be connected to the clinic network as described in
chapter:
„4.4.4 Infrastructure Online Remote Support / Clinic Network Access to Fileserver“
 Clinic intranet/satellite connection network must exist. Technical solutions are: “VPN” or
a “MPSL meshed network” by a network solution / telecommunication provider.
 The MEDNET Fileservers must be “reachable” by IP or computer name from the
workstation PC in the clinic network. (Depending on the own clinic network
infrastructure, specific network configuration changes might be required! A professional
IT administrator will be able to do this.)
 MEDNET Fileserver access is possible by Microsoft Network File sharing / SMB or FTP
or http Web frontend.
 Satellite clinic transaction: Now a Workstation PC in the clinic network can access the
source fileserver at location –A- and copy/move the treatment relevant data to a target
fileserver at location –B-. Refer to chapter “9.4 Satellite Clinic – Best Practise” for details.
 Please contact SCHWIND for additional information and provide some information of
your integration plan.
Notes:
 It is not possible to access the MEDNET medical devices directly. The fileserver in each
MEDNET is always the “interface” to the MEDNET!
 It is not possible to use one MEDNET Fileserver for all clinic locations!
 It is not possible to perform the “Satellite clinic transactions” on a PC within the
MEDNET!
Clinic location #1: “Frankfurt”
medNet Network clinic Network

Infrastructure + SCHWIND devices: Infrastructure
Cabling/Amaris/Workstation/ + clinic devices
Fileserver/medNet Router/…
INTERNET
Clinic location #2: “London”

Clinic location #3: . . .

Satellite clinic data transmission is “One large clinic intranet for all locations”
executed from PC in clinic network. with intercommunication over internet
The clinic network accesses the medNet / Intranet VPN tunnel over Internet
fileserver(s). Clinic must provide the infrastructure,
without SCHWIND responsibility.
User Manual 5. Physician’s Best Practices
5 PHYSICIAN’S BEST PRACTICES
This chapter gives common understandings and base strategies of the

MEDNET within daily productivity!
The following best practices assume a properly running network
infrastructure.
CAUTION
All MEDNET users, physicians and IT administrators shall be familiar with the
information in this chapter to guarantee safe and efficient operation of the MEDNET
enabled medical devices!
For understanding this chapter, you should be familiar with the SCHWIND medical
device treatment workflow!
The file server is the central point of all treatment relevant data for storage and data exchange.
At each stage within the treatment workflow, a file is either saved or loaded. A network
transaction from one medical device to another medical device is always carried out via the file
server.
The fileserver must always be powered on for serving the saved content to the other medical
devices. 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.
When the common MEDNET rules are ignored, the practice work can result in:
 Missing project files when spread over unknown or random locations or filed
under ambiguous project file names.
 Treatment of a wrong project on a patient when the patient name is ambiguous
or the project has been saved with an ambiguous name.
 Significant workflow time delays when searching for a specific project file or a
project’s current state is unclear.
 Wrong patient outcome.
Common Rules
The user can easily follow the rules by simply clicking on the <save> button
without modification of the filename or path. For loading, the correct network path
is also remembered and opened.
In case the network is not available, the loading dialog will jump to a local folder.
Then the network has to be chosen once the next time in the file dialog.
Avoid saving to self-created directories and changing suggested saving of names.

This might lead to confusion for other users.
Rationale
All software products provide automatic saving of names including:
ID, Last name, First name.
 The default saving target locations are configured in the software products.
Recommended treatment-software settings are listed in chapter ”7.2
TREATMENT Software - Settings”.
 The file saving syntax order can be configured in the software products. It
must remain the same in all products.
The user can choose between:
“[ID]_[Last name]_[First name]” and “[Last name]_[First name]_[ID]”
Recommendation: Use the one with ID in the first position.
 In all software products always enter valid and unambiguous patient data
Last name, First name, ID, gender, date of birth
 Automatically-suggested saving file or project name shall not be changed.
 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.
5.1 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!
Workstation#1
Amaris #2
Workstation#2
File Server
Amaris #1
A defined directory structure on the File- Server

is recommended and obligatory for all Users!
Workstation#3
Same subdirectory for all Diagnostic Exports

from the Software:
SIRIUS/PERMAMIS/SCOUT/IRX3.
All files are stored on same directory level. A

file dialog uses filtering by extension to
display relevant files only.
The sub-directory contains the CAM project

files. For each patient a separate sub-folder
will be created and can contain additional
sub-folders.
Subfolders are oriented to device serial

containing several types of system log files
and Treatment (evidence) log files. The last
folder level contains single files.
This subfolder’s content is not relevant in the
physician’s workflow.
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.
5.2 Dataflow
1
2
WORKSTATION
Creating diagnosis data Loading diagnosis
into CAM Project
Saving diagnosis STANDALONE PC
Planning Treatment
Saving CAM Project
FILESERVER
auto Saving
Logfiles Loading and saving
CAM Project
Loading
3
CAM Project
AMARIS Workstation
Treatment some parameters are
changed in a CAM Project
1. A patient is initially “scanned” with the diagnostic software. Then the “SCHWIND Export”
is created and saved to the MEDNET location for the appropriate diagnostic device.
2. In the SCHWIND CAM, the previously created diagnostic data is loaded from the
MEDNET into a newly created CAM project. The CAM treatment project is then saved to
MEDNET.
In this example a Standalone PC is used, but other CAM Software-enabled devices are
also valid, for example, using the CAM Software on the diagnostic workstation.
3. In this example the CAM project is changed on the Workstation. The CAM project is re-
loaded from 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. The CAM treatment is loaded from MEDNET by AMARIS Software. Patient is treated. The
resulting treatment (evidence) log files are saved to the MEDNET automatically.
5.3 SAVING/LOADING within Treatment Software
All software, using file access for loading and saving, can access MEDNET Server data.
MEDNET Manager Software automatically creates shortcuts to access data quickly. Navigate to
the location and the corresponding directory structure behind...
In Windows File-Explorer or any other type of file dialog, watch out for MEDNET icons. If MEDNET
Manager is not running, the links are not available.
MEDNET Server is accessed directly, read/write permission. It represents the mounted MEDNET
Server directory share.
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.
Use this direct access for loading any type of files in the Diagnosis or treatment Software.
It is assumed, the Server contains the latest data required for the treatments (when network is
online for all systems).
When saving files, direct access over this link can be used, but it is not recommended! Use the
“delegate folder” instead.
Diagnosis database on the network must point directly to server for load and save.
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.
Collected files inside the delegate folder are automatically transferred to MEDNET Server by
MEDNET Manager. The process is triggered automatically after some seconds of last save
activity. After transfer, the files are removed.
In case the MEDNET Server is not available (offline, broken connection), transfer to Server is not
possible, but collecting more files remains possible. Amount of files is increasing.
When MEDNET Server is back online, the files of the delegate folder are automatically transferred
to Server. Delegate folder is cleaned.
As a safety mechanism, the files are not deleted from delegate. They are moved to the local
“archive Folder” for later reference, if required.
Delegate folder copied date “one-way” to server only. There is no copy-back from server.
The folder can be used for saving data only, saving treatment exports.
A Database of the diagnosis systems cannot use the delegate folder, because of read/write access
to the online database.
Treatment files
SCHWIND CAM
Sirius/Peramis Saving with via
IRX3 “Delegate Folder”
Scout
Direct network access:
SCHWIND CAM Loading from Server

SCHWIND AMARIS
Load and save
Database
Online access required
(delegate not possible)
Saving and loading path in the software products must be properly configured. This
is normally done by Service or Customer Support personnel:
 Saving location must point to the local folder: “DELEGATE to medNet”
 Loading location must point directly to the network: “medNet Filestorage”

and its respective sub-directory
In the daily workflow usage by physicians, they just have to click <Save> in the saving
dialogs. 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.
Now the user can use an SD card:
A) Collect the required file(s) from the device which originally created those
files (by looking inside the “local ARCHIVE” folder)
THEN load those files onto the currently used device from the SD card.
or
B) If the network is still available on another PC, you can copy the required
files from the network to the SD card (instead of the “local ARCHIVE”
folder)
THEN loading those files on the currently used device from the SD card.
When using files from the “local ARCHIVE” folder the user must ensure those
files are the right versions and have correct data! In case another device also
generates those contents, this device also must be checked for the latest file
versions.
The next sub-chapters describe how to use the MEDNET folder mechanisms in the medical
Software, involving the delegate folder.
5.3.1 WORKSTATION: PHOENIX Software – SCHWIND Export

SETTINGS
It is recommended to fix export path:
In the Software Settings you should configure default Export path.

Point to \medNet SERVER\DIAGNOSTIC_Export
( Y:\DIAGNOSTIC_Export )
SAVING Diagnosis Images / 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.
SAVING 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.
5.3.2 WORKSTATION: Scout Software – SCHWIND Export

It is assumed, the software is configured according “7.2 TREATMENT Software - Settings”
SAVING Diagnosis Images / SCHWIND Export
Point to D:\DIAGNOSTIC_Export
Please notice, to use D:\ . There is no “delegate folder” link.
5.3.3 WORKSTATION: IRX3 Software – SCHWIND Export

SAVING 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.
5.3.4 WORKSTATION: CAM Software, CAM Projects

Saving Planned CAM treatment = Creating SCHWIND Export
From CAM Summary page, save treatment… Save into

\medNet DELEGATE to SERVER\SCHWIND_CAM
LOADING/IMPORTING Diagnosis Image to SCHWIND CAM Project
Load all type of Diagnosis Images from:

\medNet DELEGATE to SERVER\DIAGNOSTIC_Export
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.
LOADING (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)
5.3.5 AMARIS: Application Software, CAM Projects / Treatment log / etc

AMARIS, Application Software - CAM

LOADING/IMPORTING a CAM Project
LOADING/OPENING CAM Project

Load the CAM Project from:
\medNet SERVER\SCHWIND_CAM
Choose the appropriate patient’s sub-folder (name/id)
AMARIS, Application Software - CAM

SAVING 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:
CAM Project
Treatment PDF printouts
Treatment Logdata
System Logdata
Digital Video record
User Manual 6. MEDNET Manager - Overview
6 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.
The MEDNET Manager will guide the physician’s network activities on the daily productive
workflow with patients and includes outstanding countermeasures to keep the workflow alive,
even in a worst-case scenario with temporary network failure.
Besides the feature overview listed in chapter “3 Product Introduction”, the MEDNET Manager
main features for productivity purpose and maintenance & service purpose are:
 Automatic access binding of the central file server to the medical PC system.
 Convenient and safe handling of pending network transactions.
 Real time network anomaly detection with immediate user notification at the “earliest
time” possible.
 The notification includes tips on anomaly removal and behaviour recommendations to
keep the on-going workflow alive.
 Real-time network infrastructure check
 Set of effective network tests tools
 Online Remote Services for PC access over internet by SCHWIND or partners
 Automatic data management
Intuitive Design
MEDNET Symbols:
When you see one of these icons, you can expect a network related function: In daily use, a
trained user usually stops reading all texts and descriptions. The screen is “scanned” rather than
read completely when choosing the next task. The MEDNET icon and its abbreviations improve
that behaviour in an easy to remember manner.
6.1 Software Start-up & Shutdown
There is no user action required for the start up or shut down process.
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.
6.2 User Interface & Status View
open logfile folder
open pdf manual

show pending terminate Manager
notifications
miniminze Manager
workspace area
category
show/hide log Realtime status view
The status view contains the most important states of the MEDNET Manager network functions.
The status view is refreshed in short intervals (~1 minute).
LED indication: • (green)=OK • (grey)=not active • (red)=failed/error
6.3 Diagnosis View
IMPORTANT NOTE
When something is wrong with the network, the MEDNET Manager DIAGNOSIS
screen should always checked first! It provides the most important details on the
network in view of the actual computer!
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).
MEDNET Manager - Diagnosis screen:
6.4 Popup Notifications
MEDNET has a built-in rapid warning system for network failure detection. The user
is informed as early as possible by a small notification popup right after a network
anomaly has been detected. The responsible IT administrator can be informed as
early as possible for immediate repair.
Without it, the user would first become aware of a network failure at the latest time,
when the current required network action fails.
The popup always appears on top of all other windows, independent of the currently used
software product, and remains in the foreground until you click HIDE or read the notification.
The notification contains errors,

warnings and hazards regarding the
network.
It also includes important information

on the detected failure and gives
advice to physicians and IT
administrators.
Example screenshot
To maintain the practical workflow as best as possible, the physicians should follow
the advice in the popup notification. The Instructions also include intuitive
workaround suggestions where available.
In most cases it is possible to continue with real work on patients without
significant interruptions. The instructions try to keep the physician “away” from the
offline network while the problem is being repaired by the IT administration.
Pending notifications can be displayed with click on the button:
 With <close> the notifications are discarded and are not displayed again.
 Notifications are stacked when more than one is available.
 Popup can be disabled in the Settings (not recommended).
 AMARIS Application Software: Performing a laser treatment is quite important. In case
the Application Software enters the Treatment Menu, all displayed notifications are
removed automatically or suppressed when they occur to avoid any interruption of the
treatment progress. When the Treatment Menu is left, the notification will appear again.
6.5 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>

The MEDNET Manager can be accessed easily by pressing <F4> on the keyboard, independent
from currently used software! This makes it most comfortable for accessing the functions in the
Manager window.
User Manual 7. Software Configuration
7 SOFTWARE CONFIGURATION
Before start using MEDNET, Software must be installed and configured properly. MEDNET
Manager Software is mandatory for all SCHWIND PCs. AMARIS uses Application Software and
WORKSTATION is using the diagnosis software if diagnosis device is present.
7.1 MEDNET Manager - Settings
You also might have to change settings after an infrastructure change or for maintenance or (at
least) after a new software installation.
MEDNET Manager startup initialisation fails at first after installing the Software. A proper
configuration is required.
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. The default setting is ON.
Do not set it OFF permanently, otherwise the user will not prompted of occurring network
problems and the they will notice a network problem at the latest possible time (for example:
when saving to network) instead of the earliest possible time by the popup notification!
7.1.3 Device Type and Name
The correct basic system information is required. Ensure the correct setting here!
 Choose the device type of the current machine: AMARIS or WORKSTATION
 Enter the system serial number. This name will appear on the network! Never use a
name twice! The name must be unique! Notice the included text and serial number
locations for examples.
The input field rejects invalid characters. Length is limited.
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: MEDNET-SERVER or abbreviated name if changed manually OR IP: 192.168.141.99
With introduction of MEDNET Revision of 2019, the default configuration is “fixed-IP”. With
previous Revision/Models, please check if fixed IP is already set and set Fixed IP according the
chapter: “12.3 Using fixed/static IP for Fileserver”.
CAUTION
 In case the Phoenix Software -Database is moved to Fileserver, the fixed-IP
is mandatory. See chapters: ”11.3 PHOENIX (SIRIUS/PERAMIS)” and “12.3
Using fixed/static IP for Fileserver”.
 If multiple MEDNET Servers are connected to a clinic (satellite), consider

chapter: “7.4 Satellite Clinic – Fileserver Name” to avoid name conflicts.
7.1.5 Internet Access & Proxy Settings
The attached “foreign clinic network” is used for internet connectivity, provided for the MEDNET
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.
Internet Control & Check

The default state is always “DISALLOWED”: Internet access or access to the foreign network is
enabled automatically when online remote support is started. This state is obligatory when
treating a real patient!
Clicking the DEFAULT STATE button will set the DISALLOWED state.
For service & maintenance issues, the internet access can be enabled by different types:
 UNTIL NEXT REBOOT OR MEDNET MANAGER START
State “disallowed” is set after PC reboot or manual Manager close + restart
 THE CURRENT DAY
State “disallowed” is set when PC stats the next day.
 PERMANENTELY ENABLED
State is never set back automatically!! For safety, you need a password (ask Schwind if
required, however Schwind will ask for reasons ;-) )
Test & Proxy configuration

You must ensure a working internet connection via HTTP for online remote access!
For testing the internet connectivity enable internet access with THE CURRENT DAY button first,
and then use the OPEN TEST URL button or Internet Explorer with any Internet www page.
When you are finished set the default state back to Disallowed.
Does the clinic provide the network via Proxy server? If yes, set your individual parameters:
1. Open the IE PROXY CONFIGURATION
2. “Internet Properties” will appear. Now open the LAN SETTINGS.
3. Enter your proxy settings. You might also use the ADVANCED options.
4. Test your settings if you get an internet connection!
7.1.6 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.
All LEDs green to indicate OK state? If it is red (failure), check the configuration and the
network.
7.2 TREATMENT Software - Settings
IMPORTANT NOTE
Please set the following settings for medical-software on all single PanelPCs.
The path settings are important for fluent work. When saving/Loading the correct
mednet path is pre-selected.
You have to set each single software product, even in case you have to repeat the
same steps multiple times for different Computers.
WARNING
Read all information and perform the correct configuration!
 Choose a “File name format” for the automatic CAM project file naming
which fits best to the clinic’s demands:
PatientID_Lastname_Firstname is recommended
To avoid ambiguous double saved projects (each name format once), it is
important to set all available Workstations and AMARIS configurations to
the same “File name format”.
 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.
For IRX3 Software (unfortunately) fixating the path is not possible. Restart
the software will cause fall back to a default path.
7.2.1 WORKSTATION CAM Settings

File name format: Set to” PatientID” at first position
File Path
Enable user defined path.
Y:\DIAGNOSTIC_Export
D:\FILES_DELEGATEtoMEDNET\SCHWIND_CAM
D:\FILES_DELEGATEtoMEDNET\SCHWIND_CAM
Y:\SCHWIND_CAM
Set “Custom” to enables a

user defined path
CAM Project File: saving and loading path.
Saving/Export folder is the local MEDNET_delegate\SCHWIND_CAM
folder, whereas Open is pointing directly to medNet Server.
In the directory dialog, select the medNet Links and confirm.
Diagnostic Export files / Scans are saved altogether into same directory. Source
directory must be set to same directory. The open dialog is filtering the file
types by its extension.
D:\FILES_DELEGATEtoMEDNET represents the Delegate folder root, which holds data on the
local drive, then copied to Server from mednet Manager Software. Y:\ represents direct root
address to the mednet Server, for loading data directly from Server.
7.2.2 AMARIS Application Software Settings

Settings Menu
 Standard filepath for Import CAM Files:

Select MEDNET_SERVER\SCHWIND_CAM (“Y:\SCHWIND_CAM”)Folder and confirm
(Loading directly from MEDNET-Server)
 Default Save format for cam should be “PatientID_LN_FN”.
Enable user defined path.

integrated CAM - File Path
Save/export/open not required, this is handled from AMARIS

Application Software
D:\FILES_DELEGATEtoMEDNET represents the Delegate folder root, which holds data on the
local drive, copied to Server from mednet Manager Software. Y:\ represents direct root
address to the mednet Server, for loading data directly from Server.
7.2.3 WORKSTATION Phoenix Software Settings

Setting for local drive only (non- …change to MEDNET Setting:
mednet)… Enable: SCHWIND interface and Fixed export path
Export filename: ID_Surname_Name
Export path:
D:\FILES_DELEGATEtoMEDNET\DIAGNOSTIC_Export
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.
 Limit the Max exams returned to 100
 Disable the backup: set to 0
If backups are from multiple software installations at same time, this causes software error
and SW will exit.
 Optionally only one Software installation is allowed to create backup. Set to backup path
either to a local PC directory or to subfolder \bak of the File-Server DB location.
7.2.4 WORKSTATION Scout Software Settings

Use windows-explorer, go to directory C:\Keratron and double click file or right click on file, “open
with”… Notepad.
Change ini file C:\Keratron\scout.ini
Section: [ORKCAM]
Existing line: OutputDir=[path]
To Line: OutputDir=D:\FILES_DELEGATEtoMEDNET\DIAGNOSTIC_Export
Ensure to input correct path. Don’t change other parameters.
7.2.5 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
7.3 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.
 Create the new structure for DIAGNOSTIC_Export and SCHWIND_CAM directories. Other
directories are not relevant. (AMARIS “internal” SCHWIND CAM, saves project to
medNet_Server:\SCHWIND_CAM. This cannot be modified.)
7.4 Satellite Clinic – Fileserver Name
Consider this chapter in case “MEDNET satellite clinic” connection.

CAUTION
Do not make changes in the fileserver settings unless necessary. When the change
is required, follow the instructions exactly.
After the fileserver device name has been changed, it must also be changed and
entered in the 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
unique!
When the device names are not changed and another device still has the same device name,
problems will occur in the network!
For more information on a satellite network refer to chapters:

4.4.5 Satellite Clinic and 9.4 Satellite Clinic – Best Practise
Name change
1. Point to your MEDNET server with Internet Explorer web-browser
http://mednet-server (or old name: http://sets-fileserv)
or http://mednet-server:8080
or http://mednet-[other name]
or http://[IP instead of name]
Login: admin Password: elvis222
If you can’t establish the connection, try the URL with port number “:8080” or check your
proxy settings. Disabled proxy settings might be temporarily required.
2. Go to “SYSTEM ADMINISTRATION | GENERAL SETTINGS”
3. Change the SERVER NAME to your name (name is not case sensitive).
Use the prefix “medNet-“, add your clinic location for the unique naming part.
You can enter seven additional characters: medNet-1234567
4. Do not change any other setting! <APPLY> to save, and then leave the browse
User Manual 8. Online Remote Services
8 ONLINE REMOTE SERVICES
MEDNET includes outstanding online remote support integration for real-time service & support
over internet with SCHWIND, your distributor or for your own clinic purpose.
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. A clinic network must provide the internet
gateway, connected to MEDNET-Router (WAN Port). See chapter “4.4.4Infrastructure Online
Remote Support / Clinic Network Access to Fileserver” for infrastructure requirement. Establish
the internet connections.
SCHWIND medical device

remote supported device
controlled by the supporting
remote partner Other medNet devices
MEDNET Network infrastructure
Network gateway
Other clinic devices

Clinic Network infrastructure
Network gateway
Team Viewer
Mediation Server
Internet
Other devices
Network gateway
Network infrastructure remote partner
Remote partner
support assisting and controlling
the SCHWIND medical device
Note: The feature depends on network infrastructure, internet availability, TeamViewer mediation server
availability and the internet speed of the clinic. The connection cannot be guaranteed but shall be possible
in most cases.
Purpose
 By starting the remote session, an invited person can see and control the SCHWIND PC
as if being behind the screen. Connections via Internet can be established across the
world.
 For service and support assistance activities with remote personnel
 Very easy to establish the remote session of all SCHWIND device users
 Best reaction time possible
 Besides telephone, alternate communication is also possible via web camera, audio
(headset), chat (typed keyboard text).
Requirements
IMPORTANT NOTE
 Internet is required to be accessible via the MEDNET. The network
infrastructure must be set up properly as described in this manual
 Web camera and headset for audio are optional but recommended.
 The clinic IT administration has to ensure the correct infrastructure and

internet settings in order for MEDNET to access the internet!
 It is recommended to provide a stable internet connection for the sudden

case a remote connection is requested.
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
 It is important not give remote access to unknown or distrusted or untrained
personnel! Only persons who have your PC’s ID can access for the time the
session is initiated.
 The remote session must be initiated by a person on the MEDNET PC,
requesting a remoter partner for remote assistance!
Access from outside is never possible without “manually granted
permission”!
 Do not use a remote session during a treatment on a real patient!
 Data privacy statement: When the remote session is established the remote
partner sees all data on that PC and is able to do everything on the computer
as if being directly behind the screen!
 It is recommended to survey the activities of the remote partner.
 MEDNET Manager is designed to control the Internet access by default. The
internet capability is enabled automatically when the session is requested
and disabled at the end.
 It is possible to download the treatment related files.
8.1 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.
Choose Tab <Online support>
Button <START> opens the remote

connection tool. Please be aware of the
disclaimer.
Internet access is enabled by MEDNET

Manager.
TeamViewer START
After a few seconds “Your ID” is displayed
for the computer.
YOU MUST PROVIDE THIS ID TO YOUR
REMOTE PARTNER!
Once an ID is assigned, it will remain the
same for that computer and will not change
in the future.
The Password is predefined and cannot be
changed. (Your authorized remote partner
already knows the correct password! If it is
required for your own purposes contact
SCHWIND.)
In case internet is not accessible for some

reason, your IT administration has to check
the connectivity to the Internet!
The remote session will not be possible
unless the problem has been solved!
TeamViewer configuration (if required):
TeamViewer uses the Internet Explorer
Internet settings automatically.
(For MEDNET internet access the IE proxy
settings must be configured there when
required by the clinic network.)
Web camera/Headphone source:
It might be necessary to set the devices for
later use.
TeamViewer END
Click <Cancel> Button in MEDNET Manager
or “close session” <X> in the App.
Close
Enable/Disable/Settings
Minimized/Maximize
for Video/Chat/Voice
8.2 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.
Due to safety & security reasons, TeamViewer must not run as a permanent service on the
medical PC. Access must always be activated manually by a user.
Requirements:
 Establishing the connection always requires an active internet connection for both
partner due to the need to access the TeamViewer mediation servers.
Note: It is not possible to establish the connection from clinic network directly to the
MEDNET device without internet access!
 The clinic PC must download the TeamViewer Tool (V7 or later). Installation version or
portable versions are possible. Download from: http://www.teamviewer.com
Connection:
1. In MEDNET Manager enable the remote connection as described in the previous
chapter.
2. On the clinic PC TeamViewer, enter the TeamViewer ID of the medical PC.
3. The password is pre-defined on the MEDNET TeamViewer Version.
Password: elvis111
Enter it when questioned on the clinic PC.
8.3 Using Web Camera and Headset
IMPORTANT NOTE
Web camera and the headset are included in the MEDNET package. Place them near
the devices so they will be ready when needed for the remote session.
The video and audio capability depends on Internet speed. In case the speed is too poor it is
recommended not to use the function. A real telephone can solve audio issues.
Web-Cam connection:
Connect it to a free USB interface on the

PanelPC. There are no additional drivers
required. Windows recognises it
automatically
Headset connection:
The PanelPC contains Audio out/in for the

Headset. They are located somewhere on
the housing (bottom).
Green connector Red connector Plug in the headset’s connectors.
or plug with or plug with
Headphone Symbol Mic Symbol
Enable Video or Audio only. You can mute

Microphone and set volume. The gear icon
shows additional options.
User Manual 9. Fileserver - Access from Clinic Network
9 FILESERVER - ACCESS FROM CLINIC NETWORK
WARNING
 Only use the MEDNET Fileserver access if you know what you are doing! The
MEDNET installation must retain its conformity, so do not make any modifications.
 Use READONLY access credentials if write is not required.
 Use ReadWrite access temporary and only for....
 Maintenance actions (file clean-up, moving old project files,…)
 Satellite clinic: copy new project files to target File server to the correct
directory.
 It is forbidden to modify the file’s content with third party programs (Notepad,…)
 Correct use and misuse by third person remains in the clinic’s responsibility!
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.
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.
MEDNET Network Clinic Network

MEDNET Fileserver with two LAN interfaces: PC within the clinic

LAN1: Connected to MEDNET network accesses the
LAN2: Connected to clinic Network MEDNET Fileserver.
LAN Connection between MEDNET

fileserver and clinic network
Accessing the MEDNET content from clinic network is optional. Use only if clinic requires
the access.
Login / Password: See chapter “15 List of Passwords“
9.1 Fileserver - Content

IMPORTANT NOTE
The clinic can “grab” the available treatment or system relevant files on the file
server for its own purposes. For example: loading the treatment evidence logs,
extracting information for a third party patient management system.
The clinic can process all files with its content for any purpose!
SCHWIND cannot offer individual (software) changes! It remains on the clinic to

process the files correctly for their own purposes!
\medNet_Projects
 Diagnostic data export (partly includes a bitmap screenshot; binary data is not readable)
 SCHWIND CAM Treatment projects
 AMARIS Treatment logfiles
 AMARIS Treatment printout as pdf
 AMARIS system logfiles
 AMARIS Digital Video Records (if applicable on AMARIS)
 PDF printouts generated by MEDNET PDF printer
9.2 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
Clinic may require access to the \PDFPrint sub-directory only, instead of the whole “Projects”
content, for security reason. The clinic can copy the PDFs easily to their digital patient
management system as an evidence document.
ReadWrite access is most often required, because of removing or moving the file after
processing.
The PDFPrint directories with files should be cleaned-up regularly. Either deleting files or
moving to an archive directory. You can define an archive sub-directory within \PDFPrint or
\PDFPrinter\pending directory.
The clinic network is connected to 2nd LAN interface of NAS. Only PDFPrint directory is mounted
from external network.
Method A - \PDFPrint ReadWrite

For use with QNAP NAS TS-253Be (MEDNET Revision 2019) or later.
A new special NAS credential is available, which points directly to the \PDFPrint sub-directory.
(User: setsPDF, Password: T7bza8)
Mount as persistent drive letter for security reason. The password remains saved within the
windows system and is not exposed. The command line is required only once.
Windows command line example to mount \PDFPrint , READWRITE permission:

net use R: \\mednet-server\medNet_PDF T7bza8 /user:setsPDF /persistent:yes
Drive letter R: is used with persistent drive letter. It remains after reboot.
In case the pending Subdirectory shall be mounted, use:

net use R: \\mednet-server\medNet_PDF\pending T7bza8 /user:setsPDF /persistent:yes
Note: Access to /printed and /failed is not possible.
For mount on a MacOS, do it the same manner.
Method B - \PDFPrint ReadWrite

For use with MEDNET QNAP NAS delivered till 2018.
For mounting the \PDFPrint sub-directory, the Credential for the whole Project Folders must be
used. This increases hazard, because of full access whole clinical data.
Therefore, the mount must include the sub-directory.
Mount as persistent drive letter for security reason. The password remains saved within the
windows system and is not exposed. The command line is required only once.
net use R: \\mednet-server\medNet_Projects\PDFprinter [password] /user:setsAmaris

/persistent:yes
For safety and security reason, the password if delivered by Schwind upon request. Do not
mount to the root folder \medNet_Projects permanently.
Method C - \PDFPrint ReadOnly

Mount the directory with READ only permission:
net use R: \\mednet-server\medNet_Projects\PDFprinter R8HBhE /user:foreignUser
/persistent:yes
For safety and security reason, it is not recommended to mount to the root folder
\medNet_Projects permanently.
9.3 Fileserver Access – Protocols & Accounts
The fileserver provides the following directory shares and users. Access is possible via Microsoft
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:
 via the “Computer name”: The default name is “medNet-server” For satellite clinics the
file server might be renamed to a unique name: “medNet-[Locations]”
Important Note: Computer name resolution is possible in the current sub-net only. For
satellite clinics, IP address might be the better way because File servers of other
locations might not be visible in the Windows computer browser.
 via IP-address. Note: By default the IP address is requested by an DHCP Server in the
clinic, it could change! The clinic’s DHCP Server might be able to be configured to fix
the file server IP at all times!
Directory shares / accounts

CAUTION
Use READWRITE permission from non-mednet-Networks very carefully!
When the clinic network is connected to MEDNET Server, you may require readwrite
access for some reason… Set your access READWRITE only for the time, the access
is required. It is highly recommended to disconnect READWRITE mounted directory
share to the MEDNET Server after use!
This is a precaution against virus hazards.

A worst case scenario: Ransomware, running on clinic PC, could encrypt the
MEDNET server data, blackmailing the clinic to send you password for much
money... (You don’t want that.)
Always consider the use of READONLY access instead of READWRITE. Use

mount/dismount command line arguments to quickly connect or disconnect the
network share.
Consider backup strategy as noticed in chapter 13 “Server-Data Maintenance”
Microsoft Windows Network / SMB (= Directory sharing)

You can mount the share via “net use” or with Windows file explorer: “Map network drive” or
Windows File explorer: “Microsoft Windows Network Browsing”
Commandline:
net use [drive-letter]: \\mednet-server\medNet_Projects\[Subfolder] [password] /user:[user]
/persistent:yes
 If mounted via net use with drive letter and persistence, the user/password are stored into
the system via commandline entered only once.
 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 FTP protocol, Port: 21
User accounts for MEDNET_Projects as described and for MEDNET_PublicShare use Login:
anonymous without a password. The directory shares are displayed according the user logged
in.
“Filezilla” is a very good and
free ftp tool!
IMPORTANT NOTE
Windows does not include a feature to mount a ftp account into a drive letter. Third
party tools like “Netdrive” are able to do this!
WebInterface via Browser

http://[Fileserver name or
[IP]:8080/cgi-bin/filemanager/
https:// [Fileserver name or
[IP]:443/cgi-bin/filemanager/
User accounts for MEDNET_Projects
as described and for
MEDNET_PublicShare use Login:
guest without a password. The
directory shares are displayed
according the user logged in.
Using Third party tool: NetDrive
There are also tools available which can mount an FTP share permanently as a drive letter (for
example: “NetDrive” from http://www.netdrive.net
IMPORTANT NOTE
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.
9.4 Satellite Clinic – Best Practise
Clinic location #1: “Frankfurt”
medNet Network clinic Network PC A

INTERNET
Clinic location #2: “London”

PC B
Clinic location #3: . . .

Fileserver/medNet Router/… PC C
“one big clinic intranet” with

intercommunication over internet
/ Intranet VPN tunnel over
Internet
The Infrastructure setup enables “data transmission” from a MEDNET fileserver on a location #1
to another MEDNET fileserver on location #2.
For example, when the diagnosis data was obtained in Frankfurt and then the laser treatment is
executed in London. The necessary project files are first stored in “Frankfurt” and then copied
digitally over the network to “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 C.
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” the according MEDNET fileservers!
The work process should be established by the clinic IT administrator or IT team and then handled
by that trained person. The process requires enabling the read and write access to the involved
MEDNET fileservers as described above. It is recommended to enable read access for the source
and ReadWrite for the target file server only!
User Manual 10. Printing
10 PRINTING
On the PanelPCs, the Windos Printer “Print to medNet” creates PDF files
from printouts and stores them on the medNet Fileserver.
The generated PDF files can optionally be printed on real paper:
 Automatic printing from a clinic PC using to any type of printer with batch printing tool:
“medNet Print”.
or
 Automatic printing from a medNet PC using the SCHWIND delivered printers with batch
printing tool: “medNet Print”.
All generated PDF Files are stored in medNet Server and can be copied.
WARNING
 Installation and Setup shall be performed by a skilled clinic IT administrator
following the instructions described.
 SCHWIND offers technical support by email or phone for setup of the batch
printing software on the clinic PC. The clinic (PC) hardware equipment itself is
not a SCHWIND device and is therefore excluded from service and support!
All instruction steps must be followed exactly according to this manual to achieve
a reliable, safe and secure installation.
10.1 Printing scenarios
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”.
A network printer inside the MEDNET NETWORK and individual printing drivers installed on
SCHWIND PanelPCs are not allowed due to safety.
For using clinic owned printer (different to SCHWIND approved printer), consider “Scenario 3:
Printout on Printer in Clinic Network”
10.1.1 Scenario 1: Printout on USB connected Printer

Apart from MEDNET, the SCHWIND delivered PCs includes an USB printer. When printing,
choose the USB printer for printout.
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
pdf Print documents to printer “medNet PDF”
 …The PDF file has been created.
pdf The PDF file is automatically moved to the

 MEDNET Fileserver. Files are collected and stored
on the server.
When network is offline, the files are collected on
pdf pdf local PC and auto-copied to network when online.
pdf pdf
Referenced activities
SETUP:
see Chapter “10.2 Print-Setup: SCHWIND PanelPCs (Workstation, AMARIS PC)”
User can Access the PDF Files on Server manually:

see Chapter “10.6 Access or Print PDF-files from MEDNET Fileserver”
10.1.3 Scenario 3: Printout on Printer in Clinic Network

The PDF files are generated on the SCHWIND PanelPCs. Any clinic printer can be used. A clinic
Windows PC accessing the MEDNET fileserver over clinic network is required. MEDNET Print –
Tool prints out the PDF on real paper.
MEDNET network
pdf Print documents to printer “medNet PDF”
 …The PDF file has been created
pdf The PDF file is automatically moved to the

 MEDNET Fileserver.
local PC and auto-copied to network when online.
pdf pdf
MEDNET Fileserver is pdf pdf

attached to clinic network
Clinic network has access to the

files on MEDNET Fileserver
Clinic network
Paper
Any type of printer available on
printout
clinic PC – USB, network
“medNet Print” program is installed and

New arriving files on file server are
running on a clinic (office) PC is
monitoring the PDF directory and prints
 detected and printed automatically.
SETUP 1:
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
access)
SETUP 3:
Install MEDNET Print on one clinic PC with Windows printer available for printout
see Chapter “10.3 Print-Setup: MEDNET Print (SCHWIND PC or clinic PC)”
USE:
MEDNET Print, installed on Clinic PC, is printing the new files automatically on any available
windows printer. User can control MEDNET Print manually.
see Chapter “10.4 Short Manual: MEDNET Print”
USE:
From SCHWIND PCs, User can Access the PDF Files on Server manually:
10.1.4 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.
MEDNET network
pdf
 Print documents to printer “medNet PDF”
…The PDF file has been created
pdf
 The PDF file is automatically moved to the
MEDNET Fileserver.
local PC and auto-copied to network when online.
pdf pdf
pdf pdf
pdf  New arriving files on file server are
detected and printed automatically
Paper on the connected SCHWIND USB
printout printer
“medNet Print” Tool running on one

Schwind PanelPC monitoring the PDF
directory and prints new documents
automatically.
SETUP 1:
SETUP 2:
Install MEDNET Print on one SCHWIND PanelPC (Workstation) with USB printer attached.
see Chapter “10.3 Print-Setup: MEDNET Print (SCHWIND PC or clinic PC)”
USE:
MEDNET Print, installed on Workstation, is printing the new files automatically on the attached
USB printer. User can control MEDNET Print manually.
see Chapter “10.4 Short Manual: MEDNET Print”
USE:
From SCHWIND PCs, User can Access the PDF Files on Server manually:
10.2 Print-Setup: SCHWIND PanelPCs (Workstation, AMARIS PC)
Requirements:
 “print to PDF-printer: SCHWIND PanelPCs must run a specific HD Image Version:
AMARIS.7.3-5 / WORKSTATION 11.0-6 or higher.
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.
 The MEDNET network must run properly.
The following instructions must be performed separately for ALL SCHWIND PCs:
Workstation PanelPC / AMARIS PanelPC / StandalonePC
MEDNET Manager
Check the following directories, if present. If they are already available, you can skip the
following steps.
If directories are missing, create folder structure manually:

1. Quit MEDNET Manager with exit. It must not run. (You can press F4 to show.)
2. Use Windows file-explorer:

create a new sub-folder structure “PDFprinter/pending” into
DelegateFolder_SubDirStructure_AMARIS and
DelegateFolder_SubDirStructure_WORKSTATION. See the picture above. Leave
everything else untouched.
Note: The name is case sensitive. Do not abbreviate it, use exactly the capital and lower
case letters as above!
3. Re-start MEDNET Manager by starting it via the desktop icon or PC reboot.

A new “delegate directory” has become available on MEDNET-SERVER
FreePDF
FreePDF is pre-installed the SCHWIND PanelPCs. The

printer “FreePDF - medNet PDF printer” creates the pdf
file immediately into directory
D:\FILES_DELEGATEtoMEDNET\PDFprinter\pending
without questioning the user.
Just set it as the default printer via “Printers and Faxes”.

(If you don’t see the printer, check the installed HD Image
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.
When using MEDNET Print installed on any clinic PC, it scans the MEDNET Fileserver PDF
storage for new pending files in intervals (around 1-2 minutes) and prints them automatically
on any type of attached printer.
Supported file types: PDFs; simple text documents; some bitmap types (jpg, bmp, gif)
Setup
1. Ensure the correct attached clinic network to the MEDNET Fileserver according chapter:
„4.4.4 Infrastructure Online Remote Support / Clinic Network Access to Fileserver“
2. Set-up one clinic PC to be used with “MEDNET Print” Tool.

Note: It is not recommended to use two or more PCs at the same time.
3. Ensure you have a correctly installed and working printer connected to the clinic PC.
4. Copy directory “medNet_Print” from the medNet CDROM to the clinic PC. You can use
the system root C:\ or C:\Programms for example…
Call SCHWIND if you don’t have the tool available on CD-ROM. Do NOT install “MEDNET
Manager” on the clinic PC, thus it’s for the SCHWIND PCs only.
5. Optional: You can create a program link to desktop or start menu manually.
6. First start:
Start medNet_Print.exe by using Windows File-Explorer. The tool does NOT require
special permissions. (“Run as administrator” is NOT required.)
Ensure to “unblock” the firewall network traffic.
 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!
10.4 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.
Number of Start/Stop file-

 GUI/Control files available Monitoring engine Run in the background
Green: running is OK Logfile can gives

Red: Error/failure deeper insight when
grey: off/not running something goes
wrong
PENDING
The list is updated automatically in interval set in the configuration window.
All new detected files are first listed here first. They are sent to the Windows print spooler file
by file.
Note: Depending on the Windows print speed, the Windows printing queue can grow large if
many files are printed at the same time.
After each file has been printed is moved to PRINTED/SKIPPED or ERROR
ERROR
The list is updated automatically.
If printing failed the erroneous file will appear here. This can be some error by the printing
engine or file type is unsupported.
PRINTED/SKIPPED
The list is NOT updated automatically. The user has to use button “update List” manually to
retrieve the file overview.
All printed or skipped files without error appear here.
Each list includes several maintenance functions for manual use.
BUTTONS:
Update List The List is updated. VIEW The selected files are opened with the associated
program. (.PDF opens PDF viewer if installed)
(Re-Try) Print The selected files are printed (again). DELETE The selected files are deleted permanently from the
fileserver.
Skip Print The selected files in the pending list are
not printed. Suspend the monitoring
process first with button
“running/stopped”.
10.5 Print-Setup: Additional MEDNET PDF Printers
Only if equired…
A 2nd or 3rd MEDNET PDF printer make sense if you like to use more than one physical (real)
printing device. Each of them to be used for specific SCHWIND devices: For example when the
Schwind devices are separated over long distances (different floors). Laser might use clinic
printer 1 and diagnosis might use clinic printer 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 2nd printer. For a 3rd (4th) printer simply do the same setup steps and just
change the number “2” to “3” (“4”).
The installation steps on SCHWIND PanelPC is required only if you plan to use other specific clinic
printer.
FreePDF printer
New Windows PDF printer must be created manually if not available. In case the printer is already
there just set it to the default windows printer. Do not modify or alter existing printers.
The new PDF printers will save documents to
alternative fileserver Directory “/PDFprinter[x]/”
Manual creation:
1. Open Startmenu: Misc | FreePDF | FreePDF Config
2. In Profiles select the existing “medNet PDF printer” and click <Change>
3. Now a new profile (based on the default profile) will be created..

Change the following parameters only (do not make other modifications):
Basic Options: add number “2” to the Profile name.
FreePDF dialog: Add number “2” to the Path. Do not insert other characters.
<Save> the new profile.
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.
MEDNET Manager
On Schwind PanelPC the “PDFprinter2” directory structure must be available inside the
delegate folders (create the sub-directories manually if not available). This must match to the
previously installed FreePDF printer’s saving path.
MEDNET Print – configuration

“MEDNET Print” accesses only one PDF directory. To automate printing of the 2nd MEDNET PDF
directory, a new MEDNET Print instance must be installed.
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)
Also, the PDF files storage location must be changed to the 2nd instance:
Change PDF root directory to the new location:

/medNet_Projects/PDFprinter2/
<Tech-in> the new setting.
The rest of the configuration is as mentioned above for a single printer configuration, except a
different printer has to be selected.
10.6 Access or Print PDF-files from MEDNET Fileserver
In example, you can copy the files to SD Card for further purpose like viewing or printing
them directly from network to a connected printer.
The files can be accessed via File Explorer…
 …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
 Do Print within the treatment programs over the “printing” function to “medNet PDF
printer”.
It is recommended to always set this printer as the default windows printer.
 AMARIS: Set the Application-Software configuration to “automatic” printout while FreePDF

“medNet PDF printer” is the default windows printer.
 The CAM summary page printout must always be triggered manually with the summary page
“print button”.
 “MEDNET Print” Performance vs. amount of files: The number of PDF files on the medNet
Server increases. If you reach thousands of files (especially in the “printed” subfolder), the
performance of medNet print will decrease!
To avoid this, some old dated files should be moved or deleted.
MEDNET Print will give advice if the critical amount of files is reached.
User Manual 11. WORKSTATION Diagnostic-Database on MEDNET-
Server
11 WORKSTATION DIAGNOSTIC-DATABASE ON MEDNET-SERVER
By default, SCHWIND Workstation

diagnostic device normally uses an
internal database stored on the local 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. The connected PCs in the other rooms can access the data
over network with the Sirius software, view the data and create the SCHWIND CAM Export.
Multiple Workstations,
creating the eye data
Doctor office: Standalone PanelPC

Phoenix/Scout/IRX3 Software only
Data viewing and planning
Server
Application example 1: Standalone PC in a doctor’s office
When the standalone PC is installed in a doctor’s office, he or she can perform the planning
actions in his own room: Viewing the patient scans with the diagnosis Software, creating the
SCHWIND CAM Export and planning the treatment with SCHWIND CAM. The planned treatment
will be saved to network to be available for following treatments in the surgery room.
Application example 2: Standalone PC in the surgery room

Sometimes the doctor wants to choose a different patient scan for some reason. Now a
Standalone PanelPC** can be placed in the surgery room running the diagnosis Software and
SCHWIND CAM. 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…
** Note: The diagnosis Software is not approved for running on Amaris PanelPC!
Application example 3: Running Multiple Workstations

A clinic own multiple workstations, let’s say Sirius and Peramis, because of high volume patients.
All diagnosis systems stores their data to the central server. All the workstations can access all
the patient data. Additional Standalone PanelPC in doctor’s office may be used for evaluation.
Data is available via network at any workplace.
11.1 .mdb Database
CAUTION
 When the network is offline for some reason, the patient database cannot
access until it is online again. This can cause delay in the clinical workflow.
 A highly reliable and fast network system is required to avoid possible network
downtime! If performance issues are experienced, add 1GBit switches into
MEDNET.
 It is recommended to create a new database in regular intervals. Increasing size

may result in increased access time. There is no common recommendation.
When access time gets too long, consider new database!
 Use short unambiguous directory and DB file names when creating new DB.
 The diagnosis system’s databases using Microsoft

database engine. It is file oriented managed by the DB
engine running on each client. There is no DB service on
the NAS.
The database can be copied, moved, deleted directly on the

MEDNET shared directories for backup, recovery or
archiving. For each action, use the whole directory with
subdirectories.
Server
11.2 Shared Database
 Each of the Diagnosis systems SIRIUS/PERAMIS/IRX3/Scout uses a .mdb (Microsoft access

based) database engine. The devices are not compatible to use one .mdb in the middle.
Peramis+Sirius hardwarePhoenix Softwaredatabase engine.mdb file based DB for

Phoenix
Scout hardwareScout Softwaredatabase engine.mdb file based DB for Scout
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)
Workstation 1 (Sirius)
Database Workstation 2 (Sirius)
Standalone PC 1 Standalone PC 2 Standalone PC ..
11.2.2 Separate Databases for each Workstation Instance
DB “A” (Sirius) DB “B” (Sirius)

Workstation 2 Workstation 1
(Sirius) (Sirius)
Standalone PC 2 Standalone PC 1
Server
11.2.3 Concurrent Database Access
PHOENIX
 Software handles access to same database. Concurrent access is possible. User may be
notified by the software, when inconsistency is detected for some reason.
 The patient data displayed is not automatically updated, when then database content is
changed/data added by another network user.
Data is update in the software when the database content is re-read. For example: Patient
list is updated when DB is reloaded. Displayed scans are updated when a patient is (re-)
opened.
SCOUT
 Software handles access to same database. Concurrent access is possible. In case of

“simultaneous write” of a new eye scan, the software notifies the user and exists for safety
reason. After re-start Scout software, saving the eye scan can be continued or abort
list is updated when DB is reloaded. Displayed scans are updated when a patient is (re-)
opened.
IRX3
 Software handles access to same database. Concurrent access is possible. In case of

inconsistency detected, software may exit for safety reason.
list is updated when letter is entered in the “search mask”. Displayed scans are updated
when a patient is (re-) opened.
Server
11.3 PHOENIX (SIRIUS/PERAMIS)
11.3.1 Preparation
Software Registration
If the Software is not already “registered” by key the workstation requires the “diagnosis key
license” and the “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.
Fileserver Address
CAUTION
The Fileserver’s LAN Interface for MEDNET Network must be set to a fixed IP. This
IP must be set in MEDNET Manager Configuration instead of the NetBIOS Name
(“mednet-server”).
If fixed-IP configuration is not set, sporadic connection loss may occur (due to
timeout of NetBIOS to IP resolution): Software Exception in Phoenix Software will
occur sporadically.
With introduction of MEDNET Revision of 2019, the default configuration is “fixed-
IP”. With previous Revision/Models, please check if fixed IP is already set and set
Fixed IP according the chapter: “12.3 Using fixed/static IP for Fileserver”
In the following examples, sample location for SIRIUS is used. You can choose any suitable name.
If you own SIRIUS and PERAMIS, you could choose a subfolder \CSO or \SIRIUSPERAMIS.
11.3.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
instruction. This might be the case when you currently using the Workstation without a network.
Each Database on MEDNET shall be located inside a separate directory.
Use windows file-explorer:
1. Locate your current local database. The default DB is located on Drive

D:\Patient_Data_Sirius and can contain the phoenix.mdb database and many other files
including many subfolders.
2. Ensure that MEDNET is running. Copy the whole content including sub-directories of
D:\Patient_Data_Sirius to MEDNET Filestorage\Diagnosis_DB\Sirius
Do not skip any files!!!
3. It is recommended to rename the directory to a name fitting to the clinic needs.
Server
COPY
RENAME
11.3.3 CREATE new Database on Network
1. Go to the Settings then Miscellaneous, click the icon beside “Database”.
Server
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.
Server
4. Now go inside the directory you just have created. You can change the database
filename. Click Save.
5. For finishing the procedure click on Ok. Now wait a few seconds until the DB is
created. 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!
Server
“Backup in” should also point to the new network database location! For example..you can
copy’n’paste the “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.
Server
2. When the database window appears, change the database location. The Database
type must be type: Access. Click NO to open an existing one.
3. Now go to the Network Filestorage and select an existing database. Pointing to:
“My Computer | medNet FileStorage |
_DiagnosticDevice_Databases\Sirius\[DatabaseSubfolder]”, select the .mdb file and
click Open.
4. 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.
Server
11.3.5 DELETE Database
Use Windows file-explorer. Point to the MEDNET Sirius database directory and delete the whole
subfolder.
11.3.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. 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 Max exams returned to 100
 Disable the backup: set to 0

If backups are from multiple software installations at same time, this causes software error
and SW will exit.
 Optionally only one Software installation is allowed to create backup. Set to backup path
either to a local PC directory or to subfolder \bak of the File-Server DB location.
Server
11.4 SCOUT
11.4.1 Preparation
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.

If you plan to move or copy an existing database located on your Workstation’s drive, follow this
instruction. This might be the case when you currently using the Workstation without a network
before.
Each Database on MEDNET shall be located inside a separate directory!

1. Locate your current local database. The default DB is located at
D:\Patient_Data_Corneal_Wavefront_Analyzer and can contain a huge amount of sub-
directories and files.
“D:\ Patient_Data_Corneal_Wavefront_Analyzer” to “[medNet
Filestorage]:\_Diagnosis_DB\Scout”
COPY
RENAME
Server
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.
Click “File | Open Database”

When the folder Dialog appears, point to the MEDNET storing location:
“My Computer | medNet FileStorage | _DiagnosticDevice_Databases\Scout\” + Subdirectory
of the existing database.
Server
11.4.5 QUICK CHANGE Database
You can also use the “Recent database” entries. Every database which is loaded by “Open
DataBase” is entered in this list automatically.
11.4.6 DELETE Database Content
Content of the currently opened Database can be cleaned by click on “Delete Database”. The
existing database is deleted and moved to windows “recycle bin” then the database is re-created
without content. 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.

When a new patient was created by the Workstation or a patient information has been changed,
the database view of the other network devices, currently using this db, is NOT automatically
refreshed:
If you want to see the new data immediately on another PC in the software you have to “refresh”
it manually! You can re-start the Scout Software completely by closing/start it or just choose the
same database again from the “Recent database list”.
Server
11.5 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…)
CAUTION
SCHWIND recommends using the original configuration file which is shipped with
your IRX3 hardware device!
If you use another configuration file, the values are NOT falsified when viewing data,
but in case you connect a real IRX3 hardware device to the standalone PC, the
configuration file must be the correct one. If this does not match, you will create
wrong patient scans!
In case you have two or more IRX3 hardware devices available, you can choose any
configuration file of them. But you must ensure the correct configuration file when
you connect a real IRX3 hardware!
Note: IRX3 V1.2 -> Filename is IRX3_12_....

Note: IRX3 V1.4 -> Filename is IRX3_14_....
Calibration File installation:

Do not start „*setup.exe“!
Start the file via Windows file-explorer: IRX3_12_3456789_config_[Serialnumber].exe
The IRX3 Software is now ready to use.

If you plan to move or copy an existing database located on your Workstation’ drive, follow this
instruction. This might be the case when you currently using the Workstation without a network
before.
Each Database on MEDNET shall be located inside a separate directory!

1. Locate your current local database. The default DB is located on drive
D:\Patient_Data_Ocular_Wavefront_Analyzer containing one file BD Patients.mdb for the
default database.
Server
D:\Patient_Data_Ocular_Wavefront_Analyzer to medNet
Filestorage:\_Diagnosis_DB\IRX3\
COPY
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
to that location.
Step-by-step:
1. Use Windows File-explorer to open the MEDNET IRX3 Database directory.
Server
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).
Server
1. Close IRX3 Software!
2. Use Windows file-explorer. Point to the above showed folder and double click on
bdp.UDL
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.
Server
4. When the Folder Dialog appears, point to the MEDNET storing location:
My Computer | medNet FileStorage | _DiagnosticDevice_Databases\IRX3\ + the existing
database directory and database file you want to use and click “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.

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.
User Manual 12. Troubleshooting
12 TROUBLESHOOTING
CAUTION
The administrative actions should be performed by skilled persons only due to

effects on the practical clinic workflow.
It is advised to read all chapters completely before starting any actions. It is also
recommended to understand the usability of the physicians (explained in the
previous chapter).
This chapter provide s information about:

 Configuration
 Maintenance activities to keeping the MEDNET running
Troubleshooting tips in case of network problems
AFTER NEW PRODUCT INSTALLATION OR SOFTWARE UPDATE, THE CONFIGURATION
PROCESS MUST BE PASSED AND CHECKED!
12.1 Tips for Failure Cause Research
IMPORTANT NOTE
Network technology is very dynamic. All problem causes are never foreseeable.
Finding the exact reason and evaluation speed depends on the error complexity
and experience of the IT person(s).
 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. By combining that information, the cause is quickly identified in
most cases.
The following tips will help to determine the cause of a network related failure.
Evaluate problems by “do-it-yourself” before asking Schwind! Practice work has
shown that the error cause is most often identified within the network
infrastructure or bad configurations.
It should be possible to determine an error cause without using third party diagnosis
tools!
Look at MEDNET-Manager “DIAGNOSIS” Screen at first.

Behaviour
 When did the failure happen?
 Which actions were done right before or the days before the failure?
 with MEDNET manager?
 involved Software product?
 any sort of network related configuration change in software or network
infrastructure?
State of occurring at fixed intervals
 Permanent error?
 Sporadic/temporary/periodic/Intermittent error?
 How often within a specific time?
 Bad Network stability?  Try MEDNET Manager Diagnosis with logfiles, Transfer test
with large files.,…
MEDNET Network infrastructure / general hardware checks

 All cables of all devices connected? Check all cable connectors: the medical device;
galvanic LAN isolator; wall; switch “server room”
 Cables loosely plugged into the wall plug but there is no electronic connection?. Check
it!
 Connection to a patch panel correct? (no short circuit; all single cables connected?)
 If possible try another LAN cable at the switch.
 If there is a galvanic LAN isolator, remove it temporarily. (Warning: Do not treat real
persons without galvanic LAN isolation! “Onyx ZEUS” Panel PC model has built-in
isolation)
 SCHWIND recommends a (cheap) LAN cable tester to check the
line from the treatment room to the server room.
Cable tester
 Are all necessary devices permanently powered on? medNet NAS, router, switch
 As a last try, if all else fails, try another power transformer. A failure after years of use
might not be recognised when voltage or current delivery has become slightly aberrant.
 If managed switches across clinic network are used, set high throughput priority.
MEDNET NAS Fileserver
 Connected to MEDNET Router?
 Is the directory structure correct? Are all the expected files available?
 File access problem?  Try a device reboot (push power button 2 seconds; shutdown
will take one minute; turn it on again; boot-up takes ~2 minutes)
MEDNET Router
 The original SCHWIND MEDNET Router is required at all times!
 Device configured with „SCHWIND MEDNET” settings.
 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.
 The “WAN Port” is only used for connection to clinic network and NOT connected to
any MEDNET device.
SCHWIND medical device (PanelPC)
 Access to Fileserver possible?
 Cable connection to MEDNET switch possible?
 Use MEDNET Manager Software Diagnosis page.
 Reboot the device(s)
MEDNET Manager
 Is the MEDNET Manager Software properly running? (The MEDNET status area must
display “green LEDs” to indicate a correctly running network!)
 Is the MEDNET Manager software properly configured?
 Check MEDNET Manager logfile. The also log contains timestamp of all network breaks.
 Check MEDNET Manager Software Diagnosis page and tools for anomalies.
Diagnosis Database Connection slow/offline/Exception
 Ensure 1Gbit LAN ethernet connectivity
 Ensure fixed IP of MEDNET NAS, correct onfiguration?
 Working over network can be slower than local PC database.
 Speed decreases with size of DB. For example, if the patient number is approx. above
1000 this could lead into slow speed. If so, start a new database. Switching between
database is possible (but sometimes not comfortable)
 It is recommended to create a new DB in regular intervals (yearly)
 If managed switches across clinic network are used, set high throughput priority.
Combine all “network views of the Schwind device” together for ideas on possible failure
causes
Example:
C
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. Obvious error cause possibilities are: no
connection to medNet router; no connection to Fileserver; a connection problem on the PanelPC
itself or several causes at a time. A total Fileserver failure can be excluded because the other
devices have Fileserver connection!
In another example (not illustrated), when the medNet Manager diagnostic screen shows
“offline” Filestorage at all PanelPCs, the following could be wrong: Fileserver is off, corrupt,
defective, not connected to network or without connection to router. The router itself could
have a problem when there are no devices visible on the diagnosis screen.
12.2 MEDNET Manager
12.2.1 Negative status in Main View

When MEDNET Manager is started, the Main Menu shows the initialisation actions. If something
wrong is detected it will indicate the respective action with “FAILED” or “ERROR”.
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.
• (green)=OK
• (grey)=not active
• (red)=failed/error
12.2.2 Popup Notification

MEDNET Manager introduces a “popup notification” to the system. The network state is
permanently checked. In case of a detected network failure, a notification message will pop up in
front of all windows, so the physician on the PC can alert the IT administration to begin problem
solving. Screenshot shows one notification. Multiple notifications are also possible.
During “AMARIS Application Software, treatment menu” is visible, the popup is supressed.
When popup appears, all users shall consider the displayed information. Call IT Admin to fix the
problem.
12.2.3 Diagnosis
Advanced network analysis made easy!
Normally a professional IT administrator would go to the Windows command line, typing in
complex commands or installing and starting his own common network tools. 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: device type set in MEDNET Manager config

Name: device serial number
Descr: device description as entered in Manager config
Workgroup:currently assigned Workgroup (must be the
MEDNET workgroup, if abbreviated, the workgroup
must be changed!)
IP: IPs assigned to the network interfaces.:
MEDNET IP subnet is: 192.168.141.X
AMARIS also includes: 192.168.17.X
All information must be displayed properly! When something

is abbreviated as described above, something might be wrong!
Availability status of the medNet filestorage
State: ONLINE or OFFLINE

HOSTNAME:name is configured in the Manager settings ini
file. The Filestorage must be reachable via this
“Hostname”!
IP: currently assigned IP of the Fileserver
The MEDNET File storage must always be ONLINE and

reachable. If not, State is displayed as OFFLINE and (if activated)
a popup notification message is displayed! When OFFLINE
medNet is not operating properly, treatment file transfer is not
possible and the error must be fixed!
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.
Note: List view can be outdated. The “netbios” cache is hold up
to 15 minutes until the list is up to date!
All “visible” workgroups are listed
A proper MEDNET environment must show the MEDNET

workgroup only! If other workgroups are displayed, one or more
devices might not be configured properly or unauthorised
“foreign” devices are connected to the MEDNET!
Note: The overview can be up to 15 minutes old! This is a
limitation of WindowsXP. After a PC reboot, the list is always up
to date.
The network “stack” is reinitialised.
Sometimes this can help to solve TCP/IP problems in case you

“played too much” with network settings and network is not
acting as expected.
Following actions are performed in order:
1) refreshing all DHCP leases 2) clearing arp cache
3) clearing netbt 4) refreshing netb
5) clearing dns cache 6) registering dns
Internet capability state.
By default, the internet access and

“reaching other network” is controlled
and checked by MEDNET Manager.
The current status is displayed
according to the automatically set state
and comparison to the real availability

of the internet!
The default state is “disallowed”.
When internet is set to “active” and
online remote access is started, the
access is enabled.
When the red error messages are
displayed the network infrastructure
must be checked!
Network summary
A very detailed listing on the current network and system state is generated. After “something”
changes, the information might become different. It is displayed in an appearing textbox and also
saved to the MEDNET Manager logfile.
Summary section Content and expectations
 [expected status for a correctly running network]
THIS_DEVICE Device Type; Workgroup; Computer name; assigned IPs
 Correctness of device type, deviceName=serial; MEDNET
workgroup; assigneded MEDNET IP (MEDNET subnet is:
192.168.4.x)
MEDNET_FILESTORAGE Online/offline; required Computer name; detected
device IP
 Online fileserver; displayed fileserver-name
must be set to the real MEDNET fileserver’s
name
MEDNET_CURRENTLY AVAILABLE DEVICES Other “visible” devices in MEDNET Workgroup:
IN MEDNETGROUP Computername+description
Note: the list is refreshed every ~15 minutes only

and might be outdated at the time the log is
created! This is a WindowsXP issue.
 All online MEDNET devices must be displayed

as expected.
MEDNET_OTHER WORKGROUPS DETECTED Other “visible” workgroups in the same ip-sub-
network
Note: the list is refreshed every ~15 minutes only

and might be outdated at the time the log is
created! This is a WindowsXP issue.
 Only the “SCHWIND-MEDNET” Workgroup should be
visible! If not, another Schwind device is
not set to the correct workgroup OR a foreign
network or device is attached directly to the
MEDNET network. The latter must be avoided in
all cases for correct and safe MEDNET
operation!
BROWSTAT Detailed NetBIOS status. Can help to detect wrong
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…
INTERNET MEDNET internet control+check status and available
error message.
DIAGNOSIS Windows OS status of several elements
 Mainly used as a system status summary when
giving the logfile to SCHWIND Service or
distributor.
Traffic monitoring
This tool is intended for manual speed and transfer tests only.
Network Tool Box: Connection Tests already contains a build in and convenient network transfer
test.
An external tool is started and displayed to indicate the network traffic in real time.
You can use it for manual network speed tests, for example, when you are copying small files or
one very big file from the PC to the medNet filestorage.
It also displays the current speed of the network interface.
Choose the correct network adapter. The

MEDNET network interface assigned IP is
192.168.4.X
List routing table

This lists the current network routing table of the operating system.
Notice that this goes very deep into the Windows network architecture. Try not to interpret when
you don’t understand the meaning.
Accounting test
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. If another result is displayed it is likely that the fileserver
configuration is corrupt or the MEDNET Manager user account information is wrong. If so, call
SCHWIND service.
Connection Test
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.  When the speed is in
accordance with the possible speed of your special network and the transfer test is
always correct, the network should operate reliably.
Realtime transfer status: current / averaage / min / max
Test selection Test result after finish

The test selection contains 4 different test types with several configuration options. When using
the tests, try the default values first.
Perform a test only on one device at a time. If other devices access the network at the same time,
the network speed will be decreased.
Continuous ping test Transfer test: big file
Just a simple “ping”. You can select an amount of A file with defined size and random content is
loops and a pause between the pings. uploaded, downloaded and compared with a
specified amount of loops.
 All pings must answered by the fileserver  OK when no errors are detected and when the
without “timeouts” or “not_reached”. avg speed is approximately as expected according
to the network type.
Check your physical network when average time is
larger than 1000 ms and when pings are lost! Check your physical network and try a reboot of
the file server when errors are detected or when
the network speed is far lower than expected!
Transfer test: many files Transfer test: long running

An amount of files with randomized size and You can start the test and let it run in the
content is uploaded, downloaded and compared background even when the PC is used for
with a specified amount of loops. productive work on patients. It can help to detect
sporadic network failures!
 OK when no errors are detected and when the When started, several test files are generated and
avg speed is approximately as expected according uploaded, downloaded and compared. Between
to the network type. each test loop with a minimum waiting time of 25
minutes can be defined.
Check your physical network and try a reboot of The test will not start again automatically after
the file server when errors are detected or when MEDNET Manager or PanelPC are restarted.
the network speed is far lower than expected!  OK when no errors are detected and when the
avg. speed is approximately as expected according
to the network type.
Check your physical network and try a reboot of
the file server when errors are detected or when
the network speed is far lower than expected!
Speed comparison
A network speed of 100Mbit or 1GBit is negligible in the MEDNET environment. With
approximate treatment file sizes below 5MB the user does not notice the difference in the
real world!
The expected transfer rates are always lower than the physical speed because the network
protocols include some additional data package information, such as checksum, routing
information, etc.
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
LAN 100MBit 6-9 MByte
 Below 6MByte is bad!
LAN 1GBit Theoretically up to hundred MB but in reality limited due to
the NAS device speed!
Rates of 20-40MByte are possible!
WLAN 54Mbit 2-4 MByte
 Below 1MByte is bad!
 WLAN is not recommended and might not be
supported by SCHWIND due to insufficient reliability.
Network stability
When network connection is not available or broken, error log entry is generated. If that entries
appears regularly, network may have a stability (connection) problem which needs to be fixed!
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.
The user can <ABORT> the process by clicking the button. The field is removed and the
delegating/syncing is paused. The remaining files are still pending. The pause depends on the
current interval time of the delegate or sync folder check. (By default the time is ~1,5 minutes and
can increase up to 10 minutes). After this time has passed the delegate/sync process is re-started
again, preceding the remaining files.
12.2.5 Logfile
MEDNET Manager includes a detailed logfile. Upon error/failure or anomalies you can open the
logfile and “interpret” what is going on! The log is easy to read and basic functionalities can be
easily readout! Try it if you have problems with only using the diagnosis screen during network
failure cause research.
Ongoing log in MEDNET Manager

In MEDNET Manager the log is not displayed by default, but is automatically displayed upon the
occurrence of critical entries, for example: network failure.
The log can be shown and hidden with the respective button at the bottom left.
Logfile Directory
Path: C:\_medNet\SETS_medNetManager\Log
Clicking the LOGFILES button on the top of MEDNET Manager opens Windows File Explorer in
the Logfile directory. You can choose any text editor to view or copy files to SD card…
12.3 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. This prevents possible timeouts during Fileserver-access.
1. Set NAS Fileserver to fixed IP using “QNAP Finder Tool” (recommended method)
A. Use Windows File-Explorer, start the tool:

C:\_medNet\DeviceConfigurations\NAS__QNAP_Finder_Software\
“QNAP Finder [Version].EXE” (use the highest version available.)
B. Select the Server in the list, then click <Configuration>
C. Login: admin Passwort: elvis222
D. Enter IP data in Tab <Network Settings>.

Set IP 192.168.141.99 only. Do NOT use another IP! Do not change other settings.
192.168.141.99
E. Obtain the settings with <OK> and perform a Server reboot.
Alternative: via http-Frontend (not recommended)

Use Browser to log in into NAS Web-Frontend, see Chapter “15 List of Passwords” for Login details.
Then go to: System Settings (or System Administration) | Network | Network Parameters
LAN Port 1 parameters:
Set IP 192.168.141.99 only.

Set Gateway to 255.255.255.255. Do not use other IP and do not make other changes.
2. All available SCHWIND PanelPCs must be configured to the new server IP address
manually:
MEDNET Manager | SETTINGS: Set IP 192.168.141.99 only. <Teach-in>; reboot PC
12.4 Workstation – Diagnosis Database on Network
IMPORTANT NOTE
 The diagnosis software cannot be used when the network is offline!

 When the MEDNET fileserver is offline the diagnosis software Sirius/Scout/IRX3
will display error message or the software start-up acts unexpected. In that case
close and re-start the software when the file-server is online.
Existing database data is not lost or corrupted, but a current patient scan
might be lost and must repeated.
 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; Check size of Database (try a new database)
It is recommended to create a new DB in regular intervals, for example each half year…
Sporadic connection loss:

Set fixed IP. See Chapter: “12.3 Using fixed/static IP for Fileserver”
Error Messages
Sirius/Phoenix
Software start with Network offline
database file is missing (network

online)
Error message appears. “Retry” when network is online.
Connection breaks during use
Error appears: “Quit” the software, re-start when

network is online.
If appearing often: Set fixed IP. See Chapter: “12.3 Using
fixed/static IP for Fileserver”
Scout
Error is displayed at SW start, then the database jumps

back to database on HD:
c:\Keratron\database\indtest.mdb
Software start with Network offline
Empty patient list means: network problem.

Do not acquire patients, close the software immediately,
and re-open the network database with via menu “File |
recent database” when the network is online.
Software starts without error!!
Database jumps back to database on HD:
c:\Keratron\database\indtest.mdb
Database file is missing (network is

online)
Empty patient list means: network problem.

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.
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.
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. Then the “new” drive is “synchronized” with the remaining drive: The files from the
remaining drive are mirrored to the new drive and the NAS is operating properly again as before.
In case a drive is defective, all operations are performed on the remaining HD. The defective drive
should be replaced as soon as possible.
In case both drives fail, all files will be lost!
The following information is most common. If more information is required, check the
Fileserver manufacturer’s troubleshooting ressoruces about the model.
Status Check
In normal operation the drive LED indication shows no error.
In case the Server has a failure or problem, LEDs will indicate “proven” by color (red),
blinking,… Speaker output (beep, speech) may also appear.
Checking the Server Log:

Web browser URL: http://mednet-server or http://mednet-server:8080 or http://192.168.141.99
your individual server name or IP address.
Login Name: admin
Password: elvis222
Check the system messages for latest warnings and errors. Check if an error is still persistent
and (try to) fix it.
Indication is similar over certain NAS models, but similar.
Examples:
12.7 Fileserver Drive Replacement or Upgrade
CAUTION
 Prepare a full backup to external data media before replacing disks. If functions
are wrongly used, you may lose data on the drive(s).
 Follow the instructions strictly.
 For suitable replacement disk model, please ask SCHWIND for recommended
models.
Keep in mind: The File-Server is not a Backup Media. To prevent data loss, backups
should be created regularly by clinic 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.
2. Access the Web-Frontend by Address: http://mednet-server or http://mednet-

server:8080 or by IP address, http://192.168.141.99 .
3. Connect one of the old drives (incl. data) to a USB to SATA Converter (USB3).
Connect the USB to the USB Port of NAS.
Do not insert the drive into a NAS drive bay! It may be syncronized automatically with
the regular existing drive, lossing all the data.
4. If drive is OK (not defective), it should be recognized as external data media, visible in

the Web-Frontend.
With the Web-Frontend’s File manager, copy all files and folders of
[external]\medNet_Projects to the NAS internal drive folder \medNet_Projects
Do not modify anything. Do not change access rights.
In case the drive is not recognized by the NAS, access the filesystem via PC and copy
the data over Network to the NAS or via an external USB drive to the NAS. Chapter:
12.7.2 Access Drives Filesystem via Windows
12.7.2 Access Drives Filesystem via Windows

The NAS drive contains Linux Filesystem (EXT3/EXT4). To read under Windows Operating
System, install third party tool for access.
Do not make any write operations under Windows, READONLY. If you put back into the NAS a
drive with modified, this can lead to data corruption or loss.
“Linux File System for Windows by Paragon” works well. With some other products, drive
could be detected, but filesystem could not read.
Put a drive out of the NAS. Connect it to a USB (3) to SATA Converter, connected to Windows.
On the mounted filesystem, look for folder \medNet_Projects containing the data for a copy
process. Do not make any modifications on the disk.
12.7.3 Drive Replacement / Expand Space

You can exchange one defective drive or replace both drives for space expansion.
ENSURE TO USE TWO IDENTICAL DRIVE MODELS.
For space expansion, the two small drives are exchange one by one with the new bigger one.
Depending on size and speed, the process takes many hours. Plan the process overnight.
1. Access the Web-Frontend by Address: http://mednet-server or http://mednet-

server:8080 or by IP address like http://192.168.141.99 .
There are different QNAP QTS “operating” System Versions. The procedure is the
same, but may have different UI experience.
2. There will be a function for <CHANGE> disk and <EXPAND> disk.
Select the drive you want to replace: the one defective drive (or both drives for space
expansion).
Start <CHANGE>. The dialog will guide you through the process. When the new drive is
inserted, the RAID system is synchronized. You have to wait until it is finished.This can
take many hours. The process can take many hours, depending on you amount of data.
It is useful to plan this during time, when the NAS is not in use. For example overnight.
3. Expand only:
For drive space expansion, <CHANGE> the next remaining smaller drive.
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
QTS 4.2 and older – Change disk / Expand Capacity
QTS 4.3 – Change disk / Expand Capacity
QTS 4.4 – Change disk / Expand Capacity
User Manual 13. Server-Data Maintenance
13 SERVER-DATA MAINTENANCE
13.1 Backup & Recovery
recovery
mednet server Clinic

Backup server
backup
CAUTION
THE MEDNET-SERVER S NOT A DATA BACKUP!
A backup is a full copy or snapshot of a set of data at a specific time. The clinic should
establish an own backup process for safety.
The Server system contains redundant Drives. If one drive fails, it can be exchanged
easily. If both drives fail or the device is damaged, all clinical data may be lost!
 CONSIDER A BACKUP PROCESS

Configure the backup to your needs:
 Backup Interval
 Amount of full backup copies (retention span)
 Store the backup data at different places, appart from mednet NAS, offline
storage
The backup should be created when the SCHWIND devices do not access the data.
Medical data content is saved with files only (no SQL database). When creating
backup, mark it with date of the day.
For recovery, a manual file replacemnt of the existing NAS files or whole folders is
required with backup media as data source.
You can copy data from an attached USB disk to the NAS via its Web frontend or
from PanelPC, accessing the mednet server, copy the data from the backup media
to the NAS over network.
A Copy tool like Microsoft’s Rich Copy is recommended. File-Explorer can crash on
folders with many ten of tousand files or directories.
When amount of data increases, check the duration of backup from time to time.
Process should be finished in the morning before work to prevent mednet server
slowdown.
 You can use a backup tool, accessing the MEDNET_Project folders via SMB Share copy the
data to a clinic backup server.
 Whatever fits best: Create full backup in regular interval or update new or changed files only.
 A quick and minimal backup solution is to use the NAS integrated backup function to “always
attached” USB disk. Use USB3.0 only. Shedule automatic backup at night.
In this solution, to minimize the risk of simultaneous failure of NAS and USB disk (lightning),
copy the 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.
13.2 Cleanup and archive Work Folders
The content of all network related folders increases over time. The IT admin is recommended to
“tidy up” those folders regularly, for example, every quarter of a year or every half a year. The
need for “tidied up” project directories must be decided individually and performed manually.
MEDNET Manager contains a short overview on remaining free space:
CAUTION
Always move “old files” to an archive folder rather than delete files! Use Windows
File Explorer.
In case the HD space is nearing zero, list the file with Windows File Explorer by date,
create a copy on an external data storage media for external archiving and then
delete all “very old” files.
The amount of content in a network directory can cause significant slowdowns in
the network (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. Physician will see all files
or project directories of available files or patients when loading from. Listing a huge amount of
files or directories will take much more time than directories with less content. Archiving old
content will increase listing speed and creates a more clear look over the working directories.
 Use a self-created archive directory name. Using a “_” as the first character will list the
directory first before others….
i.e. “_Archive” or “_Archive (2012)” or “_Archive (outdated files)”
 Move “outdated” single files or complete subdiretories (SCHWIND_CAM projects).
 Relevant directories for Archive are DIAGNOSTIC_Export, SCHWIND_CAM and
PDFprinter. The other directories shall not be touched for archiving.
 For delete (instead of move), copy to external storage media shall be considered.
Archive folders
move manually
Content in working directories…
User Manual 14. IEC 60601-1 3rd Network FAQ
14 IEC 60601-1 3RD 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” for SCHWIND medical devices only, with all medical-
relevant network aspects covered. The MEDNET computer network can (optionally) be
connected onto a “foreign” clinic network, for internet access. Fileserver can (optionally)
be connected to “foreign” clinic network to provide data into the clinic network.
A medical network including the medical devices shall be planned, installed and
validated successfully MEDNET includes those elements by instruction.
Also a special focus on hazard and risk is required. Countermeasures are included in
MEDNET to provide a safe and secure network system, protecting the medical devices,
operator and patient.
MEDNET network characteristic is limited but very flexible

The MEDNET instructions must be followed explicitly and may not be changed. Any
type of abbreviation is not allowed if not listed in the MEDNET instructions. READ THE
MEDNET MANUAL CAREFULLY TO UNDERSTAND OPTIONS.
Purpose of SCHWIND Devices when connected to computer network

 see “3.2 Intended Use & Reasonably Foreseeable Misuse”
Network characteristic and configuration

 see “4.4 Network Characteristic, Requirement”
 see document “medNet_Installation-Requirements_Prerequisites”
Technical specifications of the network connection, including security specifications

SCHWIND medical devices (PanelPC): connected via LAN to MEDNET network; firewall
enabled; incoming connections blocked; outcoming connection to MEDNET Server;
Internet connection controlled by MEDNET-Manager –only possilble for the time,
connection is explicitly “enabled” (for the time of remote access support); Internet
connection by gateway configuration of MEDNET Router; accessing MEDNET Server
(password protected)
MEDNET Server: Connected via 1st LAN to MEDNET network; no outgoing connections;
incoming connection for providing file-server services; password protected; firewall
enabled; administrative service ports active (password protected); Connected via 2nd
LAN to clinic network (option) for access to data –password protected.
MEDNET Router: IP address management; switch capability for MEDNET network;

providing gateway to clinic network - for internet access from SCHWIND PCs to Internet,
reached over clinic network (option) for remote access; gateway Port to clinic network is
(NAT) firewall enabled – blocking all incoming connection; no blocking of outgoing data
(blocking outgoing data of PCs is software controlled by MEDNET Manager Software on
SCHWIND medical PC).
User Manual 14. IEC 60601-1 3rd Network FAQ
Information flow between devices, IT-network, other devices on it-network, routing

Medical data between medial devices/software:
 see “5.1 Fileserver Directory Structure”
 see ”5.2 Dataflow”
 see “11 WORKSTATION Diagnostic-Database on MEDNET-Server”
Online Remote Service (option):
 see “8 Online Remote Services”
Data provided from server to “foreign” clinic network (option):
 see “9 Fileserver - Access from Clinic Network”
Hazardous situations resulting from failure of the it-network

 see “2 Hazards and Safety”
Statement: Connection to it-networks including other equipment could result in

previously unidentified risks to patients, operators or third parties
 see “3.4 Medical Network Statement”
 see “Service Manual for installation in common setting, II_E082_MEDNET_Install
Instruction – General Installation notes”
Shall the clinic identify analyse, evaluate and control additional risks
By MEDNET engineering, in combination with SCHWIND medical devices, the product
combinations already covers countermeasures for possible risks. Additional activities by
clinic are not necessary in general. It is recommended in case of using “interface”
between MEDNET and “foreign” clinic network, when MEDNET network is accessed
from clinic network: incoming connection to MEDNET Server from clinic network.
Abbreviations of official MEDNET Setup (as described in MEDNET instructions),

different to MEDNET instructions, may create new hazards. Those abbreviations are not
covered by 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. The system
combination MEDNET network + medical devices voids. IT-Network system is no longer
allowed to be called “SCHWIND MEDNET”.
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.
In case clinic abbreviates the official MEDNET product, creating different other
networking system (combination of SCHWIND medical devices + IT-Network) new risks
are introduced. Safety and security for the network system and medical devices are no
longer guaranteed. The customer requires analysing the system about risk.
accompanying documents for the responsible organization include the following:

 Room requirements: “MEDNET_Installation-Requirements_Prerequisites”
 User Manual: “UI_M01-16_MEDNET”
 MEDICAL Apparatus book, containing chapters “MEDNET”
medNet CDROM (tools)
User Manual 15. List of Passwords
15 LIST OF PASSWORDS
WARNING: Handle confidentially. Do not modify any settings. Changes, explicitely allowed in MEDNET
manual or SCHWIND instructions are allowed. Never replace or create new access credentials (names,
passwords, settings).
Disclaimer: 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.
Consider safety notes “9 Fileserver - Access from Clinic Network”
Username / Password (case sensitive)
http://mednet-server
NAS Server or
QNAP http://mednet-server:8080 Admin / elvis222
admin console or individual server-name
or IP address
SMB share (case sensitive):
Readonly
foreignUser / R8HBhE
\\medNet_Projects
Read/Write
setsWorkstation / [ask Schwind for PW]
setsAmaris / [ask Schwind for PW]
NAS Server \\medNet_Projects\medNet_pdf

QNAP
SMB file Shares \\medNet_Projects\medNet_pdf2
\\medNet_Projects\medNet_pdf3
Read/Write
PDF share valid for QNAP TS-253Be or
setsPDF / T7bza8
newer (2019 model or later)
Important Info: Chapter. “9.2 Fileserver –

Access MEDNET PDF Print”
\\medNet_PublicShare no login necessary
admin / elvislive
MEDNET Router
http://192.168.141.50 or admin / elvislives
admin console or admin / [blank]
MEDNET
Manager
When TeamViewer is active Password only: elvis111
TeamViewer
Remote Login
**Password: Password upon request! Ask Schwind.
User Manual 0. Contact Address
CONTACT ADDRESS
Should you have any questions, do not hesitate to contact us.
Manufacturer:
SCHWIND eye-tech-solutions GmbH

Mainparkstrasse 6-10
D-63801 Kleinostheim
Tel.: +49-(0)6027-508-0
Fax: +49-(0)6027-508-208
Email: info@eye-tech.net
http://www.eye-tech-solutions.com
Service Hotline:
Tel.: +49-(0)6027-508-333
Fax: +49-(0)6027-508-245
Email: service@eye-tech.net
Customer Support:
Fax: +49-(0)6027-508–208
Tel.: +49-(0)6027-508-350
Email: apm@eye-tech.net
User Manual
Your notes
Document version 1.9.2, dated 2020-04-20 Page 135 of 135

User Manual

Uploaded by

Document Information

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

User Manual

Uploaded by

Copyright:

Available Formats

USER MANUAL

for MEDNET MANAGER V1.9

SCHWIND eye-tech-solutions GmbH

6.1 Software Start-up & Shutdown ..............................................................................................................46

11.3.7 Important Settings ...........................................................................................................................96

The following conventions are used in this manual.

This symbol provides the user with useful or additional information.

SCOPE OF USER MANUAL

The present manual is the ORIGINAL INSTRUCTION, which is legally binding.

USER MANUAL STORAGE LOCATION

Document version 1.9.2, dated 2020-04-20 Page 5 of 135

1.1 System Identification Data

Product name: SCHWIND MEDNET

1.2 Technical Assistance / Application Support

SCHWIND eye-tech-solutions offers a comprehensive warranty and service support program.

Service Hotline Application Support

1.3 Declaration of Manufacturer

1.4 Liability Exclusions

SCHWIND eye-tech-solutions does not assume any liability for:

Also refer to General Warranty Regulations of SCHWIND eye-tech-solutions GmbH.

5. Damages or malfunctions have to be reported to SCHWIND eye-tech-solutions or to the

1.6 License Agreement

Copyright © 2011-2020 SCHWIND eye-tech-solutions GmbH, Kleinostheim

1.9 Scope of Delivery / Delivered Content

MEDNET NAS Fileserver including 2x drives (HDD or SSD)

Galvanic LAN isolators

MEDNET Software Package: MEDNET Manager, MEDNET Print

Webcam and Headset (if available) for Remote Support

1.10 SCHWIND Labelling

The SCHWIND MEDNET components are labelled as follows:

Galvanic LAN isolator (if available)

** HW model of label position may differ due to product revisions

2 HAZARDS AND SAFETY

2.1 Restrictions of Use

Use and operation by trained personnel only!

Service & maintenance by authorized personnel only!

2.2 Training of Operator’s Personnel

2.3 Protection from Unauthorized Use

2.4 Data Protection and Data Privacy

2.5 Virus Protection

2.6 Electronic Safety on the Medical Device

AAEON ONYX 175 (2009-2014)

Use the separate galvanic LAN isolator between PC Lan

(P/N: 18800), must be provided for each Panel-PC!

ONYX ZEUS (since 2013)

1. Power OFF AMARIS and detach from main power cord.

2.7 Dangers Resulting from Software Operation

2.8 Dangers resulting from Network Failure

Dangers resulting of MEDNET network failure are not known.

2.9 Interruptions from Network Operation Failure

2.10 In Case of Emergency

A case of emergency arising from MEDNET is not known.

2.11 Contraindications / Side Effects

Supreme advantages at a glance:

3.2 Intended Use & Reasonably Foreseeable Misuse

 The resulting MEDNET eco-system offers sophisticated networking features for

 Online remote service for SCHWIND or authorized partners.

 The MEDNET network environment is intended to be a “private” network,

Reasonably foreseeable misuse

3.3 Addressed User Groups

The MEDNET Manager Software facilitates supreme usability covered by

The patient chain: from evaluate  plan  and treat is completely

The MEDNET network is intended to be maintained by the clinic’s own IT

The system is designed for commonly-known infrastructures and