Information to be shared. 3.1 The information exchanged routinely between the partner organisations will be at minimum; the data items identified in the specification for the DfE School Census, together with estimated/actual Key Stage school/pupil level attainment and value added results/analysis at appropriate and relevant levels.
3.2 Information sharing carried out under the legal framework contained in the Children & Families Xxx 0000 relating to Special Educational Needs & Disabilities (SEND) and Education Health and Care Plans (EHCP’s).
3.3 Information sharing to support vulnerable groups such as children in need, children in care and children supported by multi agency teams (MAT’s). Also information sharing to support the statutory children’s safeguarding responsibilities of the Council and the academy/school.
3.4 It is expected that workforce data, will also be exchanged at aggregate and person identifiable levels for purposes of Council HR & Payroll services and supporting schools with DfE School Workforce Census if your school subscribes to these Council services.
3.5 Data can be shared with third parties when the academy/school wishes the Council to pass on data on its behalf for specific programs set up under partnership working arrangements as long as fair processing conditions of the Data Protection Xxx 0000 are adhered to, for example: 1 to 1 tuition programs, NHS health programs e.g. vaccination programs Benchmarking analysis exercises on behalf of academies/schools and the Council This may involve sharing additional contextual data about the pupil such as address information, exclusions history, looked after status, SEN status, SEN primary need, leaver status.
3.6 Early Years Foundation Stage Profile, Key Stages 1, 2, 4 and Post 16 pupil level results data and Xxxxxxx Family Trust pupil level estimates will be uploaded and shared (when available) via secure websites of DfE, NAA, Xxxxxx Family Trust and the Council according to agreements in place.
3.7 Aggregated statistical and performance profiles such as value added analyses, school profile, school performance indicators, progress charting and pupil level target/attainment analysis will be supplied to the academy/school via the secure Council website.
3.8 Examples of routine information sharing between partners. Person identifiable data to support services provided by the Council to academies/schools, parents/carers and children e.g. data relating to SEND, pupil exclusions and behavior support. Weekly up...
Information to be shared. 4.1 TU will provide TUSU with the Personal Data of enrolled students as contained in Appendix 1 Section 3. In order for TUSU to fulfil its statutory obligations, Personal Data for students changing enrolment status part way during an academic year will continue to be shared with TUSU until conclusion of the academic year. Such sharing excludes any students who have opted out in accordance with Clause 10 of this Agreement.
Information to be shared. The Parties may share the Information and may use the Information for the purposes specified at clause 2.
Information to be shared. 15.2.1 The HO will share with DfE to meet the objectives in 15.1.1 where a) the HO suspects that an immigration offence has been committed under Section 24 or 24A of the Immigration Act 1971 or Section 35 of Asylum and Immigration (Treatment of Claimants) Act or b) where the child in question is an unaccompanied minor and XX has lost contact with the child giving rise to concerns over their wellbeing. The details supplied will be extracted from the HO Casework Information Database (CID) and will include: Surname Middle Name (if known) Forename Address Post Code Gender (if known) Date of Birth CID PER ID
15.2.2 The DfE will match this information against records and then in response provide the HO with information relating to those individuals that matched DfE records.
15.2.3 The data will be shared on a monthly basis. The number of records to be shared for the checking process will be in the region of 1500 in any given month. In exceptional circumstances (for example where there are concerns over the wellbeing of children) the HO may include up to 50 records that will be identified in this monthly feed to be checked manually with DfE. Any significant fluctuations in volumes will be notified to DfE in advance and with prior agreement with DfE.
15.2.4 Data may also be shared on an ad-hoc basis as set out in section 15.4.4 below.
15.2.5 DfE will extract the information required for this exchange from records held on the Census collections held by DfE.
15.2.6 DfE will return the following pupil/ child and school(s) information (the “DfE Return Information”): Surname Forename Middle name (If held) Former surname (If held) Preferred surname Multiple or sole addresses (for the last 3 to 5 years where held)l House number/ name, street name and town/ city Post code Relevant census collection date for this record Multiple or sole school information to include for all School number School name School post code Earliest known pupil date at school Latest known pupil date at school Adopted From Care Flag On review, HO and DfE will assess the DfE Return Information and consider any reasonable adjustments to this information.
Information to be shared. 3.1 UC will provide UCSU with the following registered student data, or subset of this data, from its student information database: • Student ID numbers • First names • Last name • Date of birth • Gender • UC email address • Network account (facilitates access to UCSU Website) • Nationality • Programme of study • Mode of study • Location of study • Year of study • Student type i.e. undergraduate, post-graduate • Mode of attendance • Personal email address for graduating students (for SUGraduation event purposes only) • Student card number (currently MiFare)
3.2 UC will provide UCSU with the following information for undergraduate applicants who are “Unconditional Firm” (UF): • First names • Last name • Personal email address • Home address • Date of Birth
3.3 Other personal data will be shared as follows: • CCTV footage or bodycam images but only where this relates to safety, security or detection and prevention of crime. • Student Support Care Plans may be shared but only where the explicit consent of student has been obtained. • Incident logs maintained by UC and UCSU contracted Security staff. • Between Student Support and Wellbeing, Conference & Accommodation, Support and Information Zone and UCSU in connection with 2.9 above.
3.4 Special categories of personal data may be transferred between UCSU and UC but only as specifically referenced in 2.9and 3.3 above.
3.5 UC will provide data and will excludethe following students: • Partnership students studying wholly or mainly (that is for more than half their time) at a partner institution where they are not our contracted student numbers. • Research students at the writing up stage. • Students studying outside the UK. • Non-UK based distance learning students. • “opt-outs” (see section 7 below)
Information to be shared. The Agreement concerns the following personal and/or sensitive information which needs to be shared for the purposes outlined in section 2. • “Personal Data” which identifies the alleged victim(s) or alleged perpetrator(s) of abuse or neglect e.g. name, date of birth, address; • “Sensitive Data” about the alleged victim(s) or alleged perpetrator(s) of abuse or neglect e.g. gender, religion, ethnicity; • Reasons for concerns and details of the alleged concerns e.g. type of abuse, location of abuse, levels of risk or urgency; • Information about the physical and or mental health of the alleged victim(s) or alleged perpetrator(s) e.g. mental capacity, communication needs; • Reports of any medical or social care assessments or examinations undertaken as part of the safeguarding adults procedures e.g. eligibility for community care, psychiatric assessment; • Personal Data which identifies professionals involved with the alleged victim(s) or alleged perpetrator(s); • Personal Data which identifies other people who may be at risk e.g. via employment, family, service; • Historical information held in records about the alleged victim(s) or alleged perpetrator(s) that may be relevant to the current safeguarding concern or case review e.g. previous safeguarding adults alert; • Name and contact details of alerter (unless they have stated they wish to remain anonymous and this anonymity would not have a detrimental impact upon the safeguarding adults process); • Name of employer or organisation if the concern relates to a paid worker or volunteer of a service provider; • The agreement also concerns aggregated data (e.g. statistics) which may be shared. In these situations, anonymised information should be used. Controller, Processor, Data Subject, Personal Data, Special Categories of Personal Data and Processing shall have the meanings given to them in the General Data Protection Regulation (GDPR) or the Data Protection Xxx 0000 (together “the Data Protection Legislation”).
Information to be shared. 7.1. The Transform Data View will provide a snapshot of the vulnerability flags, risks, assessments, involvements and attendance data, including contact details of key professionals.
7.2. Information will only be shown where there has been a historic involvement within the last two years.
7.3. Fields will indicate either 7.3.1. no information on database 7.3.2. historic
Information to be shared. For the purposes of this project, each party providing data will be considered singularly the Data Controller. Each Data Controller will specify the relevant and most appropriate data items that are required to support the delivery care. Specific sensitive codes will be either shared or not shared depending on the nature of the arrangement included in Appendix A. The inclusion of these codes will be approved by the ELHCP IG Committee and the Data Controllers on a case by case basis with decisions informed by lead clinicians from all of the services that it will affect (ie the affected sending organisation(s) and the receiving organisation(s)) The amount of data being shared and with whom should reflect the needs of residents and of the clinicians and other staff delivering their services. The amount data that is shared will also reflect the maturity of the local systems in terms of how configurable they are to share information. The Data Controllers will need to work within the confines of the abilities of these systems and adapt Appendix A as and when the systems change or become more mature in their approach to data sharing. The Data Controllers must ensure that their approach around sharing of data should be proportionate and manageable to ensure that complexities aren’t introduced that make the process unworkable or difficult for residents to understand. The data sets will be specified in Appendix A.
Information to be shared. 5.2.1 The data shared is as follows (table of fields) Email (token) Legal Surname Legal Forename Preferred Surname Preferred Forename DOB SEN Status Ethnicity (token) EAL Language code Current NC Year Gender FSM Eligible In LEA Care Gifted and Talented Entry Date Pupil Premium ServicePremium FSM Ever 6 Medical Needs SEN Needs (token) Guest students (token) Medical (token) Staff ID Staff email (the one set as ‘primary’) Title Legal forename Preferred forename Legal surname Preferred surname Staff role (token but on by default) Staff salary (token) Group ID (e.g. 32) Group name (e.g. 10A/Dr1) Group type (e.g. Class) Group description (e.g. 10A/Dr1) Subject ID (e.g. 32423) Primary staff ID (e.g. 75432) Group membership Attendance codes (Acode, Desc, Pdesc, Scode, Sdesc) Student ID Start Date Marks Result sets (token) Aspects (chosen by the school) Description StartDate AcadYear TotalCycleDays CycleDaysPerWeek PeriodsPerCycle TeachingPeriodsPerCycle YearStartDate YearEndDate StructureId PeriodNumber StartTime EndTime PeriodDescription DayName DayOrder OccurringDate TimeTableDayName TimeTableDateID LessonID PeriodID Room StaffID GroupID
5.2.2 The primary method by which you will share Protected Data with us is via your selected third party data extractor (Data Extractor). We will agree with you which Data Extractor you will use for the provision of the data export and import services. Your Data Extractor may change from time to time by agreement between us. Agreement may be made by email exchange between us. We will provide a list of the third party data extractors that we currently partner with at your request.
5.2.3 The Protected Data is collected by the Data Extractor from your MIS and securely delivered into the System.
5.2.4 You acknowledge that you shall, at your own cost, enter into a contract with the relevant Data Extractor for the provision of the data export and import services. Under no circumstances shall we be liable to you for any loss, damage, claims, demands, actions, costs, charges, expenses and liabilities of whatsoever nature arising out of or in connection with the provision of the data export services by the Data Extractor.
5.2.5 A manual upload can be used if you are unable or unwilling to use one of our listed data extractors. If manual upload is used for Protected Data you should provide the Protected Data to us by secure means (for example, by using our secure file transfer setup).
Information to be shared. Xxxxx County Public Schools will provide the Data Recipient with “view only” access to the databases. The specific student information to be shared pursuant to this Agreement is the following table below. Personally Identifiable Student Data Universe of Records Students for whom City Year has submitted records to the District of participation in the Agreement program Time Period July 1, 2020 – June 30, 2021 Data Fields “X” if Included DCPS_Student_ID X Ethnicity_Hisp_Or_Lat X Student_Full_Name X Grade_Level X Birthdate X Race_Desc X Gender X Student_Email_Address X Home_Room_Number X Homeroom_Teacher X ELL_Ind X ELL_Entry_Date X Ninth_Grade_Entry_Year X Classification_Date X Date_Entered_US_School X ELL_Exit_Date X ELP X Home_Lang_Survey_Date X Home_Lang_Survey_1-3 X Primary_Home_Lang_Code X Native_Language X Most_Freq_Spkn_Lang_Code X IEP_EP_Service_Plan_Date X IEP_Expiration_Date X Current_School_Matrix X Alt_Assessment_Administered X School_Name_Number X Title_I_Status X SAC_Reason_Code X SAC_Reason_Desc X Zoned_School_Number X Magnet_Program X Test_code X Test_name X Test_date X Test_component_desc X Test_score X Test_component_code X Subject_code X Score_type_code X Score_type_desc X Suspension_Code X Spension_Countus X Suspension_Category X Action_Duration_Total X Focus_Student_ID X Referral_Count X Present_count X Absent_PCT X Present_PCT X Period_Code X Attendance_Code X Attendance_Desc X Tardy_Count X
