Page Comparison

Reviewed PIA document for LIN. 

Although the PIA was initially made for LIN and Revalidation, TIS will be available over the internet to trainees. They will need to accept Privacy notices, terms and conditions of use on first time login.

The expectation for TIS (formerly to be called LIN) is to have trainees to accept cookie policy which should be similar to the one on HEE domain.

https://www.hee.nhs.uk/about-us/contact-us/privacy-cookies

(c.f. PIA document)

No. LIN (TIS) will not utilise N3. Patient identifiable data is not to be entered onto the system. NHS Digital has validated this approach and LIN (TIS) will follow https:// commercial practice and the GSDM.

Mainly trainees, Traininf Programme Directors (TPD), HEE Staff, Education Supervisors, Devolved Administrators. 

(Page 14 of the PIA)

Non-NHS organisations that will have access to TIS (LIN)data include: 

Education Institutions - Higher Education Institutions and Further Education Institutions;Regulatory and curriculum setting bodies;Independent Health Sector Organisations that work with HEE for NHS training. These organisations include, for example, primary care service providers, UKAS accredited independent medical laboratories and independent sector treatmentcentres; NHS Business Services authority (covering NHS Protect) NHS Litigation Authority Law enforcement organisations such as UK Police and UK security organisations.

Handling of sentitive data within TIS: The PIA pre-dates TIS. There is now availability of more sensitive data on TIS whilst new components are being developed on TIS, e.g. Enthicity, Equality and Diversity Monitoring information.  

Should this be part of an overall process that involves project board as stated in LIN PIA to ensure all partties are in agreement of the data available on TIS?

Trainees will be public facing I believe whille the rest of the users over N3. Trainees will need to see and agree a Privacy Policy on first time logging in in order to participate in the HEE's training programmes.  (Splash screen).

Privacy policy to have information regarding consent for the processing of personal identifiable or sensitive data. 

Is HEE's Privacy Notice sufficient for TIS?

https://www.hee.nhs.uk/about-us/contact-us/privacy-cookies

Implicitly - Privacy Notice on HEE's website including use of any Apps associated with LIN (TIS).

Explicitly? - Re-written for TIS with slight amendments. 

There may not be registration on TIS by trainnes but they will be invited by email to join. 

Implicitly - Privacy Notice on HEE's website including use of any Apps associated with LIN (TIS).

Explicitly? - A re-written Privacy Notice for TIS with slight amendments which the trainnes have to accept on first login.

Is a cookie policy required?

Temporary session cookie only to enable section of the site to be used and navigated or persistant cookies?

Or persistent cookie until the time set expires or the user deletes the cookie?

Required for trainees to view and accept cookies. 

Whether temporary or persistant is a technica decision. 

This is more about the data collected and how they are processed by TIS.

Documents available on:

SOPS - confluence (Ray ro send)

Governance compliance - confluence (Ray to send)

The expectation for TIS (formerly to be called LIN) is to have trainees to accept cookie policy which should be similar to the one on HEE domain.

https://www.hee.nhs.uk/about-us/contact-us/privacy-cookies

Assumption is trainees will need to accept cookie policy on first visit to the TIS landing page. 

Consideration for GDPR (May 2018) and therefore seek guidance on Information Governance (Andrew Todd)?

HEE Records management policy - 5.6 Retention and disposal – that there are consistent and documented retention and disposal procedures to include provision for permanent preservation of archival records

Systems Risk Assessment

Yes - removal of data from the system requests

Retention of medical records requirement

Arrange Call on Wednesday/Thurs - meeting with Andrew Todd

Retention of data within TIS. - DPA Principle 5

Recommentation (approved on 31 March by TIS Project Board):

HEE should come to a corporate view on the above risk, consulting within DEQ, DPD and with corporate colleagues responsible for information governance. Following this and before taking any action to remove and delete data it would be best to consult more widely as appropriate across all of the UK national NHS training and education authorities and learner stakeholders with a view to alignment andagreement on a consistent policy to underpin equal treatment of data subjects.

HEE Records management policy - 5.6 Retention and disposal – there are consistent and documented retention and disposal procedures to include provision for permanent preservation of archival records

Is this still outstanding?

Should we consider Intrepid and Oriel as a precedence?

Have the data flows to the following been risk assessed and mitigated?

• Intrepid
• ESR
• GMC/GDC

The GMC, a major Non-NHS recipient of LIN data, has its own compliant data retention regime. All organisations using the system will be required to provide an annual return for the IAO to this effect.

The governance around ESR

integration is well documented and rigorous. It is possible that integration with other systems such as e-Portfolios will be considered in due course and, if so, this will be subject to a fresh PIA.

Does Keycloak allows configuration of cookies? If so, can they be aligned with HEE's cookies policy?

https://www.hee.nhs.uk/about-us/contact-us/privacy-cookies

What are the retention periods (what is the minimum timescale) for TIS data?

Note: This is distinct from Legacy data that will be availble in the mirror up to a point. We are here referring to data that will be held on TIS.

Do we need to explicitly make mention on this on TIS Private notice?

From PIA:

The LIN project board has yet to consider the extent to which the system might remain available to learners after the end of their training programme.

The data retention periods for TIS will be stated in due course. Learners may want access to their data over the duration of their training programmes and perhaps for longer. Authorised users may require historical access to their data. HEE will propose the archive rationale and this may involve selected data being extracted and stored on a secure server. It is also planned to share the data, under clear agreements, with organisations involved in training, education and development. HEE will be clear about data retention arrangements for day-to-day operations and longer-term research and evaluation purposes. Where it is planned to use data for research and evaluation purposes outside the basic data retention period the HEE Board will be requested to approve it on a case-by-case basis to ensure compliance with the Data Protection Act.