February 2007 - EpiData-list - University of Manitoba Mailing Lists

Re: [EpiData-list] Entering time and date for outbreaks
by epidata-list＠lists.umanitoba.ca 28 Feb '07

28 Feb '07

Hi Charity Thanks very much for your formula. Its sounds really good. I had a go at putting it in a check file. Following through your example below 'Diatime' is my 'vtime2' and 'diadate' is my vdate2. I thought I would start off slowly by seeing if I coudl calculate Vhours2. I created a new field called Vhours2 in my rec file and then I put the following code into the check file. DIATIME AFTER ENTRY LET VHOURS2=INT(DIATIME)+(FRAC(DIATIME)/0.6)+(DIADATE*24) END END Epi accepted the code but nothing appears in the vhours2 field when I enter information in the diadate and diatime fields. Can you see what I am doing wrong? thanks Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 >>> <epidata-list(a)lists.umanitoba.ca> 26/02/2007 7:24 p.m. >>> Hello Chrsitine, I prefer to enter times as a decimal field, i.e. ##.##. I can then put checks in place to make sure the minutes are in correct time format e.g. IF Frac(vtime) > 0.59 THEN .... Based on this decimal 24 hour time format, I have a formula which you can use to calculate the difference in hours between two time and date combinations. Assume that your first time and date are vtime1 and vdate1, and your second time and date are vtime2 and vdate2: First calculate the number of hours (since 31st December 1899) for both time and date combinations (store them as vhours1 and vhours2) using the following formulae: vhours2=Int(vtime2) + (Frac(vtime2)/0.6) + (vdate2*24) vhours1=Int(vtime1) + (Frac(vtime1)/0.6) + (vdate1*24) And then you can just calculate the time difference /incubation period into a different variable! timediff=vhours2-vhours1 You could also have done something similar and perhaps simpler using EpiData's Time2Num function which will convert a decimal time into a number between 0 and 1 representing a fraction of a day - I just prefer to work with hours. To explain the hours calculation formula for you (only need to read below if you care how the formula works): Int(vtime) takes the integer part of the time, and Frac(vtime) takes the fractional part of the time. These are separated so Frac(vtime) alone can be converted from minutes into fraction of an hour (e.g. from 0.30 to 0.50). The date integer (representing the number of days since 31 Dec 1899) is then multiplied by 24 to get the number of hours since 31 Dec 1899. This 1899 date is relevant only because it is how EpiData stores the date as an integer - we do not have to worry about this because we only care about the difference between the two dates. Hope this helps! Charity Charity Jenkins Data Processing Officer Centre for Behavioural Research in Cancer The Cancer Council Victoria http://www.cancervic.org.au/cbrc<https://webmail.accv.org.au/exchweb/bin/redir.asp?URL=http://www.cancervic.…> On 2/26/07, epidata-list(a)lists.umanitoba.ca <epidata-list(a)lists.umanitoba.ca> wrote: > > Hello everyone > > I am after advice about the best way to record time and date > information when collecting information about food poisoning outbreaks, > given epidata does not have a time/date field. We want this information > to estimate incubation periods, in order to get clues about the likely > illness. > > Incubation > Incubation = time from when someone is exposed to the time they become > unwell. > For example someone may eat a buffet meal at 7pm on 21 February and > become unwell at 1am on 22 February = incubation of 6 hours. > > Current method > At the moment we: > a) enter information in two fields. OnsetDay is recorded in a date > field, and onsettime in a numeric field (####) > b) list the two fields (using epi info) to view the information > c) calculate incubation manually. > > Is there a better/easier way to do this? Also what is the recommended > way for entering 24 clock time - should 7.30pm be 1930 or 19.30 > > thanks very much > > 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 ** > > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > -- 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 4

work-arounds for data entry on more than one computer
by epidata-list＠lists.umanitoba.ca 28 Feb '07

28 Feb '07

Epi-Data users: What strategies have you used to get around the limitation of only being able to input the data on one computer? We are thinking of splitting the file into two - with Type A respondents in one file/on one computer and Type B respondents in another file/on a different computer and then combining the resulting datasets in Stata. Will this work? Are there other/better strategies? Thanks, Kristine Hopkins khopkins(a)prc.utexas.edu

1 3

Re: [EpiData-list] Entering time and date for outbreaks
by epidata-list＠lists.umanitoba.ca 28 Feb '07

28 Feb '07

Hi Charity I have tried adapting that check code to my file, just changing the field names as necessary, and it worked perfectly. How exciting to see my incubation times popping up effortlessly! Thanks very much for that. Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 >>> <epidata-list(a)lists.umanitoba.ca> 27/02/2007 12:24 p.m. >>> Hi Christine, I think I forgot to mention that for vhours to be a field it needs to be fairly large as the number of hours since 1899 is a big number. Also it needs to have two decimal places. I used a nine digit number plus two decimals when I tried it. Once you know you have it working you could calculate the difference directly into the timediff field (which also needs two decimal places but does not need to be nearly as large) without having to store it in vhours1 and vhours2 first, to save having meaningless numbers lying about. Also, I didn't use the word "LET" - not sure if this makes any difference. And the number will not calculate until all the fields in the formula are filled, i.e. if you put the code in the time field but do not yet have anything in the date field, it will not work. I put the full calculation in all fields so that any time a field was updated the difference would update also. I will paste what I did below and hopefully it will clear anything else up I've forgotten to mention! Let me know how you go. Thanks, Charity Below is the text from the qes file I used to test my formulae. vtime1 ##.## vdate1 <dd/mm/yyyy> vhours1 #########.## vtime2 ##.## vdate2 <dd/mm/yyyy> vhours2 #########.## timediff ####.## And the code I used in my chk file (for the second time and date only, to save space): vtime2 MUSTENTER AFTER ENTRY IF (vtime2 < 0) OR (vtime2 > 23.59) OR (Frac(vtime2) > 0.59) THEN HELP "Enter a valid time" GOTO vtime2 ENDIF vhours2=Int(vtime2) + (Frac(vtime2)/0.6) + (vdate2*24) vhours1=Int(vtime1) + (Frac(vtime1)/0.6) + (vdate1*24) timediff=vhours2-vhours1 END END vdate2 MUSTENTER AFTER ENTRY vhours2=Int(vtime2) + (Frac(vtime2)/0.6) + (vdate2*24) vhours1=Int(vtime1) + (Frac(vtime1)/0.6) + (vdate1*24) timediff=vhours2-vhours1 END END vhours2 NOENTER END Charity Jenkins Data Processing Officer Centre for Behavioural Research in Cancer The Cancer Council Victoria http://www.cancervic.org.au/cbrc<https://webmail.accv.org.au/exchweb/bin/redir.asp?URL=http://www.cancervic.…> On 2/27/07, epidata-list(a)lists.umanitoba.ca <epidata-list(a)lists.umanitoba.ca > wrote: > > Hi Charity > > Thanks very much for your formula. Its sounds really good. I had a go > at putting it in a check file. Following through your example below > 'Diatime' is my 'vtime2' and 'diadate' is my vdate2. I thought I would > start off slowly by seeing if I coudl calculate Vhours2. I created a new > field called Vhours2 in my rec file and then I put the following code > into the check file. > > > DIATIME > AFTER ENTRY > LET VHOURS2=INT(DIATIME)+(FRAC(DIATIME)/0.6)+(DIADATE*24) > END > END > > Epi accepted the code but nothing appears in the vhours2 field when I > enter information in the diadate and diatime fields. Can you see what I > am doing wrong? > > > thanks > > 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

date time difference and age calculation
by epidata-list＠lists.umanitoba.ca 26 Feb '07

26 Feb '07

In writing documentation, help file, how to's, faq solutions etc. the problem is not so much to give solutions, but how to write solutions in a way where users actually find them. For the age calculation if you look in EpiData Entry file under "time functions" you will see: ................... LET INT1=(ROUND(INT((TODAY-D1)/365.25)) Calculates the age of a person whose date of birth was entered in D1. Round is needed to convert the result of the calculation from a real number to a integer number. ................... and if you look in the help file for entry under "time functions" or "time about" or "Age on specific date" one example clearly shows how to do the calculations questioned on the list recently. The time example is also included with the installation of the Entry programme. I am not saying this to "point fingers" at the recent questioning on this list, but to underline that despite the amount of documentation, field notes, help files etc. it is my firm conviction that there is a definite need for a lively help line. For users following the Stata list or having used the very large volume of documentation and help facilities for Stata (www.stata.com) you will notice that also on that list questions shows up on issues actually explained but users not finding them. In other words: We can and should include obvious "often asked issues" in documentation, but even if we do, there will be someone not finding this information. Which is exactly why a large user base where someone find and take the time to answer these questions on the EpiData list is very important. Regards Jens Lauritsen EpiData Association

1 0

Entering time and date for outbreaks
by epidata-list＠lists.umanitoba.ca 26 Feb '07

26 Feb '07

Hello everyone I am after advice about the best way to record time and date information when collecting information about food poisoning outbreaks, given epidata does not have a time/date field. We want this information to estimate incubation periods, in order to get clues about the likely illness. Incubation Incubation = time from when someone is exposed to the time they become unwell. For example someone may eat a buffet meal at 7pm on 21 February and become unwell at 1am on 22 February = incubation of 6 hours. Current method At the moment we: a) enter information in two fields. OnsetDay is recorded in a date field, and onsettime in a numeric field (####) b) list the two fields (using epi info) to view the information c) calculate incubation manually. Is there a better/easier way to do this? Also what is the recommended way for entering 24 clock time - should 7.30pm be 1930 or 19.30 thanks very much 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 1

Current age calculation
by epidata-list＠lists.umanitoba.ca 26 Feb '07

26 Feb '07

Thank you Jamie for today mornings message. I was confused by the complex syntax of American date selection This solution was also obtained over the week end while working on a Fedora Linux machine on which Epidata entry and Analysis latest versions were installed.. Simple formulas, which produced wonders, are given below; define interval ### let interval=wdate - dbirth *calculate the interval in days using American dates. define interval ### let interval=(wdate dbirth)30.44 results in a error Data type mismatch define interval ###.# let interval=(wdate dbirth)/30.44 calculates the interval months using American dates. Epi Analysis accepts float type variables as suggested by Gillis Delmas. However round or integer prefix do not help. The output is produced in decimals and not rounded to the nearest figure. I wanted to obtain the current age hence did not include this formula in Epidata Entry as suggested by Pedro Emmanuel Brasil One request to Jens; Such examples should be included in the help file in the form of simple FAQs, which can save hours or even days of Epi Analysis Users (beginner and even experienced!!). Thank you friends for your timely help Much appreciated Dr. Shavinder Singh

1 0

Age Calculation
by epidata-list＠lists.umanitoba.ca 24 Feb '07

24 Feb '07

Dear Friends, Thanks for your time and effort. I tried in so many many ways. Nothing is working. I am attching a sample file with following PGM. The error message obtained are shown in the next line beginning with "*" Kindly help. With regards, Dr. Shavinder Singh *Try.pgm cls close set echo=off set replace logfile=on read "d:\work\amdate.rec" define wdateu <DD/MM/YYYY> LET wdateu=wdate define dbirthU <DD/MM/YYYY> LET dbirthU=dbirth logopen "TRY.PGM OUTPUT FILE" /CLOSE define interval ### let interval=date("wdateu","dmy")- date("dbirthu","dmy") list Interval *Error message - (NO RESPONSE) define interval2 ### let interval2=Integer(date("wdate" - "dbirth")) list Interval2 *Error message Access violation at address 006C91D6 in module 'EPIDATASTAT.EXE'. Read of address FFFFFFFF define interval3 ### let interval3=Integer(date("wdate") - date("dbirth")) list Interval3 *Error message - (NO RESPONSE) define interval4 ### let interval4=Integer(round(date("wdate","mdy")- date("dbirth","mdy"))) list Interval4 *Error message -(NO RESPONSE) close

1 1

<IDNUM> in statusbar!!
by epidata-list＠lists.umanitoba.ca 24 Feb '07

24 Feb '07

Hi Jamie, thanks for helping me out with the <IDNUM> problem! You also answered my other question about how to show the <IDNUM> in the statusbar. Bye, Ben.

1 0

showing <IDNUM> in statusbar
by epidata-list＠lists.umanitoba.ca 23 Feb '07

23 Feb '07

Hi all, Thanks Juergen for your valuable tip to use respnumber TYPE SATUSBAR end to show the value of field 'respnumber' in the statusbar during data entry! I'm quite unexperienced in using epidata and didn't know of this nice feature. Still I have a question. Is it also possible to show the value of the automatic IDNUM field in the statusbar? The reason for this question is that I do not want to enter the respondent number myself, but would like to use the automatically generated IDNUM instead. More or less related is the next question. If one uses the following two lines (look quite meaningless, I agree) <IDNUM> <IDNUM> in the QES file, then why does, during data entry, the first <IDNUM> always stay 1 - even after entering the second, third etc. case - while the second <IDNUM> is adjusted to the correct case number, i.e., the one who's data are currently being entered? Bye and thanks for any help, Ben.

1 0

Showing IDNUM at top of 2 or more entry screens
by epidata-list＠lists.umanitoba.ca 23 Feb '07

23 Feb '07

Hi all, With many fields to enter, the QES file of epidata can easily become very large and cover 2 (or even more) subsequent screens. While entering the data, after having filled in the last field of screen 1, there will be a continuous scrolling down after each next field is entered. To prevent this continuous scrolling of the screen, one can use the TOPOFSCREEN command in the CHK file, which places the field in question at the top of the second entry screen. This results in a more steady (over)view during data entry, which I think is preferable. Now to my question. At the top of the first screen I show the value of the automatic <IDNUM> field, which corresponds with the respondent number written on the questionnaires. Is there a way to have this <IDNUM> shown at the top of EACH new data entry screen? I've tried this by simply putting the text respondent: <IDNUM> at the top of each new screen. However, this didn't work well, since after the entry and saving of record 1, the next empty datarecord for case 2 is shown, but instead of showing respondent 2 it shows respondent 1 while at the second screen it shows respondent 2 Probably I'm doing something strange, with showing the IDNUM field more then one time in the same REC file. Does anyone know a method to manage this problem? Thanks, Ben.

1 1

IDNUM at top of each data entry screen?
by epidata-list＠lists.umanitoba.ca 22 Feb '07

22 Feb '07

Hi all, With many fields to enter, the QES file of epidata can easily become very large and cover 2 (or even more) subsequent screens. While entering the data, after having filled in the last field of screen 1, there will be a continuous scrolling down after each next field is entered. To prevent this continuous scrolling, one can use the TOPOFSCREEN command in the CHK file, which places the field in question at the top of the second entry screen. This results in a more steady (over)view during data entry, which I think is preferable. Now to my question. At the top of the first screen I show the value of the automatic <IDNUM> field, which corresponds with the respondent number written on the questionnaires. Is there a way to have this <IDNUM> shown at the top of EACH new data entry screen? I've tried this by simply putting the text respondent: <IDNUM> at the top of each new screen. However, this didn't work well, since after the entry and saving of record 1, the next empty datarecord for case 2 is shown, but instead of showing respondent 2 it shows respondent 1 while at the second screen it shows respondent 2 Probably I'm doing something strange, with showing the IDNUM field more then one time in the same REC file. Does anyone know a method to manage this problem? Thanks, Ben.

1 1

Age calculation
by epidata-list＠lists.umanitoba.ca 21 Feb '07

21 Feb '07

Hi, Gilles assessment of the problem is rigth, the message you get is because the results of your calculation is real number and your defined variable is an integer. I think the best solution is: Let age=Integer(date("WDATE","mdy") - date("DOB","mdy"))/30.44) The INTEGER function converts and real number into an integer. I have tried with some records and it works. Regarding Pedro Emmanuel´s solution, I wouldn't do that except if you need the calculation during the data entry (for example to take decisions based on the age of the patient). Otherwise i wouldn't include the field in the QES in order to save room in the harddisk (I know it is not a big issue nowadays, but..) and to save room in the screen and also make it more clear. Hope it helps. Saludos, Pedro Arias > > > > 2007/2/20, epidata-list-rtequest(a)lists.umanitoba.ca < > epidata-list-request(a)lists.umanitoba.ca>: >> >> 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. Date range selection for age calculation >> (epidata-list(a)lists.umanitoba.ca) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: 20 Feb 2007 07:15:30 -0000 >> From: epidata-list(a)lists.umanitoba.ca >> Subject: [EpiData-list] Date range selection for age calculation To: >> epidata-list-request(a)lists.umanitoba.ca >> Cc: epidata-list(a)lists.umanitoba.ca >> Message-ID: <20070220071530.19938.qmail(a)webmail35.rediffmail.com> >> Content-Type: text/plain; charset=iso-8859-1 >> >> Dear Epidata team friends, >> I have two American date >> format variables. DOB is date of birth of baby and WDATE is date of >> weighing the baby for the growth monitoring. >> >> I used to write the following statement to calculate the age in months >> in EPI6 >> >> Define age ### >> Let age=(WDATE DOB)/30.44 >> >> That does not work in EPI ANALYSIS >> >> I tried the statement; >> Let age= (date("WDATE","mdy") - date("DOB","mdy"))/30.44 >> The error message was; >> Data type mismatch >> >> Please help. >> >> Shavinder Singh >> >> >> >> ------------------------------ >> >> ________________________________________ >> EpiData-list(a)lists.umanitoba.ca >> http://lists.umanitoba.ca/mailman/listinfo/epidata-list >> >> >> End of EpiData-list Digest, Vol 40, Issue 15 >> ******************************************** >> > > > > -- > 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 40, Issue 16 > ********************************************

1 0

Re: EpiData-list Digest, Vol 40, Issue 15
by epidata-list＠lists.umanitoba.ca 21 Feb '07

21 Feb '07

Dear Shavinder Singh, I did learn in the same as you, missing a lot first. Dont give up. My suggestion is to put this variable on the .QES that would be automatically calculate during entry. Usually the formula is LET variable_age=ROUND(INT((now_date - birth_date)/365.25)) Epidata does not round and transform the calculation automatically and this syntax is necessary every time you will do any calculation with dates. Good luck, Pedro Emmanuel Brasil 2007/2/20, epidata-list-request(a)lists.umanitoba.ca < epidata-list-request(a)lists.umanitoba.ca>: > > 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. Date range selection for age calculation > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: 20 Feb 2007 07:15:30 -0000 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Date range selection for age calculation > To: epidata-list-request(a)lists.umanitoba.ca > Cc: epidata-list(a)lists.umanitoba.ca > Message-ID: <20070220071530.19938.qmail(a)webmail35.rediffmail.com> > Content-Type: text/plain; charset=iso-8859-1 > > Dear Epidata team friends, > I have two American date > format variables. DOB is date of birth of baby and WDATE is date of weighing > the baby for the growth monitoring. > > I used to write the following statement to calculate the age in months in > EPI6 > > Define age ### > Let age=(WDATE – DOB)/30.44 > > That does not work in EPI ANALYSIS > > I tried the statement; > Let age= (date("WDATE","mdy") - date("DOB","mdy"))/30.44 > The error message was; > Data type mismatch > > Please help. > > Shavinder Singh > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 40, Issue 15 > ******************************************** > -- Abraço forte e que a força esteja com você, Pedro Emmanuel

1 0

Date range selection for age calculation
by epidata-list＠lists.umanitoba.ca 21 Feb '07

21 Feb '07

Dear Epidata team friends, I have two American date format variables. DOB is date of birth of baby and WDATE is date of weighing the baby for the growth monitoring. I used to write the following statement to calculate the age in months in EPI6 Define age ### Let age=(WDATE DOB)/30.44 That does not work in EPI ANALYSIS I tried the statement; Let age= (date(WDATE,mdy) - date(DOB,mdy))/30.44 The error message was; Data type mismatch Please help. Shavinder Singh

1 1

Error when reading a rec file (list index out of bounds)
by epidata-list＠lists.umanitoba.ca 20 Feb '07

20 Feb '07

The user reporting on the 15th: When I try to open updated REC file, I get the message "List index out of out of bounds (420)" - How can I solve this problem? Thank you. We have seen the problem with earlier versions of EpiData Entry (v2.1), but as I remember not with 3.1. But I could be mistaken as I remember having seen it, but cannot reproduce the error with any data I have. A similar error was reported in February 2006, where the error was: In the chk file one of the fields had a wrong name. The very subtle error message does not give you a clue to this, but please check if this could be the cause. A good strategy is always to try to repeat the problem. What did you do since you could read the file last time. Then repeating the steps tells us where to look for a problem in the software and often also how to solve it. But your description does not help a lot, since we should know : 1. What did you do btw. the last time it worked and until it did not ? 2. Which versions of EpiData (Entry or Analysis) wrote the file (saved). If the file can be shown to others you can upload a small copy to the Mantis database, see the http://www.epidata.dk/testing.php with a description - but you must first register as a user there. An easier alternative for the user is to send the file directly to me at info at epidata.dk and we will look at it very soon. regards Jens Lauritsen EpiData Association

1 0

multiple response
by epidata-list＠lists.umanitoba.ca 20 Feb '07

20 Feb '07

The example prepared by Charity Jenkins on the multiple response issue discussed on Febr. 16th. has now been placed for download on http://www.epidata.dk/examples.php For the original description, you can see the text in the archives of the list on the 16th. http://lists.umanitoba.ca/mailman/listinfo/epidata-list Regards Jens Lauritsen EpiData Association

1 0

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

17 Feb '07

I will be out of the office starting 02/16/2007 and will not return until 02/26/2007. If you require immediate assistance, please contact Stephen Drew at extension 5330. Have a great day.

1 0

multiple response and example files
by epidata-list＠lists.umanitoba.ca 16 Feb '07

16 Feb '07

Charity offered: > I will put together an example of this as Epidata files - can I attach > this > to the list or somewhere else? > I have contacted Charity directly in the aim of adding the example for the website at www.epidata.dk/examples.php Information will be given to the list when it is ready. Some users have asked to the list for a copy. Please wait until it is ready there. Regards Jens Lauritsen EpiData Association

1 0

Multiple response questions
by epidata-list＠lists.umanitoba.ca 15 Feb '07

15 Feb '07

Dear Kristine: As one variable can take only one value, you must use as many variables as there are possible values. If you have 5 possible responses ("Do you have any of the following 5 symptoms?"), you need 5 variables, each with 3 possible values, "present", "absent", "unanswered". I don't see an easier way. Regards, Hans Dear Epi-data users: What is the best way to deal with multiple response questions? Thanks, Kristine Hopkins Population Research Center, University of Texas at Austin -- 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

1 1

Is there any possibility to sort the file without exporting the data?
by epidata-list＠lists.umanitoba.ca 15 Feb '07

15 Feb '07

Dear Mr Lauritsen, Thank you very much for your help, this was the hint I needed, works perfectly... Kind regards, Markus

1 0

EpiData-List: List index out of bounds
by epidata-list＠lists.umanitoba.ca 15 Feb '07

15 Feb '07

When I try to open updated REC file, I get the message "List index out of out of bounds (420)" How can I solve this problem? Thank you.

1 0

BUG REPORT : minus sign for MISSINGVALUE with more
by epidata-list＠lists.umanitoba.ca 15 Feb '07

15 Feb '07

It is not a bug, DATE is a reserved name, you cannot use it as a field name. Furthermore, there is nothing like "## ## ###" for a field definition, the definition for dates is <dd/mm/yyyy> (if you choose European date format) Regards, Hans Hello, I noticed a strang bug in Epidata Entry when I use the '-' sign to input=20 a MISSINGVALUE in a field. I created three fields on one line to enter a date with incomplete value = : Date ## ## #### Age ## Sexe # In the check file I used the following DATE MISSINGVALUE 99 END DATE1 MISSINGVALUE 99 END DATE2 MISSINGVALUE 9999 END -- 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

1 1

Multiple response questions
by epidata-list＠lists.umanitoba.ca 14 Feb '07

14 Feb '07

Dear Epi-data users: What is the best way to deal with multiple response questions? Thanks, Kristine Hopkins Population Research Center, University of Texas at Austin

1 0

BUG REPORT : minus sign for MISSINGVALUE with more than one field on the same line
by epidata-list＠lists.umanitoba.ca 14 Feb '07

14 Feb '07

Hello, I noticed a strang bug in Epidata Entry when I use the '-' sign to input a MISSINGVALUE in a field. I created three fields on one line to enter a date with incomplete value : Date ## ## #### Age ## Sexe # In the check file I used the following DATE MISSINGVALUE 99 END DATE1 MISSINGVALUE 99 END DATE2 MISSINGVALUE 9999 END When I type a '-' followed by enter or tab in the field - DATE, the focus goes to DATE2. - DATE1, the focus goes to the field AGE - DATE2, the focus goes to the field SEXE This only happens when I use the minus sign and when there are several fields on the same line. -- 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

1 0

��dryangyun��
by epidata-list＠lists.umanitoba.ca 14 Feb '07

14 Feb '07

where is your master websites,thank you

1 0

sorting rec file
by epidata-list＠lists.umanitoba.ca 13 Feb '07

13 Feb '07

"Is there any possibility to sort the file without exporting the data?" Within EpiData Entry: Define the ID field as a key ID key unique end then after entering all data, export data (#6 in toolbar) to EpiData file and mark "use index as sort order" In EpiData Analysis read myfile sort id savedata newfile copyfile myfile.chk newfile.chk Regards Jens Lauritsen EpiData Association

1 0

Sorting of rec File ?
by epidata-list＠lists.umanitoba.ca 13 Feb '07

13 Feb '07

Dear all, Because of our study design and the randomization procedure in our trial the ID can not be entered in the correct order. Later on it would be more convenient to enter data in the order of the ID. Is there any possibility to sort the file without exporting the data? Thanks in advance, Markus

1 0

QES with two colmns?
by epidata-list＠lists.umanitoba.ca 12 Feb '07

12 Feb '07

Hello all, As times goes by, Im getting the idea that data entry is an art more then a science. Many ptojects have to keep a lot of fields in the paper form and at the end the paper is not big enough to have them all. The consequence is that the QES file should be as similar as possible with paper forms. These last couple weeks Im tryin to make a QES file with tow columns but I cant get to straight up the second column in the REC file. When I make the QES I line up the second by hand, since menu EDIT\line field comand seems to work fine only with one column. But whe the REC file generated the variables, labels and filds of the second column are not align as the QES file (sometimes the labels are uncomplete). Exemple: QES p71 RECUPRACAO # p72 SEQUELA # p73 OBITO# p74 CAUSA MORTIS <A > p75 NECESSITOU INTERNACAO # p76 PROLONGOU A INTERNACAO # p77 MEDICAMENTO SUSPENSO # p78 HOUVE MELHORA # p79 POSOLOGIA ALTERADA # p710 NECESSITOU TRATAMENTO ADICIONAL # p711 HOUVE REEXPOSICAO # p712 REACAO REAPARECEU # p713 PRIMEIRA NOTIFICACAO # p714 NOTIFICADO PARA INDUSTRIA # -- Exemple of resulting REC. p71 RECUPRACAO # p72 SEQUELA # p73 OBITO# p74 AUS<A > p75 NECESSITOU INTERNACAO # p76 PROLON# p77 MEDICAMENTO SUSPENSO # p78 HOUVE MELHORA # p79 POSOLOGIA ALTERADA # p710 NECESSITOU TRATAMENTO ADICIONAL # p711 HOUVE REEXPOSICAO # p712 REACAO REAPARECEU # p713 PRIMEIRA NOTIFICACAO # p714 NOTIFICADO PAR # The most amazing to me is that I´ve worked on some QES files with tow columns before and sometimes it works fine and sometimes it just does not work. At this file for example, a few segments work fine and some dont. Any tip to work around this matter? Thank you, Pedro Emmanuel Brasil Abraço forte e que a força esteja com você, Pedro Emmanuel

1 2

Web Site problem corrected. - new graph command ready v2 b106 analysis
by epidata-list＠lists.umanitoba.ca 08 Feb '07

08 Feb '07

There has been a problem with the website download principle on www.epidata.dk during the last 24 hours. The problem has been resolved, but affected downloads as well as the "Mantis" documentation system. In the latest test build for analysis (b106) a new graph type was included, called "dplot" This will plot a cumulative frequency curve for a given variable. Example of usage: * Show a cumulated frequency percent plot for a variable (here height): dplot height dplot height /yline=50 - the values contained are the same as those showed at : freq height /CP * With option /P: Show a probit plot. * If the data are distributed as Gaussian (Normal) then a probit plot will show data on a straight line. X axis: Midpoints of all data. (e.g. if x = 1 3 ...., then first observation is at x=(1+(3-1)/2)=2 Y axis: The cumulated percentage is converted to probability and graphed as the inverse normal probability dplot height /P There is an unresolved issue with small numbers (incorrect showing) Regards Jens Lauritsen

1 0

How to edit a graph and set further options
by epidata-list＠lists.umanitoba.ca 07 Feb '07

07 Feb '07

Gilles responded correctly on the question of further defining graph options: Try the command: SET GRAPH EDIT = ON which will work in v1 of analysis In the test version v2.0 the "set graph edit" is not allowed. Instead you have to add /edit to any graph command. e.g. scatter v1 v2 /edit But many users will (I assume) use the dialogs from the workprocess toolbar. And in these the /edit is by default added to all graph commands. Regards Jens Lauritsen EpiData Association

1 2

Editing graphs using Epidata analysis
by epidata-list＠lists.umanitoba.ca 06 Feb '07

06 Feb '07

Hallo, I downloaded the test version of the latest Epidata analysis sofware.My problem is;How do I edit a graph so that the percentages appear in each bar or in pie chart. I think I have communicated. Thanks Caleb Ouma Ongong'a +254721-953790, +254733890191 P.O Box 756556-00200 Nairobi-Kenya "Remember that happiness doesn't depend on what you are or on what you possess, but only on how you think." --------------------------------- It's here! Your new message! Get new email alerts with the free Yahoo! Toolbar.

1 1

Today autofield
by epidata-list＠lists.umanitoba.ca 05 Feb '07

05 Feb '07

Hello all, I have been reading the epidata list for while but never tryed to send anything so far. It has been a while that I cant get the field <d/m/y-today> work at enter data. I´ve tryed other today autofields but none have worked so far. When I edit chek, this field appears to be working because the today date is there and field is not open for edition. However, when I open the enterdata, the field is always empty and, of course, I cant enter the date in there. My work around, although not as efficient, is to use the <dd/mm/yyyy> with the REPEAT comand in the check file. Is it some sort of bug or Im doing something wrong? Best regards, may the FORCE be with you all, Pedro Brasil Instituto de Pesquisa Clinica Evandro Chagas Fundação Oswaldo Cruz Av. Brasil 4365, Rio de Janeiro, Brasil -- Abraço forte e que a força esteja com você, Pedro Emmanuel

1 1

How to get test version of EpiData Analysis v2
by epidata-list＠lists.umanitoba.ca 02 Feb '07

02 Feb '07

Point your browser to : Http://www.epidata.dk/testing.php and click on: "Complete Setup" or click directly on this link: http://www.epidata.dk/php/downloadc.php?file=setupepidatastattest.exe Notice that test versions should always be used with caution until they are released from the official download page at http://www.epidata.dk/download.php Kind regards Jens Lauritsen EpiData Association

1 0

Re: [EpiData-list] Validation duplicate files
by epidata-list＠lists.umanitoba.ca 02 Feb '07

02 Feb '07

Hi Charity and Lars: There are two ways for duplicate data entry: 1) independent of sequence 2) dependent on sequence 1) If you use a field with unique identifier, you can enter the data independently of sequence twice, and then compare the two files later on that unique identifier. In this instance two data entry groups can enter add the same time part A and part B and then switch for second entry. 2) You can use the "Tools" "Prepare Double Entry Verification". If you do not tick and choose the option "Match records by field" (and choose the Unique identifier), then the second entry will by default follow the record number, and thus sequence matters. If you choose that option, the first data entry group will still have to await completion by the first data entry group. As Charity says, it is critical in any case to have a truly unique identifier which can by assured by KEY UNIQUE. Seemingly, Lars, you did not have that. You must thus identify the records with duplicate identifiers and or missing identifiers in both files, mark them for deletion (but not packing" and then compare. You deal then separately with the problematic records in both files, most simply perhaps by reentering them properly and independently in both files. Regards, Hans Hello Lars, I just did a small test of this to make sure, and the ordering/sequence of IDs in the two files does not make a difference when Validating Duplicate Files. What will cause a problem is if there is a duplicated ID in one of your two files - are you sure that the Case IDs are unique? You should have "KEY UNIQUE 1" included in your .chk file for the ID variable to ensure this. Kind regards, Charity On 2/1/07, epidata-list(a)lists.umanitoba.ca <epidata-list(a)lists.umanitoba.ca> wrote: Dear Epidata_list, I'm a new member of this list and a fairly new user of the Epidata software. In attempting to validate duplicate files not entered in same sequence by two observers I have difficulty in performing the test under documebt/validate duplicate files. Attempting to perfom the test with a selected key field of case-id an error is given; "Duplicate keys found" and the validation is terminated. Is it possible to perform a comparison of the two datasets despite the fact that the registrations are not performed in same sequence with regard to registration of the observations? Siincerely, Lars -- 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

1 0

Testing Epidata Analysis V2.0
by epidata-list＠lists.umanitoba.ca 02 Feb '07

02 Feb '07

Hi, How can i have an Epidata Analysis V2.0 for make some testing? Thanks ___________________________________________ Dr Jean-Paul DIBY-KONAN Médecin Santé Publique MCM Santé de la Reproduction Institut Médecine Tropicale Kapucinessenstraat 8 B-2000 Anvers Belgique ----- Message d'origine ---- De : "epidata-list-request(a)lists.umanitoba.ca" <epidata-list-request(a)lists.umanitoba.ca> À : epidata-list(a)lists.umanitoba.ca Envoyé le : Jeudi, 1 Février 2007, 19h15mn 13s Objet : EpiData-list Digest, Vol 40, Issue 1 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. Tables in 2.0 R. 1 Build 104 of Epidata Analysis (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Thu, 1 Feb 2007 08:04:10 -0800 (PST) From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Tables in 2.0 R. 1 Build 104 of Epidata Analysis To: epidata-list(a)lists.umanitoba.ca Message-ID: <398980.61861.qm(a)web32105.mail.mud.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 Hi, Thank you for introducing the test version of Epidata Analysis V2.0. I tried to do some tables using it but no infrential statistics is performed. Just an r*c table is shown. Even for "Means" command, just descriptive statistics is shown. Thanks Reza ____________________________________________________________________________________ It's here! Your new message! Get new email alerts with the free Yahoo! Toolbar. http://tools.search.yahoo.com/toolbar/features/mail/ ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 40, Issue 1 ******************************************* ___________________________________________________________________________ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com

1 0

Validation duplicate files
by epidata-list＠lists.umanitoba.ca 01 Feb '07

01 Feb '07

Dear Epidata_list, I'm a new member of this list and a fairly new user of the Epidata software. In attempting to validate duplicate files not entered in same sequence by two observers I have difficulty in performing the test under documebt/validate duplicate files. Attempting to perfom the test with a selected key field of case-id an error is given; "Duplicate keys found" and the validation is terminated. Is it possible to perform a comparison of the two datasets despite the fact that the registrations are not performed in same sequence with regard to registration of the observations? Siincerely, Lars

1 1

Re: Release of EpiData Analysis v2.0 for testing
by epidata-list＠lists.umanitoba.ca 01 Feb '07

01 Feb '07

As announced a short while back the module is now available for testing. A short example should help users getting started on the test. 1. Expect that some/many set commands have changed. E.g. Obsolete ones in version 2: Set statistics, set percentages, set table reverse etc 2. You only get what you ask for. e.g.: tables v1 v2 // will only give the counts tables v1 v2 /R // will give row percentages (column:/C, total: /T) tables v1 v2 /T /EX // will give a chi square test and with /EX also exact tests for 2x2 tables tables v1 v2 v3 /T /EX // will do a stratified analysis with overall exact testing as well. tables v1 v2 v3 v4 /OA //will make a condensed outbreak analysis table tables v1 v2 /SD // will sort descending instead of the default ascending sort on row and column tables v1 v2 /SRAT // will sort ascending on the row total /SRDT would be descending 3. replacement for epitables or etab will be typically (to have highest value as case and exposure): tables v1 v2 v3 /sd /t Many aspects are not final yet - notice it is a test build, e.g. some issues remain on medians in SPC graphs. Therefore the front page also states: Notice - this is a premature test build - only for experienced test persons ! regards Jens Lauritsen EpiData Association

1 0

EpiData Analysis: testing of version 2.0.1.104
by epidata-list＠lists.umanitoba.ca 01 Feb '07

01 Feb '07

Public testing of version 2 of EpiData Analysis can now begin. A lot of work has been done to reshape internal parts of EpiData Analysis. All users are now encouraged to participate in the testing. A system of comparing estimates, counting with results of Stata or Epi6 is applied. Currently the system contains around 1000 different tests. But maybe the system is not taking care of all problems, therefore user tests are also important. A complete list of changes is shown at http://www.epidata.dk/analysisversioninfo.htm. Main points are: Output is simplified. You only get what you ask for. To get more add options (e.g. /T) to the command Tables Extended (sorting, percentages, weights, outbreak) Metadata commands: missingvalue, labelvalue, rename Outbreak analysis: "tab outcome exposure variables /oa" "epicurve datevar outcome group" The test version is placed at: Http://www.epidata.dk/testing.php Please discuss the new version on this list. If you find definite bugs report to http://www.epidata.dk/php/mantis, where all development is documented. .............................................................. Regarding the discussion last week of differences btw. open-source and free software. As announced earlier a "master plan" for rewriting all EpiData Software to Open-Source as well as platform independence is part of the general development plan for EpiData. Releasing software as open-source makes no sense if the structure and content of the product is not sufficiently modular to allow for several independent development lines. Someone might disagree with me on this, but knowing how fragile software development is and seing the increased requirements for documentation and quality assurance I am assured that a controlled situation is preferable at this point in time. For almost all end users having a stable, quality assured software line is more important than having access to independent and possibly confusing development. But there should be no doubt that the aim is at an appropriate time to release the product source-code as open-source. Should anyone have a lot of energy or time to add to the project there are many issues needing assistance, e.g. answering questions on the epidata-list, assisting in sorting incoming mails to the help line, releasing mails for the epidata-list coming from un-subscribed persons, creating a FAQ collection such as that running for Stata at http://www.stata.com/support/faqs/ or joining a group running a wiki for EpiData, which could contain the FAQ. A start of this can be seen at www.epidata.org/wiki, but will not be announced before such a group has been established (A coordinator has been found). Notice also that for EpiData Entry users can develop their own CHK file commands. Modules for doing so (source code and examples) are found on http://www.epidata.dk/documentation.php .............................................................. Kind regards Jens Lauritsen EpiData Association

1 0

Tables in 2.0 R. 1 Build 104 of Epidata Analysis
by epidata-list＠lists.umanitoba.ca 01 Feb '07

01 Feb '07

Hi, Thank you for introducing the test version of Epidata Analysis V2.0. I tried to do some tables using it but no infrential statistics is performed. Just an r*c table is shown. Even for "Means" command, just descriptive statistics is shown. Thanks Reza ____________________________________________________________________________________ It's here! Your new message! Get new email alerts with the free Yahoo! Toolbar. http://tools.search.yahoo.com/toolbar/features/mail/

1 0