- EpiData-list - University of Manitoba Mailing Lists

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

12 Nov '08

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

1 1

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

11 Nov '08

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

1 1

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

09 Nov '08

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

1 0

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

08 Nov '08

Hello Could you please advise what I am doing wrong with my date selection process. I have a field called visitdate. Format = dd/mm/yyyy. The field itself is OK because FREQ visitdate works fine. My problem is when I try to select dates less than 1 July ( 01/07/2008) When I try select visitdate < "01/07/2008" I get an error message "Type Date is incompatible with type String operation aborted" When I try select visitdate < 01/07/2008 I get an error message "Type Date is incompatible with type Float Operation aborted" The only way I could find in the end was to use the month function to create a new field called visitmonth from visitdate and then select visit month <7. This worked, but I want to be able to select on the original visitdate field. Could someone help please? thanks Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 >>> <epidata-list-request(a)lists.umanitoba.ca> 29/11/2007 7:02 a.m. >>> Send EpiData-list mailing list submissions to epidata-list(a)lists.umanitoba.ca To subscribe or unsubscribe via the World Wide Web, visit http://lists.umanitoba.ca/mailman/listinfo/epidata-list or, via email, send a message with subject or body 'help' to epidata-list-request(a)lists.umanitoba.ca You can reach the person managing the list at epidata-list-owner(a)lists.umanitoba.ca When replying, please edit your Subject line so it is more specific than "Re: Contents of EpiData-list digest..." -- The information contained in this email and any attachments is confidential and may be legally privileged. If you have received this message in error, please notify the sender immediately and remove all copies of the message, including any attachments. Any views or opinions expressed in this email (unless otherwise stated) may not represent those of Hutt Valley DHB. Thank you. ** Disclaimer added by HVDHB **

1 1

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

07 Nov '08

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

1 0

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

07 Nov '08

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

1 0

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

04 Nov '08

How can I use Epidata with Lynux?

1 1

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

03 Nov '08

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

1 0

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

02 Nov '08

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

1 0

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

02 Nov '08

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

1 0