- EpiData-list - University of Manitoba Mailing Lists

Grouping for frequency tables
by epidata-list＠lists.umanitoba.ca 27 Nov '07

27 Nov '07

Hi Jens and colleagues Congratulations on the progress with Epidata analysis. I work with outbreaks so I love the OA function which lets you get the attack rate tables. My question is if it is possible to do something similar - to get a group of symptoms in one table. In our outbreak reports we want tables that show the count and percent of sick people with a range of symptoms - for example (say with 20 people ill) diarrhoea 20 100% Vomiting 10 50% Fever 5 25% At the moment I create a frequency table for each symptom and then cut and paste them into one summary table. I would like to know if there is a quick way to create just one symptoms table thanks Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 -- The information contained in this email and any attachments is confidential and may be legally privileged. If you have received this message in error, please notify the sender immediately and remove all copies of the message, including any attachments. Any views or opinions expressed in this email (unless otherwise stated) may not represent those of Hutt Valley DHB. Thank you. ** Disclaimer added by HVDHB **

1 1

EpiData Analysis v2.0 Build 129 available (any objections for release as current public version ?)
by epidata-list＠lists.umanitoba.ca 27 Nov '07

27 Nov '07

A few errors were trapped in v2.0.1.128, but I take the lack of reported errors beyond what I know of as an indication that the current build 129 can be released for general public use. Should this not be the case, please report errors immediately to the list. Notice that build 129 exists as well as v2.0.1.29 and v2.0.2.29, the latter is the one avialable at this point. For means and kwallis the correct syntax is: kwallis v1 /by=group means v1 /by=group but both commands will now accept the old syntax with a warning: kwallis v1 group - or - means v1 group Regards Jens Lauritsen EpiData Association

1 0

Re: Using Comment legal in recfiles
by epidata-list＠lists.umanitoba.ca 23 Nov '07

23 Nov '07

3. How to use large amounts of of legal values in chk file > We are building a data-entry system for the registration of medical contact for the youth in our organisation. > Therefore we need several hundreds of schoolcodes and zipcodes (postcode). > > On the page www.epidata.dk/examples.php there are two examples of using comment legal based on external files, - see these entitled: "Comment legal recfile - Birds and tick names" plus "Comment legal recfile - Bacteria list". regards Jens Lauritsen EpiData Association

1 0

How to use large amounts of of legal values in chk file
by epidata-list＠lists.umanitoba.ca 23 Nov '07

23 Nov '07

We are building a data-entry system for the registration of medical contact for the youth in our organisation. Therefore we need several hundreds of schoolcodes and zipcodes (postcode). For the quality of data I want to use this data in the chk file in the following way. In stead of: LABELBLOCK LABEL_POSTCODE LEGAL 2234 2344 2544 2645 . ETC END POSTCODE LEGAL USE LABEL_POSTCODE MUSTENTER END I want to use an externel file POSTCODE.INC whith the data and used the following syntax: LABELBLOCK LABEL_POSTCODE INCLUDE POSTCODE.INC END POSTCODE LEGAL USE LABEL_POSTCODE MUSTENTER END But I only get errors. Someone has a solution? Franco L. Sanavro Epidemiologist Regional Health Centre GGD Zuid-Holland Zuid Postbus 166 3300 AD Dordrecht The Netherlands 078 6321817 fsanavro(a)ggdzhz.nl www.ggdzhz.nl

1 1

Slow output when using EpiData Analysis
by epidata-list＠lists.umanitoba.ca 23 Nov '07

23 Nov '07

1. Output formation and slow output To remedy slow output: hit F12 button every so often. This will clear the screen and output speed goes up. Explanantion: Output in EpiData Analysis is created in html format. The same format used on internet pages. The good feature of this is that formatting is easy without a lot of programming. E.g. for reporting users can write: set echo=off read myfile count if age > 45 /q type "Number of persons was @$count" /h3 tab sex boxplot age /by=sex /ti="Current age structure by sex" set echo = on and the sentence with "type" will show the number of counts in a header type line (/h3) followed by a table of sex and a boxplot. The problem of html is however that it is a block structured file format. Therefore each time a line is added the whole output - not just the added line - has to be written on the screen. Therefore the speed of output slows down for every additional line you add. After a certain length of the output the screen clears automatically. Users cannot control this length (currently). To remedy slow output: hit F12 button every so often. Then when you have the complete output you wish, save the commands as a pgm file and run all again. Or at some point issue "logclose" and read the resulting logfile (default EAoutput.htm) in a browser. 2: Vista and analysis: There has been a report that EpiData Analysis cannot run on Windows Vista. If anyone are using Vista, please report your experiences with this. I assume that the specific user had insufficient "writing rights" to the Vista machine, since the stopping occurred when trying to open EAoutput.htm as part of the initiation sequence for analysis. regards Jens Lauritsen EpiData Association

1 0

RE: EpiData-list Digest, Vol 49, Issue 11
by epidata-list＠lists.umanitoba.ca 22 Nov '07

22 Nov '07

Please unsubcribe my name from Epidata, as I cannot do this myself online, having forgotten my password. With Thanks I. Riach ________________________________ From: epidata-list-bounces(a)lists.umanitoba.ca on behalf of epidata-list-request(a)lists.umanitoba.ca Sent: Fri 23/11/2007 5:01 AM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 49, Issue 11 Send EpiData-list mailing list submissions to epidata-list(a)lists.umanitoba.ca To subscribe or unsubscribe via the World Wide Web, visit http://lists.umanitoba.ca/mailman/listinfo/epidata-list or, via email, send a message with subject or body 'help' to epidata-list-request(a)lists.umanitoba.ca You can reach the person managing the list at epidata-list-owner(a)lists.umanitoba.ca When replying, please edit your Subject line so it is more specific than "Re: Contents of EpiData-list digest..." EpiData-list mailing list ___________________________________ Today's Topics: 1. EpiData Analysis v2.0 Build 128 available (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Thu, 22 Nov 2007 17:36:44 +0100 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] EpiData Analysis v2.0 Build 128 available To: epidata-list(a)lists.umanitoba.ca Message-ID: <4745B01C.1090106(a)epidata.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed I just uploaded v2.0.1.128 on the page: www.epidata.dk/testing.php This build remedies as far as we can test here the problems shown since release of v2.0: - saving data files with automatic naming - odds ratios in stratified tables with more than two strata - memory leaks. Plan for current testversion: 1. Leave on testing.php page for a few days (3-4 days) 2. Move as current release on the general download page. The reason for putting on the test page is that the memory leak cleanout could have introduced problems with menus and screen handling, which cannot be tested here. Memory demand after running many commands could before rise to more than e.g. 200Mb is now down to around 15-20 Mb. Since release of v2.0 the test suite applied has been extended from 1749 tests to 1884 tests. The extension includes aspects such as further sorting and stratified results for a combination of variables and files. Please test as indicated and report here if you find problems Regards Jens Lauritsen EpiData Association ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 49, Issue 11 ********************************************

1 0

EpiData Analysis v2.0 Build 128 available
by epidata-list＠lists.umanitoba.ca 22 Nov '07

22 Nov '07

I just uploaded v2.0.1.128 on the page: www.epidata.dk/testing.php This build remedies as far as we can test here the problems shown since release of v2.0: - saving data files with automatic naming - odds ratios in stratified tables with more than two strata - memory leaks. Plan for current testversion: 1. Leave on testing.php page for a few days (3-4 days) 2. Move as current release on the general download page. The reason for putting on the test page is that the memory leak cleanout could have introduced problems with menus and screen handling, which cannot be tested here. Memory demand after running many commands could before rise to more than e.g. 200Mb is now down to around 15-20 Mb. Since release of v2.0 the test suite applied has been extended from 1749 tests to 1884 tests. The extension includes aspects such as further sorting and stratified results for a combination of variables and files. Please test as indicated and report here if you find problems Regards Jens Lauritsen EpiData Association

1 0

EpiData Entry: export filter
by epidata-list＠lists.umanitoba.ca 15 Nov '07

15 Nov '07

I am hoping someone knows the answer to the following question: I am trying to export a selection of records from an EpiData rec file using version 3.1 to an Excel file, based on a date field. For instance, to select all records earlier than the 14th of November 2007: dategiven < "14/11/2007" in the filter box, but this yields an error (not a boolean expression) and the field dategiven is a <ddmmyyyy> field. I also tried without quotes and using the date function, with and without the day, month, year functions with the same result. I dare say there is a simple way to do it, but I can't see it, so if anyone can help, I'd be most grateful. Regards, Neville ----------------------------------------- ************************************************************************** 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

Problems with APPEND in build 126 and 127
by epidata-list＠lists.umanitoba.ca 14 Nov '07

14 Nov '07

In Build 122 the following 3 commands in a pgm-file could be executed correctly. close read "c:\data\tz\test1.rec" append "c:\data\tz\test2.rec" In build 126 and 127 the You get a error "Invalid variable name C:\Data ....." when running the pgm-file. But if You execute each command separately the APPEND command works.as You can se from the following output. . read Loading data C:\Data\TZ\Test1.rec, please wait.. File name : C:\Data\TZ\Test1.rec Fields: 3 Total records: 6 Included: 6 . append Append rewritten - check result Loading data C:\Data\TZ\Test2.rec, please wait.. . list RecNo x y z 1 1 2 3 2 3 2 1 3 4 5 6 4 6 5 4 5 7 8 9 6 9 8 7 7 12 . . 8 13 . . 9 14 . . 10 15 . . Note browse is faster than list . run . close File closed . read "C:\Data\TZ\Test1.rec" Loading data C:\Data\TZ\Test1.rec, please wait.. File name : C:\Data\TZ\Test1.rec Fields: 3 Total records: 6 Included: 6 . append "C:\Data\TZ\test2.rec" invalid variable name C:\Data\TZ\test2.rec Operation aborted ------------------------------------------------------------------------ Stig Uhlin tel 090-786 60 71 Stig.Uhlin(a)umdac.umu.se UMDAC 070-591 03 04 901 87 Umeå fax 090-786 67 62 Jag jobbar numera 1/2 tid enl följande: jämna veckor onsdag-fredag udda veckor måndag-tisdag ------------------------------------------------------------------------

1 1

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

10 Nov '07

I will be out of the office starting 11/10/2007 and will not return until 11/13/2007. Regional offices are closed Monday November 12th. I would be happy to respond to your e-mail upon my return. Thank-you, Alyshia

1 0

EpiData Analysis - reported problems solved - build 127 uploaded
by epidata-list＠lists.umanitoba.ca 10 Nov '07

10 Nov '07

The reported problems in relation to b126 have all been solved. In addition the following changes have been implemented: dotplot : Now dots are symmetrical for each group command prompt: At initiation the command prompt is empty (was "read" before". For users wishing to get the "read" command without using a mouse the shortest way is by pressing F4 (goto command prompt) followed by "Up-Arrow" (shows the "read" command), followed by "Enter" (open file dialog). documentation: clarified. Still some of the extended help files could have v1.0 description of options etc. The download page now shows build and version next to the page, as well as there is also a zip file available containing the setup file. Thanks for reporting the problems. Part of the problem of the /SD etc discussed was, that the release build and a former test build had the same build number (b126) (by error), such that users could think they were having the same version, but actually did not. regards Jens Lauritsen EpiData Association

1 0

RE: Sorting of 2x2 tables (Oswego example discussion)
by epidata-list＠lists.umanitoba.ca 09 Nov '07

09 Nov '07

The problem of the /sd option in relation to tab ill cakes vanilla chocolate /oa /sd /ex versus tab ill cakes vanilla chocolate /oa /ex is related to how boolean variables are sorted. Currently in the version 2.0 released there is a bug in sorting of boolean 2x2 variables. The error will be fixed as soon as possible. For numerical variables coded 1/0 or 2/1 there is no problem. The reason I did not catch the boolean Y/N error is, that the tab command gives correct estimates for boolean as well as numerical variables: tab ill cakes vanilla chocolate /oa /ex But if the user adds the sorting (as was needed earlier) : tab ill cakes vanilla chocolate /oa /ex /sd reveals the bug. The way development is done is that before release a number of tests are made, currently around 1250, e.g. after the mentioned tabulation 24 tests were applied for the tabulation of oswego rr values with different options (but not the /sd) option. The oswego rr test has now been extended to cover this issue as well. (18 more tests). A given test can be like this using result variables: tab ill vanilla rolls /o assert samenum(round($OR*100)/100,22.15) assert samenum(round($ORLL*100)/100,5.22) assert samenum(round($ORUL*100)/100,138.39) assert samenum(round($OR1*100)/100,12.26) assert samenum(round($ORLL1*100)/100,1.76) assert samenum(round($ORUL1*100)/100,150.86) assert samenum(round($OR2*100)/100,38.19) assert samenum(round($ORLL2*100)/100,4.06) assert samenum(round($ORUL2*100)/100,1983.85) assert samenum(round($SumOR*100)/100,20.61) assert samenum(round($SumORLL*100)/100,4.93) assert samenum(round($SumORUL*100)/100,126.46) The "hidden" bug arising by the sort option is a good example of why many tests are needed, but I think also that it shows that even with a number of test releases the policy of "silent release" is appropriate. regards -- Jens Lauritsen Coordinator and initiator of EpiData Project http://www.epidata.dk

1 1

Congratulations to all epidemiologist and THANKS to Jens
by epidata-list＠lists.umanitoba.ca 08 Nov '07

08 Nov '07

Dear all, The new version is wonderful. I have the oportunity to make a demo at the begining of this year to a cohort of EPIET fellows. They were using Stata and when they saw EPiData Analysis doing the, them a draft version yet, of tables ..... /oa and epicurve. They got completly breath taken I think Jens deserves all our acknowledge Pedro

1 0

Analysis V2 - Congratulations
by epidata-list＠lists.umanitoba.ca 08 Nov '07

08 Nov '07

Although there are a few minor bugs, these will usually be very obvious and only in the unusual situation. My quick testing on favourite troublesome data sets shows this is a great release. If you know anyone working on outbreak investigations who has not seen Analysis, do them a favour and show them how to do the following on the OSWEGO.REC data: tab ill cakes vanilla chocolate /oa /ex gen i onset=(onsettime div 100) + iif(onsetdate = "04/19",24,0) epicurve onset ill You will make someone very happy, I'm sure. Many of us working in the field have been waiting for something as simple as this (I have been waiting over 25 years). Sure, you could almost do this in EPI6, but only with a lot of advanced knowledge - and forget the exact test except as table by table. Many thanks to Jens & team!! Jamie Hockin Public Health Agency of Canada

1 2

Chris Sellers/FHS/ADPH is out of the office.
by epidata-list＠lists.umanitoba.ca 06 Nov '07

06 Nov '07

I will be out of the office starting 11/05/2007 and will not return until 11/13/2007. I will check emails periodically while I am away. If an issue needs immediate attention, please, contact Fred Grady at FredGrady(a)adph.state.al.us or 1-800-338-8374. Otherwise, I will respond to your email when I return.

1 0

Re: EpiData Analysis - first "silent" non-test release
by epidata-list＠lists.umanitoba.ca 05 Nov '07

05 Nov '07

The bugs in Chi Square values in stratified analysis of 2x2 tables and the correlation command error reported today has been solved. Therefore a first version v2.0 for analysis placed on the general download page. The work continues solving minor problems only affecting special situations, such as percentiles with small numbers of observations (n=10-25) or final adaptation of all help documents to the new options. Only the general help file has at this point been uploaded. When all of these points have been settled a general announcement will be made. This is expected to take 1-2 weeks. Thanks to many users for testing and commenting. regards Jens Lauritsen EpiData Association

1 0

CORRELATE command
by epidata-list＠lists.umanitoba.ca 05 Nov '07

05 Nov '07

Dear Jens, After years of hard work you have brought Epi Analysis to the current status. There are almost all the features of EPI6 and much more. Apart from the pending issues you have outlined, I wanted to draw your kind attention to CORRELATE command (build 126). According to the HELP file, correlate var1 var2 [var3 ...], it should work.. When I run this command, the following happens; table design=box . CORRELATE V1 V2 Invalid floating point operation Probably some thing is wrong in the syntax I am attaching a small sample corr.rec file. Please help. Waiting for the release of this marvelous software. With regards, Dr. Shavinder Singh

1 0

EpiData Analysis - status release candidate
by epidata-list＠lists.umanitoba.ca 04 Nov '07

04 Nov '07

Three aspects needs clarification and further exploration : 1 Chi Square values in stratified analysis of 2x2 tables 2 Saving datafiles with "Epi6 naming convention". Only "First Word" works completely. 3 Percentiles have problems with small numbers of observations Except for these three problem areas I think all major issues have now been solved. The table command syntax has been simplified to: tables ........ (default) will do stratified analysis or a n*k table. tables ....... /oa will create a condensed outbreak table with attack rates and rr tables ........ /cc a condensed table with odds ratios tables ....... /fv will do a "first against all other variables", but currently is limited to 2x2 tables It is my intention to release current as a "silent starter" for v2. By silent I mean without a lot of news due to the limitations mentioned above. A warning is given when the analysis commands (tables, describe, stattable) affected by the problems are used. I expect the problems to be solved within about a week or two at most. The reason for the "silent release" is that some courses are due, which do not use these commands. What could change my decision of release as is would be strong disagreement from users on this list. Please discuss, but if no major concerns show up, the release will happen tomorrow. regards Jens Lauritsen EpiData Association

1 0

Almost final EpiData Analysis v2.0 placed for testing
by epidata-list＠lists.umanitoba.ca 27 Oct '07

27 Oct '07

Two aspects needs clarification and further exploration : 1 Chi Square values in stratified analysis of 2x2 tables 2 Saving datafiles with "Epi6 naming convention". Only "First Word" works completely. After finding the cause for the CHI Square problems and final testing of MERGE command it is my intention to release current test build as first v2.0 of EpiData Analysis. Among the latest changes are implementation of a MERGE command, which replaces relate in analysis and removal of more or less all reported major problems on the Mantis system. Some wishes are still there, but will be looked at later. The MERGE command is a replacement for relate. An example: read patients rename name to ptname merge surgeon /file=surgeon /table rename name to surgname merge hospid /file=hospital /table rename name to hospname the /table option makes sure, that several patients can get information from one record in the hospital or surgeon file. "Table lookup". Without the /table option, the key must be unique in the files. A key consists of the variables (as many as you like, e.g. sex age city) mentioned after the merge command. Notice that the file to merge now must be given with the /file parameter. Users finding problems please discuss here or for definite errors report to the Mantis database. See www.epidata.dk/testing.php Kind regards Jens Lauritsen

1 0

Specification of output in EpiData Analysis version 2
by epidata-list＠lists.umanitoba.ca 18 Oct '07

18 Oct '07

Shavinder Sing attached a larger html file (77kb) and asked : ........................................ The Htm output file of Epi Analysis (build 122) behaves differently from the other htm files. I tried opening one htm file (after running a PGM in the Epi Analysis) in the Open Office 2.2, 2.3 (Writer) and Microsoft Word 2000, 2003, 2007. The data figures are visible. The outline of the tables is faintly visible in the white background. In the print out only data figures are visible, not table outline One has to individually select and choose the appropriate table outline from the table properties box (which is quite tedious for long reports). Is there any solution? I set table design=box. I also tried looking into the “epiout_w for any hint but no luck. Is it not possible to have the same table output for printing, as it is visible in the Epi Analysis window after generating the report? With regards, Dr. Shavinder Singh ........................................ I rejected the mail, since we do not want large attachments (some users are using slow modem lines). But the question is relevant. The output definitions in EpiData Analysis conforms to W3C standards of html and requires also knowledge of the use of css style sheets. The definitions and further description of how to handle this can be found in the document: http://www.epidata.dk/php/downloadc.php?file=epidata_analysis_output_defini… The problem of the lacking frames described is related to the use of style sheets, which are files describing output. For use of output in external browsers users should experiment with: a. copying the style sheet files to an appropriate place b. including the style sheet information in the output file. These two set commands: set STYLE SHEET "D:\EPIDATASTAT\TEST\EPIOUT.CSS" set STYLE SHEET EXTERNAL ON/off Simply: set style sheet external=off will secure that all styles are defined in the html output file. Jens Lauritsen EpiData Association

1 0

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

13 Oct '07

I will be out of the office starting 10/13/2007 and will not return until 10/17/2007. If you require immediate assistance, please contact Stephen Drew at extension 5330. Thank-you, Alyshia

1 0

providing learning materials for EpiData
by epidata-list＠lists.umanitoba.ca 13 Oct '07

13 Oct '07

As noted by Pedro Emmanuel regarding material in Portuguese the policy from my side is to provide links next to the translations for materials in the different languages on the main epidata.dk download page. It is difficult to maintain the links if they change often. To assure that all links are up to date at all times the most efficient way is to have a link to a webpage and not to a particular file. The latter changes every so often, whereas the overall - e.g. institutional site - changes rarely. All users are encouraged to locate any link errors on the epidata.dk pages and inform me directly via the mail info at epidata.dk. I tend not to disclose my personal email, since spamming soon then gets a major problem. The main mail will inform of large spam problems, but if you add "EpiData educational material" to the subject that mail should come through. On the wikipedia site I have added an entry for epidata. After some finetuning of the wikipedia by some of the administrators from wikipedia, there is now a short and rather clear text. See http://en.wikipedia.org/wiki/Epidata It could be an idea if users translate that same page for some of the "other than english" versions of wikipedia. I am not sure of the way to do so, but look in the Wikipedia site for instructions. You will notice that the wikipedia text refers to EpiData Wiki at www.epidata.org/wiki. The EpiData wiki is among other aspects on the agenda for a meeting taking place this weekend in Canada, where closer involvement of Canadian epidemiologists in the development of EpiData will be discussed. More news on this exciting event will follow next week. I expect to give within 1-2 weeks the final announcement of release of EpiData Analysis v2.0. With a few more aspects to settle the test version is almost ready. Information will be given here and to all registered users when this takes place. Regards Jens Lauritsen Coordinator , EpiData Association

1 0

Chris Sellers/FHS/ADPH is out of the office.
by epidata-list＠lists.umanitoba.ca 12 Oct '07

12 Oct '07

I will be out of the office starting 10/12/2007 and will not return until 10/23/2007. I will check emails periodically while I am away. If an issue needs immediate attention, please, contact Fred Grady at FredGrady(a)adph.state.al.us or 1-800-338-8374. Otherwise, I will respond to your email when I return.

1 0

Records marked as deleted
by epidata-list＠lists.umanitoba.ca 12 Oct '07

12 Oct '07

I am trying to use EpiData to validate duplicate files that have been entered into SPSS. I have tried saving them as dBASE III and dBASE IV files (which save only the first 128 or 256 variables respectively) and have up to 417 cases. When I open the .dbf files via SPSS, an additional column labeled D_R is included in the file. In this variable, an asterisk indicates that the record has been marked for deletion and, based on what I understand about transferring to EpiData, anything with such marking will be considered deleted but not purged. When I check the file in SPSS, no files are marked as deleted. However, when I import the file into EpiData, some of the records are - seemingly randomly - marked as deleted. I am wondering if anyone knows why this happens or what I can do to stop it. Thanks. - Amy

1 0

Leraning Material in portuguese
by epidata-list＠lists.umanitoba.ca 11 Oct '07

11 Oct '07

Hello all epidata friends, Early in this yaer I have make it avaible in the web a lerning material in portuguese wich was placed a weblink in the epidata webpage nearby the download of the portuguese version. Since I do not control the webpage and the link was a FTP in a web serverver I cant even tell if many or few have accessed the file. During this year, the teaching coordinator of our institute, facing regulatory rules asked us to put all the lerning/teching materials in a diferent place. So, the same material (which I intend to update only next year) are now at both old (first) and new (last one) weblink. Sometime in the future, probably the old one will not work anymore. The only diference between them is that the webmaster of new adress put a open code to download the file. This procedure seems to avoid automatic download of all files available at the same time and overflow the server. http://www.ipec.fiocruz.br/materialdidatico/Aplicativos_pesquisa/2007/EpiDa… http://157.86.40.74/pos/modules.php?name=Downloads&op=getit&lid=24 I hope those speak portuguese may not have any difficulties to acces if necessary. -- Abraço forte e que a força esteja com você, Pedro Emmanuel

1 0

Backup error solved
by epidata-list＠lists.umanitoba.ca 05 Oct '07

05 Oct '07

Problem solved when a did not use my new USB 2.0 flashdisk. Nikolai Stenfors

1 0

Backup error
by epidata-list＠lists.umanitoba.ca 04 Oct '07

04 Oct '07

I moved my Epidatafiles from a computer running on WinXP to a laptop with Win Vista. Now I cannot do backup. Error message "invalid filename". Epidata incompability with Vista? Nikolai Stenfors

1 0

Epidata Analysis b122 available for testing
by epidata-list＠lists.umanitoba.ca 02 Oct '07

02 Oct '07

These weeks several problems and clarifications have been made on the "road" to release finally EpiData Analysis as v2.0 Some aspects are still insufficiently final, but the level of changes are going into "corner" details from my point of view. As of build 122 some aspects have been fixed: e.g. - EpiDemiological tables (odds ratios, rr and attributable risk) will use highest value of case and exposure variables as default. - A new table dialog has been a success in my personal teaching. Quite clearly beginners adapt much faster when having proper (intuitive) dialogs. - Sorting of frequency tables by numbers - More graph types can now be used with a "group variable", e.g.: box age /by=sex - Many more subtle details have been fixed. Many of these are invisible to the end-user, but clarification makes the whole programme more stable. This will also allow shorter development time for future new commands and additions. Some issues are still creating problems, such as: - internal errors after kruskal-wallis tests. - parts of relate system not working for some files - creating more intuitive dialogs for remaining parts of the system - removing reported bugs (see mantis system). Some users might find it odd that new problems arise, but this is due to the rewriting of core parts. And consequential changes in other parts of the software take some time to find, if they are not pinpointed by the error tracking system. This system is a collection of pgm files doing all verifying results and function in all parts of the programme. Usually when a new error is reported it is due to not being tested for in the error tracking system. The system is now based on 41 pgm files with around 1150 different conditions being tested and verified. Version 2 will not be released before all of the consequences of the rewriting of core parts has taken place. But as could be stated on the www.epidata.dk/testing.php page : "Many of the functions are running and functioning very well, so after each user has verified the function of what he/she uses there is no problem in using the test versions." E.g. the table module has no known errors just now. Kind regards Jens Lauritsen EpiData Association

1 2

A bug of epidata
by epidata-list＠lists.umanitoba.ca 11 Sep '07

11 Sep '07

To any concern, I think that I have found a bug of epidata when I want to export the data from epidata to sas. The content of .qes file: This is a example! The {first} text field: __________ The {second} text field: ________________________________________________________________________________ The {third} text field: ____________ The content of .sas file which is generated by epidata. * EpiData created two files by exporting * D:\statistics\temp\epidata bug\bug.rec * * 1. D:\statistics\temp\epidata bug\bug.sas * is the SAS command file * 2. D:\statistics\temp\epidata bug\bug.txt * is an ASCII text file containing the raw data. * * You may modify the command file before submitting them. ; DATA bug(LABEL="a bug of epidata"); INFILE "D:\statistics\temp\epidata bug\bug.txt"; INPUT FIRST $ 1-10 / SECOND $ 1-80 THIRD $ 1-12; LABEL first="The first text field:" second="The second text field:" third="The third text field:"; run; The conten of .txt file which is also generated by epidata: a b c d e f When I run the .sas file in sas, the log window showed that: NOTE: The infile "D:\statistics\temp\epidata bug\bug.txt" is: File Name=D:\statistics\temp\epidata bug\bug.txt, RECFM=V,LRECL=256 NOTE: LOST CARD. FIRST=f SECOND= THIRD= _ERROR_=1 _N_=4 NOTE: 9 records were read from the infile "D:\statistics\temp\epidata bug\bug.txt". The minimum record length was 10. The maximum record length was 80. NOTE: SAS went to a new line when INPUT statement reached past the end of a line. NOTE: The data set WORK.BUG has 3 observations and 3 variables. NOTE: DATA statement used (Total process time): real time 0.18 seconds cpu time 0.07 seconds I can get the dataset 'bug' in work library. But it is not what I want. Now I can resolve the problem. I need modify the .sas file. The file which is modifed is listed below: * EpiData created two files by exporting * D:\statistics\temp\epidata bug\bug.rec * * 1. D:\statistics\temp\epidata bug\bug.sas * is the SAS command file * 2. D:\statistics\temp\epidata bug\bug.txt * is an ASCII text file containing the raw data. * * You may modify the command file before submitting them. ; DATA bug(LABEL="a bug of epidata"); INFILE "D:\statistics\temp\epidata bug\bug.txt"; INPUT FIRST $ 1-10 / SECOND $ 1-80 / THIRD $ 1-12; LABEL first="The first text field:" second="The second text field:" third="The third text field:"; run; The 'second' field caused the trouble. The 'second' field's width is 80. I hope someone can fix it. All the files is attached. You can have a try.

1 0

Re- LIST Command
by epidata-list＠lists.umanitoba.ca 03 Sep '07

03 Sep '07

Dear Jens, Thanks for the quick response. I will share my bit on the wiki. Regarding the BROWSE and LIST command message, I was not able to get the output of list command. My programmer found out the solution. We could solve the LIST command problem by SET ECHO=ON. When SET ECHO=OFF, the LIST command is also turned off. If it was supposed to be like that, please include this in the documentation. With regards, Dr. Shavinder Singh

1 0

Issues on EpiData Analysis - list etc.
by epidata-list＠lists.umanitoba.ca 03 Sep '07

03 Sep '07

Shavinder Sing suggested that ..... If each of us writes the documentation of ONE command with example, our command reference can be really exhaustive and useful like EPI6 manual. .... is very appropriate. The idea of a user based documentation centre is exactly the idea of the wiki principles, where everyone can add whatever is possible for them. I expect that a common base wiki will be ready within 6-12 months. Just now the following can be of immense importance: a. Anyone having good examples for distribution consider adding these to the experimental wiki now placed at www.epidata.org/wiki b. Consider writing documents in the form of "how to ...." and make a collection available from a local site, which can then be linked from the main site. c. Make sure that everyone registers for news from EpIData Association, since the number of persons registering there is the only "proof" of usage we have when arguing with authorities that the effort is truly a non-profit international effort. Every so often some discussions come up here in which until now it has been very important to be able to show the large number of registered users. Regarding the "LIST and BROWSE commands are not exactly replaceable." - this is true. I do not understand however why the function of list is not sufficient. There is a deficiency in list not being able to show "value labels", but apart from that I do not see any deficiencies - except that the output window is slow with large amounts of output. Possibly I do not understand the "...kindly preserve the functionality of LIST command as it was in EPI6. " For inspiration of a collaborative effort I suggest everyone to look at the website course developed as part of a number of courses run under the "wings" of IUATLD Union (see www.iuatld.org) by Hans L. Rieder, presented at "http://www.tbrieder.org/epidata/course.htm". The contents have been developed by the "EpiData Promotors" (http://www.tbrieder.org/epidata/epidata_promoters.htm) with some substantive solutions from me. The courses have also influenced the contents of commands and other parts of the Epidata Software. regards Jens Lauritsen EpiData Association

1 0

Thank and LIST command
by epidata-list＠lists.umanitoba.ca 02 Sep '07

02 Sep '07

Dear Jens, Release of build 118 is good news. Thanks you for this wonderful software. In the last few weeks, I had posted 3 queries on the list; a. Command Set replace logfile=on b. Incomplete execution of PGM c. Relational Files Relate error. Problem a could be solved by the erase command. You solved the problem b by suggesting the use of IMIF command along with If then. You solved problem c in the build 118. Jamie had also helped to clarifying the issue. My gratitude to you and Jamie. May I suggest the following? 1. There is a large Epidata Entry and Analysis user base now in many countries. Most of us are past users of EPI6 and have graduated to Epidata thankfully. If each of us writes the documentation of ONE command with example, our command reference can be really exhaustive and useful like EPI6 manual. Of course this will be massive editing job for Epidata team. There are many queries still concerned with the commands. If we were not contributing financially, at least this much effort would save some resources for the Epidata Team. If this idea appeals to you, I am willing to do my bit. 2. LIST and BROWSE commands are not exactly replaceable. BROWSE command is meant for visualizing the data only, while LIST command can actually print the list of records with selected variables in the output file. Build 118 releases LIST command only lists the list of single variables after query. If possible, kindly preserve the functionality of LIST command as it was in EPI6. With regards, Dr. Shavinder Singh

1 0

New test build 118 for EpiData Analysis
by epidata-list＠lists.umanitoba.ca 31 Aug '07

31 Aug '07

Yesterday I uploaded a new test build for analysis, now build 118. Since previous test build many internal parts have been rewritten, such that the source code is the same where possible for analysis, entry and epic. Most of this is invisible to the end-user, but assures that e.g. chk files are read the same way in the systems. A few aspects remain btw. the products. e.g. naming of integer function int() versus integer(). Of particular interest to the end-user is the following: Practical: a. A new table dialog makes it easier (hopefully) to use the possibilities in the new table command without using the command prompt. The table dialog is available from the toolbar or as a command tabdialog. b. Graphs can now be made by a group variable. e.g. box age /by=sex will create two boxes for two values of sex c CHK files are now saved with the data. Including definitions of variable labels and missing values. d When looking at a table or graph in output, rightclicking with the mouse copies that table or graph to clipboard. (for tables sometimes there is a pointer error, but this will be fixed). Technical issues: a. No new functionality will be added before release as public v2.0 except for translation, which is about half way implemented. b. Bugs should be removed before releasing. - some issues are known and will be documented in the Mantis database c. We should decide what to do about text strings in rec files, which are found in the qes files, but not read into analysis. d. Translation for analysis is about half way e. the Mantis system is not completely updated, but this should take place within about a week to reflect what was fixed and what remains. f. There are still some minor estimation problems, such as percentiles not being correct with very small samples (e.g. n<15). Regards to all -- Jens Lauritsen Coordinator and initiator of EpiData Project http://www.epidata.dk

1 0

Re: [EpiData-list] Re: Ranked variable questions
by epidata-list＠lists.umanitoba.ca 26 Aug '07

26 Aug '07

You are right Jamie - a response of 1 was given for most imporant. I will try using your v1=10-v1 and then the method Jens suggests. thank you very much to both you and Jens for your help Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 >>> <epidata-list(a)lists.umanitoba.ca> 24/08/2007 1:33 p.m. >>> An important question is whether a response of 1 most important or least important? If 1 is most important, then make the default value 11 and not zero. I would just do: describe v1-v25 and scan the medians to find those with the lowest median (if 1 is most important and default is 11) or highest median (10 is most important and default is 0). Items that are infrequently ranked will have a median equal to the default. Items most frequently ranked will have a median that is based mostly on ranks. I haven't thought about the formal statistical analysis here, but you'll get a pretty good assessment. Jens approach works very well when the most important response is 10. If most important is 1, then you can also do this: v1 = 10-v1 v2 = 10- v2 etc and use aggregate. jamie > Christine wrote: > I have been asked to set up a database for a questionnaire that has > already been written. I was going to set it up in epidata but my > problem is how to deal witha question that asks people to rank > options. The question gives a list of topics and asks the person > filling in the questionnaire to rank them from 1-10 in order of > importance. > Jens wrote: > I suggest to do the following: > For each question (say 25 different themes) enter the priority the > person gave to that issue. > setup the qes: > v1 item1 ..... ## > v2 item2 ..... ## > etc > v25 text for item 25 ## > > in chk make the defaultvalue 0: > before file > DEFAULTVALUE v1-v25 0 > end > > Then in analysis after entering the data: (say you had the 25 variables) > read response > aggregate /sum="v1,v2,v3,v4,v5" > aggregate /sum="v6,v7,v8,v9,v10" etc > > * the tables will show the sum of the variables, that is the overall > ranking sum. > -- 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

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

24 Aug '07

I will be out of the office starting 08/24/2007 and will not return until 08/28/2007. If you require immediate assistance, please contact Stephen Drew at extension 5330.

1 0

Re: Ranked variable questions
by epidata-list＠lists.umanitoba.ca 23 Aug '07

23 Aug '07

Christine wrote: I have been asked to set up a database for a questionnaire that has already been written. I was going to set it up in epidata but my problem is how to deal witha question that asks people to rank options. The question gives a list of topics and asks the person filling in the questionnaire to rank them from 1-10 in order of importance. I suggest to do the following: For each question (say 25 different themes) enter the priority the person gave to that issue. setup the qes: v1 item1 ..... ## v2 item2 ..... ## etc v25 text for item 25 ## in chk make the defaultvalue 0: before file DEFAULTVALUE v1-v25 0 end Then in analysis after entering the data: (say you had the 25 variables) read response aggregate /sum="v1,v2,v3,v4,v5" aggregate /sum="v6,v7,v8,v9,v10" etc * the tables will show the sum of the variables, that is the overall ranking sum. example read bromar // example data set for epidata aggregate /sum="dectime,km,age" which gives the output: N Ndectime SUMdecti1 Nkm SUMkm Nage SUMage 4027 3556 13913.85 3620 381084.00 3786 153740 telling us: 4027 observations in all of these 3556 contributed to dectime, 3620 to km and 3786 to age variables. Sum of the three being 13913.85, 381084.00 and 153740 Obviously here the sum makes no sense, but in your case the sum of the ranking would reflect all of the variables and the responses. regards Jens Lauritsen EpiData Association ps. I tried to locate the user sending spam to the list today/yesterday and may effectively have deleted this person from the list (if not we will see more of the same spam) - terribly annoying.

1 1

Réponse automatique d'absence du bureau : [EpiData-list] FW: Fw: Fw: Doorst.: FW: Read & Respond
by epidata-list＠lists.umanitoba.ca 23 Aug '07

23 Aug '07

Bonjour, Je suis actuellement absent du bureau.Je serai de retour le 3 septembre 2007 Je répondrai à cette date à votre message A bientôt Hello, I am currently out of the office and will be back on September the 3rd, 2007 I will reply to your message then. All the best Robert

1 0

FW: Fw: Fw: Doorst.: FW: Read & Respond
by epidata-list＠lists.umanitoba.ca 23 Aug '07

23 Aug '07

> -----Ursprüngliche Nachricht----- > Von: "B. Wiedemann" <x-72(a)gmx.de> > Gesendet: 23.08.07 09:24:18 > An: christopher.bohn2(a)travedsl.de, ilsa.ramm(a)gmx.de, b-loewe(a)web.de, m.siebelts(a)email.de, lottaleben(a)atomstromfrei.de > Betreff: Fwd: Fw: Fw: Doorst.: FW: Read & Respond -------- Original-Nachricht -------- > Datum: Thu, 16 Aug 2007 07:49:53 +0200 > Von: "Jochen Fölsterprivat" <jochen.foelster(a)foefi.de> > An: "Yvonne Moutoux" <Moutoux(a)gmx.de>, "tina johanssen" <tina_johanssen(a)yahoo.de>, "michelle" <michelle.sachs(a)gmx.net>, "Beate x-72" <x-72(a)gmx.de>, "Aljonna" <aljonna(a)foefi.de>, "aareinhild" <reinhild.fragel(a)foefi.de> > Betreff: Fw: Fw: Doorst.: FW: Read & Respond > ----- Original Message ----- From: <Grunigrunewald(a)aol.com> > To: <airoff2(a)ham.airport.de>; <Almuth.Hanke(a)gmx.de>; <McClouds(a)Collie.de>; > <chengizkaan2004(a)hotmail.com>; <Doris.Steiner(a)sparkasse-stormarn.de>; > <jochen.foelster(a)foefi.de>; <Katfoel(a)aol.com>; <knebel(a)esenet.dk>; > <mail(a)jenskohnert.de>; <koschoe(a)de.ibm.com> > Sent: Wednesday, August 15, 2007 10:51 PM > Subject: Fwd: Fw: Doorst.: FW: Read & Respond > > > > > > > > > > > > > -- GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS. > Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail > > ----------------------------------------------------------------- > > > > ----- Original Message ----- > From: esther > > To: Dirk Huizinga > > Cc: frank ; ilonka ; Jacquie Smilde ; karolina bonefaas ; Peter ; Sandra Koegler-Lieshout ; W.G. Schönhage > > Sent: Wednesday, August 15, 2007 12:42 PM > > Subject: Doorst.: FW: Read & Respond > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Read this...I mean REALLY read this > > > > > > > > > > This is without a doubt one of the nicest good luck forwards I have received. Hope it works for you -- and me! > > > You have 6 minutes > > > There's some mighty fine advice in these words, even if you're not superstitious. This has been sent To you for good luck from the Anthony Robbins organization. It has been sent around the world ten times so Far. > > > Do not keep this message. > > > This must leave your hands in 6 MINUTES. Otherwise you will get a very unpleasant surprise. This is true, even if you are not superstitious, agnostic, or otherwise faith impaired. > > > > > > > ONE. > > > Give people more than they expect and do it cheerfully. > > > TWO > > > . Marry a man/woman you love to talk to. As you get older, their conversational skills will be as important as any other. > > > THREE. > > > Don't believe all you hear, spend all you have or sleep all you want. > > > FOUR > > > . When you say, "I love you ," mean it. > > > FIVE. > > > When you say, "I'm sorry," look the person in the eye. > > > SIX > > > . Be engaged at least six months before you get married. > > > SEVEN. > > > Believe in love at first sight. > > > EIGHT. > > > Never laugh at anyone's dream. People who don't have dreams don't have much. > > > NINE > > > . Love deeply and passionately. You might get hurt but it's the only way to live life completely. > > > TEN. > > > . In disagreements, fight fairly. No name calling. > > > ELEVEN > > > . Don't judge people by their relatives. > > > TWELVE. > > > Talk slowly but think quickly. > > > THIRTEEN > > > . When someone asks you a question you don't want to answer, smile and ask, "Why do you want to know?" > > > FOURTEEN > > > . Remember that great love and great achievements involve great risk. > > > > FIFTEEN. > > > Say "bless you" when you hear someone sneeze. > > > > SIXTEEN > > > . When you lose, don't lose the lesson ! > > > SEVENTEEN > > > . Remember the three R's: Respect for self; Respect for others; and responsibility for all your actions. > > > EIGHTEEN. > > > Don't let a little dispute injure a great friendship. > > > NINETEEN. > > > When you realize you've made a mistake, take immediate steps to correct it. > > > TWENTY. > > > Smile when picking up the phone. The caller will hear it in your voice > > > > TWENTY-ONE. > > > Spend some time alone. > > > > Now, here's the FUN part! > > > Send this to at least 5 people and your life will improve. 1-4 people: Your life will improve slightly. > > > 5-9 people: Your life will improve to your liking. > > > 9-14 people: You will have at least 5 surprises in the next 3 weeks > > > 15 and above: Your life will improve drastically and everything you ever dreamed of will begin to take shape. > > > A true friend is someone who reaches for your hand and touches your heart. Do not keep this message > > > > > > ********************************************************************************************************* > > > > > > > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.5.476 / Virus Database: 269.11.11/944 - Release Date: 9/08/2007 2:44 p.m. > > > ----------------------------------------------------------------- > Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! Try it! > > > > > > > > > > > > > > > > > > > > >

1 0

Ranked variable questions
by epidata-list＠lists.umanitoba.ca 23 Aug '07

23 Aug '07

Hello everyone I have been asked to set up a database for a questionnaire that has already been written. I was going to set it up in epidata but my problem is how to deal with a question that asks people to rank options. The question gives a list of topics and asks the person filling in the questionnaire to rank them from 1-10 in order of importance. (It is for a city council and they want to know what young people are most concernred about so the choices are crime, employment, environment etc). I thought in the qes I could just make a variable for each topic and enter the number the respondent puts beside it, but I don't know how to then analyse the answers, so I can find out what the top 10 issues are overall. If anyone has done this before and can offer a suggestion I would be grateful 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

Re: Incomplete execution of PGM due to no observations in a select
by epidata-list＠lists.umanitoba.ca 20 Aug '07

20 Aug '07

Just add "IMIF" in each select group: (here shown with one group): TYPE "\LTABLE SHOWING ILLNESS IN THE SES CLASS 2" SELECT SES=2 count /q * in the next line we use a resultvariable called $count: * resultvariables are shown with the command "result" imif $count > 0 then TABLES SEX ILLNESS else type "No observations" endif Select Regards Jens Lauritsen EpiData Association

1 0

Incomplete execution of PGM
by epidata-list＠lists.umanitoba.ca 20 Aug '07

20 Aug '07

Dear All, I am bringing to your kind attention one more and last problem. Hopefully this will be looked into before the release of ver 2 of Epidata Analysis. I have a sample database of distribution of illness according to the socio- economic status in the population. The socio- economic status is divided into 1,2 and 3 classes. The sample SES.pgm is listed below.. *SES.PGM CLS CLOSE SET ECHO=OFF READ "D:\EPIDATA\SES\SES.REC" TYPE "\LTABLE SHOWING ILLNESS IN THE SES CLASS 1" SELECT SES=1 TABLES SEX ILLNESS SELECT TYPE "\LTABLE SHOWING ILLNESS IN THE SES CLASS 2" SELECT SES=2 TABLES SEX ILLNESS SELECT TYPE "\LTABLE SHOWING ILLNESS IN THE SES CLASS 3" SELECT SES=3 TABLES SEX ILLNESS SELECT *END OF PGM When I run the PGM, following output is generated. TABLES SHOWING ILLNESS IN THE SES CLASS 1 Sex Illness F M Total N 2 1 3 Y 0 3 3 Total 2 4 6 TABLES SHOWING ILLNESS IN THE SES CLASS 2 No data! Operation aborted Since there is no data in the socio-economic class 2, the PGM aborts the operation. The rest of the PGM is not processed. I am attaching a sample SES.ZIP containing the necessary qes, chk and rec files. The latest test ver 2 (build 112b) of Epi Analysis was used. If this feature is looked into, large PGMs can be run without sny break. Is there any solution of this problem? Dr. Shavinder Singh

1 0

reuse labels in several files
by epidata-list＠lists.umanitoba.ca 17 Aug '07

17 Aug '07

epidata-list-request(a)lists.umanitoba.ca wrote: > Often, one uses questionnaires where the items and a value labels might > be identical for dozens or more questions. It seems that EpiData creates > a block in the .CHK file that applies to one variable only. Is there a > way to apply the same checks and labels to several variables at the same > time? > Technique 1: Common label definitions in EpiData.LBL. When you start EpiData Entry there is a default label collection. If you often use the same labels then edit the file EpiData.lbl which you will find in the same folder as the EpiData Enter system (epidata.exe) installed. Then for a given new file create the rec file and in the Enter system use "Add/revise" to add checks to the file. a Go to the first of the variables which should have a given label b. Choose from the list of your predefined labels contained in "Epidata.lbl" and read into the definition box. c. Now switch back to the field in question (F6 goes from the definition box to the field and vice versa). d. Press Ctrl+C e. Move the cursor to each of the other fields and press Ctrl+V and the definition is copied. It takes very short time. If you are thing instead of missing values etc. look in the help file: MISSINGVALUE Missing value has three syntaxes: MISSINGVALUE x [y [z]] which can be used in fieldblocks, and MISSINGVALUE ALL x [y [z]] which can be used in BEFORE FILE blocks, and MISSINGVALUE field1-field5, field6 …. x [y [z]] which can be used in BEFORE FILE blocks You see that in this case you can use syntax similar to Stata x-y . But for labels the trick above is the only possible. Technique 2: automatic revise of a larger file for subsets: The other technique to use is to create a common (large) file with all relevant questions, properly labelled. Then for a given substudy do: 1. create copies of the common large rec file and associated chk file 2. create copy of qes file 3. edit the qes file and delete sections not currently needed. 4. choose the rec file for entering data. Enter will "see" that the qes file has a more recent date and time and will suggest to adapt the structure to the qes file. Say yes to this and you will see that a number of no longer used variables will be removed including the chk for those. In terms of the analysis programme the issue is somewhat different, but I read the question as being relevant for entry. regards Jens Lauritsen EpiData Association

1 0

Epidata: apply the same value labels and validity checks to many variables
by epidata-list＠lists.umanitoba.ca 17 Aug '07

17 Aug '07

Hi, Often, one uses questionnaires where the items and a value labels might be identical for dozens or more questions. It seems that EpiData creates a block in the .CHK file that applies to one variable only. Is there a way to apply the same checks and labels to several variables at the same time? I appreciate that one can go into a text editor and copy the block as many times as necessary and then changing the variable names. it would be great if one could use syntax similar to SPSS or Stata where information can be applied to a variable list such as VAR001-VAR010 the same way it is applied to individual variables. Thanks! John LeBlanc __________________________________________________________ John C. LeBlanc, MD, MSc, FRCPC Associate Professor Pediatrics, Psychiatry, Community Health and Epidemiology Dalhousie University IWK Health Centre Work phone: (902) 470-8930 5850 University Avenue Work fax: (902) 470-6913 Halifax, Nova Scotia Email: John.LeBlanc(a)Dal.Ca B3K 6R8 CANADA Pager: (902) 470-8888 __________________________________________________________

1 1

Relational Files Relate Error
by epidata-list＠lists.umanitoba.ca 14 Aug '07

14 Aug '07

Dear All, I have a relational database comprising of 8 data entry forms. The structure is as follow; FFNO FAMIDNUM CARD Family --------------- Ecouple ----------------------- Under5 ------ Growth Monitoring form | | | | | FFNO | CSNO | | | | Agesex Form Contraception The field names in capital are unique key fields for relating the form during data entry. When I relate Growth Monitoring form Under5 form, the relating happens. When I relate Under5 Form with Ecouple the following message is displayed. Loading data D:\EpiData\Try\Gm.rec, please wait.. Excluded: 1243184 records marked for deletion File name : D:\EpiData\Try\Gm.rec Growth Monitoring Register Fields: 9 Total records: 6 Included: 6 . relate card UNDER5 Loading data D:\EpiData\Try\UNDER5.REC, please wait.. Excluded: 1243148 records marked for deletion File name : D:\EpiData\Try\UNDER5.REC . relate FAMIDNUM Ecouple Loading data D:\EpiData\Try\Ecouple.REC, please wait.. Excluded: 1243148 records marked for deletion 1 4218388 The relation happens only up to 2 forms only. What is meant by the error message 1 4218388 Is there any way out. I am doing it through EPI6 at present which does it seamlessly. Do we still have development issue regarding RELATE command in the Epidata Analysis (Ver 2 Build 112b). I am attaching this sample database in the form of CHC ZIP. Please enlighten upon this problem. Sincerely, Dr. Shavinder .

1 1

EpiData-list Digest
by epidata-list＠lists.umanitoba.ca 14 Aug '07

14 Aug '07

Hello, Two questions : - in the last version (build 122), how to obtain the same result with "set table label = on/ff" than anterior versions ? - in the further versions, is it possible to obtain a box-plot with two or more co-variables ? Thank you B. Branger, Nantes, France

1 0

Floating point error in analysis (describe)
by epidata-list＠lists.umanitoba.ca 06 Aug '07

06 Aug '07

re: "invalid floating pint" error with DESCRIBE in Analysis > I use the command line editor to issue DESCRIBE * command, and I get descriptive summaries of all variables, including the variable called AMOUNT. > > But when I issue the command DESCRIBE AMOUNT, I get an error message: Invalid floating point operation > > Please do the following: 1. Download the most recent testing version of EpiData Analysis: www.epidata.dk/testing.php 2. Retry the same analysis 3. Report to the list if the problem persisted. 4. If the problem persisted: a. pack your data file in a zip file (e.g. with epidata entry - tools menu). b. report the error to the epidata mantis system http://www.epidata.dk/php/mantis/login_page.php and upload the zip file as part of the error report. Kind regards Jens Lauritsen EpiData Association

1 2

how to sum numeric variables even if one of the variables is empty
by epidata-list＠lists.umanitoba.ca 06 Aug '07

06 Aug '07

Hello I would like to make an automatic sum (see: variable "daystotadm") of a series of variables (see: variable "daysadm1-2..."), but if only one of these variable is empty, the automatic calculation using the function SUM give a null result. Do anyone know a way to solve this problem without the need to enter a value for each variable. In my file I don not necessarily enter all the five lines and the number of days is already a calculated field? I attach the qes and the check files Thank you Francesco Grandesso QES FILE --------------------------------------------------------------------------------- Date of entry Date of exit Number of days -------------------------------------------- --------------- {dateentry1} <dd/mm/yyyy> {dateexit1} <dd/mm/yyyy> {daysadm1} ### {dateentry2} <dd/mm/yyyy> {dateexit2} <dd/mm/yyyy> {daysadm2} ### {dateentry3} <dd/mm/yyyy> {dateexit3} <dd/mm/yyyy> {daysadm3} ### {dateentry4} <dd/mm/yyyy> {dateexit4} <dd/mm/yyyy> {daysadm4} ### {dateentry5} <dd/mm/yyyy> {dateexit5} <dd/mm/yyyy> {daysadm5} ### -------------------------------------------- --------------- {daystotadm} Total days #### CHK FILE ---------------------------------------------------------------------------------- dateexit1 AFTER ENTRY daysadm1=(dateexit1-dateentry1) daystotadm=SUM(daysadm1,daysadm2,daysadm3,daysadm4,daysadm5) END END daysadm1 NOENTER END .................... and so on for each of the five dateexit* and daysadm* variables __________________________________________ Francesco Grandesso EPICENTRE 8, Rue Saint Sabin 75011 Paris, France tel +33 (0)1 4021 2847 fax +33 (0)1 4021 2803 email Francesco.GRANDESSO(a)epicentre.msf.org

1 1

Chris Sellers/FHS/ADPH is out of the office.
by epidata-list＠lists.umanitoba.ca 04 Aug '07

04 Aug '07

I will be out of the office starting 08/03/2007 and will not return until 08/09/2007. I will check emails periodically while I am away. If an issue needs immediate attention, please, contact Fred Grady at FredGrady(a)adph.state.al.us. Otherwise, I will respond to your email when I return.

1 0

Command Set replace logfile=on
by epidata-list＠lists.umanitoba.ca 04 Aug '07

04 Aug '07

Dear Epidata Team friends, I want to get the html file output form datafile by a PGM. I want to replace the previous output in the defined folder by the new output. The commands in my PGM are as follows; Set replace logfile=on Logopen The quarterly report file . 2007 /close Error message displayed is Replace Logfile not supported I change Set replace logfile=on to another command set replace datafile=on That also does not help. The help file about /close , /replace switches of Logopen command is not clear because it does not work as expected. If you close and reload Epidata Analysis, it works only once and displays error message when the PGM is run second time in the same session. What is the right command syntax? I am using trial version 2 (build 112). With regards, Shavinder Singh

1 0

Command Set replace logfile=on
by epidata-list＠lists.umanitoba.ca 03 Aug '07

03 Aug '07

Dear Epidata Team friends, I want to get the html file output form datafile by a PGM. I want to replace the previous output in the defined folder by the new output. The commands in my PGM are as follows; Set replace logfile=on Logopen The quarterly report file . 2007 /close Error message displayed is Replace Logfile not supported I change Set replace logfile=on to another command set replace datafile=on That also does not help. The help file about /close , /replace switches of Logopen command is not clear because it does not work as expected. If you close and reload Epidata Analysis, it works only once and displays error message when the PGM is run second time in the same session. What is the right command syntax? I am using trial version 2 (build 112). With regards, Shavinder Singh

1 0

Summing a number of variables
by epidata-list＠lists.umanitoba.ca 03 Aug '07

03 Aug '07

The easiest way of summing: > I would like to make an automatic sum (see: variable "daystotadm") of a > series of variables (see: variable "daysadm1-2..."), but if only one of > these variable is empty, the automatic calculation using the function SUM > give a null result. > What I would do is: dateexit1 AFTER ENTRY if dateexit1 = . then goto daysadm1 endif end end dateexit2 AFTER ENTRY if dateexit2 = . then goto daysadm endif end end etc for the other dateexit3 to 5. daysadm before entry * assume you have at least data in the first var: daysadm=(dateexit1-dateentry1) if dateexit2 <> . then daystotadm =(dateexit2-dataentry2) + daysadm endif if dateexit3 <> . then daystotadm =(dateexit3-dataentry3) + daysadm endif if dateexit4 <> . then daystotadm =(dateexit4-dataentry4) + daysadm endif if dateexit5 <> . then daystotadm =(dateexit5-dataentry5) + daysadm endif goto ... next variable end end In this way when the first dateexit is equal to ., the program jumps and no entry is needed in ... up to number 5 variable. (I hope the comparison of date variable with . works - did not test it). Regarding the other question from yesterday. Installation of EpiData software (entry and analysis) is always very "clean", meaning not disturbing the PC, so you can have many copies if you wish for various purposes. Just copy the exe file (plus help if needed). When testing I tend to create the default for testing as: c:\epidataanalysistest such that the test version of analysis does not interfere with the release version. regards jens lauritsen EpiData Association

1 0

"invalid floating pint" error with DESCRIBE in Analysis
by epidata-list＠lists.umanitoba.ca 02 Aug '07

02 Aug '07

I have a small data file, created in EpiData 3.1 on Windows XP. It consists of 7 records and 8 variables. I load the data into Analysis version 1.1 build 68. I use the command line editor to issue DESCRIBE * command, and I get descriptive summaries of all variables, including the variable called AMOUNT. But when I issue the command DESCRIBE AMOUNT, I get an error message: Invalid floating point operation See attached html file. Any suggestions how I could solve this problem? Thanks. -- Christopher W. Ryan, MD SUNY Upstate Medical University Clinical Campus at Binghamton 40 Arch Street, Johnson City, NY 13790 cryanatbinghamtondotedu PGP public keys available at http://home.stny.rr.com/ryancw/ "If you want to build a ship, don't drum up the men to gather wood, divide the work and give orders. Instead, teach them to yearn for the vast and endless sea." [Antoine de St. Exupery]

1 0

Data entry only setup for EpIData Entry
by epidata-list＠lists.umanitoba.ca 20 Jul '07

20 Jul '07

Re: Is it possible to start Epidata Entry with "Enter data" For a system like that I suggest to add to the chk file the following: after file backup ..... see below quit end with the above, EpiData Entry will quit completely after performing a backup. Further on the backup: (copied from the help file) The syntax of the backup command is: BACKUP distination-directory or BACKUP distination-directory [ZIP zip-file-name [DATE]] or BACKUP distination-directory [ENCRYPT name-of-encrypted-zip-file password [DATE]] I usually prefer BACKUP distination-directory ZIP zip-file-name DATE Regards Jens Lauritsen EpiData Association

1 0

Re: EpiData-list Digest, Vol 45, Issue 6
by epidata-list＠lists.umanitoba.ca 19 Jul '07

19 Jul '07

Thanks for the help Jamie, it works just fine; I like the notoolbars option. -----Original Message----- From: epidata-list-request(a)lists.umanitoba.ca To: epidata-list(a)lists.umanitoba.ca Sent: Wed, 18 Jul 2007 7:01 pm Subject: EpiData-list Digest, Vol 45, 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. Re: Is it possible to start Epidata Entry with "Enter data" (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Tue, 17 Jul 2007 22:06:28 -0400 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] Is it possible to start Epidata Entry with "Enter data" To: epidata-list(a)lists.umanitoba.ca Message-ID: <469D75A4.5020506(a)sympatico.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed You can get most of this by doing the following: Make sure the Windows Toolbars option is to hide toolbars during entry (this is the default) Create a shortcut that has the command line "c:\program files\epidata\epidata.exe" "c:\data\file.rec" You can put "/notoolbars" on the end of that, but it may be better to set the options that way. Users can still turn on the other toolbars, but why would they? Everything needed for entry is there. Jamie > I would like to know if it is possible to force a data entry clerk to click on a short cut (which we can create and place on desktop) that would allow the user to only enter data without having access to the other data entry functions (e.g. check, data documentation, etc). This is to prevent the data entry person from chnaging anything with the data entry forms during the entry process. > > Shuaib > ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 45, Issue 6 ******************************************* ________________________________________________________________________ AOL now offers free email to everyone. Find out more about what's free from AOL at AOL.com.

1 0

Is it possible to start Epidata Entry with "Enter data"
by epidata-list＠lists.umanitoba.ca 17 Jul '07

17 Jul '07

Dear Epidata Users, I would like to know if it is possible to force a data entry clerk to click on a short cut (which we can create and place on desktop) that would allow the user to only enter data without having access to the other data entry functions (e.g. check, data documentation, etc). This is to prevent the data entry person from chnaging anything with the data entry forms during the entry process. Many thanks Shuaib ________________________________________________________________________ AOL now offers free email to everyone. Find out more about what's free from AOL at AOL.com.

1 1

RR in TABLES command
by epidata-list＠lists.umanitoba.ca 12 Jul '07

12 Jul '07

Regarding Pedro Arias' question Couldn't the default display for TABLES VAR1 VAR2 be NN at the 'a' cell, and YY for TABLES VAR1 VAR2 /RR ? best regards, Fúlvio ----- Mensagem original ---- De: "epidata-list-request(a)lists.umanitoba.ca" <epidata-list-request(a)lists.umanitoba.ca> Para: epidata-list(a)lists.umanitoba.ca Enviadas: Quarta-feira, 11 de Julho de 2007 18:00:51 Assunto: EpiData-list Digest, Vol 45, Issue 3 Dear all, I have a general question regarding the layout for the output of the TABLES command. In version 2 (112) the default option for TABLES is sorted in ascending order. That means that when using boolean fields TABLES will display N,N in the top left cell of a 2 x 2 table, because internally NO=0 and Yes=1. (Jens, is that correct?) When asking for RR (TABLES VAR1 VAR2 /RR) what we get is the RR of being N in the outcome if you are N in the exposure. Which is clearly the inverse of what we usually are looking for. But because most of the statistical/epidemiological software dispay the table in the other way (Y,Y on the top left cell) EpiData can misslead the users with its results. (obviously users should read the table, but...). And we have /SD as option to change that My question is: Should EPiData follow the general rule of displaying YY in the too left cell?. (and therefore calculating the RR that usually we are interested in) Jens has a point saying that if we change that when we are not interested in RR but only in the numbers and %, most of the program follow the rule of sorting the values in ascending order and that if we want to follow this rule we will need an EPITABLE command (in version 2 he is trying to get ride of innecesary commands). I think we alreday have the EPITABLE command, it is TABLES V1 V2 /RR I would appreciate if can comment on that. Version 2 is almost ready, but i think this is an important issue. Hope my explantion and question is clear. Thanks a lot, Pedro Arias EpiData Spanish cotranslator I am checking the entry in some files using the double entry verification. The data are from a family study so the unique identifying information is a family ID (4 digits), an individual ID (2 digits), and informant ID (in some cases, people will be reporting on others. Each data record, then, is uniquely identified by these 8 digits. I created a key for the entry check file as follows: rhinf RANGE 1 99 MUSTENTER after entry rhukey=famid*10000+indid*100+rhinf end END rhukey noenter key unique end This works fine to prevent entering the same record twice. I'm trying to use the variable rhukey as the match variable in the double entry program. I have intentionally entered non-matching data, but Epidata doesn't recognize any discrepancies. Is there a problem with a key that is created in the dbl file as well as in the original file? Thanks. Richard Herrell NIMH --------------------------------- Shape Yahoo! in your own image. Join our Network Research Panel today! I prefer the current method as there is no doubt about what the syntax means (lower values in top left unless you specify /SD) and the /SD switch provides a means of inverting the order. Many people code variables as 1=Yes 2=No, which gives a proper RR without the /SD switch. Many others use 0=No 1=Yes, which requires /SD. Since EpiData internally treats Booleans False as 0 and True as 1, the current approach allows programming that does not require exceptions. User help and guides should point this out. The TAB output clearly identifies the meaning of the RR, which is something a number of us requested. This is something that came into later versions of EpiInfo to help the user avoid misunderstanding. So no need for EPITABLE - just use TAB OUTCOME EXPOSURE /RR /SD Jamie > My question is: Should EPiData follow the general rule of displaying YY in > the too left cell?. (and therefore calculating the RR that usually we are > interested in) > > Jens has a point saying that if we change that when we are not interested > in RR but only in the numbers and %, most of the program follow the rule > of sorting the values in ascending order and that if we want to follow > this rule we will need an EPITABLE command (in version 2 he is trying to > get ride of innecesary commands). I think we alreday have the EPITABLE > command, it is TABLES V1 V2 /RR > ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list ____________________________________________________________________________________ Novo Yahoo! Cadê? - Experimente uma nova busca. http://yahoo.com.br/oqueeuganhocomisso

1 0

Standard tables layout
by epidata-list＠lists.umanitoba.ca 10 Jul '07

10 Jul '07

Dear all, I have a general question regarding the layout for the output of the TABLES command. In version 2 (112) the default option for TABLES is sorted in ascending order. That means that when using boolean fields TABLES will display N,N in the top left cell of a 2 x 2 table, because internally NO=0 and Yes=1. (Jens, is that correct?) When asking for RR (TABLES VAR1 VAR2 /RR) what we get is the RR of being N in the outcome if you are N in the exposure. Which is clearly the inverse of what we usually are looking for. But because most of the statistical/epidemiological software dispay the table in the other way (Y,Y on the top left cell) EpiData can misslead the users with its results. (obviously users should read the table, but...). And we have /SD as option to change that My question is: Should EPiData follow the general rule of displaying YY in the too left cell?. (and therefore calculating the RR that usually we are interested in) Jens has a point saying that if we change that when we are not interested in RR but only in the numbers and %, most of the program follow the rule of sorting the values in ascending order and that if we want to follow this rule we will need an EPITABLE command (in version 2 he is trying to get ride of innecesary commands). I think we alreday have the EPITABLE command, it is TABLES V1 V2 /RR I would appreciate if can comment on that. Version 2 is almost ready, but i think this is an important issue. Hope my explantion and question is clear. Thanks a lot, Pedro Arias EpiData Spanish cotranslator

1 2

Longitudinal data validity checks
by epidata-list＠lists.umanitoba.ca 09 Jul '07

09 Jul '07

One very efficient approach for overview of consistency. E.g. counts of id numbers at various times is to use the "count by id" function in document menu of EpiData Entry. (or for batch procedures with EpiC). The idea is to count in different files how many times a unique identifier was found:. Example output: Count of records based on field ID Selected files: File 1 = key.rec File 2 = data\idkey.rec 120 different values for ID found Files ID 1 2 --------------------- 0 1 1 1 6 6 2 6 6 The key variable could as here be a simple integer, but could also be a string, e.g. of the type: 0-1 0-2 0-3 constructed as a combination of the id (here 0) and the time of visit (here either 1 2 or 3). In the check file: id mustenter end timevar comment legal 1 "Initial visit" 2 "6 months follow-up" 3 "2 year follow up" end mustenter after entry idkey = string(id) + "-" + string(timevar) end end idkey key unique noenter end ......................................... Notice that the "key unique" status for idkey is checked at creation of the contents, that is in the "after entry" block of the time variable. regards Jens Lauritsen EpiData Association

1 0

consistency checks on longitudinal data
by epidata-list＠lists.umanitoba.ca 09 Jul '07

09 Jul '07

Hello all, I'm setting up a multi-centre longitudinal study where data will be entered by health care workers with very little experience of research or possibly of computers. Every two weeks they will be visited by researchers. The data will be entered long, ie with one record for each time point. I need the data entry to be very simple, and the researchers will run consistency checks to find problems. Some things I want to do are: 1) check for duplicates on a few fields ( of course there is a unique ID - this would be to pick up duplicate data with different IDs) 2) check number of time points per patient ID 3) check dates are within range 4) check that date for time point 2 comes after date for time point 1 for the same patient ID I have used EpiData for entry for a few years but I haven't used Analysis. I would be glad of any advice. Thanks, Vicky Simms -- Vicky Simms Research Associate Palliative Care, Policy and Rehabilitation King's College London

1 1

Changing color of a field: Re: EpiData-list Digest, Vol 44, Issue 7
by epidata-list＠lists.umanitoba.ca 29 Jun '07

29 Jun '07

Hi, i'm a new user of epidata, but already familiar with epi6. This is my first time replying to an inquiry, and hope to provide some tips or at least initiate an idea to solving an inquiry. To change the color of a field, a noenter or otherwise, you can have it defined at the beginning of a check file using the BEFORE FILE command, specifying the name of a field, and the color you want: BEFORE FILE COLOR vname color (i'm out in a field right now, i do not have access to my own pc, just using an internet cafe pc without epidata, so i can not provide more details on the command.) Thanks. . . knowell On 6/21/07, epidata-list-request(a)lists.umanitoba.ca < 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. Alyshia Landry is out of the office. > (epidata-list(a)lists.umanitoba.ca) > 2. nonter field (epidata-list(a)lists.umanitoba.ca) > 3. noenter field (epidata-list(a)lists.umanitoba.ca) > 4. Re: nonter field (epidata-list(a)lists.umanitoba.ca) > 5. RE: nonter field (epidata-list(a)lists.umanitoba.ca) > 6. Jumps in Epidata Entry (epidata-list(a)lists.umanitoba.ca) > 7. Re: Jumps in Epidata Entry (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 19 Jun 2007 13:25:33 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Alyshia Landry is out of the office. > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > < > OF5CCB8794.BB7D23E5-ON852572FF.005FB91E-852572FF.005FB91E(a)region.waterloo.on.ca > > > > Content-Type: text/plain; charset=US-ASCII > > > I will be out of the office starting 06/19/2007 and will not return until > 06/21/2007. > > If you require immediate assistance, please contact Stephen Drew at > extension 5330. > > > > > ------------------------------ > > Message: 2 > Date: Tue, 19 Jun 2007 21:25:21 -0300 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] nonter field > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <467873F1.5010202(a)ufba.br> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi epidata users ! > > Please, how can I change the color of a noenter field ? I tried modify > it using the colour function into a before block, but it works for every > field except the noenter field. > > I also tried to change the epidata.ini file, but it doesn´t work anyway. > > Where is my mistake ? > > I´d like to change the grey colour to another stronger one. > > Thank you very much. > > Mauricio > > > > ------------------------------ > > Message: 3 > Date: Tue, 19 Jun 2007 21:26:35 -0300 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] noenter field > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4678743B.5050004(a)ufba.br> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi epidata users ! > > Please, how can I change the color of a noenter field ? I tried modify > it using the colour function into a before block, but it works for every > field except the noenter field. > > I also tried to change the epidata.ini file, but it doesn´t work anyway. > > Where is my mistake ? > > I´d like to change the grey colour to another stronger one. > > Thank you very much. > > Mauricio > > > > ------------------------------ > > Message: 4 > Date: Tue, 19 Jun 2007 19:34:40 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] nonter field > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <46786810.3080009(a)sympatico.ca> > Content-Type: text/plain; charset="ISO-8859-1" > > > > ------------------------------ > > Message: 5 > Date: Wed, 20 Jun 2007 09:35:05 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: RE: [EpiData-list] nonter field > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: > <A7EAEBFDDEDEF440A7BDD772C73046A20B724769(a)xch-vac.ivs.local> > Content-Type: text/plain; charset="iso-8859-1" > > Hi Mauricio; > The noenter function hides the field, so it is nor reachable. So, I doubt > there is a way to modify its color. > Gilles Delmas > > -----Message d'origine----- > De : epidata-list(a)lists.umanitoba.ca [mailto: > epidata-list(a)lists.umanitoba.ca] > Envoyé : mardi 19 juin 2007 11:40 > À : epidata-list(a)lists.umanitoba.ca > Objet : [EpiData-list] nonter field > > Hi epidata users ! > > Please, how can I change the color of a noenter field ? I tried modify it > using the colour function into a before block, but it works for every field > except the noenter field. > > I also tried to change the epidata.ini file, but it doesn´t work anyway. > > Where is my mistake ? > > I´d like to change the grey colour to another stronger one. > > Thank you very much. > > Mauricio > > > > ------------------------------ > > Message: 6 > Date: Wed, 20 Jun 2007 10:34:14 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Jumps in Epidata Entry > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <6.1.2.0.0.20070620101610.01d0bec0(a)pop.socsci.ru.nl> > Content-Type: text/plain; charset="us-ascii"; format=flowed > > Dear list, > > I have two questions regarding Jumps in EpiData Entry. > > 1) I want to jump to variable v10 if de score for v8 is 1 to 7. Of course > this works: > v8 > RANGE 1 9 > COMMENT LEGAL USE oplcat > JUMPS > 1 v10 > 2 v10 > 3 v10 > 4 v10 > 5 v10 > 6 v10 > 7 v10 > END > MUSTENTER > END > > Is a shorter syntax possible and if so, how? > > > 2) Is it possible to make a jump defination that depends on the value > entered in a previous question? > For example: > After entering the value for variable v5 I want to jump to v8 if the > answer > on question v3=1. > > Kind Regards, > Pieter van Groenestijn > The Netherlands > > > > > > > ------------------------------ > > Message: 7 > Date: Wed, 20 Jun 2007 09:01:10 +0000 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Jumps in Epidata Entry > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4678ECD6.1040708(a)ird.bf> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi Pieter, > > You can use a "IF... THEN..." syntax instead of "JUMP". > > > For your examples: > > V8 > AFTER ENTRY > IF (V8 > 0 AND V8 < 8) THEN GOTO V10 > END > END > > > V5 > AFTER ENTRY > IF V3 = 1 THEN GOTO V8 > END > END > > > As you can see, this is pretty easy! > > Regards > > Yves > ------------------------------------------------------- > Yves MARTIN-PREVEL, Epidemiologist, MD, MSc, PhD > Nutrition Unit (WHO Collaborating Center for Nutrition) > Institut de Recherche pour le Développement (IRD) > 01 BP 182 - OUAGADOUGOU 01 - BURKINA FASO > Tel: +226 50 30 67 37; Fax: +226 50 31 03 85 > http://www.ird.bf/ > > epidata-list(a)lists.umanitoba.ca a écrit : > > Dear list, > > > > I have two questions regarding Jumps in EpiData Entry. > > > > 1) I want to jump to variable v10 if de score for v8 is 1 to 7. Of > > course this works: > > v8 > > RANGE 1 9 > > COMMENT LEGAL USE oplcat > > JUMPS > > 1 v10 > > 2 v10 > > 3 v10 > > 4 v10 > > 5 v10 > > 6 v10 > > 7 v10 > > END > > MUSTENTER > > END > > > > Is a shorter syntax possible and if so, how? > > > > > > 2) Is it possible to make a jump defination that depends on the value > > entered in a previous question? > > For example: > > After entering the value for variable v5 I want to jump to v8 if the > > answer on question v3=1. > > > > Kind Regards, > > Pieter van Groenestijn > > The Netherlands > > > > > > > > > > _______________________________________________ > > EpiData-list mailing list > > EpiData-list(a)lists.umanitoba.ca > > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 44, Issue 7 > ******************************************* > -- Knowell

1 1

Chris Sellers/FHS/ADPH is out of the office.
by epidata-list＠lists.umanitoba.ca 27 Jun '07

27 Jun '07

I will be out of the office starting Fri 06/22/2007 and will not return until Mon 07/02/2007. I will check emails periodically while I am away. If an issue needs immediate attention, please, contact Fred Grady at FredGrady(a)adph.state.al.us. Otherwise, I will respond to your email when I return.

1 0

Jumps in Epidata Entry
by epidata-list＠lists.umanitoba.ca 20 Jun '07

20 Jun '07

Dear list, I have two questions regarding Jumps in EpiData Entry. 1) I want to jump to variable v10 if de score for v8 is 1 to 7. Of course this works: v8 RANGE 1 9 COMMENT LEGAL USE oplcat JUMPS 1 v10 2 v10 3 v10 4 v10 5 v10 6 v10 7 v10 END MUSTENTER END Is a shorter syntax possible and if so, how? 2) Is it possible to make a jump defination that depends on the value entered in a previous question? For example: After entering the value for variable v5 I want to jump to v8 if the answer on question v3=1. Kind Regards, Pieter van Groenestijn The Netherlands

1 2

nonter field
by epidata-list＠lists.umanitoba.ca 20 Jun '07

20 Jun '07

Hi epidata users ! Please, how can I change the color of a noenter field ? I tried modify it using the colour function into a before block, but it works for every field except the noenter field. I also tried to change the epidata.ini file, but it doesn´t work anyway. Where is my mistake ? I´d like to change the grey colour to another stronger one. Thank you very much. Mauricio

1 2

noenter field
by epidata-list＠lists.umanitoba.ca 19 Jun '07

19 Jun '07

Hi epidata users ! Please, how can I change the color of a noenter field ? I tried modify it using the colour function into a before block, but it works for every field except the noenter field. I also tried to change the epidata.ini file, but it doesn´t work anyway. Where is my mistake ? I´d like to change the grey colour to another stronger one. Thank you very much. Mauricio

1 0

nonter field
by epidata-list＠lists.umanitoba.ca 19 Jun '07

19 Jun '07

Hi epidata users ! Please, how can I change the color of a noenter field ? I tried modify it using the colour function into a before block, but it works for every field except the noenter field. I also tried to change the epidata.ini file, but it doesn´t work anyway. Where is my mistake ? I´d like to change the grey colour to another stronger one. Thank you very much. Mauricio

1 0

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

19 Jun '07

I will be out of the office starting 06/19/2007 and will not return until 06/21/2007. If you require immediate assistance, please contact Stephen Drew at extension 5330.

1 0

selective check
by epidata-list＠lists.umanitoba.ca 19 Jun '07

19 Jun '07

Dear friends, Epidata is able to use external rec files as a check list. I would like to do this: dg1 should be groupped diagnoses dg2 should be the detail of the dg1 e.g. when there will be dg1=UTI (urinary tract infection) then I want to make the dg2 selection of SUTI - symptomatic UTI ASB - asymptomatic bacteriuria OUT - other urinary tract infections when dg1=BSI (Blood streem infection) then dg2 selection should be LCBI - laboratory confirmed bloodstreem infection CSEP - Clinical sepsis and so on. Could you help me? Tank in advance Vladimir ________________ Vladimir Prikazsky National Institute of Public Health - Statni zdravotni ustav Srobarova 48 100 42 Prague 10 Czech Republic +420 267 082 334 +420 272 741 433

1 0

Help with calculation using fields from 2 files
by epidata-list＠lists.umanitoba.ca 17 Jun '07

17 Jun '07

Dear fellow EpiData users, I have 2 data files, a demographics file called demo.rec and an assessment file called assess.rec. Demo.rec contains date of birth while assess.rec contains date of assessment. I'd like to calculate the age at assessment and display the age in assess.rec during data entry. How can I do a calculation using fields in 2 different files? An abbreviated version of my files with just the relevant fields are: demo.qes idno ### dob <dd/mm/yyyy> gender # demo.chk idno KEY UNIQUE 1 END gender LEGAL 1 2 END AFTER ENTRY RELATE idno assess END END assess.qes idno ### dateass <dd/mm/yyyy> ageass ##.# assess.chk idno KEY 1 END dateass AFTER ENTRY LET ageass=(dateass-???)/365.25 END END ageass NOENTER END Any help would be greatly appreciated. Thanks, Suzanna Suzanna Vidmar Senior Research Officer Clinical Epidemiology and Biostatistics Unit Royal Children's Hospital Flemington Rd Parkville Victoria 3052 telephone: +61 3 9345 6372 facsimile: +61 3 9345 6000

1 2

noenter field
by epidata-list＠lists.umanitoba.ca 17 Jun '07

17 Jun '07

Hi epidata users ! Please, how can I change the color of a noenter field ? I tried modify it using the colour function into a before block, but it works for every field except the noenter field. I also tried to change the epidata.ini file, but it doesn´t work anyway. Where is my mistake ? I´d like to change the grey colour to another stronger one. Thank you very much. Mauricio

1 0

value labels EpiData Analysis
by epidata-list＠lists.umanitoba.ca 07 Jun '07

07 Jun '07

I created a .rec file and added a .chk file in EpiData Entry. I created several value labels and saved the output. the .rec and .chk files are in the same folder and have identical names, but in EpiData Analysis FREQ and TABLES don't display labels in the results. SET TABLES VALUE=ON made no difference. Is there an option I haven't found to tell EpiData Analysis to use value labels from the associated .chk file? Thanks, Dave B Confidentiality Notice: This e-mail, including all attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited unless specifically provided under the New Mexico Inspection of Public Records Act. If you are not the intended recipient, please contact the sender and destroy all copies of this message. -- This email has been scanned by the Sybari - Antigen Email System.

1 0

Tabulating empty strata
by epidata-list＠lists.umanitoba.ca 04 Jun '07

04 Jun '07

If VAR1 and VAR2 can each take 5 values, but in the dataset some values are not used for both, is there a way to create a TABLES VAR1 VAR2 that lists all values and writes a zero in the cross-strata not containing any observation? I seem not been able to find the appropriate option for this. I would like to use it in EpiData Analysis Test Version 2.0 (build 112). Thank you for any assistance, Hans -- Hans L Rieder, MD, MPH Jetzikofenstr. 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 321 9122 Web: http://www.tbrieder.org

1 0

Re: EpiData Analysis - Definition of histogram
by epidata-list＠lists.umanitoba.ca 14 May '07

14 May '07

Good point by Jamie Hockin. We should incorporate into histogram (and epicurve) the ability to define length of interval. Until this is done users can work like this (in the test version) * generate the grouped variable: (age into five year groups) gen i ag = age div 5 labelvalue ag /3="<20" /4="20-24" /5="25-29" /etc ....... (3 because in this example 16 was the minimum age) histogram ag /xa // which will work as desired Regards Jens Lauritsen

1 1

Epicurve comments
by epidata-list＠lists.umanitoba.ca 13 May '07

13 May '07

I fully agree. I think there is a need of a date-time variable at least in Analysis. That can allow users to group cases in different periods of time (hours or days) with the complexity of reprograming as we have to do now. We also need the posibility of labelling the epicurve at two diferent levels in the time axis so that we can clearly see days an hours for example. This is more or less solved in EpiInfo for Windows (the grouping part). Jens, maybe you can have a look at the specifications for the epicurve I sent you earlier this year. Another question regarding some of the graphs is the need of doing the graph by a second variable for example bar agegroup by sex or line month by year. Thanks a lot Jens for all this job and thanks every body for their comments Pedro Arias > I agree. However, the question of x-axis increment is not fully defined. > There are two aspects to this. The usual option /xinc= will only affect > the labelling on the chart, as with other graphs. However, the interval > used to define boxes is something that should also be an option with > histogram. This is particularly important for epicurves. This means that > we can avoid awkward recoding of variables (especially tricky with > dates) to have an epicurve that groups cases by 4-hour intervals, for > example, and also labels the x-axis every 12 hours: > > epicurve onsettime case /xinc=12 /interval=4 > > The same would be true of a histogram by age, where we wanted age > grouped by 5 years. I would prefer > > his age /interval=5 /xinc=10 > > or > > define age5 ## > age5 = age div 5 > his age5 /interval=5 > > Right now, his and epicurve are constrained to intervals of 1, which > means that labelling is not always correct. > > Jamie Hockin > Public Health Agency of Canada > > Jens wrote: >> After constructive comments from Egil Arnesen in Tromsø, Norway and >> searching in various textbooks I have decided that for v2 the >> following two definitions will be implemented: >> >> histogram: >> A graph, where there is one bar for each value present in the data. >> The height of the bar corresponds to the count of records in the data. >> (possibly later the percentage of data). Each bar starts at the >> x-value which was in the data (e.g. age 45 is shown from 45-46.) And >> the width of one bar is the same as the unit of the x variable. >> The X-axis is numerical and can be scaled with minimum, maximum and >> increase.E.g. from 25 to 100 with tickmarks by 5 (25 30 35 ......95 >> 100) >> >> Bar: >> A graph, where there is one bar for each value represented in the >> data. The X-axis is categorical and the bar is centered around the >> tick mark, which would show the value label (or the value) given by >> the x value. >> >> If anyone has comments to this please send to this list. >> >> The principle of the histogram will be implemented also for EpiCurve >> (but has not been done yet). The mentioned implementation of bar and >> histogram should work from build 112 uploaded shortly before this >> mail. (Minor problem with the build 112 uploaded yesterday). > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 43, Issue 5 > *******************************************

1 0

EpiData Analysis - Definition of histogram
by epidata-list＠lists.umanitoba.ca 12 May '07

12 May '07

After constructive comments from Egil Arnesen in Tromsø, Norway and searching in various textbooks I have decided that for v2 the following two definitions will be implemented: histogram: A graph, where there is one bar for each value present in the data. The height of the bar corresponds to the count of records in the data. (possibly later the percentage of data). Each bar starts at the x-value which was in the data (e.g. age 45 is shown from 45-46.) And the width of one bar is the same as the unit of the x variable. The X-axis is numerical and can be scaled with minimum, maximum and increase.E.g. from 25 to 100 with tickmarks by 5 (25 30 35 ......95 100) Bar: A graph, where there is one bar for each value represented in the data. The X-axis is categorical and the bar is centered around the tick mark, which would show the value label (or the value) given by the x value. If anyone has comments to this please send to this list. The principle of the histogram will be implemented also for EpiCurve (but has not been done yet). The mentioned implementation of bar and histogram should work from build 112 uploaded shortly before this mail. (Minor problem with the build 112 uploaded yesterday). Kind regards Jens Lauritsen EpiData Association

1 1

EpiData Analysis - next test release ready
by epidata-list＠lists.umanitoba.ca 11 May '07

11 May '07

Build 112 of analysis has been uploaded for testing. Users are encouraged to try the following: * Install routine * new table command * epicurve dotplot cdfplot * Spc routines * documentation * reading and saving files _Known issues and comments_ * Default sorting of non-integer reals in tables * Histogram error (rightmost bar not shown) * Notice /cc changed to /nm in tables * recode v1 to v2 by x gives partial errors (e.g. 10-1 09) * possibly help file principle partially correct writing word in command prompt via F1 link to help file _Recently solved_ * All fields saved correctly (?) * EpiCurve Final * Added Upper Case fields * New graphs: Histogram refined (xinc xmin and xmax working) * Clarified help file (F1) * (other bugs removed) * test of date correctness * added protection against reserved terms(e.g. date) The addition of upper case fields had consequences in many areas. Previously analysis did not compare strings correctly. Before release as version 2 the following will be added: Writing chk files, Translation of menu's, Dialog for the new tables module, fixing bugs Kind regards Jens Lauritsen EpiData Association

1 0

Confidence intervals during analysis
by epidata-list＠lists.umanitoba.ca 07 May '07

07 May '07

A very belated thanks Jens for your response! Looking forward to new developments. Regards Juanette John Natural Resources & the Environment - CSIR PO Box 395 Pretoria 0001 South Africa CSIR: "our future through Science" http://www.csir.co.za -- This message is subject to the CSIR's copyright, terms and conditions and e-mail legal notice. Views expressed herein do not necessarily represent the views of the CSIR. CSIR E-mail Legal Notice http://mail.csir.co.za/CSIR_eMail_Legal_Notice.html CSIR Copyright, Terms and Conditions http://mail.csir.co.za/CSIR_Copyright.html For electronic copies of the CSIR Copyright, Terms and Conditions and the CSIR Legal Notice send a blank message with REQUEST LEGAL in the subject line to CallCentre(a)csir.co.za. This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

1 0

Réponse automatique d'absence du bureau : [EpiData-list] problem starting Epidata
by epidata-list＠lists.umanitoba.ca 02 May '07

02 May '07

Bonjour, Je suis actuellement absent du bureau.Je serai de retour le 21 mai 2007 Je répondrai à cette date à votre message A bientôt Hello, I am currently out of the office and will be back on May the 21st 2007 I will reply to your message then. All the best Robert

1 0

problem starting Epidata
by epidata-list＠lists.umanitoba.ca 02 May '07

02 May '07

Hi all, I'm new to Epidata and have worked with it for about a week now. It's running on various PCs with Windows XP, connected in a network. Now, however, a problem has occured, that the application refuses to run on any of the computers connected to the network. Upon start it looks like the app will start as normal, but then will remain as a minimized application in the taskbar. I've tried to start it both by using the shortcut on the desktop and by clicking the datafile I am working with directly, however nothing really worked. Does anybody have a clue what might be the source of the problem? And if I cannot avoid to reinstall the software, do I need to backup my data? Sorry for my poor language proficiency and the relatively simple-looking problem I have. Thanks in advance. Thorsten _______________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192

1 0

Getting values from other records (was: create reduced dataset with EpiData Analysis): long to wide conversion
by epidata-list＠lists.umanitoba.ca 30 Apr '07

30 Apr '07

Hans wishes to get from SET12.REC with variables: ID AGE SEX VAR1 VAR2 - where each person (ID) have four records which we each call one visit to NEWSET.REC with variables: ID AGE SEX VAR11 VAR21 VAR12 VAR22 VAR13 VAR23 VAR14 VAR24 where each person (ID) have one record This conversion can be named "From long to wide format" and is a conversion we often wish to work on: In the example it is quite easy, since it seems that there are exactly four visits per person. One way of doing this is: (principle must be tested on actual data) read set12.rec freq id // here I would look to make sure that all id's actually had four records * We assume that the order of visits in set12 is chronological, but wish to have an identifier: gen i visit = 1 // integer variable with value 1 for all if id = id[_n-1] then visit = visit[_n-1] + 1 // now the value of visit is correct 1 2 3 4 * the [_n] indicates recnumber and by subtracting one "_n-1" we get the previous record browse // here I would look to control that the calculation was correct * generate the 8 variables: (you could also use define followed by let ) gen var11 = -1 ..... etc until gen var24 = -1 * the reason for the value -1 is that we wish to know if the variable is changed later. Sort id visit * now we can move the values to the correct variable: (shown for the var11..var14) if visit = 1 then var11 = var1 if visit = 1 then var12 = var1[_n+1] if visit = 1 then var13 = var1[_n+2] if visit = 1 then var14 = var1[_n+3] * and similarly for the var2x variables browse // to see visually that it works * all values have now been copied from four records to the first record for each person select visit = 1 labeldata "My combined file in wide format" savedata newfile The principle above can be used for many conversions. E.q. for first and follow up visit: * assume bmi indicates body mass index. And we wish to test for bmi change by sex: gen bmidif = . if (visit = 1) and (id = id[_n+1]) then bmidif = bmi[_n+1] - bmi means bmidif sex // for testing in version 2 add /t The next question could be "How to get from wide to long format" - The reverse of what Hans wanted. This would not be quite as easy, but something like generate 400 // an empty file first, e.g. 100 observations with four records gen i s = _n // instead of _n recnumber can be used gen i id = 1 if (s mod 4) = 0 and (recnumber > 4) then id = id[_n-4] + 1 * plus some more logic to get the id numbers right. * then the data could be added by "relate" and subsequently moved to the correct variables regards Jens Lauritsen

1 2

Getting values from other records - long to wide conversion - continued
by epidata-list＠lists.umanitoba.ca 30 Apr '07

30 Apr '07

Marcel extended the example by asking: Is there a way to make sure that the data set is sorted to be sure that the assumption: "* We assume that the order of visits in set12 is chronological, holds" ? I recommend having a time in the "visits record", preferably: e.g. datevisit, but also a sequential number in patient follow up studies, e.g.visit 1=start 2=4monts 3=12 months 4=2years etc. In real empirical data it usually happens that one or more visits are either missed or taking place at a point in time not exactly being on time. E.g. how to designate a visit 5 monts after initial treatment in a study where visits are supposed to be at 4 and 6 months. Sequence often indicates certain tests (e.g. blood samples) which vary by visit, e.g. more expensive ones less often, such as x-rays. By using as well the date and the sequence we can know exactly what are the data, which variables are missing and what is the time difference from "supposed time of visit". Therefore careful planning obviously remedies this by having the possibility to sort as well on sequence and date. sort id visit In the control of such data I would always: read rawdata *suppose we need 4 visits per person, numbered 1 2 3 4 * 1+2+3+4=10 aggregate studyid /sum="visit" /close gen i ok=(sumvisit=10) list studyid visit if ok <> 1 * or the same in "epi6" mode: read rawdata aggregate .... as above... define ok # let ok = 0 if (sumvisit = 10) then ok = 1 select if ok <> 1 list studyid select regards Jens Lauritsen

1 0

Create reduced dataset with EpiData Analysis
by epidata-list＠lists.umanitoba.ca 28 Apr '07

28 Apr '07

I have a parent SET1.REC, containing a key unique identifier ID and AGE and SEX, related to child SET2.REC, containing VAR1 and VAR2 In analysis, I create SET12.REC that has now as many records as SET2 (ID, AGE, and SEX) repeated for each record up to as many times as there are values for VAR1 and VAR2. If SET1 actually represents the individuals identified by ID, and SET2, e.g., visits for ID, and I wish now to make a NEW.REC containing only as many records as there are IDs, but making new variables VAR11, VAR21, VAR12, VAR22, and VAR13, VAR23, VAR14, VAR24 (if there are up to 4 visits for each ID, HOW would one thus write an EpiData Analysis command set to get from: SET12.REC ID AGE SEX VAR1 VAR2 to NEWSET.REC ID AGE SEX VAR11 VAR21 VAR12 VAR22 VAR13 VAR23 VAR14 VAR24 (where I know there is a maximum of 4 visits per ID) with only ID number of records? Thank you for any input you might have, Hans -- Hans L Rieder, MD, MPH Jetzikofenstr. 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 321 9122 Web: http://www.tbrieder.org

1 0

Re : EpiData-list Digest, Vol 42, Issue 14
by epidata-list＠lists.umanitoba.ca 26 Apr '07

26 Apr '07

bonjour veullez ne plus m'envoyer de messages!!!merci ----- Message d'origine ---- De : "epidata-list-request(a)lists.umanitoba.ca" <epidata-list-request(a)lists.umanitoba.ca> À : epidata-list(a)lists.umanitoba.ca Envoyé le : Mardi, 24 Avril 2007, 19h03mn 39s Objet : EpiData-list Digest, Vol 42, Issue 14 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. Is there any way to import from Excel to EpiData? (epidata-list(a)lists.umanitoba.ca) 2. Re: Is there any way to import from Excel to EpiData? (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Tue, 24 Apr 2007 10:48:18 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Is there any way to import from Excel to EpiData? To: <epidata-list(a)lists.umanitoba.ca> Message-ID: <939234DEF7B61C48B044D11A67E61B748A3EDE(a)mdmexch.medecinsdumonde.net> Content-Type: text/plain; charset=iso-8859-1 Hello everyone. I understand from the user manuals that data can be imported from text, dbase, and STATA. Has anyone figured out a way to import an Excel database, even though technically it is not an option? Thank you Todd Services Technique d'Appui aux Opérations (STAO) Médecins du Monde - France 62 rue Marcadet 75018 Paris - France Tél: +33 (0)1 44 92 16 18 ------------------------------ Message: 2 Date: Tue, 24 Apr 2007 05:41:32 -0700 (PDT) From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] Is there any way to import from Excel to EpiData? To: epidata-list(a)lists.umanitoba.ca Message-ID: <467108.92422.qm(a)web43141.mail.sp1.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 You can save the Excel file as a .dbf file, then import the .dbf file into Epidata. I assume you'll need to add variable names in the first row of the Excel file. Richard Herrell NIMH epidata-list(a)lists.umanitoba.ca wrote: Hello everyone. I understand from the user manuals that data can be imported from text, dbase, and STATA. Has anyone figured out a way to import an Excel database, even though technically it is not an option? Thank you Todd Services Technique d'Appui aux Opérations (STAO) Médecins du Monde - France 62 rue Marcadet 75018 Paris - France Tél: +33 (0)1 44 92 16 18 _______________________________________________ EpiData-list mailing list EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list --------------------------------- Ahhh...imagining that irresistible "new car" smell? Check outnew cars at Yahoo! Autos. ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 42, Issue 14 ******************************************** ___________________________________________________________________________ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com

1 1

Is there any way to import from Excel to EpiData?
by epidata-list＠lists.umanitoba.ca 25 Apr '07

25 Apr '07

Hello everyone. I understand from the user manuals that data can be imported from text, dbase, and STATA. Has anyone figured out a way to import an Excel database, even though technically it is not an option? Thank you Todd Services Technique d'Appui aux Opérations (STAO) Médecins du Monde - France 62 rue Marcadet 75018 Paris - France Tél: +33 (0)1 44 92 16 18

1 3

Anyone working on EpiData in Johannesburg
by epidata-list＠lists.umanitoba.ca 22 Apr '07

22 Apr '07

Hi, I wrote introductory guideline for EpiData at Karolinska Institute, Stockholm. Now I am in Johannesburg for data collection, will spend around 10 months here. People working in bioinformatics are interested in learning more about EpiData and was asked to present about database. Anyone living in Johannesburg and interested in joining to teach EpiData? Best regards ziad -- Ziad El-Khatib AIDS Unit National Institute for Communicable Diseases (NICD) 1 Modderfontein Road Private Bag X4, Sandringham, 2131 Johannesburg, South Africa Mobile: +27 (0) 72-52 39 716 Phone: +27 (0) 11-386 6433 Fax: +27 (0)11 386 6453 http://www.nhls.ac.za/div_nicd.html Division of International Health (IHCAR) Karolinska Institutet www.phs.ki.se/ihcar

1 0

Re: Defining confidence intervals in analysis
by epidata-list＠lists.umanitoba.ca 19 Apr '07

19 Apr '07

> > >I would like to know how one could change the confidence Interval (CI) > to reflect 90% instead of 95% which I assume is the default. I am > working in Epidata Analysis V2.0 (build 108). > > The command "set table CI HEADER="(90% CI)" only changes the text in the tables, not the calculation. Until now the statistics have NOT been adapted to other confidence intervals than 95%. For a given table it should be quite easy though given you have the raw numbers. Enter these into e.g. www.openepi.com and get the desired 90% CI. For analysis the possibility of users defining CI (e.g. 90 95 99) could be implemented within the next few years. Just now for the v2 of EpiData Analysis we are working on some "subtle" internal issues, which is why seemingly very little progress was made recently. The implementation of the Upper Case fields <AAAAA> revealed need for quite many changes, since all internal parts were made only for uppercase handling. The problems mentioned in the Mantis database and on the www.epidata.dk/testing.php page that the latest test build does not save data properly has been solved. Regards Jens Lauritsen EpiData Association

1 0

Confidence intervals and stats
by epidata-list＠lists.umanitoba.ca 19 Apr '07

19 Apr '07

Hi again I sent a request on the this earlier but I don't know if everyone was on holiday because I didn't get any response:-)! So I am trying again! I would like to know how one could change the confidence Interval (CI) to reflect 90% instead of 95% which I assume is the default. I am working in Epidata Analysis V2.0 (build 108). If one uses the command: Set TABLE CI HEADER="(90% CI)", it does change the header to reflect 90% but the actual CI values still stays the same. I also need to get the Fischer Exact p value, as well as the CI values as part of my table output. I looked in the help function and the command options do not seem to match up with the explanations. There is supposed to be an option that says 'add an extra table with a summary of chi square, p values etc' but I can't find the appropriate command on the LHS. I have been able to get the Fischer's exact p by using the command /EX but the command /CI didn't give me any confidence intervals. Please let me know if there is a flaw in my logic as I am not a stats expert. Thanks. Regards Juanette John -- This message is subject to the CSIR's copyright, terms and conditions and e-mail legal notice. Views expressed herein do not necessarily represent the views of the CSIR. CSIR E-mail Legal Notice http://mail.csir.co.za/CSIR_eMail_Legal_Notice.html CSIR Copyright, Terms and Conditions http://mail.csir.co.za/CSIR_Copyright.html For electronic copies of the CSIR Copyright, Terms and Conditions and the CSIR Legal Notice send a blank message with REQUEST LEGAL in the subject line to CallCentre(a)csir.co.za. This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

1 0

Re: common site for teaching/training materials
by epidata-list＠lists.umanitoba.ca 19 Apr '07

19 Apr '07

AS some of you might have noticed I have already defined an open EpiData site - in the form of a wiki - where some experiences on using this technology already exist. The www.epidata.org site has been reserved by me a few years back with the intention that this could serve as the "community" site for EpiData, maintained collectively by the body of epidata users. Pedro Arias and I created teaching material for use in the Canadian Field Epi course last autumn. Off list I have suggested to a number of users mentioning materials to add these to the site, but the time and energy to get onto a new way of working can be difficult to find for already busy people. If the material already exist it is quite easy to copy and paste into the wiki and upload the figures/images. The experimental site is found at http://www.epidata.org/wiki There is some learning problems in the beginning when editing in the wiki format, but with a few experiments it works very well. An introduction is shown at http://en.wikipedia.org/wiki/Wikipedia:How_to_edit_a_page The optimal would be that a group of persons together take on the responsibility of maintaining the open site, since we must unfortunately expect that someone will add irrelevant material or suggestions which otherwise are not appropriate. The initial steps of forming such a group has been made, but awaits further initiatives. Kind regards Jens Lauritsen -- Jens Lauritsen Coordinator and initiator of EpiData Project http://www.epidata.dk

1 0

Re: AW: [EpiData-list] BMI Calculation
by epidata-list＠lists.umanitoba.ca 18 Apr '07

18 Apr '07

Thanks for the link. I was interested to see the Epidata training materials on this site and also the ones now on the Epidata website. I'd be very interested in any other links. I'm especially interested in materials that deal with outbreaks so it was great to see the case study about Tiramisu on the epidata website - but that only deals with the analysis side. (Here we use Epidata for our questionnaires and data entry but use Epi Info for analysis). I've done a training manual for our public health staff about using Epidata and have an outbreak case study exercise that uses epidata and epi info, but have not made on line versions yet. I would be interested in talking to others - perhaps off line about materials they use for epidata training. thanks again Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 >>> <epidata-list(a)lists.umanitoba.ca> 13/04/2007 5:26 p.m. >>> Have a look at the many available documentations on the web. A similar thing (calculating age from date of birth) is included on page 6 of a very useful intro (A brief overview of EpiData software) to be found on http://www.tbrieder.org/ (follow icon to "Revised EpiData course") marcel -----Ursprüngliche Nachricht----- Von: epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Gesendet: Donnerstag, 12. April 2007 14:13 An: epidata-list(a)lists.umanitoba.ca Betreff: [EpiData-list] BMI Calculation Thanks. I just recently started using Epidata, and I need some help on creating a Check string for automatically calculating BMI using Weight and Height (in pounds and feet/inches). Thanks, again. -- Ali B. Mansaray MANSA Consulting Services 6530 Davidson Road Columbia, SC 29209 803-381-6864 ali.mansaray(a)gmail.com -- 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 3

Re: EpiData-list Digest, Vol 42, Issue 7
by epidata-list＠lists.umanitoba.ca 17 Apr '07

17 Apr '07

Dear Hans, Your program was quick and efficient. It did it! Thank you for your help. Ali On 4/14/07, epidata-list-request(a)lists.umanitoba.ca < 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. BMI from US measures (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 14 Apr 2007 00:25:35 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] BMI from US measures > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4620035F.20600(a)tbrieder.org> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > If you do not wish to show conversion of US measures into SI units in > the QES file, then your QES file should have this: > > *.QES file > wtpd Weight in US pounds ###.# > htft Height in US feet # > htin Height in US inches ## > bmi Body Mass Index in kg/m^2 ##.# > > You then make all your calculations in the CHK file to get the BMI in SI > units: > > *.CHK file > * Definitions from Wikipedia > * 1 US foot=(1200/3937) meters > * 1 US inch=25.4 millimeters > * 1 US pound= 453.59237 grams > > wtpd > MUSTENTER > END > > htft > MUSTENTER > END > > htin > MUSTENTER > AFTER ENTRY > bmi=(wtpd*0.45359237)/((htft*(1200/3937)+(htin*0.0254))^2) > END > END > > bmi > NOENTER > END > > > and that should do it. Beware of empty fields contributing to the > denominator. Should that be the case, you must make provisions in the > CHK file. The above works only if there are no zeros for the two > denominator variables, and not permitting any blank fields. > > Hans > > -- > Hans L Rieder, MD, MPH > Jetzikofenstr. 12 > 3038 Kirchlindach > Switzerland > > Tel: +41 31 829 4577 > Mob: +41 79 321 9122 > Web: http://www.tbrieder.org > > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 42, Issue 7 > ******************************************* > -- Ali B. Mansaray MANSA Consulting Services 6530 Davidson Road Columbia, SC 29209 803-381-6864 ali.mansaray(a)gmail.com a

1 0

BMI Calculation Suggestions
by epidata-list＠lists.umanitoba.ca 16 Apr '07

16 Apr '07

Thanks ever so much Pedro, Richard and Marcel. I was away and just returned. I am sure your suggestions and insights will amply address my my question. Regards, Ali On 4/13/07, epidata-list-request(a)lists.umanitoba.ca < epidata-list-request(a)lists.umanitoba.ca> wrote: > > Send EpiData-list mailing list submissions to > epidata-list(a)lists.umanitoba.ca > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > or, via email, send a message with subject or body 'help' to > epidata-list-request(a)lists.umanitoba.ca > > You can reach the person managing the list at > epidata-list-owner(a)lists.umanitoba.ca > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of EpiData-list digest..." > > > EpiData-list mailing list > ___________________________________ > > Today's Topics: > > 1. Re: EpiData-list Digest, Vol 42, Issue 5 > (epidata-list(a)lists.umanitoba.ca) > 2. Re: Re: EpiData-list Digest, Vol 42, Issue 5 > (epidata-list(a)lists.umanitoba.ca) > 3. AW: [EpiData-list] BMI Calculation > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 12 Apr 2007 15:39:31 -0300 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Re: EpiData-list Digest, Vol 42, Issue 5 > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <a37cfb5a0704121139lba5854ex3941892ba45d43a1(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Dear Ali, > > It seems to be a simple task. First, as far as I know the BMI is > calculated > as weight/(heigh*heigh). However this values should be in Kg and m. If you > have the data in pounds and feet, then youl should transform them before. > To > make it easier, create a variable in the qes file with this information. > > qes file > > v1 heigh in feet ##.# > v2 heigh in m #.## > v3 weight in pound ###.## > v4 weight in Kg ###.# > v5 bmi ##.## > > chk file > > v1 > after entry > let v2 = round(v1*0,4536) > end > end > > v2 > noenter > end > > v3 > after entry > let v4=round(v3/3,28) > end > end > > v4 > noenter > end > > v5 > before entry > let v5=v4/(v2*v2) > goto v6 > end > end > > I hope this works fine for you because didnt test it! ;) > > Succes, > Pedro Emmanuel Brasil > > 2007/4/12, epidata-list-request(a)lists.umanitoba.ca < > epidata-list-request(a)lists.umanitoba.ca>: > > > > Send EpiData-list mailing list submissions to > > epidata-list(a)lists.umanitoba.ca > > > > To subscribe or unsubscribe via the World Wide Web, visit > > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > or, via email, send a message with subject or body 'help' to > > epidata-list-request(a)lists.umanitoba.ca > > > > You can reach the person managing the list at > > epidata-list-owner(a)lists.umanitoba.ca > > > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of EpiData-list digest..." > > > > > > EpiData-list mailing list > > ___________________________________ > > > > Today's Topics: > > > > 1. BMI Calculation (epidata-list(a)lists.umanitoba.ca) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Thu, 12 Apr 2007 08:12:37 -0400 > > From: epidata-list(a)lists.umanitoba.ca > > Subject: [EpiData-list] BMI Calculation > > To: epidata-list(a)lists.umanitoba.ca > > Message-ID: > > <9aeb5bc30704120512q55329040pc02a85328844f8d1(a)mail.gmail.com> > > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > > > Thanks. > > I just recently started using Epidata, and I need some help on creating > a > > Check string for automatically calculating BMI using Weight and Height > (in > > pounds and feet/inches). Thanks, again. > > > > > > > > -- > > Ali B. Mansaray > > MANSA Consulting Services > > 6530 Davidson Road > > Columbia, SC 29209 > > 803-381-6864 > > ali.mansaray(a)gmail.com > > > > > > ------------------------------ > > > > ________________________________________ > > EpiData-list(a)lists.umanitoba.ca > > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > > > > End of EpiData-list Digest, Vol 42, Issue 5 > > ******************************************* > > > > > ------------------------------ > > Message: 2 > Date: Thu, 12 Apr 2007 11:56:52 -0700 (PDT) > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Re: EpiData-list Digest, Vol 42, Issue 5 > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <797297.78297.qm(a)web43146.mail.sp1.yahoo.com> > Content-Type: text/plain; charset=iso-8859-1 > > > I useful little trick I picked up for us crazy Americans who insist on > using inches and pounds: Calculate pounds/(height in inches)^2. Multiple > the result by 703.0814 (or however precise you want the result) and you > have BMI. > > Richard Herrell > NIMH > > > epidata-list(a)lists.umanitoba.ca wrote: Dear Ali, > > It seems to be a simple task. First, as far as I know the BMI is > calculated > as weight/(heigh*heigh). However this values should be in Kg and m. If you > have the data in pounds and feet, then youl should transform them before. > To > make it easier, create a variable in the qes file with this information. > > qes file > > v1 heigh in feet ##.# > v2 heigh in m #.## > v3 weight in pound ###.## > v4 weight in Kg ###.# > v5 bmi ##.## > > chk file > > v1 > after entry > let v2 = round(v1*0,4536) > end > end > > v2 > noenter > end > > v3 > after entry > let v4=round(v3/3,28) > end > end > > v4 > noenter > end > > v5 > before entry > let v5=v4/(v2*v2) > goto v6 > end > end > > I hope this works fine for you because didnt test it! ;) > > Succes, > Pedro Emmanuel Brasil > > 2007/4/12, epidata-list-request(a)lists.umanitoba.ca < > epidata-list-request(a)lists.umanitoba.ca>: > > > > Send EpiData-list mailing list submissions to > > epidata-list(a)lists.umanitoba.ca > > > > To subscribe or unsubscribe via the World Wide Web, visit > > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > or, via email, send a message with subject or body 'help' to > > epidata-list-request(a)lists.umanitoba.ca > > > > You can reach the person managing the list at > > epidata-list-owner(a)lists.umanitoba.ca > > > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of EpiData-list digest..." > > > > > > EpiData-list mailing list > > ___________________________________ > > > > Today's Topics: > > > > 1. BMI Calculation (epidata-list(a)lists.umanitoba.ca) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Thu, 12 Apr 2007 08:12:37 -0400 > > From: epidata-list(a)lists.umanitoba.ca > > Subject: [EpiData-list] BMI Calculation > > To: epidata-list(a)lists.umanitoba.ca > > Message-ID: > > <9aeb5bc30704120512q55329040pc02a85328844f8d1(a)mail.gmail.com> > > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > > > Thanks. > > I just recently started using Epidata, and I need some help on creating > a > > Check string for automatically calculating BMI using Weight and Height > (in > > pounds and feet/inches). Thanks, again. > > > > > > > > -- > > Ali B. Mansaray > > MANSA Consulting Services > > 6530 Davidson Road > > Columbia, SC 29209 > > 803-381-6864 > > ali.mansaray(a)gmail.com > > > > > > ------------------------------ > > > > ________________________________________ > > EpiData-list(a)lists.umanitoba.ca > > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > > > > End of EpiData-list Digest, Vol 42, Issue 5 > > ******************************************* > > > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > > --------------------------------- > Never miss an email again! > Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out. > > ------------------------------ > > Message: 3 > Date: Fri, 13 Apr 2007 07:26:40 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: AW: [EpiData-list] BMI Calculation > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: <96551DCE4DCEF546921A8AF2F60826B0ED10CE(a)mx.ispm.unibe.ch> > Content-Type: text/plain; charset="iso-8859-1" > > Have a look at the many available documentations on the web. > A similar thing (calculating age from date of birth) is included on page 6 > of a very useful intro (A brief overview of EpiData software) to be found on > http://www.tbrieder.org/ (follow icon to "Revised EpiData course") > marcel > > > -----Ursprüngliche Nachricht----- > Von: epidata-list(a)lists.umanitoba.ca [mailto: > epidata-list(a)lists.umanitoba.ca] > Gesendet: Donnerstag, 12. April 2007 14:13 > An: epidata-list(a)lists.umanitoba.ca > Betreff: [EpiData-list] BMI Calculation > > Thanks. > I just recently started using Epidata, and I need some help on creating a > Check string for automatically calculating BMI using Weight and Height (in > pounds and feet/inches). Thanks, again. > > > > -- > Ali B. Mansaray > MANSA Consulting Services > 6530 Davidson Road > Columbia, SC 29209 > 803-381-6864 > ali.mansaray(a)gmail.com > > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 42, Issue 6 > ******************************************* > -- Ali B. Mansaray MANSA Consulting Services 6530 Davidson Road Columbia, SC 29209 803-381-6864 ali.mansaray(a)gmail.com a

1 0

BMI from US measures
by epidata-list＠lists.umanitoba.ca 13 Apr '07

13 Apr '07

If you do not wish to show conversion of US measures into SI units in the QES file, then your QES file should have this: *.QES file wtpd Weight in US pounds ###.# htft Height in US feet # htin Height in US inches ## bmi Body Mass Index in kg/m^2 ##.# You then make all your calculations in the CHK file to get the BMI in SI units: *.CHK file * Definitions from Wikipedia * 1 US foot=(1200/3937) meters * 1 US inch=25.4 millimeters * 1 US pound= 453.59237 grams wtpd MUSTENTER END htft MUSTENTER END htin MUSTENTER AFTER ENTRY bmi=(wtpd*0.45359237)/((htft*(1200/3937)+(htin*0.0254))^2) END END bmi NOENTER END and that should do it. Beware of empty fields contributing to the denominator. Should that be the case, you must make provisions in the CHK file. The above works only if there are no zeros for the two denominator variables, and not permitting any blank fields. Hans -- Hans L Rieder, MD, MPH Jetzikofenstr. 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 321 9122 Web: http://www.tbrieder.org

1 0

BMI Calculation
by epidata-list＠lists.umanitoba.ca 13 Apr '07

13 Apr '07

Thanks. I just recently started using Epidata, and I need some help on creating a Check string for automatically calculating BMI using Weight and Height (in pounds and feet/inches). Thanks, again. -- Ali B. Mansaray MANSA Consulting Services 6530 Davidson Road Columbia, SC 29209 803-381-6864 ali.mansaray(a)gmail.com

1 1

Re: EpiData-list Digest, Vol 42, Issue 5
by epidata-list＠lists.umanitoba.ca 12 Apr '07

12 Apr '07

Dear Ali, It seems to be a simple task. First, as far as I know the BMI is calculated as weight/(heigh*heigh). However this values should be in Kg and m. If you have the data in pounds and feet, then youl should transform them before. To make it easier, create a variable in the qes file with this information. qes file v1 heigh in feet ##.# v2 heigh in m #.## v3 weight in pound ###.## v4 weight in Kg ###.# v5 bmi ##.## chk file v1 after entry let v2 = round(v1*0,4536) end end v2 noenter end v3 after entry let v4=round(v3/3,28) end end v4 noenter end v5 before entry let v5=v4/(v2*v2) goto v6 end end I hope this works fine for you because didnt test it! ;) Succes, Pedro Emmanuel Brasil 2007/4/12, epidata-list-request(a)lists.umanitoba.ca < epidata-list-request(a)lists.umanitoba.ca>: > > Send EpiData-list mailing list submissions to > epidata-list(a)lists.umanitoba.ca > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > or, via email, send a message with subject or body 'help' to > epidata-list-request(a)lists.umanitoba.ca > > You can reach the person managing the list at > epidata-list-owner(a)lists.umanitoba.ca > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of EpiData-list digest..." > > > EpiData-list mailing list > ___________________________________ > > Today's Topics: > > 1. BMI Calculation (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 12 Apr 2007 08:12:37 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] BMI Calculation > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <9aeb5bc30704120512q55329040pc02a85328844f8d1(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Thanks. > I just recently started using Epidata, and I need some help on creating a > Check string for automatically calculating BMI using Weight and Height (in > pounds and feet/inches). Thanks, again. > > > > -- > Ali B. Mansaray > MANSA Consulting Services > 6530 Davidson Road > Columbia, SC 29209 > 803-381-6864 > ali.mansaray(a)gmail.com > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 42, Issue 5 > ******************************************* >

1 1

How to get appropriate stats - correction
by epidata-list＠lists.umanitoba.ca 08 Apr '07

08 Apr '07

Apologies. Part of my previous request about appropriate stats would not have made sense as I have subsequently realised that adding /f gives frequencies of the variables. Please bear with me and consider my revised question around the issue on how to get the appropriate stats. I would like to get the Fischer Exact p value, as well as the CI values as part of my table output. I looked in the help function and the command options do not seem to match up with the explanations. There is supposed to be an option that says 'add an extra table with a summary of chi square, p values etc' but I can't find the appropriate command on the LHS. I have been able to get the Fischer's exact p by using the command /EX but the command /CI didn't give me any confidence intervals. (I am using build 108). Thanks. Juanette -- This message is subject to the CSIR's copyright, terms and conditions and e-mail legal notice. Views expressed herein do not necessarily represent the views of the CSIR. CSIR E-mail Legal Notice http://mail.csir.co.za/CSIR_eMail_Legal_Notice.html CSIR Copyright, Terms and Conditions http://mail.csir.co.za/CSIR_Copyright.html For electronic copies of the CSIR Copyright, Terms and Conditions and the CSIR Legal Notice send a blank message with REQUEST LEGAL in the subject line to CallCentre(a)csir.co.za. This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

1 0

Changing confidence intervals & getting appropriate stats
by epidata-list＠lists.umanitoba.ca 05 Apr '07

05 Apr '07

I sent a request on the 29th of March asking how one could change CI to reflect 90% instead of 95% which I assume is the default. I am working in Epidata Analysis V2.0 (build 108). Someone suggested to add the following command: Set TABLE CI HEADER="(90% CI)", which I've tried. It does change the header to reflect 90% but the actual CI values still stays the same. I would also like to get the Fischer Exact p value, as well as the CI values in the table. The only way I've been able to get these, has been to put in the following command: tables var1 var2 /EX /CI /f (see below). But then it gives me two tables, which I am not sure how to interpret. .tables diarrh numtous2 /EX /CI /F Any member of family suffered of DIARRHOEA during last month? N % (90% CI) ........ only header changed, not values underneath 1 9 2.4 (1.3-4.5) 2 368 97.6 (95.5-98.7) Total 377 100.0 NUMTOUS2 N % (90% CI) <5 182 49.3 (44.3-54.4) 5&MORE 187 50.7 (45.6-55.7) Total 369 100.0 Thanks. Regards Juanette -- This message is subject to the CSIR's copyright, terms and conditions and e-mail legal notice. Views expressed herein do not necessarily represent the views of the CSIR. CSIR E-mail Legal Notice http://mail.csir.co.za/CSIR_eMail_Legal_Notice.html CSIR Copyright, Terms and Conditions http://mail.csir.co.za/CSIR_Copyright.html For electronic copies of the CSIR Copyright, Terms and Conditions and the CSIR Legal Notice send a blank message with REQUEST LEGAL in the subject line to CallCentre(a)csir.co.za. This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

1 0

First word or Automatic Field Names
by epidata-list＠lists.umanitoba.ca 05 Apr '07

05 Apr '07

I am interested as to why the default setting for Epidata for Field names is first word. I assume because it is the default setting that it is the most commonly used. Do other people use the first word setting when developing questionnaires? I have always used the automatic field names settings. I use Epidata mainly for outbreak questionnaires. For these we ask standard questions each time 1. descriptive details about the person 2. information about the pattern of illness 3. information about the things (usually food) that a person has been exposed to Becuase you have to develop questionnaires quickly when there is an outbreak I have a 'master file' which is like a template. When there is a new outbreak I just change the exposures and save it as a new name. The following is a sample of what part of the epidata qes file would look like: First name __________ Last Name _________ Sex <A> DOB <mm/dd/yyyy> Ill <Y> Diarrhoea <Y> OnsetDate <mm/dd/yyyy> Ham <Y> Beef <Y> Chicken <Y> What would be the advantage of using the first name setting? It would mean the field for the first name in the example above would be 'First'. I have seen people develop questionnaires that use say V1 as the field and Ham as the label. But it seems to be to be much easier to analyse data when the field name is self explanatory. I give other people the advice to set up their questionnaire like I have and I don't want to be telling them the wrong thing, so would be interested to know what other people 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

Duplicate files
by epidata-list＠lists.umanitoba.ca 04 Apr '07

04 Apr '07

Hello I have entered my data twice on epi data and would now like to validate files to make sure that my data is accurate. I have different ID numbers so can not run on Id keys but I have entered the data in the same order so the record numbers match. I have 1 deleted record in one database which I have adjusted for but checking the box that says ignore deleted records. I have 126 records in total when I go to validate files it comes up with an error box saying that it cannot create log file. Does anyone have any ideas on how this could be fixed. Thanx aysha

1 2

Printing forms
by epidata-list＠lists.umanitoba.ca 02 Apr '07

02 Apr '07

Helo all, Recently I was involved in a clinical trial in one center. Because of that I had to read some new stuff and to have classes of good clinical practices and about the ICH (International conference on harmonization). There are some stuff about these regulatory good clinical practice that I woul like to put on the list but for now a more pratical issue. Because of these regulatory resolutions, the research have to keep the clinical forms on paper, dated and signed by those who fill them. Since the clinical interview and evaluation will be made in offices where computer are easily accessible, then it would be easier if the professionals fill the forms on the computer an right after to print them. And only then sign and date the forms. There is a print option in the file menu while the enter data is open. However I would like to turn it automatic. Such as at the end of the form, while saving in the file, epidata would automaticlly send the form to the printer. As far as I could look for, I didnt find any chk command that would satisfy my wishes. So, I was figuring out to put a warning message, but it wouldnt work the same way. Any one with a tip to work around? Thank you, Pedro Emmanuel Brasil -- Abraço forte e que a força esteja com você, Pedro Emmanuel

1 0

Re: EpiData-list Digest, Vol 41, Issue 12
by epidata-list＠lists.umanitoba.ca 29 Mar '07

29 Mar '07

Dear Aysha, Not having an ID number is a fatal error that may compromize a lot of stuff in the analysis. By now U must have figured out that the best strategy would be a ID number generated by you and have the same ID number on the pair file. I did the same error and learned making mistakes and having to do all again sometimes in the past. I assume that U have the exact same 126 forms digitized twice in differrent files! If You have them all in the same order somethings can be done to work arround. The first sugestion, since it seems to bem few records, is to digitize a third time using the validate double files in the tool menu. (Im not shure if I can call like this because my menus are in portuguese) At this tool EpiData creates a second file with the same name with the extension yourfile_dbl.rec. Enter data in this file and U will see that as U put the data in the file it will show the difference of th first file and then ask if want to keep the new value or the old value! This one takes work thouh! The second work arround that I can imagine is that U may create a new variable in the qes file that would be the ID, update the rec file, enter the new unique IDs and the same ID inthe mirror file. A more clever one is to export your two files to other format such as STATA or xls and then create a new sequencial variable such as 1 to 126, doing the same with the mirror file. Watch out for mistakes here, beacause if U do mistakes it may be hard to find where it is! Then import them again inthe Epidata format an now compare them! If U work with STATA, it also have tool to compare datasets. Im shure that SAS and SPSS or R also have similar tools. I hope it helps you! Good luck, Pedro Emmanuel Brasil 2007/3/29, epidata-list-request(a)lists.umanitoba.ca < epidata-list-request(a)lists.umanitoba.ca>: > > Send EpiData-list mailing list submissions to > epidata-list(a)lists.umanitoba.ca > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > or, via email, send a message with subject or body 'help' to > epidata-list-request(a)lists.umanitoba.ca > > You can reach the person managing the list at > epidata-list-owner(a)lists.umanitoba.ca > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of EpiData-list digest..." > > > EpiData-list mailing list > ___________________________________ > > Today's Topics: > > 1. Duplicate files (epidata-list(a)lists.umanitoba.ca) > 2. Changing Confidence Intervals on EpiData Analysis > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 28 Mar 2007 16:28:37 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Duplicate files > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: > <7AC047D44A8CD243B7FE9305102D5FD105D96B27(a)MAIL.bc.iop.kcl.ac.uk> > Content-Type: text/plain; charset="us-ascii" > > Hello > > I have entered my data twice on epi data and would now like to validate > files to make sure that my data is accurate. I have different ID > numbers so can not run on Id keys but I have entered the data in the > same order so the record numbers match. I have 1 deleted record in one > database which I have adjusted for but checking the box that says ignore > deleted records. I have 126 records in total when I go to validate > files it comes up with an error box saying that it cannot create log > file. > > Does anyone have any ideas on how this could be fixed. > > Thanx > aysha > > > ------------------------------ > > Message: 2 > Date: Thu, 29 Mar 2007 10:51:36 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Changing Confidence Intervals on EpiData > Analysis > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: <460B9A38020000770000C4B6(a)cs-emo.csir.co.za> > Content-Type: text/plain; charset=US-ASCII > > Hi, I would like the stats I get when doing an epitable to to reflect a > 90% CI, instead of the default 95%. Is it possible to do so, and if yes, > how? > > Thanks! > > REgards > Juanette John > > Natural Resources & the Environment - CSIR > PO Box 395 > Pretoria > 0001 > South Africa > jjohn(a)csir.co.za > Tel 27 12 841 4189 (mornings only) > Cell 083 4100 444 > Fax 27 12 841 4257/086 6180084 > > CSIR: "our future through Science" > http://www.csir.co.za > > -- > This message is subject to the CSIR's copyright, terms and conditions and > e-mail legal notice. Views expressed herein do not necessarily represent > the > views of the CSIR. > > CSIR E-mail Legal Notice > http://mail.csir.co.za/CSIR_eMail_Legal_Notice.html > > CSIR Copyright, Terms and Conditions > http://mail.csir.co.za/CSIR_Copyright.html > > For electronic copies of the CSIR Copyright, Terms and Conditions and the > CSIR > Legal Notice send a blank message with REQUEST LEGAL in the subject line > to > CallCentre(a)csir.co.za. > > > This message has been scanned for viruses and dangerous content by > MailScanner, > and is believed to be clean. > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 41, Issue 12 > ******************************************** > -- Abraço forte e que a força esteja com você, Pedro Emmanuel

1 0

Re : EpiData-list Digest, Vol 41, Issue 12
by epidata-list＠lists.umanitoba.ca 29 Mar '07

29 Mar '07

Hello Juanette John You will make that to execute the following command [ set TABLE CI HEADER="(90% CI)" ] and after all the proportions will have IC 90 % Thank you ___________________________________________ Dr Jean-Paul DIBY-KONAN Médecin Santé Publique MCM Santé de la Reproduction Institut Médecine Tropicale Kapucinessenstraat 8 B-2000 Anvers Belgique ----- Message d'origine ---- De : "epidata-list-request(a)lists.umanitoba.ca" <epidata-list-request(a)lists.umanitoba.ca> À : epidata-list(a)lists.umanitoba.ca Envoyé le : Jeudi, 29 Mars 2007, 19h02mn 31s Objet : EpiData-list Digest, Vol 41, Issue 12 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. Duplicate files (epidata-list(a)lists.umanitoba.ca) 2. Changing Confidence Intervals on EpiData Analysis (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Wed, 28 Mar 2007 16:28:37 +0100 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Duplicate files To: <epidata-list(a)lists.umanitoba.ca> Message-ID: <7AC047D44A8CD243B7FE9305102D5FD105D96B27(a)MAIL.bc.iop.kcl.ac.uk> Content-Type: text/plain; charset="us-ascii" Hello I have entered my data twice on epi data and would now like to validate files to make sure that my data is accurate. I have different ID numbers so can not run on Id keys but I have entered the data in the same order so the record numbers match. I have 1 deleted record in one database which I have adjusted for but checking the box that says ignore deleted records. I have 126 records in total when I go to validate files it comes up with an error box saying that it cannot create log file. Does anyone have any ideas on how this could be fixed. Thanx aysha ------------------------------ Message: 2 Date: Thu, 29 Mar 2007 10:51:36 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Changing Confidence Intervals on EpiData Analysis To: <epidata-list(a)lists.umanitoba.ca> Message-ID: <460B9A38020000770000C4B6(a)cs-emo.csir.co.za> Content-Type: text/plain; charset=US-ASCII Hi, I would like the stats I get when doing an epitable to to reflect a 90% CI, instead of the default 95%. Is it possible to do so, and if yes, how? Thanks! REgards Juanette John Natural Resources & the Environment - CSIR PO Box 395 Pretoria 0001 South Africa jjohn(a)csir.co.za Tel 27 12 841 4189 (mornings only) Cell 083 4100 444 Fax 27 12 841 4257/086 6180084 CSIR: "our future through Science" http://www.csir.co.za -- This message is subject to the CSIR's copyright, terms and conditions and e-mail legal notice. Views expressed herein do not necessarily represent the views of the CSIR. CSIR E-mail Legal Notice http://mail.csir.co.za/CSIR_eMail_Legal_Notice.html CSIR Copyright, Terms and Conditions http://mail.csir.co.za/CSIR_Copyright.html For electronic copies of the CSIR Copyright, Terms and Conditions and the CSIR Legal Notice send a blank message with REQUEST LEGAL in the subject line to CallCentre(a)csir.co.za. This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 41, Issue 12 ******************************************** ___________________________________________________________________________ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com

1 0