<?xml version="1.0" encoding="UTF-8"?>
<codeBook version="1.2.2" ID="CIV_2009-2014_INDEPTH-THDSS_v01_M" xml-lang="en" xmlns="http://www.icpsr.umich.edu/DDI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.icpsr.umich.edu/DDI http://www.icpsr.umich.edu/DDI/Version1-2-2.xsd">
<docDscr>
  <citation>
    <titlStmt>
      <IDNo>DDI_CIV_2009-2014_INDEPTH-THDSS_v01_M</IDNo>
    </titlStmt>
    <prodStmt>
      <producer abbr="isTT" affiliation="INDEPTH Network" role="Technical Support">iSHARE2 Technical Team</producer>
      <producer abbr="" affiliation="THDSS" role="DDI Author">Martial Laubet</producer>
      <prodDate date="2017-05-17">2017-05-17</prodDate>
      <software version="v5">NADA</software>
    </prodStmt>
    <verStmt>
      <version>- v01 (May 2017)
The DDI was produced by INDEPTH Network. It was downloaded on October 18, 2017 from http://www.indepth-ishare.org/index.php/catalog/118/ by the World Bank Microdata Library documentation team.

- v02 (October 2017)
Modifications in the study ID and DDI ID were done by the World Bank Microdata Library documentation team to match the standard used by the library and the IHSN Survey Catalog. Some metadata fields were also edited.</version>
    </verStmt>
  </citation>
</docDscr>
<stdyDscr>
  <citation>
    <titlStmt>
      <titl>Taabo HDSS INDEPTH Core Dataset 2009 - 2014 (Release 2017)</titl>
      <subTitl/>
      <altTitl>HDSS 2009-11</altTitl>
      <parTitl>Historique de la base de données de 2009-2014</parTitl>
      <IDNo>CIV_2009-2014_INDEPTH-THDSS_v01_M</IDNo>
    </titlStmt>
    <rspStmt>
      <AuthEnty affiliation="CSRS, unit&#xE9; de formation et de recherches Bioscience Universit&#xE9; Felix Houphouet Boigny">N'Goran Eliezer</AuthEnty>
      <othId role="Data Manager" affiliation="CSRS" email="">
        <p>BAIKORO NAHOUA</p>
      </othId>
    </rspStmt>
    <prodStmt>
      <copyright>This dataset documentation is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License. The dataset is shared in terms of the data-use agreement accepted at the time of data download.</copyright>
      <software version="5.0" date="2021-03-30">NADA</software>
      <fundAg abbr="CSRS" role="">Centre Suisse de Recherches Scientifiques</fundAg>
      <fundAg abbr="" role="">FAIRMED</fundAg>
      <fundAg abbr="" role="">Swiss TPH</fundAg>
      <grantNo/>
    </prodStmt>
    <distStmt>
      <contact affiliation="INDEPTH Network" URI="http://indepth-ishare.org/howtouse" email="help-data@indepth-network.org">iSHARE2 Helpdesk</contact>
      <depDate date=""/>
      <distDate date=""/>
    </distStmt>
    <serStmt>
      <serName>Demographic Surveillance</serName>
      <serInfo>Round 1 to 14 of the annual our demographic surveillance from 2009 to 2014</serInfo>
    </serStmt>
    <verStmt>
      <version date="2017-05-16">CMV2014.V1</version>
      <verResp/>
      <notes>Developed during iShare 2 workshop</notes>
    </verStmt>
    <biblCit format=""/>
    <holdings location="" callno="" URI="10.7796/INDEPTH.CI011.CMD2014.v1"/>
    <notes/>
  </citation>
  <stdyInfo>
    <studyBudget/>
    <subject>
      <keyword vocab="" vocabURI="">Population</keyword>
      <keyword vocab="" vocabURI="">Migration</keyword>
      <keyword vocab="" vocabURI="">Mortality</keyword>
      <keyword vocab="" vocabURI="">Fertility</keyword>
      <topcClas vocab="MeSH" vocabURI="http://www.ncbi.nlm.nih.gov/mesh">Demography [N01.224]</topcClas>
      <topcClas vocab="MeSH" vocabURI="http://www.ncbi.nlm.nih.gov/mesh">Emigration and Immigration [N01.224.625.350]</topcClas>
      <topcClas vocab="MeSH" vocabURI="http://www.ncbi.nlm.nih.gov/mesh">Mortality [N01.224.935.698]</topcClas>
      <topcClas vocab="MeSH" vocabURI="http://www.ncbi.nlm.nih.gov/mesh">Birth Rate [N01.224.935.849.500]</topcClas>
    </subject>
    <abstract>The Taabo Health and Demographic Surveillance System (HDSS) is located in south-central Côte d'Ivoire, approximately 150 km north-west of Abidjan. The Taabo HDSS started surveillance activities in early 2009 and the man-made Lake Taabo is a key eco-epidemiological feature. Since inception, there has been a strong interest in research and integrated control of water-associated diseases such as schistosomiasis and malaria. The Taabo HDSS has generated setting-specific evidence on the impact of targeted interventions against malaria, schistosomiasis and other neglected tropical diseases. The Taabo HDSS consists of a small town, 13 villages and over 100 hamlets. At the end of 2013, a total population of 42 480 inhabitants drawn from 6707 households was under surveillance. Verbal autopsies have been conducted to determine causes of death. Repeated cross-sectional epidemiological surveys on approximately 5-7% of the population and specific, layered-on haematological, parasitological and questionnaire surveys have been conducted. The Taabo HDSS provides a database for surveys, facilitates interdisciplinary research, as well as surveillance, and provides a platform for the evaluation of health interventions.</abstract>
    <sumDscr>
      <timePrd date="2009-01-01" event="start" cycle=""/>
      <timePrd date="2013-12-31" event="end" cycle=""/>
      <collDate date="2009-01-01" event="start" cycle="Release Coverage"/>
      <collDate date="2014-12-31" event="end" cycle="Release Coverage"/>
      <collDate date="2010-10" event="start" cycle="02"/>
      <collDate date="2010-01-17" event="end" cycle="02"/>
      <collDate date="2010-02-23" event="start" cycle="03"/>
      <collDate date="2010-04-23" event="end" cycle="03"/>
      <collDate date="2010-07-05" event="start" cycle="04"/>
      <collDate date="2010-09-05" event="end" cycle="04"/>
      <collDate date="2010-09-17" event="start" cycle="05"/>
      <collDate date="2010-12-17" event="end" cycle="05"/>
      <collDate date="2011-02-25" event="start" cycle="06"/>
      <collDate date="2011-06-01" event="end" cycle="06"/>
      <collDate date="2011-08-05" event="start" cycle="07"/>
      <collDate date="2011-11-05" event="end" cycle="07"/>
      <nation abbr="CIV">Côte d'Ivoire</nation>
      <geogCover>Taabo HDSS located in the center of country, in rural area. It cover approximately 750 km².</geogCover>
      <geogUnit/>
      <anlyUnit>Individual</anlyUnit>
      <universe>All individuals residing in the Taabo HDSS area.</universe>
      <dataKind>Event history data</dataKind>
    </sumDscr>
    <!-- qualityStatement - ddi2.5 - complex type
     
     This structure consists of two parts, standardsCompliance and otherQualityStatements. 
     In standardsCompliance list all specific standards complied with during the execution of this 
     study. Note the standard name and producer and how the study complied with the standard. 
     Enter any additional quality statements in otherQualityStatements.
     
     -->
    <qualityStatement>
      <standardsCompliance>
        <standard>
          <standardName/>
          <producer/>
        </standard>
        <complianceDescription/>
      </standardsCompliance>
      <otherQualityStatement/>
    </qualityStatement>
    <notes>Individuals: Individual ID, Location ID, Individual Sex and Date of Birth
Event Date: Birth, Death, Inmigration, Outmigration
Event Code: Birth, Death, Inmigration, Outmigration
Deliveries: Mother ID</notes>
    <!-- exPostEvaluation ddi2.5
      Use this section to describe evaluation procedures not address in data evaluation processes. 
      These may include issues such as timing of the study, sequencing issues, cost/budget issues, 
      relevance, instituional or legal arrangments etc. of the study. 
      
      The completionDate attribute holds the date the evaluation was completed. 
      The type attribute is an optional type to identify the type of evaluation with or without 
      the use of a controlled vocabulary.
    -->
    <exPostEvaluation completionDate="" type="">
      <evaluationProcess/>
      <outcomes/>
    </exPostEvaluation>
  </stdyInfo>
  <method>
    <dataColl>
      <timeMeth/>
      <dataCollector abbr="" affiliation="CSRS">Taabo HDSS</dataCollector>
      <!-- collectorTraining - DDI2.5
        
        Collector Training

        Describes the training provided to data collectors including internviewer training, process testing, 
        compliance with standards etc. This is repeatable for language and to capture different aspects of the 
        training process. The type attribute allows specification of the type of training being described.
        
        -->
      <collectorTraining type=""/>
      <frequenc>Threer rounds per year</frequenc>
      <sampProc>Not Applicable</sampProc>
      <sampleFrame>
        <sampleFrameName/>
        <custodian/>
        <universe/>
        <frameUnit isPrimary="">
          <unitType numberOfUnits=""/>
        </frameUnit>
        <updateProcedure/>
      </sampleFrame>
      <deviat>None</deviat>
      <collMode>Proxy Respondent [proxy]</collMode>
      <resInstru>The following forms were used to collect the social and demographic data:
- In-Migration Paper
- Out-Migration Paper
- Pregnancy Paper
- Issue And Morbidity Of Pregnancy Paper
- Death Paper
- Entry And Exit Provisional Paper
- New Member Paper
- New Household Paper
- Counting Paper
- Internal Migration Paper
- External Migration Paper
- Remark Paper
- Changing Of Head Household Paper
- Proposition Of Changing Of Head Household Paper
- Autopsy Verbal Paper</resInstru>
      <!-- instrumentDevelopment - DDI2.5             
        Describe any development work on the data collection instrument. Type attribute allows for the optional use of a defined development type with or without use of a controlled vocabulary.
        -->
      <instrumentDevelopment type=""/>
      <collSitu>In average, the duration of the interview was one hour. 

The data collection team included:
- a leader of station
- an administrative and financial assistant
- a data manager
- a manager of all person who collect data (supervisor and data collector)
- one supervisor of data operator
-  three data operators
- four supervisors of data collectors
- twelve data collectors
- two supervisors of event (migration and verbal autopsy)</collSitu>
      <actMin>The supervisor is responsible for the performance of the hearing officer he had under his direction. So it must verify the accuracy of the number of households to investigate by the interviewer during the round of surveillance. Then in agreement with data collector one supervisor defines a work schedule. In this schedule there is the minimum number of household to visit per day, days of recovery completed questionnaires on work days with supervisors migration and verbal autopsies. This planning must necessarily be respected. So during the first week of the round the supervisor will accompany the data collector in households to ensure that it controls the variability of concepts and performs correctly filling out questionnaires. This work strategy is called assisted surveys. Also scheduled day will recover supervisors completed questionnaires, will correct them on the spot, the codify and convey them on the site for HDSS second verification and entry. Also few weeks, that is to say 2-3 weeks, they will conduct investigations against 3 to 5% of households selected randomly by the IT department, depending on the size of households in each enumeration district.</actMin>
      <ConOps/>
      <weight>Not Applicable</weight>
      <cleanOps>The following processing checks are done during the ETL process.

If the first event is legal. Like the first event must be enumeration, birth or inmigration.
If the last event is legal. Like the last event must be end of observation, death or outmigration.
If the transition events are legal.
The list of legal transitions:

    Birth followed by death
    Birth followed by exit
    Birth followed by end of observation
    Birth followed by outmigration

    Death followed by none

    Entry followed by death
    Entry followed by exit
    Entry followed by end of observation
    Entry followed by outmigration
    Enumeration followed by death
    Enumeration followed by exit
    Enumeration followed by outmigration

    Exit followed by entry

    Inmigration followed by Death
    Inmigration followed by exit
    Inmigration followed by end of observation
    Inmigration followed by outmigration

    End of observation followed by none

    Outmigration followed by none
    Outmigration followed by enumeration
    Outmigration followed by inmigration

    The list of illegal transitions:

    Birth followed by none
    Birth followed by birth
    Birth followed by entry
    Birth followed by enumeration
    Birth followed by   inmigration

    Death followed by birth
    Death followed by death
    Death followed by entry
    Death followed by enumeration
    Death followed by exit
    Death followed by inmigration
    Death followed by outmigration
    Death followed by end of observation

    Entry followed by none
    Entry followed by birth
    Entry followed by entry
    Entry followed by enumeration
    Entry followed by inmigration

    Enumeration followed by none
    Enumeration followed by birth
    Enumeration followed by entry
    Enumeration followed by enumeration
    Enumeration followed by inmigration

    Exit followed by birth
    Exit followed by death
    Exit followed by exit
    Exit followed by end of observation
    Exit followed by outmigration

    Inmigration followed by none
    Inmigration followed by birth
    Inmigration followed by entry
    Inmigration followed by enumeration
    Inmigration followed by inmigration

    End of observation followed by birth
    End of observation followed by death
    End of observation followed by entry
    End of observation followed by enumeration
    End of observation followed by exit
    End of observation followed by inmigration
    End of observation followed by end of observation
    End of observation followed by outmigration

    Outmigration followed by birth
    Outmigration followed by death
    Outmigration followed by exit
    Outmigration followed by end of observation
    Outmigration followed by outmigration

    List of edited events:

    Exit followed by none
    Exit followed by enumeration
    Exit followed by inmigration

    Outmigration followed by entry</cleanOps>
    </dataColl>
    <notes/>
    <anlyInfo>
      <respRate>2009 100%
2010 100%
2011 100%
2012 100%
2013 100%
2014 100%
2015 100%</respRate>
      <EstSmpErr>Not Applicable</EstSmpErr>
      <dataAppr>CentreIdMetricTableQMetricIllegalLegalTotalMetricRunDate
CI011MicroDataCleanedStarts838132017-05-16 07:59
CI011MicroDataCleanedTransitions 31751641751670.2017-05-16 07:59
CI011MicroDataCleanedEnds838132017-05-16 07:59
CI011MicroDataCleanedSexValues1751672017-05-16 07:59
CI011MicroDataCleanedDoBValues1751672017-05-16 07:59</dataAppr>
    </anlyInfo>
    <stdyClas/>
    <dataProcessing type=""/>
    <codingInstructions relatedProcesses="" type="">
      <txt/>
      <command formalLanguage=""/>
    </codingInstructions>
  </method>
  <dataAccs>
    <setAvail>
      <accsPlac URI="http://www.indepth-ishare.org/index.php/catalog/35">INDEPTH Data Repository</accsPlac>
      <origArch>Taabo (CI011)</origArch>
      <avlStatus/>
      <collSize/>
      <complete/>
      <fileQnty/>
      <notes/>
    </setAvail>
    <useStmt>
      <confDec required="yes" formNo="" URI="">This data is anonymised and no confidentiality agreement in addition to the general data use agreement is required.</confDec>
      <restrctn/>
      <contact affiliation="INDEPTH" URI="http://indepth-ishare.org" email="help-data@indepth-network.com">iSHARE2</contact>
      <citReq>Any use of this dataset must cite the digital object identifier (doi) associated with this dataset using the following form:

"Taabo HDSS INDEPTH Core Dataset 2009-2014 (Release 2017). Provider by the INDEPTH Network Data Repository  www.indepth-network.org &lt;http://www.indepth-network.org&gt;. doi:10.7796/INDEPTH.CI011.CMD2014.v1"</citReq>
      <deposReq/>
      <conditions>This data is made available for licensed access under the following conditions: 

1. Data and other material provided by INDEPTH will not be redistributed or sold to other individuals, institutions or organisations without INDEPTH's written agreement. 

2. In the case of multi-centre datasets, data originating from a single contributing member centre of the INDEPTH Network may not be analysed or reported on in isolation without the express permission of the member centre concerned.  

3. No attempt will be made to re-identify respondents, and there will be no use of the identity of any person or establishment discovered inadvertently. Any such discovery will be reported immediately to INDEPTH. 

4. No attempt will be made to produce links between datasets provided by INDEPTH or between INDEPTH data and other datasets that could identify individuals. 

5. Any books, articles, conference papers, theses, dissertations, reports or other publications employing data obtained from INDEPTH will cite the source, in line with the citation requirement provided with the dataset. 

6. An electronic copy of all publications based on the requested data will be sent to INDEPTH. 

7. The original collector of the data, INDEPTH, and the relevant funding agencies bear no responsibility for the data's use or interpretation or inferences based upon it.</conditions>
      <disclaimer>The user of the data acknowledges that the original collector of the data, INDEPTH, and the relevant funding agencies bear no responsibility for the data use or interpretation or inferences based upon it.</disclaimer>
    </useStmt>
    <notes/>
  </dataAccs>
  <notes/>
</stdyDscr>
<fileDscr ID="F1">
  <fileTxt>
    <fileName>CI011.CMD2014.V1</fileName>
    <fileCont>This file contains event history data for Taabo HDSS</fileCont>
    <dimensns>
      <caseQnty>0</caseQnty>
      <varQnty>14</varQnty>
    </dimensns>
    <dataChck></dataChck>
    <dataMsng></dataMsng>
    <verStmt>
      <version></version>
    </verStmt>
  </fileTxt>
  <notes></notes>
</fileDscr>
<dataDscr>
<var ID="V1" name="RecNr" files="F1" intrvl="contin">
  <location StartPos="1" EndPos="6" width="6"/>
  <labl>RecNr</labl>
  <imputation>RecNr</imputation>
  <security>RecNr</security>
  <embargo>RecNr</embargo>
  <respUnit>RecNr</respUnit>
  <sumStat type="vald"/>
  <sumStat type="invd"/>
  <txt>A sequential number uniquely identifying each record in the data file</txt>
</var>
<var ID="V2" name="CountryId" files="F1" intrvl="discrete">
  <location StartPos="7" EndPos="9" width="3"/>
  <labl>CountryId</labl>
  <imputation>CountryId</imputation>
  <security>CountryId</security>
  <embargo>CountryId</embargo>
  <respUnit>CountryId</respUnit>
  <sumStat type="vald"/>
  <sumStat type="invd"/>
  <txt>ISO 3166-1 numeric code of the country where the surveillance site is situated</txt>
</var>
<var ID="V3" name="CentreId" files="F1" intrvl="discrete">
  <location StartPos="10" EndPos="14" width="5"/>
  <labl>CentreId</labl>
  <imputation>CentreId</imputation>
  <security>CentreId</security>
  <embargo>CentreId</embargo>
  <respUnit>CentreId</respUnit>
  <sumStat type="vald"/>
  <sumStat type="invd"/>
  <txt>An identifier issued by INDEPTH to each member centre of the format CCNNS, Where CCNNS is the INDEPTH Member site code, constructed as follows:
- CC the ISO 3166-1 alpha-2 code of the country where the site is situated
- NN is a sequential number uniquely identifying an INDEPTH member centre within the country. Starting with 01 to 99, for a maximum of 99 centres per country
-S is a sequential character uniquely identifying the geographical surveillance site. Starting with 1 to 9, thereafter A to Z, for a maximum of 35 sites per centre.</txt>
</var>
<var ID="V4" name="IndividualId" files="F1" intrvl="contin">
  <location StartPos="15" EndPos="19" width="5"/>
  <labl>IndividualId</labl>
  <imputation>IndividualId</imputation>
  <security>IndividualId</security>
  <embargo>IndividualId</embargo>
  <respUnit>IndividualId</respUnit>
  <sumStat type="vald"/>
  <sumStat type="invd"/>
  <txt>A number uniquely identifying all the records belonging to a specific individual in the data file. This number is not the same as the identifier used by a contributing centre to be identify the individual</txt>
</var>
<var ID="V5" name="Sex" files="F1" intrvl="discrete">
  <location StartPos="20" EndPos="20" width="1"/>
  <labl>Sex</labl>
  <imputation>Sex</imputation>
  <security>Sex</security>
  <embargo>Sex</embargo>
  <respUnit>Sex</respUnit>
  <sumStat type="vald"/>
  <sumStat type="invd"/>
  <catgry>
    <labl>UNKNOWN</labl>
    <catStat type="vald"/>
  </catgry>
  <catgry>
    <catValu>1</catValu>
    <labl>Male</labl>
    <catStat type="invd"/>
  </catgry>
  <catgry>
    <catValu>2</catValu>
    <labl>Female</labl>
  </catgry>
  <txt>Sex of the individual
- 0 - Unknown
- 1 - Male
- 2 - Female</txt>
</var>
<var ID="V6" name="DoB" files="F1" intrvl="discrete">
  <location StartPos="21" EndPos="30" width="10"/>
  <labl>DoB</labl>
  <imputation>DoB</imputation>
  <security>DoB</security>
  <embargo>DoB</embargo>
  <respUnit>DoB</respUnit>
  <sumStat type="vald"/>
  <txt>The date of birth of the individual Format YYYY-MM-DD</txt>
</var>
<var ID="V7" name="EventCount" files="F1" intrvl="discrete">
  <location StartPos="31" EndPos="31" width="1"/>
  <labl>EventCount</labl>
  <imputation>EventCount</imputation>
  <security>EventCount</security>
  <embargo>EventCount</embargo>
  <respUnit>EventCount</respUnit>
  <sumStat type="vald"/>
  <sumStat type="invd"/>
  <txt>The total number of events associated with this individual in this data set</txt>
</var>
<var ID="V8" name="EventNr" files="F1" intrvl="discrete">
  <location StartPos="32" EndPos="32" width="1"/>
  <labl>EventNr</labl>
  <imputation>EventNr</imputation>
  <security>EventNr</security>
  <embargo>EventNr</embargo>
  <respUnit>EventNr</respUnit>
  <sumStat type="vald"/>
  <sumStat type="invd"/>
  <txt>A number increasing from 1 to EventCount for each event record in order of event occured</txt>
</var>
<var ID="V9" name="EventCode" files="F1" intrvl="discrete">
  <location StartPos="33" EndPos="35" width="3"/>
  <labl>EventCode</labl>
  <imputation>EventCode</imputation>
  <security>EventCode</security>
  <embargo>EventCode</embargo>
  <respUnit>EventCode</respUnit>
  <sumStat type="vald"/>
  <sumStat type="invd"/>
  <catgry>
    <catValu>BTH</catValu>
    <labl>Birth</labl>
    <catStat type="vald"/>
  </catgry>
  <catgry>
    <catValu>DLV</catValu>
    <labl>Delivery</labl>
    <catStat type="invd"/>
  </catgry>
  <catgry>
    <catValu>DTH</catValu>
    <labl>Death</labl>
  </catgry>
  <catgry>
    <catValu>ENT</catValu>
    <labl>Location Entry</labl>
  </catgry>
  <catgry>
    <catValu>ENU</catValu>
    <labl>Enumeration</labl>
  </catgry>
  <catgry>
    <catValu>EXT</catValu>
    <labl>Location Exit</labl>
  </catgry>
  <catgry>
    <catValu>IMG</catValu>
    <labl>In-Migration</labl>
  </catgry>
  <catgry>
    <catValu>OBE</catValu>
    <labl>Observation ended</labl>
  </catgry>
  <catgry>
    <catValu>OBL</catValu>
    <labl>Last Observation</labl>
  </catgry>
  <catgry>
    <catValu>OBS</catValu>
    <labl>Observation</labl>
  </catgry>
  <catgry>
    <catValu>OMG</catValu>
    <labl>Out-Migration</labl>
  </catgry>
  <txt>A code which identifies the  type of event that has occurred</txt>
</var>
<var ID="V10" name="EventDate" files="F1" intrvl="discrete">
  <location StartPos="36" EndPos="45" width="10"/>
  <labl>EventDate</labl>
  <imputation>EventDate</imputation>
  <security>EventDate</security>
  <embargo>EventDate</embargo>
  <respUnit>EventDate</respUnit>
  <sumStat type="vald"/>
  <txt>The date on which the event occured Format: YYYY-MM-DD</txt>
</var>
<var ID="V11" name="ObservationDate" files="F1" intrvl="discrete">
  <location StartPos="46" EndPos="55" width="10"/>
  <labl>ObservationDate</labl>
  <imputation>ObservationDate</imputation>
  <security>ObservationDate</security>
  <embargo>ObservationDate</embargo>
  <respUnit>ObservationDate</respUnit>
  <sumStat type="vald"/>
  <txt>Date on which the event was observed (recorded), also known as surveillance visit date Format YYYY-MM-DD</txt>
</var>
<var ID="V12" name="LocationId" files="F1" intrvl="contin">
  <location StartPos="56" EndPos="59" width="4"/>
  <labl>LocationId</labl>
  <imputation>LocationId</imputation>
  <security>LocationId</security>
  <embargo>LocationId</embargo>
  <respUnit>LocationId</respUnit>
  <sumStat type="vald"/>
  <sumStat type="invd"/>
  <txt>Unique identifier associated with a residence unit within the site and is the location where the individual was or became resident, when the event occurred. this identifier is not the same as the identifier used internally by the contributing centre</txt>
</var>
<var ID="V13" name="MotherId" files="F1" intrvl="contin">
  <location StartPos="60" EndPos="64" width="5"/>
  <labl>MotherId</labl>
  <imputation>MotherId</imputation>
  <security>MotherId</security>
  <embargo>MotherId</embargo>
  <respUnit>MotherId</respUnit>
  <sumStat type="vald"/>
  <sumStat type="invd"/>
  <txt>The individual of the mother, only provided for BTH events</txt>
</var>
<var ID="V14" name="DeliveryId" files="F1" intrvl="contin">
  <location StartPos="65" EndPos="68" width="4"/>
  <labl>DeliveryId</labl>
  <imputation>DeliveryId</imputation>
  <security>DeliveryId</security>
  <embargo>DeliveryId</embargo>
  <respUnit>DeliveryId</respUnit>
  <sumStat type="vald"/>
  <sumStat type="invd"/>
  <txt>The RecNr of the delivery event associated with this birth</txt>
</var>
</dataDscr></codeBook>
