Posed indirectly:
>Can anyone help me with the following question?
>Is there a function on EpiData Entry which allows data to be
>repeated from one record to the other (without the data enterer
>having to fill in all the same data again)?
>
>For example, we are interviewing all the family members in 10
>different households. On the record of each household member, the
> 'household' data will be the same, but their individual data will be
> different. We want the household data to appear on each record
>without the data enterer having to re-enter all the data.
>
>Is it possible to put a command in the .chk file so the data is
>re-entered on that record automatically?
>
>For Example:
>Qu: Does this individual belong to the same household as the
>previous record? (If the answer is yes, the 'household data' will
> automatically replicate that of the previous record).
>Thanks in advance for your advice,
>
> Dr Jean-Francois Trani
> Leonard Cheshire Disability and Inclusive Development Centre
> University College London
> Website: www.lcdisability.org/idc
Answer:
This can be done with the "repeat" and "clear" feature. An example has
been uploaded to the page http://www.epidata.dk/examples.php
................................................................................................................
Extract of chk file is:
same
COMMENT LEGAL USE label_same
MUSTENTER
type comment allfields Blue
AFTER ENTRY
IF same = 2 THEN
CLEAR class
CLEAR school
ELSE
GOTO age
ENDIF
END
END
school
COMMENT LEGAL USE label_school
REPEAT
END
................................................................................................................
regards
Jens Lauritsen
EpiData Association
Hi.
Hi.
Can Epidata fetch data from one or more database and add up the data in
Epidata database?
Is Epidata safe for using in matters of social security numbers etc.?
Thanks in advance/
Uffe.
Dear All
We are approaching finalisation of the current SPC graph implementation
in EpiData Analysis. But await comments and further testing by users and
specialists. Some errors were found in build 155 for Ichart-moving range
charts. Today build 156 has been uploaded.
Since public release of v2.1.0 the following SPC graphs have been
implemented in the test version 2.1.1. build 156 available from
http://www.epidata.dk/testing.php :
Gchart, UChart, XBar (Sigma and Range), CChart, Ichart moving range
Apart from the new commands it would be good if users would comment
further on the new aspects of v2.1, e.g. the current implementation of
lifetables. How is it working in practice, is the help file sufficient etc.
An issue was raised on the list regarding use of "actuarial versus
Kaplan-Meier" principles. It seems as if this relates to use of floating
point variables (e.g. 1.4 week) for the time variable, which now is read
as a rounded integer variable. Following further clarification I will
notify here.
Next in line in the development is release of a translation tool, such
that analysis can be translated in a "smooth" way. And in analysis
further implementation of "set ...." will be added to facilitate easier
default setting of user options. The following general "set" will be added:
set graph option=" ......" (for all graphs)
set table option=" ......" (for cross tables and frequency tables)
set spc option=" ..... " (for spc graphs and analysis)
Possible also the following will be added for means, describe etc.: set
descriptive option="..... "
regards
Jens Lauritsen
EpiData Association
Thank you for your response to my date question.
During entry, if the date field is not applicable to a certain record
(whereas I do not need to enter a date for that specific record, rather
skip it) what do I designate as my skip code. I did have -77, but when I
would enter that, it would say it was an illegal entry.
How do I write the code, so that a skip is -77, and it still be a legal
entry in some instances?
legdat
RANGE 01/01/1900 31/12/2008
LEGAL
30/12/2009
24/11/2008
END
END
(somewhere in there, I need to put it a skip code)
Thank you for your time,
Lindsay
Lindsay Iser, M.A.
University of South Florida
Florida Mental Health Institute
Department of Aging and Mental Health
13301 N. Bruce B. Downs BlVd.
MHC 1403
Tampa, FL 33612
Tel-(813)-974-1975
Fax-(813)-974-1968
-----Original Message-----
From: epidata-list-bounces(a)lists.umanitoba.ca
[mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of
epidata-list-request(a)lists.umanitoba.ca
Sent: Thursday, November 13, 2008 1:10 PM
To: epidata-list(a)lists.umanitoba.ca
Subject: EpiData-list Digest, Vol 61, Issue 7
Send EpiData-list mailing list submissions to
epidata-list(a)lists.umanitoba.ca
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.umanitoba.ca/mailman/listinfo/epidata-list
or, via email, send a message with subject or body 'help' to
epidata-list-request(a)lists.umanitoba.ca
You can reach the person managing the list at
epidata-list-owner(a)lists.umanitoba.ca
When replying, please edit your Subject line so it is more specific
than "Re: Contents of EpiData-list digest..."
EpiData-list mailing list
___________________________________
Today's Topics:
1. Re: "Illegal entry" Dates (epidata-list(a)lists.umanitoba.ca)
2. charting developments in hospital infections - extension
(epidata-list(a)lists.umanitoba.ca)
3. Re: Algorithm RUT, numeric field (epidata-list(a)lists.umanitoba.ca)
----------------------------------------------------------------------
Message: 1
Date: Wed, 12 Nov 2008 20:21:14 +0100
From: epidata-list(a)lists.umanitoba.ca
Subject: Re: [EpiData-list] "Illegal entry" Dates
To: epidata-list(a)lists.umanitoba.ca
Message-ID: <491B2CAA.1090708(a)tbrieder.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
You cannot have illegal dates: 99, -77, 88 are not dates and if they
were, they are not legal, there is no date that contains, e.g. "99". A
command for a legal date range and legal date values should look
something like this (using European date format here):
legdat
RANGE 01/01/1900 31/12/2008
LEGAL
30/12/2009
24/11/2008
END
END
Regards,
Hans
epidata-list(a)lists.umanitoba.ca wrote:
> Provided below is the syntax. I've also made a few notes about the
> error I am getting. I have tried several times to fix this, but for
> some reason EpiData is telling me it is illegal.
>
>
>
> 1. fa163axxxx
>
> RANGE 01/01/1900 12/31/2008
>
> LEGAL
>
> 99
>
> -77
>
> 88
>
> END
>
> MUSTENTER
>
> END
>
>
>
--
Hans L Rieder, MD, MPH
Jetzikofenstrasse 12
3038 Kirchlindach
Switzerland
Tel: +41 31 829 4577
Mob: +41 79 321 9122
Web: http://wwww.tbrieder.org
------------------------------
Message: 2
Date: Thu, 13 Nov 2008 00:18:43 +0100
From: epidata-list(a)lists.umanitoba.ca
Subject: [EpiData-list] charting developments in hospital infections -
extension
To: epidata-list(a)lists.umanitoba.ca
Message-ID: <491B6453.9070802(a)epidata.dk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Regarding the most recent question to the list on MRSA infections, users
could read these articles:
Mohammed MA, Worthington P, Woodall WH. Results of a multicentre
randomised controlled trial of statistical process control charts and
structured diagnostic tools to reduce ward-acquired meticillin-resistant
Staphylococcus aureus: the CHART Project.J Hosp Infect. 2008
Oct;70(2):127-35. Epub 2008 Aug 23.
Curran E, Harper P, Loveday H, Gilmour H, Jones S, Benneyan J, Hood J,
Pratt R.
Results of a multicentre randomised controlled trial of statistical
process control charts and structured diagnostic tools to reduce
ward-acquired meticillin-resistant Staphylococcus aureus: the CHART
Project.J Hosp Infect. 2008 Oct;70(2):127-35. Epub 2008 Aug 23.
Borckardt JJ, Nash MR, Hardesty S, Herbert J, Cooney H, Pelic C.
How unusual are the "unusual events" detected by control chart
techniques in healthcare settings? J Healthc Qual. 2006
Jul-Aug;28(4):4-9.
regards Jens Lauritsen
EpiData Association
------------------------------
Message: 3
Date: Thu, 13 Nov 2008 08:20:31 -0500
From: epidata-list(a)lists.umanitoba.ca
Subject: Re: [EpiData-list] Algorithm RUT, numeric field
To: epidata-list(a)lists.umanitoba.ca
Message-ID: <491C299F.3030509(a)sympatico.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
There is an example of this, based on the Danish CPR number on the
Epidata web site: http://www.epidata.dk/examples.php
The example is in English & Danish, with an explanation in English.
You input the number as a single text field and then "take it apart"
into its individual digits.
Jamie
Carlos wrote wrote:
> I would like to know if I can read a numeric field and break down
their
> individual one-digit figure.
> This, with the intention of obtaining the digit verifier (dv) of a
RUT.
>
> I tried an algorithm, but I have to make individual fields for each
digit,
>
>
------------------------------
________________________________________
EpiData-list(a)lists.umanitoba.ca
http://lists.umanitoba.ca/mailman/listinfo/epidata-list
End of EpiData-list Digest, Vol 61, Issue 7
*******************************************
I'm from Chile (South America), my native language is Spanis... I write a
draft text below.
Estimados amigos,
Me gustaria saber si puedo leer un campo numérico y descomponer
individualmente sus dígitos de aquella cifra.
Esto, con la intención de obtener el digito verificador(dv) de un RUT.
Intenté un algoritmo, pero tengo que hacer campos individuales para cada
digito, que no es la idea, lo que hago es:
R1# R2# R3# R4# R5# R6# R7# R8# -dv<A>
entonces ingreso:
3 0 6 8 6 9 5 7 -dv 4(este surge del
algoritmo)
Me gustaria que fuese asi:
RUT ######## -dv<A> (este surga del algoritmo)
30686957 -dv 4
Les agradesco mucha vuestra colaboración.
Carlos Ortega Areyte
Academico
Procedimiento para obtener el dígito verificador.
--------------------------------------------------
El RUT consta de dos partes, el número y el dígito verificador separados por
un guión.
En el siguiente ejemplo se toma como RUT el número 30.686.957- X,
donde 30.686.957 es el número del RUT y X será el dígito verificador que se
desea verificar o conocer:
- Se procede a tomar el número de RUT de derecha a izquierda,
multiplicando cada dígito por los números que componen la serie numérica
2,3,4,5,6,7; y sumando el resultado de estos productos,
como se muestra a continuación (si se ha aplicado la serie hasta el 7 y
quedan dígitos por multiplicar, se comienza la serie nuevamente):
En el ejemplo:
7 × 2 = 14,
5 × 3 = 15,
9 × 4 = 36,
6 × 5 = 30,
8 × 6 = 48,
6 × 7 = 42,
0 × 2 = 0,
3 × 3 = 9,
entonces la suma de los productos es: 14+15+36+30+48+42+0+9 = 194
- Al número obtenido por la suma del producto de cada dígito por la serie ya
mencionada, se le aplica módulo 11,
o sea, se divide por 11 y se determina el resto de la división.
En el ejemplo:
194: 11 = 17
Resto: 7
Ahora a 11 se le resta el resto:
En el ejemplo:
11 - 7 = 4
Si el resultado es 11, el dígito verificador será 0.
Si el resultado es 10, el dígito verificador será K.
En otro caso el resultado será el dígito verificador.
Como en el ejemplo el resultado de la resta es 4, el dígito verificador es
4.
Por ende, el RUT del ejemplo es el 30.686.957-4.
Por cierto, este ejemplo lo Obtuve de es.wikipedia.org
************** **************
*******************************
This is a translation,
I'm from Chile (South America), my native language is Spanish ... sorry my
little English.
Dear friends,
I would like to know if I can read a numeric field and break down their
individual one-digit figure.
This, with the intention of obtaining the digit verifier (dv) of a RUT.
I tried an algorithm, but I have to make individual fields for each digit,
that is not the idea, what I do is:
R1 # R2 # R3 # R4 # R5 # R6 # # R7 R8 # -dv <A>
then login:
3 0 6 8 6 9 5 7 dv- 4 (this born from the
algorithm)
I would like it to be like this:
RUT ######## -dv <A> (this born from the algorithm)
30686957 -dv 4
Thank you very much for your cooperation.
Carlos Ortega Areyte
Academic
Obtain the procedure for verifying digit.
--------------------------------------------------
The RUT is in two parts, the number and verifying digit separated by a
hyphen.
In the following example is taken as RUT number 30686957 - X,
where 30686957 is the number of RUT and X will be the verifying digit you
want to know or verify:
- We shall proceed to take the number of RUT from right to left,
by multiplying each digit numbers that make up the numerical series
2,3,4,5,6,7; and adding the output of these products,
as shown below (if the series has been implemented and are up to 7 digits
per leverage, the series begins again):
In the example:
7 x 2 = 14
5 x 3 = 15,
9 × 4 = 36
6 x 5 = 30,
8 × 6 = 48
6 x 7 = 42
0 x 2 = 0,
3 x 3 = 9
then the sum of products is: 14 +15 +36 +30 +48 +42 +0 +9 = 194
- The number obtained by the amount of the proceeds of each digit in the
series already mentioned, it is covered module 11,
in other words, is divided by 11 and determining the rest of the division.
In the example:
194: 11 = 17
Rest: 7
Now he is a 11 subtracts the rest:
In the example:
11-7 = 4
If the result is 11, the verifier digit will be 0.
If the result is 10, will be verifying digit K.
Otherwise the result will be verifying digit.
As in the example the result of the remainder is 4, the digit verifier is 4.
Thus, the RUT's example is the 30.686.957- 4.
this example of what I got es.wikipedia.org
--
Carlos A. Ortega Areyte
Prof. de Matemática y Computación
Magíster en Bioestadística
ACADÉMICO
Regarding the most recent question to the list on MRSA infections, users
could read these articles:
Mohammed MA, Worthington P, Woodall WH. Results of a multicentre
randomised controlled trial of statistical process control charts and
structured diagnostic tools to reduce ward-acquired meticillin-resistant
Staphylococcus aureus: the CHART Project.J Hosp Infect. 2008
Oct;70(2):127-35. Epub 2008 Aug 23.
Curran E, Harper P, Loveday H, Gilmour H, Jones S, Benneyan J, Hood J,
Pratt R.
Results of a multicentre randomised controlled trial of statistical
process control charts and structured diagnostic tools to reduce
ward-acquired meticillin-resistant Staphylococcus aureus: the CHART
Project.J Hosp Infect. 2008 Oct;70(2):127-35. Epub 2008 Aug 23.
Borckardt JJ, Nash MR, Hardesty S, Herbert J, Cooney H, Pelic C.
How unusual are the "unusual events" detected by control chart
techniques in healthcare settings? J Healthc Qual. 2006 Jul-Aug;28(4):4-9.
regards Jens Lauritsen
EpiData Association
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
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
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
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 **