- EpiData-list - University of Manitoba Mailing Lists

Re: EpiData-list Digest, Vol 89, Issue 1
by epidata-list＠lists.umanitoba.ca 16 Mar '11

16 Mar '11

Thank you Jens for suggestion. It was helpful. I was trying to automate at entry, so did the following and it works, MSM RANGE 0 9 AFTER ENTRY IF (a = 1) and (b=0) THEN MSM=0 ENDIF IF (a = 1) and (b= 1) THEN MSM=1 ENDIF IF (a = 1) and (b= 1) and (c= 0) THEN MSM=2 ENDIF IF (a = 1) and (b= 1) and (c= 1) THEN MSM=3 ENDIF IF (a = 1) and (b= 1) and (c= 1) and (d = 0) THEN MSM=0 ENDIF IF (a = 1) and (b= 1) and (c= 1) and (d = 1) THEN MSM=4 ENDIF IF (a = 1) and (b= 1) and (c= 1) and (d = 1) and (e=0) THEN MSM=9 ENDIF END END *Bijay Adhikari*, PhD, MPH, DVM Prov. Communicable Disease Epidemiologist Population Health Branch Saskatchewan Ministry of Health Regina, SK Canada On Sat, Mar 12, 2011 at 12:00 PM, <epidata-list-request(a)lists.umanitoba.ca>wrote: > Send EpiData-list mailing list submissions to > epidata-list(a)lists.umanitoba.ca > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > or, via email, send a message with subject or body 'help' to > epidata-list-request(a)lists.umanitoba.ca > > You can reach the person managing the list at > epidata-list-owner(a)lists.umanitoba.ca > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of EpiData-list digest..." > > > EpiData-list mailing list > ___________________________________ > > Today's Topics: > > 1. Conditional formula (epidata-list(a)lists.umanitoba.ca) > 2. Re: Conditional formula (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 11 Mar 2011 18:43:02 -0600 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Conditional formula > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <AANLkTik4syh1ti3z-sqV=SA+ULthRgmLrfYYxjpj_H-m(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hello Epidata users, I am having problem to code conditional formula in > epidata as described below, can anyone suggest how to code to the following > condition, > > If a= 1 and b = 1 then exposure= K > > If a= 1 and b = 0 then exposure= K > > If a= 1 and b = 1 and c= 1 then exposure= K > > If a= 1 and b = 1 and c= 1 and d=0 then exposure= K > > If a= 1 and b = 1 and c= 1 and d=1 then exposure= K > > else exposure= K1 > > Thanks > > > -- > *Dr. Bijay Adhikari*, PhD, MPH, DVM* > Prov. Communicable Disease Epidemiologist > Population Health Branch > Saskatchewan Ministry of Health > Regina, SK Canada > > > ------------------------------ > > Message: 2 > Date: Sat, 12 Mar 2011 10:45:12 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Conditional formula > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4D7B40A8.8080601(a)epidata.dk> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hello Epidata users, I am having problem to code conditional formula in > > epidata as described below, can anyone suggest how to code to the > following > > condition, > I think the problem is that you should use more parenthesis. Is this in > analysis or in entry ? > > I assume analysis: > > * first create the integer variable k: > define k # > * or you could use the gen statement: "i" makes this an integer variable > gen i k = 0 > > * give labels > labelvalue k /0="No" /1="Yes" /9="Missing" /8="Not recoded" > > * now for certain conditions change exposure to "no" or yes: > * I just give different examples > * first I give all the value 8 to make sure I am in control of the > recoding: > k = 8 > If ( (a= 1) and (b = 1)) then exposure= 0 > If ( (f = 1) ) then exposure= 9 > If ( (a= 1) and (b = 1) and (c = 1) and (d = 1) ) then exposure= 1 > tab k > * if any records are stille with the value 8, then you would know there > is a problem. > > regards > Jens Lauritsen > EpiData Association > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 89, Issue 1 > ******************************************* >

1 0

EpiData Entry Program Exceeding 999 Lines
by epidata-list＠lists.umanitoba.ca 16 Mar '11

16 Mar '11

Hello, I am working on a project with a data entry program that exceeds 999 lines and I would like to avoid breaking the entry into sections (we would need at least 4 sections for our data entry program). Are there any tricks to work around this situation besides breaking up the program into several parts? If not, does anyone have suggestions for alternative programs to use for data entry on long surveys like this? I have heard that CSPro may work, but I have no experience with it. If you have any experience with CSPro or other data entry programs that might work, please email me directly ( Haddaway-sam(a)norc.org). Thanks, Sam Sam Haddaway | Research Analyst, International Projects NORC at the University of Chicago 4350 East-West Highway, 8th Floor, Bethesda MD 20814 haddaway-sam(a)norc.org <mailto:haddaway-sam@norc.org> | office +1 (301) 634-9423

1 1

EpiData for Mac
by epidata-list＠lists.umanitoba.ca 15 Mar '11

15 Mar '11

Dear EpiData colleagues, I have just started using Epidata and I own a mac. There seem to be no detailed help guides to help follow and use the Mac version. Is it that its still under development? Is there anyone with access to this document Kind Regards Aloysius Ssemaganda UVRI/IAVI HIV Vaccine Program Uganda Virus Research Institute P.O.Box 49 Entebbe,Uganda. Tel: +256 414 322 377/8,+256 414 321 094 Cell: +256 782 334 633 Fax: + 256 414 321 124 Email: assemaganda(a)iavi.or.ug or assemaganda(a)gmail.com

1 1

Conditional formula
by epidata-list＠lists.umanitoba.ca 12 Mar '11

12 Mar '11

Hello Epidata users, I am having problem to code conditional formula in epidata as described below, can anyone suggest how to code to the following condition, If a= 1 and b = 1 then exposure= K If a= 1 and b = 0 then exposure= K If a= 1 and b = 1 and c= 1 then exposure= K If a= 1 and b = 1 and c= 1 and d=0 then exposure= K If a= 1 and b = 1 and c= 1 and d=1 then exposure= K else exposure= K1 Thanks -- *Dr. Bijay Adhikari*, PhD, MPH, DVM* Prov. Communicable Disease Epidemiologist Population Health Branch Saskatchewan Ministry of Health Regina, SK Canada

1 1

Thankyou
by epidata-list＠lists.umanitoba.ca 26 Feb '11

26 Feb '11

Hi Everyone, I would like to thank you for all your help answering my query with Epidata. All your help is much appreciated. Kind Regards, Niamh

1 0

Query about Epidata and Exporting to SPSS
by epidata-list＠lists.umanitoba.ca 25 Feb '11

25 Feb '11

Hi all, I have a quick question. I used Epidata to put all my data from a survey I conducted. I did not export all my inputted data in SPSS but I am using SPSS for analysis. I was wondering is it possible to export all of my data in Epidata into SPSS. Or is it better to manually put it into SPSS. Also, I am new to research and statistics and was advised to use Epidata first and then analyse using SPSS. I was wondering why people use Epidata first and then export to SPSS. I mean, what are the advantages of doing this? Is it better to do this first and then export to SPSS? Any advise would be greatly appreciated, Kind Regards, Niamh

1 4

Check commands and field naming
by epidata-list＠lists.umanitoba.ca 19 Feb '11

19 Feb '11

Well done to Jens and Torsten on the progress of the manager and entry client. I have a few questions. I see that there is a confirm field check in the manager, but appears to be applied to the field in question only. So if one wishes to make every field a confirm field, then such an edit would need to be made for every field. I wondered if there were plans to enable the user to set such a thing for the whole database by having it as a global setting. Similarly for a missing value (9999 might always be a missing value code). Another question is whether there any plans to enable chk files created in EpiData Entry to be imported into the manager and/or rec files containing such checks to be brought into the manager with the checks preserved (at present they are ignored). A final question concerns the pasting of a qes file into the manager which uses EpiData Entry automatic field naming (i.e. the curly brackets to define filed names) and whether this will be supported in the manager. At present, the brackets are ignored by the program. Regards, Neville ----------------------------------------- ************************************************************************** The information contained in the EMail and any attachments is confidential and intended solely and for the attention and use of the named addressee(s). It may not be disclosed to any other person without the express authority of the HPA, or the intended recipient, or both. If you are not the intended recipient, you must not disclose, copy, distribute or retain this message or any part of it. This footnote also confirms that this EMail has been swept for computer viruses, but please re-sweep any attachments before opening or saving. HTTP://www.HPA.org.uk **************************************************************************

1 1

Updated entry client fixing a backup problem uploaded
by epidata-list＠lists.umanitoba.ca 16 Feb '11

16 Feb '11

Unfortunately the backup at closure of a project was not working in the EntryClient uploaded last friday. This has been fixed in the version which has just been uploaded. An article on data quality describing the principles we are working under is available now as a free pdf from: http://www.ingentaconnect.com/search/download?pub=infobike%3a%2f%2fiuatld%2… the reference is: Quality assurance of data: ensuring that numbers reflect operational definitions and contain real measurements Authors: Rieder, H.L.1; Lauritsen, J.M.2 Source: The International Journal of Tuberculosis and Lung Disease, Volume 15, Number 3, March 2011 , pp. 296-304(9) regards to all Jens Lauritsen EpiData Association regards to all Jens Lauritsen EpiData Association

1 0

Asymmetric limbs of Confidence Interval - clarification
by epidata-list＠lists.umanitoba.ca 16 Feb '11

16 Feb '11

Please see below the table generated in Epidata analysis and note the confidence interval in the first row HIV results Total 1539 108 7.0 (5.8-8.4) This is the proportion of HIV infected among a group of TB suspects which is 7% with 95% CI being 5.8 - 8.4. It can be deduced that the upper limb of confidence interval(which is 1.96 times Standard error) is 8.4 minus 7 = 1.4 Similarly, it can be deduced that the lower limb of confidence interval(which is 1.96 times Standard error) is 7 minus 5.8 = 1.2 *Query - why are the two limbs of the confidence interval different?* the same observation can be noted in all CIs noted above in the table. The asymmetry of limbs of CI are expected in case of non-linear measures like Odds Ratio, Relative risk, Hazard Ratio etc, but not in case of simple proportions. I am given to understand (from Dr Hans Reider, from whom I learnt Epidata) that EpiData Analysis is purported to follow the recommendations by the BMJ in the calculation of most confidence intervals and this would indeed suggest that the CI around a proportion should be symmetric on a linear scale. Would be grateful if you could clarify. Regards, Ajay -- ****************** Dr. M. V. Ajay Kumar WHO National Consultant - RNTCP Central TB Division, MOHFW 523'C' Wing, Nirman Bhavan, Maulana Azad Road, New Delhi - 110108 Mail - No. 353-C, J&K Pocket, Dilshad Garden, Delhi - 110095 Phone : +91-9311384574 Email : Kumaramv(a)rntcp.org;

1 2

Technical details of test release
by epidata-list＠lists.umanitoba.ca 16 Feb '11

16 Feb '11

Dear All Today we have released new test versions of EpiData EntryClient and EpiData Manager. This email is mainly technical and will give broad view of changes and additions to the two programs. Important aspect: flow of entry. On a normal entry of fields, the flow is defined as moving from field to field in a left-to-right, then down, manner – but at the same time following sections. Once inside a section this section will be completed before exiting. This should simulate a normal work flow working with schemes/registration forms. The flow of entry is followed if you leave the field in a "standard" way. Standard ways are: "The entire length of the field is filled" or by using one of the following keys: ”Arrow down”, ”Enter” or ”Tab”. These keys are "flow of entry keys" and should be used during data entry. To break the flow of entry (not recommended) : Either use "Arrow Up" key, the mouse or enter a legal value and then avoid saving the record. We note "not recommended" since a field could have some attributes set that defines another flow of entry, e.g. a jump. The programming is handled in three "parts": A common core, EntryClient and Manager. Any change to the Core module will affect the two other parts: *Changes for Core*: * Define jumpsfor a field. Changes the flow of entry (see above) and rules for resetting field data. (leave as is, blank, add defined missing) * Define Entry Mode for a field. The possible (mutually exclusive) attributes are: Default Entry, Must Enter or No Enter. * Define Confirm Entry. This will force a user to confirm the entry using a key (see below). * Define Show Value Label. Show category text for a given entered value next to the field (right side) (formerly known as comment legal show). * Various bug fixes, including incorrect import of dates from Stata files and definitions of "missing" status of a Value Label. Changes for both programs: * Added a check such that programs can only be started once (single instance). * The programs now check that the active project file has not been modified between saves. * Added short-cuts to the 9 most recent files: Ctrl + Shift + <number> * Shortcuts for Mac OS X have been changed to follow the native style of the OS. * Adapted setup and properties for the new options Changes for Manager: * Hides Work Process Toolbar when a project is active. * Assign jumpsto field. One or more jumps may be assigned to a field. * Added the ability to "copy & paste" field/heading/sections on the designer. - A section can be copied to the main section. - Copying a section will also copy fields/headings within that section. - Fields/Headings can be copied to/from sections (including main section). - Field attributes can be copied from one field to another of same type. * "Tab" key should now work as "change cell" key on the Value Label Editor. * Value Label Editor modified. * Flyspray bugfixes: 71, 72, 73 Changes for Entry: * AutoIncrement (Formerly IDNUM) fields can start at a defined value * User specified Colour for errors * Enhanced control of focus for active field. * Fixed several bugs - including loading of corrupt/invalid files Kind regards, Torsten Bonde Christiansen Jens Lauritsen EpiData Association.

1 1