The Connection Agreement replaces the N3 Information Governance Statement of Compliance (IGSoC). In doing this, the arrangements for being able to use HSCN have been separated from those relating to accessing data or systems available on HSCN. See the Information Governance and data security section below.

Every organisation that wishes to use HSCN must complete a Connection Agreement. By 'use HSCN', we mean 'send or receive data across HSCN'. Signing this agreement will mean that your organisation is ready to be connected to the HSCN once you've identified an HSCN supplier.

The HSCN Connection Agreement is organisation-centric: each organisation must sign just one Connection Agreement no matter how many locations or HSCN connections they have or use.

See a copy of the HSCN Connection Agreement. Please note this downloadable copy is for information purposes only. To sign the HSCN Connection Agreement for your organisation please follow the process below.

Change control process for Connection Agreements

In the event that the Connection Agreement needs to be updated, the change will be carried out by the HSCN Authority in line with its documented change control procedures. A log of the changes made via this process can be accessed in the HSCN Connection Agreement Version Control Log.

To access and sign the HSCN Connection Agreement, essential for connecting to HSCN, a representative of your organisation must confirm that your intended use for HSCN aligns with the following statement:

The guidance below is intended to help you to understand the different types of Connection Agreement available and judge whether your organisation needs to sign one.

The different kinds of Connection Agreement

There are three types of HSCN Connection Agreement:

1. Standard - most HSCN users will sign this Connection Agreement.
2. Organisations representing other HSCN Consumers  - for CCGs representing GPs.
3. IT service providers - for organisations which provide IT services (such as infrastructure or hosting services) to other HSCN users.

In addition, for each type there are "1 Part" and "2 Part" sub-types:

1. The 1 Part Connection Agreement relates to the use of HSCN only.
2. The 2 Part Connection Agreement relates to the use of both the Transition Network (formerly N3) and HSCN.

The combination of these three types and two sub-types means that there are six possible variations of the HSCN Connection Agreement. 

The HSCN Portal will automatically present the correct type and sub-type for you to sign based on NHS Digital's understanding of your organisation. If for any reason you do not believe this is correct, please contact enquiries@nhsdigital.nhs.uk to discuss this.

Important note: if your organisation currently uses the Transition Network (formerly N3) then you need to sign a 2 Part Connection Agreement as soon as possible regardless of your HSCN migration plans/timelines. See the Existing Transition Network customers section above.

Does my organisation need to sign a Connection Agreement?

All organisations using, or with access to HSCN will need to sign a Connection Agreement (subject to the "Shared Connection" scenario below). 

Answer the questions presented in Figure 1 below to ascertain whether your organisation needs to sign a Connection Agreement. Further information regarding the "Shared Connection Scenario" is given in the following section.

Figure1. Connection Agreement Business Rules

The "Shared Connection Scenario" explained

If, for any reason, one or more other organisations use your HSCN connection, such as members of a community of interest network (CoIN), then you are responsible for ensuring that they are bound to the terms and conditions set out in the Connection Agreement. Clauses 4.2.2.1 and 4.2.2.2 in the Connection Agreement (paraphrased here) represent a choice that you can make about how to manage this:

1. Ensure that any other organisations using your connection have signed the Connection Agreement (this is choice 4.2.2.1)
2. Enter into a legally binding agreement with the organisations that use your connection with terms and conditions identical to those set out in the Connection Agreement (this is choice 4.2.2.2)

If you opt for 4.2.2.2 then the organisations using your connection do not need to sign a Connection Agreement. They will, however, need to enter into a legally binding agreement with your organisation which the HSCN Authority has the right to audit at any time.

Figure 2 below depicts a scenario in which an organisation has opted to follow clause 4.2.2.1. In this scenario an agreement exists between the HSCN Authority and both Org 1 and Org 2.

Figure 2, Scenario 4.2.2.1

Figure 3 below depicts a scenario in which an organisation has opted to follow clause 4.2.2.2. In that scenario an agreement exists between:

1. The HSCN Authority and Org 1
2. Org 1 and Org 2

The "local" agreement between Org 1 and Org 2 means that Org 2 does not need to enter directly into an agreement with the HSCN Authority i.e. by signing the HSCN Connection Agreement. The risks and responsibilities associated with this option are held by Org 1. If, in future, Org 2 wants to procure its own HSCN connection then it must sign an HSCN Connection Agreement. The "local" agreement between Orgs 1 and 2 will not be sufficient for Org 2's chosen CNSP who is obliged to ensure that its customers have signed a Connection Agreement before delivering a live service.

Figure 3. Scenario 4.2.2.2

The Information Governance Toolkit (IGT) has now been replaced by the Data Security and Protection Toolkit (DSPT).

It is not necessary to complete a Data Security and Protection Toolkit (DSPT) assessment in order to gain access to HSCN. However, all organisations that have or require access to NHS patient data and systems must use this toolkit to provide assurance that they are practising good data security and that personal information is handled correctly.

This means that having an HSCN connection does not automatically grant your organisation access to the systems and services available on it. A DSPT assessment is still required to access NHS Digital’s national applications (such as the NHS e-Referral Service (ERS), Personal Demographics Service (PDS) and Secondary Uses Service (SUS)). Other suppliers may have alternative prerequisites for access to their systems.

More information about the systems and services provided by NHS Digital can be found on the NHS Digital systems and services page.

HSCN is a private network, designed as a reliable business resource to carry information, which is only available to certain organisations. This is very different from a 'secure' network.

HSCN doesn't provide security to prevent loss, tampering, authenticity or inappropriate usage of the information it carries or the systems or services available through it.

This means that if patient data or personal data is being transmitted across HSCN, then encryption must be used. It also means that if you provide systems or services over HSCN, it's your responsibility to secure them and to make decisions about who can access those systems or services.

The National Cyber Security Centre provides useful information on encryption and how to protect your data in transit.

Please note, in the context of this information, that HSCN Suppliers are obliged to operate their networks in line with the requirements set out in the Communications-Electronics Security Group (CESG) Assured Services (Telecoms) [CAS(T)] scheme.

More about the Connection Agreement

The Connection Agreement sets out a collaborative way of working, which means:

• HSCN customers acknowledge responsibility for securing information - practically, this means that patient data should always be encrypted when being sent across any network, including the HSCN
• ownership and responsibility for the use of the HSCN connection sits at a senior level within the organisation
• HSCN customers give enough information to allow us to understand which organisations are using each HSCN connection
• if there are organisations that haven't signed a Connection Agreement, then those organisations cannot route information to or from the HSCN - practically, this means making arrangements with your supplier to prevent this, for example by adding access restrictions to firewalls
• HSCN customers provide security contact details so we can work with those customers if we detect or suspect a cyber incident or malicious activity across that HSCN connection
• NHS Digital's Data Security Centre will work with HSCN customers to resolve issues - however, as the HSCN is an important business resource, NHS Digital does retain the right to restrict access in exceptional circumstances

The Connection Agreement  sets out arrangements that could apply in the event of a dispute with your supplier - these arrangements are designed to make dispute resolution simpler and more cost effective in the unlikely event that a dispute occurs.

It also meets Data Protection responsibilities:

• by clarifying the relationship between HSCN customers, NHS Digital and its service providers, such as the internet content checking service provider
• by satisfying the Data Protection duty of data controllers to have written agreements with those parties that may process their data