What’s included in our server hosting?
As standard
- Purchase or use of a high performance HP Proliant series server
- Full CarePaq-based maintenance
- ILO Advanced pack installation
- Windows 2003 Server
- Monitoring Agents
- Server Build & Install
- Hosting (rack space, power, cooling, etc.)
- Server management
- Backup services (advanced, offsite backup)
- Support services – helpdesk
- 24x7x365 monitoring and response
- Bandwidth
- Advice and someone to talk your needs through with also come as standard - always.
Depending on requirements
- Additional software licences
- User support
- Load balancing, failover, security and performance consultancy and design
- How quickly can you set up our hosting?
- For simple server and application hosting we can normally have you up and running within 2 weeks of you placing an order with us; this includes ordering, configuring and installing hardware and obtaining Code of Connect where needed. Extensive server farms may require some further order and setup time.
- Hosting on our shared boxes can typically be arranged in just a couple of days
What is the Compaq Carepaq?
This is a 4-hour-fix support service that HP/Compaq provide for their servers in the event of a hardware failure.
What Hardware do we use?
We always use HP/Compaq equipment because, in our experience, it is reliable and their support services are superior to other vendors. Our typical server is a Proliant DL380 G-series Xeon based rack server.
How are the servers monitored?
All our servers are monitored constantly. The monitoring is automated by the installation of agents on the server. Output from these agents is then displayed within an application used by our service desk and Carelink support team. Alerts about potential issues can be responded to before they become full-blown incidents.
How can we have access to the server?
There are several ways that this can be achieved and we usually resolve this in discussion with yourselves and our lead engineer, who is responsible for the support of the platform. Options include ftp and http access. In some cases Terminal Services access to applications or even supervised physical to our server rooms can be arranged. Given the combined needs for security and resilience we ask our customers to understand that we place stringent controls on access to our environment.
Do applications need to be hosted on the N3 platform to be N3 compliant or could NHS sites simply connect directly via the internet?
No, applications do not have to be approved as compliant to be offered to the NHS. However there is a requirement to protect the data, especially any that identifies individuals. The options are to use a Connecting for Health approved hosting environment and allow the data to be transmitted over N3 or to ensure the data is strongly encrypted and secured. It is possible that all NHS sites may not have Internet access, in this case hosting on N3 provides an alternative means of access.
What does compliance really mean?
Compliancy refers to the hosting environment from which the application is served to the N3 network; as mentioned above, applications themselves do not need to be tested for compliance. Any N3 connected environment needs to be approved by CfH, by way of an independent audit, to ensure that the integrity of the N3 network is maintained. This approval is known as a “Code of Connection”.
Are applications hosted on our N3 platform allowed to communicate over the internet with external sites and users and if so are there constraints or limitations?
Yes, that’s exactly what our environment allows. The main constraints are:
- Applications in our hosting environment may not initiate outbound connections to systems on the N3 network
- Through connections are not permitted – so you cannot access other sites and resources on N3 directly through our connection.
- You may not push advertising or malware onto the N3 network
As of March 2007 these restrictions have been relaxed somewhat, provided we can convince CfH that the connections are secure and non-disruptive
Can NHS sites not on N3 be able to access systems from outside the N3 Network, i.e. through the worldwide web?
Yes, although the great majority of NHS locations are now N3 connected, those that aren’t (or where there are mobile working requirements) can have access to applications and data hosted on our site via the internet.
Does N3 impose constraints on sharing patient data with external bodies provided that they have authorised access?
The N3 network does not impose a technical constraint, however this is always a matter for the Caldecott Guardians at the respective trusts and must be considered in any such project.
Can users access the hosted system via the worldwide web (or VPN networks) using any form of connection (i.e. telephone, mobile, ISDN, ASDL etc.)?
Yes, once there is a connection to the Internet through an ISP the application etc. is available.
Is there a cost premium for hosting applications with a N3 hosting provider and if so why?
There is an increase in cost over hosting on the Internet alone. This additional cost is related to the provision of N3 bandwidth (which is amazingly expensive) and the overhead of maintaining an N3 compliant environment. We aim to provide good value by sharing our N3 connection over many clients, providing high burst capacity, with multi-user load balancing.
Does the reliability of the N3 network impact the downtime of hosted applications also accessible via the worldwide web?
There is no interdependence between the N3 network and the Internet, so the loss of either one would not affect the other. We have not found any significant issues with the N3 network in terms of reliability – though some trusts have experienced bottle necking at times due to local traffic. Both our N3 and Internet connections are resilient, as is our entire environment. This enables us to provide a high availability service with close to 100% uptime. However, any system is only strong as its weakest link and single points of failure within the client’s own systems may have an impact on uptime.