<?xml version="1.0" encoding="UTF-8"?>
<codeBook version="1.2.2" ID="MNG_2013_MCC-H_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_MNG_2013_MCC-H_v01_M</IDNo>
    </titlStmt>
    <prodStmt>
      <producer abbr="MCC" affiliation="" role="Review of Metadata">Millennium Challenge Corporation</producer>
      <prodDate date="2014-05">2014-05</prodDate>
      <software version="v5">NADA</software>
    </prodStmt>
    <verStmt>
      <version>Version 1.0 (May 2014)
Version 2.0 (April 2015). Edited version based on Version 01 (DDI-MCC-MNG-IE-HEALTH-2014-v01) that was done by Millennium Challenge Corporation.</version>
    </verStmt>
  </citation>
</docDscr>
<stdyDscr>
  <citation>
    <titlStmt>
      <titl>Health 2013</titl>
      <subTitl/>
      <altTitl>MCC-H 2013</altTitl>
      <parTitl/>
      <IDNo>MNG_2013_MCC-H_v01_M</IDNo>
    </titlStmt>
    <rspStmt>
      <AuthEnty affiliation="">Pim de Graaf</AuthEnty>
    </rspStmt>
    <prodStmt>
      <copyright/>
      <software version="5.0" date="2021-05-03">NADA</software>
      <fundAg abbr="MCC" role="">Millennium Challenge Corporation</fundAg>
      <grantNo/>
    </prodStmt>
    <distStmt>
      <contact affiliation="Millennium Challenge Corporation" URI="" email="impact-eval@mcc.gov">Monitoring &amp; Evaluation Division</contact>
      <depDate date=""/>
      <distDate date=""/>
    </distStmt>
    <serStmt>
      <serName>Independent Performance Evaluation</serName>
      <serInfo/>
    </serStmt>
    <verStmt>
      <version date="">Not applicable to this evaluation; no quantitative data to be shared</version>
      <verResp/>
      <notes/>
    </verStmt>
    <biblCit format=""/>
    <notes/>
  </citation>
  <stdyInfo>
    <studyBudget/>
    <subject>
      <topcClas vocab="" vocabURI="">Health</topcClas>
      <topcClas vocab="" vocabURI="">Mongolia</topcClas>
      <topcClas vocab="" vocabURI="">Performance evaluation</topcClas>
    </subject>
    <abstract>To comprehensively evaluate the MCA Mongolia Health Project, the Independent Evaluator compared various survey data, reviewed project documents, and conducted interviews with project stakeholders. 

The evaluator reached the following conclusions (more can be found in Chapter 11 of the full report):
1. The Health Project has delivered a major contribution to Mongolia. Its courageous design that favored primary care and adopted a very population oriented approach - in contrast to a health system and hospitals first approach - has meant that the project had and still has ramifications in the most far away soums and khoroos. 

2. Strategies and activities of the Health Project were comprehensive and well chosen, some of them can be considered as good practice, see below. The expected impact of the NCDI strategies on the health of the population is long-term; effects of the Health Project on the Health System are short- and mid-term. 

3. The Health Project has implemented all the activities of the amended Compact, and more than that. In spite of serious obstacles, most activities were well planned and implemented. Exception to be made for the planning of the Stroke and AMI Units. 

4. The Health Project has strengthened the health system rather than weakened it, although there are areas for improvement. 

5. Beyond NCDIs, the Health Project has strengthened a culture of quality and thoroughness of planning and analysis in the Health System. It also has stimulated a culture of efficiency and accountability in the health sector. 

6. The period of actual implementation of the Health Project was between 24 and 30 months. This is far too short for a complex program that is so deeply embedded in the health system. Many components of the Health Project are half-finished, like training and the establishment of smooth running screening programs. 
In terms of sustainability, the Health Project missed a few opportunities, like leaving behind a costing plan for further investment and activities on NCDI's and a repository of relevant documents. Bits and pieces have been left behind but no complete repository.</abstract>
    <sumDscr>
      <collDate date="2013" event="start" cycle=""/>
      <collDate date="2013" event="end" cycle=""/>
      <nation abbr="MNG">Mongolia</nation>
      <geogCover/>
      <geogUnit/>
      <anlyUnit/>
      <universe/>
      <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/>
    <!-- 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/>
      <!-- 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/>
      <sampProc/>
      <sampleFrame>
        <sampleFrameName/>
        <custodian/>
        <universe/>
        <frameUnit isPrimary="">
          <unitType numberOfUnits=""/>
        </frameUnit>
        <updateProcedure/>
      </sampleFrame>
      <deviat/>
      <collMode/>
      <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/>
      <actMin/>
      <ConOps/>
      <weight/>
      <cleanOps/>
    </dataColl>
    <notes/>
    <anlyInfo>
      <respRate/>
      <EstSmpErr/>
      <dataAppr/>
    </anlyInfo>
    <stdyClas/>
    <dataProcessing type=""/>
    <codingInstructions relatedProcesses="" type="">
      <txt/>
      <command formalLanguage=""/>
    </codingInstructions>
  </method>
  <dataAccs>
    <setAvail>
      <accsPlac URI="http://data.mcc.gov/evaluations/index.php/catalog/97">Millennium Challenge Corporation</accsPlac>
      <origArch>Millennium Challenge Corporation
http://data.mcc.gov/evaluations/index.php/catalog/97
Cost: None</origArch>
      <avlStatus/>
      <collSize/>
      <complete/>
      <fileQnty/>
      <notes/>
    </setAvail>
    <useStmt>
      <confDec required="no" formNo="" URI=""/>
      <restrctn/>
      <citReq/>
      <deposReq/>
      <conditions/>
      <disclaimer/>
    </useStmt>
    <notes/>
  </dataAccs>
  <notes/>
</stdyDscr>
<dataDscr>
</dataDscr></codeBook>
