| Home » Topics » Child Health » matching WHO weight/height scores to older surveys (matching WHO weight/height scores to older surveys) Goto Forum:
	| 
		
			| matching WHO weight/height scores to older surveys [message #24358] | Thu, 28 April 2022 10:05  |  
			| 
				
				
					|  Elliott_Green Messages: 1
 Registered: April 2022
 | Member |  |  |  
	| Hello  my question is about how to link the "Height and Weight Scores - WHO Child Growth Standards" files to the Births Recode file.  I have two queries: 
 1.	For some surveys (cf. Benin 2001) the case identification is hwhhid and there is no hwcaseid to allow me to link the data to mothers (via the caseid variables) in the Births Recode file.  How can I access hwcaseid for these files?
 2.	For others (cf. Central African Republic 1994/95) there is indeed a hwcaseid variable allowing me to link to the caseid variables in the Births Recode files.  However, there is no individual data from the children which would allow me to link the data across the two files (i.e., the bidx variable in the Births Recode files).  How can I link the individual children to each other?
 
 I hope these questions make sense.  Thanks in advance for your help on this.
 
 best,
 
 Elliott Green
 Associate Professor
 Department of International Development
 London School of Economics
 Houghton Street
 London WC2A 2AE
 UK
 +44 (0)20-7852-3632
 |  
	|  |  |  
	| 
		
			| Re: matching WHO weight/height scores to older surveys [message #24360 is a reply to message #24358] | Thu, 28 April 2022 10:56  |  
			| 
				
				
					|  Janet-DHS Messages: 938
 Registered: April 2022
 | Senior Member |  |  |  
	| Following is response from DHS Research & Data Analysis Director, Tom Pullum: 
 With Benin 2001 (BJ41) and some other surveys the HW file includes a variable hwhhid that is a string containing hv001 and hv002.  You have to extract hv001 and hv002, which requires figuring out which columns of hwhhid contain them.  The following code will do this:
 
 use "...BJHW41FL.DTA", clear
 
 tab hwlevel
 * household file; the merge is with the PR file
 
 * Look at the values of hwhhid
 list hwhhid if _n<=20, table clean
 
 describe hwhhid
 * We see that hwhhid is a 12-character string; must unpack to get cluster number and household number
 
 forvalues lc=1/12 {
 gen c_`lc'=substr(hwhhid,`lc',1)
 }
 
 list c_* hwhhid if _n<=20, table clean compress
 
 * It appears that the cluster id is in cols 1-10 and the household id is in cols 11-12
 gen hv001=substr(hwhhid,1,10)
 gen hv002=substr(hwhhid,11,2)
 
 * convert from string to numeric
 destring hv001 hv002, replace
 
 drop c_*
 rename hwline hvidx
 
 sort hv001 hv002 hvidx
 
 I think that's what you are looking for.  In the HW file, hwline is the line number of the child.  You can then merge with the child in the PR file.  The mother's line number, if you need it, is hv112 on the child's record.
 
 
 For the CAR 1994-95 data (CF31), the merge is with the KR file, not the PR file.
 
 use "...CFHW31FL.DTA", clear
 
 tab hwlevel
 * individual file rather than household file; the merge is with the KR file
 
 tab hwline
 * It appears that hwline is bidx
 
 * Look at the values of hwcaseid
 list hwcaseid hwline if _n<=20, table clean
 
 describe hwcaseid
 * We see that hwcaseid is a 15-character string; must unpack to get cluster number and household number
 
 forvalues lc=1/15 {
 gen c_`lc'=substr(hwcaseid,`lc',1)
 }
 
 list c_* hwcaseid hwline if _n<=20, table clean compress
 
 * It appears that the cluster id is in cols 1-10 and the household id is in 11-12, the mother's line is in 13-15
 gen v001=substr(hwcaseid,1,10)
 gen v002=substr(hwcaseid,11,2)
 gen v003=substr(hwcaseid,13,3)
 
 * convert from string to numeric
 destring v001 v002 v003, replace
 
 drop c_*
 rename hwline bidx
 
 sort v001 v002 v003 bidx
 
 * Next merge with the KR file
 
 Here, hwline is bidx, the sequence of the child (bidx=1 is the youngest child).
 
 |  
	|  |  | 
 
 
 Current Time: Fri Oct 31 17:45:57 Coordinated Universal Time 2025 |