This article is only valid for Guardian v2 - therefore removed from general public

Please refer to enclosed network topology diagram in conjunction with these notes

K2MS Bedside Portal

• Portal supplied by K2MS.
  
• Portals and Central Station use TCP port 1433 to communicate to the database server.
  
• Portals, Central Station share live data via broadcast or multicast traffic using UDP port 5025 and TCP port 5073. These devices should be part of a dedicated VLAN.
  
• Routed access from the K2 VLAN is required for Portals, Central Station to connect to the database server and web server from within the VLAN.
  
• If wireless Portals employed, multicast traffic will need to pass between the wireless network and the K2 VLAN if wireless Portals are required to communicate with Central Station.
  
• A unicast environment can be created instead of a broadcast environment. Whilst the system can be configured to use unicast, this can increase network traffic and reduce system redundancy.
  
• Portals print by sending a Microsoft XPS file to the K2 Print Server, which prints the document to a local printer. The print server can be installed on any PC, but is normally installed on the Central Station. This removes the requirement for Portals to have specific printer drivers installed and simplifies printer support. Communication is via TCP 4530.
  
• Portals need to be able to communicate with the database server, Central Station and each other and some of this communication may be broadcast based.
  
• The default computer names are K2MSPortalxx, where xx is a two digit sequential number. Should the Customer require anything different, please specify.
  
• K2MS recommends using dynamic IP addresses, however if static addresses are required please specify.
  

Central Station (Central Surveillance)

• Hardware supplied by the Hospital.
  
• Displays live chalk board / patient list and CTG traces derived from Real-Time data. Normally comprises one large (42” or larger) display for the chalkboard and two smaller (24”) displays for CTG trace data. Each CTG screen can display up to 9 traces at once.
  
• Normally located centrally on the delivery ward with easy access to midwives.
  
• Communicates with the SQL server on TCP 1433.
  
• Must be able to receive Real-Time data from Portals on the delivery ward and any other Portals that the Hospital wishes to have displayed on the ward. Real time data is normally sent to the network broadcast address on UDP port 5025.
  
• Normally runs the K2 Print Server to allow printing from Portals, communicating on TCP 4530.
  
• Normally runs the Broadcast Relay, which forwards the Real-Time data from the ward to the Web Server, which can then transmit it to Athena or Web Connect clients for display in the labour ward view. Communication between the Broadcast Relay and the web server uses TCP 5073.
  

• Hardware supplied by and Server managed by the Hospital.
  
• Server running Microsoft SQL Server and holding a minimum of the K2MS Live database, but may also hold training and test databases.
  
• Can be an existing SQL Server managed by the trust or a dedicated server.
  
• Communicates with all K2 systems on TCP 1433.
  
• RDP access via VPN recommended for K2MS to provide support.
  

K2MS Guardian Web Server

• Hardware supplied by and server managed by the Hospital.
  
• Server running IIS and hosting the Clinical Web Portal, an internal site allowing read-only access to Guardian data.
  
• Runs the Real Time Service, which communicates with the Broadcast Relay and forwards Real-Time data from the Portals to Athena and Web Connect clients. This communication uses TCP 5073 to the Broadcast Relay and TCP 4530 to clients.
  
• Communicates with database server on TCP 1433.
  
• RDP access via VPN required for K2MS to provide support.