June 2008 - EpiData-list - University of Manitoba Mailing Lists

Unable to use Command FIND (Ctrl F) in Enter Record to find field with date format as <mm/dd/yyyy>
by epidata-list＠lists.umanitoba.ca 01 Jul '08

01 Jul '08

Dear all, I recently installed Epidata version 3.1 and able to convert 1 of my recfile from EPI6 successfully! I found that with field date using format <mm/dd/yyyy> unable to use control FIND <Ctrl F> unless it change to format <dd/mm/yyyy>. Would you please help me to find way to using FIND command with format <mm/dd/yyyy>. Thank you very much and have a great day to all of you, kim -----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: Monday, June 30, 2008 11:51 AM To: Dang, Kim Subject: Welcome to the "EpiData-list" mailing list (Digest mode) Welcome to the EpiData-list(a)lists.umanitoba.ca mailing list! The list is intended for communication among users of EpiData. DO NOT USE the list for commercial adverticements, job seeking and similar issues !!! If you do so you will be deleted from the list immediately without warning. Since most qes/rec/chk files are very small a limit of attachments has been set to 25k. Also we suggest that you only submit "text only" formatted e-mails to the list. Kind Regards Chris Green, Moderator of the list Jens M.Lauritsen, initiator EpiData Association EpiData general information: www.epidata.dk To post to this list, send your email to: epidata-list(a)lists.umanitoba.ca General information about the mailing list is at: http://lists.umanitoba.ca/mailman/listinfo/epidata-list If you ever want to unsubscribe or change your options (eg, switch to or from digest mode, change your password, etc.), visit your subscription page at: http://lists.umanitoba.ca/mailman/options/epidata-list/kim.dang%40hhs.sc cgov.org You can also make such adjustments via email by sending a message to: EpiData-list-request(a)lists.umanitoba.ca with the word `help' in the subject or body (don't include the quotes), and you will get back a message with instructions. You must know your password to change your options (including changing the password, itself) or to unsubscribe. It is: 11111 Normally, Mailman will remind you of your lists.umanitoba.ca mailing list passwords once every month, although you can disable this if you prefer. This reminder will also include instructions on how to unsubscribe or change your account options. There is also a button on your options page that will email your current password to you.

1 1

can you write "or" in epidata?
by epidata-list＠lists.umanitoba.ca 17 Jun '08

17 Jun '08

Hi! very simple question, can you write "or" if you are using "if" command? Thank you and best regards ziad

1 0

Re: [EpiData-list] Re: EpiData-list Digest, Vol 56, Issue 9
by epidata-list＠lists.umanitoba.ca 17 Jun '08

17 Jun '08

Dear All accept my best regards, and I have a question, does any body know any version of Epidata which support the alphabets of Arabic , Dari or Farsi thanks Ibrahim Hussaini Database Officer Afghan Independent Human Rights Commission Kabul Afghanistan -------------------------------------------------- From: <epidata-list(a)lists.umanitoba.ca> Sent: 16-06-2008 8:59 PM To: <epidata-list(a)lists.umanitoba.ca> Subject: [EpiData-list] Re: EpiData-list Digest, Vol 56, Issue 9 > Thank you. > > Quoting 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. Re: Edit qes and keeping chk commands >> (epidata-list(a)lists.umanitoba.ca) >> 2. Saving a CHK file when editing a QES file >> (epidata-list(a)lists.umanitoba.ca) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Fri, 13 Jun 2008 17:11:03 -0300 >> From: epidata-list(a)lists.umanitoba.ca >> Subject: [EpiData-list] Re: Edit qes and keeping chk commands >> To: epidata-list(a)lists.umanitoba.ca >> Message-ID: >> <a37cfb5a0806131311g2b6f2e85w107e14f49b82a91c(a)mail.gmail.com> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> Dear Susan, >> >> The tip here is never to change the variables names! You may add new >> variables, change the labels, change the variables places in the >> questionnaire. When U open the rec file, epidata will ask U to update the >> rec file and everything will be there. Bur if you change the variable >> name >> in the qes file, EpiData will undestand that U erased the variable and >> created a new one, and your data will be lost "for ever". :( The chk >> files >> follows the same principle. The name of the varible is what matters. If >> you >> want to change a varible name in a dataset wiht lots of observations then >> you should look in the tools menu. There is an option to change variables >> names. >> >> Best regards, >> Pedro Emmanuel Brasil >> >> 2008/6/13 <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. simple question (epidata-list(a)lists.umanitoba.ca) >> > >> > >> > ---------------------------------------------------------------------- >> > >> > Message: 1 >> > Date: Fri, 13 Jun 2008 10:09:26 -0400 >> > From: epidata-list(a)lists.umanitoba.ca >> > Subject: [EpiData-list] simple question >> > To: epidata-list(a)lists.umanitoba.ca >> > Message-ID: <1213366166.48527f96b7cfc(a)webmail.med.yale.edu> >> > Content-Type: text/plain; charset=ISO-8859-1 >> > >> > When I go back and edit an ques file add questions, etc. I want to >> > retain >> > the >> > checks from the previous ques file, but incorporate new edits to ques >> > file. >> > How do I make data file w/o overwriting previous checks and/or >> > creating >> > new >> > data file? >> > >> > Susan >> > >> > >> > ------------------------------ >> > >> > ________________________________________ >> > EpiData-list(a)lists.umanitoba.ca >> > http://lists.umanitoba.ca/mailman/listinfo/epidata-list >> > >> > >> > End of EpiData-list Digest, Vol 56, Issue 8 >> > ******************************************* >> > >> >> >> >> -- >> Abraço forte e que a força esteja com você, >> Pedro Emmanuel >> >> >> ------------------------------ >> >> Message: 2 >> Date: Sat, 14 Jun 2008 12:18:51 +0200 (CEST) >> From: epidata-list(a)lists.umanitoba.ca >> Subject: [EpiData-list] Saving a CHK file when editing a QES file >> To: <epidata-list(a)lists.umanitoba.ca> >> Message-ID: <1841.83.250.109.61.1213438731.squirrel(a)www.asoles.org> >> Content-Type: text/plain; charset=iso-8859-1 >> >> > >> > When I go back and edit an ques file add questions, etc. I want to >> > retain the checks from the previous ques file, but incorporate new >> > edits >> > to ques file. How do I make data file w/o overwriting previous checks >> > and/or creating new data file? >> > >> > Susan >> >> Hi Susan, >> >> In Epidata there are three main files associated to a data set: >> QES the design of the layout and properties of the questionnaire >> REC the data set itself >> CHK the definition of check controls during tha data entry >> >> In order to Enter data you anly need two of them (REC and CHK). >> >> If you edit a QES file and update the REC using the revised QES your >> check >> file will work if: >> The name of the new REC files is the same as the name of the CHK file. >> and >> The names of the fields in the REC file have not been changed. For >> example >> in the old file you have a field names SEX and you keep the same name in >> the new version. However if you change the name of the field to GENDER >> the >> CHK file will give you an error. (usually Epidata will ask you to display >> where the erros are located, what will help you to fix the problems) >> >> I am not sure but I think there was an option in EpiData Entry to save >> the >> CHK file ate the same time that you are updating a REC file from a QES. >> Can some one comment on that? >> >> Hope it helps, >> >> Pedro Arias. Stockholm >> >> >> >> >> >> ------------------------------ >> >> ________________________________________ >> EpiData-list(a)lists.umanitoba.ca >> http://lists.umanitoba.ca/mailman/listinfo/epidata-list >> >> >> End of EpiData-list Digest, Vol 56, Issue 9 >> ******************************************* >> >> > > > Susan Caplan, RN, MSN, FNP-BC > Yale University > PhD Student in Nursing > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list >

1 0

Re: EpiData-list Digest, Vol 56, Issue 9
by epidata-list＠lists.umanitoba.ca 16 Jun '08

16 Jun '08

Thank you. Quoting 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. Re: Edit qes and keeping chk commands > (epidata-list(a)lists.umanitoba.ca) > 2. Saving a CHK file when editing a QES file > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 13 Jun 2008 17:11:03 -0300 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Re: Edit qes and keeping chk commands > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <a37cfb5a0806131311g2b6f2e85w107e14f49b82a91c(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Dear Susan, > > The tip here is never to change the variables names! You may add new > variables, change the labels, change the variables places in the > questionnaire. When U open the rec file, epidata will ask U to update the > rec file and everything will be there. Bur if you change the variable name > in the qes file, EpiData will undestand that U erased the variable and > created a new one, and your data will be lost "for ever". :( The chk files > follows the same principle. The name of the varible is what matters. If you > want to change a varible name in a dataset wiht lots of observations then > you should look in the tools menu. There is an option to change variables > names. > > Best regards, > Pedro Emmanuel Brasil > > 2008/6/13 <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. simple question (epidata-list(a)lists.umanitoba.ca) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Fri, 13 Jun 2008 10:09:26 -0400 > > From: epidata-list(a)lists.umanitoba.ca > > Subject: [EpiData-list] simple question > > To: epidata-list(a)lists.umanitoba.ca > > Message-ID: <1213366166.48527f96b7cfc(a)webmail.med.yale.edu> > > Content-Type: text/plain; charset=ISO-8859-1 > > > > When I go back and edit an ques file add questions, etc. I want to retain > > the > > checks from the previous ques file, but incorporate new edits to ques file. > > How do I make data file w/o overwriting previous checks and/or creating > > new > > data file? > > > > Susan > > > > > > ------------------------------ > > > > ________________________________________ > > EpiData-list(a)lists.umanitoba.ca > > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > > > > End of EpiData-list Digest, Vol 56, Issue 8 > > ******************************************* > > > > > > -- > Abraço forte e que a força esteja com você, > Pedro Emmanuel > > > ------------------------------ > > Message: 2 > Date: Sat, 14 Jun 2008 12:18:51 +0200 (CEST) > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Saving a CHK file when editing a QES file > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: <1841.83.250.109.61.1213438731.squirrel(a)www.asoles.org> > Content-Type: text/plain; charset=iso-8859-1 > > > > > When I go back and edit an ques file add questions, etc. I want to > > retain the checks from the previous ques file, but incorporate new edits > > to ques file. How do I make data file w/o overwriting previous checks > > and/or creating new data file? > > > > Susan > > Hi Susan, > > In Epidata there are three main files associated to a data set: > QES the design of the layout and properties of the questionnaire > REC the data set itself > CHK the definition of check controls during tha data entry > > In order to Enter data you anly need two of them (REC and CHK). > > If you edit a QES file and update the REC using the revised QES your check > file will work if: > The name of the new REC files is the same as the name of the CHK file. > and > The names of the fields in the REC file have not been changed. For example > in the old file you have a field names SEX and you keep the same name in > the new version. However if you change the name of the field to GENDER the > CHK file will give you an error. (usually Epidata will ask you to display > where the erros are located, what will help you to fix the problems) > > I am not sure but I think there was an option in EpiData Entry to save the > CHK file ate the same time that you are updating a REC file from a QES. > Can some one comment on that? > > Hope it helps, > > Pedro Arias. Stockholm > > > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 56, Issue 9 > ******************************************* > > Susan Caplan, RN, MSN, FNP-BC Yale University PhD Student in Nursing

1 0

Saving a CHK file when editing a QES file
by epidata-list＠lists.umanitoba.ca 14 Jun '08

14 Jun '08

> > When I go back and edit an ques file add questions, etc. I want to > retain the checks from the previous ques file, but incorporate new edits > to ques file. How do I make data file w/o overwriting previous checks > and/or creating new data file? > > Susan Hi Susan, In Epidata there are three main files associated to a data set: QES the design of the layout and properties of the questionnaire REC the data set itself CHK the definition of check controls during tha data entry In order to Enter data you anly need two of them (REC and CHK). If you edit a QES file and update the REC using the revised QES your check file will work if: The name of the new REC files is the same as the name of the CHK file. and The names of the fields in the REC file have not been changed. For example in the old file you have a field names SEX and you keep the same name in the new version. However if you change the name of the field to GENDER the CHK file will give you an error. (usually Epidata will ask you to display where the erros are located, what will help you to fix the problems) I am not sure but I think there was an option in EpiData Entry to save the CHK file ate the same time that you are updating a REC file from a QES. Can some one comment on that? Hope it helps, Pedro Arias. Stockholm

1 0

Re: Edit qes and keeping chk commands
by epidata-list＠lists.umanitoba.ca 13 Jun '08

13 Jun '08

Dear Susan, The tip here is never to change the variables names! You may add new variables, change the labels, change the variables places in the questionnaire. When U open the rec file, epidata will ask U to update the rec file and everything will be there. Bur if you change the variable name in the qes file, EpiData will undestand that U erased the variable and created a new one, and your data will be lost "for ever". :( The chk files follows the same principle. The name of the varible is what matters. If you want to change a varible name in a dataset wiht lots of observations then you should look in the tools menu. There is an option to change variables names. Best regards, Pedro Emmanuel Brasil 2008/6/13 <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. simple question (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 13 Jun 2008 10:09:26 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] simple question > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <1213366166.48527f96b7cfc(a)webmail.med.yale.edu> > Content-Type: text/plain; charset=ISO-8859-1 > > When I go back and edit an ques file add questions, etc. I want to retain > the > checks from the previous ques file, but incorporate new edits to ques file. > How do I make data file w/o overwriting previous checks and/or creating > new > data file? > > Susan > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 56, Issue 8 > ******************************************* > -- Abraço forte e que a força esteja com você, Pedro Emmanuel

1 0

simple question
by epidata-list＠lists.umanitoba.ca 13 Jun '08

13 Jun '08

When I go back and edit an ques file add questions, etc. I want to retain the checks from the previous ques file, but incorporate new edits to ques file. How do I make data file w/o overwriting previous checks and/or creating new data file? Susan

1 0

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

11 Jun '08

Thanks for your response. I realize the questions are rather basic, but I had perused many of the help and intro files, without finding anything that specifically addressing syntax. Perhaps the intro file for beginner users could be made more user friendly with an additional paragraph in bold under the section: Value label: For categorical data this defines the meaning of the values. E.g. 1=man 2=women. The values are edited via the + . The drop-down list lets you pick an existing label definition. ACCEPTABLE SYNTAX with all the rules spelled out, such as when quotes are necessary etc. Susan Quoting 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. 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) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 14 May 2008 14:26:56 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] value labels error message > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <1210789616.482b2ef0e2844(a)webmail.med.yale.edu> > Content-Type: text/plain; charset=ISO-8859-1 > > 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 > > > ------------------------------ > > Message: 2 > Date: Wed, 14 May 2008 14:30:04 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] legal use? > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <1210789804.482b2facb3c80(a)webmail.med.yale.edu> > Content-Type: text/plain; charset=ISO-8859-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 > > > ------------------------------ > > Message: 3 > Date: Wed, 14 May 2008 14:30:55 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] combined numeric text variable > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <1210789855.482b2fdfe2bd4(a)webmail.med.yale.edu> > Content-Type: text/plain; charset=ISO-8859-1 > > 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 > > > ------------------------------ > > Message: 4 > Date: Wed, 14 May 2008 21:44:22 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] combined numeric text variable > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <482B9576.9040305(a)sympatico.ca> > Content-Type: text/plain; charset=windows-1252; format=flowed > > 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 dont want to opt for text only. Suggestions? > > > > > > Susan Caplan, RN, MSN, FNP-BC > > Yale University > > PhD Student in Nursing > > > ------------------------------ > > Message: 5 > Date: Thu, 15 May 2008 11:12:57 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] legal use? > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <482BFE99.9010100(a)univ-angers.fr> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > 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 > > > > ------------------------------ > > Message: 6 > Date: Thu, 15 May 2008 11:03:14 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] value labels error message > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <482BFC52.6010508(a)univ-angers.fr> > Content-Type: text/plain; charset=windows-1252; format=flowed > > > 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 > > dont 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 > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 55, Issue 11 > ******************************************** > > Susan Caplan, RN, MSN, FNP-BC Yale University PhD Student in Nursing

1 0

RE: How to use browse in the middle of analysis
by epidata-list＠lists.umanitoba.ca 10 Jun '08

10 Jun '08

The easy way to use browse is: Hit the F6 button. This will move control to the browse window and show all current data Obviously a pgm cannot be running in the background, but a strategy whereby: The system to help beginners is the "dialog" / menu system, which you find using the toolbar. By using the dialog there is no need to know the options for most standard possibilities. 1. For beginners: a Use the menu's and the toolbar to create a command, e.g. in analysis find the tables part b In the menu's (dialogs) there is a "more" arrow. When clicking this more options show up. By the menu's most standard options are available, but for some see the "experienced". 2. Experienced a Write the command in the command prompt. b If in doubt of options, click the F1 button and the help file for that command will be shown in the viewer. 3. Run the command / execute the command 4. When all is in place and running. Open the pgm file editor (F5) and insert history Clean up in the lines and you have your working pgm ready. Jens Lauritsen EpiData Association

1 0

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

10 Jun '08

Thank Chrystine, To solve this issue, one way (of course may not be the best) is to append datasets (providing ID are different) using EpiData Entry/Analysis which ever is convenient for you). Not sure if merge is an appropriate way for such combination of datasets. If the two datasets have some common features such as unique key values for example ID, then merge may be required to deal with it. Alternatively try append, the two file or more files should be combined to produce one. Perhaps the memory needs to be cleared prior to READ other files, then append/merge them to be READ in one file. First of all "cls" to clear the screen out then "read". Save replace, save your new dataset (golden rule). Best wishes Tieble 2008/6/10 <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. Re: Re: Outbreak analysis diary - multiple data sets > (epidata-list(a)lists.umanitoba.ca) > 2. EpiData Analysis notes (epidata-list(a)lists.umanitoba.ca) > 3. RE: If..then (epidata-list(a)lists.umanitoba.ca) > 4. Re: Re: Outbreak analysis diary - multiple data sets > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 10 Jun 2008 12:04:34 +1200 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Re: Outbreak analysis diary - multiple > data sets > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: <484E6DD2020000CA00016D7A(a)GW.hvh.co.nz> > Content-Type: text/plain; charset=US-ASCII > > 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 ** > > > > ------------------------------ > > Message: 2 > Date: Tue, 10 Jun 2008 09:39:25 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] EpiData Analysis notes > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: > <AD682418821AA34BAB0650CECBC8B92D074D02(a)colhpaexc001.HPA.org.uk> > Content-Type: text/plain; charset="us-ascii" > > 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 > ************************************************************************** > > ------------------------------ > > Message: 3 > Date: Tue, 10 Jun 2008 10:58:20 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: RE: [EpiData-list] If..then > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: <ED5A894B497B0040A17FD2AE66D789B07517B1(a)xch-2.ivs.local> > Content-Type: text/plain; charset="iso-8859-1" > > Should be written as follows (only 1 argument per line) > > -----Message d'origine----- > De : epidata-list(a)lists.umanitoba.ca [mailto: > epidata-list(a)lists.umanitoba.ca] > Envoyé : mercredi 28 mai 2008 17:48 > À : epidata-list(a)lists.umanitoba.ca > Objet : [EpiData-list] If..then > > 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 > V65=9 > V66=9 > goto V67 > ENDIF > > > Thank you in advance > best regards > ziad > > > > ------------------------------ > > Message: 4 > Date: Tue, 10 Jun 2008 07:37:20 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Re: Outbreak analysis diary - multiple > data sets > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <484E6770.8070508(a)sympatico.ca> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > 1. Merge vs. Read and Append in Analysis > > Apologies - the correct syntax to read multiple files in Analysis is: > > read file1 > append /file=file2 > > you can keep adding files. > > SAVEDATA will save a new .rec file. This is especially useful if you > have temporary variables that are used to manipulate the data. You can > do this: > > VAR DROP temp1 temp2 temp3 > SAVEDATA finaldata.rec > > Merging with Entry provides a bit of documentation of what was done and > can be automated with EPIC (but thats another level of data management). > > 2. Merge and IDNUM. I normally avoid IDNUM as it is often useful to > record ID numbers before you get to enter the data. However, you can use > IDNUM and merge data successfully, if you assign each data entry person > a unique range of IDs. In EpiData Entry, you can set an option for the > first ID to use when entering the first record of a file. It is under > File, Options and the Advanced tab. So one person could go with the > default (1) and another could change this to 1001 before entering any data. > > Another approach, where IDNUM was used and both sets of data start with > 1 (although this is really not good data mangement practice, you might > do this by including another code that indicates who entered the data). > In this case, use Analysis to merge the data as above. Analysis doesn't > care about unique ID numbers. > > 3. Field Epidemiology course and EpiData - we do a small field survey or > observational study each year. We can send more info. Contact us via the > e-mail address found at http://www.phac-aspc.gc.ca/cfep (Put my name in > the subject line). > > Jamie > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 56, Issue 5 > ******************************************* >

1 0

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