Laserfiche WebLink
The Collaboration Live server is a cloud -hosted enterprise solution that provides contact <br />management, secure connectivity and streaming services for Collaboration Live text, audio <br />and video features. This server is accessed from a separate PC installed in the Azurion <br />control room and remote client end -points over the internet using an industry standard TLS <br />method of connectivity. The server is hosted by IIT (Innovative Imaging Technologies, <br />Montreal, Canada). <br />2. Connectivi <br />In order to connect to the Collaboration Live server, the system will need access from within <br />the healthcare facility network to the internet for outbound connections over port 443, and <br />UDP and TCP protocol must be allowed. We recommend whitelisting the following domains: <br />*.iitreacts.com <br />*.reacts.com <br />The minimum bandwidth of 0.5 Mbit/s upload and 0.5 Mbit/s download is required for <br />connectivity. The recommended bandwidth for optimal performance is 1.5 Mbit/s upload and <br />1.5 bit/s download. <br />N,, . II IIII I <br />r, <br />�1F � <br />Collaboration Live server <br />-- <br />powered by Reacts' <br />10 <br />� of W'II�I"°IIII �a <br />a) <br />iWeb KEPI <br />k <br />Ram t <br />`ittl;. d <br />"I <br />I� = <br />i <br />� _ r � gllllplp^II19111 . <br />I <br />0 - ... <br />0 <br />- The privacy policy of IIT Reacts are available online: <br />https://reacts.com/en/legal/privacy <br />The security overview of IIT Reacts is available online from the Security and Privacy Page: <br />ttps://reacts.com/security-overview/ <br />L <br />0 <br />a) <br />0 <br />70 <br />C <br />cN <br />Z <br />0 <br />.E <br />0 <br />n <br />0 <br />0 <br />THIS SHEET IS PART OF THE DOCUMENT SET LISTED ON SHEET C1 AND SHOULD NOT BE SEPARATED, <br />Philips Healthcare Remote Services Network (RSN', <br />Secure broadband connection required for Philips remote technical support, diagnostics, and applications assistance <br />Broadband Site -to -Site Connectivity (Preferred) Option 2: Back End Connected to the HCF Firewall Connectivity Method <br />This connectivity method is designed for customers who prefer a connection from the RSN Data This connectivity method is designed for customers who prefer a Philips RSN Router installed <br />Center to the Health Care Facility (HCF) utilizing their existing VPN equipment. on site by setting up an IP-Based policy allowing access thru existing HCF Firewall to Philips <br />equipment. <br />Connectivity Details: <br />- A Site -to -Site connection from the RSN data center's Cisco router will be established to the <br />HCF's VPN concentrator. <br />- The VPN Tunnel will be an IPSEC, 3DES encrypted Tunnel using IKE as standard, but <br />alternative standards are also available, such as AES, MD5, SHA, Security Association lifetime <br />and Encryption Mode. <br />- Every system that we will be servicing remotely will have a static NAT IP that we configure on <br />the RSN Data center side. --------- --------------------- <br />HCF VPN Healthcare Facility <br />Concentrator <br />General Network Router Philips <br />Overview Philips Nuc Med Philips <br />(Not site specific) PACS MR <br />c <br />Hospital Philips <br />Internet J- \ Network X-Ray <br />I <br />Shared VPN <br />I Ultrasound Philips <br />I Patient CT � <br />Monitoring <br />L— ---------- <br />Action Required by Hospital: <br />Review and approve connection details. <br />- Complete appropriate Site Checklist. <br />- Configure and allow Site -to -Site access prior to setting up connectivity depending on the <br />access criteria that the HCF decides to implement (ex: Source IP filtering, destination IP <br />filtering, NAT assignment, etc.). <br />- Route traffic from within the hospital network with destination addresses 192.68.48.0/22 to <br />the designed IP provided by Philips. <br />Broadband Router Installed at Health Care Facility <br />This connectivity method is designed for customers who have a dedicated high speed <br />connection for Philips equipment. <br />Connectivity Details: <br />-An RSN Cisco 1711 or 1712 router will be preconfigured and installed at the HCF by Philips <br />in conjunction with the HCF IT representative. <br />- The VPN Tunnel will be an IPSEC, 3DES encrypted Tunnel using IKE and will be established <br />from the RSN-DC and terminated at the RSN Router on -site. <br />- One to One NAT is used to limit access to Philips equipment only. <br />- Router Config and IP auditing is enabled for Customer IT to view via website 24/7. <br />- Dedicated DSL connections are also supported. <br />Option 1: Parallel to HCF Firewall Connectivity Method <br />This connectivity method is designed for customers who prefer a Philips RSN Router installed <br />on site utilizing all the security features provided and managed by Philips. <br />General Network <br />---------------------------------- <br />Philips Router <br />Healthcare Facility <br />Overview <br />Philips Philips <br />Philips <br />(Not site specific) <br />�, �, <br />PACS Nuc Med <br />MR <br />Firewalls <br />Hospital <br />Philips <br />Internet <br />I <br />Network <br />X-Ray � <br />hilips VPN or <br />ite-to-Site VPN <br />0.CT <br />Ultrasound Patient <br />Philips <br />I <br />Monitoring <br />L------------------------------------ <br />Action Required by Hospital: <br />- Assign a fixed public IP Address from the ISP to be configured on the Philips router. This is <br />the DOTTED link on the picture connected to the firewall. <br />- Assign a Back end IP for the Philips router on the Hospital Network. <br />- Complete appropriate Site Checklist. <br />- Route traffic from within the hospital network with destination addresses 192.68.48.0/22 to <br />internal Philips router Ethernet interface. This is the DASHED line connected to the firewall. <br />General Network <br />Overview <br />(Not site specific) <br />Internet <br />hilips VP orN <br />Site -to -Site VPN <br />� Philips Healthcare Facility � <br />� I <br />Router Philips <br />I Philips Nuc Med Philips � <br />PACE MR <br />Hospital <br />Network <br />Ultrasound Philips <br />CT <br />Patient Monitoring <br />---------------------------J <br />Action Required by Hospital: <br />- Assign a fixed public IP Address from the ISP to be configured on the Philips router. This is <br />the DOTTED link on the picture connected to the firewall. <br />- Assign a Back end IP for the Philips router on the Hospital Network. <br />- Complete appropriate Site Checklist. <br />- Route traffic from within the hospital network with destination addresses 192.68.48.0/22 to <br />internal Philips router Ethernet interface. This is the DASHED line connected to the firewall. <br />- Configure and allow on the firewall on the DASHED line interface access between the IP <br />address allocated by the hospital to the Philips internal Ethernet router interface and the target <br />modality IP address. <br />Option 3: Router Installed Inside the HCF's DZM <br />This connectivity method is designed for customers who prefer the RSN Router installed inside <br />and existing, or new DMZ, allowing access to Philips equipment. <br />General Network <br />Overview <br />(Not site specific) <br />Internet <br />hilips VPN or <br />ite-to-Site VPN <br />— — — — — — — — — — — <br />I Phili ps Healthcare Facility <br />Router Philips <br />Nuc Med <br />Philips Philips <br />J� �a PACS i MR <br />Hospital Philips <br />Network X-Ray <br />Philips <br />Ultrasound CT <br />Patient <br />Monitoring <br />— -----J <br />Action Required by Hospital: <br />- Assign a fixed public IP Address from the ISP to be configured on the Philips router. This is the <br />DOTTED link on the picture connected to the firewall. <br />- Assign a Back end IP for the Philips router on the Hospital Network. <br />- Complete appropriate Site Checklist. <br />- Route traffic from within the hospital network with destination addresses 192.68.48.0/22 to <br />internal Philips router Ethernet interface. This is the DASHED line connected to the firewall. <br />- Configure and allow on the firewall on the DASHED line interface IPSec protocol <br />communication by opening protocol 500, 50, 51, 47 and port 23 + TACACS. Traffic should be <br />between external IP Address located on the Philips router and the RSN Data center IP address <br />192.68.48/24 and IP address AOSN TACAS. <br />- Configure and allow on the firewall on the DASHED line interface access between the IP <br />address allocated by the hospital to the Philips internal Ethernet router interface and the target <br />modality IP address. <br />(20.0) <br />aw <br />L uj <br />4) H <br />W <br />i 2 <br />D <br />V o <br />® 0-6 <br />Z <br />p o <br />•_ U i <br />:D0 <br />Z <br />® o- <br />U <br />•® ® � <br />Z o <br />N < <br />®� (D 0 <br />o N L ® > 0 <br />aQaVW� Q(D <br />W N <br />�CL <br />�( <br />CO4- <br />Z� <br />o <br />U-0 <br />W M <br />o E m .f <br />0) o U O > <br />0 � 0)o C o <br />s Z <br />a) <br />CQ �' �' <br />N <br />Q o <br />L cc LLi m <br />2 N N o 0.0 <br />tm -0 a ZE <br />o E Z z". <br />Z p�q�, <br />fn <br />j U _ � Z 0 <br />a)® <br />o E W <br />a C 0 W o �C <br />O-0 <br />F� <br />L <br />D 0 <br />U0) <br />¢m <br />o <br />cv ® Q <br />r o ®� <br />W i <br />o ®o <br />Q N (3) M 0 C <br />45 of <br />j- o L <br />E ® = ON oLr) (� <br />Z <br />L <br />in <br />T Zo U 0 <br />L, Q 0 <br />L1J ® L o <br />o - F- <br />C) z o C) O Z <br />p 0 <br />�C <br />�E <br />N10� <br />z� <br />W <br />F_ 0- <br />06.26.2020 <br />