Data Processing Contract (NHS)

PART 1 – DEFINITIONS AND CLAUSES

This Agreement is dated .

1. PARTIES

A. Patients Know Best (“PKB”); and

B. The Providers (listed in Schedule 4), (“Providers”), each a “Party” and together the “Parties”. 

2. BACKGROUND

A. The Lead Controller has contracted with PKB under the Commissioning Contract to provide patients with access to and some control of their health data. The PKB platform facilitates patient access to their health data contributed by the Providers and facilitates the patient to add information which may be viewed by their health and care providers and other people of their choosing. The Providers are all organisations with a legal duty to provide free at the point of delivery care to individuals (as part of the NHS), to which PKB supports the facilitation of this duty.

B. Data received by PKB from the Providers is here referred to as the Patient Record. 

C. Providers are Independent Controllers and PKB are Processors of the Patient Record.

D. Where a Patient has activated access to their health data, any personal data entered by them is referred to as the Patient Account. 

E. PKB is the Controller for data within the Patient Account.

F. Where personal data within the Patient Account is accessed by a Provider, PKB and the accessing Provider are Joint Controllers.

G. The Parties consider it is necessary to use certain Personal Data between them to give effect to the objectives of the Processing and this Joint Controller Arrangement and Data Processing Contract (“Agreement”) sets out the framework for such use, including the principles and procedures that the Parties shall adhere to and the responsibilities the Parties owe to each other.

H. Where PKB are Processors for the Providers, Part 1, 3, 4 and the Schedules shall apply. 

I. Where PKB are Joint Controllers with the Providers, Parts 1,2,4 and the Schedules shall apply.

3. DEFINITIONS AND INTERPRETATION

3.1 Unless specifically provided for in this Agreement, the following terms shall have the following meanings:

3.2 The following rules of interpretation apply to this Agreement:

3.2.1 clause, schedule, and paragraph headings shall not affect the interpretation of this Agreement.

3.2.2 a person includes a natural person, corporate or unincorporated body (whether or not having separate legal personality).

3.2.3 the Schedules form part of this Agreement and shall have effect as if set out in full in the body of this Agreement. Any reference to this Agreement includes the Schedules;

3.2.4 unless the context otherwise requires, words in the singular shall include the plural and, in the plural, shall include the singular;

3.2.5 a reference to a statute, statutory provision or other legal instrument is a reference to it as amended, extended, or re-enacted from time to time; and

3.2.6 any words following the terms including, include, in particular, for example or any similar expression shall be construed as illustrative and shall not limit the sense of the words, description, definition, phrase or term preceding those terms.

3.3 In the event and to the extent of a conflict between: 

3.3.1 the main body of this Agreement and the Schedules, except as expressly stated otherwise, the main body of this Agreement shall prevail to the extent of such conflict.

4. SCOPE AND APPLICATION

4.1 This Agreement applies to the processing of Personal Data on the PKB Platform. Any reference in this Agreement to PKB Data shall be interpreted as a reference to any Personal Data held on the PKB Platform.

4.2 For the purpose of Data Protection Laws, this Arrangement shall prevail in the event of a conflict with the Commissioning Contract and any other agreement between the Parties and PKB.

4.3 For the avoidance of doubt, PKB will comply with all necessary data protection obligations while acting as sole controller.

4.4 Where PKB Data under this Agreement is accessed by another Provider organisation, that organisation shall be considered a Third Party under Article 4 of UK GDPR.

5. COMMENCEMENT AND DURATION

5.1 This Agreement shall commence on the date set out at the top of it (the “Commencement Date”) and shall continue in accordance with its terms.

6. PATIENT AND REGULATORY ENGAGEMENT

6.1 Prior to the commencement of Processing, in respect of the activities contemplated by this Agreement, the Parties shall cooperate with each other to: 

6.1.1 conduct patient engagement activities to assist the Parties in considering the views of patients; and

6.1.2 develop supporting materials for the provision of information to patients regarding the Processing of PKB Data;

6.1.3 For a period of not less than eight weeks, promote by all reasonably available and effective communication channels with patients and the public the proposed processing activity, purpose, risks and expected benefits using a layered approach and notifying and explaining the right and process for opting out.

6.2 Following the commencement of processing activity, the Providers will continue to promote the proposed processing activity in accordance with their duty of transparency.

7. AGREED PURPOSES

7.1 The Parties agree to only Process PKB Data under this Agreement for:

7.1.1 The provision of health and social treatment and care

7.1.2 Provide a platform for patients to access and add to their PKB health record

7.1.3 Allow patients to determine which organisations can view their profile

7.1.4 Maintaining a patient level record for statutory period

7.1.5 The maintenance by PKB of the PKB platform and data held on it

7.1.6 [Add here other purpose agreed by the parties]

each of the above, an “Agreed Purpose”.

PART 2  - APPLICABLE WHERE A JOINT CONTROLLER RELATIONSHIP EXISTS

8. LAWFUL BASES FOR PROCESSING AND CLASSIFICATION OF PARTIES

8.1 The lawful bases for each Party’s Processing of Personal Data and the classification of the Parties for the purposes of Data Protection Law under this Agreement is set out in Schedule 2.

9. PROVIDER’S RESPONSIBILITY FOR PATIENT-FACING COMMUNICATIONS.

9.1 Generally

9.1.1 Except where expressly stated in this Agreement or agreed by the Parties in writing, Providers shall be responsible for all communications with Data Subjects in relation to Personal Data covered by this Part 2, prior to the creation of the Patient Account:

9.1.1.1 the provision of information to Data Subjects in accordance with Article 13 and 14 of the GDPR;

9.1.1.2 responding to Data Subject Requests as set out in clause 9.2; 

9.1.1.3 notifying Data Subjects of a Personal Data Breach where such notification is required by Data Protection Law.

9.1.2 Notwithstanding the above, each of the Parties acknowledges that a Data Subject may exercise its rights under Data Protection Law against and of the Parties in relation to Personal Data covered by this Part 2  under this Agreement and nothing in this Agreement shall prevent either Party from complying with its obligations under Data Protection Law.

9.2 Data Subject Access Requests.

9.2.1 If either Party receives a Data Subject Access Request related to Personal Data covered by this Part 2: 

9.2.1.1 it shall notify the other within five (5) Business Days of receiving the Data Subject Access Request;

9.2.1.2 Each Providers shall be responsible for responding to the Data Subject Access Request received by them;

9.2.1.3 PKB shall provide Providers with reasonable assistance in responding to the Data Subject Access Request including, taking into account the nature of the Processing, assisting Providers by appropriate technical and organisational measures, insofar as this is possible to respond to requests from Data Subjects exercising their rights under Data Protection Law; and

9.2.1.4 Providers shall keep PKB reasonably informed as to the status and resolution of the Data Subject Access Request.

10. DATA MINIMISATION (INCLUDING OPT-OUT) AND PSEUDONYMISATION

10.1 Taking into the cost of implementation and the nature, scope, context and purposes of Processing as well as the risks of varying likelihood and severity for rights and freedoms of Data Subjects each Party shall implement appropriate technical and organisational measures, including pseudonymisation, to ensure that the use of Personal Data in relation to the processing is minimised. 

10.2 Each Party shall periodically review data minimisation measures implemented in accordance with this clause 10, and may agree with the other Party further steps to be taken to ensure the minimisation of Personal Data as may be required by Data Protection Law and in any case no less than every three years.

11. GENERAL OBLIGATIONS OF THE PARTIES

11.1 Each Party shall implement appropriate technical and organisational measures to protect Personal Data against unauthorised or accidental access, loss, alteration, disclosure, destruction or other unauthorised or unlawful forms of Processing (such measures may include, where appropriate, the pseudonymisation and encryption of Personal Data covered by this Part 2 and other measures referred to in Article 32(1) of the GDPR).

11.2 Each Party shall ensure that its personnel who have access to Personal Data covered by this Part 2 for the performance of this Agreement are under an obligation of confidentiality and ensure that such access is limited to those individuals who need to know and access PKB Data.

11.3 Upon becoming aware of a Personal Data Breach relating processing where both Parties are Joint Controllers, each Party shall: 

11.3.1 notify the other Party in writing without undue delay, and in any event within forty-eight (48) hours, (such notification to include the provision of information as is required under Data Protection Law in respect of the Personal Data Breach); 

11.3.2 promptly take reasonable steps to investigate, mitigate and remediate the Personal Data Breach; and 

11.3.3 provide reasonable assistance to the other Party, in relation to the other Party’s efforts to investigate, mitigate and remediate the Personal Data Breach. 

11.4 PKB shall not transfer Personal Data covered by this Part 2 from the United Kingdom to another jurisdiction without the prior written approval of the Providers and without putting in place appropriate safeguards where required for compliance with Data Protection Law.

11.5 Each Party shall notify the other Parties in writing within five (5) Business Days if it receives a “Third Party Communication” including but not limited to:

11.5.1 any communication from the ICO or any other regulatory authority in connection with Personal Data covered by this Part 2  or;

11.5.2 a request from any third party for disclosure of Personal Data covered by this Part 2 where compliance with such request is required or purported to be required by Applicable Law,

11.6 Each Party shall provide the other Party with reasonable assistance in responding to any Third Party Communication and shall work with the other Party to determine the most appropriate Controller to respond to any Third Party Communication (the “Responsible Controller”) provided that nothing in this Agreement shall prevent a Party from responding to a Third Party Communication to the extent required by Applicable Law. 

11.7 The Responsible Controller shall keep the other Party informed as to the status of the resolution of any Third-Party Communication, and the Parties shall provide all such assistance to one another as may be reasonably requested in respect of the same. 

11.8 Each Party shall provide reasonable assistance to the other Party in ensuring compliance with its obligations under Data Protection Law taking into account the nature of the Processing for the purposes of this Agreement and the information available to it, including in respect of each Party’s obligations as set out in this Agreement relating to:

11.8.1 security of Processing;

11.8.2 notification of a Personal Data Breach to the ICO;

11.8.3 communication of a Personal Data Breach to the affected Data Subjects; and

11.8.4 Data Protection Impact Assessments and any subsequent consultations with the ICO.

11.9 Each Party shall provide the other Party with such information as the other Party may reasonably request to demonstrate compliance with this Agreement, and if the requesting Party (acting reasonably) considers that such information does not demonstrate the other Party’s compliance with this Agreement, to allow for audits, including inspections, by the requesting Party or an auditor mandated by the requesting Party to verify the other Party’s compliance with this Agreement subject to: 

11.9.1 such audit or inspection being conducted during the other Party’s usual business hours and on reasonable advance notice; and 

11.9.2 the Party conducting the audit and any third-party auditor: 

11.9.3 using reasonable endeavours to minimise any disruption on the other Party’s business; and

11.9.4 complying with any reasonable requirements imposed by the other Party to protect the safety, integrity and security of its premises and systems, and the confidentiality of the other Party’s or third-party confidential information.

11.10 Each Party shall bear its own costs of any audit or inspection under clause 11.9, unless the audit or inspection was conducted by an independent third party and such third party determines the audited Party has materially breached its obligations under this Agreement in which case the audited Party shall reimburse the auditing Party in respect of its reasonable and properly incurred costs of engaging such third party to conduct such audit or inspection.

11.11 The Parties shall keep this Agreement under review and either Party may request a change to this Agreement as may be reasonably required to comply with Data Protection Law. Upon receipt of such a request from a Party, the Parties shall discuss and consider such request in good faith and do all things reasonably necessary to comply with Data Protection Law, including varying this Agreement or entering into any subsequent agreements.

12. JOINT CONTROLLERS

12.1 Each Party acknowledges and agrees that there is a common objective in respect of the Processing and are Joint Controllers for the purpose of Data Protection Law in respect of such Processing. 

12.2 Each of the Parties shall perform the obligations allocated to it the table below following allocation of responsibilities in accordance with Article 26 of the GDPR:

13. USE OF PROCESSORS

13.1 Where PKB uses a Processor to Process Personal Data covered by this Part 2 a, PKB shall:

13.2 provide Providers with such information regarding such processors as Providers may reasonably request. For clarity, PKB shall not be required to provide Providers with details of any commercial terms between PKB and any Processor; 

13.3 ensure that such Processing is subject to an agreement as required by Article 28(3) of the GDPR; and

13.4 where Providers have provided their prior written approval to the international transfer of Personal Data covered by this Part 2  conduct such international transfer in accordance with Data Protection Law.

14. COMBINATION WITH OTHER DATA

14.1 Providers acknowledge and agree that PKB may combine Providers Data to external sources of health data (including other Trusts, patient inputted data and third-party application data) with the objective of increasing the quality and breadth of the Personal Data covered by this Part 2.

15. DATA RETENTION AND DELETION

15.1 The Parties shall not retain or Process Personal Data covered by this Part 2 under this Agreement for longer than is necessary to carry out the Agreed Purposes. 

PART 3 – APPLICABLE WHERE PKB IS A PROCESSOR 

16. The Parties acknowledge that for the purposes of the Data Protection Legislation that the Providers are the Controller and PKB is the Processor. The only processing that the Processor is authorised to do is set out in Schedule 1, which is attached to and forms part of this agreement, by the Controller and may not be determined by the Processor.

16.1 The Processor shall notify the Controller within 72 hours if it considers that any of the Controller’s instructions infringe Data Protection Legislation.  

16.2 The Processor shall provide all reasonable assistance to the Controller in the preparation of any Data Protection Impact Assessment prior to commencing any processing. Such assistance may, at the discretion of the Controller, include:

(a.) a systematic description of the envisaged processing operations and the purpose of the processing;

(b.) an assessment of the necessity and proportionality of the processing operations in relation to the Services;

(c.) an assessment of the risks to the rights and freedoms of Data Subjects; and

(d.) the measures envisaged to address the risks, including safeguards, security measures and mechanisms to ensure the protection of Personal Data.

16.3 The Processor shall, in relation to any Personal Data Processed in connection with its obligations under this Agreement:

(a.) process that Personal Data only in accordance with Schedule 1, unless the Processor is required to do otherwise by Law. If it is so required, the Processor shall promptly notify the Controller before processing the Personal Data unless prohibited by Law;

(b.) ensure that all measures in Schedule 2 are adhered to and met at all times of the processing and has in place all Protective Measures, which have been reviewed and approved by the Controller as appropriate to protect against a Data Loss Event having taken account of:

i. the nature of the data to be protected;

ii. the harm and risks that might result from a Data Loss Event;

iii. assessment of the technical and non-technical controls to mitigate these risks; and

iv. the cost of implementing any measures if required;

v. ensuring that the Processor Personnel do not process Personal Data except in accordance with this Agreement, and in particular Schedule 1;

vi. taking all reasonable steps further detailed in schedule 2, both technical and non-technical to ensure the reliability and integrity of any Processor Personnel who have access to the Personal Data and ensure that they:

(c.) are aware of and comply with the Processor’s duties under this clause;

(d.) are subject to appropriate confidentiality undertakings with the Processor or any Sub-processor. This includes but is not limited to commercially sensitive information and Personal Data;

(e.) are informed of the confidential nature of the Personal Data and commercially sensitive information and do not publish, disclose or divulge any of the Personal Data or commercially sensitive information to any third Party unless directed in writing to do so by the Controller or as otherwise permitted by this Agreement; and

(f.) have undergone adequate annual training in the use, care, protection and handling of Personal Data and are assessed as competent to undertake the processing activity or activities; 

(g.) keep personal data and commercially sensitive information confidential for the length of the contract and ensure that once the contract has ended or terminated that personal data and commercially sensitive information is kept confidential indefinitely.  

(h.) not transfer Personal Data outside of the European Economic Area (EEA) unless the prior written consent of the Controller has been obtained and the following conditions are fulfilled:

i. the Controller or the Processor has provided appropriate safeguards in relation to the transfer (whether in accordance with UK GDPR Article 46) as determined by the Controller;

ii. the Data Subject has enforceable rights and effective legal remedies;

iii. the Processor complies with its obligations under the Data Protection Legislation by providing an adequate level of protection to any Personal Data that is transferred (or, if it is not so bound, uses its best endeavours to assist the Controller in meeting its obligations); and

iv. the Processor complies with any reasonable instructions notified to it in advance by the Controller with respect to the processing of the Personal Data;

v. the Processor notifies the Data Controller prior to any transformation of the Personal Data which is not part of this agreed processing but occurs due to the transfer of Personal Data from the service provider to or from another organisation party to this agreement.

(i.) at the written direction of the Controller, delete or return the Personal   Data (and any copies of it) to the Controller on termination of the Agreement unless the Processor is required by Law to retain the Personal Data.

16.4 The Processor shall notify the Controller within 72 hours if it:

(a.) receives an Individual Rights Request or any Freedom of Information (FOI) / Environmental Information Regulations (EIR) request relating to this processing;

(b.) receives a request to rectify, block or erase or transfer any Personal Data by the data subject;

(c.) receives any other request, complaint or communication relating to either Party's obligations under the Data Protection Legislation;

(d.) receives any communication from the Information Commissioner or any other regulatory authority in connection with Personal Data Processed under this Agreement;

(e.) receives a request from any third Party for disclosure of Personal Data where compliance with such request is required or purported to be required by Law; or

(f.) becomes aware of a Data Loss Event.

16.5 The Processor’s obligation to notify under clause 16.4 shall include the provision of further information to the Controller in phases, as details become available.

16.6 Taking into account the nature of the processing, the Processor shall provide the Controller with full assistance in relation to either Party's obligations under Data Protection Legislation and any complaint, communication or request made under clause 16.4 (and insofar as possible within the timescales reasonably required by the Controller) including by promptly providing:

(a.) the Controller with full details and copies of the complaint, communication, data loss event or request;

(b.) such assistance as is reasonably requested by the Controller to enable the Controller to comply with an Individual Rights Request within the relevant timescales set out in the Data Protection Legislation;

(c.) the Controller, at its request, with any Personal Data it holds in relation to a Data Subject;

(d.) assistance as requested by the Controller following any data loss event;

(e.) assistance as requested by the Controller with respect to any request from the Information Commissioner’s Office, or any consultation by the Controller with the Information Commissioner's Office.

16.7 The Processor shall allow for audits of its Data Processing activity by the Controller or the Controller’s designated auditor. 

16.8 The Processor when ensuring that it has in place such Protective Measures, having been reviewed and approved by the Controller, shall follow the reasonable request of the Controller to supply such evidence as requested by the Controller within 28 days.  

16.9 The Processor shall designate a Data Protection Officer or where not required by Law, authorised responsible officer who is David Stone, dpo@patientsknowbest.com. 

16.10 Before any Personal Data is shared by the Providers with PKB, the Providers shall: 

16.10.1 identify and remove the Personal Data of any Data Subjects who have opted out of data being loaded to the PKB platform through a locally operated and promoted Opt-Out scheme; 

16.10.2 implement data minimisation measures as required by this clause 16.10 and as may be agreed by the Parties from time to time to ensure only approved data is loaded to the PKB platform; and

16.11 Before allowing any Sub-processor to process any Personal Data related to this Agreement, the Processor must:

(a.) notify the Controller in writing of the intended Sub-processor and processing; 

(b.) obtain the written consent of the Controller;

(c.) enter into a written agreement with the Sub-processor which gives effect to the terms set out in this clause 1 and associated schedules such that they apply to the Sub-processor; and

(d.) provide the Controller with such information regarding the Sub-processor as the Controller may reasonably require.

16.12 The Processor shall remain fully liable for all acts or omissions of any Sub-processor.

16.13 The Controller may, at any time on not less than 30 Working Days’ notice, revise this clause by replacing it with any applicable controller to processor standard clauses or similar terms forming part of an applicable certification scheme (which shall apply when incorporated by attachment to this Agreement).

16.14 The Parties agree to take account of any guidance issued by the Information Commissioner’s Office. The Controller may on not less than 30 Working Days’ notice to the Processor amend this agreement to ensure that it complies with any guidance issued by the Information Commissioner’s Office.

16.15 The Controller may immediately terminate this Agreement on written notice to the Processor. The Processor may not terminate this Agreement without the written consent of the Controller.

16.16 At the choice of the Controller, the Processor shall return or destroy all personal data to the Controller at the end of the provision of services relating to the processing and delete any existing copies.

16.17 The Processor warrants that it shall:

i.  Process the Personal Data in compliance with Law; and

ii. take appropriate technical and organisational measures against Data Breach.

16.18 The Processor agrees to indemnify and keep indemnified and defend at its own expense the Controller against all costs, claims, damages or expenses incurred by the Controller or for which the Controller may become liable due to any failure by the Processor or its employees or agents to comply with any of its obligations under this Agreement.

16.19 This Agreement is subject to English law and the exclusive jurisdiction of the English Courts.

16.20 Any variation (change request) to this agreement must be agreed by the Data Controller in advance of the change. This request must be in writing to the data controller and must be authorised in writing back to the Processor before any variation can take place.  The authorised officers who can approve, raise, reject or escalate variations to this agreement are detailed in Schedule 3 and can be updated from time to time in writing by either party. Any change that is authorised by the data controller must be acknowledged as a variation to this contract and parties who initially signed this agreement must also resign this agreement. This variation should be dated and clearly detailed within any subsequent agreement.  If the variation is rejected and the Processor is unable to continue meeting its obligations as part of this agreement, then this must be escalated to the data controller who has the right to terminate this agreement with immediate effect.  

16.21 Day to day management of this contract is undertaken by the parties as detailed in Schedule 3 which can be updated from time to time in writing by either party.

16.22 Where there is a dispute, the aggrieved Party shall notify the other Party in writing of the nature of the dispute with as much detail as possible about the deficient performance of the other party. A representative from senior management of each of the parties (together the "Representatives") shall meet in person or communicate by telephone within five Working Days of the date of the written notification in order to reach an agreement about the nature of the deficiency and the corrective action to be taken by the respective Parties. The Representatives shall produce a report about the nature of the dispute in detail to their respective boards and if no agreement is reached on corrective action, then the chief executives of each Party shall meet in person or communicate by telephone, to facilitate an agreement within five Working Days of a written notice by one to the other. If the dispute cannot be resolved at board level within a further five Working Days, or if the agreed upon completion dates in any written plan of corrective action are exceeded, either party may seek the legal remedies to which it is entitled under this agreement.

16.23 If the Processor listed in this Schedule is taken over, goes out of business or enters administration, then the representative of the Data Controller will decide on the next steps and endeavour to find an alternative data processor for the purposes of this project. However, in the event that there are no alternative Processor(s) (Data Processor(s), all data processing for the purposes of this project will come to an end and all relevant parties listed in this Data Processing Agreement will be notified accordingly. 

16.24 The Processor will ensure adequate business continuity services and disaster recovery services are in place and regularly tested. Evidence of this testing will be required as part of the Controller's due diligence.

PART 4 – APPLICABLE TO ALL

17. RECORDS

17.1 Each Party shall maintain such records as required by Data Protection Law in respect of its Processing of PKB Data and as may be reasonably necessary to demonstrate its compliance with this Agreement.

18. REVIEW OF THIS AGREEMENT

18.1 The effectiveness of this Agreement shall be reviewed from time to time at such intervals as may be agreed by the Governance Committee, having consideration to the Permitted Purposes and whether any amendments may be necessary to this Agreement. This review will involve assessing whether: 

18.1.1 this Agreement needs to be updated to comply with any amendments to Data Protection Law; and

18.1.2 Personal Data Breaches have been handled in accordance with this Agreement where PKB Data are involved.

19. WARRANTIES 

19.1 Each Party represents and warrants to the other Party that:

19.1.1 it has full capacity to enter into and perform this Agreement which has been duly executed by the required corporate action;

19.1.2 entry into and performance of this Agreement does and will not violate or be subject to any restriction in or by any other agreement or obligation. 

19.2 The use of PKB Data as permitted by this Agreement does not infringe the rights of any third party.

20. LIMITATION AND EXCLUSION OF LIABILITY 

20.1 Each Party’s liability arising out of or in connection with this Agreement, whether in contract, tort (including negligence) or otherwise shall be limited costs incurred by the other parties as a direct result of negligence of the Party, including failure to comply with this Agreement.

20.2 Each Party is responsible for the cost of remedying any non-compliance with Data Protection Laws determined the responsibility of that Party by this Arrangement. Liability under this Arrangement for each Party is limited to that which arises from a breach of Data Protection Laws.

20.3 Any liability arising from processing activity undertaken under this Arrangement shall be determined by the roles and responsibilities of each Party in line with Article 82 of GDPR. 

21. TERMINATION

21.1 Without affecting any other right or remedy available to it, either Party may terminate this Agreement with immediate effect by giving written notice to the other Party: 

21.1.1 if the other Party commits a material breach of this Agreement which breach is irremediable or (if such breach is remediable) fails to remedy that breach within a period of ninety (90) days after being notified in writing to do so; 

21.1.2 if the other Party repeatedly breaches any of the terms of this Agreement in such a manner as to reasonably justify the opinion that its conduct is inconsistent with it having the intention or ability to give effect to the terms of this Agreement;

21.1.3 if the other Party is subject to an Insolvency Event; 

21.1.4 if there is a change of control of the other Party excluding any intra-group reorganisation (or similar) of such other Party; or 

21.1.5 in accordance with clause 29. 

21.2 If the Commissioning Contract terminates for any reason this Agreement shall terminate automatically at the same time as the effective date of termination of the Commissioning Contract without any further action required by either Party.

21.3 Each Party’s rights to terminate this Agreement set out in this clause 21 shall not affect any other right or remedy available to it including those arising under this Agreement prior to termination.

22. CONSEQUENCES OF TERMINATION

Upon termination or expiry of this Agreement:

22.1 PKB will permanently delete Patient Record data which has not been accessed by the Providers. 

22.2 Return to the Providers a copy of Patient Record data which has been accessed by the Providers, after which it will be permanently deleted.

22.3 For the absence of doubt, Patient Accounts will be retained by PKB in accordance with their role and responsibilities as a Controller.

Termination or expiry of this Agreement shall not affect any rights, remedies, obligations or liabilities of the Parties that have accrued up to the date of termination or expiry, including the right to claim damages in respect of any breach of this Agreement which existed at or before the date of termination or expiry.

23. FORCE MAJEURE

1. Non-performance or delay of either Party will be excused to the extent that performance is caused by any circumstance beyond Party’s reasonable control, including strike, fire, natural disaster, governmental acts, orders or restrictions, failure of suppliers or subcontractors. In such circumstances the affected Party shall be entitled to a reasonable extension of time for performance. If the period of non-performance or delay continues for ninety (90) days, the Party not affected may terminate this Agreement immediately on written notice to the affected Party. 

2. ASSIGNMENT AND OTHER DEALINGS 

   1. Neither Party may assign or otherwise transfer any of its rights or obligations under this Agreement without the prior written approval of the other Party, except as expressly permitted by clause 24.2. 

   2. A Party may, upon written notice to the other Party and subject to the prior written approval of the other Party (such approval not to be unreasonably withheld or delayed), assign or otherwise transfer this Agreement to any of its affiliates or in connection with a change of control transaction (whether by merger, consolidation, sale of equity interests, sale of all or substantially all assets, or otherwise). For clarity, where such assignment or transfer would give rise to a breach of obligations in relation to Data Protection Law or other Applicable Law or may already affect any research ethics approvals or would not be expected in accordance with the common law duty of confidentiality, such grounds shall amongst other matters be considered reasonable for refusing approval to such assignment or transfer. Any assignment or other transfer in violation of this clause will be void. 

   3. This Agreement will be binding upon and inure to the benefit of the Parties hereto and their permitted successors and assigns.

3. VARIATION 

   1. No variation of this Agreement shall be effective unless it is in writing and signed by the Parties.

4. NOTICES 

   1. All notices required or permitted under this Agreement and all requests for approvals, consents and waivers must be delivered by a method providing for proof of delivery. Any notice or request will be deemed to have been given on the date of delivery. Notices and requests must be delivered to the Parties at the addresses on the first page of this Agreement until a different address has been designated by notice to the other Party.

5. SEVERANCE 

   1. If any provision of this Agreement is found to be unenforceable, such provision will be deemed to be deleted or narrowly construed to such extent as is necessary to make it enforceable and this Agreement will otherwise remain in full force and effect. 

6. RELATIONSHIP OF THE PARTIES

   1. The Parties are and will be independent contractors and neither Party has any right, power, or authority to act or create any obligation on behalf of the other Party.

7. RIGHTS AND REMEDIES 

   1. The rights and remedies provided under this Agreement are in addition to, and not exclusive of, any rights or remedies provided by law.

30. WAIVER 

    1. No term or provision of this Agreement will be deemed waived and no breach will be deemed excused, unless such waiver is in writing and signed by the Party claimed to have waived.

31. COUNTERPARTS 

    1. This Agreement may be executed in counterparts (which may be exchanged by facsimile or .pdf copies), each of which will be deemed an original, but all of which together will constitute the same Agreement.

32. THIRD PARTY RIGHTS 

    1. This Agreement does not give rise to any rights under the Contracts (Rights of Third Parties) Act 1999 to enforce any term of this Agreement.

33. FURTHER ASSURANCE 

    1. Each Party shall use reasonable endeavours to procure that any necessary third party shall, promptly execute and deliver such documents and perform such acts as may reasonably be required for the purpose of giving full effect to this Agreement.

34. COSTS 

    1. Each Party shall pay its own costs incurred in connection with the negotiation, preparation, and execution of this Agreement.

35. ENTIRE AGREEMENT 

    1. This Agreement constitutes the entire agreement between the Parties and supersedes and extinguishes all previous drafts, agreements, arrangements, and understandings between them, whether written or oral, relating to its subject matter.

    2. Each Party acknowledges that in entering into this Agreement it does not rely upon, and shall have no remedies in respect of, any representation or warranty (whether made innocently or negligently) that is not set out in this Agreement. No Party shall have any claim for innocent or negligent misrepresentation based on any statement in this Agreement.

36. GOVERNING LAW AND DISPUTE RESOLUTION

    1. Governing law

       1. This Agreement and all matters arising out of or in connection with it, including any Dispute and any dispute resolution procedure provided for in this Agreement, shall be governed by, and construed in accordance with, the law of England and Wales.

    2. Dispute resolution:

       1. The Parties shall resolve any Disputes in accordance with the Commissioning Contract terms.

37. SCHEDULE 1: DATA PROCESSING PARTICULARS

    1. PERSONAL DATA TO BE PROCESSED

       1. This Schedule describes the types of PKB Data that may be Processed under this Agreement. The Parties may agree to amend the descriptions in this clause at any time with the approval of the Parties.

       2. For clarity, PKB Data Processed under this Agreement shall be subject to the data minimisation measures described in clause 10, including:

    2. Providers applying data minimisation measures prior to sharing any data with PKB; and 

    3. the Parties continuing to review the data minimisation measures to ensure the minimisation of Personal Data within PKB Data as may be required by Data Protection Law.

       1. PKB Data to be Processed under this Agreement may include data from the following sources: 

4. The inclusion of personal data of any natural person under the age of 13 should be considered on a case by case basis.

38. SCHEDULE 2: PROCESSING OPERATIONS

2A PROCESSING OPERATION A

Processing Operation: Maintaining Patient Account

Performed by: PKB

Classification of Parties: PKB – Sole Controller

Lawful Bases for Processing: -Article 6(1)(f) and Article 9(2)(h)

Specific Responsibilities for Parties: N/A as no Joint Processing

Compliance with Principles

Principle 1 – Processing is lawful, fair and Transparent:

Individuals are invited to create an account by their healthcare provider (who has commissioned PKB) where they are able to provide their own personal data. Where this is the case, PKB acts as Sole Controller and as such provides the individual with transparency information when registering. 

Principle 2 – Collected for specific, explicit and legitimate purposes:

Personal data Processed by PKB within the patient account is only used for the purposes of providing that service to the individual to help the individual manage their health and care. It is not used for further purposes. 

Principle 3 – Adequate relevant and not excessive:

This Processing will only involve personal data provided by the patient themselves, and as such will be limited to the personal data provided by the patient.

Principle 4 – Accurate and up to date:

Given the personal data is provided by the patient, PKB will have no determination as to the accuracy of that data. However, this will be marked within the PKB system as patient inputted data, so it will be clear to those accessing within the Patient Record (in the case it is transferred to the Patient Record).

Principle 5 – Kept for no longer than is necessary:

The Patient Account will be kept for up to 8 years after the last access date by Providers.

Principle 6 – Processed securely

PKB implements strong technical and organisational controls to maintain the integrity and confidentiality of this Processing, including annual penetration testing, adherence to the Data Security and Protection Toolkit and a role-based training programme for all employees. 

2B PROCESSING OPERATION B

Processing Operation: Maintaining Patient-Inputted Data as part of the Patient Account where accessed by Provider.

Performed by: PKB and Providers

Classification of Parties: PKB and the Providers act as Joint Controllers.

Lawful Bases for Processing: 

Providers – Article 6(1)(e) and Article 9(2)(h)

PKB - Article 6(1)(e) and Article 9(2)(h)/(g)

Specific Responsibilities for Parties:

PKB provides the platform. 

PKB are responsible for providing the security around the platform.

The Providers are responsible for only providing access to those in their own organisation who require it.

Principle 1 – Processing is lawful, fair and Transparent:

Processing of the patient-inputted data is considered necessary in order to support the care of the individual and allows the individual to have more choice and engagement with regard to their health and care information. 

Principle 2 – Collected for specific, explicit and legitimate purposes:

Personal data Processed which is provided directly by the patient is Processed in line with the original purpose of collection.

Principle 3 – Adequate relevant and not excessive:

Patients will be responsible for the information provided by themselves and they are able to decide what is shared with the healthcare providers. 

Principle 4 – Accurate and up to date:

The accuracy of the information provided directly by patients is the responsibility of those patients which choose to do so, but all self-uploaded records are notified to clinicians as such to enable clinicians to make decisions based on the knowledge these are self-uploaded data items.

Principle 5 – Kept for no longer than is necessary:

The Patient-Inputted data will be kept for up to 8 years after the contract with Providers ends to maintain the integrity of the health record. 

Principle 6 – Processed securely

PKB implements strong technical and organisational controls to maintain the integrity and confidentiality of this Processing, including annual penetration testing, adherence to the Data Security and Protection Toolkit and a role-based training programme for all employees. 

2C PROCESSING OPERATION C

Processing Operation: Service Evaluation and Improvement

Performed by: PKB 

Classification of Parties: PKB as Independent Controller

Lawful Bases for Processing: 

PKB - Article 6(1)(f) 

Specific Responsibilities for Parties:

PKB will undertake service evaluation and improvement to improve the user experience for both clinicians and patients.

Principle 1 – Processing is lawful, fair and Transparent:

Processing for these purposes is detailed within the transparency information to inform individuals of the Processing. No special category data will be used for these purposes, and any personal data will be pseudonymised and aggregated where necessary for this purpose.

Principle 2 – Collected for specific, explicit and legitimate purposes:

The purpose of service evaluation and improvement is considered a compatible purpose of Processing against the original purpose of collection in order to support the original purpose Personal Data was collected.

Principle 3 – Adequate relevant and not excessive:

All Personal Data will undergo pseudonymisation and aggregation where necessary to ensure that only the minimum necessary personal data is used for this purpose.

Principle 4 – Accurate and up to date:

All Personal Data will be utilised directly from the PKB Account and Record to ensure it is accurate and up to date.

Principle 5 – Kept for no longer than is necessary:

Any Personal Data used for this purpose will be destroyed in line with standard PKB retention schedules. No Personal Data will be retained for longer for this specific purpose.

Principle 6 – Processed securely

PKB implements strong technical and organisational controls to maintain the integrity and confidentiality of this Processing, including annual penetration testing, adherence to the Data Security and Protection Toolkit and a role-based training programme for all employees. 

2D PROCESSING OPERATION D

Processing Operation: Maintaining Patient Record (where data originates from Provider)

Performed by: PKB and Providers

Classification of Parties: Provider as Controller, PKB as Processor

Lawful Bases for Processing: 

Providers - Article 6(1)(e) / Article 9(2)(h)

Specific Responsibilities for Parties:

PKB will only act under the following instruction of the Provider for this Processing operation 

39. SCHEDULE 3: SECURITY CONTROLS

39.1 SECURITY RESPONSIBILITIES

39.1.1 PKB shall maintain appropriate information security arrangements for all forms of Data held in any format and expressed or relayed in any communication (oral or written) in a manner consistent with the principles of the most current version of the NHS Data Security and Protection Toolkit (DSPT) and ISO 27002 - Code of Practice for Information Security Management (with the principles of the DSPT prevailing in case of any conflict). In particular:

39.1.2 PKB shall have management arrangements in place for the management of information security; 

39.1.3 PKB shall comply with the DSPT assessment, reporting and audit requirements relevant to its organisation type; and 

39.1.4 PKB shall have appropriate operational risk assessment and management processes in place for the identification, mitigation and management of operational security risks.

39.1.5 PKB shall ensure an appropriate level of protection for data at rest commensurate with the risks to rights and freedoms, including encryption to the latest available industry standard. 

39.1.6 PKB shall comply with the requirements of Article 32 of GDPR and ensure that all data is held and Processed according to the risk attached to the category of data Processed.

39.1.7 The Parties shall agree, and PKB shall have in place, an information security policy that is supported by appropriate organisational, security and technical security standards (the “Security Policy”).

39.1.8 PKB shall propose changes to the Security Policy on an on-going basis to reflect good industry practice or changes necessitated by any changes in applicable law. Material changes to the management of information relating to the Controller's business shall be agreed in writing by both parties, and the requirement for all such changes shall be promptly notified to the other party.

39.1.9 PKB shall create, design, establish, provide, implement, manage and maintain safeguards (including security architecture) that reflect the Security Policy and shall ensure that any changes to the Security Policy from time to time are reflected in the secure environment provided to Controller as soon as practicable.

39.1.10 PKB shall be equally responsible for managing information security risk should the Data, or access to the Data, be made available to any third parties or Processors (as may be permitted elsewhere). Such engagements will be preceded by a satisfactory due diligence process, contractual documentation being signed, and the establishment of monitoring, auditing and incident handling procedures so that the Data is no less secure under the third party’s management.

39.1.11 PKB shall ensure that all transfers of the Data undertaken by it or on its behalf will be in accordance with Secure File Transfer Protocols within the Health and Social Care Network (HSCN) and/or in accordance with the NHS Digital Good Practice Guidelines.

39.2 SECURITY MANAGEMENT

39.2.1 PKB shall plan, determine, create, implement, manage, review and maintain security control over the technology and physical storage infrastructure, and respond appropriately to security events. This includes the implementation of secure technical infrastructures, technologies and physical controls (including firewalls, encryption, authentication services and swipe access) appropriate to the UK public health sector.

39.2.2 PKB shall implement control, technologies and procedures to limit the risk of unauthorised access to the environment used to provide the Services (the "Services Environment") appropriate to the UK health and social care sector.

39.2.3 PKB shall inform and make recommendations to the Providers if it becomes aware of any products, methods or services that would result in required improvements to the security procedures in operation.

39.2.4 PKB shall create, acquire, provide, install, implement, manage and maintain any such improvements reasonably requested by the Providers that reflect Good Industry Practice.

39.3 SECURITY ADMINISTRATION

39.3.1 PKB shall track, co-ordinate, implement, manage and maintain all security changes across the Services.

39.3.2 PKB shall limit the risk of unauthorised access to the Services Environment including content filtering to prevent objectionable material, virus protection, password controls and physical security. PKB shall have regard to the confidentiality and sensitivity contained within the Services Environment and shall ensure that measures applicable to the UK health and social care sector are in place to prevent unauthorised access.

39.4 SECURITY AUDIT

39.4.1 PKB shall provide to the Providers any information that the Providers reasonably requires for the purpose of allowing the Providers to have assurance with PKB’s compliance with the provisions of this Clause 39 within a reasonable time from the Provider’s request. PKB shall provide this information in such format as the Providers may reasonably require.

39.5 NON-COMPLIANCE REPORTING

39.5.1 PKB shall monitor, on an ongoing basis, computer and network security configurations.

39.5.2 PKB shall create and issue reports to the Providers on incidents of non-compliance with the Security Policy according to their severity within a reasonable time after such incidents occur.

39.6 SYSTEM ACCESS CONTROL

39.6.1 PKB shall administer the provision of access to the Services Environment (by both the Provider’s Personnel and PKB's Personnel), Data and any other applicable data in accordance with Good Industry Practice.

39.6.2 PKB shall restrict access to the Services Environment to appropriately identified authenticated and authorised personnel and shall keep records of which personnel have access to the Services Environment and the reasons for such personnel being given such access. PKB shall also keep records of which personnel have accessed the Services Environment (including details of login and logout times). 

39.6.3 PKB shall restrict user access to information and data held on external networks.

39.7 CRYPTOGRAPHY MANAGEMENT 

39.7.1 PKB shall ensure that Data is encrypted as appropriate in accordance with Good Industry Practice and the most current version of the Data Security and Protection Toolkit and ISO 27002 - Code of Practice for Information Security Management (with the principles of the Data Security and Protection Toolkit prevailing in case of any conflict).

39.7.2 PKB shall manage all processes and procedures pertaining to the administration of the encryption keys, including secure key storage, periodic changing of keys, destruction of old keys, and registration of keys with the appropriate authorities. 

39.8 ASSET PROTECTION

39.8.1 PKB shall acquire, create, provide, manage and maintain mechanisms to prevent or mitigate destruction, loss, alteration, disclosure or misuse of equipment used within the Services Environment, Data and Providers assets, having regard to Good Industry Practice. This includes annual Penetration testing and the satisfactory completion of remedial actions identified following that testing. 

39.8.2 All Data shall be appropriately backed up and stored in a secure facility which in line with industry practice would be off site.

39.8.3 PKB will ensure adequate business continuity services and disaster recovery services are in place and regularly tested. Evidence of this testing may be required as part of the Provider’s due diligence.

39.8.4 PKB shall ensure that no-one, other than properly authorised Processor manner having regard to their confidentiality including, where appropriate, being securely destroyed or shredded prior to disposal.

39.8.5 PKB will classify the security of documentation and information to limit distribution and to ensure adequate controls are in place to protect more sensitive content.Personnel, has physical access to any servers in scope under this Contract or used to deliver the Services, including any servers located at PKB's facilities without formal documented approval from the Providers. 

39.8.6 In relation to PKB’s facilities, PKB shall, at a minimum, acquire, create, provide, manage and maintain mechanisms to prevent or mitigate destruction, loss, alteration, disclosure or misuse of Data, having regard to Good Industry Practice.

39.8.7 PKB will fully and regularly assess the physical security risk for all premises and ensure reasonable controls are in place to prevent inappropriate access as would be expected for the National Health Service.

39.8.8 Implement National Cyber Security Centre (NCSC) guidelines (e.g. cyber essentials) as agreed with the Controller so that assets are protected. 

39.9 SECURITY AWARENESS

PKB shall ensure that all its Personnel working on the Providers account are screened and security checked to an appropriate standard, trained in the Security Policy and any other requirements of this Contract, undertake annual training and are deemed competent to undertake Processing activities and are individually accountable for their actions. All PKB Personnel shall, as at the commencement of the Services, be deemed to be appropriately screened and trained to a level befitting the UK health and care sector.

39.10 DOCUMENTATION AND RECORD PRESERVATION

39.10.1 PKB shall protect all Data held by its employees, agents or Processors in a physical form by adopting a “clear desk” policy in respect of such Data and disposing of such information securely by treating it as confidential waste.

39.10.2 PKB shall ensure that any documentation or records relating to the Services being disposed of by or on behalf of PKB are treated in an appropriate 

40. SCHEDULE 4: SIGNATORIES 

Party A 

Patients Know Best Ltd

PATIENTS KNOW BEST LIMITED, a company limited by shares and registered in the United Kingdom with company registration number 06517382, whose registered office is at St John's Innovation Centre, Cowley Road, Cambridge CB4 0WS.

Executed by: 

____________________________

Party B 

whose registered office is at 

Executed by: