Third Principle Sample Clauses

Third Principle. Data Protection 20 4.3.1 How the agreement complies with the third data principle 20

Third Principle. Personal data shall be adequate, relevant and not excessive in relation to the purpose or purposes for which they are processed. 5.4.1 Due to the complexity of the MASH it is difficult to provide a prescriptive list of all data fields to be shared but examples include social care information, GP and health records, school and educational information, police intelligence, housing information. 5.4.2 Once a referral has been received by the MASH all partners will be under a duty to scrutinise their information systems and share any relevant information as necessary to achieve the aims of this agreement. 5.4.3 Once a referral has been received by the MASH, decisions on use and any further dissemination shall be considered and decided on a case by case basis. 5.4.4 Only relevant and proportionate information will be shared where a partner organisation has a ‘need-to-know’ basis.

Third Principle. Personal data shall be adequate, relevant and not excessive in relation to the purpose or purposes for which they are processed 5.4.1 Due to the complexity of the MASH, providing a comprehensive, prescriptive list of data fields to be shared is impractical. Once a referral has been received by the MASH, decisions on which information systems will be scrutinised will be decided on a case by case basis. Only relevant and proportionate information will be shared where an organisation has a ‘need‐to‐know’ justification to see the information. Appendix 3 gives an overview of information that is shared.

Third Principle. Personal data shall be adequate, relevant and not excessive in relation to the purpose or purposes for which they are processed. Due to the complexity of the information sharing through this protocol, providing a prescriptive list of data to be shared is difficult. Therefore partners will agree to share proportionate information that will be the minimum necessary to enable the panel to achieve its objectives under the Operating Protocol. It will be for the controllers of the relevant information to assess its worth in meeting this principal and determining if disclosure is therefore necessary.

Third Principle. Personal data shall be adequate, relevant and not excessive in relation to the purpose or purposes for which they are processed. The information to be shared under this agreement shall be no more than is necessary to be shared in order to assess and manage risk associated with MAPPA offenders.

Third Principle. Data Protection Personal data shall be adequate, relevant and not excessive in relation to the purpose or purposes for which they are processed. RELEVANT LEGISLATION Schedule 1, Part 2 Data Protection Act 2018 (The third principle): ▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇▇▇▇▇.▇▇▇.▇▇/ukpga/2018/12/section/37/enacted 6.4.1 How the agreement complies with the third data principle The data to be shared with the education establishment will be the minimum necessary for both parties to conduct an accurate risk assessment and decide upon the measures required to manage an individual or provide assistance to them.

Third Principle. Personal data shall be adequate, relevant and not excessive in relation to the purpose or purposes for which they are processed. Due to the complexity of the MASH, providing a prescriptive list of data fields to be shared is difficult. Any information that is shared into and within the MASH Hub will be decided on a case- by-case basis and must be relevant to the aims of this agreement. Examples of data that may be shared include; • Name of subject (child) and other family members, their carers and other persons whose presence and/or relationship with the subject child or children, is relevant to identifying and assessing the risks to that child. • Age/date of birth of subject and other family members, carers, other persons detailed. • Ethnic origin of family members. • Relevant Police information and intelligence • School and educational information (to include family members where appropriate and relevant) • GP and health records (to include family members where appropriate and relevant) • Relevant ASB data • Relevant data from London Ambulance Service or London Fire Brigade • Housing and other partnership data relevant to the child and family who may affect the welfare of that child. Not all of the above information will be shared in every case; only relevant information will be shared on a case-by-case basis where an organisation has a ‘need-to-know’ about the information.

Third Principle. Data Protection Personal data shall be adequate, relevant and not excessive in relation to the purpose or purposes for which they are processed. 4.3.1 How the agreement complies with the third data principle The information to be shared with the school/college will be the minimum necessary for the college to conduct an accurate risk assessment and decide upon the measures required to manage an individual or provide assistance to them. In pursuance of the objectives, the information that may be disclosed in relation to the student(s), to assist with matching persons and incidents and ensuring they are the correct individual could include: Name /alias Date of birth Address Gender Ethnicity Physical description/ image Information relating to criminal offences, anti-social behaviour or other factors that could prevent the child from obtaining the statutory 5 outcomes of the Children ▇▇▇ ▇▇▇▇ which may be shared include: Nature of offence Nature of information, for example behaviour Any known risk The Police systems that may be interrogated for information are: The Police National Computer (PNC) The Criminal Intelligence System (CRIMINT) Crime Reporting Information System (▇▇▇▇) Computer Aided Despatch (CAD) - data relating to incidents reported to police concerning crime and events within the MPS Merlin (system the MPS uses to record when children come to police attention) Custody Records (NSPIS) Custody imaging system Youth Offending Team records