- EpiData-list - University of Manitoba Mailing Lists

found it! Re: EpiData-list Digest, Vol 55, Issue 20
by epidata-list＠lists.umanitoba.ca 10 Jun '08

10 Jun '08

Hello! managed to sort it out, pasting below the proper one if something fyi! DISP1 AFTER ENTRY IF (DRUG1="EFV") and (DOS1=600) and (DISP1>28) and (DISP1<101) THEN DAILYD1=1 GOTO DRUG2 ENDIF IF (DRUG1="EFV") and (DOS1=200) and (DISP1>118) and (DISP1<181) THEN DAILYD1=4 GOTO DRUG2 ENDIF IF (DRUG1="EFV") and (DOS1=200) and (DISP1>88) and (DISP1<110) THEN DAILYD1=3 GOTO DRUG2 ENDIF END END best regards ziad On Tue, Jun 10, 2008 at 12:08 PM, Ziad El-Khatib <ziad.khatib(a)gmail.com> wrote: > Hi again, > another question inline with previous query i posted last month, to > have different -if..then- conditions (pasted below), when i test it, > it does not write anything under DAILYD1 cell, as instructed below, > any tips? > > DISP1 > AFTER ENTRY > IF (DRUG1="EFV" & DOS1=600 & DISP1>29 & DISP1<101) THEN > DAILYD1=1 > ELSE > IF (DRUG1="EFV" & DOS1=200 & DISP1>119 & DISP1<181) THEN > DAILYD1=4 > ELSE > IF (DRUG1="EFV" & DOS1=200 & DISP1>89 & DISP1<110) THEN > DAILYD1=3 > GOTO DRUG2 > ENDIF > ENDIF > ENDIF > END > END > > > > > > Thank you and best regards > ziad > > > On Thu, May 29, 2008 at 10:03 AM, > <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. Re: If..then (epidata-list(a)lists.umanitoba.ca) >> 2. re: If..then (epidata-list(a)lists.umanitoba.ca) >> 3. Re: EpiData-list Digest, Vol 55, Issue 19 Missing values is >> not NA (epidata-list(a)lists.umanitoba.ca) >> >> >> ---------- Forwarded message ---------- >> From: epidata-list(a)lists.umanitoba.ca >> To: epidata-list(a)lists.umanitoba.ca >> Date: Wed, 28 May 2008 20:33:07 +0200 >> Subject: Re: [EpiData-list] If..then >> Perhaps: >> >> AFTER ENTRY >> IF v64="NA" THEN >> V65=9 >> V66=9 >> goto V67 >> ENDIF >> END >> >> >> Regards, >> >> Hans >> >> >> epidata-list(a)lists.umanitoba.ca wrote: >>> >>> Hi, >>> might be easy question, i am trying to write condition under check >>> file to write value of 9 in 2 places if one cell equal to NA (code >>> below), it does not work (and no error message), any tips? >>> >>> >>> >>> Thank you in advance >>> best regards >>> ziad >>> >>> >> >> -- >> Hans L Rieder, MD, MPH >> Jetzikofenstr. 12 >> 3038 Kirchlindach >> Switzerland >> >> Tel: +41 31 829 4577 >> Mob: +41 79 321 9122 >> Web: http://www.tbrieder.org >> >> >> >> >> >> ---------- Forwarded message ---------- >> From: epidata-list(a)lists.umanitoba.ca >> To: epidata-list(a)lists.umanitoba.ca >> Date: Wed, 28 May 2008 23:33:56 +0200 >> Subject: [EpiData-list] re: If..then >> Just split in three lines: >> >> after entry >> IF v64=NA THEN >> LET V65=9 >> V66=9 >> goto V67 >> ENDIF >> >> >> regards >> Jens Lauritsen >> EpiData Association >> >> >> >> ---------- Forwarded message ---------- >> From: epidata-list(a)lists.umanitoba.ca >> To: epidata-list(a)lists.umanitoba.ca >> Date: Thu, 29 May 2008 09:05:47 -0300 >> Subject: [EpiData-list] Re: EpiData-list Digest, Vol 55, Issue 19 Missing values is not NA >> Dear friend Ziad, >> >> NA is common expression to identify missing values. If you are working with >> R or S-Plus then NA is NA. That means that all functions or commands that >> you want to specify NA, the expression is also NA. However, in Stata or >> Epidata entry the NAs are epecified by dots (.) and sometimes by empty >> quotes (" ") depending if the variable of interest is formated as numeric or >> text. So, my guess is that your check command will work fine if do like >> this... >> >> AFTER ENTRY >> IF v64=. THEN >> LET V65=9 & V66=9 & goto V67 >> ENDIF >> END >> >> Best regards, >> Pedro Emmanuel >> >> >> >>> Today's Topics: >>> >>> 1. If..then (epidata-list(a)lists.umanitoba.ca) >>> >>> >>> ---------------------------------------------------------------------- >>> >>> Message: 1 >>> Date: Wed, 28 May 2008 08:47:34 -0700 >>> From: epidata-list(a)lists.umanitoba.ca >>> Subject: [EpiData-list] If..then >>> To: epidata-list(a)lists.umanitoba.ca >>> Message-ID: >>> <897a5cf60805280847u3b99c66ak6f49e3855b879141(a)mail.gmail.com> >>> Content-Type: text/plain; charset=ISO-8859-1 >>> >>> Hi, >>> might be easy question, i am trying to write condition under check >>> file to write value of 9 in 2 places if one cell equal to NA (code >>> below), it does not work (and no error message), any tips? >>> >>> AFTER ENTRY >>> IF v64=NA THEN >>> LET V65=9 & V66=9 & goto V67 >>> ENDIF >>> >>> >>> Thank you in advance >>> best regards >>> ziad >>> >>> >>> ------------------------------ >>> >>> ________________________________________ >>> EpiData-list(a)lists.umanitoba.ca >>> http://lists.umanitoba.ca/mailman/listinfo/epidata-list >>> >>> >>> End of EpiData-list Digest, Vol 55, Issue 19 >>> ******************************************** >>> >> >> >> ________________________________________ >> EpiData-list(a)lists.umanitoba.ca >> http://lists.umanitoba.ca/mailman/listinfo/epidata-list >> >> >

1 0

Re: EpiData-list Digest, Vol 55, Issue 20
by epidata-list＠lists.umanitoba.ca 10 Jun '08

10 Jun '08

Hi again, another question inline with previous query i posted last month, to have different -if..then- conditions (pasted below), when i test it, it does not write anything under DAILYD1 cell, as instructed below, any tips? DISP1 AFTER ENTRY IF (DRUG1="EFV" & DOS1=600 & DISP1>29 & DISP1<101) THEN DAILYD1=1 ELSE IF (DRUG1="EFV" & DOS1=200 & DISP1>119 & DISP1<181) THEN DAILYD1=4 ELSE IF (DRUG1="EFV" & DOS1=200 & DISP1>89 & DISP1<110) THEN DAILYD1=3 GOTO DRUG2 ENDIF ENDIF ENDIF END END Thank you and best regards ziad On Thu, May 29, 2008 at 10:03 AM, <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. Re: If..then (epidata-list(a)lists.umanitoba.ca) > 2. re: If..then (epidata-list(a)lists.umanitoba.ca) > 3. Re: EpiData-list Digest, Vol 55, Issue 19 Missing values is > not NA (epidata-list(a)lists.umanitoba.ca) > > > ---------- Forwarded message ---------- > From: epidata-list(a)lists.umanitoba.ca > To: epidata-list(a)lists.umanitoba.ca > Date: Wed, 28 May 2008 20:33:07 +0200 > Subject: Re: [EpiData-list] If..then > Perhaps: > > AFTER ENTRY > IF v64="NA" THEN > V65=9 > V66=9 > goto V67 > ENDIF > END > > > Regards, > > Hans > > > epidata-list(a)lists.umanitoba.ca wrote: >> >> Hi, >> might be easy question, i am trying to write condition under check >> file to write value of 9 in 2 places if one cell equal to NA (code >> below), it does not work (and no error message), any tips? >> >> >> >> Thank you in advance >> best regards >> ziad >> >> > > -- > Hans L Rieder, MD, MPH > Jetzikofenstr. 12 > 3038 Kirchlindach > Switzerland > > Tel: +41 31 829 4577 > Mob: +41 79 321 9122 > Web: http://www.tbrieder.org > > > > > > ---------- Forwarded message ---------- > From: epidata-list(a)lists.umanitoba.ca > To: epidata-list(a)lists.umanitoba.ca > Date: Wed, 28 May 2008 23:33:56 +0200 > Subject: [EpiData-list] re: If..then > Just split in three lines: > > after entry > IF v64=NA THEN > LET V65=9 > V66=9 > goto V67 > ENDIF > > > regards > Jens Lauritsen > EpiData Association > > > > ---------- Forwarded message ---------- > From: epidata-list(a)lists.umanitoba.ca > To: epidata-list(a)lists.umanitoba.ca > Date: Thu, 29 May 2008 09:05:47 -0300 > Subject: [EpiData-list] Re: EpiData-list Digest, Vol 55, Issue 19 Missing values is not NA > Dear friend Ziad, > > NA is common expression to identify missing values. If you are working with > R or S-Plus then NA is NA. That means that all functions or commands that > you want to specify NA, the expression is also NA. However, in Stata or > Epidata entry the NAs are epecified by dots (.) and sometimes by empty > quotes (" ") depending if the variable of interest is formated as numeric or > text. So, my guess is that your check command will work fine if do like > this... > > AFTER ENTRY > IF v64=. THEN > LET V65=9 & V66=9 & goto V67 > ENDIF > END > > Best regards, > Pedro Emmanuel > > > >> Today's Topics: >> >> 1. If..then (epidata-list(a)lists.umanitoba.ca) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Wed, 28 May 2008 08:47:34 -0700 >> From: epidata-list(a)lists.umanitoba.ca >> Subject: [EpiData-list] If..then >> To: epidata-list(a)lists.umanitoba.ca >> Message-ID: >> <897a5cf60805280847u3b99c66ak6f49e3855b879141(a)mail.gmail.com> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> Hi, >> might be easy question, i am trying to write condition under check >> file to write value of 9 in 2 places if one cell equal to NA (code >> below), it does not work (and no error message), any tips? >> >> AFTER ENTRY >> IF v64=NA THEN >> LET V65=9 & V66=9 & goto V67 >> ENDIF >> >> >> Thank you in advance >> best regards >> ziad >> >> >> ------------------------------ >> >> ________________________________________ >> EpiData-list(a)lists.umanitoba.ca >> http://lists.umanitoba.ca/mailman/listinfo/epidata-list >> >> >> End of EpiData-list Digest, Vol 55, Issue 19 >> ******************************************** >> > > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > >

1 0

Re: [EpiData-list] Re: Outbreak analysis diary - multiple data sets
by epidata-list＠lists.umanitoba.ca 10 Jun '08

10 Jun '08

Hi Jamie Sorry I sent the message without finishing my section on multiple data sets. Working with Multiple data sets in Epidata Analysis What I was going to say was our first attempt at working with several copies of an outbreak dataset had been sucessful. This was a timing thing - we wanted to get the data in more quickly. We had already entered 150 records when we decided to use another data entry person, but that was Ok the process still worked. Our steps were 1. Created a file and entered records (outbreak1) 2. Used Tools copy structure to create a new file (outbreak 2) 3. Entered records in both outbreak 1 and outbreak 2 4. Used Data in/out then Append/merge option B to create a new file outbreak_final, that was outbreak1 and outbreak 2 combined. What was good about this was that it was easy, and I also really liked the option to copy the check file we had set up for the first file to use with the new file when you copied the structure. The only thing I didn't like so much was we ended up with a duplicate ID which we wouldn't get with an autoID (which we usually use for our ID field) but I used a number field rather than AutoID this time as I thought it would be a problem with the merge to have auto ID. Using Multiple data sets in Epidata Analysis - READ and multiple data sets Could you explain a bit more about how to do this. When I try and READ more than one data set it says "no data will be lost close first". Then - what does the SAVEDATA do - create a new file like MERGE does? Which do you recommend to combine data - Merging in Epidata entry or in Analysis. Using Epidata analysis in a field epidemilogy course I'm very interested in how you use Epidata Analysis in your field epidemiology course . Would I be able to find out a bit more about this from you - perhaps off the list to avoid taking up too much time on this topic? As I am involved in teaching courses using epidata/epi info to support field epi I am very interested in what you cover in your courses but realise others may not have the same interest Many thanks Christine For multiple data sets (we do this every year in our Field Epidemiology Course), you can use Merge in EpiData Entry or just READ multiple data sets on one line in Analysis and then SAVEDATA. Jamie Christine wrote: > I really like the outbreak analysis feature but on my wish list would be > 1. for 'outbreak analysis' to be an option in one of the menus somewhere. I only knew about this feature through someone mentioning it on the list and I had to search through the docuentation to find it. Maybe this was what the 'attack rate plus RR' option was but I could not seem to select this - it stayed greyed out Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 -- The information contained in this email and any attachments is confidential and may be legally privileged. If you have received this message in error, please notify the sender immediately and remove all copies of the message, including any attachments. Any views or opinions expressed in this email (unless otherwise stated) may not represent those of Hutt Valley DHB. Thank you. ** Disclaimer added by HVDHB **

1 1

If..then
by epidata-list＠lists.umanitoba.ca 10 Jun '08

10 Jun '08

Hi, might be easy question, i am trying to write condition under check file to write value of 9 in 2 places if one cell equal to NA (code below), it does not work (and no error message), any tips? AFTER ENTRY IF v64=NA THEN LET V65=9 & V66=9 & goto V67 ENDIF Thank you in advance best regards ziad

1 2

EpiData Analysis notes
by epidata-list＠lists.umanitoba.ca 10 Jun '08

10 Jun '08

Dear Christine We do have notes (although different trainers have different notes to reflect their own style). If you wish we can discuss further off-list (e-mail neville.verlander(a)hpa.org.uk). Regards, Neville ------------------------------------------------------------------------ ------------------------------------------------------------------------ ------------------------------------------------------------------------ ----------------------------- Neville Verlander Statistics Unit Statistics, Modelling and Bioinformatics Department Health Protection Agency Centre for Infections 61 Colindale Avenue London NW9 5EQ Tel: (direct) (+44) (0)208 3277426 Fax: (+44) (0)208 200 7868 ----------------------------------------- ************************************************************************** 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 0

RE: [EpiData-list] Outbreak analysis diary - Defining cases as a newvariable
by epidata-list＠lists.umanitoba.ca 08 Jun '08

08 Jun '08

Hi Alistair Thank you for that. I found a copy of your training manual for using Epidata/Epi Info for analysing outbreaks on the web and think it is excellent. Yes it is an interesting question about whether to change to Epidata Analysis for outbreak analysis. Like you I teach courses in using Epidata/Epiinfo and am interested in it from an ease of teaching/ease of use perspective as well as for my own use. For my own use I am pretty sure I will change to Epidata analysis. We just had another small outbreak come up at the same time as the one I have been writing to the list about and my colleague wanted the data analysed in a hurry. Data had been entered in a questionnaire that was based on our standard epidata master one, just as the large outbreak was. I copied the programme I had written and saved for the large outbreak in Epidata analysis - made a couple of small changes - and was able to print out a symptoms profile, Epicurv graphs and two full attack rate tables - one with the outcome sick and one for the outcome of case (the case definition was created as part of the programme) for the 25 foods of interest less than 15 minutes. I thought that was pretty good. For my training courses though I am not so sure. A large group coming to these are field staff who are new and/or infrequent users of any outbreak analysis software. At the moment my instinct is that although Epidata Analysis does things more quickly and has some great features- especially the attack rate tables which are brilliant - I think Epi info is easier for these new or infrequent users to understand. I am thinking I may see if their is interest in me developing a one day course to introduce Epidata Analysis to people in public health units who are likely to take on a regular role analysing outbreaks, and stick with my current Epi info course for the wider group who want a very basic knowledge - so that it an emergency they could get out the manual and follow the instructions if the main person is away. I am interested to see though that the Health Protection Agency in the UK is offering both beginning and advanced one day courses for in Epidata Entry/Epidata Analysis. I saw the course outlines on the web http://www.hpa.nhs.uk - click on training and events - but I would love to see if I could have a look at their training notes. Do you know anything about these courses? In terms of a basic set of introduction notes I found the training notes (pdf file) provided by the International Union against Tuberculosis and Lung disease very helpful. The link is http://www.tbrieder.org then go to Epidata best wishes Christine >>> <epidata-list(a)lists.umanitoba.ca> 6/06/2008 7:41 p.m. >>> Christine These notes are really useful, thank you! Like you I have 'traditionally' used EpiData for questionnaire design and entry, and then switched to Epi Info for Windows for the more user-friendly (to me at least) data analysis. Hopefully your experiences will give a good idea to others about the readiness of EpiData Analysis for use in this type of situation. Thanks Alastair --------------------------------------- Alastair Tomlinson Chartered EHP, Lecturer in Environmental Health 029 2020 1528 AGTomlinson(a)uwic.ac.uk -----Original Message----- From: epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Sent: 05 June 2008 06:05 To: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Outbreak analysis diary - Defining cases as a newvariable Today we started doing the analysis of exposures for our outbreak. First we need to create a new variable, as not everyone who is sick meets the case definition for the outbreak. Case definition Our case definition is someone who has diarrhoea and/or vomiting 24-72 hours after the function. I used the programme editor to define a new variable called Case I made case a Boolean field so the relative risks would calculate correctly (with a Boolean field the Y appears first in a two by two table and then the N and this is what you want to calculate relative risks correctly). Diarrhoea and Vomit - the fields I needed to create the Case field were also Booklean fields. For a long time I had a problem as I was trying many combinations of If Diarrhoea = Yes or Y or "Y" in my code and it was not working. Then my workmate suggested I try TRUE. I think this is confusing as when you print a Frequency of a boolean Field it prints as Y. Anyway here was the code that worked. Define case <Y> If Diarrhoea = TRUE or Vomit = TRUE then case = TRUE This deals with the first part of the case definition - that they must have diarrhoea or vomiting. The next part is that they are NOT a case if the symptoms started on the same day. The code I ended up using for this was IF onsetdate <= date("24/05/2008") then case = FALSE. I had to put the date function as well as the date itself or the code would not run. I don't know why that is but any other combination I tried like "24/05/2008" or 24/05/2008 or ("24/05/2008") did not work. Onsetdate In the last post I asked if anyone had some code to create a single onset date from two pieces of information - the vomitdate and the diarrhoea date. My workmate helped me figure out something that worked and this is it. If diadate < vomdate then onsetdate = diadate If vomdate < diadate then onsetdate = vomdate If vomdate =diadate then onsetdate = diadate If vomdate =(.) then onsetdate = diadate If diadate =(.) then onsetdate = vomdate Now we have a variables of case and onset date and I created an Epicurv graph using them. It was great. One more frustration. While we were working on the code we often used browse to check our results. We wrote the browse command into the programme editor but the results of the Browse do not appear in the output so I had to do it over again each time in the output screen. I tried list instead of Browse but this didn't work either. Any suggestions for how you can build the output from a browse or line list command into a programme will be welcome. Next posting we will get on to analysing the exposures thanks Christine -- The information contained in this email and any attachments is confidential and may be legally privileged. If you have received this message in error, please notify the sender immediately and remove all copies of the message, including any attachments. Any views or opinions expressed in this email (unless otherwise stated) may not represent those of Hutt Valley DHB. Thank you. ** Disclaimer added by HVDHB ** Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 -- The information contained in this email and any attachments is confidential and may be legally privileged. If you have received this message in error, please notify the sender immediately and remove all copies of the message, including any attachments. Any views or opinions expressed in this email (unless otherwise stated) may not represent those of Hutt Valley DHB. Thank you. ** Disclaimer added by HVDHB **

1 0

Re: Outbreak analysis diary - attack rate table
by epidata-list＠lists.umanitoba.ca 08 Jun '08

08 Jun '08

thanks very much Jens, Hans and Jamie for the suggestions and Alistair for the encouragement. Hans thanks I tried your suggestion for the browse and it worked well. The other suggestions will take a bit longer to work through. I will report back when I do but this post I want to report on the analysis and also the success of creating and combining two data entry files. Attack rate table of exposures As has been said several times on this list but is worth saying again, the 'outbreak analysis' function in Epidata that creates a single attack rate table showing attack rates, relative risks, CIS and pvalues of all exposures of interest against the outcome of 'case' is a wonderful feature. The command is TAB CASE .....all exposures of interest/OA The steps I took were: 1. Click on Browse Data from the menu bar 2. Tick my outcome of interest (Case) and all my exposures of interest (foods etc) 3. Click on Paste (this copies all the selected variables into the section at the bottom of the output screen) 4. I then copied this line into the programme editor, took out the browse at the start and added/OA at the end as below: TAB CASE ANYFOOD COURTL1 COURTL2 JUNGLEPLAY JTOILET BTOILET KIOSK M1NUGGETS M2CHEERIOS M3CHIPS M4SAUCE M5PIZZA M6JUICE M7JELLYICE M8YOGURT M9CHOCCRAC M10CAKE M11LOLLIES M12TEA M13COFFEE M14SAV M15SAND M16HOTDOG M18FISHBIT M19FISHFIL M20FRUITSA M21DANISH M22BURGER/OA Note: Adding EX after OA gives the pvalue I then selected run programme - this creates the attack rate table in the output screen, and also in the default output file. I really like the outbreak analysis feature but on my wish list would be 1. for 'outbreak analysis' to be an option in one of the menus somewhere. I only knew about this feature through someone mentioning it on the list and I had to search through the docuentation to find it. Maybe this was what the 'attack rate plus RR' option was but I could not seem to select this - it stayed greyed out. 2. If a select' has been used for this to show above the attack rate table. I ran the outbreak analysis above again but this time selecting only people who had attended the centre on a certain date. The command I used was Select Day25 = TRUE I know the select has worked because N has gone down from 251 to 66, but there is no indicaiton on the output file or the information under the attack rate table that a 'select' is in place. Thank you all again for your feedback on these postings. I will do one maybe two more - covering the process of sending the data output to a report and a final summary of the main steps and final programme I used. Christine Having more than one data entry file We ended up with 250 questionnaires so decided we would try using several data entry operators to enter the data Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 >>> <epidata-list(a)lists.umanitoba.ca> 6/06/2008 8:56 a.m. >>> Dear Christine: Just a quick comment on BROWSE. Did you use the command: set display databrowser=on before issuing the BROWSE field1 field2 command? The default is that the browser is off. Note that this works fine with the public release version, but if you experiment withe (marvelous) test version build 134, there seems to be some hickup that occasionally blocks the program, but I believe to have noted that it works if the command is in the beginning of the program before reading the file (not yet certain). In any case, I appreciate your telling us your experiences, they are useful for many. Apologies for not taking the time to answer to more of your queries, but I am currently a bit taken with traveling between continents. Regards, Hans epidata-list(a)lists.umanitoba.ca wrote: > Today we started doing the analysis of exposures for our outbreak. First we need to create a new variable, as not everyone who is sick meets the case definition for the outbreak. > > Case definition > Our case definition is someone who has diarrhoea and/or vomiting 24-72 hours after the function. > I used the programme editor to define a new variable called Case > I made case a Boolean field so the relative risks would calculate correctly (with a Boolean field the Y appears first in a two by two table and then the N and this is what you want to calculate relative risks correctly). > > Diarrhoea and Vomit - the fields I needed to create the Case field were also Booklean fields. For a long time I had a problem as I was trying many combinations of If Diarrhoea =es or Y or "Y" in my code and it was not working. Then my workmate suggested I try TRUE. I think this is confusing as when you print a Frequency of a boolean Field it prints as Y. Anyway here was the code that worked. > > Define case <Y> > If Diarrhoea =RUE or Vomit = TRUE then case = TRUE > > This deals with the first part of the case definition - that they must have diarrhoea or vomiting. The next part is that they are NOT a case if the symptoms started on the same day. > > The code I ended up using for this was IF onsetdate <=ate("24/05/2008") then case = FALSE. I had to put the date function as well as the date itself or the code would not run. I don't know why that is but any other combination I tried like "24/05/2008" or 24/05/2008 or ("24/05/2008") did not work. > > Onsetdate > In the last post I asked if anyone had some code to create a single onset date from two pieces of information - the vomitdate and the diarrhoea date. My workmate helped me figure out something that worked and this is it. > > If diadate < vomdate then onsetdate =iadate > If vomdate < diadate then onsetdate =omdate > If vomdate =adate then onsetdate = diadate > If vomdate =) then onsetdate = diadate > If diadate =) then onsetdate = vomdate > > Now we have a variables of case and onset date and I created an Epicurv graph using them. It was great. > One more frustration. While we were working on the code we often used browse to check our results. We wrote the browse command into the programme editor but the results of the Browse do not appear in the output so I had to do it over again each time in the output screen. I tried list instead of Browse but this didn't work either. Any suggestions for how you can build the output from a browse or line list command into a programme will be welcome. > > Next posting we will get on to analysing the exposures > > thanks > > Christine > > > -- Hans L Rieder, MD, MPH Jetzikofenstr. 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 321 9122 Web: http://www.tbrieder.org -- The information contained in this email and any attachments is confidential and may be legally privileged. If you have received this message in error, please notify the sender immediately and remove all copies of the message, including any attachments. Any views or opinions expressed in this email (unless otherwise stated) may not represent those of Hutt Valley DHB. Thank you. ** Disclaimer added by HVDHB **

1 1

Epidata analysis on a network with restricted access to c drive
by epidata-list＠lists.umanitoba.ca 08 Jun '08

08 Jun '08

Just a quick question re an issue I have with Epidata analysis and the C drive default directories it uses for some functions. This is the message I get when I load Epidata Analyis * EpiData Analysis default settings file * Edit the next lines to change size or font . set echo=off Access is denied Operation aborted Although I can still use Epidata Analysis I do not get the option to change the settings, I don't see the results of the read command displayed or information about how many records are in the file. I also have to change the default I send the output to as I can not access the default directory. I asked our IT help desk and they say the reason this happens is that I am now allowed access to one of the directories Epidata looks for - an administrator folder in the C drive. I wonder if this might be a problem for others who are in organisations/working on networks where users are not allowed access to administrator folders. Do you have a suggested workaround? thanks Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 >>> <epidata-list-request(a)lists.umanitoba.ca> 7/06/2008 5:04 a.m. >>> 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..." -- The information contained in this email and any attachments is confidential and may be legally privileged. If you have received this message in error, please notify the sender immediately and remove all copies of the message, including any attachments. Any views or opinions expressed in this email (unless otherwise stated) may not represent those of Hutt Valley DHB. Thank you. ** Disclaimer added by HVDHB **

1 0

Outbreak analysis diary - Defining cases as a new variable
by epidata-list＠lists.umanitoba.ca 06 Jun '08

06 Jun '08

Today we started doing the analysis of exposures for our outbreak. First we need to create a new variable, as not everyone who is sick meets the case definition for the outbreak. Case definition Our case definition is someone who has diarrhoea and/or vomiting 24-72 hours after the function. I used the programme editor to define a new variable called Case I made case a Boolean field so the relative risks would calculate correctly (with a Boolean field the Y appears first in a two by two table and then the N and this is what you want to calculate relative risks correctly). Diarrhoea and Vomit - the fields I needed to create the Case field were also Booklean fields. For a long time I had a problem as I was trying many combinations of If Diarrhoea = Yes or Y or "Y" in my code and it was not working. Then my workmate suggested I try TRUE. I think this is confusing as when you print a Frequency of a boolean Field it prints as Y. Anyway here was the code that worked. Define case <Y> If Diarrhoea = TRUE or Vomit = TRUE then case = TRUE This deals with the first part of the case definition - that they must have diarrhoea or vomiting. The next part is that they are NOT a case if the symptoms started on the same day. The code I ended up using for this was IF onsetdate <= date("24/05/2008") then case = FALSE. I had to put the date function as well as the date itself or the code would not run. I don't know why that is but any other combination I tried like "24/05/2008" or 24/05/2008 or ("24/05/2008") did not work. Onsetdate In the last post I asked if anyone had some code to create a single onset date from two pieces of information - the vomitdate and the diarrhoea date. My workmate helped me figure out something that worked and this is it. If diadate < vomdate then onsetdate = diadate If vomdate < diadate then onsetdate = vomdate If vomdate =diadate then onsetdate = diadate If vomdate =(.) then onsetdate = diadate If diadate =(.) then onsetdate = vomdate Now we have a variables of case and onset date and I created an Epicurv graph using them. It was great. One more frustration. While we were working on the code we often used browse to check our results. We wrote the browse command into the programme editor but the results of the Browse do not appear in the output so I had to do it over again each time in the output screen. I tried list instead of Browse but this didn't work either. Any suggestions for how you can build the output from a browse or line list command into a programme will be welcome. Next posting we will get on to analysing the exposures thanks Christine -- The information contained in this email and any attachments is confidential and may be legally privileged. If you have received this message in error, please notify the sender immediately and remove all copies of the message, including any attachments. Any views or opinions expressed in this email (unless otherwise stated) may not represent those of Hutt Valley DHB. Thank you. ** Disclaimer added by HVDHB **

1 2

re: ongoing outbreak
by epidata-list＠lists.umanitoba.ca 05 Jun '08

05 Jun '08

I think this opportunity for open sharing of ideas and experiences is very good and unique In general I discourage the use of boolean variables. In particular since these in many softwares can have only the values true (Y) or false (N), and not the value "no value". With the introduction of value labels it is far more efficient to use integer variables, e.g. for the current outbreak: qes file food items intaken : v1 food item 1 (e.g. soup) # v2 food item 2 (e.g. vanilla icecream) # etc Preparation of chk file is then easy. 1. add checks (#3 in entry) 2. define a value label (+) for v1: 0 no 1 yes 9 missing 3. further define "9" as missing for v1: F9 (edit) and add missingvalue all 9 3. after defining that go to field 1 and press ctrl+c 4. go to v2 (and all other food items) and press ctrl+v now all fields have 0 and 1 defined and 9 as missing value. 5. enter your data 6 read data into analysis define cases: strategy 1: define case # case = 0 if (vomiting = 1) then case = 1 * remove those vomiting before 24 hours or after 72 hours if (vomiting=1) and (hourvomit < 24) then case = 0 if (vomiting=1) and (hourvomit > 72) then case = 0 * alternatively if we have a fixed date of exposure on 21st of may) if (vomiting=1) and (datevomit < dmy(22,5,2008) then case = 0 if (vomiting=1) and (datevomit > dmy(24,5,2008) then case = 0 * all with diarrhoea are cases: if (diarrhoea = 1) then case = 1 * date of symptoms: define dateonset <dd/mm/yyyy> If diadate < vomdate then onsetdate = diadate If vomdate < diadate then onsetdate = vomdate If vomdate =diadate then onsetdate = diadate If vomdate =(.) then onsetdate = diadate If diadate =(.) then onsetdate = vomdate * now we are ready for the first simple analysis: tab case v1 v2 v3 .... etc - all exposure variables..... /oa /t epicurve onsetdate case epicurve onsetdate case /by=sex The problems reported the latest days, such as: using boolean variables changing from string to numerical etc. a Can be handled by combining entry and analysis - as was shown on the list by others: a. rewrite the qes file and some conversions are done by EpiData Entry when possible b. take the file into analysis - generate the new numerical variables, e.g. gen i v1 = (upper(v1string) = "Y") c. save the data (savedata newfile) d. with entry create a qes file from the rec file (in Entry - menu tools) e. change the format and labels in qes file and save the qes file f. enter more data - entry will see that the qes file is new and adapt format of rec file. But the best strategy is to have a standard qes file and rec file from the beginning and then adapt to the current outbreak. Two examples of this is shown in the "field guide under way" in http://www.epidata.org/wiki/index.php/Field_Guide Exciting to get more news on the ongoing analysis "down under" (seen from my perspective). regards Jens Lauritsen EpiData Association

1 1

Outbreak analysis diary - Symptoms and Epicurves
by epidata-list＠lists.umanitoba.ca 04 Jun '08

04 Jun '08

Today I am trying to see if I can use Epidata Analysis to do the first three analysis tasks. 1. How many people are sick 2. What is the symptoms profile 3. Epidemic curve Tasks 1 and 2 are nice and easy. a) click Analysis b) Click on Frequency c) Select Sick from the Select Variable Menu d) Tick row percentages I can do the same with the symptoms profile (Diarrhoea, Vomiting etc) What I don't like is the no comes first on the table that is produced, even though it is a Boolean field. What would be on my 'wish list' is if all the symptoms I select could appear in the one table as exposures do when you select outbreak analysis for attack rates Epidemic Curve The epidemic curve starts badly. I start by asking for a histogram of diadate (date of onset of diarrhoea) and even though this is a date field (and shows as dates if I do a frequency) the graph shows 76115, 76116 etc on the X axis instead of 27/05/2008, 28/05/2008. Then I remember there is an 'epicurve' graph and this works well. I would like to be able to show diatime on there as well (time of day people were sick) but remember this is not possible yet. Never mind - dates will do for now. My question for today is - can someone help with some code to create a single onset date? There are two variables - one called diadate and one called vomitdate - the onset date should be whichever one of these is the earliest. We could calculate this manually but it would be great if we could build it in to either epidata (we still have at least 100 records to enter that check code could help with) or epi analysis Thanks Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 >>> <epidata-list-request(a)lists.umanitoba.ca> 27/05/2008 5:04 a.m. >>> 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..." -- The information contained in this email and any attachments is confidential and may be legally privileged. If you have received this message in error, please notify the sender immediately and remove all copies of the message, including any attachments. Any views or opinions expressed in this email (unless otherwise stated) may not represent those of Hutt Valley DHB. Thank you. ** Disclaimer added by HVDHB **

1 0

Outbreak analysis with Epidata Analysis diary - 1 Data issues - text to Boolean
by epidata-list＠lists.umanitoba.ca 04 Jun '08

04 Jun '08

We have an outbreak to deal with. Up to several hundred people are possiblly sick after attending a local sports venue that also hosts children's birthday parties. Like many outbreaks it comes at a difficult time (they seem to love happening on Christmas Eve or the day before Easter). This one we learn about the day before a holiday weekend and I have the day off the next day. Someone has designed a questionnaire asking our usual questions (Demographics, symptoms and exposures) and the phone calls have already started. I help someone create an Epidata questionnaire to enter the data and promise to help with the analysis on my return. There are two main things we have to do in our outbreak analysis 1. Describe the pattern of illness by person place and time (how many people are sick with what symptoms, when did they get sick and for how long) 2. Discover if certain 'exposures' - e.g. eating certain foods are associated with illness. Today I come back and find I have a problem I must fix before we start the analysis. My workmate has changed my file so all the Boolean fields I used to record the exposure information are now text fields. (She did this because she wanted to be able to put "U" for unknown. I explain we need the data in Boolean fields for our two by table analysis and if the answer is unknown to leave the field blank. She has entered 66 records already so I have a problem - how do I change the data from text to Boolean as changing a field type in Epidata from text to Boolean would lose all the data? The way I work out is: (using the example outbreak.rec for the file that has data entered as text) 1. Use Save as with outbreak.qes to make a new file called outbreak2.qes. Change this file so the txt fields are now boolean fields 2. Create a new blank rec file from outbreak2.qes called outbreak2.rec 3. Export outbreak.rec to Excel as outbreak2.xls 4. Use search and replace to change the Y, N and U that have been entered to 1,0 and blank 5. Save Outbreak.xls to a text file outbreak2.csv (CSV) 6. Import outbreak2.csv as a text file ticking the option to not use first line. This 'pulls' the data into outbreak2.rec and the boolean fields with the 1 and 0 showing as Yes and No This seems a long way round so maybe someone has a better way to fix this problem? Next posting I will start with the analysis thanks Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 >>> <epidata-list-request(a)lists.umanitoba.ca> 26/05/2008 5:01 a.m. >>> 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..." -- The information contained in this email and any attachments is confidential and may be legally privileged. If you have received this message in error, please notify the sender immediately and remove all copies of the message, including any attachments. Any views or opinions expressed in this email (unless otherwise stated) may not represent those of Hutt Valley DHB. Thank you. ** Disclaimer added by HVDHB **

1 0

Outbreak analysis with Epidata Analysis diary
by epidata-list＠lists.umanitoba.ca 04 Jun '08

04 Jun '08

I use Epidata to help with the analysis of outbreaks of communicable disease. Up until now I have used Epidata to design the questionnaires and enter the data and Epi info to analyse the data, but for the last outbreak I used Epidata Analysis to do some of the analysis (to produce the attack rate table). This was much better than using epi info. I told Jens I might try using Epidata analysis for all the outbreak analysis in the future and he suggested I write some short notes about what I do, and post them to the list as the basis for a future field guide. We now have a brand new outbreak to analyse so I will do this and hope you will contribute with comments and suggestions if you do similar tasks or are interested. Thanks Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 >>> <epidata-list-request(a)lists.umanitoba.ca> 26/05/2008 5:01 a.m. >>> 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..." -- The information contained in this email and any attachments is confidential and may be legally privileged. If you have received this message in error, please notify the sender immediately and remove all copies of the message, including any attachments. Any views or opinions expressed in this email (unless otherwise stated) may not represent those of Hutt Valley DHB. Thank you. ** Disclaimer added by HVDHB **

1 0

Re: EpiData-list Digest, Vol 55, Issue 19 Missing values is not NA
by epidata-list＠lists.umanitoba.ca 29 May '08

29 May '08

Dear friend Ziad, NA is common expression to identify missing values. If you are working with R or S-Plus then NA is NA. That means that all functions or commands that you want to specify NA, the expression is also NA. However, in Stata or Epidata entry the NAs are epecified by dots (.) and sometimes by empty quotes (" ") depending if the variable of interest is formated as numeric or text. So, my guess is that your check command will work fine if do like this... AFTER ENTRY IF v64=. THEN LET V65=9 & V66=9 & goto V67 ENDIF END Best regards, Pedro Emmanuel > Today's Topics: > > 1. If..then (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 28 May 2008 08:47:34 -0700 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] If..then > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <897a5cf60805280847u3b99c66ak6f49e3855b879141(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi, > might be easy question, i am trying to write condition under check > file to write value of 9 in 2 places if one cell equal to NA (code > below), it does not work (and no error message), any tips? > > AFTER ENTRY > IF v64=NA THEN > LET V65=9 & V66=9 & goto V67 > ENDIF > > > Thank you in advance > best regards > ziad > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 55, Issue 19 > ******************************************** >

1 0

re: If..then
by epidata-list＠lists.umanitoba.ca 28 May '08

28 May '08

Just split in three lines: after entry IF v64=NA THEN LET V65=9 V66=9 goto V67 ENDIF regards Jens Lauritsen EpiData Association

1 0

Epidata Analysis and diagnostic test accuracy analysis
by epidata-list＠lists.umanitoba.ca 27 May '08

27 May '08

Hi all, I did look at epidata website but for any unknown reasean I could not find the pdf manual of EpiData analysis. I use a lot the epidata entry but neve tryed before the analysis. I would like to know if any of you could tell me if EpiData analysis has resources to analyse diagnostic test accuracy such as sensitivity, specificity (and theses estimates in different prevalences), estimate the area under the ROC curve, draw ROC curves, compare ROC curves form different tests? I also did try to download/install the software and look for theses abilaties, but here at the institute where I work none of the users are coputers administrator (security reasons) and install "non standart softwares" is just not that simple! Thanks a lot in advance! -- Abraço forte e que a força esteja com você, Pedro Emmanuel

1 1

Re: [EpiData-list] Program simulated data in EpiData (Analysis)
by epidata-list＠lists.umanitoba.ca 25 May '08

25 May '08

Greetings SK, [This may be a repeat -- first posting didn't seem to get through] I like to use a little program by Christian Maas to generate data, Random file generator from: http://www.chmaas.handshake.de/delphi/freeware/freeware.htm The command line version can be run from a BAT file containing a statement such as: RndFileC.exe /R=50000 /Z=YYYY/MM/DD /N=4 /F=1,@ /C=15 /F=1,, /B /C=1 /S=14 /B /C=1 /S=14 /F=1,@ /Y=1945,2003 data.txt For example, this generates 50,000 records with the given date format and range, plus other fields. Then import into EpiData. I prefer to set up the EpiData files, enter a few records, and then export them to a CSV file; then make sure you use the same format to generate the random records to import back into EpiData. I have use Maas's program to generate 8,000,000 records (but not this number for EpiData; this was data to analyze using gawk in GNU/Linux). The sort program is real nice, too. Hope this helps, Pete Geddes geddes(a)ix.netcom.com ----- Original Message --------------- Subject: [EpiData-list] Program simulated data in EpiData (Analysis) From: epidata-list(a)lists.umanitoba.ca Date: Sun, 25 May 2008 09:38:58 -0400 To: epidata-list(a)lists.umanitoba.ca > >Dear All > >I was wondering if EpiData Analysis could do simulations: here is what I am contemplating doing; I have created a database of admissions/discharges from a hospital using a standardized register and using EpiData as the software for data entry and ana;ysis. I wish to populate the fields (15 in total, of various types: boolean, categorical with k values, numeric, and date fields) I have created with say N=5,000 observations. The reason I wish to do this is to show the stakeholders (in this case Hospital Managers and Unit Heads) that one could use simple yet effective data entry and analysis software (like EpiData) to monitor and evaluate hospital-based programs. I wanted them to see EpiData in action with the simulated data--starting with EpiData Entry and then with Analysis. > > > >Can simulation be done in Analysis? or should I prepare the dataset with Stata or SAS and then import in EpiData--I am not sure how to do this, but I will search around to see how to get it done? > > > >Thanks, > >SK >

1 0

How to: Simulation with EpiData Analysis
by epidata-list＠lists.umanitoba.ca 25 May '08

25 May '08

Simulation for entry is not that easy. But some tests have been done with "recording software". The results of this could be uploaded if there is an interest. Simulation for analysis is rather simple. The simplest way is: close * generate x empty observations, e.g. 1000: generate 1000 * then generate the variables: e,g, integer sex: gen i sex = 1 if recnumber > 499 then sex = 0 .... continue with other variables. * look also in the help file for: random functions. The extended way is to use the user specified commands. For explanation of this see: The documentation page or the direct download link at: http://www.epidata.dk/php/downloadc.php?file=cmd_command_epidata_analysis.p… Kind regards Jens Lauritsen EpiData Association

1 0

Program simulated data in EpiData (Analysis)
by epidata-list＠lists.umanitoba.ca 25 May '08

25 May '08

Dear All I was wondering if EpiData Analysis could do simulations: here is what I am contemplating doing; I have created a database of admissions/discharges from a hospital using a standardized register and using EpiData as the software for data entry and ana;ysis. I wish to populate the fields (15 in total, of various types: boolean, categorical with k values, numeric, and date fields) I have created with say N=5,000 observations. The reason I wish to do this is to show the stakeholders (in this case Hospital Managers and Unit Heads) that one could use simple yet effective data entry and analysis software (like EpiData) to monitor and evaluate hospital-based programs. I wanted them to see EpiData in action with the simulated data--starting with EpiData Entry and then with Analysis. Can simulation be done in Analysis? or should I prepare the dataset with Stata or SAS and then import in EpiData--I am not sure how to do this, but I will search around to see how to get it done? Thanks, SK

1 1

Default values in boolean fields
by epidata-list＠lists.umanitoba.ca 22 May '08

22 May '08

The simplest solution for default values is to use the chk command "Defaultvalue" Further explanation is shown in the help file. eg qes: v1 my boolean variable <y> v2 ....... etc chk v1 defaultvalue 0 end regards Jens Lauritsen

1 0

improvised checkboxes
by epidata-list＠lists.umanitoba.ca 21 May '08

21 May '08

I understand that epiData does not have checkboxes as such. Therefore the boolean fieldtype is suggested. In order to save time when entering data for certain variables, I would like to have epiData automatically write N, if nothing is entered. Otherwise all dummy variables are created as missing, unless I type "0" or "N" in each field. Is there a way to do this automatically? I already tried MISSINGVALUE N or MISSINGVALUE 0 and AFTER RECORD IF saaadr = . THEN saaadr=0 ENDIF END but unfortunately with no result. Thanks in advance for any suggestion. Marius _________________________________________________________________ News, entertainment and everything you care about at Live.com. Get it now! http://www.live.com/getstarted.aspx

1 1

Alyshia Landry is out of the office.
by epidata-list＠lists.umanitoba.ca 16 May '08

16 May '08

I will be out of the office starting 05/16/2008 and will not return until 05/20/2008. If you require immediate assistance, please contact Celina Sousa at extension 5300. Thank-you and have a nice weekend, Alyshia

1 0

Error Message on Values Labels
by epidata-list＠lists.umanitoba.ca 16 May '08

16 May '08

Susan Caplan wrote: 'When I try to enter a string under value label LABEL Label_hablaespan 1 espanol 2 mayormente espanol 3 espanol e ingles igual 4 mayormente ingles 5 ingles solamente END It says Missing label for one or more accepted values. ' Yes, you will get such an error message because some of your value labels have more than one word. When your value label has more than one word, you should use quotes as shown below: LABEL Label_hablaespan 1 espanol 2 "mayormente espanol" 3 "espanol e ingles igual" 4 "mayormente ingles" 5 "ingles solamente" END Also, you don't use legal values and label blocks at the same time. Regards, Biggie, Maseru, Lesotho --------------------------------- Sent from Yahoo! Mail. A Smarter Email.

1 0

Res: EpiData-list Digest, Vol 55, Issue 11
by epidata-list＠lists.umanitoba.ca 15 May '08

15 May '08

Hi Susan Did you try " " ? 1 espanol 2 "mayormente espanol" 3 "espanol e ingles igual" 4 "mayormente ingles" 5 "ingles solamente" Hope this help, Fúlvio Porto Alegre - Brasil ----- Mensagem original ---- De: "epidata-list-request(a)lists.umanitoba.ca" <epidata-list-request(a)lists.umanitoba.ca> Para: epidata-list(a)lists.umanitoba.ca Enviadas: Quinta-feira, 15 de Maio de 2008 14:01:57 Assunto: EpiData-list Digest, Vol 55, Issue 11 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. value labels error message (epidata-list(a)lists.umanitoba.ca) 2. legal use? (epidata-list(a)lists.umanitoba.ca) 3. combined numeric text variable (epidata-list(a)lists.umanitoba.ca) 4. Re: combined numeric text variable (epidata-list(a)lists.umanitoba.ca) 5. Re: legal use? (epidata-list(a)lists.umanitoba.ca) 6. Re: value labels error message (epidata-list(a)lists.umanitoba.ca) ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list When I try to enter a string under “value label” LABEL Label_hablaespan 1 espanol 2 mayormente espanol 3 espanol e ingles igual 4 mayormente ingles 5 ingles solamente END It says “Missing label for one or more accepted values.” I have tried entering legal values 1-5 and/or omitting values, but I still get this message, which I don’t know how to correct. Susan Caplan Message recieved: The check file C:\Documents and Settings\Susan Caplan\My Documents\database diss\databaseimmigrant.chk contains the following errors: Value is not compatible with this field type in line 33: COMMENT LEGAL USE label_dm2 Value is not compatible with this field type in line 46: COMMENT LEGAL USE label_dm4 LABELBLOCK LABEL label_dm2 lang pref 1. Spanish 2. English END LABEL label_dm4 1. nuevo 2. previa END 1) What is wrong with the field types in the above variables? 2) The above message continues repeating and I am not allowed to edit/revise checks, but must clear all checks to get back into check dialogue Susan I want to create a variable that is numeric ## and text ___________________________ for a fill in response such as “other”. However, a combination of text and numeric within the same variable creates two variables. For statistical purposes I don’t want to opt for text only. Suggestions? Susan Caplan, RN, MSN, FNP-BC Yale University PhD Student in Nursing Susan - glad to see you are using EpiData. I think you just need to look at some of the sample files to get over the initial step of learning some of the syntax. You cannot create a variable of mixed type (##____________). This will always create two variables and this is how you need to set up your file. Although programs like Access will let you create patterns for data entry, they will not let you create mixed type variables. You will find that EpiData has huge advantages. I suggest you just set up your data entry line as follows somevar ##__________________________ EpiData creates two fields (variables), named "somevar" and "somevar01" - may vary depending on your settings. This is actually exactly what you want. You can then set a range or legal values on the ## field to be sure the entry is correct. If you need to combine them into one at some point, this is very easy in EpiData or any other software. In your other postings, there are a couple of things to watch out for - these are explained in the short introduction file. 1) In the check file, text that has any spaces or other special characters must be put into regular quotes 3 "espanol e ingles igual" 2) If your entry field is ##, do not use decimal points in the range or legal values LABEL label_dm2 lang pref 1 Spanish 2 English END While a number of us will be glad to offer help as you get started, I encourage you to look at examples, at the list serv archives and at all of the help files for guidance. Jamie > I want to create a variable that is numeric ## and text > ___________________________ for a fill in response such as “other”. However, a > combination of text and numeric within the same variable creates two variables. > For statistical purposes I don’t want to opt for text only. Suggestions? > > > Susan Caplan, RN, MSN, FNP-BC > Yale University > PhD Student in Nursing 1) The line. lang pref should be marked as a comment with a * sign at the begin of the line 2) the dot after the numbers should be removed. check file : LABELBLOCK LABEL label_dm2 1 Spanish 2 English END LABEL label_dm4 1 nuevo 2 previa END END The type of dm2 and dm4 must be integer of size 1 (#) > Message recieved: > > The check file C:\Documents and Settings\Susan Caplan\My Documents\database > diss\databaseimmigrant.chk contains the following errors: > > > > Value is not compatible with this field type in line 33: > COMMENT LEGAL USE label_dm2 > > Value is not compatible with this field type in line 46: > COMMENT LEGAL USE label_dm4 > > > LABELBLOCK > LABEL label_dm2 > lang pref > 1. Spanish > 2. English > END > LABEL label_dm4 > 1. nuevo > 2. previa > END > > 1) What is wrong with the field types in the above variables? > 2) The above message continues repeating and I am not allowed to edit/revise > checks, but must clear all checks to get back into check dialogue > > > > Susan > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > -- Jean-Marie Chrétien CHU d'Angers - Centre de Recherche Clinique 4 rue Larrey 49933 ANGERS Cedex 9 Tel : 02.41.35.59.76 Fax : 02.41.35.59.68 Dear Susan, You must enclose your labels with double quotes when they contains spaces: 2 "mayormente espanol" ... Jean-Marie Chrétien > When I try to enter a string under “value label” LABEL Label_hablaespan > 1 espanol > 2 mayormente espanol > 3 espanol e ingles igual > 4 mayormente ingles > 5 ingles solamente > END > > It says “Missing label for one or more accepted values.” I have tried entering > legal values 1-5 and/or omitting values, but I still get this message, which I > don’t know how to correct. > > > Susan Caplan > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > -- Jean-Marie Chrétien CHU d'Angers - Centre de Recherche Clinique 4 rue Larrey 49933 ANGERS Cedex 9 Tel : 02.41.35.59.76 Fax : 02.41.35.59.68 Abra sua conta no Yahoo! Mail, o único sem limite de espaço para armazenamento! http://br.mail.yahoo.com/

1 0

legal use?
by epidata-list＠lists.umanitoba.ca 15 May '08

15 May '08

Message recieved: The check file C:\Documents and Settings\Susan Caplan\My Documents\database diss\databaseimmigrant.chk contains the following errors: Value is not compatible with this field type in line 33: COMMENT LEGAL USE label_dm2 Value is not compatible with this field type in line 46: COMMENT LEGAL USE label_dm4 LABELBLOCK LABEL label_dm2 lang pref 1. Spanish 2. English END LABEL label_dm4 1. nuevo 2. previa END 1) What is wrong with the field types in the above variables? 2) The above message continues repeating and I am not allowed to edit/revise checks, but must clear all checks to get back into check dialogue Susan

1 1

value labels error message
by epidata-list＠lists.umanitoba.ca 15 May '08

15 May '08

When I try to enter a string under value label LABEL Label_hablaespan 1 espanol 2 mayormente espanol 3 espanol e ingles igual 4 mayormente ingles 5 ingles solamente END It says Missing label for one or more accepted values. I have tried entering legal values 1-5 and/or omitting values, but I still get this message, which I dont know how to correct. Susan Caplan

1 1

combined numeric text variable
by epidata-list＠lists.umanitoba.ca 14 May '08

14 May '08

I want to create a variable that is numeric ## and text ___________________________ for a fill in response such as other. However, a combination of text and numeric within the same variable creates two variables. For statistical purposes I dont want to opt for text only. Suggestions? Susan Caplan, RN, MSN, FNP-BC Yale University PhD Student in Nursing

1 1

AW: EpiData-list Digest, Vol 55, Issue 6 - EpiData und Linux
by epidata-list＠lists.umanitoba.ca 13 May '08

13 May '08

Dear Mr. Lauritsen, i can test EpiData-Linux with GNU/Debian Linux 4.0r3. Yours sincerley, Dirk Cremer Stadt Bielefeld - Der Oberbürgermeister - Gesundheits-, Veterinär- & Lebensmittelüberwachungsamt Nikolaus-Dürkopp-Str. 5-9 33597 Bielefeld http://www.bielefeld.de (bitte Gesundheitsberichterstattung in die Suchfunktion eingeben) Auskunft gibt Ihnen: Dirk Cremer Gesundheitsberichterstattung Raum 217 Tel.: 0521 51-5022 Fax: 0521 51-3406 -----Ursprüngliche Nachricht----- Von: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] Im Auftrag von epidata-list-request(a)lists.umanitoba.ca Gesendet: Mittwoch, 7. Mai 2008 19:11 An: epidata-list(a)lists.umanitoba.ca Betreff: EpiData-list Digest, Vol 55, Issue 6 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. RE: EpiData-list Digest, Vol 55, Issue 5 (epidata-list(a)lists.umanitoba.ca) 2. Date time combinations in epicurves (epidata-list(a)lists.umanitoba.ca) 3. Using attack rate table output in reports (epidata-list(a)lists.umanitoba.ca) 4. EpiData and linux (epidata-list(a)lists.umanitoba.ca) 5. Re: EpiData and linux (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Tue, 6 May 2008 20:29:14 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] RE: EpiData-list Digest, Vol 55, Issue 5 To: <epidata-list(a)lists.umanitoba.ca> Message-ID: <30123C01C7D6EE46B6AAA1B1772331971E1447(a)491-mail.mrcad.mrc.ac.za> Content-Type: text/plain; charset="iso-8859-1" You are absolutely correct, once a duplicated number is entered, it will pop up "Number already exists, do you want to go to record????? As long as you type "key Unique 1" A Key Unique number can be altered if it was entered by mistake but if you select the ID as AUTO select, then that number which is generated by the computer can not be altered. Sandy MRC (South Africa) -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list-request(a)lists.umanitoba.ca Sent: 06 May 2008 07:02 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 55, Issue 5 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. Re: Re: EpiData-list Digest, Vol 55, Issue 3 Unique ID number (epidata-list(a)lists.umanitoba.ca) 2. Epidata with Ubuntu gusty (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Mon, 05 May 2008 19:16:22 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] Re: EpiData-list Digest, Vol 55, Issue 3 Unique ID number To: epidata-list(a)lists.umanitoba.ca Message-ID: <481F40E6.4090109(a)tbrieder.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Pedro: Am I incorrect in opinionating that actually KEY UNIQUE gives you all answers as well, that an identifier value is already in existence and in which record it is and allowing you to go to precisely that previous record. Hans epidata-list(a)lists.umanitoba.ca wrote: > Gilles, > > All the anterior answers are correct. Hoewever I have a preference for > another command: > > idnumber > autosearch list > end > > This command does not exactly the same thing as key unique. I have > this preference because key unique does not allow U to enter a > previous entered number and does not warn you which record this number > is. Autoserach warns that this number is already in the dataset and > gives you the option to edit this one or to generate a new one. This > is handy when the mistake is in the first one. > For example... suppose you are entering data of questionnaire number > 12, but by mistake you enter 22 at the ID number. When you get on 22, > key unique only tells you U cant enter 22, becasue it is already in > the databank. Autosearch list will show you the record with ID 22 for > you to compare and see if this is the same you entering and allow you > to go to this > 22 and change it to 12 if necessary. > > Also, you may use them both at the same check if u like ... > > id > key unique > autosearch list > end > > Best regards, > Pedro Emmanuel > ------------------------------ Message: 2 Date: Mon, 5 May 2008 22:48:48 -0300 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Epidata with Ubuntu gusty To: epidata-list(a)lists.umanitoba.ca Message-ID: <a37cfb5a0805051848m3464cc07x658fc4e4946d9157(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Hello all, I tryed to install Epidata in Ubuntu today and it seems to work fine at first. I looked at the web page and old messages at the list but latest one were from 2004. The installation looked pretty simlpe with wine already installed. Just click on it and wine seems to do the rest. Choose the directory as in windows .... press continue... At first it seems a little weird ... the installation and the program were not in portuguese but in english. There is a lot of violations errors when opening and closing files and sometimes epidata just dont open the files. Some simple commands in windows such as Ctrl+Z dont work. I try to import a simple dataset from a csv file with 6 variables and 45 observations and the same error did not allow me to complete the import.... the ID variable is not compatible. The ID variable was a number from 1 to 45. I try even to delete some variables eand most of observations to make it simple but it didnt work out. Does anyone have recent experiences with Epidata in Linux? Good or bad? -- Abraço forte e que a força esteja com você, Pedro Emmanuel ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 55, Issue 5 ******************************************* ------------------------------ Message: 2 Date: Wed, 07 May 2008 08:20:35 +1200 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Date time combinations in epicurves To: <epidata-list(a)lists.umanitoba.ca> Message-ID: <001d01c8af63$0f2698f0$663b4979@acerc6bac00326> Content-Type: text/plain; charset=US-ASCII I saw an earlier thread on the list suggesting a date time variable in epi analysis or the option to show two variables such as day and hours in an epicurve. I would find this very helpful as for an outbreak I was asked to produce an epi curve, preferably grouped in 3 hourly lots, but certainly showing both date and hour of onset on one graph. The outbreak data was entered into Epidata and as Epidata doesn't have a datetime field information about when people first became sick was stored in two different fields - onsetday (a date field) and onsettime (a numeric field entered as a 24 hour clock). There are three different onset days and a range of onsettimes in each day. I couldn't think of a way of putting both pieces of information on one graph in either epidata analysis or epi info (though in epi info you can group the hours and it will make you a different graph for each day), so finally I exported the data to Excel, grouped the data manually and then graphed it that way. Does anyone have a better suggestion about how to make an epicurv that includes both date and time information? thanks Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 -- The information contained in this email and any attachments is confidential and may be legally privileged. If you have received this message in error, please notify the sender immediately and remove all copies of the message, including any attachments. Any views or opinions expressed in this email (unless otherwise stated) may not represent those of Hutt Valley DHB. Thank you. ** Disclaimer added by HVDHB ** ------------------------------ Message: 3 Date: Wed, 07 May 2008 08:19:05 +1200 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Using attack rate table output in reports To: <epidata-list(a)lists.umanitoba.ca> Message-ID: <001d01c8af63$0f2698f0$663b4979@acerc6bac00326> Content-Type: text/plain; charset=US-ASCII First to say how great the outbreak analysis option is in Epi analysis. Instead of slowly cutting and pasting or copying information from a whole series of 2 by 2 tables as in Epi Info as I used to, I can now quickly create an attack rate table with for all exposures of interest including not just attack rates in the exposed and unexposed, but relative risks, p values and confidence intervals though that one command. I am helping analyse an outbreak at the moment and it has saved me lots of time, thank you very much. I am still learning about working with the output though, so what I am interested to learn from others is if you are using epi analysis attack rate output table in reports written in microsoft word and if so how. I was asked to provide the table in a version that could be incorporated in a write up about the outbreak to be written in MS word . My method was to 1. open microsoft word 2. chose insert file (making sure all files option was selected) 3. Insert the epianalysis htm file containing the table 4. Use table/select table and autoformat/grid 5. Do a small amount of re-formating This resulted in a table that looked OK in an MS word document - but is there a better way to do it? Also how do you change the default filename and path from EAoutput.htm to something else? I have another question about the epicurv but will email separately thanks Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 -- The information contained in this email and any attachments is confidential and may be legally privileged. If you have received this message in error, please notify the sender immediately and remove all copies of the message, including any attachments. Any views or opinions expressed in this email (unless otherwise stated) may not represent those of Hutt Valley DHB. Thank you. ** Disclaimer added by HVDHB ** ------------------------------ Message: 4 Date: Wed, 07 May 2008 17:07:54 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] EpiData and linux To: epidata-list(a)lists.umanitoba.ca Message-ID: <4821C5CA.2070107(a)epidata.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed It would be good to form a kind of "EpiData Linux group" - I have allocated some of the development funding for getting into "linux". This is expected to start mid 2008. If we are to be succesfull it is of utmost importance, that some key users in each operating system will take part of the testing etc. Therefore the question yesterday on experiences comes in very handy, since the experiences will be part of "how and what to consider", when converting EpiData Entry from a "windows only" to a "multiplatform software". regards Jens Lauritsen EpiData Association ------------------------------ Message: 5 Date: Wed, 07 May 2008 11:32:41 -0500 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] EpiData and linux To: epidata-list(a)lists.umanitoba.ca Message-ID: <4821D9A9.2040102(a)binghamton.edu> Content-Type: text/plain; charset=ISO-8859-1 I would love to test a version of EpiData on Linux. I use Kanotix, a Debian-based distro. Sadly, I have no coding skills to contribute. --Chris Christopher W. Ryan, MD SUNY Upstate Medical University Clinical Campus at Binghamton 40 Arch Street, Johnson City, NY 13790 cryanatbinghamtondotedu PGP public keys available at http://home.stny.rr.com/ryancw/ "If you want to build a ship, don't drum up the men to gather wood, divide the work and give orders. Instead, teach them to yearn for the vast and endless sea." [Antoine de St. Exupery] epidata-list(a)lists.umanitoba.ca wrote: > It would be good to form a kind of "EpiData Linux group" - > > I have allocated some of the development funding for getting into "linux". > > This is expected to start mid 2008. If we are to be succesfull it is of > utmost importance, that some key users in each operating system will > take part of the testing etc. > > Therefore the question yesterday on experiences comes in very handy, > since the experiences will be part of "how and what to consider", when > converting EpiData Entry from a "windows only" to a "multiplatform > software". > > regards > > Jens Lauritsen > EpiData Association > > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 55, Issue 6 *******************************************

1 0

Attachments on EpiDatalist - do not use.
by epidata-list＠lists.umanitoba.ca 09 May '08

09 May '08

The EpiData list is planned as a "list without attachments". The problem of attachments is that sometimes they work only if users have certain software. (Apart from EpiData software). In general all attachments will be stripped (deleted), but sometimes the filters for this are not sufficient. The advice for users is to: A. Send mail as TEXT only mail to the list B. Try to generalise the statements in standard text C. Keep volumen low, since with slow internet connections the contents gets to be a problem. There is a limit on size in the list. If we run into problems I might change the limit (up or down). In other words. Attachments gives different users problems. So please send your questions as ordinary text only. Extended documentation or files can be the user be uploaded to that users own website. And then in the posting to the list refer to that site, where the file is placed. regards Jens Lauritsen EpiData Association

1 0

value labels
by epidata-list＠lists.umanitoba.ca 09 May '08

09 May '08

Please see attachment.

1 1

How to: Time variables and Epicurves (grouping by hours)
by epidata-list＠lists.umanitoba.ca 07 May '08

07 May '08

Christine asked how to create efficient epicurves with an X axis grouping in time intervals. I think the efficient way would be to change your date/time variables into hours since observation or a given day. Then cut the x-axis and work a bit on labelling. That might sound easier than done (would take some time of experimentation). But for the development plan I think we should consider adding easier ways of doing that. E.g. to allow epicurve to scale the axis with different groupings, but also to find ways of managing time/date situations. Some hints to the solution could be along these lines - A test could be: variables: dateonset : date of first symptom timeonset: hour at which the symptom came on that date (say the observations start on 1st of May this year) case: at least one positive symptom * generate 50 test observations and an epicurve grouped by 3: Close generate 50 gen d dateonset=dmy(1,5,2008)+(recnumber mod 3) gen i timeonset = 24 mod recnumber gen i timevar = 24*(dateonset - dmy(1,5,2008)) + timeonset gen i case = recnumber mod 2 * epicurve by hour would then be epicurve timevar case * recode hours to grouped hours by 3: define time3 ### recode timevar to time3 by 3 tab time3 * show epicurve: epicurve time3 case /xinc=3 /ti="Epicurve for ..... cases in 3 hour groups since start" Notice that the time3 variable will have labels, but currently these are not added to the graph. But for just showing the graph the lines would work. regards Jens Lauritsen EpiData Association

1 0

Copying tables and graphs from analysis to a report
by epidata-list＠lists.umanitoba.ca 07 May '08

07 May '08

1. manipulating file names and positions. The output saved by command "openlog" can be placed anywhere, include the path you like, e.g.: logclose logopen "f:\australia\outbreak\first attempt\logfile 1.htm" 2. Copying graphs from output: To get graphs from output can be done in several ways: a1. produce a single graph. b1 switch to an open "other application", e.g. textprocessing. press ctrl+v (and the graph as added as a wmf editable file) a2. point at a graph in output with the mouse. b2. right click on that graph and "copy to clipboard" c2. switch to the other application and press : Ctrl+V the graph is added as a bmp file (non-editable) a3. produce the graph and add the /save="Myfile" option You can specify graph format with a set command. 3. Copy tables: a. produce a table in output. b. add en empty line at the bottom of the screen by putting a period "." in the command prompt and pressing enter c. mark the table from the command to the line after the table as a block d. right click within the block. e. Choose either "copy as text" or "copy as html". f. Switch to other application and press ctrl+V (or insert special). with text you get tab delimited text copied, with html a formatted table (if the recipient can take in such a table) regards Jens Lauritsen EpiData Association

1 0

EpiData and linux
by epidata-list＠lists.umanitoba.ca 07 May '08

07 May '08

It would be good to form a kind of "EpiData Linux group" - I have allocated some of the development funding for getting into "linux". This is expected to start mid 2008. If we are to be succesfull it is of utmost importance, that some key users in each operating system will take part of the testing etc. Therefore the question yesterday on experiences comes in very handy, since the experiences will be part of "how and what to consider", when converting EpiData Entry from a "windows only" to a "multiplatform software". regards Jens Lauritsen EpiData Association

1 1

Date time combinations in epicurves
by epidata-list＠lists.umanitoba.ca 06 May '08

06 May '08

I saw an earlier thread on the list suggesting a date time variable in epi analysis or the option to show two variables such as day and hours in an epicurve. I would find this very helpful as for an outbreak I was asked to produce an epi curve, preferably grouped in 3 hourly lots, but certainly showing both date and hour of onset on one graph. The outbreak data was entered into Epidata and as Epidata doesn't have a datetime field information about when people first became sick was stored in two different fields - onsetday (a date field) and onsettime (a numeric field entered as a 24 hour clock). There are three different onset days and a range of onsettimes in each day. I couldn't think of a way of putting both pieces of information on one graph in either epidata analysis or epi info (though in epi info you can group the hours and it will make you a different graph for each day), so finally I exported the data to Excel, grouped the data manually and then graphed it that way. Does anyone have a better suggestion about how to make an epicurv that includes both date and time information? thanks Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 -- The information contained in this email and any attachments is confidential and may be legally privileged. If you have received this message in error, please notify the sender immediately and remove all copies of the message, including any attachments. Any views or opinions expressed in this email (unless otherwise stated) may not represent those of Hutt Valley DHB. Thank you. ** Disclaimer added by HVDHB **

1 0

RE: EpiData-list Digest, Vol 55, Issue 5
by epidata-list＠lists.umanitoba.ca 06 May '08

06 May '08

You are absolutely correct, once a duplicated number is entered, it will pop up "Number already exists, do you want to go to record????? As long as you type "key Unique 1" A Key Unique number can be altered if it was entered by mistake but if you select the ID as AUTO select, then that number which is generated by the computer can not be altered. Sandy MRC (South Africa) -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list-request(a)lists.umanitoba.ca Sent: 06 May 2008 07:02 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 55, Issue 5 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. Re: Re: EpiData-list Digest, Vol 55, Issue 3 Unique ID number (epidata-list(a)lists.umanitoba.ca) 2. Epidata with Ubuntu gusty (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Mon, 05 May 2008 19:16:22 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] Re: EpiData-list Digest, Vol 55, Issue 3 Unique ID number To: epidata-list(a)lists.umanitoba.ca Message-ID: <481F40E6.4090109(a)tbrieder.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Pedro: Am I incorrect in opinionating that actually KEY UNIQUE gives you all answers as well, that an identifier value is already in existence and in which record it is and allowing you to go to precisely that previous record. Hans epidata-list(a)lists.umanitoba.ca wrote: > Gilles, > > All the anterior answers are correct. Hoewever I have a preference for > another command: > > idnumber > autosearch list > end > > This command does not exactly the same thing as key unique. I have this > preference because key unique does not allow U to enter a previous entered > number and does not warn you which record this number is. Autoserach warns > that this number is already in the dataset and gives you the option to edit > this one or to generate a new one. This is handy when the mistake is in the > first one. > For example... suppose you are entering data of questionnaire number 12, > but by mistake you enter 22 at the ID number. When you get on 22, key > unique only tells you U cant enter 22, becasue it is already in the > databank. Autosearch list will show you the record with ID 22 for you to > compare and see if this is the same you entering and allow you to go to this > 22 and change it to 12 if necessary. > > Also, you may use them both at the same check if u like ... > > id > key unique > autosearch list > end > > Best regards, > Pedro Emmanuel > ------------------------------ Message: 2 Date: Mon, 5 May 2008 22:48:48 -0300 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Epidata with Ubuntu gusty To: epidata-list(a)lists.umanitoba.ca Message-ID: <a37cfb5a0805051848m3464cc07x658fc4e4946d9157(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Hello all, I tryed to install Epidata in Ubuntu today and it seems to work fine at first. I looked at the web page and old messages at the list but latest one were from 2004. The installation looked pretty simlpe with wine already installed. Just click on it and wine seems to do the rest. Choose the directory as in windows .... press continue... At first it seems a little weird ... the installation and the program were not in portuguese but in english. There is a lot of violations errors when opening and closing files and sometimes epidata just dont open the files. Some simple commands in windows such as Ctrl+Z dont work. I try to import a simple dataset from a csv file with 6 variables and 45 observations and the same error did not allow me to complete the import.... the ID variable is not compatible. The ID variable was a number from 1 to 45. I try even to delete some variables eand most of observations to make it simple but it didnt work out. Does anyone have recent experiences with Epidata in Linux? Good or bad? -- Abraço forte e que a força esteja com você, Pedro Emmanuel ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 55, Issue 5 *******************************************

1 0

Epidata with Ubuntu gusty
by epidata-list＠lists.umanitoba.ca 05 May '08

05 May '08

Hello all, I tryed to install Epidata in Ubuntu today and it seems to work fine at first. I looked at the web page and old messages at the list but latest one were from 2004. The installation looked pretty simlpe with wine already installed. Just click on it and wine seems to do the rest. Choose the directory as in windows .... press continue... At first it seems a little weird ... the installation and the program were not in portuguese but in english. There is a lot of violations errors when opening and closing files and sometimes epidata just dont open the files. Some simple commands in windows such as Ctrl+Z dont work. I try to import a simple dataset from a csv file with 6 variables and 45 observations and the same error did not allow me to complete the import.... the ID variable is not compatible. The ID variable was a number from 1 to 45. I try even to delete some variables eand most of observations to make it simple but it didnt work out. Does anyone have recent experiences with Epidata in Linux? Good or bad? -- Abraço forte e que a força esteja com você, Pedro Emmanuel

1 0

Re: EpiData-list Digest, Vol 55, Issue 3 Unique ID number
by epidata-list＠lists.umanitoba.ca 05 May '08

05 May '08

Gilles, All the anterior answers are correct. Hoewever I have a preference for another command: idnumber autosearch list end This command does not exactly the same thing as key unique. I have this preference because key unique does not allow U to enter a previous entered number and does not warn you which record this number is. Autoserach warns that this number is already in the dataset and gives you the option to edit this one or to generate a new one. This is handy when the mistake is in the first one. For example... suppose you are entering data of questionnaire number 12, but by mistake you enter 22 at the ID number. When you get on 22, key unique only tells you U cant enter 22, becasue it is already in the databank. Autosearch list will show you the record with ID 22 for you to compare and see if this is the same you entering and allow you to go to this 22 and change it to 12 if necessary. Also, you may use them both at the same check if u like ... id key unique autosearch list end Best regards, Pedro Emmanuel Hello, When creating a questionnaire, in the field pick list, in the "other" tab, select ID auto number Alternatively in the questionnaire create a field with this specific field marker: <IDNUM> Example ID <IDNUM> Best regards Gilles Desve

1 1

RE: EpiData-list Digest, Vol 55, Issue 2
by epidata-list＠lists.umanitoba.ca 03 May '08

03 May '08

Yes, in the "checks" option, click on Edit, Type in "Key Unique " - save and this will prevent duplicates from being entered. Sandy -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list-request(a)lists.umanitoba.ca Sent: 02 May 2008 07:02 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 55, Issue 2 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. Adding unique number manually (epidata-list(a)lists.umanitoba.ca) 2. Re: Adding unique number manually (epidata-list(a)lists.umanitoba.ca) 3. Re: Adding unique number manually (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Fri, 2 May 2008 00:46:02 -0700 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Adding unique number manually To: epidata-list(a)lists.umanitoba.ca Message-ID: <897a5cf60805020046l1308e015s24557a2fd822b4f6(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Dear EpiData lister, thank you for your kind reply for my previous query. There is new question. Can I have variable for ID numbers, called id, and to make sure the value entered is unique to avoid duplicates during data entry? Thank you in advance and best regards ziad ------------------------------ Message: 2 Date: Fri, 02 May 2008 11:01:07 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] Adding unique number manually To: epidata-list(a)lists.umanitoba.ca Message-ID: <481AD853.3080807(a)epiconcept.fr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Hello, When creating a questionnaire, in the field pick list, in the "other" tab, select ID auto number Alternatively in the questionnaire create a field with this specific field marker: <IDNUM> Example ID <IDNUM> Best regards Gilles Desve epidata-list(a)lists.umanitoba.ca a écrit : > Dear EpiData lister, thank you for your kind reply for my previous query. > > There is new question. > Can I have variable for ID numbers, called id, and to make sure the > value entered is unique to avoid duplicates during data entry? > > Thank you in advance and best regards > ziad > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > ------------------------------ Message: 3 Date: Fri, 2 May 2008 02:21:17 -0700 (PDT) From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] Adding unique number manually To: epidata-list(a)lists.umanitoba.ca Message-ID: <790215.97441.qm(a)web55315.mail.re4.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 Hallo, Just use key unique command Caleb Ouma Ongong'a +254721-953790,020 356 2426 P.O Box 1984-00200 Nairobi-Kenya. Alternative e-mails oumacaleb(a)gmail.com caleb(a)dataworldresearch.com "Remember that happiness doesn't depend on what you are or on what you possess, but only on how you think."> --------------------------------- Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 55, Issue 2 *******************************************

1 0

Adding unique number manually
by epidata-list＠lists.umanitoba.ca 02 May '08

02 May '08

Dear EpiData lister, thank you for your kind reply for my previous query. There is new question. Can I have variable for ID numbers, called id, and to make sure the value entered is unique to avoid duplicates during data entry? Thank you in advance and best regards ziad

1 2

Alyshia Landry is out of the office.
by epidata-list＠lists.umanitoba.ca 30 Apr '08

30 Apr '08

I will be out of the office starting 04/30/2008 and will not return until 05/01/2008. If you require immediate assistance, please contact Celina Sousa at extension 5300. Thanks and have a great day, Alyshia

1 0

Loosing data when reviewing the QES
by epidata-list＠lists.umanitoba.ca 29 Apr '08

29 Apr '08

Hi, all the answers that you have received are right. There is still one more reason why you can loose the data when trying to change the QES file. If you have used the option in EpiData to modify the name of the variables directly in the REC file (tools-->rename fields), then when you make a modification in the QES file no matter which way you use you will loose your data as the names of the variables in the REC file do not match the name of the variables in the QES. Hope it helps Pedro > -----Message d'origine----- > De : epidata-list(a)lists.umanitoba.ca > [mailto:epidata-list@lists.umanitoba.ca] Envoyé : lundi 28 avril 2008 > 13:13 > À : epidata-list(a)lists.umanitoba.ca > Objet : [EpiData-list] How to keep data when modifying questionnaire > > Hi, > i started data entry and now need to add 2 new variables to the QES > file, when i transfer the QES file into REC file, the old data > disappeared, any tips how to avoid it? > > Thank you in advance and best regards > ziad > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 54, Issue 13 > ********************************************

1 0

How to keep data when modifying questionnaire
by epidata-list＠lists.umanitoba.ca 29 Apr '08

29 Apr '08

Hi, i started data entry and now need to add 2 new variables to the QES file, when i transfer the QES file into REC file, the old data disappeared, any tips how to avoid it? Thank you in advance and best regards ziad

1 3

Res: EpiData-list Digest, Vol 54, Issue 12 -- adding new variables to a REC file
by epidata-list＠lists.umanitoba.ca 28 Apr '08

28 Apr '08

Hi, Ziad I think you can do it with menu TOOLS > REVISE DATA FILE You will have to enter values for these new variables on the yet entered questionaires, for sure. Hope it helps, Fúlvio Grups de Recerca d'Amèrica i Àfrica Llatines - UAB (Barcelona, Spain) Porto Alegre, Brazil ----- Mensagem original ---- De: "epidata-list-request(a)lists.umanitoba.ca" <epidata-list-request(a)lists.umanitoba.ca> Para: epidata-list(a)lists.umanitoba.ca Enviadas: Segunda-feira, 28 de Abril de 2008 19:09:21 Assunto: EpiData-list Digest, Vol 54, Issue 12 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. How to keep data when modifying questionnaire (epidata-list(a)lists.umanitoba.ca) Hi, i started data entry and now need to add 2 new variables to the QES file, when i transfer the QES file into REC file, the old data disappeared, any tips how to avoid it? Thank you in advance and best regards ziad ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list Abra sua conta no Yahoo! Mail, o único sem limite de espaço para armazenamento! http://br.mail.yahoo.com/

1 0

Problems in EpiData Analysis test build 134 (browse and editor block)
by epidata-list＠lists.umanitoba.ca 25 Apr '08

25 Apr '08

EpiData Analysis build 134 I found problems with the internal definitions of variable names after running a browse in combination of running part of a pgm file in the editor in a block (F8). If you get strange "variable not found ....." or similar error and that variable is no longer in your dataset, unfortunetely you have to close analysis and start over. The error is either part of the editor NOT parsing lines correctly to analysis (e.g. the block is sent for analysis in a different size than shown on the screen) or the browser not cleaning up memory correctly after a browse. The error will be further documented, tracked and removed. I have NOT been able to create the error without using browse. - for safe mode showing of data in this build then use list command instead. (This underlines the necessity of always having a test period before final release). regards Jens Lauritsen Coordinator and initiator of EpiData Project http://www.epidata.dk

1 0

How To: Compare treatment A and B, when not given on all days for all patients
by epidata-list＠lists.umanitoba.ca 25 Apr '08

25 Apr '08

For a medication study we wish to test the hypothesis of no diffence in use of additional morphine for patients given two different pain regimens. The data collected for each patient is the date and time of additional medication from day one until day seven. The number of additional medication given varies from 0 to many. Therefore we record the data as: id : patient id d : date of medication m : Dosage of the medication Basic data are saved for each patient grp : treatment group, A vs. B dayop : Date of surgery For the analysis we also need: variable m : sum of additional morphica given varable d : day of treatment This would seem easy: read medication * add day of surgery etc.: merge id /table=basicdata gen i day = d - dayop * now aggregate on day of medication aggregate id day grp /sum=m * save for later: savedata daymedication /replace * this creates the summary variable summ for m * summ contains the sum of medication on each day for each patient means summ /by=grp /t : overall means summ /by=grp / t if day = 1 : example comparison on day one. But this will give a wrong result, since only persons given medication are recorded in the medication file. We therefore need to restructure the analysis: A. Create a complete file for all patients: * generate file of patient id' numbers * (here 22 patients on day one and two): generate 44 gen i idn = recnumber +1 * we need two lines for each patient: gen i id = (idn div 2) gen i grp = 1 * our dataset is such that first 11 patients are group 1 and remaining group 2: if id > 11 then grp = 2 gen i day = 1 if (id = id[recnumber-1]) then day = 2 drop idn labeldata "Key file for all patients" savedata key /replace * this file now contains exactly one record for all patients on each of day one and two. B now we can analyse the data again: (notice the daymedication file created above) * get the complete file: Read key /close * add medication information: merge id day /table=daymedication * add basic information on merge id /table=basicdata * for patients with no medication summ is equal to . (missing) recode summ .=0 * now summ contains the sum of medication on each day for each patient * show the observations for all days: * generate indicator variable based on day and group gen i g = 10*(grp-1) + day labelvalue g /1="Case Day 1" /2="Day 2" /11="Control day 1" /12="Day 2" * verify distribution of summ as a probit plot cdfplot summ /p * for aggregation in the cdfplot the variable must be integer: gen i mx = integer(summ*1000) cdfplot mx /p /agg * for my specific data showing a straight line * (with a slight "too many at zero" problem) * show as box and dotplot: box summ /by=g /n /out dotplot summ /by=g /sizex=600 /xa /di=0.25 /ti="Amount given - patient level" * finally test the hypothesis means summ /by=grp /t : overall means summ /by=grp if day = 1 : comparison on day one. means summ /by=grp if day = 2 : comparison on day two. Jens Lauritsen Coordinator and initiator of EpiData Project http://www.epidata.dk

1 0

Jump command
by epidata-list＠lists.umanitoba.ca 22 Apr '08

22 Apr '08

Dear EpiData lister, I have field v4 that has formula v4=v3-v2 any way to let the cursor jumps from v3 to v5? thank you and best regards ziad

1 2

Epi data mailing list
by epidata-list＠lists.umanitoba.ca 21 Apr '08

21 Apr '08

Please confirm 78db47628922fd527350fbdaadfc20cf854513cc. Thank you, Nino

1 0

EpiData Analysis build 134 ready for testing
by epidata-list＠lists.umanitoba.ca 20 Apr '08

20 Apr '08

Many minor problems have now (hopefully) been solved in build 134 of EpiData Analysis. Which is available from the usual testing page: www.epidata.dk/testing.php Some issues remain: - small data / zero cell inaccuracies (Most likely not solved, but better information should be developed) - update had to be disabled in this build - a major rewrite is needed before stable function use EpiData Entry for changes to data instead. - some wishes reported to Mantis database - The user base seems divided in where to put some aspects in the menu system: - should logfiles be in file menu or results - should edit setup ini be in file menu or edit Issues solved: Version 2.0.0 build 134 * Extended or adapted function * CIPLOT: adapted to changed order of variables and defaults new plot with confidence intervals for proportions (e.g. cases in subgroups of other variables) * BAR and Histogram: Y axis can be scaled as percent: Option /PCT * Weight variables can be non-integer in tables * merge accepts comparing upper string with string key * Update disabled this build (inconsistent behaviour must be rewritten) * Documentation * Command reference updated (F1) * added quick guide (see F1) * Bugs * Upper string variables written as standard string * Various bugs removed For those wishing to test or comment on the adapted menu system, please see www.epidata.dk/testing.php to get the updated build. Following testing we are approaching release as v2.1 with first translations in Spanish and French. I do acknowledge in particular Gilles Desve for the adaptation of the multinational translation module and Jamie Hockin, Pedro Arias, Peron (Juan Carlos Merino), Bjørnar Nyen, Hans L. Rieder and Neville Verlander for discussions and inputs. But also the EpiData-list discussants in general. In the previous year the Association of Public Health Epidemiologists in Ontario have established an important expert panel, which have been very active in the specification of the CIplot command and other recent aspects. More on this latter collaboration will be announced later. Update is not permanently disabled, but has shown many problems. Therefore I am considering NOT to wait a full rewrite of update, but instead disabling update, to be able to release v2.1 with translation. Comments welcomed on this aspect also. Regards Jens Lauritsen EpiData Association

1 0

Alyshia Landry is out of the office.
by epidata-list＠lists.umanitoba.ca 19 Apr '08

19 Apr '08

I will be out of the office starting 04/19/2008 and will not return until 04/23/2008. If you require immediate assistance, please contact Celina Sousa at extension 5300. Thanks and have a great day, Alyshia

1 0

Count n days between dates?
by epidata-list＠lists.umanitoba.ca 19 Apr '08

19 Apr '08

Dear EpiData lister, it might be simple question, how is it possible to have var 'ndays' showing the number of days between 2 dates, any tips? Thank you in advance and best regards ziad

1 1

Re: Command line help--thank you
by epidata-list＠lists.umanitoba.ca 19 Apr '08

19 Apr '08

Dear Jens Many thanks for the help. Much appreciated. SK -----Original Message----- From: epidata-list-request(a)lists.umanitoba.ca To: epidata-list(a)lists.umanitoba.ca Sent: Wed, 16 Apr 2008 7:21 pm Subject: EpiData-list Digest, Vol 54, Issue 6 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. Re: Re: New user trying to implement a check algoritm (epidata-list(a)lists.umanitoba.ca) 2. Re: Worked examples of EpiData Analysis: command line (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Tue, 15 Apr 2008 20:44:53 -0400 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] Re: New user trying to implement a check algoritm To: epidata-list(a)lists.umanitoba.ca Message-ID: <48054C05.4050809(a)sympatico.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Range checks do work on string variables, since EpiData just compares the internal values. However, EpiData will not care whether the strings have non-numeric values within this range. For example, the following will pass the RANGE test: 1993ABCDEFGH since this is 12 digits and internally any string starting with "1993" will lie between "1992xxxxxxxx" and "2018xxxxxxxx" EpiData will detect an error and assign a missing value to PRNx variables when this happens. The default option is to NOT notify you of errors in check files at data entry, so you should also check that CHECKSUM <> . If only the last digit (the checksum value) is bad, CHECKSUM <> PRN12 will tell you there is an error In my experience, the internal precision of EpiData will let you use 12-digit integers. The RANGE checks will then work fine and entry of non numbers is impossible. So another way to guarantee entry in this range is define preQ2A ____________ global preQ2 Range 1991...... etc preQ2A = string(preQ2) and work everything on preQ2A, since it is easy to pick apart strings using the COPY function. Where you can get into trouble with long integers is when you start to do arithmetic with them. Jamie Gustaf wrote: > I've now redefined preQ2 to be a string variable, but the RANGE check > still works. How is this possible? > > preQ2 > RANGE 199201010001 201801010001 > END ------------------------------ Message: 2 Date: Tue, 15 Apr 2008 20:57:01 -0400 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] Worked examples of EpiData Analysis: command line To: epidata-list(a)lists.umanitoba.ca Message-ID: <48054EDD.2070706(a)sympatico.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed There is no / before the if This is a case of EpiData having somewhat simpler and more natural syntax. The / is reserved for options. So: list idno sr if idno < 10 There is only one option with list (/no to not show record numbers), so: list idno sr /no if idno < 10 Syntax for this use of IF is in the command reference under "temporary selection" The error messages with syntax problems are sometimes misleading. Jamie SK wrote: > here is what I did and the error message: > . read > Loading data F:\EpiExam\blood.rec, please wait.. > File name : F:\EpiExam\blood.rec > Fields: 5 Total records: 2166 Included: 2166 > . List?????? idno? sr? /if idno<10 > = sign expected at idno > ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 54, Issue 6 *******************************************

1 0

Worked examples of EpiData Analysis: command line
by epidata-list＠lists.umanitoba.ca 15 Apr '08

15 Apr '08

Dear all I wish to use EpiData Analysis editor to write a program to help users prepare a standard statistical report from data they will be collecting in Epidata Entry. I have used SAS so am not new to command line programing. I have looked at the command line help in Analysis, but it does not have examples of the codes used: e.g. for the list command, I wish to use a selection of records IF a condition is met: list v1 v2 v3 /if v1<10 here is what I did and the error message: . read Loading data F:\EpiExam\blood.rec, please wait.. File name : F:\EpiExam\blood.rec Fields: 5 Total records: 2166 Included: 2166 . List?????? idno? sr? /if idno<10 = sign expected at idno Could someone help me out and send me an example where command lines are used for common analysis with options as well. Again many thanks for the help, SK South Africa

1 1

Re: New user trying to implement a check algoritm
by epidata-list＠lists.umanitoba.ca 15 Apr '08

15 Apr '08

Comment 1: Hi Gustav, What an coincidence. Today we have been doing something similar with the Danish cpr-nr which is 10 digit 'ddmmyyzzz'. When we treated this as a numeric fiels with 10 digits our algorithms broke down when the date was after the 21. I think that the problem is that the largest integer in many pc languages (here Delphi/pascal) for an integer systems is The MaxInt constant gives the largest allowed value for an Integer. The value is normally (2^32)-1 = 2147483647 If you use a float you will get other problems. The solution for us was to store the complete personal number af a string variable and then extract the relevant number using substr and real. Best wishes Claus Seniorstatistician Claus Holst Institute of Preventive Medicine Center for Health and Society Copenhagen The institute: http://www.ipm.regionh.dk EU projects: http://www.nugenob.org http://www.diogenes-eu.org/ Comment 2: In EpiData we recently changed default max length for integers to be 9 digits and to have the same default in as well analysis and entry. (Although for analysis if you use gen command the length would be 4) The reason for the limitation of length of integer being smaller than the MaxInt constant mentioned by Claus Holst. This is due to the founding of the rec file format in Epi Info v6, which handled integers until the length of 4 as true integers, but stored larger integers internally as floats. We can discuss if the length of 9 is sufficient. But it is my experience in all software that merging on large integers tends to give problems of precision. Therefore my suggested solution for Gustav's problem would be as Claus Holst also suggests to use a string variable. In extension (but not related to the integer/string problem) the algoritm for the luhn algorithm (http://en.wikipedia.org/wiki/Luhn_algorithm) could be implemented as a user written CHK command based on the procedures written for EpiData Entry. This is documented on the page www.epidata.dk/documentation.php with two examples: Soundex, Metaphone and Gumm algoritms. regards Jens Lauritsen EpiData Association

1 2

Re: EpiData-list Digest, Vol 54, Issue 2
by epidata-list＠lists.umanitoba.ca 14 Apr '08

14 Apr '08

Dear Epidata Users Many thanks for the input you all gave me about packaging Epidata with the data folders. Much appreciated. Kind regards, SK -----Original Message----- From: epidata-list-request(a)lists.umanitoba.ca To: epidata-list(a)lists.umanitoba.ca Sent: Thu, 10 Apr 2008 7:24 pm Subject: EpiData-list Digest, Vol 54, Issue 2 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. EpiData-list Digest, Vol 54, Issue 1 Attach files to executable (epidata-list(a)lists.umanitoba.ca) 2. Re: How to package Epidate Software with desired data entry files (epidata-list(a)lists.umanitoba.ca) 3. Re: How to package Epidata Software with desired data entry files (epidata-list(a)lists.umanitoba.ca) 4. How to package Epidata Software with desired data entry files (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Wed, 9 Apr 2008 15:49:31 -0300 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] EpiData-list Digest, Vol 54, Issue 1 Attach files to executable To: epidata-list(a)lists.umanitoba.ca Message-ID: <a37cfb5a0804091149g599b97f0ydd5409f612fd881a(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Dear SK, I did a similar thing many years ago. I hope it works for you even nowadays. Lets assume that Epidata can just be pasted at some place such as c:\ (wich is reasonable and works fine wiht me - as far as know epidata does not require any system files). Then, I sugest that you delete the Epidata sample files and place your files in this same directory where the sample files were. This would make the one who is starting Epidata for the first time to see your files instead of the sample files if the short cut does not work. So naw U have a c:/epidata with your files in c:/epidata/samples. Make a shortcut on your desktop that point to c:\epidata\samples\<myproject>.rec, and be sure that this short cut has the option "open with" pointing to the epidata executable in c:\epidata\. Test it. If it is fine follow next... Then, you should have a progrma such as winzip or winrar. This programs can make executable files that self-exctrat to a prespecified place such as c:/. I dont remeber exactly how it is but look for options to meke self extract files. So, if when the user executes them the file extratcs the whole folder or whatever you put in them to the prespecified place. You also may want to input a password at the files to be extratcted, winzip for shure does that. Then when you sand an email for your mates, with these two files, one zipped selfextracted (.exe) and a shortcut wiht the following tip - paste both files ate your desktop, execute the .exe file, execute the shortcut. The magic should work... at least it did with me. Best Regards, Pedro Emmanuel Brasil ------------------------------ Message: 2 Date: Wed, 09 Apr 2008 20:39:05 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Re: How to package Epidate Software with desired data entry files To: epidata-list(a)lists.umanitoba.ca Message-ID: <47FD0D49.1010107(a)soziologie.uni-freiburg.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 1. You can have a look at the epidata command line options and then add a batch file (.bat) to your zipped package. there is no need to install epidata, but you can simply let the users unpack the .zip to a folder on their desktop and double click the batch file. 2. More convenient way is to use an installer software like http://nsis.sourceforge.net/Main_Page (you can create desktop shortcuts and things like that). But be aware of user rights, common desktop systems in professional setups dont allow installations in programm directory or are even more restricted. so people may have to call an administrator to install the package. hope this helps, markus jenki epidata-list-request(a)lists.umanitoba.ca schrieb: > 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. How to package Epidata Software with desired data entry files > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 08 Apr 2008 13:42:29 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] How to package Epidata Software with desired > data entry files > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <8CA67B70CD54729-D58-2F4(a)MBLK-D29.sysops.aol.com> > Content-Type: text/plain; charset="us-ascii" > > Hi there, > > I am embarking on a project to keep an in-patient child admissions/discharge database in all district hospitals in our Province. I have designed the database and created data entry files (QES|CHK|REC|EIX) and put them into a folder (IPDatabase). Now what I wish to do is package this folder into the EpiData Entry|Analysis software (*.exe setup files); so that the users could just click the installation and have the software installed in a default WinXP Program directory directly, and with this would go the IPDatabase folder with all the data entry files. > 1. The user (data capturer) will then start data entry by going to the folder to pick up the .REC file in the IPDatabase folder, but first he will have to start up Epidata Entry.. > 2 Or create a desktop shortcut that will directly link up with the data entry process; without even staritng up the EpiData Entry software--desired outcome > > Why am I doing this?--well, I have users who have difficulties understanding difference between installation of the software and using the data entry file. One precess that will get the objectives met: capture data without having to think about the process. > > I hope this is a possibility? > > Many thanks in advance. > > SK > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 54, Issue 1 > ******************************************* > ------------------------------ Message: 3 Date: Wed, 09 Apr 2008 18:58:39 -0400 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] How to package Epidata Software with desired data entry files To: epidata-list(a)lists.umanitoba.ca Message-ID: <47FD4A1F.70603(a)sympatico.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed There are many solutions as some have already sent you. When packaging EpiData and Analysis up, you can use the shortcut/batch files mentioned to load Analysis so that it launches with an HTML file. This is the way it gets loaded the first time after it is installed. If you are at all familiar with command lines and simple HTML, have a look at the file in (on my computer) c:\program files\epidata\docs\en\startepi.htm This HTML file provides a way to launch a menu system with Analysis. You can provide options such as - Enter Data - launches Enter yourfile.rec - Analyze Data - execute the READ yourfile command and then lets the user use Analysis commands - you can even package up what commands should be used. However, these are not techniques for the novice. Have a look at startepi.htm to get an idea of how this works and then decide how sophisticated you want to make things (i.e. how easy/fool proof for your users) Jamie epidata-list(a)lists.umanitoba.ca wrote: > Hi there, > > I am embarking on a project to keep an in-patient child admissions/discharge database in all district hospitals in our Province. I have designed the database and created data entry files (QES|CHK|REC|EIX) and put them into a folder (IPDatabase). Now what I wish to do is package this folder into the EpiData Entry|Analysis software (*.exe setup files); so that the users could just click the installation and have the software installed in a default WinXP Program directory directly, and with this would go the IPDatabase folder with all the data entry files. > 1. The user (data capturer) will then start data entry by going to the folder to pick up the .REC file in the IPDatabase folder, but first he will have to start up Epidata Entry.. > 2 Or create a desktop shortcut that will directly link up with the data entry process; without even staritng up the EpiData Entry software--desired outcome > > Why am I doing this?--well, I have users who have difficulties understanding difference between installation of the software and using the data entry file. One precess that will get the objectives met: capture data without having to think about the process. > > I hope this is a possibility? > > Many thanks in advance. > > SK > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > ------------------------------ Message: 4 Date: Thu, 10 Apr 2008 10:51:49 +0100 (BST) From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] How to package Epidata Software with desired data entry files To: epidata-list(a)lists.umanitoba.ca Message-ID: <287335.55799.qm(a)web25003.mail.ukl.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 SK asked about “intelligent” setup on pc’s for users without IT knowledge. Basically install EpiData Entry on your computer and create the data entry files. You can run the basic EpiData Entry and EpiData Analysis without installation of the programmes. Package the data entry files (Qes, Chk, Rec, Eix) and only the EpiData.exe file (not the setup_epidata.exe file which does not need to be installed to run the program. Zip them and send them to the users. For the users: Unzip the files into a created folder (IPDatabase in your case) In that folder, double click EpiData.exe, EpiData Entry opens, then go to “Enter Data” and open the created folder, and open the *.rec file for data entry. Second possibility is to create a link on the desktop and add the name of the datafile as a parameter e.g. “epidata.exe c:\ip\IPDatabase.rec” Additionally you could you could automate backup and exit EpiData Entry by adding the following block to the chk file. For the backup to work you must manually create the backup folder. AFTER FILE BACKUP c:\ip\backup zip ip DATE QUIT END Regards, Biggie Mabaera Maseru, Lesotho --------------------------------- Yahoo! for Good helps you make a difference ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 54, Issue 2 *******************************************

1 0

New user trying to implement a check algorithm
by epidata-list＠lists.umanitoba.ca 11 Apr '08

11 Apr '08

Hi all, I'm a new user of EpiData. At the moment, I'm making a data entry system for a medical questionnaire. In this questionnaire, a 12 digit personal identification number should be entered. The first 8 digits of this number is the birthday, the following 3 digits carry some obscure meaning (gender being one of them), and the last digit is a control number calculated from the previous 11 digits by the luhn algorithm (http://en.wikipedia.org/wiki/Luhn_algorithm). I've been trying to implement this algorithm in EpiData (see below), but when I try to use this check file, EipData doesn't like it, claiming the "FLOAT(copy(preQ2s,1,1))"-expressions are too wide. Any suggestions on how to solve this in a more elegant way? Many thanks in advance, Gustaf ------ Algorithm. "preQ2" is the variable name for the specific question, defined as a 12 digit number (############)------------ preQ2 RANGE 199201010001 201801010001 DEFINE pnr1 _ DEFINE pnr2 _ DEFINE pnr3 _ DEFINE pnr4 _ DEFINE pnr5 _ DEFINE pnr6 _ DEFINE pnr7 _ DEFINE pnr8 _ DEFINE pnr9 _ DEFINE pnr10 _ DEFINE pnr11 _ DEFINE pnr12 _ DEFINE preQ2s ____________ DEFINE checkSum ## preQ2s=string(preQ2) pnr1=FLOAT(copy(preQ2s,1,1)) pnr2=FLOAT(copy(preQ2s,2,2)) pnr3=FLOAT(copy(preQ2s,3,3)) pnr4=FLOAT(copy(preQ2s,4,4)) pnr5=FLOAT(copy(preQ2s,5,5)) pnr6=FLOAT(copy(preQ2s,6,6)) pnr7=FLOAT(copy(preQ2s,7,7)) pnr8=FLOAT(copy(preQ2s,8,8)) pnr9=FLOAT(copy(preQ2s,9,9)) pnr10=FLOAT(copy(preQ2s,10,10)) pnr11=FLOAT(copy(preQ2s,11,11)) pnr12=FLOAT(copy(preQ2s,12,12)) IF (pnr3>4) THEN pnr3=pnr3*2-9 ELSE pnr3=pnr3*2 ENDIF IF (pnr5>4) THEN pnr5=pnr5*2-9 ELSE pnr5=pnr5*2 ENDIF IF (pnr7>4) THEN pnr7=pnr7*2-9 ELSE pnr7=pnr7*2 ENDIF IF (pnr9>4) THEN pnr9=pnr9*2-9 ELSE pnr9=pnr9*2 ENDIF IF (pnr11>4) THEN pnr11=pnr11*2-9 ELSE pnr11=pnr11*2 ENDIF checkSum=pnr3+pnr4+pnr5+pnr6+pnr7+pnr8+pnr9+pnr10+pnr11 IF (checkSum=10*int(checkSum)) THEN checkSum=checkSum/10 ELSE checkSum=10*(TRUNC(checkSum/10)+1)-checkSum ENDIF IF (pnr12<>checkSum) THEN HELP "felaktigt PersonNummer" TYPE=ERROR GOTO preQ2 ENDIF END -- Gustaf Rydevik, M.Sci. tel: +46(0)703 051 451 address:Essingetorget 40,112 66 Stockholm, SE skype:gustaf_rydevik

1 1

How to package Epidata Software with desired data entry files
by epidata-list＠lists.umanitoba.ca 10 Apr '08

10 Apr '08

SK asked about intelligent setup on pcs for users without IT knowledge. Basically install EpiData Entry on your computer and create the data entry files. You can run the basic EpiData Entry and EpiData Analysis without installation of the programmes. Package the data entry files (Qes, Chk, Rec, Eix) and only the EpiData.exe file (not the setup_epidata.exe file which does not need to be installed to run the program. Zip them and send them to the users. For the users: Unzip the files into a created folder (IPDatabase in your case) In that folder, double click EpiData.exe, EpiData Entry opens, then go to Enter Data and open the created folder, and open the *.rec file for data entry. Second possibility is to create a link on the desktop and add the name of the datafile as a parameter e.g. epidata.exe c:\ip\IPDatabase.rec Additionally you could you could automate backup and exit EpiData Entry by adding the following block to the chk file. For the backup to work you must manually create the backup folder. AFTER FILE BACKUP c:\ip\backup zip ip DATE QUIT END Regards, Biggie Mabaera Maseru, Lesotho --------------------------------- Yahoo! for Good helps you make a difference

1 0

How to package Epidata Software with desired data entry files
by epidata-list＠lists.umanitoba.ca 09 Apr '08

09 Apr '08

Hi there, I am embarking on a project to keep an in-patient child admissions/discharge database in all district hospitals in our Province. I have designed the database and created data entry files (QES|CHK|REC|EIX) and put them into a folder (IPDatabase). Now what I wish to do is package this folder into the EpiData Entry|Analysis software (*.exe setup files); so that the users could just click the installation and have the software installed in a default WinXP Program directory directly, and with this would go the IPDatabase folder with all the data entry files. 1. The user (data capturer) will then start data entry by going to the folder to pick up the .REC file in the IPDatabase folder, but first he will have to start up Epidata Entry.. 2 Or create a desktop shortcut that will directly link up with the data entry process; without even staritng up the EpiData Entry software--desired outcome Why am I doing this?--well, I have users who have difficulties understanding difference between installation of the software and using the data entry file. One precess that will get the objectives met: capture data without having to think about the process. I hope this is a possibility? Many thanks in advance. SK

1 1

EpiData-list Digest, Vol 54, Issue 1 Attach files to executable
by epidata-list＠lists.umanitoba.ca 09 Apr '08

09 Apr '08

Dear SK, I did a similar thing many years ago. I hope it works for you even nowadays. Lets assume that Epidata can just be pasted at some place such as c:\ (wich is reasonable and works fine wiht me - as far as know epidata does not require any system files). Then, I sugest that you delete the Epidata sample files and place your files in this same directory where the sample files were. This would make the one who is starting Epidata for the first time to see your files instead of the sample files if the short cut does not work. So naw U have a c:/epidata with your files in c:/epidata/samples. Make a shortcut on your desktop that point to c:\epidata\samples\<myproject>.rec, and be sure that this short cut has the option "open with" pointing to the epidata executable in c:\epidata\. Test it. If it is fine follow next... Then, you should have a progrma such as winzip or winrar. This programs can make executable files that self-exctrat to a prespecified place such as c:/. I dont remeber exactly how it is but look for options to meke self extract files. So, if when the user executes them the file extratcs the whole folder or whatever you put in them to the prespecified place. You also may want to input a password at the files to be extratcted, winzip for shure does that. Then when you sand an email for your mates, with these two files, one zipped selfextracted (.exe) and a shortcut wiht the following tip - paste both files ate your desktop, execute the .exe file, execute the shortcut. The magic should work... at least it did with me. Best Regards, Pedro Emmanuel Brasil

1 0

Re: How to package Epidate Software with desired data entry files
by epidata-list＠lists.umanitoba.ca 09 Apr '08

09 Apr '08

1. You can have a look at the epidata command line options and then add a batch file (.bat) to your zipped package. there is no need to install epidata, but you can simply let the users unpack the .zip to a folder on their desktop and double click the batch file. 2. More convenient way is to use an installer software like http://nsis.sourceforge.net/Main_Page (you can create desktop shortcuts and things like that). But be aware of user rights, common desktop systems in professional setups dont allow installations in programm directory or are even more restricted. so people may have to call an administrator to install the package. hope this helps, markus jenki epidata-list-request(a)lists.umanitoba.ca schrieb: > 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. How to package Epidata Software with desired data entry files > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 08 Apr 2008 13:42:29 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] How to package Epidata Software with desired > data entry files > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <8CA67B70CD54729-D58-2F4(a)MBLK-D29.sysops.aol.com> > Content-Type: text/plain; charset="us-ascii" > > Hi there, > > I am embarking on a project to keep an in-patient child admissions/discharge database in all district hospitals in our Province. I have designed the database and created data entry files (QES|CHK|REC|EIX) and put them into a folder (IPDatabase). Now what I wish to do is package this folder into the EpiData Entry|Analysis software (*.exe setup files); so that the users could just click the installation and have the software installed in a default WinXP Program directory directly, and with this would go the IPDatabase folder with all the data entry files. > 1. The user (data capturer) will then start data entry by going to the folder to pick up the .REC file in the IPDatabase folder, but first he will have to start up Epidata Entry.. > 2 Or create a desktop shortcut that will directly link up with the data entry process; without even staritng up the EpiData Entry software--desired outcome > > Why am I doing this?--well, I have users who have difficulties understanding difference between installation of the software and using the data entry file. One precess that will get the objectives met: capture data without having to think about the process. > > I hope this is a possibility? > > Many thanks in advance. > > SK > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 54, Issue 1 > ******************************************* >

1 0

EpiData-list Digest
by epidata-list＠lists.umanitoba.ca 30 Mar '08

30 Mar '08

Hello, In ANALYSIS V1.X, there is command "set table label=on/off" To watch label variables or not. What the equivalent command in V2.X ? Thank you Bernard BRANGER, Nantes

1 1

Labeling to transfer into STATA
by epidata-list＠lists.umanitoba.ca 28 Mar '08

28 Mar '08

Dear EpiData lister i am preparing my dataset now in EpiData, with aim to analyse in STATA. meant to ask how to transfer the labels into STATA? Thank you in advance and best regards ziad

1 2

Link to Note / French / Nantes
by epidata-list＠lists.umanitoba.ca 23 Mar '08

23 Mar '08

The Link with EIDATA site / Download / Epidata Entry - Introduction Notes-Nantes is bad. The godd link is : http://www.reseau-naissance.com/joomla/index.php?option=com_content&task=sec tion&id=11&Itemid=78 Thank you. Bernard Branger, Nantes

1 0

Random Selection of records - Thanks
by epidata-list＠lists.umanitoba.ca 21 Mar '08

21 Mar '08

Dear Jamie, Thanks for the nice response to the query Random selection of records. It worked very well. Epi Analysis has far more features than EPI6 and the documentation is not that detailed. I had suggested to Jens once to get the manual written by the vast user base. Jens suggested to add to the how to section only. If you look at the questions, answers of the last few years (since the release of Epi Analysis) it is a huge database of good quality questions and answers. If these are classified and documented in the form of a pdf manual, it can save a lot of time of the friends at the epidata help desk. Of course detailed command reference (like that of EPI6) is our dream and together all of us users can make it happen. Once again I am thankful for the solution provided. With regards, Dr. Shavinder Singh

1 0

Urgent query
by epidata-list＠lists.umanitoba.ca 13 Mar '08

13 Mar '08

Hi, Can you please advise if one has two versions of One Database and an entry exists in version One but should be in Version Two, is there a way of taking that record across to version two? Kind Regards Sandy Dayaram Biostats Unit Medical Research Council (South Africa) This e-mail and its contents are subject to the South African Medical Research Council e-mail legal notice available at http://www.mrc.ac.za/about/EmailLegalNotice.html -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list-request(a)lists.umanitoba.ca Sent: 12 March 2008 19:07 To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 53, Issue 7 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. Res: EpiData-list Digest, Vol 53, Issue 6 (epidata-list(a)lists.umanitoba.ca) 2. Re: EpiData-list Digest, Vol 53, Issue 6 (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Tue, 11 Mar 2008 16:44:45 -0700 (PDT) From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Res: EpiData-list Digest, Vol 53, Issue 6 To: epidata-list(a)lists.umanitoba.ca Message-ID: <254490.87770.qm(a)web50510.mail.re2.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 in EpiData Analysis you still can do it (combine data bases with append or merge commands), isn't it? best wishes, Fúlvio B. Nedel, Brasil ----- Mensagem original ---- De: "epidata-list-request(a)lists.umanitoba.ca" <epidata-list-request(a)lists.umanitoba.ca> Para: epidata-list(a)lists.umanitoba.ca Enviadas: Terça-feira, 11 de Março de 2008 18:03:18 Assunto: EpiData-list Digest, Vol 53, Issue 6 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. Re: EpiData-list Digest, Vol 53, Issue 5 - Show Labelsand combine datasets (epidata-list(a)lists.umanitoba.ca) -----Mensagem incorporada----- Ziad, To show the labels while entering data is simple. Use the command show in the CHK file: sex comment legal use label_sex show end When cursor is in the field a box with the options will appear. You may also use the "type" command to make the label to be seen after the fild has been filled. Unfortunatenly (or forntunately), Epidta does not have a multiuser mode such as in EPI6. So, when several digitizers work wiht the same file, from time to time, or at the end some one has to merge the files. Epidata does that. Epidata can merge the files side to side or end to end. I dont know exactly where it is because my menus are in portuguese. Look for something such as "combine datasets". It is intuitive and easy to use. In this process you have to be carefull not to delete observations in the dataset or a whole dataset and not to use duplicates (merge the same dataset twice). Most statistical softwares such as Stata and R have functions to find duplicates lines in the dataset. Best regards, Pedro Brasil ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list Ziad, To show the labels while entering data is simple. Use the command show in the CHK file: sex comment legal use label_sex show end When cursor is in the field a box with the options will appear. You may also use the "type" command to make the label to be seen after the fild has been filled. Unfortunatenly (or forntunately), Epidta does not have a multiuser mode such as in EPI6. So, when several digitizers work wiht the same file, from time to time, or at the end some one has to merge the files. Epidata does that. Epidata can merge the files side to side or end to end. I dont know exactly where it is because my menus are in portuguese. Look for something such as "combine datasets". It is intuitive and easy to use. In this process you have to be carefull not to delete observations in the dataset or a whole dataset and not to use duplicates (merge the same dataset twice). Most statistical softwares such as Stata and R have functions to find duplicates lines in the dataset. Best regards, Pedro Brasil Abra sua conta no Yahoo! Mail, o único sem limite de espaço para armazenamento! http://br.mail.yahoo.com/ ------------------------------ Message: 2 Date: Wed, 12 Mar 2008 10:34:26 +0000 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Re: EpiData-list Digest, Vol 53, Issue 6 To: epidata-list(a)lists.umanitoba.ca Message-ID: <bf1bb7700803120334m3fa5a315w59d93365b1c855a0(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 The TYPE COMMENT command is very useful to display the label associated with an entered variable value during the data entry. Example: go the checks file and select sex then click Edit. Now edit the CHECK command as follow: SEX TYPE COMMENT COMMENT LEGAL USE label_sex END Accept and close then save; the label should appear when to try to enter value for sex into the rec file. Kind regards Tieble On 11/03/2008, epidata-list-request(a)lists.umanitoba.ca < 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. Re: EpiData-list Digest, Vol 53, Issue 5 - Show Labelsand > combine datasets (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 11 Mar 2008 01:48:04 -0300 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Re: EpiData-list Digest, Vol 53, Issue 5 - > Show Labelsand combine datasets > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <a37cfb5a0803102148x3a0e0aacu8157ba62f36a403c(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Ziad, > > To show the labels while entering data is simple. Use the command show > in the CHK file: > > sex > comment legal use label_sex show > end > > When cursor is in the field a box with the options will appear. You > may also use the "type" command to make the label to be seen after the > fild has been filled. > > Unfortunatenly (or forntunately), Epidta does not have a multiuser > mode such as in EPI6. So, when several digitizers work wiht the same > file, from time to time, or at the end some one has to merge the > files. Epidata does that. > Epidata can merge the files side to side or end to end. I dont know > exactly where it is because my menus are in portuguese. Look for > something such as "combine datasets". It is intuitive and easy to use. > > In this process you have to be carefull not to delete observations in > the dataset or a whole dataset and not to use duplicates (merge the > same dataset twice). Most statistical softwares such as Stata and R > have functions to find duplicates lines in the dataset. > > Best regards, > Pedro Brasil > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 53, Issue 6 > ******************************************* > ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 53, Issue 7 ******************************************* -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

1 0

Re: EpiData-list Digest, Vol 53, Issue 6
by epidata-list＠lists.umanitoba.ca 12 Mar '08

12 Mar '08

The TYPE COMMENT command is very useful to display the label associated with an entered variable value during the data entry. Example: go the checks file and select sex then click Edit. Now edit the CHECK command as follow: SEX TYPE COMMENT COMMENT LEGAL USE label_sex END Accept and close then save; the label should appear when to try to enter value for sex into the rec file. Kind regards Tieble On 11/03/2008, epidata-list-request(a)lists.umanitoba.ca < 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. Re: EpiData-list Digest, Vol 53, Issue 5 - Show Labelsand > combine datasets (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 11 Mar 2008 01:48:04 -0300 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Re: EpiData-list Digest, Vol 53, Issue 5 - > Show Labelsand combine datasets > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <a37cfb5a0803102148x3a0e0aacu8157ba62f36a403c(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Ziad, > > To show the labels while entering data is simple. Use the command show in > the CHK file: > > sex > comment legal use label_sex show > end > > When cursor is in the field a box with the options will appear. You may > also > use the "type" command to make the label to be seen after the fild has > been > filled. > > Unfortunatenly (or forntunately), Epidta does not have a multiuser mode > such > as in EPI6. So, when several digitizers work wiht the same file, from time > to time, or at the end some one has to merge the files. Epidata does that. > Epidata can merge the files side to side or end to end. I dont know > exactly > where it is because my menus are in portuguese. Look for something such as > "combine datasets". It is intuitive and easy to use. > > In this process you have to be carefull not to delete observations in the > dataset or a whole dataset and not to use duplicates (merge the same > dataset > twice). Most statistical softwares such as Stata and R have functions to > find duplicates lines in the dataset. > > Best regards, > Pedro Brasil > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 53, Issue 6 > ******************************************* >

1 0

Res: EpiData-list Digest, Vol 53, Issue 6
by epidata-list＠lists.umanitoba.ca 11 Mar '08

11 Mar '08

in EpiData Analysis you still can do it (combine data bases with append or merge commands), isn't it? best wishes, Fúlvio B. Nedel, Brasil ----- Mensagem original ---- De: "epidata-list-request(a)lists.umanitoba.ca" <epidata-list-request(a)lists.umanitoba.ca> Para: epidata-list(a)lists.umanitoba.ca Enviadas: Terça-feira, 11 de Março de 2008 18:03:18 Assunto: EpiData-list Digest, Vol 53, Issue 6 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. Re: EpiData-list Digest, Vol 53, Issue 5 - Show Labelsand combine datasets (epidata-list(a)lists.umanitoba.ca) -----Mensagem incorporada----- Ziad, To show the labels while entering data is simple. Use the command show in the CHK file: sex comment legal use label_sex show end When cursor is in the field a box with the options will appear. You may also use the "type" command to make the label to be seen after the fild has been filled. Unfortunatenly (or forntunately), Epidta does not have a multiuser mode such as in EPI6. So, when several digitizers work wiht the same file, from time to time, or at the end some one has to merge the files. Epidata does that. Epidata can merge the files side to side or end to end. I dont know exactly where it is because my menus are in portuguese. Look for something such as "combine datasets". It is intuitive and easy to use. In this process you have to be carefull not to delete observations in the dataset or a whole dataset and not to use duplicates (merge the same dataset twice). Most statistical softwares such as Stata and R have functions to find duplicates lines in the dataset. Best regards, Pedro Brasil ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list Ziad, To show the labels while entering data is simple. Use the command show in the CHK file: sex comment legal use label_sex show end When cursor is in the field a box with the options will appear. You may also use the "type" command to make the label to be seen after the fild has been filled. Unfortunatenly (or forntunately), Epidta does not have a multiuser mode such as in EPI6. So, when several digitizers work wiht the same file, from time to time, or at the end some one has to merge the files. Epidata does that. Epidata can merge the files side to side or end to end. I dont know exactly where it is because my menus are in portuguese. Look for something such as "combine datasets". It is intuitive and easy to use. In this process you have to be carefull not to delete observations in the dataset or a whole dataset and not to use duplicates (merge the same dataset twice). Most statistical softwares such as Stata and R have functions to find duplicates lines in the dataset. Best regards, Pedro Brasil Abra sua conta no Yahoo! Mail, o único sem limite de espaço para armazenamento! http://br.mail.yahoo.com/

1 0

Re: EpiData-list Digest, Vol 53, Issue 5 - Show Labelsand combine datasets
by epidata-list＠lists.umanitoba.ca 10 Mar '08

10 Mar '08

Ziad, To show the labels while entering data is simple. Use the command show in the CHK file: sex comment legal use label_sex show end When cursor is in the field a box with the options will appear. You may also use the "type" command to make the label to be seen after the fild has been filled. Unfortunatenly (or forntunately), Epidta does not have a multiuser mode such as in EPI6. So, when several digitizers work wiht the same file, from time to time, or at the end some one has to merge the files. Epidata does that. Epidata can merge the files side to side or end to end. I dont know exactly where it is because my menus are in portuguese. Look for something such as "combine datasets". It is intuitive and easy to use. In this process you have to be carefull not to delete observations in the dataset or a whole dataset and not to use duplicates (merge the same dataset twice). Most statistical softwares such as Stata and R have functions to find duplicates lines in the dataset. Best regards, Pedro Brasil

1 0

2 questions (showing labels while entering data/copy records)
by epidata-list＠lists.umanitoba.ca 07 Mar '08

07 Mar '08

Hello, I built some data entry files for entering the questionnaires of my research. There are 2 dilemmas I don't how to solve and which I cannot find in the help menu. 1. Is it possible to see the labels (like 0 = no; 1 = yes) while entering data? How? 2. Some students will help me entering data on different computers (so I copied the datafiles and put it on those computers). Is it possible to copy records so I can put them in the end all together in the original datafile on my computer? If yes, how? I hope some-one can answer my two questions Floor van Santvoort

1 1

Re: EpiData-list Digest, Vol 53, Issue 4
by epidata-list＠lists.umanitoba.ca 07 Mar '08

07 Mar '08

I built some data entry files for entering the questionnaires of my research. There are 2 dilemmas I don't how to solve and which I cannot find in the help menu. 1. Is it possible to see the labels (like 0 = no; 1 = yes) while entering data? How? --> I usually write the labels below the question. 2. Some students will help me entering data on different computers (so I copied the datafiles and put it on those computers). Is it possible to copy records so I can put them in the end all together in the original datafile on my computer? If yes, how? --> you can do it using merge option? Good luck! ziad I hope some-one can answer my two questions Floor van Santvoort On Fri, Mar 7, 2008 at 10:13 AM, <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. Re: EpiData-list Digest, Vol 53, Issue 3 > (epidata-list(a)lists.umanitoba.ca) > 2. 2 questions (showing labels while entering data/copy records) > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 6 Mar 2008 10:38:02 -0800 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Re: EpiData-list Digest, Vol 53, Issue 3 > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <897a5cf60803061038o6fa179d0xa3e671f062557a59(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Dear Pedro, > Thank you for your kind reply. > > I plan to review medical records using paper form. > Expecting to have 1 observation at baseline to be entered in baseline > file and 6-24 observations for time of follow-up, will be entered in > follow-up file. > Then data will be entered twice and compared (around 600 patients in total). > > I am trying to find an alternative way to collect data using papers. > Palm would be solution but more expensive etc.. > > > Thank you in advance and best regards > ziad > > > > > > On Thu, Mar 6, 2008 at 10:02 AM, > <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. Re: EpiData-list Digest, Vol 53, Issue 2 - Review Medical > > records (epidata-list(a)lists.umanitoba.ca) > > 2. Re: CHK file with calculations does not work as it did in > > EpiInfo (epidata-list(a)lists.umanitoba.ca) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Thu, 6 Mar 2008 09:13:47 -0300 > > From: epidata-list(a)lists.umanitoba.ca > > Subject: [EpiData-list] Re: EpiData-list Digest, Vol 53, Issue 2 - > > Review Medical records > > To: epidata-list(a)lists.umanitoba.ca > > Message-ID: > > <a37cfb5a0803060413m190e2205jb408707648dbca2a(a)mail.gmail.com> > > Content-Type: text/plain; charset=ISO-8859-1 > > > > Dear Ziad, > > > > Your question is rather non specific, but I ve been through a similar > > experience with some bad memories. > > > > Review medical records is not an easy task. First of all, the type of study > > > (for exemple a suvival analysis) is of extremem importance on how the data > > > should be organized. Then you must decide what information should be > > > extracted from the records. Going back to the records a second or third time > > > is really frustrating and time consuming. In general for ARV, to register > > > all the ARV combinations, with the start dates and end dates, all CD4 cell > > > counts and Viral loads with their respective dates, all diagnosis of > > > oportunistic infections and their respective dates of diagnosis. Also, you > > > shlould consider making a separate data entry for each one of this data or > > > all of them in the same data entry, if you have someone experience in this > > > tipe of data analyis, the separate way will make easier to extract and type. > > > To use the AUTOSEARCH LIST command in the check file will be of help. Also > > > dont forget a field if the ARV is HAART or not and an outcome such as death > > > and/or hospitalization and of course its date. > > > > > > > Good Luck, > > Pedro Brasil > > > > ---------------------------------------------------------------------- > > > > > > Message: 1 > > > Date: Tue, 4 Mar 2008 10:16:56 -0800 > > > From: epidata-list(a)lists.umanitoba.ca > > > Subject: [EpiData-list] Using EpiData to review medical records > > > To: epidata-list(a)lists.umanitoba.ca > > > Message-ID: > > > <897a5cf60803041016y396e0f9dwf0baa18ba3168469(a)mail.gmail.com> > > > Content-Type: text/plain; charset=ISO-8859-1 > > > > > > Dear EpiDataLister, > > > It is semi-technical question. I intend to review medical records > > > retrospectively for patients on ARVs. It seems to be involving lot of > > > papers to review their history to be able to enter them into EpiData. > > > Meant to check if someone had similar experience to share how did you > > > sort it out? > > > > > > Thank you in advance and best regards > > > ziad > > > > > > > > > > > > > > > ------------------------------ > > > > Message: 2 > > Date: Wed, 5 Mar 2008 22:28:28 -0400 > > From: epidata-list(a)lists.umanitoba.ca > > Subject: [EpiData-list] Re: CHK file with calculations does not work > > as it did in EpiInfo > > To: <epidata-list(a)lists.umanitoba.ca> > > Message-ID: <200835222828.983160@IW2575> > > Content-Type: text/plain; charset="iso-8859-1" > > > > Thanks Hans, I don't know what happened. This is what was pasted except that I exchanged the double quotes for single quotes in case that is why text got truncated. > > > > IF N9SUICIDE = 3 or (N9SUICIDE = 2 AND TOTAL >= 16) or TOTAL > 42 > > THEN > > ATRISK='Y' > > ELSE > > ATRISK='N' > > ENDIF > > END > > > > John LeBlanc > > ----------------------------------------- > > Message: 2 > > Date: Tue, 04 Mar 2008 20:10:27 +0100 > > From: epidata-list(a)lists.umanitoba.ca > > Subject: Re: [EpiData-list] CHK file with calculations does not work > > as it did in EpiInfo > > To: epidata-list(a)lists.umanitoba.ca > > Message-ID: <47CD9EA3.5000402(a)tbrieder.org> > > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > > > Unless, something go lost, there is surely something missing here: > > > > IF N9SUICIDE = or (N9SUICIDE = 2 AND TOTAL >= 16) or TOTAL > 42 > > > > > > Hans > > > > > > John LeBlanc > > > > > > On Tue, 4 Mar 2008 12:50:55 -0400, John LeBlanc wrote: > > Hi, > > > > I wonder if someone can spot the syntax problem in this CHK file for the Beck Depression inventory. I've struggled for hours to get it to work the way it did under Epi Info. Basically, there are three conditions in an IF statement. I've tried with the two simple conditions alone and the script works (condition at the beginning & at the end). Combining conditions always gives the 'atrisk' calculated variable the answer "N". Is there a limitation or syntax difference in Epidata?? > > > > Here's the syntax. thanks for the help. > > > > BEFORE FILE > > DEFINE TOTALPG1 ## GLOBAL > > DEFINE TOTALPG2 ## GLOBAL > > DEFINE varID #### > > END > > > > AFTER RECORD > > TOTALPG1=N1SAD+N2DISCOURA+N3FAILURE+N4SATISFAC+N5GUILT+N6PUNISHED+N7DISAPPOI+N8SELFCRIT+N9SUICIDE+N10CRY+N11IRRITAT > > TOTALPG2=N12INTPPL+N13DECISIO+N14LOOKWOR+N15CANWORK+N16SLEEP+N17TIRED+N18APPETIT+N19WEIGHT+N20WORRYHL+N21INTSEX > > TOTAL=TOTALPG1 + TOTALPG2 > > IF N9SUICIDE = 3 or (N9SUICIDE = 2 AND TOTAL >= 16) or TOTAL > 42 > > THEN > > ATRISK="Y" > > ELSE > > ATRISK="N" > > ENDIF > > END > > > > idnum > > MUSTENTER > > REPEAT > > AFTER ENTRY > > VarID=IDNUM > > END > > END > > > > total > > NOENTER > > END > > > > atrisk > > NOENTER > > END > > > > n1sad > > RANGE 0 3 > > END > > > > etc. for the other variables > > > > > > John LeBlanc > > __________________________________________________________ > > > > John C. LeBlanc, MD, MSc, FRCPC > > Associate Professor > > Pediatrics, Psychiatry, Community Health and Epidemiology > > Dalhousie University > > > > IWK Health Centre Work phone: (902) 470-8930 > > 5850 University Avenue Work fax: (902) 470-6913 > > Halifax, Nova Scotia Email: John.LeBlanc(a)Dal.Ca > > B3K 6R8 CANADA Pager: (902) 470-8888 > > __________________________________________________________ > > > > > > ------------------------------ > > > > ________________________________________ > > EpiData-list(a)lists.umanitoba.ca > > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > > > > End of EpiData-list Digest, Vol 53, Issue 3 > > ******************************************* > > > > > > -- > Ziad El-Khatib > AIDS Unit > National Institute for Communicable Diseases (NICD) > 1 Modderfontein Road > Private Bag X4, Sandringham, 2131 > Johannesburg, South Africa > Mobile: +27 (0) 72-52 39 716 > Phone: +27 (0) 11-386 6433 > Fax (NICD): +27 (0)11 386 6453 > Fax (alternative): +27 (0)866 18 2871 > http://www.nicd.ac.za/ > > Division of International Health (IHCAR) > Karolinska Institutet > www.phs.ki.se/ihcar > > > ------------------------------ > > Message: 2 > Date: Fri, 07 Mar 2008 13:06:35 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] 2 questions (showing labels while entering > data/copy records) > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <47D12FCB.8050109(a)psych.ru.nl> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hello, > > I built some data entry files for entering the questionnaires of my > research. There are 2 dilemmas I don't how to solve and which I cannot > find in the help menu. > 1. Is it possible to see the labels (like 0 = no; 1 = yes) while > entering data? How? > 2. Some students will help me entering data on different computers (so I > copied the datafiles and put it on those computers). Is it possible to > copy records so I can put them in the end all together in the original > datafile on my computer? If yes, how? > > I hope some-one can answer my two questions > > Floor van Santvoort > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > >

1 0

Re: EpiData-list Digest, Vol 53, Issue 3
by epidata-list＠lists.umanitoba.ca 06 Mar '08

06 Mar '08

Dear Pedro, Thank you for your kind reply. I plan to review medical records using paper form. Expecting to have 1 observation at baseline to be entered in baseline file and 6-24 observations for time of follow-up, will be entered in follow-up file. Then data will be entered twice and compared (around 600 patients in total). I am trying to find an alternative way to collect data using papers. Palm would be solution but more expensive etc.. Thank you in advance and best regards ziad On Thu, Mar 6, 2008 at 10:02 AM, <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. Re: EpiData-list Digest, Vol 53, Issue 2 - Review Medical > records (epidata-list(a)lists.umanitoba.ca) > 2. Re: CHK file with calculations does not work as it did in > EpiInfo (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 6 Mar 2008 09:13:47 -0300 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Re: EpiData-list Digest, Vol 53, Issue 2 - > Review Medical records > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <a37cfb5a0803060413m190e2205jb408707648dbca2a(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Dear Ziad, > > Your question is rather non specific, but I ve been through a similar > experience with some bad memories. > > Review medical records is not an easy task. First of all, the type of study > > (for exemple a suvival analysis) is of extremem importance on how the data > > should be organized. Then you must decide what information should be > > extracted from the records. Going back to the records a second or third time > > is really frustrating and time consuming. In general for ARV, to register > > all the ARV combinations, with the start dates and end dates, all CD4 cell > > counts and Viral loads with their respective dates, all diagnosis of > > oportunistic infections and their respective dates of diagnosis. Also, you > > shlould consider making a separate data entry for each one of this data or > > all of them in the same data entry, if you have someone experience in this > > tipe of data analyis, the separate way will make easier to extract and type. > > To use the AUTOSEARCH LIST command in the check file will be of help. Also > > dont forget a field if the ARV is HAART or not and an outcome such as death > > and/or hospitalization and of course its date. > > > > Good Luck, > Pedro Brasil > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Tue, 4 Mar 2008 10:16:56 -0800 > > From: epidata-list(a)lists.umanitoba.ca > > Subject: [EpiData-list] Using EpiData to review medical records > > To: epidata-list(a)lists.umanitoba.ca > > Message-ID: > > <897a5cf60803041016y396e0f9dwf0baa18ba3168469(a)mail.gmail.com> > > Content-Type: text/plain; charset=ISO-8859-1 > > > > Dear EpiDataLister, > > It is semi-technical question. I intend to review medical records > > retrospectively for patients on ARVs. It seems to be involving lot of > > papers to review their history to be able to enter them into EpiData. > > Meant to check if someone had similar experience to share how did you > > sort it out? > > > > Thank you in advance and best regards > > ziad > > > > > > > > > ------------------------------ > > Message: 2 > Date: Wed, 5 Mar 2008 22:28:28 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Re: CHK file with calculations does not work > as it did in EpiInfo > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: <200835222828.983160@IW2575> > Content-Type: text/plain; charset="iso-8859-1" > > Thanks Hans, I don't know what happened. This is what was pasted except that I exchanged the double quotes for single quotes in case that is why text got truncated. > > IF N9SUICIDE = 3 or (N9SUICIDE = 2 AND TOTAL >= 16) or TOTAL > 42 > THEN > ATRISK='Y' > ELSE > ATRISK='N' > ENDIF > END > > John LeBlanc > ----------------------------------------- > Message: 2 > Date: Tue, 04 Mar 2008 20:10:27 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] CHK file with calculations does not work > as it did in EpiInfo > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <47CD9EA3.5000402(a)tbrieder.org> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Unless, something go lost, there is surely something missing here: > > IF N9SUICIDE = or (N9SUICIDE = 2 AND TOTAL >= 16) or TOTAL > 42 > > > Hans > > > John LeBlanc > > > On Tue, 4 Mar 2008 12:50:55 -0400, John LeBlanc wrote: > Hi, > > I wonder if someone can spot the syntax problem in this CHK file for the Beck Depression inventory. I've struggled for hours to get it to work the way it did under Epi Info. Basically, there are three conditions in an IF statement. I've tried with the two simple conditions alone and the script works (condition at the beginning & at the end). Combining conditions always gives the 'atrisk' calculated variable the answer "N". Is there a limitation or syntax difference in Epidata?? > > Here's the syntax. thanks for the help. > > BEFORE FILE > DEFINE TOTALPG1 ## GLOBAL > DEFINE TOTALPG2 ## GLOBAL > DEFINE varID #### > END > > AFTER RECORD > TOTALPG1=N1SAD+N2DISCOURA+N3FAILURE+N4SATISFAC+N5GUILT+N6PUNISHED+N7DISAPPOI+N8SELFCRIT+N9SUICIDE+N10CRY+N11IRRITAT > TOTALPG2=N12INTPPL+N13DECISIO+N14LOOKWOR+N15CANWORK+N16SLEEP+N17TIRED+N18APPETIT+N19WEIGHT+N20WORRYHL+N21INTSEX > TOTAL=TOTALPG1 + TOTALPG2 > IF N9SUICIDE = 3 or (N9SUICIDE = 2 AND TOTAL >= 16) or TOTAL > 42 > THEN > ATRISK="Y" > ELSE > ATRISK="N" > ENDIF > END > > idnum > MUSTENTER > REPEAT > AFTER ENTRY > VarID=IDNUM > END > END > > total > NOENTER > END > > atrisk > NOENTER > END > > n1sad > RANGE 0 3 > END > > etc. for the other variables > > > John LeBlanc > __________________________________________________________ > > John C. LeBlanc, MD, MSc, FRCPC > Associate Professor > Pediatrics, Psychiatry, Community Health and Epidemiology > Dalhousie University > > IWK Health Centre Work phone: (902) 470-8930 > 5850 University Avenue Work fax: (902) 470-6913 > Halifax, Nova Scotia Email: John.LeBlanc(a)Dal.Ca > B3K 6R8 CANADA Pager: (902) 470-8888 > __________________________________________________________ > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 53, Issue 3 > ******************************************* > -- Ziad El-Khatib AIDS Unit National Institute for Communicable Diseases (NICD) 1 Modderfontein Road Private Bag X4, Sandringham, 2131 Johannesburg, South Africa Mobile: +27 (0) 72-52 39 716 Phone: +27 (0) 11-386 6433 Fax (NICD): +27 (0)11 386 6453 Fax (alternative): +27 (0)866 18 2871 http://www.nicd.ac.za/ Division of International Health (IHCAR) Karolinska Institutet www.phs.ki.se/ihcar

1 0

Re: EpiData-list Digest, Vol 53, Issue 2 - Review Medical records
by epidata-list＠lists.umanitoba.ca 06 Mar '08

06 Mar '08

Dear Ziad, Your question is rather non specific, but I ve been through a similar experience with some bad memories. Review medical records is not an easy task. First of all, the type of study > (for exemple a suvival analysis) is of extremem importance on how the data > should be organized. Then you must decide what information should be > extracted from the records. Going back to the records a second or third time > is really frustrating and time consuming. In general for ARV, to register > all the ARV combinations, with the start dates and end dates, all CD4 cell > counts and Viral loads with their respective dates, all diagnosis of > oportunistic infections and their respective dates of diagnosis. Also, you > shlould consider making a separate data entry for each one of this data or > all of them in the same data entry, if you have someone experience in this > tipe of data analyis, the separate way will make easier to extract and type. > To use the AUTOSEARCH LIST command in the check file will be of help. Also > dont forget a field if the ARV is HAART or not and an outcome such as death > and/or hospitalization and of course its date. > Good Luck, Pedro Brasil ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 4 Mar 2008 10:16:56 -0800 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Using EpiData to review medical records > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <897a5cf60803041016y396e0f9dwf0baa18ba3168469(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Dear EpiDataLister, > It is semi-technical question. I intend to review medical records > retrospectively for patients on ARVs. It seems to be involving lot of > papers to review their history to be able to enter them into EpiData. > Meant to check if someone had similar experience to share how did you > sort it out? > > Thank you in advance and best regards > ziad > > >

1 0

CHK file with calculations does not work as it did in EpiInfo
by epidata-list＠lists.umanitoba.ca 05 Mar '08

05 Mar '08

Hi, I wonder if someone can spot the syntax problem in this CHK file for the Beck Depression inventory. I've struggled for hours to get it to work the way it did under Epi Info. Basically, there are three conditions in an IF statement. I've tried with the two simple conditions alone and the script works (condition at the beginning & at the end). Combining conditions always gives the 'atrisk' calculated variable the answer "N". Is there a limitation or syntax difference in Epidata?? Here's the syntax. thanks for the help. BEFORE FILE DEFINE TOTALPG1 ## GLOBAL DEFINE TOTALPG2 ## GLOBAL DEFINE varID #### END AFTER RECORD TOTALPG1=N1SAD+N2DISCOURA+N3FAILURE+N4SATISFAC+N5GUILT+N6PUNISHED+N7DISAPPOI+N8SELFCRIT+N9SUICIDE+N10CRY+N11IRRITAT TOTALPG2=N12INTPPL+N13DECISIO+N14LOOKWOR+N15CANWORK+N16SLEEP+N17TIRED+N18APPETIT+N19WEIGHT+N20WORRYHL+N21INTSEX TOTAL=TOTALPG1 + TOTALPG2 IF N9SUICIDE = 3 or (N9SUICIDE = 2 AND TOTAL >= 16) or TOTAL > 42 THEN ATRISK="Y" ELSE ATRISK="N" ENDIF END idnum MUSTENTER REPEAT AFTER ENTRY VarID=IDNUM END END total NOENTER END atrisk NOENTER END n1sad RANGE 0 3 END etc. for the other variables John LeBlanc __________________________________________________________ John C. LeBlanc, MD, MSc, FRCPC Associate Professor Pediatrics, Psychiatry, Community Health and Epidemiology Dalhousie University IWK Health Centre Work phone: (902) 470-8930 5850 University Avenue Work fax: (902) 470-6913 Halifax, Nova Scotia Email: John.LeBlanc(a)Dal.Ca B3K 6R8 CANADA Pager: (902) 470-8888 __________________________________________________________

1 2

Random selection of records
by epidata-list＠lists.umanitoba.ca 04 Mar '08

04 Mar '08

Dear Jamie, Thank you so much for the solution for the query INCOMPATIBLE KEY VARIABLES. It worked well. Can you please help in two other situation also ? 1. There is a file say try.rec Is it possible to read it and write another file with 5 randomly selected records or selecting every 4th record (as done in systematic sampling). The documentation of the commands such as SET RANDOM SEED and RANDOM SIMULATIONS is not clear in the help file. I am attaching a sample file try.zip. 2.What is the equivalent of SET LISTREC=ON/OFF (EPI6) in Epi Analysis ver 2.03 ? With regards, Dr. Shavinder Singh

1 1

Complex if statements (was chk file with calculations ....)
by epidata-list＠lists.umanitoba.ca 04 Mar '08

04 Mar '08

For the suggested chk file command: > IF N9SUICIDE = 3 or (N9SUICIDE = 2 AND TOTAL >= 16) or TOTAL > 42 > THEN > ATRISK="Y" > ELSE > ATRISK="N" > ENDIF > I would always write: IF ((N9SUICIDE = 3) or ((N9SUICIDE = 2) AND (TOTAL >= 16)) or (TOTAL > 42)) then most likely this would/should also work: IF (N9SUICIDE = 3) or ((N9SUICIDE = 2) AND (TOTAL >= 16)) or (TOTAL > 42) then In other words: Always be very explicit with parenthesis. Test and report please. regards Jens Lauritsen EpiData Association

1 0

Using EpiData to review medical records
by epidata-list＠lists.umanitoba.ca 04 Mar '08

04 Mar '08

Dear EpiDataLister, It is semi-technical question. I intend to review medical records retrospectively for patients on ARVs. It seems to be involving lot of papers to review their history to be able to enter them into EpiData. Meant to check if someone had similar experience to share how did you sort it out? Thank you in advance and best regards ziad

1 0

Screen Flickering in Epidata data entry
by epidata-list＠lists.umanitoba.ca 04 Mar '08

04 Mar '08

I'm using epidata on thinkpad winXP sp2 laptop- all drivers are updated: One "bug" which is very annoying is that the whole screen output constantly flickers and is unstable when I enter data. It seems like the whole screen sort of disappears with every key that is pressed. This bug is only present in the data entry form Is this something which can be prevented?? thanks -- Jannik

1 0

Re: DEFINE var not seen in file structure
by epidata-list＠lists.umanitoba.ca 28 Feb '08

28 Feb '08

Thank you Jens. This is most helpful. Sorry for not replying sooner, had problems with getting connected to the net. I will revise the QES and CHK file accordingly and come back if there are further issues. Again, Many thanks Kindest Regards SK -----Original Message----- From: epidata-list-request(a)lists.umanitoba.ca To: epidata-list(a)lists.umanitoba.ca Sent: Sun, 24 Feb 2008 8:04 pm Subject: EpiData-list Digest, Vol 52, Issue 12 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. DEFINE var not seen in file structure. Answer: Define in entry and in analysis have different consequences (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Sun, 24 Feb 2008 11:04:40 +0100 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] DEFINE var not seen in file structure. Answer: Define in entry and in analysis have different consequences To: epidata-list(a)lists.umanitoba.ca Message-ID: <47C14138.2070103(a)epidata.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed There are two types of variables: 1. Variables which can be saved in files. In Entry these are defined in the qes file, e.g. var1 Label for this variable #### After creating the data file (rec file) and entering data, the data are stored in a rec file In Analysis variables can be created in two ways: a. Define var1 ###### var1 = integer((today-dob)/365.25) label var1 "Age at date of calculation" b gen i var1 = integer((today-dob)/365.25) label var1 "Age at date of calculation" c In both instances (a+b) the values are only kept further on if you issue a saving command: savedata 2. Temporary variables - which are only kept in memory In entry these are defined as SK did: > BEFORE FILE > DEFINE var1 ##### > DEFINE var2 ##### > END In analysis these are defined : (notice "global") define var1 ##### global Temporary variables cannot be saved to a rec file unless the content is transferred to a variable saved in a data file. Sometimes we call variables in data files for "fields" in contrast to what is only in memory. SK could argue that define should do the same in analysis and entry to avoid the confusion. In other words now SK can get the results of the calculation saved for analysis by: Add to the qes file aged Age in days ##### agem Age in months #### chk file. remove the "define" in before file but keep the calculation "let" in the "after entry" block and add this aged noenter end agem noenter end 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 52, Issue 12 ********************************************

1 0

RE: EpiData-list Digest, Vol 52, Issue 13
by epidata-list＠lists.umanitoba.ca 27 Feb '08

27 Feb '08

Merci beacoup - I realised that obvious solution just after I posted the question!! Sorry! Dr Josh Davis NH&MRC Scholar Menzies School of Health Research Staff Specialist in Infectious Diseases and General Medicine Royal Darwin Hospital -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list-request(a)lists.umanitoba.ca Sent: Thursday, 28 February 2008 3:43 AM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 52, Issue 13 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. Incompatible Key Variables (epidata-list(a)lists.umanitoba.ca) 2. Problem with label values (epidata-list(a)lists.umanitoba.ca) 3. Re: Incompatible Key Variables (epidata-list(a)lists.umanitoba.ca) 4. Re: Problem with label values (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: 27 Feb 2008 06:38:27 -0000 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Incompatible Key Variables To: epidata-list-request(a)lists.umanitoba.ca Cc: epidata-list(a)lists.umanitoba.ca Message-ID: <20080227063827.17613.qmail(a)webmail47.rediffmail.com> Content-Type: text/plain; charset="iso-8859-1" Dear Epidata users, I am trying to relate a child file (gm.rec which is growth monitoring data) with the parent file (Under5b.rec, an under 5 children file) The card variable of Under5b.rec is <IDNUM> type while it is numeric in the GM.rec file. After giving the MERGE CARD /FILE=UNDER5B.REC command, I get the following message; Incompatible key variables. Current file: Card of type Float Merge file: Card of type Integer Is there any solution for this problem. Actually IDNUM (automatic counter) is also a numeric variable. EPI6 relates these without any problem. Can any one help please. I am attaching a child.zip file (Under5b.rec and gm.rec in the form of child.zip) for the demonstration of the problem. Waiting for you response. With regards Dr. Shavinder SinghÂ

1 0

Problem with label values
by epidata-list＠lists.umanitoba.ca 27 Feb '08

27 Feb '08

I have several list fields in my datasheet which have more than 9 possible values, and I want to make a label list reflecting this. However. Epidata seems to only allow up to 9. I can;t find documentation on this, but trial and error tells me. Are there any possible solutions? (to clarify, I have: LABEL label_resid 1 abc 2 ddd 3 kk 4 ggg (and then up to 12, and 99 for unknown) 99 unknown END Dr Josh Davis NH&MRC PhD Scholar Menzies School of Health Research and Charles Darwin University Darwin, NT Staff Specialist in Infectious Diseases and General Medicine Royal Darwin Hospital ________________________________

1 1

Incompatible Key Variables
by epidata-list＠lists.umanitoba.ca 27 Feb '08

27 Feb '08

Dear Epidata users, I am trying to relate a child file (gm.rec which is growth monitoring data) with the parent file (Under5b.rec, an under 5 children file) The card variable of Under5b.rec is <IDNUM> type while it is numeric in the GM.rec file. After giving the MERGE CARD /FILE=UNDER5B.REC command, I get the following message; Incompatible key variables. Current file: Card of type Float Merge file: Card of type Integer Is there any solution for this problem. Actually IDNUM (automatic counter) is also a numeric variable. EPI6 relates these without any problem. Can any one help please. I am attaching a child.zip file (Under5b.rec and gm.rec in the form of child.zip) for the demonstration of the problem. Waiting for you response. With regards Dr. Shavinder Singh

1 1

DEFINE var not seen in file structure. Answer: Define in entry and in analysis have different consequences
by epidata-list＠lists.umanitoba.ca 24 Feb '08

24 Feb '08

There are two types of variables: 1. Variables which can be saved in files. In Entry these are defined in the qes file, e.g. var1 Label for this variable #### After creating the data file (rec file) and entering data, the data are stored in a rec file In Analysis variables can be created in two ways: a. Define var1 ###### var1 = integer((today-dob)/365.25) label var1 "Age at date of calculation" b gen i var1 = integer((today-dob)/365.25) label var1 "Age at date of calculation" c In both instances (a+b) the values are only kept further on if you issue a saving command: savedata 2. Temporary variables - which are only kept in memory In entry these are defined as SK did: > BEFORE FILE > DEFINE var1 ##### > DEFINE var2 ##### > END In analysis these are defined : (notice "global") define var1 ##### global Temporary variables cannot be saved to a rec file unless the content is transferred to a variable saved in a data file. Sometimes we call variables in data files for "fields" in contrast to what is only in memory. SK could argue that define should do the same in analysis and entry to avoid the confusion. In other words now SK can get the results of the calculation saved for analysis by: Add to the qes file aged Age in days ##### agem Age in months #### chk file. remove the "define" in before file but keep the calculation "let" in the "after entry" block and add this aged noenter end agem noenter end regards Jens Lauritsen EpiData Association

1 0

Epidata Entry: DEFINE var not seen in file structure or analysis
by epidata-list＠lists.umanitoba.ca 21 Feb '08

21 Feb '08

Dear Epidata Users Hope you can help me understand why this problem is arising. I have created a CHK file with the commends: BEFORE FILE ??? DEFINE var1 ??? DEFINE var2 END ....more code---- var1 and var2 are child age in days and months respectively, computed from date of admission-date of birth; ...code--- dateadm ??? AFTER ENTRY ??? ?? LET aged=dateadm-dob ??? ?? LET agem=(dateadm-dob)/30 ??? END END Now when I try to "File Structure" to see the variables created in the database, I do not see these 2 new variables. Even in Epidata Analysis, after reading the file, these variables do not appear in the variable lsit. Have I missed something? Thanks SK ________________________________________________________________________ More new features than ever. Check out the new AOL Mail ! - http://webmail.aol.com

1 0

EpiData Help in Windows Vista
by epidata-list＠lists.umanitoba.ca 20 Feb '08

20 Feb '08

EpiData Entry users with a Windows Vista machine may experience a problem in reading the EpiData Entry Help file. A plug can be obtained from the MS site that will fox the problem. An EpiData introduction course participant kindly provided me with the link where to get it and I wanted to share it for the record in the EpiData list: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=6eb… Hans

1 0

problem with the Jan 2008 version
by epidata-list＠lists.umanitoba.ca 19 Feb '08

19 Feb '08

I have a problem downloading the current version. Any time I download it I am not able to luanch it.A message will appear that it is currupted. It is the same for the analysis one too. Thank Joe. Akolgo Asampana Joseph Nayag and Sons L .C.S P.O Box 415 Bolga Phone +233-244476218 Ghana ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

1 0

Re: Fording 3 digit ID numbers
by epidata-list＠lists.umanitoba.ca 17 Feb '08

17 Feb '08

This proposed solution has the problem that ID is then a string variable, which will be confusing when you transfer it to STATA, SPSS etc. Another solution would be to not worry about the leading zeros until you have transferred it into STATA, at which point you could use the STATA format command to force it to display as 3 digits. Regards Dr Josh Davis NH&MRC Scholar Menzies School of Health Research Staff Specialist in Infectious Diseases and General Medicine Royal Darwin Hospital -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list-request(a)lists.umanitoba.ca Sent: Sunday, 17 February 2008 3:33 AM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 52, Issue 7 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. Re: forcing 3-digit id numbers (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Sat, 16 Feb 2008 00:42:00 +0100 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] forcing 3-digit id numbers To: epidata-list(a)lists.umanitoba.ca Message-ID: <47B62348.2070106(a)tbrieder.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Vicky: I reproduced your problem, and while perhaps awkward, this seems to be a possible solution: Make an IDN as a numeric field and your ID as a text field: QES: idn ### id ___ sex # In the CHK file you write: idn RANGE 1 150 MUSTENTER AFTER ENTRY id=idn IF idn<10 THEN id="00"+id ENDIF IF (idn>9) and (idn<100) THEN id="0"+id ENDIF END END id KEY UNIQUE 1 NOENTER END and you have your ID as unique identifier in the format you want it to be. Regards, Hans epidata-list(a)lists.umanitoba.ca wrote: > <div class="moz-text-flowed" style="font-family: -moz-fixed">I am > using a unique ID for individuals in a study. The ID must be between > 001 and 150 and it is a 3-character string field to ensure 054 is > entered, for instance, rather than 54. > Certain numbers can be entered with fewer than 3 digits without > generating an error message. Without trying every possible > combination, it seems that these numbers are 1, 10, 11, 12, 13, 14 and > 15. The thing that these seven numbers have in common is that they > could all be extended to 3 digits by filling in only zeroes, and still > meet the criteria for the field (100, 100 again, 110, 120, 130, 140, > 150). 160 is too big for the range, so 16 generates an error message. > 200 is too big, so 2 is not allowed. This is just a guess to explain > why these seven numbers slip through the filter. > If I'm right, is there anything I can do about it? If I'm wrong, > what's the explanation? > Thanks for your help, > Vicky Simms > > King's College London > > > </div> -- Hans L Rieder, MD, MPH Jetzikofenstr. 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 321 9122 Web: http://www.tbrieder.org ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 52, Issue 7 *******************************************

1 0

forcing 3-digit id numbers
by epidata-list＠lists.umanitoba.ca 17 Feb '08

17 Feb '08

I am using a unique ID for individuals in a study. The ID must be between 001 and 150 and it is a 3-character string field to ensure 054 is entered, for instance, rather than 54. Certain numbers can be entered with fewer than 3 digits without generating an error message. Without trying every possible combination, it seems that these numbers are 1, 10, 11, 12, 13, 14 and 15. The thing that these seven numbers have in common is that they could all be extended to 3 digits by filling in only zeroes, and still meet the criteria for the field (100, 100 again, 110, 120, 130, 140, 150). 160 is too big for the range, so 16 generates an error message. 200 is too big, so 2 is not allowed. This is just a guess to explain why these seven numbers slip through the filter. If I'm right, is there anything I can do about it? If I'm wrong, what's the explanation? Thanks for your help, Vicky Simms King's College London

1 2

Re: EpiData-list Digest, Vol 52, Issue 4
by epidata-list＠lists.umanitoba.ca 13 Feb '08

13 Feb '08

Today's Topics: > 1. Updating data is overwriting the .rec file and preventing > further data entry via data entry (epidata-list(a)lists.umanitoba.ca) > > "When I update data in analysis and save it with savedata /replace .And then go to put in more data I can no longer get access to the file in epidata to put more data in. " Several possibilities: 1: There is an error in the software. 2: You are saving the file somewhere and something goes wrong with the rights management to the file. 3: There is a conflict in the elaborated chk file and rec file between Entry and Analysis. In any case can you send a portion of the file in a zip archive to the mail: info at epidata.dk and I will look at it. regards Jens Lauritsen

1 0

Updating data is overwriting the .rec file and preventing further data entry via data entry
by epidata-list＠lists.umanitoba.ca 13 Feb '08

13 Feb '08

Dear Epi Data list When I update data in analysis and save it with savedata /replace . And then go to put in more data I can no longer get access to the file in epidata to put more data in. Please tell me what I am doing wrong. Evonne Evonne Curran SRN, MPH, Dip Infect Cont. Nurse Consultant Infection Control Honorary Lecturer Glasgow University Infection Control Team NHS National Services Scotland Health Protection Scotland 1 Cadogan Square Cadogan Street Glasgow G2 7HF T: +44 (0) 141 300 1151 F: +44 (0) 141 847 0399 www.hps.scot.nhs.uk Please consider the environment before printing this email. NHS National Services Scotland is the common name for the Common Services Agency for the Scottish Health www.nhsnss.org <http://www.nhsnss.org/> _________________________________________________________________ NHS National Services Scotland Disclaimer The information contained in this message may be confidential or legally privileged and is intended for the addressee only. If you have received this message in error or there are any problems please notify the originator immediately. The unauthorised use, disclosure, copying or alteration of this message is strictly forbidden. _________________________________________________________________

1 0

Teaching learning/material in portuguese
by epidata-list＠lists.umanitoba.ca 12 Feb '08

12 Feb '08

Dear Mr JM.Lauritsen, A few months ago I sent an email to the list warning that a learning/teaching material in potuguese that was available at the epidata download website, right beside the download file, (a link to a pdf file) would change because of regulatory matters. Now, back from vacation, I got an email about the new version of EpiData. For curiosity, I try the link for the material in portuguese and the link is broken because the FTP file directory is not available. The same pdf file is available for some time in a HTTP... http://www.pesquisaclinica.ipec.fiocruz.br/modules.php?name=Downloads&op=ge… Jens...If you would like to keep the learning material in portuguese available, please update de link at the EpiData download website. Best regards, -- Abraço forte e que a força esteja com você, Pedro Emmanuel

1 0

Re: EpiData-list Digest, Vol 52, Issue 1
by epidata-list＠lists.umanitoba.ca 02 Feb '08

02 Feb '08

epidata-list-request(a)lists.umanitoba.ca pravi: > 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. News sent out - and analysis b130 ready for testing > (epidata-list(a)lists.umanitoba.ca) > > > ------------------------------------------------------------------------ > > Zadeva: > [EpiData-list] News sent out - and analysis b130 ready for testing > Od: > epidata-list(a)lists.umanitoba.ca > Datum: > Thu, 31 Jan 2008 21:32:18 +0100 > Za: > epidata-list(a)lists.umanitoba.ca > > Za: > epidata-list(a)lists.umanitoba.ca > > > I placed build 130 on the www.epidata.dk/testing.php for download. > > Please see if recently reported bugs are solved as I expect. Most > importantly it will be welcomed if some have the time to see if the > adapted menu system is clear. The change is needed to facilitate > translation. > > Some experimentation can be done with translation but it is not in > place completely. (translators can request material). > > Some issues are still unsolved in v2, such as special types of merge > and other details having the status "unresolved" in the Mantis database. > > A news message has been sent to all 1046 persons registered on the > "receive news from EpiData Association". I am not sure if an error > occurred, but possibly everyone received the message four times > (apologies if this is so). > > Regards > > Jens Lauritsen > EpiData Association > > ------------------------------------------------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > Dear Jens I am interested for translation of EpiDataAnalysis. Please send me files for translation in Slovenian and Serbian languages. Sincerely Marko Kovacevic

1 0

News sent out - and analysis b130 ready for testing
by epidata-list＠lists.umanitoba.ca 31 Jan '08

31 Jan '08

I placed build 130 on the www.epidata.dk/testing.php for download. Please see if recently reported bugs are solved as I expect. Most importantly it will be welcomed if some have the time to see if the adapted menu system is clear. The change is needed to facilitate translation. Some experimentation can be done with translation but it is not in place completely. (translators can request material). Some issues are still unsolved in v2, such as special types of merge and other details having the status "unresolved" in the Mantis database. A news message has been sent to all 1046 persons registered on the "receive news from EpiData Association". I am not sure if an error occurred, but possibly everyone received the message four times (apologies if this is so). Regards Jens Lauritsen EpiData Association

1 0

Export SPSS : name variables length
by epidata-list＠lists.umanitoba.ca 31 Jan '08

31 Jan '08

Hello, When exported from epidata, variables are limited to 8 characters. Recent version of SPSS (V11 and above) allows longer names. Would it be possible to add an option on the export dialog box to allow a length fixed by the user ? A command line option for epic would be necessary to take into account this parameter. In CHK files it is possible to specify MISSING VALUES with the appropriate command. When data are exported to SPSS, the MISSING VALUES syntax is not created. Would it be possible to add this syntax in the next minor release of Epidata ? Thanks for all. Jean-Marie Chrétien Centre de Recherche Clinique CHU ANGERS - FRANCE

1 0

New EpiData Entry v3.1 (build 27Jan2008) uploaded -warning of incorrect counts with analysis tab /cc option
by epidata-list＠lists.umanitoba.ca 28 Jan '08

28 Jan '08

A new compilation of EpiData Entry has been uploaded for all languages. The following bugs have been fixed: Bug fix for export to SPSS (dates) Bug fix jump to noenter field Integers up to 9 digits saved as integer (extended from 4) for compatibility with Analysis Backup relative paths fixed Various other issues, see Mantis database Regarding the long integers (9 digits) - this will be changed in an upload of EpiData Analysis expected later this week. The revised build of analysis will also fix the wrong placement of counts in "Tab ..... /cc" , where there is a misplacement of counts btw. columns. (Mantis issue reported) Until the bugfix has been uploaded get correct counts by also adding the /obs option. E.g. tab case sex ham eggs protein /cc /obs And use the correct counts in the "obs" column. Odds ratios and ChiSq tests are correct. The translation of analysis is in preparation and the implementation of this has revealed need for more clear separation of the various menu parts. Before final upload a testversion will be placed for comments on the testing page. The list will be notified, when this occurs. Regards Jens Lauritsen EpiData Association

1 0

Guide Epidata Analyse en francais
by epidata-list＠lists.umanitoba.ca 21 Jan '08

21 Jan '08

Bonjour, Je vous annonce qu'un guide de EPIDATA Analysis 2.0 est disponible en *.pdf sur le site suivant <http://www.reseau-naissance.fr> http://www.reseau-naissance.fr, page Epidémiologie Ce guide fait 17 pages. Merci de vos avis. PS : A la réflexion, il manque un "config.epi" comme dans EPIINFO pour paramétrer par défaut les résultats des commandes comme les % dans les tableaux comme dans la version 1.0 ! Bernard BRANGER - Médecin coordinateur Réseau de périnatalité "Sécurité Naissance - Naître ensemble" des Pays de la Loire 1, allée Baco - 44000 NANTES Tel 02 40 48 55 81 - Fax 02 40 12 40 72 Courriel : <mailto:bernard.branger@naitre-ensemble-ploire.org> bernard.branger(a)naitre-ensemble-ploire.org Site Internet : <http://www.reseau-naissance.fr> http://www.reseau-naissance.fr _____ J'utilise la version gratuite de SPAMfighter pour utilisateurs privés. 4605 e-mails spam ont été bloqués jusqu'à maintenant. Les utilisateurs payant n'ont pas ce message dans leurs e-mails. Essayez SPAMfighter <http://www.spamfighter.com/lfr> gratuitement maintenant!

1 0

Re: Exporting to SPSS
by epidata-list＠lists.umanitoba.ca 17 Jan '08

17 Jan '08

Hi Bruce, Perhaps one could press just "enter" key without any number (known 999 treated as missing by EpiData) rather than leaving it blank. If you leave it blank without pressing enter EpiData may not recognise it as missing consequently SPSS will not. You will also need to chance the missing code 9 or 999 to SPSS missing code. Kind regards Tieble On 17/01/2008, epidata-list-request(a)lists.umanitoba.ca < 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. Export to SPSS messed up by missing data > (epidata-list(a)lists.umanitoba.ca) > 2. Re: Export to SPSS messed up by missing data > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 16 Jan 2008 15:50:29 -0500 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Export to SPSS messed up by missing data > To: "EpiData List" <epidata-list(a)lists.umanitoba.ca> > Message-ID: > <73dc8140801161250k4c49d36bge7101df054e1727e(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hello folks. I just noticed that when I export to SPSS, things can end up > either missing or in the wrong columns when there are empty fields in the > .rec file. Here's a simple example I generated to test it. I created a > .qes file that looks like this: > > {string1} String variable 1 __________ > {num1} Numeric variable 1 ## > {datevar1} Date variable 1 <yyyy/mm/dd> > > {string2} String variable 2 __________ > {num2} Numeric variable 2 ## > {datevar2} Date variable 2 <yyyy/mm/dd> > > {string3} String variable 3 __________ > {num3} Numeric variable 3 ## > {datevar3} Date variable 3 <yyyy/mm/dd> > > ------------------------------- > > Then I entered a couple rows of data, with complete data on row 1, but > incomplete data on row 2 (num1 and datevar 1 were left blank). > When I export to Excel, I get the following (which is correct): > > STRING1 NUM1 DATEVAR1 STRING2 NUM2 DATEVAR2 STRING3 NUM3 > DATEVAR3 > record 1.1 1 06/01/2008 record 1.2 2 . rec 1.3 3 > 06/01/2008 > rec 2.1 . . rec 2.2 22 01/01/2008 rec 2.3 23 > 02/01/2008 > > But if I export to SPSS, I get this, which is not correct: > > STRING1 NUM1 DATEVAR1 STRING2 NUM2 DATEVAR2 STRING3 NUM3 > DATEVAR3 > record 1.1 1 01/06/2008 record 1.2 2 01/16/2008 rec 1.3 3 > 01/06/2008 > rec 2.1 . . 2201/01/20 8 . 2301/02/20 > 8 . > > My first thought was that SPSS 16 is lousing things up. (I've been forced > to upgrade from v15 due to an institutional decision, and I've noticed > several other problems with v16). But the same problem occurred when I > tried on another machine running SPSS 11. > > Has anyone else run into this? I didn't find any mention of it in the > archives. > > What I'm doing for now to circumvent the problem is this: > > 1) Exporting to SPSS to get syntax for all the variable and value labels > 2) Exporting to Excel to get the data into a format I can read with SPSS > 3) Creating syntax to import the Excel file, then adding the variable and > value label syntax generated by exporting to SPSS. > > It's not terribly more complicated than a straight export to SPSS, but it > would be nice if I could do it in one step. > > By the way, I'm running EpiData 3.1 on a ThinkPad (XP Professional, SP2, 4 > gigs of memory IIRC). > > Thanks, > Bruce > > -- > Bruce Weaver > bweaver(a)lakeheadu.ca > www.angelfire.com/wv/bwhomedir > "When all else fails, RTFM." > > > ------------------------------ > > Message: 2 > Date: Thu, 17 Jan 2008 09:34:49 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Export to SPSS messed up by missing data > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <478F1329.8000402(a)fifas.de> > Content-Type: text/plain; charset="iso-8859-1" > > Hello Bruce, > > I had a similar problem, when I exported strings with a length of 80 > characters, which is the maximum. The datalist-syntax for spss was wrong > and imported only 79 (!) characters, so that the following variables > started one column to the left. If the following variable is numeric > with the lenght 1, it will be missing. > > Regards > Juergen > > > epidata-list(a)lists.umanitoba.ca schrieb: > > Hello folks. I just noticed that when I export to SPSS, things can end > up > > either missing or in the wrong columns when there are empty fields in > the > > .rec file. Here's a simple example I generated to test it. I created a > > .qes file that looks like this: > > > > {string1} String variable 1 __________ > > {num1} Numeric variable 1 ## > > {datevar1} Date variable 1 <yyyy/mm/dd> > > > > {string2} String variable 2 __________ > > {num2} Numeric variable 2 ## > > {datevar2} Date variable 2 <yyyy/mm/dd> > > > > {string3} String variable 3 __________ > > {num3} Numeric variable 3 ## > > {datevar3} Date variable 3 <yyyy/mm/dd> > > > > ------------------------------- > > > > Then I entered a couple rows of data, with complete data on row 1, but > > incomplete data on row 2 (num1 and datevar 1 were left blank). > > When I export to Excel, I get the following (which is correct): > > > > STRING1 NUM1 DATEVAR1 STRING2 NUM2 DATEVAR2 STRING3 NUM3 > > DATEVAR3 > > record 1.1 1 06/01/2008 record 1.2 2 . rec 1.3 3 > > 06/01/2008 > > rec 2.1 . . rec 2.2 22 01/01/2008 rec 2.3 23 > > 02/01/2008 > > > > But if I export to SPSS, I get this, which is not correct: > > > > STRING1 NUM1 DATEVAR1 STRING2 NUM2 DATEVAR2 STRING3 NUM3 > > DATEVAR3 > > record 1.1 1 01/06/2008 record 1.2 2 01/16/2008 rec 1.3 3 > > 01/06/2008 > > rec 2.1 . . 2201/01/20 8 . 2301/02/20 > > 8 . > > > > My first thought was that SPSS 16 is lousing things up. (I've been > forced > > to upgrade from v15 due to an institutional decision, and I've noticed > > several other problems with v16). But the same problem occurred when I > > tried on another machine running SPSS 11. > > > > Has anyone else run into this? I didn't find any mention of it in the > > archives. > > > > What I'm doing for now to circumvent the problem is this: > > > > 1) Exporting to SPSS to get syntax for all the variable and value labels > > 2) Exporting to Excel to get the data into a format I can read with SPSS > > 3) Creating syntax to import the Excel file, then adding the variable > and > > value label syntax generated by exporting to SPSS. > > > > It's not terribly more complicated than a straight export to SPSS, but > it > > would be nice if I could do it in one step. > > > > By the way, I'm running EpiData 3.1 on a ThinkPad (XP Professional, SP2, > 4 > > gigs of memory IIRC). > > > > Thanks, > > Bruce > > > > > > -- > *********************************************************** > Freiburger Institut fuer angewandte Sozialwissenschaft e.V. > FIFAS > Erasmusstr. 16, D-79098 Freiburg > Telefon: (0761) 28 83 64 Fax: (0761) 29 27 493 > Web: www.fifas.de > E-Mail: info(a)fifas.de > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 51, Issue 3 > ******************************************* >

1 0

Alyshia Landry is out of the office.
by epidata-list＠lists.umanitoba.ca 17 Jan '08

17 Jan '08

I will be out of the office starting 01/15/2008 and will not return until 01/23/2008. If you require immediate assistance, please contact Stephen Drew at extension 5330. Thank-you and have an excellent day, Alyshia

1 0

Export to SPSS messed up by missing data
by epidata-list＠lists.umanitoba.ca 17 Jan '08

17 Jan '08

Hello folks. I just noticed that when I export to SPSS, things can end up either missing or in the wrong columns when there are empty fields in the .rec file. Here's a simple example I generated to test it. I created a .qes file that looks like this: {string1} String variable 1 __________ {num1} Numeric variable 1 ## {datevar1} Date variable 1 <yyyy/mm/dd> {string2} String variable 2 __________ {num2} Numeric variable 2 ## {datevar2} Date variable 2 <yyyy/mm/dd> {string3} String variable 3 __________ {num3} Numeric variable 3 ## {datevar3} Date variable 3 <yyyy/mm/dd> ------------------------------- Then I entered a couple rows of data, with complete data on row 1, but incomplete data on row 2 (num1 and datevar 1 were left blank). When I export to Excel, I get the following (which is correct): STRING1 NUM1 DATEVAR1 STRING2 NUM2 DATEVAR2 STRING3 NUM3 DATEVAR3 record 1.1 1 06/01/2008 record 1.2 2 . rec 1.3 3 06/01/2008 rec 2.1 . . rec 2.2 22 01/01/2008 rec 2.3 23 02/01/2008 But if I export to SPSS, I get this, which is not correct: STRING1 NUM1 DATEVAR1 STRING2 NUM2 DATEVAR2 STRING3 NUM3 DATEVAR3 record 1.1 1 01/06/2008 record 1.2 2 01/16/2008 rec 1.3 3 01/06/2008 rec 2.1 . . 2201/01/20 8 . 2301/02/20 8 . My first thought was that SPSS 16 is lousing things up. (I've been forced to upgrade from v15 due to an institutional decision, and I've noticed several other problems with v16). But the same problem occurred when I tried on another machine running SPSS 11. Has anyone else run into this? I didn't find any mention of it in the archives. What I'm doing for now to circumvent the problem is this: 1) Exporting to SPSS to get syntax for all the variable and value labels 2) Exporting to Excel to get the data into a format I can read with SPSS 3) Creating syntax to import the Excel file, then adding the variable and value label syntax generated by exporting to SPSS. It's not terribly more complicated than a straight export to SPSS, but it would be nice if I could do it in one step. By the way, I'm running EpiData 3.1 on a ThinkPad (XP Professional, SP2, 4 gigs of memory IIRC). Thanks, Bruce -- Bruce Weaver bweaver(a)lakeheadu.ca www.angelfire.com/wv/bwhomedir "When all else fails, RTFM."

1 1

How to: relate files - how can I get only one record in sub files for each main record ?
by epidata-list＠lists.umanitoba.ca 03 Jan '08

03 Jan '08

Hi, This is fine but I want to have a field in the middle of the form that determines whether to stop and save the record and return to File A or to relate to another file. If the value is 1 save and return. If the value is 2 continue entering data. v4 AFTER ENTRY IF V4 = 2 THEN RELATE id fileC ELSE GOTO WRITE ENDIF END But this (GOTO WRITE) doesn't quite work. Epidata saves the record ok, and returns to File a but then somehow returns to File b in Read Only mode. My structure is exactly as below. I'd like to stay in file a. Note, F10 does not work in this case. I have to use mouse to close. Thanks....Edward ------- Ziad asked: How to go for new record if you have two parts in EpiData? >/ I have database made of two parts. When we finish data entry in "part 2", />/ instead of moving to new record file, and we expect to see part 1, we get />/ new record file in part 2. />/ /I assume the situation is this: a. enter data into file A b. at latest field in file A perform a relate to file B based on unique ID c. continue with more data in B d. at last field in file B you wish to continue with next record in file A. IF you specify in file A last field: after entry relate id fileB end Then after entering last field in file B you will have a new record in file B, but if you instead: after entry relate id fileB 1 end then only one record will be entered in file B and you will return to file A Example: qes files: file a: id <IDNUM> v1 first field # v2 date <dd/mm/yyyy> v3 relate # file b: id ##### v1 first field # v2 date <dd/mm/yyyy> v3 relate # Chk files: file a: id KEY UNIQUE 1 END v3 AFTER ENTRY RELATE id fileb 1 END END file b: id KEY UNIQUE 1 END Kind regards Jens Lauritsen EpiData Association -- (\_ _/) (='.'=) ('')_('') -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

1 0

Substring function in EpiData Entry
by epidata-list＠lists.umanitoba.ca 01 Jan '08

01 Jan '08

Happy New Year to all! In EpiData Analysis, you can state: if substr(varx,3,2)="YY" then vary="XX" Would anybody know if there is an equivalent to that in EpiData Entry? Thank you, Hans

1 1

EpiData Analysis - difference error and information
by epidata-list＠lists.umanitoba.ca 25 Dec '07

25 Dec '07

As a follow up on the question reported to the list (in Spanish) I agree we should change: EpiData Analysis, such that error: if syntax of a given command is insufficient or erroneous examples: wrong variable name trying to read data without close information: all situations where an "expected" result did not happen, examples: no data in a variable name of file just read trying to drop variable which does not exist Report comments or situations , where the rule was not applied (once implemented) Another issue is translation. This will start for analysis. And also a translation tool will be developed Regards and happy new year to all. Thanks for support and comments over the previous year. Jens Lauritsen EpiData Association

1 0