- EpiData-list - University of Manitoba Mailing Lists

Video tutorial for epidata analysis
by epidata-list＠lists.umanitoba.ca 23 Jun '14

23 Jun '14

Dear All I want to learn to use epidata analysis Does anyone know a good video tutorial or online resource that can help many thanks Thambu

1 1

Video tutorial for epidata analysis
by epidata-list＠lists.umanitoba.ca 23 Jun '14

23 Jun '14

Dear All I want to learn to use epidata analysis Does anyone know a good video tutorial or online resource that can help many thanks Thambu

1 0

Relate - v2.0.0.0 testing
by epidata-list＠lists.umanitoba.ca 19 Jun '14

19 Jun '14

Quick testing of the test version of Manager & Entry Client with relational data forms was successful. I suggest that we be able to move to a child form without having to create a field that just provides the ‘switch’ to go. If we could allow relate to proceed on any value of a field, the jump to the child form would be much like it is now in classic Epidata. This equivalent to an unconditional jump (that is jump on value *). This way, the child form can be invoked as part of a logical flow of data entry without adding an additional field. Jamie

1 1

Revise .epx-file structure during data entry?
by epidata-list＠lists.umanitoba.ca 18 Jun '14

18 Jun '14

Hello list, Data has been entered into foo.epx. Some data could not be entered as values were outside accepted range. Thus, we have to revise foo.epx . How should foo.epx be revised in EpidataManager? By "open file" and revise variable structure or "import file" and....? Nikolai Stenfors

1 1

Unable to open the file
by epidata-list＠lists.umanitoba.ca 18 Jun '14

18 Jun '14

Hello list, Data has been entered using EpidatentryClient 1.41 into foo.epx in an Windows-environment I am unable to open the file in my LInux-environment: Unable to open the file: foo.epx An error occured: In 'stream:' (line 2 pos 1): Root element is missing Any suggestions? Nikolai Stenfors

1 0

Major STEP: First experimental EpiData Manager and EntryClient with RELATIONAL DATA
by epidata-list＠lists.umanitoba.ca 17 Jun '14

17 Jun '14

Dear all A major step in EpiData Project development has been taken during the past weeks and months. It has been rather silent on our point, but that was due to working intensively with relational data capabilities Today we have placed v2.0.0.0 of EpiData Manager as "experimental" here: http://epidata.dk/testing.php#alpha Notice move down. At the top you will find v1.4.4.5 Please experiment with building relational data bases and also "one dataform only" databases to verify function or find problems. An example clinical database with several dataforms is included in the downloads. Before releasing relational data function as a release for "real" projectdata the following is needed: a. Tests by many users (You) b. Development of reporting for multi-dataform projects c. Development of exporting of data in multi-dataform projects d. Fix any bugs reported We hope to fix any reported bugs and points b+c within the next 2-3 weeks. To work with the new principle you will find updated introduction pdf files installed with the software. regards Torsten Bonde Christiansen and Jens Lauritsen EpiData Association Denmark

1 0

V1.4.4.5 available of EpiData Manager for Testing
by epidata-list＠lists.umanitoba.ca 17 Jun '14

17 Jun '14

Dear all On June 11th we have released v1.4.4.5 of EpiData Manager as "pre release candidate" on this page: http://epidata.dk/testing.php at the top. (notice version) Minor bugs have been fixed and internal routines for various aspects of file management have been enhanced. In addition You may now append epx/epz files with the same structure. Append is found in the main menu in "Tools". Unless problems are identified the pre-release v1.4.4.5 will be placed for general public download towards the end of current week. regards Jens Lauritsen Initiator and Coordinator EpiData Association

1 0

Re: EpiData-list Digest, Vol 127, Issue 9
by epidata-list＠lists.umanitoba.ca 14 Jun '14

14 Jun '14

Jamie, Thank you so much for helpful advice - your recipe works! :-) Defining custom command mycmd01 fas very helpful calculating hospital ward utilization starting av certain day: CMD mycmd01 count if (inndato <= aday) and (utdato >= aday) pct=$count/9*100 //Percent utilization of a 9 bed ward type "Beds occupied on @aday : @$count Percent filled : @pct" *** Next statement adds a line to aggregate file sday = sday + $count aday = aday + 1 end // repeating this command necessary number of times. To take this even further, I try to produce a SPC graph of utilization rate variation over time. I thought that I will need an aggregate file with 2 variables: Counting date (aday) and Count (of beds each day). I have tried to use aggregate command combined with repeating the CMD segment obove, but it fails. i have also tried to define a new REC file containing the two variables aday (or inndato) and beds=$count, and put this command into the mycmd01 block: append aday beds /file="aggfile.rec" I have trouble understanding the EpiDaat Process flow... Any hints? best regards, Vegard 2014-05-29 19:03 GMT+02:00 <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. Community Hospital Ward utilization > (epidata-list(a)lists.umanitoba.ca) > 2. Re: Community Hospital Ward utilization > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 29 May 2014 00:08:58 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Community Hospital Ward utilization > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > < > CAOcA-0iU6TNqJJrkPrNOtKBjwWHkhJKfUUWRZs1ib4JVUc8gBg(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Dear list, > I am thinking of designing a monitoring system for a short-term community > hospital ward with 9 beds > > Among variables are > > Patient ID > indate (admission date) <dd/mm/yyyy> inhour admission hour ## > outdate (discharge date) <dd/mm/yyyy> outhour discharge hour ## (not always > recorded) > > Age, sex diagnose1, diagnose2 diagnose3, treatment elements etc. > > Does anybody have a hint on how I can monitor utilization rate, i.e. how > many beds are occupied each day, and average utilization rate per week? > > In Epi Info I would put up a sequence of commands that runs through the > datafile for each consecutive day to count number of patients. in EpiInfo > the PROCESS command would run thhrough the file and do the maths > > I thought a defined variable inhouse # and a counter date > gen d testdate ="01/09/2013" // Opening date > > if testdate < today > then > if testdate >=indate and testdate <=outdate then > inhouse=1 else inhouse=0 > endif > testdate=testdate + 1 > else goto end > endif > > Then route to an aggregate file date, count. > > PROCESS > > But there seems to be no equivalent command in EpiData. I have not figured > out if aggregate or stab could be used for such a purpose. Anye ideas or > hints? > > Best Regards > Vegard HÃ¸gli > Community Medical Officer > Skien, Norway > > > ------------------------------ > > Message: 2 > Date: Wed, 28 May 2014 20:35:37 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Community Hospital Ward utilization > To: EpiData List <epidata-list(a)lists.umanitoba.ca> > Message-ID: <BLU0-SMTP92545148C20845F4C74AC1FD240(a)phx.gbl> > Content-Type: text/plain; charset="windows-1252" > > In Epidata Analysis, you could do something like this for daily > utilization for a whole week: > > read thedatafile > define aday <dd/mm/yyyy> global > define sday #### global > define avbed ###.# > > aday = dmy(?Start day?,?Start month?,?Start year?) // allows you to set a > start date > // add an imif here to check validity of the start date > > sday = 0 > ? “Utilization for the week starting @aday" > > count if (indate <= aday) and (outdate >= a day) > ? “Beds used on @aday : @$count” > sday = sday + $count > aday = aday + 1 > > count if (indate <= aday) and (outdate >= a day) > ? “Beds used on @aday : @$count” > sday = sday + $count > aday = aday + 1 > > // repeat last 4 steps 5 more times > > avbed = float(sday)/7.0 > ? “Average bed count for the week was #avbed” > > Note that the 4 commands starting with count if could be used to define a > cmd to simplify the program. > You could also set aday this way to get the 7 previous days: > > aday = today - 6 > > Jamie > > On May 28, 2014, at 6:08 PM, epidata-list(a)lists.umanitoba.ca wrote: > > > Does anybody have a hint on how I can monitor utilization rate, i.e. how > > many beds are occupied each day, and average utilization rate per week? > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 127, Issue 9 > ******************************************** >

1 1

Community Hospital Ward utilization
by epidata-list＠lists.umanitoba.ca 29 May '14

29 May '14

Dear list, I am thinking of designing a monitoring system for a short-term community hospital ward with 9 beds Among variables are Patient ID indate (admission date) <dd/mm/yyyy> inhour admission hour ## outdate (discharge date) <dd/mm/yyyy> outhour discharge hour ## (not always recorded) Age, sex diagnose1, diagnose2 diagnose3, treatment elements etc. Does anybody have a hint on how I can monitor utilization rate, i.e. how many beds are occupied each day, and average utilization rate per week? In Epi Info I would put up a sequence of commands that runs through the datafile for each consecutive day to count number of patients. in EpiInfo the PROCESS command would run thhrough the file and do the maths I thought a defined variable inhouse # and a counter date gen d testdate ="01/09/2013" // Opening date if testdate < today then if testdate >=indate and testdate <=outdate then inhouse=1 else inhouse=0 endif testdate=testdate + 1 else goto end endif Then route to an aggregate file date, count. PROCESS But there seems to be no equivalent command in EpiData. I have not figured out if aggregate or stab could be used for such a purpose. Anye ideas or hints? Best Regards Vegard Høgli Community Medical Officer Skien, Norway

1 1

password request
by epidata-list＠lists.umanitoba.ca 23 May '14

23 May '14

Hi I am a psychiatric epidemiologist from Uganda and I use epidata for our community research. I have downloaded EpiDataentryclient 1.5.1.0 and while installing it, I was asked for a password. Can anyone provide me with this password. Thank you & very best, Ethel

1 1