llowing true or 1 for the true state, and false or 0 for the false state. However, we recognise that users of MISs may be presented with a number of ways of recording this type of 25 information, such as check boxes or a drop down list. In this case the export functionality of any system will need to convert these fields to the XML standard format. 26 2. Data module 1: child identifiers This module contains details about the child’s identity and it must be completed for every child record. If a child is adopted from care during the year and remains in need, then the child should have two separate unlinked records entered for them: one for pre-adoption and one for post-adoption with appropriate new child identifiers. Items 2.1 to 2.7 are used for identifying and matching purposes. 2.1 ‘LA child ID’ This must be a unique id for each child (no longer than 10 characters), and it should be retained from year to year. The ‘LA child ID’ can only contain alphabetic or numeric characters. It must be the same id that is used for other purposes, for example in the children looked after data collection return. Local authorities are free to choose their own child ids according to the above format. If you are planning to change the ‘LA child ID’, either for a single child or for a whole group of children, it will prevent DfE from analysing data across different children in need census years and between the children in need and the children looked after collections. For this reason, any proposal to change ids should be discussed with DfE at an early stage and in advance of any changes. You should notify DfE of any changes via a data collections service request form. Unborn children should be allocated their own ‘LA child ID’. 2.2 Unique pupil number (UPN) A unique pupil number (UPN) i