- EpiData-list - University of Manitoba Mailing Lists

about: Lifetable in v2.1
by epidata-list＠lists.umanitoba.ca 02 Nov '08

02 Nov '08

B.Branger questioned whether the lifetable is "actuarial" or "Kaplan-Meier" principle. The principle is to calculate changes in survival probabilities at each date, where a change happens - either censoring or case status. In actuarial calculations there would be an aggregation to say half year, month or similar. Therefore if you DO NOT use the /i for "Interval" the calculation will be "Kaplan-Meier" technique. If you found an example where this is not the case let us know. regards Jens Lauritsen EpiData Association

1 0

Epidata Analysis 2
by epidata-list＠lists.umanitoba.ca 02 Nov '08

02 Nov '08

Hello, Three suggestions on last version of Epidata Analysis 2.0 (very good on the whole): - a regression line in scatter graph is imperative like EPI 6 and all the statistic softwares ++ - a few "set command" are desirable; for example : * "set statistics = on" instead to write /t for all the commands * "set table percentage = row" instead to write /r for all the "tables" commands - "set freq percentage= column" instead to write /c for all "freq" commands A question about "lifetable" command (very useful and pratical) : - In understand that the method is "actuarial" ou "lifetable" with a range of time for the calculation of probability (1 by default). The result is the same than SPSS with the command "lifetable" and time range = 1. It's not Kaplan-Meier method because the probability is not calculated at each event, (or calculation of remaining number at each censored data). Thank you your observation. B. BRANGER. PS : I modify this week the help on my site www.reseau-naissance.fr <http://www.reseau-naissance.fr/>

1 0

Update for EpiData Analysis v2.1 and news on further development.
by epidata-list＠lists.umanitoba.ca 02 Nov '08

02 Nov '08

A new build for EpiData Analysis has been placed for general download. From v2.1.0.154 it is possible to give dates as a parameter to x-axis limits in EpiCurve and Kaplan Meier Survival plots. e.g. Epicurve outcome dayonset /xmin="01/10/1986" /xmax="25/10/1986" Notice the DMY format. A few other bugs have been solved. If you are not using Epicurve there is no reason for updating. A recent seminar in Canada forms part of the intensified development ongoing this year. This collaboration is with the Assocation of Public Health Epidemiologists in Ontario, Canada, see: http://www.apheo.ca/index.php?pid=47 On the testing page (http://www.epidata.dk/testing.php) v2.1.1.154 includes two new commands released for tests and comments: xbar /Range, xbar /Sigma , and ichart /MR - these will perform double charts used in Statistical Process Control analysis and visualisation. An extended user manual is in development and expected ready for general use in about one month. G-charts are expected within 1-2 weeks for testing. Regards Jens Lauritsen EpiData Association

1 0

Re: new install zipfile on web
by epidata-list＠lists.umanitoba.ca 23 Oct '08

23 Oct '08

I am a user who does not have administrative rights so may thanks for the new feature. I like the new version of Epidata Analysis but I have one small issue. When I go file open in the programme editor It always opens up to the test data file directory C:\programme files\epidata\test data and i have to navigate to the directory where I saved my programme. With the old version if I clicked open in editor it would open at the directory of the last programme I used (e.g. F:\programmes\health protection\outbreaks). Is there something I can do to change to make the new version do this? thanks Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 >>> <epidata-list(a)lists.umanitoba.ca> 23/10/2008 4:52 p.m. >>> A few bugs has been found in the public release the latest week: a. In Epicurve when started from the menu, the time variable could not be date - fixed b. In Epicurve the default Yincrease is now set to one. (/yinc=1) these are fixed, in addition c the reported error with define and gen of variables "_" will be fixed An increasing number of users cannot install files on their own pc. Since Epidata software is not really installed, but only unzipped and copied the zip file for download does not contain an install file, but a zipped copy of an installed version. This means that all users who have problems due to lack of administrative rights should be able to download the "Setup (zip)", unzip and place somewhere, e.g. a subfolder to the desktop. It is then up to the user to edit the ini file found via the edit menu to the correct path/folder name. If you are not using epidemic curves there is no reason to change from build 151 to 152. regards Jens Lauritsen -- 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

Corrected Analysis v2.1.0.152 and new install zip file on web
by epidata-list＠lists.umanitoba.ca 22 Oct '08

22 Oct '08

A few bugs has been found in the public release the latest week: a. In Epicurve when started from the menu, the time variable could not be date - fixed b. In Epicurve the default Yincrease is now set to one. (/yinc=1) these are fixed, in addition c the reported error with define and gen of variables "_" will be fixed An increasing number of users cannot install files on their own pc. Since Epidata software is not really installed, but only unzipped and copied the zip file for download does not contain an install file, but a zipped copy of an installed version. This means that all users who have problems due to lack of administrative rights should be able to download the "Setup (zip)", unzip and place somewhere, e.g. a subfolder to the desktop. It is then up to the user to edit the ini file found via the edit menu to the correct path/folder name. If you are not using epidemic curves there is no reason to change from build 151 to 152. regards Jens Lauritsen

1 0

Double entry and unique field
by epidata-list＠lists.umanitoba.ca 22 Oct '08

22 Oct '08

Dear EpiData friends, Im in project about adverse events of a particular kind of patients using some medications. The data entry has a rationale of every adverse event of a single patient has a different questionnaire. This means that a unique number of the patient could be typed in the dataset more than once. So far ... OK But we are plannig a double entry... and than the unique identifier of the patient may couse problmes and errors! So I was thinking about creating a sequence for each adverse event, and than a patient 19230 would have a event A, B,C .... and so on A unique variable could be automaticly created by patientnumber+uniqueevent wich could give something like 19230A, 19230B, 19230C and so on! But this does not seem to me an elegante work around! Does any one else have other suggestions? -- Abraço forte e que a força esteja com você, Pedro Emmanuel

1 0

SPC Charts
by epidata-list＠lists.umanitoba.ca 20 Oct '08

20 Oct '08

I wonder if someone can give me some advice. I would like to create SPC charts that include data on actual counts and target. I have been playing around and it seems I can only include one field. Is there any way I can create SPC Charts that show actual counts (e.g of MRSA) against targets? Thanks, Shakeel ----------------------------------------- ************************************************************************** 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: Problem with underscore character in variable name
by epidata-list＠lists.umanitoba.ca 19 Oct '08

19 Oct '08

"According to the documentation, an underscore character is allowed in variable names. And, indeed, I have no problem defining new variable names with an underscore and using them in analysis (v2.1.0.151). .... However, when the data have been saved and one opens the file for further analysis, the variable has been renamed v1 (or v2, etc). " Actually this is a bug in analysis. Will be corrected. Explicitly _ is NOT allowed. Where in the documentation is _ allowed. This is a misrepresentation. The reason is : _ is the representation of a string variable in the qes file, but apparently we made an error in the analysis allowing for this on generate. (e.g. gen i abc_d = 1 or define abc_d # ) regards Jens Lauritsen

1 1

Backup command: make routine snapshots without replacing previous backup (TIME STAMP?)
by epidata-list＠lists.umanitoba.ca 19 Oct '08

19 Oct '08

With sufficient patience and testing any name structure can be given for a backup file. Here shown with calling of the external file epic. Some adaptation of the command line is necessary, which is why the backup command was developed. This block will ask whether to create a zip file with the name of todays date using an external application epic.exe - it can be a little (often quite) tedious to work out the parameters to execute, but do so first in a command window outside epidata entry. Include in the chk file this "after file" block, which names the zip file by date, hour and minute: after file help "Create zip file ? 1:yes 2:no" keys="12" type=CONFIRMATION if resultvalue = 1 then define tmpz _________________________________________________ let tmpz = "zip c:\temp\first"+string(day(today)) if month(today) < 10 then tmpz = tmpz + "0" + string(month(today)) + string(year(today)) + string(Num2Time(Now)) + " replace first.*" else tmpz = tmpz + string(month(today))+ string(year(today)) + string(Num2Time(Now)) +" replace first.*" endif help @tmpz execute epic "@tmpz" wait endif END Regards Jens Lauritsen

1 0

Problem with underscore character in variable name
by epidata-list＠lists.umanitoba.ca 19 Oct '08

19 Oct '08

According to the documentation, an underscore character is allowed in variable names. And, indeed, I have no problem defining new variable names with an underscore and using them in analysis (v2.1.0.151). However, when the data have been saved and one opens the file for further analysis, the variable has been renamed v1 (or v2, etc). In addition, the original variable name containing the underscore is put into the variable label. For example, I created a variable abc_test. After saving the data and opening the file, I find that the variable now has the name v1 and the label "abc_test abc-test". Annemieke van Middelkoop Pretoria, South Africa

1 1

Backup command: make routine snapshots without replacing previous backup (TIME STAMP?)
by epidata-list＠lists.umanitoba.ca 19 Oct '08

19 Oct '08

Hi EpiData users, I am trying out the backup function in CHK file: .... AFTER FILE BACKUP "D:/backupfolder" ENCRYPT file1 pw123 TODAY END ... What happens is the backup is created each time I close the "ENTER DATA" file in the "D:/backupfolder" as file1_19OCT08.ZKY. This is good. It replaces the previous backed-up ZKY file. I guess if I did this on another date (tomorrow) a new file will be created file1_20OCT08.ZKY, correct? So I would get DAILY snapshots of the data? Is there a way to specify a TIME stamp as well? Thanks S EDIT: Just writing this made me realise, why would one want a more frequent backup? Daily is sufficient. On Sat, Oct 18, 2008 at 7:02 PM, <epidata-list-request(a)lists.umanitoba.ca>wrote: > Send EpiData-list mailing list submissions to > epidata-list(a)lists.umanitoba.ca > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > or, via email, send a message with subject or body 'help' to > epidata-list-request(a)lists.umanitoba.ca > > You can reach the person managing the list at > epidata-list-owner(a)lists.umanitoba.ca > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of EpiData-list digest..." > > > EpiData-list mailing list > ___________________________________ > > Today's Topics: > > 1. EpiData Analysis v2.1 ready (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 18 Oct 2008 01:05:43 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] EpiData Analysis v2.1 ready > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <48F91A47.4000204(a)epidata.dk> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > V2.1 of EpiData Analysis has been placed for general download on the > http://www.epidata.dk/download.php > > All changes since last public release as v2.0 build 129 are documented in: > http://www.epidata.dk/analysisversioninfo.htm > > Main changes are: > 1 new commands: > Lifetable Lifetable and Kaplan-Meier plots, including estimation of > differences and testing of similarity btw. groups. > Stattables : summary reporting > CIplot: Plot of proportions and confidende intervals for strata defined > by other variables > Read /CB: read delimited data from clipboard, e.g. copied from > spreadsheets > 2 rewriting: > many commands and internal structures, including update and browse > 3 enhanced and clarified: > all outcome related estimation commands are synchronised with outcome > variable first. > enhanced options, e.g. /pct giving percentages on bar and histograms > graphs allowing /by > increased number of user "set" specifications including modifiable headers > percentiles for small n table based, see > http://www.epidata.dk/documentation.php > 4 bug removal > all known bugs removed > > Report and discuss on this list please. Definete errors should be > reported to the Mantis database > > More information on credits and funding later > - without this and user involvement in testing the development would not > be possible. > > regards > Jens Lauritsen > > > > > > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 60, Issue 11 > ******************************************** > -- Shuaib Kauchali Department of Paediatrics & Child Health Pietermaritzburg Metropolitan Hospitals Complex & University of KwaZulu-Natal Email: kauchalis(a)gmail.com Cell: +27-84-581-1142 Office: +27-33-897-3221 & -3230 (Secretary) Fax: +27-33-897-3409 No virus detected in this incoming message.

1 0

EpiData Analysis v2.1 ready
by epidata-list＠lists.umanitoba.ca 17 Oct '08

17 Oct '08

V2.1 of EpiData Analysis has been placed for general download on the http://www.epidata.dk/download.php All changes since last public release as v2.0 build 129 are documented in: http://www.epidata.dk/analysisversioninfo.htm Main changes are: 1 new commands: Lifetable Lifetable and Kaplan-Meier plots, including estimation of differences and testing of similarity btw. groups. Stattables : summary reporting CIplot: Plot of proportions and confidende intervals for strata defined by other variables Read /CB: read delimited data from clipboard, e.g. copied from spreadsheets 2 rewriting: many commands and internal structures, including update and browse 3 enhanced and clarified: all outcome related estimation commands are synchronised with outcome variable first. enhanced options, e.g. /pct giving percentages on bar and histograms graphs allowing /by increased number of user "set" specifications including modifiable headers percentiles for small n table based, see http://www.epidata.dk/documentation.php 4 bug removal all known bugs removed Report and discuss on this list please. Definete errors should be reported to the Mantis database More information on credits and funding later - without this and user involvement in testing the development would not be possible. regards Jens Lauritsen

1 0

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

16 Oct '08

Hello All!The new form of capturing data with PDA or Mobile application is known as Episurveyor and it is facilitated by WHO and datadyne. for free software please check www.datadyne.org Thanks Ras Sedzro On Thu, Oct 16, 2008 at 6:05 PM, <epidata-list-request(a)lists.umanitoba.ca>wrote: > Send EpiData-list mailing list submissions to > epidata-list(a)lists.umanitoba.ca > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > or, via email, send a message with subject or body 'help' to > epidata-list-request(a)lists.umanitoba.ca > > You can reach the person managing the list at > epidata-list-owner(a)lists.umanitoba.ca > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of EpiData-list digest..." > > EpiData-list mailing list > ___________________________________ > Today's Topics: > > 1. PDA entry (epidata-list(a)lists.umanitoba.ca) > 2. Alyshia Landry is out of the office. > (epidata-list(a)lists.umanitoba.ca) > 3. Re: PDA entry (epidata-list(a)lists.umanitoba.ca) > 4. Re: EpiData Analysis v2.1.0.150 available on testing.php > (epidata-list(a)lists.umanitoba.ca) > > > ---------- Forwarded message ---------- > From: epidata-list(a)lists.umanitoba.ca > To: epidata-list(a)lists.umanitoba.ca > Date: Wed, 15 Oct 2008 14:38:56 -0300 > Subject: [EpiData-list] PDA entry > I do not have any experience with PDA, but I have used a software called > PenDragon in a vaccine survey a time a go. This is used in palm tops. Its > functionallity is very similar to EpiData. > > I guess a I did not help much, > > Sorry, > > Pedro Brasil > > > > ---------- Forwarded message ---------- > From: epidata-list(a)lists.umanitoba.ca > To: epidata-list(a)lists.umanitoba.ca > Date: Wed, 15 Oct 2008 14:27:09 -0400 > Subject: [EpiData-list] Alyshia Landry is out of the office. > > I will be out of the office starting 10/15/2008 and will not return until > 10/17/2008. > > If you require immediate assistance, please contact Celina Sousa at > extension 5300. > > Thanks and have a wonderful day, > Alyshia > > > > > > ---------- Forwarded message ---------- > From: epidata-list(a)lists.umanitoba.ca > To: Epidata Mail List <epidata-list(a)lists.umanitoba.ca> > Date: Thu, 16 Oct 2008 09:30:58 +1100 > Subject: Re: [EpiData-list] PDA entry > See the email from WHO below - many thanks to Leanne. > > Best regards, > Maximilian de Courten MD, MPH > > On 15/10/2008, at 22:49, "Riley, Leanne" <rileyl(a)who.int> wrote: > > Thanks Max. Tony, my email at WHO is: >> >> rileyl(a)who.int >> >> We would be happy to share our survey software (we call it eSTEPS) with >> you. Best wishes, Leanne >> >> >> >> Leanne Riley >> Team Leader, Surveillance >> Department of Chronic Diseases and Health Promotion >> World Health Organization >> 20 Avenue Appia >> CH 1211 Geneva, Switzerland >> Tel: +41 22 791 4319 >> Email: rileyl(a)who.int >> >> Please consider the environment before printing this email >> >> -----Original Message----- >> From: de Courten Maximilian [mailto:max.decourten@med.monash.edu.au] >> Sent: 15 October 2008 03:45 >> To: epidata-list(a)lists.umanitoba.ca >> Cc: Riley, Leanne >> Subject: Re: [EpiData-list] PDA entry >> >> Hello Tony, >> >> The WHO has commissioned a PDA-based data capture software which is easy >> to use for any questionnaire, contains various types of question types >> (radio-button, tick-box, multiple answers, free-text fields, numeric >> fields) and safes the data in the .rec format. The software is available >> through WHO and was used in several surveys and some cost- comparison >> against paper-based surveys were done too. >> Best to contact Leanne Riley from WHO about its availability. >> >> Best regards >> Max >> >> On 15/10/2008, at 7:51 AM, epidata-list(a)lists.umanitoba.ca wrote: >> >> Does anyone have any experience or suggestions for suitable data >>> capture software on PDAs that will collect data in a form usable by >>> EpiData? >>> We're looking to do an immunisation survey. Flat file will be >>> sufficient, no need for related fields. >>> >>> Tony Stewart >>> _______________________________________________ >>> EpiData-list mailing list >>> EpiData-list(a)lists.umanitoba.ca >>> http://lists.umanitoba.ca/mailman/listinfo/epidata-list >>> >> >> > > > ---------- Forwarded message ---------- > From: epidata-list(a)lists.umanitoba.ca > To: epidata-list(a)lists.umanitoba.ca > Date: Wed, 15 Oct 2008 20:45:12 -0400 > Subject: Re: [EpiData-list] EpiData Analysis v2.1.0.150 available on > testing.php > Hi Jens, > > I've been playing with LIFETABLE and it seems to be functioning as > described. I am using the CANCER dataset that is provided with Stata. I have > not tried to reproduce results from Stata other than the graphs, which > match. So I assume the underlying life tables match. > > It would be nice to have a chance to eat somewhere in Stockholm on the > 27th. I don't know what time our meeting will end, but I don't think they > have dinner planned as most people may just be heading home. > > Shirley will be sightseeing on the 27th. > > Jamie > > epidata-list(a)lists.umanitoba.ca wrote: > >> Dear all >> >> I have placed version 2.1 of EpiData Analysis on the >> http://www.epidata.dk/testing.php for download. >> >> As always we cannot be sure if some "un-discovered" problems remain. But >> obviously by moving to general download there should be no problems >> resulting in e.g. wrong estimation or break-down. None such has been >> reported, only some very special issues remaining - which you can see in the >> Mantis database - but these will not affect the vast majority of users. >> >> If no major bugs show up within the next few days, the same version will >> be placed for general download. One of the aspects for which no feedback has >> been given is the lifetable and km-plot routines. >> >> The documentation in the form of the overall and detailed command >> reference has been updated. In the next months all the pdf based >> documentation will be revised and updated with current screen design etc. >> >> regards >> >> Jens Lauritsen >> EpiData Association >> _______________________________________________ >> EpiData-list mailing list >> EpiData-list(a)lists.umanitoba.ca >> http://lists.umanitoba.ca/mailman/listinfo/epidata-list >> >> > > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > -- SEDZRO KOJO MENSAH P.O.Box AS 387 Ashaiman -Tema Ghana House : +233-22-300789 MOBILE : +233-244-458788 -------------------------------------------------- The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

1 1

EpiData Analysis v2.1.0.150 available on testing.php
by epidata-list＠lists.umanitoba.ca 15 Oct '08

15 Oct '08

Dear all I have placed version 2.1 of EpiData Analysis on the http://www.epidata.dk/testing.php for download. As always we cannot be sure if some "un-discovered" problems remain. But obviously by moving to general download there should be no problems resulting in e.g. wrong estimation or break-down. None such has been reported, only some very special issues remaining - which you can see in the Mantis database - but these will not affect the vast majority of users. If no major bugs show up within the next few days, the same version will be placed for general download. One of the aspects for which no feedback has been given is the lifetable and km-plot routines. The documentation in the form of the overall and detailed command reference has been updated. In the next months all the pdf based documentation will be revised and updated with current screen design etc. regards Jens Lauritsen EpiData Association

1 1

Re: [EpiData-list] PDA entry
by epidata-list＠lists.umanitoba.ca 15 Oct '08

15 Oct '08

See the email from WHO below - many thanks to Leanne. Best regards, Maximilian de Courten MD, MPH On 15/10/2008, at 22:49, "Riley, Leanne" <rileyl(a)who.int> wrote: > Thanks Max. Tony, my email at WHO is: > > rileyl(a)who.int > > We would be happy to share our survey software (we call it eSTEPS) > with > you. Best wishes, Leanne > > > > Leanne Riley > Team Leader, Surveillance > Department of Chronic Diseases and Health Promotion > World Health Organization > 20 Avenue Appia > CH 1211 Geneva, Switzerland > Tel: +41 22 791 4319 > Email: rileyl(a)who.int > > Please consider the environment before printing this email > > -----Original Message----- > From: de Courten Maximilian [mailto:max.decourten@med.monash.edu.au] > Sent: 15 October 2008 03:45 > To: epidata-list(a)lists.umanitoba.ca > Cc: Riley, Leanne > Subject: Re: [EpiData-list] PDA entry > > Hello Tony, > > The WHO has commissioned a PDA-based data capture software which is > easy > to use for any questionnaire, contains various types of question types > (radio-button, tick-box, multiple answers, free-text fields, numeric > fields) and safes the data in the .rec format. The software is > available > through WHO and was used in several surveys and some cost- comparison > against paper-based surveys were done too. > Best to contact Leanne Riley from WHO about its availability. > > Best regards > Max > > On 15/10/2008, at 7:51 AM, epidata-list(a)lists.umanitoba.ca wrote: > >> Does anyone have any experience or suggestions for suitable data >> capture software on PDAs that will collect data in a form usable by >> EpiData? >> We're looking to do an immunisation survey. Flat file will be >> sufficient, no need for related fields. >> >> Tony Stewart >> _______________________________________________ >> EpiData-list mailing list >> EpiData-list(a)lists.umanitoba.ca >> http://lists.umanitoba.ca/mailman/listinfo/epidata-list >

1 0

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

15 Oct '08

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

1 0

PDA entry
by epidata-list＠lists.umanitoba.ca 15 Oct '08

15 Oct '08

I do not have any experience with PDA, but I have used a software called PenDragon in a vaccine survey a time a go. This is used in palm tops. Its functionallity is very similar to EpiData. I guess a I did not help much, Sorry, Pedro Brasil

1 0

PDA entry
by epidata-list＠lists.umanitoba.ca 14 Oct '08

14 Oct '08

Does anyone have any experience or suggestions for suitable data capture software on PDAs that will collect data in a form usable by EpiData? We're looking to do an immunisation survey. Flat file will be sufficient, no need for related fields. Tony Stewart

1 1

OR error report
by epidata-list＠lists.umanitoba.ca 14 Oct '08

14 Oct '08

This is concerning to v2.0.3.129 EpiData Analysis. Recently I dig in to OR and RR using said version. The data base I used was one used in SPSS to do the same. In essence, the calculation result were different from what I obtained from SPSS, given that I recoded outcomes and risk exposures, i.e. 1=2, 2=1. (SPSS uses ascending order for both outcomes and risk exposures, 1 codes as positive 2 as negative which is just the opposite of EpiData Analysis handling) EpiData Analysis result: OR=3.68 (95% CI: 1.03-11.89)Fishersexact p= 0.0224 SPSS result: OR=3.72 (3.7158) (95% CI: 1.27039-10.86604) Fishersexact p=.02239 Whereas RR resulted the same. EpiData Analysis: RR = 2.86 (95% CI: 1.31-6.24)Fishersexact p= 0.0224 SPSS: RR = 2.86 (2.85789) (95% CI: 1.30965-6.23646) USING CELL OBSERVED FREQUENCIES AS A=6, B=13, C=20, D=161 WHEREAS A:C1R1, B:C2R1, C:C1R2, D:C2R2. I wonder if the formula used by EpiData Analysis is OR=(A/C)/(B/D)=(A/B)/(C/D)= (AD)/(BC). The OR as well as corresponding CI are different from that of SPSS. The attached .dbf file uses RV3 as outcome variable and RRIESGO as risk exposure variable using code 2 as positive for both variables.

1 3

Problem with STATTABLES command
by epidata-list＠lists.umanitoba.ca 10 Oct '08

10 Oct '08

Good morning Jens, I have a problem with saving the results of a stattables command to another file. The command I use is: stattables bcg3 /stat="sum" /by="mth" save="c:\downloads\epidata\testsave.rec" (In analysis, this command is all on one line) I have not had this problem with versions prior to build 148. The correct table is produced in the output screen, but the testsave.rec file is not created. Nor is there any indication in analysis that there might be a problem. I have tried specifying the full path (as in this example) as well as just specifying the filename testsave.rec. I have also tried it with the /replace option. Annemieke van Middelkoop Pretoria, South Africa

1 1

Adapted EpiData Analysis b149 ready
by epidata-list＠lists.umanitoba.ca 08 Oct '08

08 Oct '08

A few errors have been reported in the b148 of analysis of last week. These are now fixed, and a new build uploaded for testing. (Users who have taken b148 and are not using compact tables can continue with b148 and report). If no major bugs are found the build 149 will be released as v2.1 at the end of this week for general use replacing current build 2.0 on the download page. regards Jens Lauritsen EpiData Association

1 0

multiple response (& server is up again)
by epidata-list＠lists.umanitoba.ca 07 Oct '08

07 Oct '08

The server is now up and running again. (All scripts have been checked - there were no problems, but only assumed problems). Off list the following question was asked regarding EpiData Analysis > Hi There, > I have a question that i am trying to evaluate with a multi response answer. > I have set out the question as follow with a text variable for each answer: > > Q1: What fruit do you like _ _ _ _ _ > a - Apples b - Orange c - Banana d - Pear e - Grapes > Now when i go to analyse this, is there a way i can graph the response > for this answer on a bar graph? I cannot seem to be able to add > multiple series into the graph to compare all answers for this question? Currently bar graphs can only take one variable at a time. Except for box and scatter/line plots for several variables. Box plots for several variables has just been introduced with the pre v2.1 - v2.0.5.148 version. For all graphs a /by variable has been introduced, but this does not change the basic limitation of one variable per plot. What you could do to analyse the data is to use stattables and count binary indicators calculated like this: gen i apple = (pos(q1, "a" ) > 0) gen i orange = (pos(q1, "b" ) > 0) etc for the other fruits. stattable apple orange ......../stat="sum" /N /close * then in the new file with counts of the fruits and the total some percentages could be worked out. A graph showing the combinations of the variables in the form of a VENN diagram could be a solution, but currently this cannot be done with EpiData Analysis. I wrote a command for Stata for this: See: http://www.stata.com/products/stb/journals/stb47.pdf . The initial version has been extended with four factor ellipses. We could consider including Venn diagrams in a later version (but at the earliest second quarter 2009) and also a multiple response tables command. regards Jens Lauritsen EpiData Association

1 0

website epidata.dk is down due to attempts of "phishing"
by epidata-list＠lists.umanitoba.ca 06 Oct '08

06 Oct '08

The webserver company claims someone tried to use the epidata.dk site for spamming. I will notify when the server is up again. regards Jens Lauritsen EpiData Association

1 0

Final test version of rel 5 v2.0.5.148 placed on testing.php page
by epidata-list＠lists.umanitoba.ca 01 Oct '08

01 Oct '08

The final build for testing of release candidate of v2.1 EpiData Analysis has been placed on the page: http://www.epidata.dk/testing.php After testing of build 148 by users this will be released as v2.1 replacing current general download version, which has a number of known problems/bugs. Please report any problem with b148 to the list or discuss principles here. There will be NO further implementation of function before release of v2.1 - only fixing any bugs reported. Many issues have been solved - among these unification of commands, new lifetable and stattable command and fixing titles for graphs. Among many other extensions the possibility of making box plots for several variables in the same graphs and further user "set" specifications of headers in table and output can be mentioned. The principle of /by variable has been implemented where relevant, and a new reporting oriented command stattable has been introduced, where summary measures can be used. Unification means that all tables or graphs working with an outcome variable will have this variable first, examples: epicurve outcome timevar lifetable outcome timevar tables outcome exposure ciplot outcome variables The lifetable takes on two forms with explicit time variable and the possibility of giving as well "date of entry" and "date of exit", plus an option /MT "missing time" to indicate how to handle missing data on the "exit" variable, e.g. when follow-up is still ongoing. Lifetable implements the principles of confidence intervals published by Altman et al in "statistics with confidence" e.g. estimates at specified levels of survival (median and quartiles) or survival with confidence intervals at specified times. The plan is to implement other "Statistics with confidence - CI principles" in the coming year. All commands are documented in the commands.htm file, which will be shown when hitting the F1 button with an empty command prompt. (But I am quite sure, there could be some deficiencies in the documentation, so please report these). I wish to give credit for the current extension and intensified development, which is only possible by funding of full time academic programmer for the project by various projects credited on the www.epidata.dk/funding.htm page and the willingness of people to take on tasks. More about the funding sources and staff listing will be revealed when v2.1 is released. Work now continues with implementation of further SPC (statistical process control) graphs, these will be included for general use accompanied by full implementation of translation in v2.5. regards Jens Lauritsen EpiData Association

1 0

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

30 Sep '08

I will be out of the office starting 09/27/2008 and will not return until 10/06/2008. If you require immediate assistance, please contact Celina Sousa at extension 5300. Thank-you, Alyshia

1 0

numerical to date chk?
by epidata-list＠lists.umanitoba.ca 30 Sep '08

30 Sep '08

Dear Epidata list, I am looking for a way to generate a date-variable from a numerical-variable. i.e. I will type in the Danish central person registration number (10 digits where the 6 first digits are the birthday ddmmyy) I would like to automatically create a date variable from this - to calculate ages at later dates. I have looked for a chk that would do it, but couldn't find any. Does anybody have a solution? (and sorry if this has been discussed before, I searched and couldn't find any relevant discussion threads) thanks in advance, Drude Molbo, data admin dept. of social medicine, KU DK

1 1

Opening html files in excel and using not equal to blank with date fields
by epidata-list＠lists.umanitoba.ca 15 Sep '08

15 Sep '08

One comment and one query Use of brackets in AR% column I just wondered if it was necessary to use brackets in the AR% tables in attack rate tables. The reason I ask is that when I open an Epidata output (html file) using Excel the AR% columns show as negative numbers - I suppose because Excel thinks the brackets indicate a negative number. Not equal to blank in date fields I am having trouble wtih an if then statement where I want to do something if a date field is not blank. I know that Epidata will accept (.) for blank dates as it accepts If vomdate =(.) and diadate = (.) then onsetdate = (.) But it does not accept If vomdate =(.) and diadate <> (.) then onsetdate = diadate Could someone please suggest a better code for "not blank" with a date field? thanks Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 -- The information contained in this email and any attachments is confidential and may be legally privileged. If you have received this message in error, please notify the sender immediately and remove all copies of the message, including any attachments. Any views or opinions expressed in this email (unless otherwise stated) may not represent those of Hutt Valley DHB. Thank you. ** Disclaimer added by HVDHB **

1 1

Another question about SPC
by epidata-list＠lists.umanitoba.ca 11 Sep '08

11 Sep '08

I am trying to use EpiData to display information about Healthcare Associated Infections, such as MRSA and C difficile. I was wondering if SPC charts can be used to show actual and cases against targets. Please see an example attached of what I am trying to achieve. This has been done in excel (I think!) Thanks, Shakeel ----------------------------------------- ************************************************************************** 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

EPIC bug report - fails on Stata7 option.
by epidata-list＠lists.umanitoba.ca 11 Sep '08

11 Sep '08

EPIC.exe has a bug. It failes with a pointer error Access Violation when trying to use the export to "Stata7" option. It does leave a small Stata .dta file which has a size of 717 bytes. Stata hangs on trying to open this small file. Specifying the Stata, Stata5 and Stata6 options works fine. I've tried the command in various formats (lower/uppercase etc), on local hard drive, network drive etc. Windows XP. Any chances of a quick fix? This is a problem for me because Stata6 only has 8-character variable names, whereas Stata7 doesn't have this limitation. With EpiC, my Stata data cleaning process could work automatically from the most recent data entry version. Would a 200 Euro donation to the Epidata association help fix this problem at some point in time? HERE IS AN ERROR LOG: ==================== C:\tmp>EpiC.exe export stata7 file1.rec file1.dta EpiC - the EpiData command application version 3.1 10. Jan. 2006 (C) Copyright 2002-2006 - EpiData Association, http://www.epidata.dk Programmed by M.Bruus. Design: JM.Lauritsen & M.Bruus 0 % doneException EAccessViolation in module EpiC.exe at 00001C3C. Access violation at address 00401C3C in module 'EpiC.exe'. Write of address 0000 0004. ==================== Yours, Jan Brogger

1 0

SPC Charts
by epidata-list＠lists.umanitoba.ca 10 Sep '08

10 Sep '08

Hello, Is it possible to create SPC Charts in Epidata Analysis- if so, what is the procedure? Thanks Shakeel ----------------------------------------- ************************************************************************** The information contained in the EMail and any attachments is confidential and intended solely and for the attention and use of the named addressee(s). It may not be disclosed to any other person without the express authority of the HPA, or the intended recipient, or both. If you are not the intended recipient, you must not disclose, copy, distribute or retain this message or any part of it. This footnote also confirms that this EMail has been swept for computer viruses, but please re-sweep any attachments before opening or saving. HTTP://www.HPA.org.uk **************************************************************************

1 1

Two questions
by epidata-list＠lists.umanitoba.ca 09 Sep '08

09 Sep '08

Hello, 1- In Analysis, the width of variable codes is 20 characters with "freq" or "tables". Is it possible to increase this width ? I have variable codes> 20 characters. 2- In related file ("daughter file"), I need, for a calculation, of a variable in "father file". How to proceed ? Thank you. Bernard BRANGER, Nantes, France

1 2

Help needed
by epidata-list＠lists.umanitoba.ca 08 Sep '08

08 Sep '08

I am new to epi-data analysis. I set up a test file called test.csv to practice. However, I am getting the following message. Any advice would be appreciated: Access is denied Operation aborted Separators: (tab: 0)(semicolon: 0)(comma: 0)(space: 0) Lines: 1 Cannot define number of variables .. check data file - cannot open.. Operation aborted Operation aborted Separators: (tab: 0)(semicolon: 0)(comma: 0)(space: 0) Lines: 1 Cannot define number of variables .. check data file - cannot open.. Operation aborted Operation aborted ----------------------------------------- ************************************************************************** The information contained in the EMail and any attachments is confidential and intended solely and for the attention and use of the named addressee(s). It may not be disclosed to any other person without the express authority of the HPA, or the intended recipient, or both. If you are not the intended recipient, you must not disclose, copy, distribute or retain this message or any part of it. This footnote also confirms that this EMail has been swept for computer viruses, but please re-sweep any attachments before opening or saving. HTTP://www.HPA.org.uk **************************************************************************

1 1

Re:EpiData-list Digest, Vol 59, Issue 4
by epidata-list＠lists.umanitoba.ca 06 Sep '08

06 Sep '08

Hi, Peter Thanks for your help. We are using Java as the primary language in the project. It seems that you also try to do a job like that. We will contribute the Java code to the community if possible :) 2008-09-06，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: Where can I get the file format's specification for both > .qes and .rec files? (epidata-list(a)lists.umanitoba.ca) > 2. Help needed (epidata-list(a)lists.umanitoba.ca) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Thu, 04 Sep 2008 15:09:12 -0400 >From: epidata-list(a)lists.umanitoba.ca >Subject: Re: [EpiData-list] Where can I get the file format's > specification for both .qes and .rec files? >To: epidata-list(a)lists.umanitoba.ca >Message-ID: <48C03258.5050708(a)ix.netcom.com> >Content-Type: text/plain; charset=x-gbk > >The .REC files are described in the pdf document Data File Structure: >http://www.epidata.dk/php/downloadc.php?file=epidata_datafile.pdf > >What language do you plan to use to re-organize all of this? > >Peter Geddes >geddes(a)ix.netcom.com > >epidata-list(a)lists.umanitoba.ca wrote: >> Hi, >> >> I am working on a goverment project in which we have to handle about 3000 EPIData files. Different fields exist in different files and the same field's names are not extract matched among files such as age0 and ageForFirstTime. >> >> Obviously, it takes too much human resources to merge those files and we want to develop a program to do the job. And we have to know the file format for both .qes and .rec files. >> >> Does anyone knows where we can get the specification for those files? >> >> >> >> _______________________________________________ >> EpiData-list mailing list >> EpiData-list(a)lists.umanitoba.ca >> http://lists.umanitoba.ca/mailman/listinfo/epidata-list >> >> >> > > >------------------------------ > >Message: 2 >Date: Fri, 5 Sep 2008 14:07:55 +0100 >From: epidata-list(a)lists.umanitoba.ca >Subject: [EpiData-list] Help needed >To: >Message-ID: > >Content-Type: text/plain; charset="us-ascii" > >I am new to epi-data analysis. I set up a test file called test.csv to >practice. However, I am getting the following message. Any advice would >be appreciated: > > > >Access is denied > >Operation aborted > >Separators: (tab: 0)(semicolon: 0)(comma: 0)(space: 0) Lines: 1 > >Cannot define number of variables > >.. check data file - cannot open.. > >Operation aborted > >Operation aborted > >Separators: (tab: 0)(semicolon: 0)(comma: 0)(space: 0) Lines: 1 > >Cannot define number of variables > >.. check data file - cannot open.. > >Operation aborted > >Operation aborted > > > > > >----------------------------------------- >************************************************************************** >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 >************************************************************************** > >------------------------------ > >________________________________________ >EpiData-list(a)lists.umanitoba.ca >http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > >End of EpiData-list Digest, Vol 59, Issue 4 >*******************************************

1 0

Where can I get the file format's specification for both .qes and .rec files?
by epidata-list＠lists.umanitoba.ca 04 Sep '08

04 Sep '08

Hi, I am working on a goverment project in which we have to handle about 3000 EPIData files. Different fields exist in different files and the same field's names are not extract matched among files such as age0 and ageForFirstTime. Obviously, it takes too much human resources to merge those files and we want to develop a program to do the job. And we have to know the file format for both .qes and .rec files. Does anyone knows where we can get the specification for those files?

1 1

Mailing List
by epidata-list＠lists.umanitoba.ca 04 Sep '08

04 Sep '08

Sir, Please include my email in the mailing list Olaniyan, M.A madeolaniyan(a)gmail.com

1 0

"run error" in analysis test build 145/46 fixed
by epidata-list＠lists.umanitoba.ca 03 Sep '08

03 Sep '08

The error mentioned on the list of "graph dialog and "run" has been fixed. For this reason a new build 147 is now on the test site. Usually we will not put out this many builds, but since the dialogs are a crucial part of the testing I decided to do so. Regarding the other comment : "2. Correlation coefficient “r” information needs some face lift. Can the coefficient of determination, r2 that is the measure of meaningfulness of “r “ is provided?" I can only agree. The whole linear regression and correlation part will be rewritten, but I do not expect this to happen before early 2009. Some issues in relation to translation are being worked upon. V2.1 will not be released in general before these are settled. Kind regards Jens Lauritsen

1 0

copying data btw. file levels in related entry (type comment)
by epidata-list＠lists.umanitoba.ca 03 Sep '08

03 Sep '08

Pedro wrote: "The first problem here is that the field name can not automaticaly be inserted in the projectresult.rec, such as with TYPE COMMENT. " There is a way to transfer data which could then be added as shown in the samples with EpiData Entry, - house-person-visit, where name and status of each person is transferred and shown on the screen next to the entry field. In the visit.chk file: (notice global) BEFORE FILE DEFINE varNAME _________________________________ GLOBAL DEFINE varAGE ### GLOBAL DEFINE varSEX _ GLOBAL DEFINE varILL _ GLOBAL HELP "Please enter names etc. for all persons living in \n \n @varADDRESS \n @varCITY" END in the visit.chk: BEFORE FILE define info _________________________________________________ END Before record * these come from the person file: let info = varNAME + " Age: " + varAGE + " Sex: " + varSEX + " Ill: " + varILL end VISIT BEFORE ENTRY type "@info" END END The same technique could take your name entered at an upper level and saved also in the next level. (instead of the "type" here) regards Jens Lauritsen EpiData Association

1 0

I think a found a bug
by epidata-list＠lists.umanitoba.ca 03 Sep '08

03 Sep '08

Jens, I think a found a bug. I was having a difficult time to look at a simple dataset at Stata to control patients inclusion. After several try outs and different sorts, I found that some dates were changed. That is... paciente that recruited in june had dates in july, some that were at the 25aug2008 were shown as 1aug2008. At first, I tought that was typing error. Than I checked one by one and most of it were correct at the epidata dataset but wrong in the stata dataset. Thereofre I think there is something wrong in the export tool to stata format. Later I will try other ways, and softwares of export data to see if the same dates keep coming wrong. Did anyone have any experience like this? Also I found yesterday that EpiData does not import from Stata 10, only Stata9/8. Any update soon? -- Abraço forte e que a força esteja com você, Pedro Emmanuel

1 0

Epi Analysis test release 146 (2nd Sept) - Few suggestions
by epidata-list＠lists.umanitoba.ca 03 Sep '08

03 Sep '08

Dear Jens, It is heartening to see that the development of Epidata Analysis is continuing at rapid pace. Few suggestions; 1. The graphs have been disabled. None of graph dialog box is opening. 2. Correlation coefficient r information needs some face lift. Can the coefficient of determination, r2 that is the measure of meaningfulness of r is provided? It is only a square of r, one might say, but multiple r2 calculations from one database can be cumbersome. EPI6 was providing both r and r2 with 95% confidence intervals also. 3. Epi Analysis development is hard work but you are fast approaching the release of a wonderful product that will be far better then EPI6 while preserving its full functionality. With regards, Shavinder Singh

1 0

Re: EpiData-list Digest, Vol 58, Issue 10
by epidata-list＠lists.umanitoba.ca 02 Sep '08

02 Sep '08

Dear EpiData friends, I figure out a workaround for my problem at last, the only problem now is that my partner has a preference in typing the name of the patient two or three time then to work with the solution. To remind: Im typing data from patients in which each colects 3 blood samples so my qes looks something like: identifier #### name<A > samplenumber # result # Assuming that my patients will be inserted in the data file three times each, I wanted to avoid differences in the typing of the names, such as missing letter or middle names comes in one record but not in the other. so the solution was: projectID.qes identifier #### name<A > projectID.chk identifier key unique end name key relate identifier projectresult.rec end projectresult.qes identifier #### samplenumber # result # projectresult.chk identifier key 1 Autosearch list identifier END The first problem here is that the field name can not automaticaly be inserted in the projectresult.rec, such as with TYPE COMMENT. By consequence, later I will have to merge the two files side by side to have the name of the patient or other id fileds in the results file (not very difficult but not automatic). The work around to see the name while typing is to tile the related windows horizontaly, then one can see the name and the number of the patient at the top of the screen and the data at the botton at the same time. The second problem is that autosearch does not work in the child file. It is necessary to navigate (F7 or F8) by the (few) records of each patient to reach a new empty record for that patient, and at last, for some unknown reason my partner, who is typing the data, likes better to work only with one screen. The idea of pressing F8 to find a new record and F10 each end of child record to return to the parent record did not seem to be atractive. Maybe Jens could consider a "autocomplete" check command for string fileds for a future update of EpiData entry. Best regards for all, Pedro Brasil 2008/8/30 <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: Repeat values in other records > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 30 Aug 2008 01:18:53 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Re: Repeat values in other records > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <48B883DD.7010603(a)epidata.dk> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > "I looked for in several chk commands but didnt figure out a solution > yet. Isit possible, when the cursor is at the name field and a type > "Mary", EpiData shows all the "Mary" already in the rec file, so I could > pick one of them ....." > > Look in helpfile for EpiData Entry under "Autosearch" > AUTOSEARCH > Autosearch is a look-up function that checks the remaining data file for > records with certain data. Look-up can be defined to be on one field or > a combination of several fields. > > Let us know on the list your solution - and experiences > > Regards > Jens Lauritsen > EpiData Association > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 58, Issue 10 > ******************************************** >

1 0

New EpiData Analysis ready for test - again
by epidata-list＠lists.umanitoba.ca 02 Sep '08

02 Sep '08

Some problems with menu dialogs showed up in b145 which made me release b146 today of EpiData Analysis. The main difference from yesterday (b145) is changes to CIPLOT dialog. But unfortunately today we have discovered a number of problems with the dialogs as well in b146: "RUN" button does not work - use "execute" instead. means dialog takes wrong variables to the command line For some graphs the x and y texts are missing. The main problem this shows is that in addition to the batch testing which we do on estimates etc. some principle of testing user interface should be added. Another issue reported is very small font size in printing. If someone have experienced this let us know - in particular if there is a solution regards Jens Lauritsen EpiData Association

1 0

input data in selected fields
by epidata-list＠lists.umanitoba.ca 02 Sep '08

02 Sep '08

i would suggest the following procedure: 1. create a data entry file with all fields and add your checks for 81-85 2. HIDE all fields except 81-85 3. JUMP to 81 after opening a record 4. AUTOSAVE after 85 hope this helps, Markus epidata-list-request(a)lists.umanitoba.ca schrieb am 25.08.2008 19:08: > 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. input data in selected fields (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 25 Aug 2008 10:47:48 -0500 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] input data in selected fields > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <200808251556.m7PFu8PX002301(a)tunku.uady.mx> > Content-Type: text/plain; charset="iso-8859-1"; format=flowed > > Dear members in the list > > I have a database with about 2000 records, each > one with 90 fields. I want to input information > that is missing in fields 81 to 85. I would like > to use an entry screen that shows me only field > 81 to 90. This is because I have a chk file that > has command that produce information in fields 86 > to 90, based on the information I input in fields 81 to 85. > Is it possible to do that to make a simplified > entry screen to use only a fraction of the fields in the data base? > I will appreciate your help > > Jose > Mexico > > > Dr. Jose Arturo Farfan Ale > Centro de Investigaciones Regionales > "Dr. Hideyo Noguchi" > Universidad Autónoma de Yucatán > Av. Itzáes por 59, num. 490 > Mérida, Yucatán, México 97000 > Tel: (999) 923-22-74 > (999) 924-57-55 > Fax: (999) 923-61-20 > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 58, Issue 7 > ******************************************* >

1 0

New EpiData Analysis ready for test
by epidata-list＠lists.umanitoba.ca 01 Sep '08

01 Sep '08

Just uploaded: Version 2.0.5 build 145 Release candidate for v2.1 * Extended or adapted function o lifetable :New command for life tables and Kaplan Meier plots o New syntax for compact tables: tab outcome variables /ct [/OA /O /RR] o Uniform syntax for lifetable, epicurve, compact tables, ciplot cmd outcome ..... The outcome variable is the first one o Uniform options for No Confidence Interval: /NOCI (lifetables, ciplot) o SPC charts: to exclude information on central values: /NCVI o More table headers in control of user, see: set table ct ..., set lifetable header ... * Bugs fixed o /c=xxx can now be used for value labels with string variables o percent signs cannot be used in lines with a comment * o Sorting tables now correct in dialogs and /fv tables o Table dialog for Pareto corrected to take string variables o Extra lines on graph PNG files removed (bottom and right side) o other bugs fixed See full information on the testing and analysis version files referenced on Http://www.epidata.dk/testing.php A decision has been made to include lifetables and Kaplan Meier plots in next release (v2.1). Please test this in the just uploaded build. The command accepts two different syntax forms: lifetable outcome time lifetable outcome startdate enddate We are still clarifying some aspects of translation, which necessitates postponing v2.1 release. Another issue being investigated just now is the possibility to include new SPC graph types. The main objective for v2.1 release is that after release a major rebuild will take place of structures not updated since the very first analysis parts and also allow for user defined add-on modules. regards Jens Lauritsen EpiData Association

1 0

EpiData-list Digest
by epidata-list＠lists.umanitoba.ca 31 Aug '08

31 Aug '08

Hello, In Analysis, the width of variable codes is 20 characters With "freq" or "tables". Is it possible to increase this width ? I have variable codes> 20 characters. Thank you. Bernard BRANGER, Nantes, France

1 0

Re: Repeat values in other records
by epidata-list＠lists.umanitoba.ca 29 Aug '08

29 Aug '08

"I looked for in several chk commands but didnt figure out a solution yet. Isit possible, when the cursor is at the name field and a type "Mary", EpiData shows all the "Mary" already in the rec file, so I could pick one of them ....." Look in helpfile for EpiData Entry under "Autosearch" AUTOSEARCH Autosearch is a look-up function that checks the remaining data file for records with certain data. Look-up can be defined to be on one field or a combination of several fields. Let us know on the list your solution - and experiences Regards Jens Lauritsen EpiData Association

1 0

Repeat values in other records
by epidata-list＠lists.umanitoba.ca 29 Aug '08

29 Aug '08

Dear EpiData friends, Im storing data form a particular a research of a diagnostic test. Each patient will colect three samples during the protocol. Each sample should be at least one week apart from each other. This means that the name and number of the patient (but not the sample) is repeated trhee times, but most likely, not in consecutive records. I looked for in several chk commands but didnt figure out a solution yet. Is it possible, when the cursor is at the name field and a type "Mary", EpiData shows all the "Mary" already in the rec file, so I could pick one of them and fill the name exactly as filled in the first patient record? The objective here is to avoid things such as: record 1: name: "Mary Smith" patientnumber: 1 samplenumber: 1 record 23: name: "Mary Bush Smith" patientnumber: 1 samplenumber: 3 In Openoffice spreadsheet, for example, when I start typing a name that was typed before a sugestion to complete appears. It does not have to be exactly like this but something similar. -- Abraço forte e que a força esteja com você, Pedro Emmanuel

1 0

Entry in selected fields
by epidata-list＠lists.umanitoba.ca 26 Aug '08

26 Aug '08

Jose, I guess your question was recently questionned and answered in this list. I sugest you look for past emails in the list to see if the a possible solutions is waiting for you elsewhere. Simple way to do that is open you original rec file to enter data as usual. Find the record you want to update. (this could be done by a autoserach or key unique or Ctrl+F) Press F4 and a field with which variable you want the cursor to go will appear. e.g. fill with v85 Update the fields u want then press Ctrl+N (or F7 or F8) and save the updated record. This is the easiest way I can imagne, but you will see all fields in the file, not only those fields you will update. A more complicated way is to export the file to epidata format filtering the variables you want with the unique identifier of each record: say chart number and v85 to v91 (use option 6 of the numbered menu, it is very intuitive) Update the file as usual. Merge (last option of the third EpiData menu from left to right) your new file with the old one side by side, with the new one updating the old - this is also very intuitive in EpiData. Good luck, Pedro Brasil

1 0

Re: EpiData-list Digest, Vol 58, Issue 7
by epidata-list＠lists.umanitoba.ca 26 Aug '08

26 Aug '08

Jose, I guess your q

1 0

Epidemiologists in French Language
by epidata-list＠lists.umanitoba.ca 25 Aug '08

25 Aug '08

Bonjour, A l'occasion du Congrès de l'ADELF à Paris les 15, 16 et 17 octobre, une réunion d'utilisateurs d'EPIDATA pourrait s'envisager dans le cadre déchanges mutuels des utilisations et des « recettes ». Merci de votre avis. Sinon, une réunion en 2009 serait-elle plus opportune ? A Nantes, par exemple. Merci. Bernard BRANGER, NANTES Tel 02 40 48 55 81 Voir les documents relatifs à Epidata Sur notre site www.reseau-naissance.fr <http://www.reseau-naissance.fr/> Page Epidémiologie

1 1

input data in selected fields
by epidata-list＠lists.umanitoba.ca 25 Aug '08

25 Aug '08

Dear members in the list I have a database with about 2000 records, each one with 90 fields. I want to input information that is missing in fields 81 to 85. I would like to use an entry screen that shows me only field 81 to 90. This is because I have a chk file that has command that produce information in fields 86 to 90, based on the information I input in fields 81 to 85. Is it possible to do that to make a simplified entry screen to use only a fraction of the fields in the data base? I will appreciate your help Jose Mexico Dr. Jose Arturo Farfan Ale Centro de Investigaciones Regionales "Dr. Hideyo Noguchi" Universidad Autónoma de Yucatán Av. Itzáes por 59, num. 490 Mérida, Yucatán, México 97000 Tel: (999) 923-22-74 (999) 924-57-55 Fax: (999) 923-61-20

1 2

Re: Codebook writing: Error message
by epidata-list＠lists.umanitoba.ca 21 Aug '08

21 Aug '08

Try to do the following: 1. Install EpiData Analysis from http://www.epidata.dk 2. Read the data file (copy number one or two) 3. write in the command prompt: describe 4. Look at your results and see if the minimum, maximum etc are as you expect. If some variable is completely strange - e.g. all with no content then re-run in EpiData Entry the codebook without check mark for that variable. regards Jens Lauritsen (write to me directly at info (at) epidata.dk if no solution comes up. EpiData Association

1 0

Re: EpiData-list Digest, Vol 58, Issue 5
by epidata-list＠lists.umanitoba.ca 21 Aug '08

21 Aug '08

Hey Elize! I guess it means it is dividing by a value "0" (zero), how does your denominator look like? you can read more about this math expression under http://en.wikipedia.org/wiki/Division_by_zero Hope this helps Best regards ziad NICD, Johanneburg On Thu, Aug 21, 2008 at 10:08 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. Codebook writing: Error message (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 20 Aug 2008 21:15:46 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Codebook writing: Error message > To: "Epidata" <epidata-list(a)lists.umanitoba.ca> > Message-ID: <48AC8982.271E.00B1.0(a)up.ac.za> > Content-Type: text/plain; charset=US-ASCII > > Hi > > I am trying to write a codebook from a dataset that has been entered in Double Verification mode. I have 588 records in the dataset. > > The error message is: "Floating point division by zero". What does this mean and how can I fix the problem so that I can write the Codebook? > > Elize Webb > University of Pretoria > South Africa > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 58, Issue 5 > ******************************************* >

1 0

Codebook writing: Error message
by epidata-list＠lists.umanitoba.ca 20 Aug '08

20 Aug '08

Hi I am trying to write a codebook from a dataset that has been entered in Double Verification mode. I have 588 records in the dataset. The error message is: "Floating point division by zero". What does this mean and how can I fix the problem so that I can write the Codebook? Elize Webb University of Pretoria South Africa

1 0

hiding field from the entry form
by epidata-list＠lists.umanitoba.ca 14 Aug '08

14 Aug '08

Dear members in the group I am working with a data base with more than 90 variables. I want to incorporate some information in selected 5 or 6 field. I want to use an entry mask that only display the fields I will work on so I can have the benefits of using the information in the chk list. BEFORE RECORD HIDE STUDY HIDE CONSENTIMI HIDE ETNIAN HIDE ETNIA HIDE NAME . . END That works but is displays all the entry form (preventing the data entry in the hidden fiels. Is there any way to prevent that the hidden variables are displayed in the screen? I am attaching the QES file thank you in advance Jose Arturo Dr. Jose Arturo Farfan Ale Centro de Investigaciones Regionales "Dr. Hideyo Noguchi" Universidad Autónoma de Yucatán Av. Itzáes por 59, num. 490 Mérida, Yucatán, México 97000 Tel: (999) 923-22-74 (999) 924-57-55 Fax: (999) 923-61-20

1 0

New test build 141 for EpiData Analysis
by epidata-list＠lists.umanitoba.ca 10 Aug '08

10 Aug '08

Another build of EpiData Analysis is now ready from http://www.epidata.dk/testing.php Thanks to several users for reporting smaller and larger bugs. All reported major bugs been removed in build 141. Some problems will not be removed until a complete rewrite, e.g. related to regression and correlation. Users can see these on the mantis system as http://www.epidata.dk/php/mantis/login_page.php Acknowledged issues here means they will be handled later. The only problems currently not investigated or decided upon are : - small sample size percentiles - some strange test results for some situations of gamma and Chi2. - global variables (define .... global) are not completely independent of settings in windows The main news since current public release is: - removal of many small bugs and inconsistencies New or rewritten commands: - CIPLOT: new command to show proportions and Confidence Interval - HELPVIEW: new command show html file in help window - Read data from the clipboard, e.g. copied from spreadsheets. - Browse and Update extended (e.g. show labels and copy to clipboard) - List display labels (list will be changed to a table format in v2.1) Extended commands: - Recode: value labels automatic - BAR and Histogram: Y axis can be scaled as percent: Option /PCT - Weight variables can be non-integer - Merge accepts comparing upper string with string key Design: - Menu and toolbar design simplified and unified (for translation) - Translation: All dialogs translated (ready for translators) - More options for display font size Waiting for final decision before release as v2.1: - KMPLOT: Kaplan-Meier plots (expected, but not fully decided) I am aware that it can be annoying to keep getting information on new builds, since we are releasing for test about once a week. But there is no other way of informing and asking for assistance in the "bug removal" process. - apart from the internal test routines, which now test more than 1890 aspects routinely. As usual the test version is available from http://www.epidata.dk/testing.php regards Jens Lauritsen EpiData Association

1 1

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

10 Aug '08

I will be out of the office starting 08/04/2008 and will not return until 08/11/2008. If you require immediate assistance, please contact Celina Sousa at extension 5300. Thank-you, Alyshia

1 0

New test build 138 for EpiData Analysis
by epidata-list＠lists.umanitoba.ca 02 Aug '08

02 Aug '08

As I mentioned a few days back just now work is being made on finalisation of v2.1 analysis for release. In build 138 these changes have been implemented. I am aware that some aspects are not fully implemented, see the list below: * Extended or adapted function o READ /CB: Read "csv" files placed on clipboard o Import data from clipboard (if placed as delimited files) o Browse and Updata completely rewritten + Copy all or part of data to clipboard + Sort while looking at data pointing to a variable + Variable information available on right click o List displays labels by default. Add /vl /v to modify o Recode: value labels extended for all recoding o Translation: All dialogs translated (ready for translators) * Documentation o Command reference updated (F1) * Bugs o Various bugs removed o Known bugs or problems + percent signs cannot be used in lines with a comment * + Some examples of reading csv files with problems exist + Small data size problems can occour exist with 2x2 estimation and percentiles + Pareto plot - in menu dialog - cannot take weight variable As usual the test version is available from http://www.epidata.dk/testing.php regards Jens Lauritsen

1 0

Coming release of EpiData Analysis v2.1
by epidata-list＠lists.umanitoba.ca 31 Jul '08

31 Jul '08

As part of the intensified developments of software I announced earlier we are now working on the following: 1. Analysis v2.1, which will include complete translation rewritten update and browse import data from clipboard export data from browser to clipboard other aspects which have been in the test versions Expected timeframe: 1-4 weeks for release of final test version 2. EpiData Entry Rewriting some of the logic for creation and change of data (easier logic for beginners) Prototype for GCP principles (logging) Expected timeframe: 3-5 months for first prototype Testversions will be place on the testing page as usual. Http://www.epidata.dk/testing.php With short notices on the front page of epidata.dk and/or a message to the EpiData-list. A newsletter to all registered users for this will be mailed when final versions are ready for download from the main download page. Regards Jens Lauritsen Coordinator and initiator of EpiData Project http://www.epidata.dk

1 0

Append data from laboratory
by epidata-list＠lists.umanitoba.ca 28 Jul '08

28 Jul '08

Dear Ziad, My sugestion is first make two different rec files... one wiht the data you are entering and a second one from one or more laboratory results. Usually is easier to keep different files from different sources. Lets say... one from clinical evaluations, one from CD4+ T cells and Viral Loads, one from the hamatology laboratories, one froam immunology laboratories and etc, because thy come from different sources. The most important thing here is to keep in all files with a unique identfier, or a combination of fields that uniquely connect each lab result and its owner (the patient). Usually this connection is done later... right before the data cleaning, before the analysis. But if you see a necessity to bind tha data for a beter controls of what is going on with your patinets (and your data) then... Make a qes file with all the fields whith the data is the xls spreadsheet. If the spreadsheet has wierd column names... first backup the file, later change the column names to the name which you want in the rec file. Make shure that the two recfiles have the very same variable names (the one with CD4 and VL and the one wiht the CD4 and VL and all clinical data). Example: xls "unique number" name CD4+ "Viral laod" "Collection date" 1 Ziad 560 <80 last sunday ........ to xls v1 v2 v5 v6 v7 1 Ziad 560 <80 last sunday ........ CD4VL.qes ***************** My lab results ***************** v1 Unique aidentifier ###### v2 Name <A > v5 CD4 cell count #### v6 Viral load ######### v7 Collection date <dd/mm/yyyy> Also important that these variables must have the vary same name in the destination recfile with the clinical and lab results data... AIDS.qes ***************** My patients data ***************** v1 Unique aidentifier ###### v2 Name <A > v3 Date of HIV diagnosis <dd/mm/yyyy> v4 Date of TB diagnosis <dd/mm/yyyy> v5 CD4 cell count #### v6 Viral load ######### v7 Collection date <dd/mm/yyyy> ..... Now that you got this, you must save your spread as a TXT separeted by TAB or by commas (I like TAB better :)) Now, from in EpiData import this spread sheet using the CD4LV.qes as structure. Chek you data, if it is OK then go on... Now you r going to combine you dataset side by side using the unique identfier. This option in Epidata is very ituitive. IMPORTANT IS TO BACKUP ALL THE FILES BEFORE YOU START. Sometimes the variable format are tricky from xls and you might have to make it several times before you got it right! A tip is allways use Stata to import data into EpiData, because in this situation Epidata keeps all the file structure and all the labels. From stata you dont have to make a qes file before. But this doen not seem to be you case because your data is allready on xls. Another easier way to do it is to use a software that transport and tranform almost every datase format such as StatTransfer. In this situation from .xls to .rec in a plink of you eyes. And then conbine in EpiData entry or your analysis software! May the force be with you! -- Abraço forte e que a força esteja com você, Pedro Emmanuel

1 0

Adding data from excel file
by epidata-list＠lists.umanitoba.ca 28 Jul '08

28 Jul '08

Hi! I entering my interviews into EpiData and have biomarker data (variables:VL and CD4) sent to me from the lab in Excel format, can I add them into EpiData dataset automatically instead of doing it manually? Thank you and best regards ziad

1 1

error message "one or more records are corrupted"
by epidata-list＠lists.umanitoba.ca 21 Jul '08

21 Jul '08

Dear list members, Below you'll find a message posted on this list November 2003 and referring to the error message "one or more records are corrupted". I have had this error in EpiData 3.1 after my computer crashed in a power cut. The remedy was similar or the same as described below: I had to open the "x.rec" file in a simple text editor program and delete all the non-data crap at the end of the file. Then it was possible to open it again in EpiData. best regards, raffael A type of error like this is very difficult to find since it can be due to many factors. e.g. network failure, network cache failure, disk occupied failures etc. But to minimise this type of error the principle of saving files was changed with version 2.1 to eliminate that error. And from v2.1b that type of error has only until now been reported from two instances in Kenya and China from situations where the computer lost power while entering data. The cause of the error was in both cases that the operating system (not epidata) were handling open files at power breakdown in a way where end of file markers were faulty. Even if the error still occurs only in rare cases we will consider a tool to "repair corrupt files" as part of the tool. The idea being to 1. read the file structure. 2. read the records from the start of the file and write them to a new file. 3. If a record was not of correct length, then tell the user how many records were retrieved. regards Jens Lauritsen >>> <epidata-list at lists.umanitoba.ca> 24-11-03 16:08 >>> Hi - Periodically (perhaps every few months) I am not able to open a .rec file, and get the message that "one or more files are corrupted". Our IT person will find that the end of the file marker has to be reset, and once that is done, we're able to use the file again. We're now using EpiData2.1b, although this has been happening for probably about a year, with previous versions. I'm wondering if there is anything we can do to prevent this "file corruption" from happening. I'm wondering if this problem could be related to my editing records in EpiInfo that have been originally entered in EpiData. thanks, Elise Elise Lennon, RN, MPH Research Analyst Massachusetts Rural Domestic Violence and Child Victimization Project Massachusetts Department of Public Health Western Regional Office 23 Service Center Northampton, MA 01060

1 0

Re: EpiData-list Digest, Vol 57, Issue 14
by epidata-list＠lists.umanitoba.ca 18 Jul '08

18 Jul '08

Dear Pedro, Thank you for your kind and the great insights! I guess I am thinking of visit number as control variable to know number of visits per patient which of course I could do it later on. So I guess it was just matter of "can't wait until time of analysis to know the answer per patient". I better hold down my horses until analysis time then! :-) Best regards ziad On Fri, Jul 18, 2008 at 10:04 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. Visit number (epidata-list(a)lists.umanitoba.ca) > > > ---------- Forwarded message ---------- > From: epidata-list(a)lists.umanitoba.ca > To: epidata-list(a)lists.umanitoba.ca > Date: Fri, 18 Jul 2008 09:47:07 -0300 > Subject: [EpiData-list] Visit number > Dear Ziad, > > Of course a visit number is interresting... if you want visualize your data > and order it by visit number. Having a visit number at your paper forms is > also interresting for the very same reason. > > However, most analysis softwares such as R and Stata do not bother with the > visit number while running survival analysis - which I guess you will do > later. :) For survival analysis the most important data is the date of the > evaluation, somehting indicatig what happened at the period, and a date > indicating the beggining of the period. Most softwares have available > analysis whith time dpending variables - which has a dataset wiht a > structure containing the same patient at several lines - each line a > different period. Of course to do that, there must a unique idenfier for > each patient which will be repeated all the lines where the same patient > appear. > > Again, visit number is important but not that importatn. As a previous > answered, if you already started your job and you have a lot of data in your > dataset it will be easier to insert a variable indicating visit number. > Otherwise, you could update you qes file with a nwe variable indicating > visit number. > > Best regards, > Pedro Emmanuel > > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > -- Ziad El-Khatib AIDS Unit National Institute for Communicable Diseases (NICD) 1 Modderfontein Road Private Bag X4, Sandringham, 2131 Johannesburg, South Africa Mobile: +27 (0) 72-52 39 716 Phone: +27 (0) 11-386 6433 Fax (NICD): +27 (0) 11 386 6453 Fax (connected to my email): +27 (0) 86 18 2871 http://www.nhls.ac.za/div_nicd.html Division of International Health (IHCAR) Department of Public Health Sciences Karolinska Institute Nobels väg 9 SE-171 77 Stockholm, Sweden Landline (connected to Skype):+46 (0) 8-559 21 659 Fax: +46 (0) 8-311590 http://ki.se/ki/jsp/polopoly.jsp?d=18835&l=en

1 0

Visit number
by epidata-list＠lists.umanitoba.ca 18 Jul '08

18 Jul '08

Dear Ziad, Of course a visit number is interresting... if you want visualize your data and order it by visit number. Having a visit number at your paper forms is also interresting for the very same reason. However, most analysis softwares such as R and Stata do not bother with the visit number while running survival analysis - which I guess you will do later. :) For survival analysis the most important data is the date of the evaluation, somehting indicatig what happened at the period, and a date indicating the beggining of the period. Most softwares have available analysis whith time dpending variables - which has a dataset wiht a structure containing the same patient at several lines - each line a different period. Of course to do that, there must a unique idenfier for each patient which will be repeated all the lines where the same patient appear. Again, visit number is important but not that importatn. As a previous answered, if you already started your job and you have a lot of data in your dataset it will be easier to insert a variable indicating visit number. Otherwise, you could update you qes file with a nwe variable indicating visit number. Best regards, Pedro Emmanuel

1 0

First and last observations in a file
by epidata-list＠lists.umanitoba.ca 16 Jul '08

16 Jul '08

I have a data file with multiple observations for each person and each of the multiple observations is on a separate record. A person may have one, two, three, or more observations. I need to create a file with the first and last observation on the same record for each person. Each record has a person's id variable, date, and observation number. If I could first identify the first and last observations and then write them out to separate files, then it would be possible to rename the variables except for the id variable and merge the files using the id variable. I searched the archive for something similar with no success. Thanks, John

1 1

Continuous number at every new ID number
by epidata-list＠lists.umanitoba.ca 14 Jul '08

14 Jul '08

Dear EpiData lister, I am entering longitudinal data into EpiData, is it possible to have a variable 'visit' that will have new number every time I enter new record for the same patient? Then it will start from beginning with number when i am entering new patient? example below id visit -- ----- 1001 1 1001 2 1001 3 1001 4 1001 5 1002 1 1002 2 1002 3 1003 1 1003 2 1004 1 1004 2 1004 3 etc.. Thank you in advance and best regards ziad

1 1

RE: EpiData-list Digest, Vol 57, Issue 8
by epidata-list＠lists.umanitoba.ca 14 Jul '08

14 Jul '08

In the check file BEFORE ENTRY IGNOREMISSING V3=V1+V2 END This should work. Sandy MRC (SA) -----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: 11 July 2008 19:07 To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 57, Issue 8 Send EpiData-list mailing list submissions to epidata-list(a)lists.umanitoba.ca To subscribe or unsubscribe via the World Wide Web, visit http://lists.umanitoba.ca/mailman/listinfo/epidata-list or, via email, send a message with subject or body 'help' to epidata-list-request(a)lists.umanitoba.ca You can reach the person managing the list at epidata-list-owner(a)lists.umanitoba.ca When replying, please edit your Subject line so it is more specific than "Re: Contents of EpiData-list digest..." EpiData-list mailing list ___________________________________ Today's Topics: 1. Adding values of 2 cells (epidata-list(a)lists.umanitoba.ca) 2. Adding/Revising Checks (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Thu, 10 Jul 2008 11:00:23 -0700 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Adding values of 2 cells To: epidata-list(a)lists.umanitoba.ca Message-ID: <897a5cf60807101100q72d4f35drd460ec55f4f56b65(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Hi! How can I create v3=value of v1 and value of v2? example: ID v1 v2 v3 --- --- --- --- 1 BW 101 BW101 2 CW 102 CW102 etc.. ' any tips? Thank you in advance and best regards ziad ------------------------------ Message: 2 Date: Thu, 10 Jul 2008 16:03:26 -0500 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Adding/Revising Checks To: <epidata-list(a)lists.umanitoba.ca> Message-ID: <000001c8e2d0$65e4af60$6401a8c0@EA5E71A6DE4A4D9> Content-Type: text/plain; charset="us-ascii" I have created the qes, rec, and chk files using 3.1. When I use add/revise on the checks menu, make changes, and then save the file, many of the previously defined labels and commands are deleted. My manual states that a check file can be created by using add/revise or the editor. Can edits to the chk file only be made using the editor? Thanks much, John Hater Memphis, TN ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 57, Issue 8 *******************************************

1 0

Adding values of 2 cells
by epidata-list＠lists.umanitoba.ca 11 Jul '08

11 Jul '08

Hi! How can I create v3=value of v1 and value of v2? example: ID v1 v2 v3 --- --- --- --- 1 BW 101 BW101 2 CW 102 CW102 etc.. ' any tips? Thank you in advance and best regards ziad

1 1

Adding/Revising Checks
by epidata-list＠lists.umanitoba.ca 11 Jul '08

11 Jul '08

I have created the qes, rec, and chk files using 3.1. When I use add/revise on the checks menu, make changes, and then save the file, many of the previously defined labels and commands are deleted. My manual states that a check file can be created by using add/revise or the editor. Can edits to the chk file only be made using the editor? Thanks much, John Hater Memphis, TN

1 1

Re:Problem in creating data file (Field without closing-bracket)
by epidata-list＠lists.umanitoba.ca 10 Jul '08

10 Jul '08

Dear colleagues I am a new EpiData user, I am trying to create a data file for my QES file, but as I click "make data file" this message comes: The .QES file contains errors. The following errors were found: <...> field without closing-bracket in line 73: I wonder whether I can get help to solve this from any of you. George

1 1

Mac
by epidata-list＠lists.umanitoba.ca 06 Jul '08

06 Jul '08

Hi, I am using EpiData on Windows environment and might change into Mac, can EpiData work there or do I need to install different version? Thank you in advance and best regards ziad

1 0

Re: Loading a photo id during entry
by epidata-list＠lists.umanitoba.ca 04 Jul '08

04 Jul '08

A question was: "I am currently working on a Vaccine trial and I intend using epidata for the study. My problem now is that I have been struggling with how to create a field to load photo ID. I need a help on this." I suggest in addition to other help also to look at the "execute" command, which is a check file command that allows running external software during entry. From the help file of EpiData entry this example is found under "execute": PICTNUM DEFINE tmpName _________________ AFTER ENTRY LET tmpName="d:\pics\picture"+pictnum+".jpg" EXECUTE @tmpName WAIT END END The field PICTNUM is a integer field. If user enters the number 3 then a .jpg picture file called "d:\pics\picture3.jpg" will be opened by the default program for .jpg files. EpiData halts until pictureviewer (or –editor) is closed.@tmpName means that @tmpName should be replaced by the contents of the variable tmpName. Regards Jens Lauritsen EpiData Association

1 0

Need Help
by epidata-list＠lists.umanitoba.ca 04 Jul '08

04 Jul '08

Dear All, > I am currently working on a Vaccine trial and I intend using epidata for > the study. My problem now is that I have been struggling with how to > create a field to load photo ID. I need a help on this. > > Thank you and kind regards > Joe. Phone +233-244476218 Ghana

1 0

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

03 Jul '08

Dear Han and all, Thank you for your help and encourage! I follow what you told me, even I did it before, and it still not work. So I used the .QES save under a new name like test.qes and make a brand new data file name: test.rec. Then I entered some record, and I was able to use the FIND command for date format <mm/dd/yyyy>. I feel great and hopeful. After that, I entered data with the previous .chk file ... name test.chk And I found that I was unable to use it FIND command for date field with format <mm/dd/yyyy>, it always give me the Information box with message "Search string(s) not found"; And still the FIND command only works for format date as <dd/mm/yyyy>. May be something wrong with my check file? Thank you very much for your help and support! Kim Dang, CDI Santa Clara County - TB Clinic 976 Lenzen Ave, Basement San Jose, CA 95126 USA Phone: (408) 792 - 5586 Fax: (408) 947 - 8778 -----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: Wednesday, July 02, 2008 10:11 AM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 57, Issue 2 Send EpiData-list mailing list submissions to epidata-list(a)lists.umanitoba.ca To subscribe or unsubscribe via the World Wide Web, visit http://lists.umanitoba.ca/mailman/listinfo/epidata-list or, via email, send a message with subject or body 'help' to epidata-list-request(a)lists.umanitoba.ca You can reach the person managing the list at epidata-list-owner(a)lists.umanitoba.ca When replying, please edit your Subject line so it is more specific than "Re: Contents of EpiData-list digest..." EpiData-list mailing list ___________________________________ Today's Topics: 1. Re: Unable to use Command FIND (Ctrl F) in Enter Record to find field with date format as <mm/dd/yyyy> (epidata-list(a)lists.umanitoba.ca) 2. Alyshia Landry is out of the office. (epidata-list(a)lists.umanitoba.ca) 3. Formatting in EpiData (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Tue, 01 Jul 2008 19:25:41 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] Unable to use Command FIND (Ctrl F) in Enter Record to find field with date format as <mm/dd/yyyy> To: epidata-list(a)lists.umanitoba.ca Message-ID: <486A6895.1070408(a)tbrieder.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Dear Kim: It works, but you must take care to enter it properly. Assume it is May 30, 2000, thus you must search: 05/30/2000 and it works (I just tested it). Regards, Hans epidata-list(a)lists.umanitoba.ca wrote: > 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 > > ------------------------------ Message: 2 Date: Tue, 1 Jul 2008 15:45:21 -0400 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Alyshia Landry is out of the office. To: epidata-list(a)lists.umanitoba.ca Message-ID: <OF9BE4E8CC.A52A6D1A-ON85257479.006C85EC-85257479.006C85EC(a)region.waterl oo.on.ca> Content-Type: text/plain; charset=US-ASCII I will be out of the office starting 06/30/2008 and will not return until 07/02/2008. If you require immediate assistance, please contact Celina Sousa at extension 5300. Thank-you, Alyshia ------------------------------ Message: 3 Date: Wed, 2 Jul 2008 11:09:59 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Formatting in EpiData To: epidata-list(a)lists.umanitoba.ca Message-ID: <9906aaf80807020209o783dd268y306c1eac8c66aa6b(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Dear all: How much does EpiData allow formatting of text in questionnaires? For instance putting titles in the Questionnaire form in bold, italic or underlined mode? Or putting a block of the questionnaire in a different background colour? Thank you for your help and guidance m -- *********************************************** Marco ZEIMET eMail: marco.zeimet(a)gmail.com Internet: http://www.ehealthsys.info Internet: http://www.health-informatics.lu *********************************************** ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 57, Issue 2 *******************************************

1 1

Formatting in EpiData
by epidata-list＠lists.umanitoba.ca 02 Jul '08

02 Jul '08

Dear all: How much does EpiData allow formatting of text in questionnaires? For instance putting titles in the Questionnaire form in bold, italic or underlined mode? Or putting a block of the questionnaire in a different background colour? Thank you for your help and guidance m -- *********************************************** Marco ZEIMET eMail: marco.zeimet(a)gmail.com Internet: http://www.ehealthsys.info Internet: http://www.health-informatics.lu ***********************************************

1 1

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

01 Jul '08

I will be out of the office starting 06/30/2008 and will not return until 07/02/2008. If you require immediate assistance, please contact Celina Sousa at extension 5300. Thank-you, Alyshia

1 0

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

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

29 May '08

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

1 0

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

28 May '08

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

1 0