- EpiData-list - University of Manitoba Mailing Lists

EpiData Analysis interactive selection
by epidata-list＠lists.umanitoba.ca 04 Dec '08

04 Dec '08

I have a field UNITNUM with values for treatment. I write in an EpiData Analysis program: .... define u #### global set echo=on freq unitnum /vl set echo=off u=?Enter unit to analyze? select if unitnum=@u .... to prompt interactively which of the many units I wish to select for subsequent analysis. Any suggestion, how to modify the program to be able to either make the selection for a specific unit (as now) or alternatively not to make a selection to analyze the full set? Thanks for any suggestion, Hans -- Hans L Rieder, MD, MPH Jetzikofenstrasse 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 321 9122 Web: http://wwww.tbrieder.org

1 0

Re: Dealing with 'Ongoing' duration in epicurves
by epidata-list＠lists.umanitoba.ca 02 Dec '08

02 Dec '08

"I would appreciate it if those working with outbreaks could reply about how they enter and display "ongoing" duration of illness." We create a graph showing at what time (date) the symptoms start and graph this according to exposure or time window. For epicurve the standard way of thinking is: ..............dayonset (start) ................................. ...... dayonset (start) ..................................... command could be: epicurve case dayonset In a different instance we would like to analyse "pattern of disease development" or pattern of how long time disease lasts begin ----------------------- end begin ----------------------------------------- (still under observation) The typical analysis here could be a Survival curve indicating length of disease period: Assume we have cases and string variables for start and end in the analysis. We would : read ourdata (or read from clipboard since these are copied from a spreadsheet). * generate two date variables for start and end of period: gen d stop = . if end <> "ongoing" then stop = date(end, "%dmy") gen d start = date(begin, "%dmy") * generate a case variable indicating if people were cured or are still under observation: gen i well = 0 if end <> "ongoing" then well = 1 * now we are ready for the analysis. notice the /mt which will assume that everyone with end time missing were observed until the latest of those where "stop" was "non-missing". lifetable well start stop /mt * an alternative would be to give the stop as a precise value: e.g. Dec 1st 2008 if end = "ongoing" then stop = dmy(1,12,2008) lifetable well start stop Notice that we did not change the "well" to 1 since keeping this with the value 0 indicates this observation was observed until given stop date, but did not develop disease. The lifetable would show median survival, possibly grouped or compared to a reference with the options "/by=sex /p25 ....." Regards Jens Lauritsen EpiData Association

1 0

Dealing with 'Ongoing' duration in epicurves
by epidata-list＠lists.umanitoba.ca 02 Dec '08

02 Dec '08

I would appreciate it if those working with outbreaks could reply about how they enter and display "ongoing" duration of illness. I have been given an Excel sheet to analyse in Epidata. For this outbreak people were asked the date and time when they became unwell and the date and time when they felt better. There is a calculated field in the spreadsheet that calculates duration in days (date better - date unwell), but for some people this is empty because "ongoing" has been entered as text in the "date better" field. I want to modify the Excel sheet so I include those people with 'ongoing' illness in an epidemic curve. I thought I could enter a date sometime in the future instead of 'ongoing' This would mean the duration days would not be blank, but a number of days well beyond the maximum value for those whose illness is finished. What do others do? 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 2

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

02 Dec '08

Hello!Can you attached the file for me to figure out the problem for you. Regards Mensah On Mon, Dec 1, 2008 at 6:04 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. Export to SPSS requires 2 stage procedure > (epidata-list(a)lists.umanitoba.ca) > 2. Dealing with 'Ongoing' duration in epicurves > (epidata-list(a)lists.umanitoba.ca) > > > ---------- Forwarded message ---------- > From: epidata-list(a)lists.umanitoba.ca > To: epidata-list(a)lists.umanitoba.ca > Date: Sun, 30 Nov 2008 21:46:21 +0200 > Subject: [EpiData-list] Export to SPSS requires 2 stage procedure > Hello users and developers, > > I am using Epidata Entry 3.1 27 Jan 2008 on Windows XP Pro SP3. I have date > entered in .REC files. When I perform the export function using the drop > down menus, it does so fine, but the .SPS and .TXT files created are all > blank. If I try re-exporting (with Epidata Entry still open), and error > message pops up: "...data still in use..." or something like that. A > successful data export to SPSS is only possible if I complete quite Epidata > Entry and and start a new instance to perform the export procedure once > again. > > Could somone please verify this for me, and if so please explain what is > going on. It is quite frustrating that to have to do export in 2 stages. > > Thanks, > Shuaib > > > > ---------- Forwarded message ---------- > From: epidata-list(a)lists.umanitoba.ca > To: <epidata-list(a)lists.umanitoba.ca> > Date: Mon, 01 Dec 2008 11:18:23 +1300 > Subject: [EpiData-list] Dealing with 'Ongoing' duration in epicurves > I would appreciate it if those working with outbreaks could reply about how > they enter and display "ongoing" duration of illness. I have been given an > Excel sheet to analyse in Epidata. For this outbreak people were asked the > date and time when they became unwell and the date and time when they felt > better. There is a calculated field in the spreadsheet that calculates > duration in days (date better - date unwell), but for some people this is > empty because "ongoing" has been entered as text in the "date better" field. > I want to modify the Excel sheet so I include those people with 'ongoing' > illness in an epidemic curve. > > I thought I could enter a date sometime in the future instead of 'ongoing' > This would mean the duration days would not be blank, but a number of days > well beyond the maximum value for those whose illness is finished. What do > others do? > > 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 ** > > > > ________________________________________ > 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 0

Export to SPSS requires 2 stage procedure
by epidata-list＠lists.umanitoba.ca 30 Nov '08

30 Nov '08

Hello users and developers, I am using Epidata Entry 3.1 27 Jan 2008 on Windows XP Pro SP3. I have date entered in .REC files. When I perform the export function using the drop down menus, it does so fine, but the .SPS and .TXT files created are all blank. If I try re-exporting (with Epidata Entry still open), and error message pops up: "...data still in use..." or something like that. A successful data export to SPSS is only possible if I complete quite Epidata Entry and and start a new instance to perform the export procedure once again. Could somone please verify this for me, and if so please explain what is going on. It is quite frustrating that to have to do export in 2 stages. Thanks, Shuaib

1 0

Re: Test of a new "set" principle
by epidata-list＠lists.umanitoba.ca 27 Nov '08

27 Nov '08

The very quick message from N. Verlander was the observation that: set option means = ? option means not supported . set option means = "/t" OPTION MEANS = "/t" set option tables = ? tables sex kmgrp option tables = /t /r tables sex kmgrp /t /r (but the user wrote the same as above) The message of the default options NOT defined is correct. But we could/should most likely change the message from: option table not supported to option table not defined Another issue was that the option /t2 was not defined for Ichart. This will add two tests: test 4: 2 out 3 successive points more than 2 standard deviations (sigma) away from the centerline. test 5: 4 out of 5 successive points more than one standard deviation (sigma) away from the centerline. and currently also lines at 1 and 2 sigma from the centerline, but only for Ichart. A detailed document on respecification of spc charts is now available on the testing page. -- Jens Lauritsen Coordinator and initiator of EpiData Project http://www.epidata.dk

1 0

Test of a new "set" principle and question on definition of SPC commands
by epidata-list＠lists.umanitoba.ca 27 Nov '08

27 Nov '08

At the test page http://www.epidata.dk/testing.php a new build (158) of EpiData Analysis has been placed for testing and commenting here on the list. The main new aspect is a change in user specifications for set commands as a consequence of the discussion on this list last week. For all commands each user can define his/her own options, e.g. if you desire row percentage and chi square tests always for tables add to your epidatastat.ini file: set option tables = "/t /r" If you have the custom instead to use the short form of tables you would write: set option tab = "/t /r" Two "command group" set commands are predefined: set OPTION GRAPH (all graphs excluding SPC graphs) set OPTION SPC (SPC charts including pareto chart and run chart) Another area for testing is the extended SPC definitions, with new graphs: ichart /mr, gchart, cchart,uchart and ichart /t2 A suggestion has been made to change SPC charts such that the "time" variable is only used when the user specifically wishes to do so. It is expected that after a certain build/release the syntax for SPC charts will be: Xbar-S measurement‭ ‬time Ichart measurement‭ [‬time‭/label]* Uchart count volume ‭[‬time/label‭]* Cchart count‭ [‬time‭/label]* Pchart count total‭ [‬time‭/label]* Gchart "time at‭ ‬incident‭"‬ (only one variable) Pareto categories‭ Where [time/label]* indicates that this variable is NOT mandatory. If given this will be used as a label (like /xlabel), when the variable is string and as a value for x when it is numerical. Comments to this change are welcomed. -- Jens Lauritsen Coordinator and initiator of EpiData Project http://www.epidata.dk

1 0

Documentation of lifetable updated
by epidata-list＠lists.umanitoba.ca 27 Nov '08

27 Nov '08

Branger pointed out that the documentation on lifetable command in latest analysis was faulty. An updated version of commands.htm has been uploaded and can be found at: http://www.epidata.dk/commands.htm#lifetabgrp The file will be added to install versions later. Estimation options: /time=x :Calculate Survival estimate at indicated time value (values) /p25 p50 p75 :Calculate Time span estimates at Quartiles and Median of Survival Proportions (0.75 0.5 0.25) /t : Log-rank test and Hazard Ratio (only relevant with /by) /ref=x : Indicates value of /by variable to use as reference for comparisons when the difference from reference is estimated for /time /p and /t options The option /G has been replaced with /NG to hide the graph., but was incorrect in the documentation. Hide/show: * /NG do notshow the Kaplan Meier plot * /NT : do not show summary documentation table * /NOLT: do not show lifetable * /E0 /E1 /E2 /E3 /E4 : show results with this number of decimals * /NOCI : Hide confidence intervals in tables and graph (e.g. if graphs overlap for groups) regards Jens Lauritsen EpiData Association

1 0

Epidata
by epidata-list＠lists.umanitoba.ca 26 Nov '08

26 Nov '08

Hello, I have a problem with relate for two related files (with merge command), and its OK with EPI INFO 6 (DOS) The key is fiche. I wrote these commands (I simplify) : read first.rec merge fiche /file=second.rec and is written : Non-unique key in: second.rec The two files .chk are : - first.rec FICHE KEY UNIQUE END ONEVAR IF ONEVAR=1 THEN RELATE FICHE SECOND.REC ENDIF END - second.rec FICHE KEY 1 END Thank you PS : In lifetable Help /haz and /G are notified but these commands are not effective Bernard BRANGER - Médecin coordinateur Réseau de Santé en Périnatalité "Sécurité Naissance - Naître ensemble" des Pays de la Loire 1, allée Baco - 44000 NANTES Tél 02 40 48 55 81 - Fax 02 40 12 40 72

1 1

Numeric Range for field (two ranges)
by epidata-list＠lists.umanitoba.ca 26 Nov '08

26 Nov '08

1. Numeric Range for field (epidata-list(a)lists.umanitoba.ca) > Hello, > In the .chk file, I want to define a range for a numeric field (v1 ###) as follows: 100-120, 200-250 > Easiest solution: v1 range 100 250 after entry if (v1 > 120) and (v1 < 200) then help "Range allowed: 100-120 or 200-250" goto v1 endif end end Regarding the other question yesterday on loss of date we need to know more. regards Jens Lauritsen EpiData Association

1 0