- EpiData-list - University of Manitoba Mailing Lists

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