- EpiData-list - University of Manitoba Mailing Lists

Re: [EpiData-list] Graphing results of outcome analysis showing CIs
by epidata-list＠lists.umanitoba.ca 05 Oct '09

05 Oct '09

Thanks Jamie I tried this and it worked well. It was quite easy to copy the Attack rate table into Excel. I just highlighted the data in the htm file and pasted it into a black worksheet. Then I 1. used data/text to columns to separate out the confidence interval colum into two columns (low and high) 2. Used edit replace to take out the brackets 4. Change the order of the columns to LowCI HighCI RR 3. Selected the data to make a chart 4. Chose stock chart 5. I also chose the option to include the data table within the chart The graph does not look as good as CIplot but does look pretty good. many thanks Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 >>> <epidata-list(a)lists.umanitoba.ca> 6/10/2009 2:28 a.m. >>> Hi Christine, CIPLOT is showing proportions, not RR. I think you will have to create your own chart in another package. You can import the attack rate table into excel and with a bit of manipulation, get the columns in the right order for a "stock chart" - stock chart uses the order Close, High, Low, where Close will be RR, High will be UCL and Low will be LCL. However, you will have to do some formatting to do to get the chart looking as good as CIPLOT. Jamie Hockin Christine wrote > Does anyone have a tip for the best and easiest way to graph the results of the attack rate table for an outbreak analysis including confidence intervals? I have run the outbreak analysis and generated the attack rate table > (TAB CASE 1 OYSTERS PRAWNS CHICKEN etc OA/ex), This is great. BUT... > > Now I have been asked to show all the exposures with relative risks higher than 2 and CIs that don't include 1 (of which there are about 10) on a single graph. The graph must show relative risk, lower confidence interval and higher confidence interval for each exposure. I have looked at the CI graph in Epidata Analysis but > a) I only want the total and the CIPLOT graph shows Yes and No as well as total > b) I want to show more than one exposure on the same graph and I don't think I can do this with the CI. > -- 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

Graphing results of outcome analysis showing CIs
by epidata-list＠lists.umanitoba.ca 05 Oct '09

05 Oct '09

Hi Does anyone have a tip for the best and easiest way to graph the results of the attack rate table for an outbreak analysis including confidence intervals? I have run the outbreak analysis and generated the attack rate table (TAB CASE 1 OYSTERS PRAWNS CHICKEN etc OA/ex), This is great. BUT... Now I have been asked to show all the exposures with relative risks higher than 2 and CIs that don't include 1 (of which there are about 10) on a single graph. The graph must show relative risk, lower confidence interval and higher confidence interval for each exposure. I have looked at the CI graph in Epidata Analysis but a) I only want the total and the CIPLOT graph shows Yes and No as well as total b) I want to show more than one exposure on the same graph and I don't think I can do this with the CI. Any help much appreciated. 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

New data format for testing and comments - tests needed
by epidata-list＠lists.umanitoba.ca 02 Oct '09

02 Oct '09

An exiting phase of development is now ready for general comments and testing. In june/july of this year the first cross platform experiments were available published on the testing page http://www.epidata.dk/testing.php Crossplatform function must solve aspects such as: - many different local character sets - different standards for physical file formats - the user should not do anything special when sending or receiving files created on another operating system On top of this another issue is coming up soon - the development of a dedicated data entry module also allowing for GCP (Good Clinical Practice) rules of transaction logging. Therefore we have now experimented with development and specification of a file format which contains as well the data as the metadata needed for understanding the data. By doing so we are moving towards a new structure: a. Datafile containing datadefinition and data. (parts of current rec and chk file). Suggested extension: recxml b. Dataentry definition file containing control during entry (e.g. relate, range, mustenter etc). Suggested extension: chkxml - part b not developed yet The proposed new data format is described here: http://www.epidata.org/dokuwiki/doku.php/documentation:datafileformat_xml Just now users are encouraged to test the following: 1. Can the test application read your files ? 2. Can the test application write your files ? 3. In particular test - when possible - whether the data files can be read on another operating system. E.g. saved by a Linux or Mac and then read on a windows pc. Get the test application from: http://www.epidata.dk/testing.php And report to the epidata-list of failures and success. Data formats supported are: REC, RECXML, ODF, DBF, XLS A table of what can be imported and exported is shown here: http://www.epidata.org/dokuwiki/doku.php/documentation:importexport Operating systems supported are: Mac (OS X), Linux (32+64bit), Windows. Mac PowerPC expected soon. After a few weeks of comments on the format a new test application will be created. Which will collect some time estimates of reading and writing data with subsequent reporting to a central database. This method should allow for future user tests of core modules with documentation available on the central website. Regards Jens Lauritsen EpiData Association

1 0

V2.2.1 of EpiData Analysis uploaded
by epidata-list＠lists.umanitoba.ca 01 Oct '09

01 Oct '09

v2.2.1 (Build 171) of EpiData Analysis has been uploaded. The only changes are: Fixing mismatch of subfoot and estimates information on SPC charts. Extending information for RunCharts - telling the number of measurements and points omitted on median. regards Jens Lauritsen EpiData Association

1 0

Re: EpiData-list Digest, Vol 71, Issue 6
by epidata-list＠lists.umanitoba.ca 24 Sep '09

24 Sep '09

The best way is to create a new variable from the old var Then pursue with the analysis. Alternatively, you should work on the original file .rec then .che before moving on the analytical part. Best wishes Tieble 2009/9/24 <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. losing checks after inserting new variables and saving data > in Epidata Analysis (epidata-list(a)lists.umanitoba.ca) > 2. Re: losing checks after inserting new variables and saving > data in Epidata Analysis (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 24 Sep 2009 12:30:28 +0530 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] losing checks after inserting new variables > and saving data in Epidata Analysis > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <367f37ad0909240000u631a3637i4dec713b968ce095(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > I am losing all my checks in the rec file after I insert new variables > using > Epidata Analysis and saving the file using command savedata. Please advise > how to retail my file structure as well as checks after I insert some new > variables using Epidata Analysis. > > -- > Ajay Kumar Reddy > > > ------------------------------ > > Message: 2 > Date: Thu, 24 Sep 2009 07:34:09 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] losing checks after inserting new > variables and saving data in Epidata Analysis > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4ABB5931.2000905(a)sympatico.ca> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > I have not had that problem using the current release. You can check the > version of Analysis under the help menu. When you SAVEDATA, Analysis > does create the corresponding .chk along with any new label values you > created for the new variables. You should be saving to a different file > name. > > What you can do if you continue to have this problem is to manually copy > the .chk for the original file to a new .chk that matches the file > created with SAVEDATA. > > I am losing all my checks in the rec file after I insert new variables > using > > Epidata Analysis and saving the file using command savedata. Please > advise > > how to retail my file structure as well as checks after I insert some new > > variables using Epidata Analysis. > > > > > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 71, Issue 6 > ******************************************* >

1 0

losing checks after inserting new variables and saving data in Epidata Analysis
by epidata-list＠lists.umanitoba.ca 24 Sep '09

24 Sep '09

I am losing all my checks in the rec file after I insert new variables using Epidata Analysis and saving the file using command savedata. Please advise how to retail my file structure as well as checks after I insert some new variables using Epidata Analysis. -- Ajay Kumar Reddy

1 1

Automatic fill in
by epidata-list＠lists.umanitoba.ca 15 Sep '09

15 Sep '09

I was wondering if anybody have an easy description of how to autofill variables after an if statement Per Kjaer

1 1

RE: EpiData-list Digest, Vol 71, Issue 1
by epidata-list＠lists.umanitoba.ca 12 Sep '09

12 Sep '09

Hello, Two questions : - Is "P50 lifetable" validity in progress ? - In scatter graph, is a linear regression line planned ? Congratulations for all the progress with last versions; Bernard BRANGER, Nantes, France -- J’utilise la version gratuite de SPAMfighter pour utilisateurs privés. Jusqu’à présent SPAMfighter a bloqué 922 courriels spam. Nous avons en ce moment 6 millions d’utilisateurs de par le monde entier. Les utlisateurs payants n’ont pas ce message. Vous pouvez télécharger la version gratuite: http://www.spamfighter.com/lfr

1 0

New Core Module uploaded.
by epidata-list＠lists.umanitoba.ca 09 Sep '09

09 Sep '09

Dear EpiData users. I have posted a new version of the Core Module for testing on the EpiData website: http://epidata.dk/testing.php With the latest version it is now possible to import and export Open Office spreadsheets (Open Document Standard) although with limited support for exporting dates. Please see the wiki for information on what formats are supported: http://www.epidata.org/dokuwiki/doku.php/documentation:importexport Additionally it is also possible to export to Excel spreadsheet. Importing is yet no possible. With kind regards, Torsten Bonde Christiansen. Software Developer, Epidata.

1 2

possible strategy discussion meeting in Baltimore (sept. 12th.-18th)
by epidata-list＠lists.umanitoba.ca 02 Sep '09

02 Sep '09

Dear all During the current development phase some strategic decisions need to be taken. E.g. on data file format, data formats to support for import/export. How to handle support issues etc. What types of analysis should be supported and developed etc. I would like users to arrange locally such strategic meetings and let us know on the list of the viewpoints. If anyone in the Baltimore region in USA have interest in a strategic discussion meeting during the time from Sept. 13th. to Sept. 18th. let me know (off list). I could arrange such a meeting in late afternoons or early evening on campus at Johns Hopkins University, where I will attend a course on quality assurance . Another option is in New York on Sept. 11th. Regards Jens Lauritsen in case of interest email directly to: info at epidata.dk (disregard the return message I will contact you directly).

1 0

New EpiData Analysis b170 uploaded
by epidata-list＠lists.umanitoba.ca 23 Aug '09

23 Aug '09

Public Release Version *2.2.1* build 170 - Aug 23th 2009 * Extended o Histogram Now groups data into bins. o /CLOSE added to Generate command. o Added: /FONTSIZE and /SUBFOOT added to graph commands. * Bugs fixed o Removed Sigma3 from legend in runchart command. o Freq sorted incorrectly by default, and using /SA or /SD. o Variable name with "if" in, cause pre-processor to incorrectly insert "set option" text the wrong place. o Labelvalue command gave no error with incorrect construction. o Use of /W in tables command deleted wrong variable in some instances regards Jens Lauritsen EpiData Association

1 0

Emulating check boxes in Epidata Entry
by epidata-list＠lists.umanitoba.ca 21 Aug '09

21 Aug '09

I have been working on a data entry form that was previously in Access. It has a lot of check box fields in Access (boolean fields that are represented on the screen by a box that alternates between being checked (true) and empty (false) when clicked. There is a way to do this in Epidata, which can be useful when presenting a long list of symptoms/signs or exposures to be completed. The trick to doing this is to create Yes/No fields that cannot be entered using the tab or cursor keys. They can, however, be entered using the mouse. In this example, clicking in one of these fields will toggle the value of the field between "Y" and missing. Perhaps others will find this useful. Jamie Hockin 11 1 VLAB _label1 1 1 30 0 0 0 0 112 Emulate check boxes #id 1 3 30 4 3 12 5 112 id #age 1 5 30 5 5 0 2 112 age _sex 1 6 30 5 6 3 1 112 sex _label2 1 8 30 0 0 0 0 112 Check as many boxes as you want _a 1 10 30 3 10 5 1 112 a _b 6 10 30 9 10 5 1 112 b _c 12 10 30 15 10 5 1 112 c #xnotused 1 12 30 10 12 0 1 112 xnotused #action 1 14 30 8 14 0 1 112 action _label3 9 14 30 0 0 0 0 112 Anything to finish up 1 12M Y ! 2 11FY Y ! 3 10MYY ! * Emulate check boxes age range 0 99 end sex comment legal M Male F Female end * this is the last field before the check boxes * jump to the field beyond the check boxes goto action end * this is a checkbox field that can only be entered * by clicking the cursor * If Epidata gets to this field, it must be that the * user has clicked in the field. This means that the * value of the field is toggled between Y and missing. * Note that any other cycle of changes is possible * Y to N to Y, Y to N to blank to Y, etc * Just program the nested if ... then ... endif blocks * These blocks MUST be NESTED and not sequential. a before entry if a = "Y" then a = . else if a = . then a = "Y" endif endif goto action end end b before entry if b = "Y" then b = . else if b = . then b = "Y" endif endif goto action end end c before entry if c = "Y" then c = . else if c = . then c = "Y" endif endif goto action end end * This field is used to block going to field c * with the cursor. Cursor UP from field ACTION will * come here and immediately go back to field ACTION xnotused before entry goto action end end Emulate check boxes id <idnum> age ## sex <A> Check as many boxes as you want a <Y> b <Y> c <Y> xnotused # action # Anything to finish up

1 0

Out of the office
by epidata-list＠lists.umanitoba.ca 20 Aug '09

20 Aug '09

I will be out of the office starting 2009-08-19 and will not return until 2009-08-31. Though I will have access to email and will try to respond to correspondence, for urgent CFEP matters please contact Gisele Jolicoeur at 613-941-0709.

1 0

Trouble in export to SAS
by epidata-list＠lists.umanitoba.ca 20 Aug '09

20 Aug '09

Hello for my first post, In .recfile I had a numeric variable X like /_##_/ In SAS program I get .../... /INPUT X _1_/ etc... .../... that implies in the SAS table a variable like . (missing variable). On correcting with _/1-2/_, it works. Thanks for explanation. best regards, D

1 1

Status on EpiData developments (August 2009)
by epidata-list＠lists.umanitoba.ca 10 Aug '09

10 Aug '09

Dear all During the most recent year development has been focused on SPC methods in Analysis (SPC: Statistical Process Control graphs and analysis), but also directed towards the longer sustainability issue of converting all EpiData Software to Open-Source and a unified approach, including a new principle of translation (not put into practice yet). Such that regardless of variety (Entry, Analysis, EpiC) the same function will do the same. The other aspect is to run on several operating systems (linux, windows, Mac). A major break through in this respect was reached upon release of the first test version for Linux and Windows in May/June this year. In the near future (weeks/days) two aspects will become visible: a. Minor update of EpiData Analysis with key reported problems such as: Histograms (are essentially bar graphs until now), Parsing of varible names containing "if", Setting font size in graphs via dialogs b. Next step in the core project, where users can test the future "engine". The current and next release allows reading and writing of text files, including "intelligent" guessing of variable format. A new aspect is that decimal separator can be defined by the user. With a bit of luck also a Mac variant of the core module will appear in a few weeks (if no major problem shows up). The principle now is that known problems mainly are solved in the core project rather than a temporary solution in e.g. Analysis. The coming phases of development are expected to be: A - getting to the point where translation can be applied (the principle is visible - but not implemented fully at: epidata.info/asger3) - rewriting EpiC to use the core module - develop a batch testing principle for reading and writing files B - Inclusion of the new core in Analysis C - Development of a GCP/FDA part 11/EMEA (Good Clinical practice for US and EU officially approved data entry) compliant data-entry client. The GCP principles will follow guidelines as shown on the European Clinical Network research ECRIN - page and published by an international working group in which I was a member, see http://www.ecrin.org - publications and find: GCP-compliant data management in multinational clinical trials. ECRIN-2, Deliverable D10, Version 1, 15 September 2008. In between these aspects some further development of Analysis and other products (Entry and EpiC) will take place, but focus will be on getting it all together on the new core to ensure sustainable development. Actually the current year marks a decade since first relase of EpiData Software and the autumn might contain special activities to celebrate this. I should mention that the project as a whole could not have been completed without the efforts of donors, the user base, the critical input, the specific work of people involved (see www.epidata.dk/credit.htm) . In particular for the rewriting focused donations from a number of institutions mentioned on the www.epidata.dk/funding.htm page has been essential. Such that full time employed Torsten Christiansen has been extended beyond the first year to a full two year period. Without the skillful efforts of Torsten in the first year leading to funding for a second year the whole rewriting would not be possible. I could also add, that without the thorough programming efforts by Michael Bruus in Entry and EpiC in the first ten years the rewriting would also not be possible in a two year period. The coming year again seems to give the EpiData Society as a whole (users and developers) another fruitful season. Warm Regards to all Jens Lauritsen Coordinator and initiator of EpiData Project http://www.epidata.dk

1 0

Access violation
by epidata-list＠lists.umanitoba.ca 07 Aug '09

07 Aug '09

Hello, I created a data entry system for a project which includes five relational databases. When we open EpiData and choose "enter data" all of the screens open, but we get the following message: Access violation at address 00464077. Write of address 0000000C I will appreciate any help I can get on this issue. Thanks, Regina Harders

1 1

date field: check fails
by epidata-list＠lists.umanitoba.ca 07 Aug '09

07 Aug '09

Dear all, I'm just starting to use epidata entry so I have probably overlooked something. Any pointers are appreciated! I defined a date field as follows in the .qes file: DOB date of birth <dd/mm/yyyy> in the .rec file I added the following sanity check: DOB MUSTENTER AFTER ENTRY IF ((year(DOB) < 1900) OR (DOB > TODAY)) THEN HELP "This date is not allowed" TYPE=ERROR CLEAR DOB GOTO DOB ENDIF END END Most of the time the field behaves as I expect it to: dates in the future or far in the past are not allowed. However, the following typo gets accepted without triggering an error: 05/08/20001. Adding an extra trailing zero (05/08/200010) results in a prompt conversion to 05/08/3402, and the sanity check works again. Some experimentation seems to confirm that values between 20000 and 20099 are accepted as valid for year, bigger values trigger either my check or are converted to some weird value, again triggering the check. How can I prevent this from happening? thanks in advance, Peter version info: epidata v3.1 (270108), on windows XP.

1 4

Limit on number of .rec files that can be RELATEd
by epidata-list＠lists.umanitoba.ca 17 Jul '09

17 Jul '09

Dear EpiData users, It appears as if there is a limit of 30 .rec files that can be linked together in a relational structure for data entry using the RELATE command. Am I mistaken or is there any work around for this? I have 29 files linked to a single "master" file and I need to be able to relate 2 more files to this first file for data entry to work well. Thank you in advance, Emilie

1 1

Re: Negative integer
by epidata-list＠lists.umanitoba.ca 15 Jul '09

15 Jul '09

Thak you guys, setting the field to ## worked fine! Best regards, Abraço forte e que a força esteja com você, Pedro Brasil

1 0

negative integers in epidata entry
by epidata-list＠lists.umanitoba.ca 15 Jul '09

15 Jul '09

Dear EpiData friends, I have a qes like this days NUMBER OF DAYS WITHOUT MEDICINE IN THE PERIOD ## However the ones who filled the CRFs filled this with -1 if there was no information about this question. Now Im testin the entrys to start feeding the datasets and just realize that -1 is not a legal integer for field # I thought that converting this field from # to <A > would work and later in the analysis to encode this variable to integer. WOuld this work? any more elegant workaround? Best regards, Abraço forte e que a força esteja com você, Pedro Emmanuel

1 3

creating an identifiant from various variables + double data entry
by epidata-list＠lists.umanitoba.ca 10 Jul '09

10 Jul '09

Dear Jens, Thanks for your helpful comment on creating an identifiant from various variables and double data entry (see below). I just wanted to clarify a few things: 1) Does this mean that when using the 'Double Entry Verification' option (immediate comparison), this will not work if you have added any new variables into the .rec, or changed the order of the variables from the existing .rec? 2) If you use the other method of data verification (entering data into two seperate files and then validating duplicate files afterwards), is it possible to compare the old and new .rec files, even if a new variable has been added, or the order of the variables has been changed? Will using the 'validate duplicate files' option work if the new .rec file has the variables in a different order? Thanks so much for all your help, Nicki Bailey One aspect of this about unique identifiers is when users want to do double entry. The only double entry option in this situation is to enter the data twice and then compare afterwards, since the "immediate comparison" double entry mode is not available for combined field unique entries unless the records are entered in EXACTLY the same sequence as the first time. The problem for the user is, that the system is NOT giving correct warnings in the immediate double entry if the unique index is created in contrast to entered directly. > I would like the identifier to be automatically created in the .rec > file after entering 4 variables and as an aggregation of these 4 > variables. > For instance my identifier is > ID=region number+village number+household number+member in the > household number regards Jens Lauritsen EpiData Association

1 6

Is it possible to link the follow-up to the baseline using EpiData?
by epidata-list＠lists.umanitoba.ca 30 Jun '09

30 Jun '09

Dear all, I have a question about linking the follow-up round of a survey to the baseline which was data entered using EpiData. The follow-up is a new database that will be linked to the baseline during analysis. During data entry, I want to make sure that the IDs entered in the follow-up match those from the baseline in the household roster of the survey. No member that was in the household in the baseline should be missing, however new members can be added to the household. I have villageid, householdid, and personid, each of which is entered separately. I can then create a unique id which combines these to ID the unique individual. The baseline data was entered using double data entry where the data was compared dynamically (Menu Option: "Double Entry verification") and the follow-up will be done in the same manner. The survey is large and the data are entered on several different computers that are not networked. The only way I can think of to link the follow-up to the baseline in order to compare the IDs would be to do a mini double data entry after the first data entry of the household roster where I check only the IDs for the data and see what is in the follow-up that isn't in the baseline, but this seems like a poor solution. I would prefer to do something dynamic, which 1) doesn't allow the data entry clerk to move on to another household until they have entered all of the IDs from the baseline and 2) flashes a warning if there is an ID entered that does not match with the baseline. I don't think that EpiData has these capabilities. Please let me know if I am simply not educated enough in this software. Thank you for your help (and I apologize for this long posting). Emilie

1 3

Changed principles for passwords
by epidata-list＠lists.umanitoba.ca 29 Jun '09

29 Jun '09

Dear All Due to several requests the list will from now on send password reminders from time to time. You can go into the list specification and turn this on (after you receive the first reminder). It would be constructive for the development of the Core module if users could find some time to challenge the core-module-test application in Linux or Windows. See www.epidata.dk/testing.php Report success and/or failures to the list. regards Jens Lauritsen EpiData Association

1 6

Re: EpiData-list Digest, Vol 68, Issue 5
by epidata-list＠lists.umanitoba.ca 29 Jun '09

29 Jun '09

Jose, Well, I would say that You could use a softaware such as stattransfer which would solve this problem. If you dotnt have it, I would recomend any other statistical software is usually able to do so. I usually work with stata or R. With stata you may save he spreadsheet as csv or tb separeted and import within stata and save in stata format. With R is even more simple because thereis some packages that are able to import directly from xls and then save it in stata format or dbf format. Usually stata format is the most friendly for epidata entry. If you dont have any experience with R, perhaps you will find easier to use a grphical interface such as Rcmdr or pmg. To install the Rcmdr and use R with a graphical interface, after installing it type "install.packeges("Rcmdr")" and afer the install type "library("Rcmdr")" The rest should be more intuitive! Abraço forte e que a força esteja com você, Pedro Emmanuel

1 0

Excel 2007
by epidata-list＠lists.umanitoba.ca 28 Jun '09

28 Jun '09

Dear member in the group is there any way to export data from Excel 2007 that can be read with Epidata. I have found the excel 2007 does not export to dbf format. I will appreciate any help. 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 2

EpiData Core Module - update
by epidata-list＠lists.umanitoba.ca 17 Jun '09

17 Jun '09

1 0

GPS data format in EpiData?
by epidata-list＠lists.umanitoba.ca 02 Jun '09

02 Jun '09

hi Has anyone figured out how to enter GPS coordinates in Epidata in a form which preserves the structure so that they can be exported to another program for analysis? Thanks in advance for any help, Susie Foster

1 2

Re: EpiData-list Digest, Vol 67, Issue 6
by epidata-list＠lists.umanitoba.ca 20 May '09

20 May '09

Dear Juergen (and all), Thanks for your help. I want the MEMID to be automatically created after MEMBERNO has been entered. 4 variables will be entered, and the MEMID must be an agreggation of these 3 variables. So this is how the chk file command currently looks: MEMBERNO RANGE 0 99 MUSTENTER AFTER ENTRY LET MEMID=String(LOCALITY)+String(VILLAGECOD)+String(HHOLDCODE)+String(MEMBERNO) END END The MEMID must be 10 digits long, which means that the other variables must be a certain length, and therefore 'keep their zeros' at the beginning. For example: LOCALITY = 1 (must be 1 digit) VILLAGECOD = 023 (must be 3 digits) HHOLDCODE = 0014 (must be 4 digits) MEMBERNO = 12 (must be 2 digits) Juergen, I tried to include what you suggested within the brackets but in this case, the MEMID simply didn't appear. This is how it looked: MEMBERNO RANGE 0 99 MUSTENTER AFTER ENTRY LET MEMID=String(LOCALITY*1000000000)+String(VILLAGECOD*1000000)+String(HHOLDCODE*1000)+String(MEMBERNO) END END Any ideas why this didn't work? Your help is very much appreciated! Thanks again, Nicki At 18:01 18/05/2009, you 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. Consistency in number of digits (epidata-list(a)lists.umanitoba.ca) > 2. Re: Consistency in number of digits > (epidata-list(a)lists.umanitoba.ca) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Mon, 18 May 2009 14:28:12 +0100 >From: epidata-list(a)lists.umanitoba.ca >Subject: [EpiData-list] Consistency in number of digits >To: epidata-list(a)lists.umanitoba.ca >Message-ID: <6.2.5.6.0.20090518141625.03381728(a)ucl.ac.uk> >Content-Type: text/plain; charset="us-ascii"; format=flowed > >Dear All, > >I apologise if this question is simple but I really can't figure it out. > >In creating my chk file, I need to ensure that four of the variables >contain a certain number of digits. I know this is normally >controlled by number fields the .qes file. However, in this instance >I need zeros to be included at the beginning (eg. 0003) so that all >responses contain the same number of digits. This is because I will >be putting these 4 variables together to create a 10 digit identifier >later in the chk file. > >At the moment, whenever I enter 0003, the zeros are removed and I am >left with just 3. > >Does anyone know if there is a way to ensure the zeros remain, and to >ensure that each variable entered contains 4 digits? > >Many thanks in advance for your advice! > >Nicki > > >Nicki Bailey >Centre Administrator >Leonard Cheshire Disability and Inclusive Development Centre >Department of Epidemiology and Public Health >University College London >4 Taviton Street, London, WC1H 0BT, UK >Tel: +44 (0) 207 679 5589 >Fax: +44 (0) 207 388 2291 >www.lcdisability.org/idc > > > >------------------------------ > >Message: 2 >Date: Mon, 18 May 2009 16:05:12 +0200 >From: epidata-list(a)lists.umanitoba.ca >Subject: Re: [EpiData-list] Consistency in number of digits >To: epidata-list(a)lists.umanitoba.ca >Message-ID: <4A116B18.2010104(a)fifas.de> >Content-Type: text/plain; charset="iso-8859-1" > >Dear Nicki, > >how will your identifier look like? Why doesn`t it work like this? > >v1=2 >v2=105 >v3=27 >v4=7 > >ident= v1*1000000000 + v2*1000000 + v3*1000 + v4 = 2105027007 (with 3 >digits/variable) > >Regards >Juergen > > >epidata-list(a)lists.umanitoba.ca schrieb: > > Dear All, > > > > I apologise if this question is simple but I really can't figure it out. > > > > In creating my chk file, I need to ensure that four of the variables > > contain a certain number of digits. I know this is normally controlled > > by number fields the .qes file. However, in this instance I need zeros > > to be included at the beginning (eg. 0003) so that all responses > > contain the same number of digits. This is because I will be putting > > these 4 variables together to create a 10 digit identifier later in > > the chk file. > > > > At the moment, whenever I enter 0003, the zeros are removed and I am > > left with just 3. > > > > Does anyone know if there is a way to ensure the zeros remain, and to > > ensure that each variable entered contains 4 digits? > > > > Many thanks in advance for your advice! > > > > Nicki > > > > > > Nicki Bailey > > Centre Administrator > > Leonard Cheshire Disability and Inclusive Development Centre > > Department of Epidemiology and Public Health > > University College London > > 4 Taviton Street, London, WC1H 0BT, UK > > Tel: +44 (0) 207 679 5589 > > Fax: +44 (0) 207 388 2291 > > www.lcdisability.org/idc > > _______________________________________________ > > EpiData-list mailing list > > EpiData-list(a)lists.umanitoba.ca > > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > >-- >*********************************************************** >Freiburger Institut fuer angewandte Sozialwissenschaft e.V. >FIFAS >Erasmusstr. 16, D-79098 Freiburg >Telefon: (0761) 28 83 64 Fax: (0761) 29 27 493 >Web: www.fifas.de >E-Mail: info(a)fifas.de > >

1 3

Re: EpiData-list Digest, Vol 67, Issue 6
by epidata-list＠lists.umanitoba.ca 19 May '09

19 May '09

Dear Nicki, Just set the type of data to STRING,then "0" will not be ingored.You can connect several strings directly.so: v1=2 v2=105 v3=27 v4=7 V5=v1+v2+v3+v4=2105277 note that v1-v5 are all strings! of course u can input "0" in the fields and they are all identified as strings. also you can try function string(), which can convert interger to string. regards, Justin 2009-05-19 alasiri17 发件人： epidata-list-request 发送时间： 2009-05-19 01:01:30 收件人： epidata-list 抄送：主题： EpiData-list Digest, Vol 67, Issue 6 Send EpiData-list mailing list submissions to epidata-list(a)lists.umanitoba.ca To subscribe or unsubscribe via the World Wide Web, visit http://lists.umanitoba.ca/mailman/listinfo/epidata-list or, via email, send a message with subject or body 'help' to epidata-list-request(a)lists.umanitoba.ca You can reach the person managing the list at epidata-list-owner(a)lists.umanitoba.ca When replying, please edit your Subject line so it is more specific than "Re: Contents of EpiData-list digest..." EpiData-list mailing list ___________________________________ Today's Topics: 1. Consistency in number of digits (epidata-list(a)lists.umanitoba.ca) 2. Re: Consistency in number of digits (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Mon, 18 May 2009 14:28:12 +0100 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Consistency in number of digits To: epidata-list(a)lists.umanitoba.ca Message-ID: <6.2.5.6.0.20090518141625.03381728(a)ucl.ac.uk> Content-Type: text/plain; charset="us-ascii"; format=flowed Dear All, I apologise if this question is simple but I really can't figure it out. In creating my chk file, I need to ensure that four of the variables contain a certain number of digits. I know this is normally controlled by number fields the .qes file. However, in this instance I need zeros to be included at the beginning (eg. 0003) so that all responses contain the same number of digits. This is because I will be putting these 4 variables together to create a 10 digit identifier later in the chk file. At the moment, whenever I enter 0003, the zeros are removed and I am left with just 3. Does anyone know if there is a way to ensure the zeros remain, and to ensure that each variable entered contains 4 digits? Many thanks in advance for your advice! Nicki Nicki Bailey Centre Administrator Leonard Cheshire Disability and Inclusive Development Centre Department of Epidemiology and Public Health University College London 4 Taviton Street, London, WC1H 0BT, UK Tel: +44 (0) 207 679 5589 Fax: +44 (0) 207 388 2291 www.lcdisability.org/idc ------------------------------ Message: 2 Date: Mon, 18 May 2009 16:05:12 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] Consistency in number of digits To: epidata-list(a)lists.umanitoba.ca Message-ID: <4A116B18.2010104(a)fifas.de> Content-Type: text/plain; charset="iso-8859-1" Dear Nicki, how will your identifier look like? Why doesn`t it work like this? v1=2 v2=105 v3=27 v4=7 ident= v1*1000000000 + v2*1000000 + v3*1000 + v4 = 2105027007 (with 3 digits/variable) Regards Juergen epidata-list(a)lists.umanitoba.ca schrieb: > Dear All, > > I apologise if this question is simple but I really can't figure it out. > > In creating my chk file, I need to ensure that four of the variables > contain a certain number of digits. I know this is normally controlled > by number fields the .qes file. However, in this instance I need zeros > to be included at the beginning (eg. 0003) so that all responses > contain the same number of digits. This is because I will be putting > these 4 variables together to create a 10 digit identifier later in > the chk file. > > At the moment, whenever I enter 0003, the zeros are removed and I am > left with just 3. > > Does anyone know if there is a way to ensure the zeros remain, and to > ensure that each variable entered contains 4 digits? > > Many thanks in advance for your advice! > > Nicki > > > Nicki Bailey > Centre Administrator > Leonard Cheshire Disability and Inclusive Development Centre > Department of Epidemiology and Public Health > University College London > 4 Taviton Street, London, WC1H 0BT, UK > Tel: +44 (0) 207 679 5589 > Fax: +44 (0) 207 388 2291 > www.lcdisability.org/idc > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list -- *********************************************************** Freiburger Institut fuer angewandte Sozialwissenschaft e.V. FIFAS Erasmusstr. 16, D-79098 Freiburg Telefon: (0761) 28 83 64 Fax: (0761) 29 27 493 Web: www.fifas.de E-Mail: info(a)fifas.de -------------- next part -------------- A non-text attachment was scrubbed... Name: info.vcf Type: text/x-vcard Size: 213 bytes Desc: not available Url : http://lists.umanitoba.ca/pipermail/epidata-list/attachments/20090518/15e5b… ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 67, Issue 6 *******************************************

1 0

Consistency in number of digits
by epidata-list＠lists.umanitoba.ca 18 May '09

18 May '09

Dear All, I apologise if this question is simple but I really can't figure it out. In creating my chk file, I need to ensure that four of the variables contain a certain number of digits. I know this is normally controlled by number fields the .qes file. However, in this instance I need zeros to be included at the beginning (eg. 0003) so that all responses contain the same number of digits. This is because I will be putting these 4 variables together to create a 10 digit identifier later in the chk file. At the moment, whenever I enter 0003, the zeros are removed and I am left with just 3. Does anyone know if there is a way to ensure the zeros remain, and to ensure that each variable entered contains 4 digits? Many thanks in advance for your advice! Nicki Nicki Bailey Centre Administrator Leonard Cheshire Disability and Inclusive Development Centre Department of Epidemiology and Public Health University College London 4 Taviton Street, London, WC1H 0BT, UK Tel: +44 (0) 207 679 5589 Fax: +44 (0) 207 388 2291 www.lcdisability.org/idc

1 3

creating an identifiant from various variables
by epidata-list＠lists.umanitoba.ca 16 May '09

16 May '09

Dear all, I would have a question about the creation of an identifier for data entry. I would like the identifier to be automatically created in the .rec file after entering 4 variables and as an aggregation of these 4 variables. For instance my identifier is ID=region number+village number+household number+member in the household number Do you have any clue about how to do this? Thank you for your help. Jean-Francois

1 5

Backup Command working twice ...
by epidata-list＠lists.umanitoba.ca 16 May '09

16 May '09

Hello I use the command for copy the REC file, AFTER FILE BACKUP C: \ backup \ HPH END and it works very well. But I need to add other directories in this BACKUP simultaneously (F: \ backup \ HPH) and (C: \ backup \ HPH ) How can I run this command twice? In the same CHK. 1 .- I tried: AFTER FILE BACKUP C: \ backup \ HPH BACKUP F: \ backup \ HPH END It does not work (1 .-) 2 .- I tried AFTER FILE BACKUP C: \ backup \ HPH END AFTER FILE BACKUP F: \ backup \ HPH END It does not work (2 .-) How can I do? I appreciate your prompt response Greetings, I write from Chile South America Carlos Ortega Areyte Biostatistician -- Carlos A. Ortega Areyte Prof. de Matemática y Computación Magíster en Bioestadística

1 2

Réf. : EpiData-list Digest, Vol 67, Issue 3
by epidata-list＠lists.umanitoba.ca 16 May '09

16 May '09

Hi Jean-François This is what is needed: If you want the ID is generated automatically Considers that your variables are string type Q01 Région <A > Q02 Village <A > Q03 Household <A > Q04 Member <A > ID Identifiant <A > in the chikfile Paste: Q01 RANGE 1 10 LEGAL 2 3 4 5 END MUSTENTER END Q02 RANGE 1 30 LEGAL 2 3 4 5 6 7 8 9 10 END MUSTENTER END Q03 RANGE 1 10 LEGAL 2 3 5 6 END MUSTENTER END Q04 RANGE 1 7 LEGAL 2 3 4 5 6 7 END MUSTENTER AFTER ENTRY LET ID=Q01+Q02+Q03+Q04 END END ID NOENTER END Put the "Range" if you think putting Number, but it is not worth Thanks __________________________ JP DIBY-KONAN, MD, MPH Sous-Directeur de l'Information Sanitaire Ministère de la Santé & Hygiène Publique (+225) 05 994 326 / 02 724 162 (+225) 20 323 440 -------Message original------- De : epidata-list-request(a)lists.umanitoba.ca Date : 16/05/2009 02:02:36 A : epidata-list(a)lists.umanitoba.ca Sujet : EpiData-list Digest, Vol 67, Issue 3 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. creating an identifiant from various variables (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Fri, 15 May 2009 17:38:04 +0100 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] creating an identifiant from various variables To: epidata-list(a)lists.umanitoba.ca Message-ID: <6.2.5.6.0.20090515173330.035cdd18(a)ucl.ac.uk> Content-Type: text/plain; charset="us-ascii"; format=flowed Dear all, I would have a question about the creation of an identifier for data entry. I would like the identifier to be automatically created in the .rec file after entering 4 variables and as an aggregation of these 4 variables. For instance my identifier is ID=region number+village number+household number+member in the household number Do you have any clue about how to do this? Thank you for your help. Jean-Francois ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 67, Issue 3 *******************************************

1 0

clearing all "legal comments" in data-entry before starting
by epidata-list＠lists.umanitoba.ca 06 May '09

06 May '09

Even in using dataentry for many applications, I never had this problem before: the new database has a "base.rec" with basic informations about a unit and connected with "relate" a file with 25 lines, all similar (only the var names changes) describing actions through a code . The line consists of date, actions and a small comment-field. The actions are numeric and the label appears when typed with the "type" command. One unit can have more than one of this actions sheet; when a sheet is full the user starts a new one. Till here there is no problem. ---- action file ---- id ____ jenr aujourd'hui <Today-dmy> jcd01 <dd/mm/yyyy> jca01 ## jcm01 ________________ jcd02 <dd/mm/yyyy> jca02 ## jcm02 ________________ jcd03 <dd/mm/yyyy> jca03 ## jcm03 ________________ ------ The problem appears only - what happens daily - when the user has to add one or two "action-codes" for one unit, than has to change to another unit and add new actions for another unit and of course on an other actions-sheet. At that moment the action labels from the first sheet appears also on your screen and theses comments are usually wrong. So I want to add a "clear comment legal all" command in the before record block of the corresponding chk-file but that is not possible. Is there another method to get to the same result ? regards Casta

1 1

Re: EpiData-list Digest, Vol 66, Issue 5
by epidata-list＠lists.umanitoba.ca 30 Apr '09

30 Apr '09

Jamie, Thank you for the chk code... it works perfectly. Very nice indeed. Best regards, Abraço forte e que a força esteja com você, Pedro Emmanuel

1 3

Retreiving a string
by epidata-list＠lists.umanitoba.ca 15 Apr '09

15 Apr '09

Epidata friends, I just spend almost the whole day trying to fix some typing errors. Nothing more than usual before starting some analysis. However It came to my attention that having just one key field maybe a lot misleading. Lets say that there a key id field called number in qes. v1 number ######### if the one who is typing types the worng number lets say 231022009 instead of 221022009 later this error may cause a lot of confusion and lead to other errors. The point is that this particular sort of error is hard to find and locate because this is the one field by which we should locate the record (the link to the CRF). Looking for the record by other fields is very fustrating unless the record has some very unusual data, such as age 99. How many records I would have with age 99?? Most likeli very few. One field that very often hleps is the patient intials, although it has very few letters, very unlikeli there is more than 3 or 4 in every thousand records with the same initials. Therefore I ask to you guys if there is a way in the chk file to retrieve from the name the initials of the full name. v1 number ######### v2 name: <A > v3 initials: <A > The objetictive is: v2 name: JENS LAURISTEN v3 initials: JL v2 name: PEDRO EMMANUEL AMERICANO DO BRASIL v3 initials PEADB Telling the typer to type this is an option, but Is it possible stick this magic in the chk file? I looked in the string functions from Epidata documentation but didnt find anything that could make a way around! Best regards? Abraço forte e que a força esteja com você, Pedro Emmanuel

1 1

Re: Double entry verification numeric fields
by epidata-list＠lists.umanitoba.ca 13 Apr '09

13 Apr '09

Epidata Friends, Yves gave a good work around on the id fields with leading zeros. I was suffering from the very same problem and did not stop to think on a work around. I did try this here with a data of mine and I have a another sugestion. It came to my attention that if the fieldnum has a autoserach command and the typer goes to edit a record already in the dataset then the fieldnum is deleted by the second chk command below. Perhaps a HELP command is more nice. FIELDNUM BEFORE ENTRY fieldnum=integer(fieldchar) goto nextvariable END autosearch list fieldnum END NEXTVARIABLE BEFORE ENTRY IF (fieldnum <> integer(fieldchar)) THEN HELP "PERHAPS THERE ARE SOME NON INTEGER CHARACTERS. CONSIDER REVISING!" ENDIF END This will call the attention of the typer and will not delete the data in the field if the record is to be edited. Best regards. Abraço forte e que a força esteja com você, Pedro Emmanuel

1 0

double entry verification : problem when entering numerical fields
by epidata-list＠lists.umanitoba.ca 12 Apr '09

12 Apr '09

Dear Epidata Team, First we have to thank you very much for the quality of your software. We intend to use EpiData for a double entry verification. Unfortunately, we have found a problem when entering numerical fields. If the keyboarder types 001 in a 3 digit numerical field, Epidata stores 1 (whitch is quite normal). But during the verification step, if they enter 001 again ... there is a message to remind them that there is a difference. Of course, the difference is between the stored value 1 et the first typed digit 0. This is a problem for us. In the framework of Clinical Trials, the operators have to enter exactly what is written on the CRF. A solution could be to define the field as a text one. But of course this allows to enter letters instead of digits, and that is not enough secure. We also tried to associate a numerical range (000-999) to the text 3 characters field (in a .CHK file). With this kind of control, typing a11 is denied, but typing 1a1 is allowed... Do you have an other solution or idea to solve this problem? In your forum, you answered to somebody that this problem will be solved in the next version of EpiData. Have you already an idea of the availability date of this version? Thank you very much in advance, Valérie Conte -- --------------------------------------------------------------- Valérie CONTE Directrice technique adjointe du CREDIM Chef de projet développement CREDIM Centre de Recherche Et Développement en Informatique Médicale ISPED Institut de Santé Publique, d'Epidémiologie et de Développement Casier 11 Université Victor Segalen Bordeaux 2 146 rue Leo Saignat 33076 Bordeaux Cedex Tel : 05.57.57.47.60 Fax : 05.57.57.45.41 --------------------------------------------------------------- Mel : mailto:Valerie.Conte@isped.u-bordeaux2.fr Web : http://www.isped.u-bordeaux2.fr ---------------------------------------------------------------

1 4

Error in exporting to Stata
by epidata-list＠lists.umanitoba.ca 30 Mar '09

30 Mar '09

Epidata friends, Im using epidata entry and after almost a 1000 records Im trying to export the data to Stata to start some initial analysis. However, when exporting to Stata format a warning comes and no data are exported. The warning is... Invalid data in record #889, filed sintocol, Export concluded. I tryed to export ot other formats such as dbase an sas and spss... the problem only happans when exporting to stata format! I opened epidataentry and checked the register 889 and it did not seemed to have anything wrong wiht it. Later I tryed to delete this register and the error still coming! Any sugestions? -- Abraço forte e que a força esteja com você, Pedro Emmanuel

1 0

fixing the p50 problem
by epidata-list＠lists.umanitoba.ca 29 Mar '09

29 Mar '09

Bono Branger gave an example of an existing problem with Epidata Analysis. The problem relates to the median (P50) for life-tables. I am aware of the "non-fixing" of the problem. Obviously we will fix this problem, but you must also be aware of the nature of the project. We are NOT a company, we do not get any license fees from the users. We are fixing problems within certain timelimits and priorities. Just now - as I have informed on this list - the priority is to rewrite some core modules for long term sustainability. We will get to the p50 problem. Reproducible errors should be reported to the bug tracking system - for which you find the address on the website epidata.dk (Mantis system). Anyone not satisfied with the principles can at any time choose not to use the software and buy (expensive) commercial software. regards Jens Lauritsen EpiData Association

1 0

Lifetable - Error on P50 calculation
by epidata-list＠lists.umanitoba.ca 29 Mar '09

29 Mar '09

Hello, I am very disappointed about error for the calculation of p50 in lifetable. Probably, Ill stop the use of this command (I had very hoped in this program..). I join an example with 3 errors. I can address the file. Thank you. Bernard BRANGER, Nantes, France . lifetable arret durall /p50 /by=codemat /t /noci Life Table: ARRET by codemat Total N Cases n Expected Cases Time Minimum Maximum Sum time Hazard Ratio Time S=0.50 Time Diff. 1 19 16 11.56 1 29 249 Ref. 10.00 Ref. 2 10 6 5.97 1 29 127 1.07 11.00 1.00 3 10 5 6.81 1 28 147 0.02 15.00 5.00 4 10 6 3.04 1 14 77 842818.30 8.00 -2.00 5 22 14 16.74 1 29 344 0.09 14.00 4.00 6 18 13 13.09 4 27 284 0.91 26.00 16.00 8 14 13 7.27 1 29 160 87399.95 23.00 13.00 9 18 15 10.93 0 29 239 223.32 12.00 2.00 10 20 17 15.50 1 28 333 4.12 30.00 20.00 11 7 6 3.22 1 22 72 235936.51 11.00 1.00 12 21 11 14.84 1 29 312 0.02 18.00 8.00 13 20 15 13.92 1 28 303 3.09 13.00 3.00 14 28 15 20.54 3 29 437 0.02 23.00 13.00 15 20 8 16.57 0 29 344 0.00 27.00 17.00 Outcome: ARRET = 1 Log Rank test of equality of survivor function: Chi2(13)= 21.092 P= 0.0711 LR test of homogeneity among groups Chi2(13)= 17.547 p= 0.1755 Interval NAt risk Deaths Lost Survival 1 1-2 19 1 0 0.95 2-3 18 2 0 0.84 4-5 16 1 0 0.79 6-7 15 2 0 0.68 8-9 13 1 0 0.63 9-10 12 1 0 0.58 10-11 11 2 0 0.47 13-14 9 1 0 0.42 14-15 8 1 0 0.37 16-17 7 1 0 0.32 19-20 6 1 0 0.26 21-22 5 1 0 0.21 25-26 4 1 0 0.16 27-28 3 0 1 0.16 28-29 2 0 2 0.16 2 1-2 10 1 0 0.90 4-5 9 1 0 0.80 8-9 8 2 0 0.60 9-10 6 0 1 0.60 11-12 5 1 0 0.48 15-16 4 1 1 0.36 28-29 2 0 2 0.36 3 1-2 10 2 0 0.80 7-8 8 1 0 0.70 9-10 7 0 1 0.70 13-14 6 1 0 0.58 15-16 5 1 0 0.47 24-25 4 0 1 0.47 25-26 3 0 2 0.47 27-28 1 0 1 0.47 4 1-2 10 1 0 0.90 5-6 9 1 1 0.80 6-7 7 1 0 0.69 8-9 6 2 0 0.46 9-10 4 1 1 0.34 13-14 2 0 2 0.34 5 1-2 22 1 0 0.95 3-4 21 4 0 0.77 5-6 17 1 0 0.73 8-9 16 1 0 0.68 10-11 15 2 1 0.59 11-12 12 1 0 0.54 14-15 11 1 0 0.49 16-17 10 1 0 0.44 25-26 9 1 0 0.39 27-28 8 0 2 0.39 28-29 6 1 5 0.33 6 4-5 18 1 0 0.94 5-6 17 1 0 0.89 6-7 16 1 0 0.83 7-8 15 1 0 0.78 8-9 14 1 0 0.72 11-12 13 1 0 0.67 12-13 12 1 0 0.61 13-14 11 1 0 0.56 15-16 10 1 0 0.50 16-17 9 1 0 0.44 17-18 8 1 0 0.39 19-20 7 1 0 0.33 21-22 6 1 0 0.28 26-27 5 0 5 0.28 8 1-2 14 1 0 0.93 3-4 13 2 0 0.79 7-8 11 2 0 0.64 8-9 9 2 0 0.50 9-10 7 1 0 0.43 10-11 6 1 0 0.36 15-16 5 1 0 0.29 18-19 4 2 0 0.14 25-26 2 1 0 0.07 28-29 1 0 1 0.07 9 0-1 18 1 0 0.94 4-5 17 1 1 0.89 6-7 15 2 0 0.77 7-8 13 1 0 0.71 9-10 12 2 0 0.59 12-13 10 2 0 0.47 14-15 8 2 0 0.36 16-17 6 1 0 0.30 20-21 5 1 0 0.24 25-26 4 2 0 0.12 28-29 2 0 2 0.12 10 1-2 20 1 0 0.95 3-4 19 1 0 0.90 5-6 18 1 0 0.85 7-8 17 1 0 0.80 8-9 16 2 0 0.70 10-11 14 1 0 0.65 14-15 13 1 0 0.60 15-16 12 1 0 0.55 18-19 11 2 0 0.45 22-23 9 1 0 0.40 23-24 8 2 0 0.30 25-26 6 1 0 0.25 26-27 5 2 0 0.15 27-28 3 0 3 0.15 11 1-2 7 1 0 0.86 4-5 6 1 0 0.71 10-11 5 1 1 0.57 11-12 3 1 0 0.38 15-16 2 1 0 0.19 21-22 1 1 0 0.00 12 1-2 21 1 0 0.95 3-4 20 1 0 0.90 4-5 19 0 1 0.90 7-8 18 2 0 0.80 9-10 16 2 1 0.70 10-11 13 1 0 0.65 13-14 12 0 1 0.65 14-15 11 0 1 0.65 16-17 10 2 0 0.52 17-18 8 0 1 0.52 18-19 7 1 0 0.45 20-21 6 1 0 0.37 27-28 5 0 1 0.37 28-29 4 0 4 0.37 13 1-2 20 1 0 0.95 4-5 19 0 1 0.95 7-8 18 1 0 0.90 9-10 17 3 0 0.74 12-13 14 3 0 0.58 13-14 11 3 0 0.42 15-16 8 1 0 0.37 16-17 7 1 0 0.32 25-26 6 1 0 0.26 26-27 5 1 1 0.21 27-28 3 0 3 0.21 14 3-4 28 2 0 0.93 5-6 26 0 1 0.93 6-7 25 1 0 0.89 8-9 24 1 2 0.85 9-10 21 1 2 0.81 10-11 18 0 1 0.81 13-14 17 0 3 0.81 14-15 14 0 1 0.81 15-16 13 1 0 0.75 16-17 12 1 0 0.69 19-20 11 0 1 0.69 21-22 10 2 0 0.55 23-24 8 1 0 0.48 24-25 7 1 0 0.41 27-28 6 1 0 0.34 28-29 5 3 2 0.14 15 0-1 20 1 0 0.95 3-4 19 1 0 0.90 5-6 18 0 1 0.90 7-8 17 0 1 0.90 11-12 16 0 1 0.90 13-14 15 1 0 0.84 14-15 14 0 3 0.84 15-16 11 2 0 0.69 19-20 9 1 0 0.61 21-22 8 1 0 0.53 26-27 7 0 1 0.53 27-28 6 1 0 0.45 28-29 5 0 5 0.45 _____ Jutilise la version gratuite de SPAMfighter pour utilisateurs privés. Jusquà présent SPAMfighter a bloqué 568 courriels spam. Nous avons en ce moment 6 millions dutilisateurs de par le monde entier. Les utlisateurs payants nont pas ce message. Vous pouvez télécharger la version gratuite <http://www.spamfighter.com/lfr> _____ Jutilise la version gratuite de SPAMfighter pour utilisateurs privés. Jusquà présent SPAMfighter a bloqué 594 courriels spam. Nous avons en ce moment 6 millions dutilisateurs de par le monde entier. Les utlisateurs payants nont pas ce message. Vous pouvez télécharger la version gratuite <http://www.spamfighter.com/lfr>

1 0

testing of quick guide for SPC graphs
by epidata-list＠lists.umanitoba.ca 22 Mar '09

22 Mar '09

Dear All As part of telling of the most recent implementation of SPC Control graphs while attending a quality assurance conference/forum in Berlin (http://internationalforum.bmj.com/) last week I produced a "Statistical Process Control Graphs in 5 minutes" - a link is placed near the top on epidata.dk. Please comment whether you find the text appropritate. (e.g. whether it should be 10 rather than 5 minutes). See front page of EpiData or this direct link: http://www.epidata.dk/downloads/spc5min_epidata.pdf regards Jens Lauritsen EpiData Association

1 0

recoding numbers....
by epidata-list＠lists.umanitoba.ca 12 Mar '09

12 Mar '09

Hello all, Im facing a little problem which so far I could not find a work around. Any sugestions would be welcome. I have tow datasets which come from different sources... I intended to join them side-by-side with epidata entry to keep on going wiht the data update. I know that the second one would update some stuff in the firts one, at least for the majority of the observations. Both of the have a unique identifier which is a variable called num. However in the first set num is like this... 133.01.2007 244.01.2007 while in the second one num is like this... 2007.01.133 2007.01.244 For any software these would be different numbers but given that I know that 2007 is the yaer and 1 is january and 244 or 133 is the sequence within the month I know that the second dataset have num in the inverse order. Concatenating the datasets like this would be just as append because no observatiosn would match. I tought in recode the numbers but this would be same as digitizing all again. Nay sugestions? -- Abraço forte e que a força esteja com você, Pedro Emmanuel

1 1

v2.2 of EpiData Analysis - released
by epidata-list＠lists.umanitoba.ca 12 Mar '09

12 Mar '09

Version 2.2 has been released for public downloads today. You can get it from http://www.epidata.dk/downloads.php The file is provided as a setup exe file, but also as already installed, where all files are contained in a zip file. Since last public release in november 2008 quite many aspects have been improved or adapted. In particular the whole SPC (Statistical Process Control) graph system has been extended with more options and more efficient layout. Also a grid for creating SPC graphs from scratch has been implemented. - is available from the graph menu. Some set commands have changed, such that users can be forced to update any specified ini file that was created with the former version. An extension is the possibility for the user to create preference options for all commands, example: set option tables = "/t /r /c" would define that all tables done with the command "tables" will be added the options /t /r and /c Just today an error with stratified tables and small sample sizes was reported - the error is now fixed. The problem was that some strata would be combined incorrectly. Analysis done previously should be repeated with the new version and proper control. Please report any remaining problem. To see all changes go to the file: http://www.epidata.dk/analysisversioninfo.htm Commands are all as previously documented in the command reference, which will open when you press F1. Please notice that the release of this depends on donated funding, as documented on the page: http://www.epidata.dk/funding.htm Users should update to this version of analysis, since some of the bugs removed could affect results. The development continues with further online documentation and teaching materials as well as core module restructuring, such as announced on the list recently. regards Jens Lauritsen

1 1

SPSS v17 export problem
by epidata-list＠lists.umanitoba.ca 11 Mar '09

11 Mar '09

Hello. I have recently "upgraded" to SPSS v17. My exports from EpiData to SPSS format no longer work. The error messages I get in the SPSS syntax editor are: 14 DATA LIST Unrecognized text appears on the DATA LIST command where a variable name was expected. Text: TO 69 VARIABLE LABELS This command is not permitted before the beginning of file definition commands. 137 execute This command is not valid before a working file has been defined. Can someone suggest a resolution? Thank-you kindly. __________________________ Stephen Drew Health Data Analyst Region of Waterloo Public Health

1 1

naming of files (htm or html)
by epidata-list＠lists.umanitoba.ca 08 Mar '09

08 Mar '09

Dear all As part of the transition it was suggested to name all help files which has the type "html" to be released with extension html instead of htm - which is now used for EpiData Analysis. eg. commands.htm would be commands.html, start.htm would be start.html etc. If this poses problems to anyone let us know on the list. regards Jens Lauritsen EpiData Association

1 0

Autobackup-feature and current test of EpiData Analysis b160
by epidata-list＠lists.umanitoba.ca 23 Feb '09

23 Feb '09

The development is now at a crucial point in time getting to a certain "gate". Before the gate is opened EpiData Analysis will be released as v2.2 and some updates to EpiData Entry will also take place, e.g. hopefully fixing the reported "auto backup" problem reported. After the gate there will be a common core system for reading, writing and interpreting files for as well EpiData Entry, EpiData Analysis and EpiC. This will not be seen immediately by the end user, but will assure that all functions are doing the same regardless of which part of EpiData Software and errors only needs one place for bug fixes. The translation process will also be adapted and released in common for the three software parts, since after that all functions and commands in relation to reading and writing data files and chk files will have the same number code. The list and translators will be informed when possible on all of this later this quarter or beginning of next quarter. Meanwhile EpiData Analysis b161 has been placed for testing for download from the testing.php page of the main site. (by a mistake the first were called b160, but actually were b161) - if you report problems report the date of the build if this was b160). One new aspect is that one commented by J. Hockin in the Mantis issue number 335. (A template for SPC graphs in a menu like system): The technical principle is the following: A: An htm file is created by the user outside of analysis with a combination of EpiData Analysis commands and ordinary html coding. (here called spc.htm) B: This file is activated in the help window via an entry in the graph-spc toolbar menu/dialog. (the same as the command: helpview "spc.htm") C: When the user clicks on a given link in the file, certain commands are issued and information can be given in the output window - without closing the helpview file. J.Hockin argues in the Mantis issue that the strange window is difficult to close again and that it would be preferred to have the spc.htm file opened in the main results window. I experimented a bit with both solutions and it turns (to me) an easier approach to use the help window. This is the same approach used if one uses the menu "Windows->screen font". Users can develop other htm files for such menu systems and load them either into help window (helpview spc.htm) or result window (view spc.htm) and if you wish an easy return to such a file issue the "set START PAGE " command after which you can open your menu file with F8 or have the system open it at start of the exe file. For inspiration on creation of such files, see the startfont.htm and the spc.htm files. Apart from testing that new menu/command button principle it is important for us to get tests of the Statistical Process Control Graphs and the new features introduced. I will contact a number of users directly, but all are more than welcome to participate. The optimal is if users would : a1: Create simple datasets using the built in system accessible via the toolbar-graph-spc menu/dialog in such a way that the following can be documented: - freeze (where estimates are based on the first n data points - breaks (where the time series are split in sub-parts) - exclude (where individual data points are excluded from estimates) and the tests (t1-t5), which will show different tendencies/aberrations. The optimal is to send such datasets in a zip file to "info at epidata.dk" consisting of the data and the pgm file to run the tests, including expected results. Disregard the mail notion of the mail not being received - we will let these through the spam filter and contact you directly. regards Jens Lauritsen EpiData Association

1 0

auto backup!!
by epidata-list＠lists.umanitoba.ca 20 Feb '09

20 Feb '09

Batch files are fine and easy to automaticly do stuff. Improving the last coment, I would sugest to put a Warning to press F10 before exit in after file block or in a before file block in the check file! Although this may not work 100%, it may help educate and remind the training!!! -- Abraço forte e que a força esteja com você, Pedro Emmanuel

1 0

serious backup problem in epidata entry
by epidata-list＠lists.umanitoba.ca 20 Feb '09

20 Feb '09

Hello Friends I create many datasets at my hospital and instruct physicians on how to use it. I always add a backup section to my chk files. The problem is that after the user clicks 'save record to disk' and wants to exit, he/she usually clicks the top 'x' on the upper right side of the screen, which is the way most software works. Unfortunately, the backup is not done unless the user clicks the lower 'x'. There is no warning, and backups are not made. Am I doing something wrong? If not, is there a workaround. Failure to make backups has caused me many problems . I am using ver 3.1(120306). I would really appreciate any help with this problem. Thank you all Steve Blum Bronx-Lebanon Hospital Center Department of Medicine Bronx, NY

1 1

New Analysis - release candidate as v2.2
by epidata-list＠lists.umanitoba.ca 15 Feb '09

15 Feb '09

Since previous release of EpiData Analysis quite a few changes have been implemented. Most of these fall in two groups: a. Bug fixes of minor (spelling, parsing certain data sets etc) and major importance. Of major importance are a few in relation to aggregating data (aggregate and Stattables) and some if statements. Also some parts of other graphs, e.g. epicurves which would show incorrectly as connected rectangular bars when outcomes were separated by long periods. b. Enhancements and further implementation of SPC (Statistical Process Control Graphs) New chart types have been added (xbar-s, uchart , cchart), and further possibilities of doing proper analysis, e.g. freeze mean and limits based on first part of data, further warning tests (t4 and t5) and the setup of variables has been simplified. Additionaly a new "spc from scratch" menu has been added. You will find this on the graph toolbar submenu. c. Translation is now possible. But further documentation and contact to translators is needed. Users will find the translation tools on the testing page (in windows and linux versions). Please also test these. After test and removal of identified bugs this build will be released as v2.2. Known issues are: some datasets will give floating point error with xbar-s - please report on this. The internal validation routines used here are being updated to a new structure. Users are highly urged to test the new build and report problems here or in the feature and bug reporting database. The test versions are available from: http:\\www.epidata.dk\testing.php Other changes are expected soon in the documentation with a shift of core documentation (technical documentation) to a "wiki" based principle. After v2.2 a quite long period should be expected without new builds (apart from removal of identified serious bugs). The core parts are being rewritten to a common form for as well EpiData Entry, Epic and Analysis. And next test release will be based on this new core for all three parts. regards Jens Lauritsen EpiData Association

1 0

export to spss
by epidata-list＠lists.umanitoba.ca 11 Feb '09

11 Feb '09

Hi to All, I have a very simple question: when I am trying to export data to spss, the export menu transform the .rec files into .sps files, ie syntax and not .sav files, ie data files. Any idea why? Thanks for your help Best Regards Jean-Francois Dr Jean-Francois Trani Leonard Cheshire Disability and Inclusive Development Centre University College London 4 Taviton Street London WC1H 0BT Tel: +44 (0)20 7679 4886 Fax: +44 (0)20 7388 2291 Email: j.trani(a)ucl.ac.uk Website: www.lcdisability.org/idc Thank you for thinking of the environment before printing this message

1 1

Simple question
by epidata-list＠lists.umanitoba.ca 11 Feb '09

11 Feb '09

I am fairly new to epidata and wonder if someone can give me some advice on the following task: I am trying to determine if there is any significance in the difference between the number of days hospital outbreaks of norovirus last as against the length of community outbreaks. Is that something I could do in epidata, if so, which function would I use? 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

Link updata to learning/teaching material in portuguese
by epidata-list＠lists.umanitoba.ca 11 Feb '09

11 Feb '09

Lauritsen, Recently, I realized that the web adress to the Epidata Entry learning/teaching material in Portuguese changed. Therefore, the link right beside the Epidata entry portuguese file download is broken. Ther correct link from now on is: http://www.pesquisaclinica.ipec.fiocruz.br/cgi/cgilua.exe/sys/start.htm?inf… Best regards, -- Abraço forte e que a força esteja com você, Pedro Emmanuel

1 0

Re: EpiData-list Digest, Vol 64, Issue 4
by epidata-list＠lists.umanitoba.ca 11 Feb '09

11 Feb '09

Hello Dr Jean-Francois! That is the default epidata export to SPSS . if you want to have access to the file in .sav format, please follow the procedure. 1. Launch your spss software. 2 Go to file menu ->Open-> Syntax. 3. In the syntax window, select all and click on run. With this steps you can have you files in data file(i.e .sav) instead of the syntax file. regards Mensah On Tue, Feb 10, 2009 at 6:00 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 (epidata-list(a)lists.umanitoba.ca) > > > ---------- Forwarded message ---------- > From: epidata-list(a)lists.umanitoba.ca > To: epidata-list(a)lists.umanitoba.ca > Date: Tue, 10 Feb 2009 16:14:13 +0000 > Subject: [EpiData-list] export to spss > Hi to All, > I have a very simple question: when I am trying to export data to spss, the export menu transform the .rec files into .sps files, ie syntax and not .sav files, ie data files. Any idea why? > Thanks for your help > Best Regards > Jean-Francois > Dr Jean-Francois Trani > Leonard Cheshire Disability and Inclusive Development Centre > University College London > 4 Taviton Street > London > WC1H 0BT > > Tel: +44 (0)20 7679 4886 > Fax: +44 (0)20 7388 2291 > Email: j.trani(a)ucl.ac.uk > Website: www.lcdisability.org/idc > Thank you for thinking of the environment before printing this message > > > ________________________________________ > 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

re: export to spss
by epidata-list＠lists.umanitoba.ca 10 Feb '09

10 Feb '09

Hi to All, > I have a very simple question: when I am trying to export data to > spss, the export menu transform the .rec files into .sps files, ie > syntax and not .sav files, ie data files. Any idea why? Thanks for > your help Best Regards Dr Jean-Francois Trani , London. The explanation is quite simple. SPSS, SAS and other commercial software companies like M$ are using closed (proprietary) data formats, which they are not documenting. Therefore we cannot export to .sav format. This is in contrast to e.g. EpiData or Stata, where the file formats are fully documented and available for general download. I suggest you write an e-mail to SPSS and ask why they have a secret data file format. I would be astonished if they even answered your mail. The system of closed formats is even more strange. Earlier we had (in my hospital department) license for SAS for some years (cost around 1200 Euro per year for one PC) for about what EpiData Analysis can do. And now we cannot even use our licensed exe files to read the data again...... This is one of the reasons why we develop EpiData Software. ... For users in extensive need of converting data I suggest to look at the EpiC utility we develop or you can look at StatTransfer, which is working quite well and has the policy "once paid - use as long as you like". Kind regards Jens Lauritsen EpiData Association

1 0

SPSS export
by epidata-list＠lists.umanitoba.ca 10 Feb '09

10 Feb '09

Did you try running the syntax to see what happens? My guess is that you going to have a good surprise!!! -- Abraço forte e que a força esteja com você, Pedro Emmanuel

1 0

Re: EpiData / External systems Integration
by epidata-list＠lists.umanitoba.ca 08 Feb '09

08 Feb '09

Mark from TriSano asked on the list about how to best integrate analysis with other systems. The whole issue of integration has a lot of room in the EpiData Project and a number of tools are already capable of solving various aspects of this. E.g.: 1. EpiC: Batch data conversion, documentation, validation, backup, encryption 2. EpiData Analysis: Reporting systems for repeated analysis. 3. Documentation and examples - see the documentation part of the main website. - in particular study the technical documents. The documentation for EpiC is available from the documentation site and the conversion process of this year for EpiData Analysis and EpiData Entry adds to the diversity of integration possibilities. I expect the whole documentation for this to be ready later the coming year, but would in general say that the path follows this line for using EpIData Analysis with data created in other systems. The first thing would be to know whether exported csv files from the other system can be read. If not we could extend the import routines based on the experiences. Errors or inconsistencies can be reported to the Mantis database. Looking forward to a possible collaboration in this sense. (I will contact TriSano directly off list.). regards Jens Lauritsen EpiData Association

1 0

EpiData / TriSano Integration
by epidata-list＠lists.umanitoba.ca 06 Feb '09

06 Feb '09

To introduce myself, I am the Program Manager for TriSano - an open source, next generation disease surveillance and outbreak management application: http://www.trisano.org We just finished planning for TriSano 1.1 and one item we are in the process of determining is if there is a statistical package we should integrate with. EpiData seems to have potential. I thought I would reach out to you to see if you could point us in the right direction for the best way to do this with EpiData. I cc'd a number of my TriSano collaborators. Thanks in advance, Mike -- Mike Herrick Program Manager, Collaborative Software Initiative mike(a)csinitiative.com M: +1 971.340.0302 O: +1 503.295.7970 Extension: 104 F: +1 503.295.7789 1 SW Columbia Street, Suite 640 Portland, Or 97258 http://www.csinitiative.com

1 0

Double entry for a longitudinal study
by epidata-list＠lists.umanitoba.ca 28 Jan '09

28 Jan '09

I am preparing a double entry verification dataset for a longitudinal study; each participant has 6 follow-ups. Obviously, I'd like the double entry to compare the original entry with the correct follow-up number. For example, ID 100 has 6 follow-ups. I'd like to compare the original entry of follow-up 6 for ID 100 to the new entry of follow-up 6. As far as I know, you can only use ONE identifiable number to compare each entry, which makes double entry for a longitudinal study inconvenient. Is there a way to use both the ID number as well as the follow-up number while doing double entry? Thank you for your time and attention! Lindsay Lindsay Iser, M.A. University of South Florida Florida Mental Health Institute Department of Aging and Mental Health 13301 N. Bruce B. Downs BlVd. MHC 1403 Tampa, FL 33612 Tel-(813)-974-1975 Fax-(813)-974-1968

1 1

Definition of copyrights for EpiData software and documentation
by epidata-list＠lists.umanitoba.ca 28 Jan '09

28 Jan '09

One of the topics for decision on the pathway to open-source of the software is declaration of copy-rights. Formally the copy-right of current products lies with the EpiData Association in combination with the authors of documents etc, which in principle is defined as the sum of persons involved (users, developers, initiators, contributors), but in practice a core group of more influential persons. See the credit pages of the website. There are an abundance of various software open-source/freeware/,..... formulations of copyrights and license principles. Basically as I see it there are three considerations a. By releasing the software one does not take responsibility for errors, timeloss or other losses by using the software (protection against claims from users). b. Someone else should not take the documentation and or software and use for their own purpose without proper referring to those who created the various parts. c. How can we protect the development for future use without restrictions imposed by patents, licensing or similar. And how can we make sure to keep it from being "taken over" under changed conditions. I am not asking for a lengthy discussion of this on this list, but should anyone have viewpoints on the topic let us know. Currently I am favouring the use of this one: "Creative Commons Attribution-Non-Commercial-Share Alike 3.0 Unported Licence" which can be seen at: http://creativecommons.org/licenses/by-nc-sa/3.0/ as well in English as many other languages. The "Unported" means not translated. Kind regards Jens Lauritsen EpiData Association

1 1

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

17 Jan '09

I will be out of the office starting 01/17/2009 and will not return until 01/20/2009. If you require immediate assistance, please contact Celina Sousa at extension 5300. Thanks, Alyshia

1 0

IMIF command Problem
by epidata-list＠lists.umanitoba.ca 17 Jan '09

17 Jan '09

Dear All, I am finding a problem while using IMIF command to tabulate the Opportunistic infections of the database aids.rec. The PGM being used is AIDSP which is meant to tabulate the Opportunistic infections. When I run the PGM there is no tabulation of the Opportunistic infections. However select and freq commands do display the Opportunistic infections in the database. I was using IMIF command because the PGM was getting stuck where there were no Opportunistic infections data in the record. I am attaching the sample database and PGM file for testing in Try.zip file with this message.. Any help will be appreciated. Dr. Shavinder

1 2

Current development of Entry and Analysis - and a question
by epidata-list＠lists.umanitoba.ca 15 Jan '09

15 Jan '09

During recent months extensive work was done rewriting core parts of the software to a unified form for Entry and Analysis regarding reading, saving, exporting, importing and validating data in the internal structures. All of this is not visible to the end-user, but remedies some of the problems seen with different functioning of Entry and Analysis. The strategy is to ensure unified modularity of the internal structure instead of the "add lumps" principles which to some extend have been used over the first five years of development. At the same time known problems and deficiencies are fixed, e.g.: a. In Analysis the graph and table dialogs cannot be resized b. In Entry a clearer logic of creating data files and chks can be implemented, and implementation of Good Clinical Practice principles. As part of the core parts development a key highly technical decision has to be taken: One subtle aspect of earlier standards has been that integer variables were treated in a different form depending on the 1-4 or 5 and larger. Where integers of length 5 (#####) and larger actually were kept internally in the software (Entry and Analysis) as float variables with 0 decimals. The reason for this rests in the old Epi6 format and memory usage in the 1980'ies. We have taken the decision that from next versions of Analysis and Entry all will be built upon a common core system, where all integers (up to 14 in length) are treated as integers internally in the system. The change will only have impact for users reading rec files in other software than EpiData. All existing rec files will be read with no changes. For exports and imports the software will adapt appropriately. But users will have to use the most new versions for reading files created after the change. If anyone reject to this decision please discuss the consequences here on the list. -- Jens Lauritsen Coordinator and initiator of EpiData Project http://www.epidata.dk -- Jens Lauritsen Coordinator and initiator of EpiData Project http://www.epidata.dk

1 0

problem with dialog box
by epidata-list＠lists.umanitoba.ca 15 Jan '09

15 Jan '09

I downloaded EpiData Analysis V2.1.0.157 and wanted to conduct a basic analysis. I can read in a dataset and click on the "Analysis" button. If I select something like "Tables", a dialog box opens up that cannot be resized (to see all of the options in the dialog box). Is there an easy solution to this? Dragging the corners of the box with my mouse does not seem to work, nor does pressing any button while dragging the box. It seems like there should be a scroll bar on the right side too so that one can scroll down to see the "Sorting" options; without this ability, the Sorting options are cut off. Reinstalling EpiData does not seem to solve the problem either. Is there a simple solution to this problem? Wayne Enanoria

1 2

Re: Relate example in Epidata
by epidata-list＠lists.umanitoba.ca 23 Dec '08

23 Dec '08

Renate wrote "I am trying to figure out how the relate function works in Epidata. I am following the examples on the epidata website. I downloaded this zip file today: Relate example - Clinical Study with four forms" Unfortunately I think the uploaded copy was with errors. I just uploaded a fresh copy, which worked on my PC. I used EpiData Entry version 3.1, build (060106) with Windows XP. Please download again and report to the list if the new one works. http://www.epidata.dk/php/downloadc.php?file=epidata_clin_study_example.zip I suggest also to try the other relate examples also found on http://www.epidata.dk/examples.php regards Jens Lauritsen EpiData Association

1 0

Re: [EpiData-list] Export of file from EpiData Entry to new rec file
by epidata-list＠lists.umanitoba.ca 23 Dec '08

23 Dec '08

Hi Jens Thanks for getting back to me about the error I reported. I'm using Epidata version 3.0, (build 131103) and Windows 2000. I tried doing the Export Data/back up command on my workmates computer (who also has Epidata loaded and is on the same network) and we did not get the error. Everything worked fine. The two differences between the two of us are 1. she is using XP 2. she has adminstrator rights to our network (meaning she could save to the C Drive) However I was not trying to save the file to the C Drive. I had not chosen a location to export to when I got the error, or even selected a file to work with. The error I got came up as soon as I clicked on "Back up" before even a dialogue box appeared. I gave you the name of the last file I had been working with as I noticed this appears by default in the dialogue box when I (sucessfully) used the other Export Data commands I have been using this version of Epidata for some time and have had no other problems. I can't remember if I have tried to do a back up before with this version - it is not a command I use a lot. Perhaps it is just a bug with my computer. It is being upgraded to XP in the new year so it will be interesting to see if the error goes away after that. Merry Christmas and thanks again for this great software. Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 >>> <epidata-list(a)lists.umanitoba.ca> 21/12/2008 8:27 a.m. >>> Christine reported: > I am having a problem with the Export data command in Epidata. I had made a rec file for someone else and I wanted to show them how they could save the file to another directory after they had completed their data entry. I clicked on EXPORT Data/Back up but I got a message saying "invalid filename." No dialogue box came up at all just the message, so I had not selected a file to export. There was no problem I could see with this file. I had sucessfully created it and entered data into it. > I had no problem here exporting to the name you used with: EpiData Entry (version 3.1, build 060106)) on windows xp The error you are mentioning could indicate to me, that you are working with Windows Vista, since I have seen a number of very strange errors on this. Due to the fact that Vista is by default to dis-allow (reject) many logical choices by the users. The other possibility is that you have insufficient rights to export to the folder, where you try do so, and only the error message is insufficient. On one particular pc I had a problem, that suddenly the Vista system decided to delete the CHK file of a system. Most likely because the work I did coincided with an internal routine cleaning up files (not under user control) and the setup of that pc was to delete all files called CHK, which by windows is used also as the extension for files found by defragmentation. If this happens repeatedly we might have to change the extension of the chk file to something else, e.g. ckh - finally also it could be a bug in the EpiData Entry software. Please try to export on a different pc and see if you can replicate. is it a problem with the file name or with exporting as such to recfile. When reporting problems here it is good practice to tell which software version, build and operation system. regards Jens Lauritsen EpiData Association -- 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

Relate example in Epidata
by epidata-list＠lists.umanitoba.ca 22 Dec '08

22 Dec '08

Hi Epidata members, I am trying to figure out how the relate function works in Epidata. I am following the examples on the epidata website. I downloaded this zip file today: Relate example - Clinical Study with four forms Working example of the structure for a Clinical study with a start, then by relating on id entering data into basic person information, sideeffects, status information and pre-study level. This example is giving me all kinds of errors. First, I thought that it was because the Start.Rec and Clinical Study.rec are the same. I excluded all the files starting with start.*. This wasn't the case, I narrowed it down to the file controlvisit.rec. The error received is : The field id is KEY UNIQUE, but duplicate keys were found in records 1 and 2. A second error pops up directly after the first one: Access violation at address 004138D3 in module 'EpiData.exe' Read of address 00000000. I am looking forward to learn more on how to solve this issue. Happy Holidays! Renate Renate van Dorp, MSc, PhD Epidemiologist Perth District Health Unit 653 West Gore Street Stratford, ON N5A 1L4 Tel: 519-271-7600 ext 246 Fax: 519-271-2195 Email: rvandorp(a)pdhu.on.ca <mailto:rvandorp@pdhu.on.ca> This message is intended only for the named recipient and may contain information that is exempt from disclosure under privacy legislation in the Province of Ontario. If you received this in error, please contact the sender immediately by return electronic transmission and then immediately delete this transmission, including all attachments, without copying, distributing or disclosing same.

1 0

Export of file from EpiData Entry to new rec file
by epidata-list＠lists.umanitoba.ca 20 Dec '08

20 Dec '08

Christine reported: > I am having a problem with the Export data command in Epidata. I had made a rec file for someone else and I wanted to show them how they could save the file to another directory after they had completed their data entry. I clicked on EXPORT Data/Back up but I got a message saying "invalid filename." No dialogue box came up at all just the message, so I had not selected a file to export. There was no problem I could see with this file. I had sucessfully created it and entered data into it. > I had no problem here exporting to the name you used with: EpiData Entry (version 3.1, build 060106)) on windows xp The error you are mentioning could indicate to me, that you are working with Windows Vista, since I have seen a number of very strange errors on this. Due to the fact that Vista is by default to dis-allow (reject) many logical choices by the users. The other possibility is that you have insufficient rights to export to the folder, where you try do so, and only the error message is insufficient. On one particular pc I had a problem, that suddenly the Vista system decided to delete the CHK file of a system. Most likely because the work I did coincided with an internal routine cleaning up files (not under user control) and the setup of that pc was to delete all files called CHK, which by windows is used also as the extension for files found by defragmentation. If this happens repeatedly we might have to change the extension of the chk file to something else, e.g. ckh - finally also it could be a bug in the EpiData Entry software. Please try to export on a different pc and see if you can replicate. is it a problem with the file name or with exporting as such to recfile. When reporting problems here it is good practice to tell which software version, build and operation system. regards Jens Lauritsen EpiData Association

1 0

France
by epidata-list＠lists.umanitoba.ca 20 Dec '08

20 Dec '08

Dear Jens, "2008" is a good year for epidemiology and statistic... Thank you for your work and the new versions of EPIDATA Analysis 2.xx. The "lifetable" programs are very interesting for epidemiologists. I hope that 2009 year will a new good year for you and for us, happy users of this software. For your interest, I join a file with four variables and 239 lines. "Arret" is outcome variable (1=interest), and "durall" time variable in weeks. Plus two variables "plaisir" and "moment" in two categories (1 and 2). The result of lifetable command with "lifetable arret durall /by=plaisir /p50 /t" is curious (with version 159 and anterior) instead of "7" or "8" for the categorie "plaisir=2" (probability of 0.50). It's OK with variable "moment". Why the reason ? Sincerely Bernard Branger PS : The link for "Course materials in French" is the following : http://www.reseau-naissance.com/joomla/index.php?option=com_content&task=cat egory&sectionid=20&id=70&Itemid=148 -- J'utilise la version gratuite de SPAMfighter pour utilisateurs prives. Jusqu'a present SPAMfighter a bloque 298 courriels spam. Nous avons en ce moment 5.7 millions d'utilisateurs de par le monde entier. Les utlisateurs payants n'ont pas ce message. Vous pouvez telecharger la version gratuite: http://www.spamfighter.com/lfr

1 1

Exporting
by epidata-list＠lists.umanitoba.ca 19 Dec '08

19 Dec '08

I am having a problem with the Export data command in Epidata. I had made a rec file for someone else and I wanted to show them how they could save the file to another directory after they had completed their data entry. I clicked on EXPORT Data/Back up but I got a message saying "invalid filename." No dialogue box came up at all just the message, so I had not selected a file to export. There was no problem I could see with this file. I had sucessfully created it and entered data into it. I had no trouble with exporting the file I had just created to Excel or dbf. In each case a dialogue box came up asking me what I wanted to call the new file and it sucessfully created a file in the new format. I could also select Epidata and save the full file under a new name. I tried loading another file and doing some data entry in it, so this different file was the last one used, and then tried to back up export. The same thing happened. I got the same 'invalid file name.' message and no dialogue box. I could however use the other commands in the export menu on this file. The name of the file I was trying to export was UHutt_Youth_Questionnaires_2008.rec but I got the error message before I had selected the file so I can't see how the name itself would be a problem. thanks Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 -- The information contained in this email and any attachments is confidential and may be legally privileged. If you have received this message in error, please notify the sender immediately and remove all copies of the message, including any attachments. Any views or opinions expressed in this email (unless otherwise stated) may not represent those of Hutt Valley DHB. Thank you. ** Disclaimer added by HVDHB **

1 0

EpiC Installation Instructions--Please review if this is correct?
by epidata-list＠lists.umanitoba.ca 06 Dec '08

06 Dec '08

Dear All I begun testing how I could automate some routines (data export mainly) using EpiC. I searched around on the website for instructions on how to install and use EpiC. I am not a programmer to start of with, but in the EpiC.PDF document it states the ff : "EpiC is a utility for some of the functions and tools in EpiData. EpiC can be run from a command prompt or from a command (or batch) file, making it possible to automate repetitive tasks". So I wondered how to invoke the command prompt in Windows?? (cmd in run). I finally managed to solve this like so: ****************** 11:41 AM 12/6/2008 EPiC installation: 1.Download the EpiC.ZIP file from Epidata.dk 2. Unzip to EpiC folder using unzip program (7-zip) 3. Open EpiC folder and find 2 files in it: EpiC.exe and EPiC.pdf 4. Copy EpiC.exe into the Windows system32 folder (you will need admin previlages for this): VISTA: C:\Windows\System32 XP: C:\Windows\System32 Now in the same folder as the .REC file was created/stored, create a new .TXT file (call it export_epic_commands.txt). In this file write the EpiC commands. E.g. to automate export to SAS (see other commands in EpiC.PDF file): epic e sas inputfile.rec outputfile * Once the commands are typed into the TXT file, save it, and then rename the extension to CMD, like so export_epic_commands.cmd. This is now executable by double-clicking it. Once executed 3 (you will see a black screen flash a couple of time--very fast!) additional files will be created in the same folder where the .REC file was: outputfile.sas and outputfile.txt and EpiC.log (this file has all the commands executed and error messages--be sure to check it; compare with codes provided in the EpiC.PDF file) ************************ Please let me know if I have overlooked anything or it is not necessary to copy paste EpiC.exe in the system folder (seems odd to be be doing this, as sometimes admin previlages are not availabe? Thanks, S Kauchali UKZN South Africa

1 0

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

05 Dec '08

I have a field UNITNUM with values for treatment units. 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 2

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

Changing id value
by epidata-list＠lists.umanitoba.ca 24 Nov '08

24 Nov '08

Can anyone tell me how to change the value of in my id? When ever I change the value some of my data disappears. Thanks Raphael

1 0

Numeric Range for field
by epidata-list＠lists.umanitoba.ca 24 Nov '08

24 Nov '08

Hello, In the .chk file, I want to define a range for a numeric field (v1 ###) as follows: 100-120, 200-250 (Break the continuity) But I'm trying generates an error. Note: Epidata accept: 100-120, 200 In addition tried v1 RANGE 100 120 RANGE 200 250 END Then, open the REC but when entering data and a message "is not a valid floating point value" What's happening? and how can I set the range for my values, without defining them individually? Cordially Carlos Ortega Areyte Biostatistics from Chile, South America -- Carlos A. Ortega Areyte Prof. de Matemática y Computación Magíster en Bioestadística ACADÉMICO

1 0

Select, if and count giving different numbers in EpiData Analysis v2x
by epidata-list＠lists.umanitoba.ca 21 Nov '08

21 Nov '08

For certain logical statements the following commands would work on different subsets of the data read myfile sort samlet select if (samlet = samlet[_n-1]) count if (samlet = samlet[_n-1]) test = test + "x" if (samlet = samlet[_n-1]) if (samlet = samlet[_n-1]) then test = test + "x" .................................................................................................................... The bad news is that this is very bad behaviour. The good news is that the cause of the error has been located and a new build (v2.1.0.157) has been uploaded. If you are not working with selects and if statements this will not affect your work. Strange that no-one found the bug before (I found this yesterday) and the test environment has been extended with this aspect. regards Jens Lauritsen EpiData Association

1 0

How to: repeat variables for group level entry and clear when group changes
by epidata-list＠lists.umanitoba.ca 21 Nov '08

21 Nov '08

Posed indirectly: >Can anyone help me with the following question? >Is there a function on EpiData Entry which allows data to be >repeated from one record to the other (without the data enterer >having to fill in all the same data again)? > >For example, we are interviewing all the family members in 10 >different households. On the record of each household member, the > 'household' data will be the same, but their individual data will be > different. We want the household data to appear on each record >without the data enterer having to re-enter all the data. > >Is it possible to put a command in the .chk file so the data is >re-entered on that record automatically? > >For Example: >Qu: Does this individual belong to the same household as the >previous record? (If the answer is yes, the 'household data' will > automatically replicate that of the previous record). >Thanks in advance for your advice, > > Dr Jean-Francois Trani > Leonard Cheshire Disability and Inclusive Development Centre > University College London > Website: www.lcdisability.org/idc Answer: This can be done with the "repeat" and "clear" feature. An example has been uploaded to the page http://www.epidata.dk/examples.php ................................................................................................................ Extract of chk file is: same COMMENT LEGAL USE label_same MUSTENTER type comment allfields Blue AFTER ENTRY IF same = 2 THEN CLEAR class CLEAR school ELSE GOTO age ENDIF END END school COMMENT LEGAL USE label_school REPEAT END ................................................................................................................ regards Jens Lauritsen EpiData Association

1 0

Database
by epidata-list＠lists.umanitoba.ca 19 Nov '08

19 Nov '08

Hi. Hi. Can Epidata fetch data from one or more database and add up the data in Epidata database? Is Epidata safe for using in matters of social security numbers etc.? Thanks in advance/ Uffe.

1 2

SPC commands for testing and other aspects of EpiData Analysis v2.1
by epidata-list＠lists.umanitoba.ca 16 Nov '08

16 Nov '08

Dear All We are approaching finalisation of the current SPC graph implementation in EpiData Analysis. But await comments and further testing by users and specialists. Some errors were found in build 155 for Ichart-moving range charts. Today build 156 has been uploaded. Since public release of v2.1.0 the following SPC graphs have been implemented in the test version 2.1.1. build 156 available from http://www.epidata.dk/testing.php : Gchart, UChart, XBar (Sigma and Range), CChart, Ichart moving range Apart from the new commands it would be good if users would comment further on the new aspects of v2.1, e.g. the current implementation of lifetables. How is it working in practice, is the help file sufficient etc. An issue was raised on the list regarding use of "actuarial versus Kaplan-Meier" principles. It seems as if this relates to use of floating point variables (e.g. 1.4 week) for the time variable, which now is read as a rounded integer variable. Following further clarification I will notify here. Next in line in the development is release of a translation tool, such that analysis can be translated in a "smooth" way. And in analysis further implementation of "set ...." will be added to facilitate easier default setting of user options. The following general "set" will be added: set graph option=" ......" (for all graphs) set table option=" ......" (for cross tables and frequency tables) set spc option=" ..... " (for spc graphs and analysis) Possible also the following will be added for means, describe etc.: set descriptive option="..... " regards Jens Lauritsen EpiData Association

1 0

Date-illegal entry
by epidata-list＠lists.umanitoba.ca 14 Nov '08

14 Nov '08

Thank you for your response to my date question. During entry, if the date field is not applicable to a certain record (whereas I do not need to enter a date for that specific record, rather skip it) what do I designate as my skip code. I did have -77, but when I would enter that, it would say it was an illegal entry. How do I write the code, so that a skip is -77, and it still be a legal entry in some instances? legdat RANGE 01/01/1900 31/12/2008 LEGAL 30/12/2009 24/11/2008 END END (somewhere in there, I need to put it a skip code) Thank you for your time, Lindsay Lindsay Iser, M.A. University of South Florida Florida Mental Health Institute Department of Aging and Mental Health 13301 N. Bruce B. Downs BlVd. MHC 1403 Tampa, FL 33612 Tel-(813)-974-1975 Fax-(813)-974-1968 -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list-request(a)lists.umanitoba.ca Sent: Thursday, November 13, 2008 1:10 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 61, Issue 7 Send EpiData-list mailing list submissions to epidata-list(a)lists.umanitoba.ca To subscribe or unsubscribe via the World Wide Web, visit http://lists.umanitoba.ca/mailman/listinfo/epidata-list or, via email, send a message with subject or body 'help' to epidata-list-request(a)lists.umanitoba.ca You can reach the person managing the list at epidata-list-owner(a)lists.umanitoba.ca When replying, please edit your Subject line so it is more specific than "Re: Contents of EpiData-list digest..." EpiData-list mailing list ___________________________________ Today's Topics: 1. Re: "Illegal entry" Dates (epidata-list(a)lists.umanitoba.ca) 2. charting developments in hospital infections - extension (epidata-list(a)lists.umanitoba.ca) 3. Re: Algorithm RUT, numeric field (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Wed, 12 Nov 2008 20:21:14 +0100 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] "Illegal entry" Dates To: epidata-list(a)lists.umanitoba.ca Message-ID: <491B2CAA.1090708(a)tbrieder.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed You cannot have illegal dates: 99, -77, 88 are not dates and if they were, they are not legal, there is no date that contains, e.g. "99". A command for a legal date range and legal date values should look something like this (using European date format here): legdat RANGE 01/01/1900 31/12/2008 LEGAL 30/12/2009 24/11/2008 END END Regards, Hans epidata-list(a)lists.umanitoba.ca wrote: > Provided below is the syntax. I've also made a few notes about the > error I am getting. I have tried several times to fix this, but for > some reason EpiData is telling me it is illegal. > > > > 1. fa163axxxx > > RANGE 01/01/1900 12/31/2008 > > LEGAL > > 99 > > -77 > > 88 > > END > > MUSTENTER > > END > > > -- 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 ------------------------------ Message: 2 Date: Thu, 13 Nov 2008 00:18:43 +0100 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] charting developments in hospital infections - extension To: epidata-list(a)lists.umanitoba.ca Message-ID: <491B6453.9070802(a)epidata.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Regarding the most recent question to the list on MRSA infections, users could read these articles: Mohammed MA, Worthington P, Woodall WH. Results of a multicentre randomised controlled trial of statistical process control charts and structured diagnostic tools to reduce ward-acquired meticillin-resistant Staphylococcus aureus: the CHART Project.J Hosp Infect. 2008 Oct;70(2):127-35. Epub 2008 Aug 23. Curran E, Harper P, Loveday H, Gilmour H, Jones S, Benneyan J, Hood J, Pratt R. Results of a multicentre randomised controlled trial of statistical process control charts and structured diagnostic tools to reduce ward-acquired meticillin-resistant Staphylococcus aureus: the CHART Project.J Hosp Infect. 2008 Oct;70(2):127-35. Epub 2008 Aug 23. Borckardt JJ, Nash MR, Hardesty S, Herbert J, Cooney H, Pelic C. How unusual are the "unusual events" detected by control chart techniques in healthcare settings? J Healthc Qual. 2006 Jul-Aug;28(4):4-9. regards Jens Lauritsen EpiData Association ------------------------------ Message: 3 Date: Thu, 13 Nov 2008 08:20:31 -0500 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] Algorithm RUT, numeric field To: epidata-list(a)lists.umanitoba.ca Message-ID: <491C299F.3030509(a)sympatico.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed There is an example of this, based on the Danish CPR number on the Epidata web site: http://www.epidata.dk/examples.php The example is in English & Danish, with an explanation in English. You input the number as a single text field and then "take it apart" into its individual digits. Jamie Carlos wrote wrote: > I would like to know if I can read a numeric field and break down their > individual one-digit figure. > This, with the intention of obtaining the digit verifier (dv) of a RUT. > > I tried an algorithm, but I have to make individual fields for each digit, > > ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 61, Issue 7 *******************************************

1 2

Algorithm RUT, numeric field
by epidata-list＠lists.umanitoba.ca 13 Nov '08

13 Nov '08

I'm from Chile (South America), my native language is Spanis... I write a draft text below. Estimados amigos, Me gustaria saber si puedo leer un campo numérico y descomponer individualmente sus dígitos de aquella cifra. Esto, con la intención de obtener el digito verificador(dv) de un RUT. Intenté un algoritmo, pero tengo que hacer campos individuales para cada digito, que no es la idea, lo que hago es: R1# R2# R3# R4# R5# R6# R7# R8# -dv<A> entonces ingreso: 3 0 6 8 6 9 5 7 -dv 4(este surge del algoritmo) Me gustaria que fuese asi: RUT ######## -dv<A> (este surga del algoritmo) 30686957 -dv 4 Les agradesco mucha vuestra colaboración. Carlos Ortega Areyte Academico Procedimiento para obtener el dígito verificador. -------------------------------------------------- El RUT consta de dos partes, el número y el dígito verificador separados por un guión. En el siguiente ejemplo se toma como RUT el número 30.686.957- X, donde 30.686.957 es el número del RUT y X será el dígito verificador que se desea verificar o conocer: - Se procede a tomar el número de RUT de derecha a izquierda, multiplicando cada dígito por los números que componen la serie numérica 2,3,4,5,6,7; y sumando el resultado de estos productos, como se muestra a continuación (si se ha aplicado la serie hasta el 7 y quedan dígitos por multiplicar, se comienza la serie nuevamente): En el ejemplo: 7 × 2 = 14, 5 × 3 = 15, 9 × 4 = 36, 6 × 5 = 30, 8 × 6 = 48, 6 × 7 = 42, 0 × 2 = 0, 3 × 3 = 9, entonces la suma de los productos es: 14+15+36+30+48+42+0+9 = 194 - Al número obtenido por la suma del producto de cada dígito por la serie ya mencionada, se le aplica módulo 11, o sea, se divide por 11 y se determina el resto de la división. En el ejemplo: 194: 11 = 17 Resto: 7 Ahora a 11 se le resta el resto: En el ejemplo: 11 - 7 = 4 Si el resultado es 11, el dígito verificador será 0. Si el resultado es 10, el dígito verificador será K. En otro caso el resultado será el dígito verificador. Como en el ejemplo el resultado de la resta es 4, el dígito verificador es 4. Por ende, el RUT del ejemplo es el 30.686.957-4. Por cierto, este ejemplo lo Obtuve de es.wikipedia.org ************** ************** ******************************* This is a translation, I'm from Chile (South America), my native language is Spanish ... sorry my little English. Dear friends, I would like to know if I can read a numeric field and break down their individual one-digit figure. This, with the intention of obtaining the digit verifier (dv) of a RUT. I tried an algorithm, but I have to make individual fields for each digit, that is not the idea, what I do is: R1 # R2 # R3 # R4 # R5 # R6 # # R7 R8 # -dv <A> then login: 3 0 6 8 6 9 5 7 dv- 4 (this born from the algorithm) I would like it to be like this: RUT ######## -dv <A> (this born from the algorithm) 30686957 -dv 4 Thank you very much for your cooperation. Carlos Ortega Areyte Academic Obtain the procedure for verifying digit. -------------------------------------------------- The RUT is in two parts, the number and verifying digit separated by a hyphen. In the following example is taken as RUT number 30686957 - X, where 30686957 is the number of RUT and X will be the verifying digit you want to know or verify: - We shall proceed to take the number of RUT from right to left, by multiplying each digit numbers that make up the numerical series 2,3,4,5,6,7; and adding the output of these products, as shown below (if the series has been implemented and are up to 7 digits per leverage, the series begins again): In the example: 7 x 2 = 14 5 x 3 = 15, 9 × 4 = 36 6 x 5 = 30, 8 × 6 = 48 6 x 7 = 42 0 x 2 = 0, 3 x 3 = 9 then the sum of products is: 14 +15 +36 +30 +48 +42 +0 +9 = 194 - The number obtained by the amount of the proceeds of each digit in the series already mentioned, it is covered module 11, in other words, is divided by 11 and determining the rest of the division. In the example: 194: 11 = 17 Rest: 7 Now he is a 11 subtracts the rest: In the example: 11-7 = 4 If the result is 11, the verifier digit will be 0. If the result is 10, will be verifying digit K. Otherwise the result will be verifying digit. As in the example the result of the remainder is 4, the digit verifier is 4. Thus, the RUT's example is the 30.686.957- 4. this example of what I got es.wikipedia.org -- Carlos A. Ortega Areyte Prof. de Matemática y Computación Magíster en Bioestadística ACADÉMICO

1 1

charting developments in hospital infections - extension
by epidata-list＠lists.umanitoba.ca 12 Nov '08

12 Nov '08

Regarding the most recent question to the list on MRSA infections, users could read these articles: Mohammed MA, Worthington P, Woodall WH. Results of a multicentre randomised controlled trial of statistical process control charts and structured diagnostic tools to reduce ward-acquired meticillin-resistant Staphylococcus aureus: the CHART Project.J Hosp Infect. 2008 Oct;70(2):127-35. Epub 2008 Aug 23. Curran E, Harper P, Loveday H, Gilmour H, Jones S, Benneyan J, Hood J, Pratt R. Results of a multicentre randomised controlled trial of statistical process control charts and structured diagnostic tools to reduce ward-acquired meticillin-resistant Staphylococcus aureus: the CHART Project.J Hosp Infect. 2008 Oct;70(2):127-35. Epub 2008 Aug 23. Borckardt JJ, Nash MR, Hardesty S, Herbert J, Cooney H, Pelic C. How unusual are the "unusual events" detected by control chart techniques in healthcare settings? J Healthc Qual. 2006 Jul-Aug;28(4):4-9. regards Jens Lauritsen EpiData Association

1 0

"Illegal entry" Dates
by epidata-list＠lists.umanitoba.ca 12 Nov '08

12 Nov '08

Provided below is the syntax. I've also made a few notes about the error I am getting. I have tried several times to fix this, but for some reason EpiData is telling me it is illegal. 1. fa163axxxx RANGE 01/01/1900 12/31/2008 LEGAL 99 -77 88 END MUSTENTER END 1: i. No date will satisfy the commands. ii. When you do put a date it, it reads : "Illegal entry- Legal values are 01/01/1900-12/31/2008, -77, 99, 88" iii. I've tried to change the field type to date and have had difficulty making these changes. 2. fa163cxxxx RANGE 1/1/2004 1/1/2009 LEGAL -77 99 88 END MUSTENTER END 3. fa163exxxx RANGE 1/1/2004 1/1/2009 LEGAL -77 99 88 END COMMENT LEGAL USE nscid MUSTENTER END 2 and 3: i. No date will satisfy the commands. ii. When you do put a date it, it reads : "Illegal entry- Legal values are 1/1/2004-1/1/2009, -77, 99, 88" iii. I've tried to change the field type to date and have had difficulty making these changes. Thank you for your time!! Lindsay

1 1

sort field
by epidata-list＠lists.umanitoba.ca 11 Nov '08

11 Nov '08

I have 300 records, each was stored in a disorderly file, "failure.REC" So, when I preview the records, in step 5.Document (view data) this showing: id age sex event 2 0 1 25 80 1 1 28 125 0 1 36 3 1 1 19 18 0 1 44 23 0 0 12 . . . 10 0 0 21 300 0 1 39 287 1 0 58 1 0 1 23 How can I get these same records appear sorted by id, in the file failure.REC when I try to enter an new records? So when you enter the id 300, so this can then enter the id 300? I managed this trick, STATA by exporting to ... order by id, the new failure.dta Then, import failure.dta to a new failure.REC ... I am working. But it's also complicated and I do not retain the original format, let alone id ###### sex ###### event ###### age ###### erasing {id} What is the id of the questionnaire? # # # {sex} Indicate sex # {event} What is the patient's condition at the end of the period? # {age} Age at onset of the study # # I hope you understand my question. Carlos Ortega A. Biostatistics

1 1

Charting SPC (statistical process control) data with EpiData Analysis
by epidata-list＠lists.umanitoba.ca 09 Nov '08

09 Nov '08

Shakeel asked on the list: "Is there any way I can create SPC Charts that show actual counts (e.g of MRSA) against targets?" There are three SPC strategies here, depending on the frequency of MRSA infections: 1. If rare: Record date of incidence (e.g. dateinci) and save in a rec file, then in analysis (latest test release): read mrsadata ; Gchart dateinci /t 2. If a certain proportion of patients. Record dates (e.g. hospdate) number of infections (count) and total volume of patients (total): read mrsadata ; pchart hospdate count total /t 3. If you only have the counts, but not the totals, you can either do a runchart or ichart: read mrsadata ; runchart hospdate count /t ; Ichart hospdate count /t; In other words it depends on the nature of the contact to the patients, the similarity of the underlying data in subgroups etc. For adding the target an option with the graphs is required, e.g.: Say the target was 1 % of all patients with a certain infection: pchart hospdate count total /t /yline=0.1 /sub="Target indicated at Y=10%" A good advice is always regardless of the above, that a lot can often be learned by just plotting the raw data on a time scale. A "manual" for SPC is underway, but meanwhile read some of the textbooks available. regards Jens Lauritsen EpiData Association

1 0

Selecting Dates
by epidata-list＠lists.umanitoba.ca 08 Nov '08

08 Nov '08

Hello Could you please advise what I am doing wrong with my date selection process. I have a field called visitdate. Format = dd/mm/yyyy. The field itself is OK because FREQ visitdate works fine. My problem is when I try to select dates less than 1 July ( 01/07/2008) When I try select visitdate < "01/07/2008" I get an error message "Type Date is incompatible with type String operation aborted" When I try select visitdate < 01/07/2008 I get an error message "Type Date is incompatible with type Float Operation aborted" The only way I could find in the end was to use the month function to create a new field called visitmonth from visitdate and then select visit month <7. This worked, but I want to be able to select on the original visitdate field. Could someone help please? thanks Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 >>> <epidata-list-request(a)lists.umanitoba.ca> 29/11/2007 7:02 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 1

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

07 Nov '08

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

1 0

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

07 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

Epidata with lynux
by epidata-list＠lists.umanitoba.ca 04 Nov '08

04 Nov '08

How can I use Epidata with Lynux?

1 1

Options versus set
by epidata-list＠lists.umanitoba.ca 03 Nov '08

03 Nov '08

I am more than just in favor of options, I believe that they are the best possible approach, it makes everything so straight forward and simple. Sometimes we want something to test, then we do it with the option, else we take it out, and it is all in the same command line, rather than a "set xx=on" then the command, then "set xx=off" again. Options are very intuitive. Hans

1 0

Default behaviour of EpiData Analysis
by epidata-list＠lists.umanitoba.ca 02 Nov '08

02 Nov '08

There will always be differences as to how users wish to run different commands. Some time ago a discussion was on the list regarding the list. The decision was to move as much as possible to options, since otherwise the users have to issue different commands for changes. As was suggested by B.Branger why not "get back" the "set statistics", "set table percentage" etc. The problem of this is the implementation in the menu system (dialogs), which becomes a bit messy. The suggestion for users is rather to use the following technique: Add to your epidatastat.ini: define tableoption __________ global tableoption = " /t /R /C" // or whatever you prefer or shorter: define t __________ global t = " /t /R /C" // or whatever you prefer Now in your actual pgm file or at the command line, just issue: tab v1 v2 @t You might say "a bit annoying" to add @t, but still less than writing the options. Another aspect of the issue is that the set definitions mentioned are part of the Epi Info v6 specification, but many users who did not do statistical analysis with Epi6 are not aware of this by now. regards Jens Lauritsen Epidata Association

1 0