- EpiData-list - University of Manitoba Mailing Lists

remove me from this list
by epidata-list＠lists.umanitoba.ca 23 Feb '10

23 Feb '10

remove me from this list

1 0

Status and plans for development (as of February 2010)
by epidata-list＠lists.umanitoba.ca 22 Feb '10

22 Feb '10

This is a brief status of developments - (rather technical in content) It is reassuring to see, that the interest in testing is rather large (Approximate download counts for latest version: Linux 50 , Mac 75 and Windows 300). Few comments have been given on the list, but I take that as a positive indication - I hope I am right, otherwise please notify on the list. The short story is: We are definitely moving forward - the basic way of working in graphic mode with data definition is more or less in place. But we must spend time on implementing related data structures and finding a final data structure. Therefore the first EpiData Entry Client based on the new principles will not come out until some time from now. The longer story is: During the most recent decade use of standardised data formats in public sectors and research has become an increasingly important issue. The idea of this is that data should be usable in any application and system based on published verifiable standards (XML based). XML is one of the structured information formats for machine readable information published by the W3C organisation - and is very complex - other ones from W3C are css and html. The published standards for XML based data documentation and storage of data as such are unfortunately plenty, a few of these are DDI (see DDI-alliance.org), CDISC ODM (see cdisc.org), SDMX (see sdmx.org). It seems as medicine, national statistics and the social sciences each have developed their own. The only common denominator seems to be in relation to overall descriptions such as "title", "contributor", abstract etc. These terms are well known from citations and are based on a metadata set called Dublin Core Metadata (see http://dublincore.org/specifications/). For implementation of a XML based file format in the EpiData Software it would seem obvious to NOT develop a new one, but instead use one or more of the mentioned ones. Therefore there have been discussions with data documentation specialists at the Danish Data Archives (see http://samfund.dda.dk/default-en.asp). Following these discussions and after studying several published standards it has been decided that the EpiData Software XML format will conform to the overall principles of the mentioned standards, but also that we must work with a restricted set of these. The nature of the EpiData project is to be focused on simplicity and we must stick to this principle. Otherwise we would be lost in months of generalisation, of no interest to the general user and also completely unrealistic within the economical and personal resources available. The time frame for the next phases are uncertain, but I will give orientation on this list as improvements are made and obstacles removed. Most likely there will be a meeting in the second week of March in Paris for detailed discussions on some of these issues. More information on that later. regards Jens Lauritsen EpiData Association

1 0

Re: Copy and Paste an Entry
by epidata-list＠lists.umanitoba.ca 17 Feb '10

17 Feb '10

Hello YC, Though i appreciate the solution YMP is giving you, i think you can also think of using the repeat command, since it is more easy play around with. With that you can be able to enter a field once and the next recode the field comes with the previous entry as a default which just needs your confirmation. All the best Edson BN On Tue, Feb 16, 2010 at 10:00 AM, <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: Copy and Paste an Entry? (epidata-list(a)lists.umanitoba.ca) > 2. Re: Copy and Paste an Entry? (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 15 Feb 2010 18:51:52 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: RE: [EpiData-list] Copy and Paste an Entry? > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: <00bf01caae67$8ee97710$acbc6530$@martin-prevel@ird.fr> > Content-Type: text/plain; charset="utf-8" > > Hello, > > I think the best way to get round this problem is to have a relational data > base with two files: > (i) the "Master" file with patient's information > (ii) the related file with daily information > > There are several examples of such related data entry and how it works on > the Epidata website > > Hope this helps > > YMP > > > -----Message d'origine----- > De : epidata-list-bounces(a)lists.umanitoba.ca [mailto: > epidata-list-bounces(a)lists.umanitoba.ca] De la part de > epidata-list(a)lists.umanitoba.ca > Envoyé : lundi 15 février 2010 17:38 > À : epidata-list(a)lists.umanitoba.ca > Objet : [EpiData-list] Copy and Paste an Entry? > > > Hello. I was wondering if it is possible to copy and paste an entry? I am > entering data for patients at a hospital by day, and each time I enter a > new day's entry I have to re-type the patients' information. Is there a way > to copy a previous entry for a patient and paste it on the new entry? > Please help me as this adds a large amount of time to my work. > > Thank you, > YC > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > > ------------------------------ > > Message: 2 > Date: Mon, 15 Feb 2010 13:22:33 -0500 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Copy and Paste an Entry? > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <BLU0-SMTP79433833F8433A3AF41361FD4A0(a)phx.gbl> > Content-Type: text/plain; charset=us-ascii > > See the example titled "Relate example - Clinical Study with four forms" on > the Examples page - click on the link on the main page at epidata.dk > This is how to structure the related files. > See the example titled "Relate example - Household, Person, Visit" to see > how to copy information from one entry screen to another--you do this with > GLOBAL variables. > > This is a very common set up for clinical records. > > Jamie Hockin > Ottawa > > On 2010-02-15, at 11:40 AM, epidata-list(a)lists.umanitoba.ca wrote: > > > > > Hello. I was wondering if it is possible to copy and paste an entry? I am > > entering data for patients at a hospital by day, and each time I enter a > > new day's entry I have to re-type the patients' information. Is there a > way > > to copy a previous entry for a patient and paste it on the new entry? > > Please help me as this adds a large amount of time to my work. > > > > Thank you, > > YC > > _______________________________________________ > > 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 76, Issue 3 > ******************************************* > -- Edson Byamukama Po Box 12027 Kampala, Uganda Office : +256 414251025 Mobile: +256 712202650

1 0

Re: EpiData-list Digest, Vol 76, Issue 3
by epidata-list＠lists.umanitoba.ca 16 Feb '10

16 Feb '10

Hi there, As I am not sure what information you have in your hands, I assume you could add check before the data entry and chose the *repeat* option for the required field information. Consequently, the information will remain until you changed it. Best wishes Tieble On 16 February 2010 18:00, <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: Copy and Paste an Entry? (epidata-list(a)lists.umanitoba.ca) > 2. Re: Copy and Paste an Entry? (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 15 Feb 2010 18:51:52 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: RE: [EpiData-list] Copy and Paste an Entry? > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: <00bf01caae67$8ee97710$acbc6530$@martin-prevel@ird.fr> > Content-Type: text/plain; charset="utf-8" > > Hello, > > I think the best way to get round this problem is to have a relational data > base with two files: > (i) the "Master" file with patient's information > (ii) the related file with daily information > > There are several examples of such related data entry and how it works on > the Epidata website > > Hope this helps > > YMP > > > -----Message d'origine----- > De : epidata-list-bounces(a)lists.umanitoba.ca [mailto: > epidata-list-bounces(a)lists.umanitoba.ca] De la part de > epidata-list(a)lists.umanitoba.ca > Envoyé : lundi 15 février 2010 17:38 > À : epidata-list(a)lists.umanitoba.ca > Objet : [EpiData-list] Copy and Paste an Entry? > > > Hello. I was wondering if it is possible to copy and paste an entry? I am > entering data for patients at a hospital by day, and each time I enter a > new day's entry I have to re-type the patients' information. Is there a way > to copy a previous entry for a patient and paste it on the new entry? > Please help me as this adds a large amount of time to my work. > > Thank you, > YC > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > > ------------------------------ > > Message: 2 > Date: Mon, 15 Feb 2010 13:22:33 -0500 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Copy and Paste an Entry? > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <BLU0-SMTP79433833F8433A3AF41361FD4A0(a)phx.gbl> > Content-Type: text/plain; charset=us-ascii > > See the example titled "Relate example - Clinical Study with four forms" on > the Examples page - click on the link on the main page at epidata.dk > This is how to structure the related files. > See the example titled "Relate example - Household, Person, Visit" to see > how to copy information from one entry screen to another--you do this with > GLOBAL variables. > > This is a very common set up for clinical records. > > Jamie Hockin > Ottawa > > On 2010-02-15, at 11:40 AM, epidata-list(a)lists.umanitoba.ca wrote: > > > > > Hello. I was wondering if it is possible to copy and paste an entry? I am > > entering data for patients at a hospital by day, and each time I enter a > > new day's entry I have to re-type the patients' information. Is there a > way > > to copy a previous entry for a patient and paste it on the new entry? > > Please help me as this adds a large amount of time to my work. > > > > Thank you, > > YC > > _______________________________________________ > > 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 76, Issue 3 > ******************************************* >

1 0

Copy and Paste an Entry?
by epidata-list＠lists.umanitoba.ca 15 Feb '10

15 Feb '10

Hello. I was wondering if it is possible to copy and paste an entry? I am entering data for patients at a hospital by day, and each time I enter a new day's entry I have to re-type the patients' information. Is there a way to copy a previous entry for a patient and paste it on the new entry? Please help me as this adds a large amount of time to my work. Thank you, YC

1 1

Copy and Paste an Entry?
by epidata-list＠lists.umanitoba.ca 15 Feb '10

15 Feb '10

Hello. I was wondering if it is possible to copy and paste an entry? I am entering data for patients at a hospital by day, and each time I enter a new day's entry I have to re-type the patients' information. Is there a way to copy a previous entry for a patient and paste it on the new entry? Please help me as this adds a large amount of time to my work. Thank you, YC

1 1

Export to excel with Filter using Checkcode
by epidata-list＠lists.umanitoba.ca 08 Feb '10

08 Feb '10

Hi Just sharing my experience with the users here in calling Export command of Epic from check file in Epidata The Dos command looks like this c:\EpiC e excel d:\ves101\ves101.rec d:\ves101\VIV02081919_FARI.xls filter="fari1yes2n=1" DELETED REPLACE However when I try the same in the check file, the filter did not get applied My check file looks like this sourcedir = "d:\ves101\" INVES2 = COPY(INVESTIGAT,1,3) mth2 = string(month(today)) d2 = string(day(today)) hr2 = string(hr) mins3 = string(mins2) recfile = sourcedir+"ves101.rec" fariout = sourcedir+INVES2+mth2+d2+hr2+mins3+"_FARI.xls" execute c:\epic.exe "e excel @recfile @fariout filter="fari1yes2n=1" DELETED REPLACE" wait The EpiC.log file shows the following Command: EpiC e excel d:\ves101\ves101.rec d:\ves101\VIV02081928_FARI.xls DELETED REPLACE 2/8/2010 7:29:15 PM Exporting d:\ves101\ves101.rec to d:\ves101\VIV02081928_FARI.xls Exports to: Excel Records: All Filter: None Deleted records in inputfile are included in export 7 records with 18 fields exported I can see that the " " around the Filter are creating the problem. Single quotes did not work Command: EpiC e excel d:\ves101\ves101.rec d:\ves101\VIV02081952_FARI.xls filter='fari1yes2n=1' DELETED REPLACE 2/8/2010 7:52:25 PM Exporting d:\ves101\ves101.rec to d:\ves101\VIV02081952_FARI.xls Exports to: Excel Records: All Filter: 'fari1yes2n=1' Deleted records in inputfile are included in export 0 records with 18 fields exported Finally what did the trick was simply to remove the "" execute c:\epic.exe "e excel @recfile @fariout filter=fari1yes2n=1 DELETED REPLACE" wait EpiC Log shows: Command: EpiC e excel d:\ves101\ves101.rec d:\ves101\VIV02081955_FARI.xls filter=fari1yes2n=1 DELETED REPLACE 2/8/2010 7:54:38 PM Exporting d:\ves101\ves101.rec to d:\ves101\VIV02081955_FARI.xls Exports to: Excel Records: All Filter: fari1yes2n=1 Deleted records in inputfile are included in export 5 records with 18 fields exported I hope this information would be of use to some of the members. Am psoting it as searching through the archives did not yield much. Another thing I noted was that the Zip files created by EpiC can not be opened by WinRAR or PkZIP on my machine though EPiC can extract the same just fine. Thanks ,Dr. Vivek Gupta, MBBS, MD (Community Medicine)All India Institute of Medical Sciences New Delhi. Phone: (+91)9899410420 Alt. E-mail: drvivek(dot)gupta(at)gmail(dot)com

1 0

Ruwan Ratnayake est absent.
by epidata-list＠lists.umanitoba.ca 29 Jan '10

29 Jan '10

Je serai absent(e) du Ven 22/01/2010 au Mer 17/02/2010. Bonjour! Veuillez prendre note que je serai absente de mon bureau le 25 janvier au 15 février. I will be out of the office from January 25-February 15. I will reply to your message upon my return. Ruwan

1 0

entering arabic letters
by epidata-list＠lists.umanitoba.ca 29 Jan '10

29 Jan '10

Dear All, At our office, we are using epidata since 2003 for our local applications. Using MS office 2003, windows XP, we were entering our data using epidata3.1 in English version, but we have kept some variables for entering names using Arabic letters. Later, the .rec file was exported to excel in order to search for duplicates using the Arabic letters. It has worked. Yesterday, we had a new desktop with MS office 2007. That function of entering data using Arabic letters has disappeared. Do you have any idea why this happened? And how can we solve this matter? Sincerely Nada Ghosn, Eman Chamas, Epidemiological Surveillance Program Ministry of Public Health Beirut Lebanon

1 2

testing manager version 0.3.2.9
by epidata-list＠lists.umanitoba.ca 28 Jan '10

28 Jan '10

Heemskerk 28/01/2010 Hello JENS and ALL, While testing this I got a message when I tried to read a DBF file, it says that it is a corrupted ZIPfile !! In true it is a perfect DBF file made by EPIDATA 3.1. Reading TXT, CSV, REC, QES files works perfect. Shifting the fields on the screen with the mouse : OK. Would appreciate more explanation about the SETTINGS, not all clear to me. A possibility to change the type of an already existing field would be nice.. I add a recxml file that contains some remarks. Yours, Louk. <?xml version="1.0"?> <EPIDATA> <SETTINGS> <VERSION>0</VERSION> <DATESEP>/</DATESEP> <DECIMALSEP>.</DECIMALSEP> <MISSINGMARK>.</MISSINGMARK> </SETTINGS> <METADATA> <LABELS> </LABELS> </METADATA> <FIELDS> <FIELD TYPE="15"> <NAME>label_1</NAME> <TAG>F1</TAG> <LENGTH>0</LENGTH> <DECIMALS>0</DECIMALS> <POS X="31" Y="19"/> <LABEL X="31" Y="19">Label text to clarify PURPOSE file.</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="15"> <NAME>label_2</NAME> <TAG>F2</TAG> <LENGTH>0</LENGTH> <DECIMALS>0</DECIMALS> <POS X="31" Y="43"/> <LABEL X="31" Y="43">++++++++++++++++++++++++++++++++++++</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="1"> <NAME>V1-short string</NAME> <TAG>F3</TAG> <LENGTH>10</LENGTH> <DECIMALS>0</DECIMALS> <POS X="198" Y="68"/> <LABEL X="130" Y="73">[SHORTY]</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="1"> <NAME>V2-long string100</NAME> <TAG>F4</TAG> <LENGTH>100</LENGTH> <DECIMALS>0</DECIMALS> <POS X="198" Y="118"/> <LABEL X="123" Y="123">[VERYlong]</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="15"> <NAME>label_5</NAME> <TAG>F5</TAG> <LENGTH>0</LENGTH> <DECIMALS>0</DECIMALS> <POS X="198" Y="144"/> <LABEL X="198" Y="144">Very nice that such a long field is possible !!!!.</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="0"> <NAME>V3-Integer</NAME> <TAG>F6</TAG> <LENGTH>4</LENGTH> <DECIMALS>0</DECIMALS> <POS X="198" Y="194"/> <LABEL X="133" Y="199">[Number]</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="6"> <NAME>V4-Floaty</NAME> <TAG>F7</TAG> <LENGTH>11</LENGTH> <DECIMALS>6</DECIMALS> <POS X="198" Y="224"/> <LABEL X="130" Y="229">[Floatfield]</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="11"> <NAME>V5-Holiday</NAME> <TAG>F8</TAG> <LENGTH>10</LENGTH> <DECIMALS>0</DECIMALS> <POS X="198" Y="267"/> <LABEL X="112" Y="272">[Normaldate]</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="16"> <NAME>V6-THISDAY</NAME> <TAG>F9</TAG> <LENGTH>10</LENGTH> <DECIMALS>0</DECIMALS> <POS X="198" Y="297"/> <LABEL X="120" Y="302">[Todayfield]</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="12"> <NAME>V7-IDfield</NAME> <TAG>F10</TAG> <LENGTH>4</LENGTH> <DECIMALS>0</DECIMALS> <POS X="198" Y="350"/> <LABEL X="74" Y="355">[RECORDNUMBER]</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="15"> <NAME>label_3</NAME> <TAG>F11</TAG> <LENGTH>0</LENGTH> <DECIMALS>0</DECIMALS> <POS X="72" Y="399"/> <LABEL X="72" Y="399">NOTE ! Each time when I click in a field , this field moves one pixel to the bottom. !!!</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="15"> <NAME>label_4</NAME> <TAG>F12</TAG> <LENGTH>0</LENGTH> <DECIMALS>0</DECIMALS> <POS X="143" Y="428"/> <LABEL X="143" Y="428">Writing the FIEDLABELS between square brackets keeps the aspect tidy...</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> </FIELDS> <RECORDS> </RECORDS> </EPIDATA>

1 0