- EpiData-list - University of Manitoba Mailing Lists

new test release of EpiData Manager available
by epidata-list＠lists.umanitoba.ca 26 May '10

26 May '10

Dear All Due to funding received (and more expected) the development phase has been lengthened to summer 2011 allowing for the continuation of T.Christiansen to work fulltime on the restructuring. All programming is now done in Freepascal and Lazarus. The development of the EpiData Manager has now come to a new stage, where test versions will be released with shorter intervals. The release will happen in these steps: a. Test placement of fields in data entry forms. Move fields, add sections. Only one form is allowed. Edit variable labels (questions). b. Include previous data structures on a form. Will import rec files and dta (stata) files. c. Write data files and export data structures to rec file and dta files d. Start development of a dedicated entry client. e. Add definition and editing of category labels (value labels). f. Add to data forms the possibility of translating labels and questions If all goes well points a-f will be ready within the next few months. After this a new planning sequence will include relational aspects and multi entry forms of the same project, user access control and other coming aspects. The first new release mentioned above (a) was released earlier today from http://www.epidata.dk/testing.php for the operating systems Linux, Mac and Windows. It will seem as a backstep in relation to the previous test version, but we are approaching the same level with a completely new final XML data file structure. The new structure will accomodate all we would like and will be visible in the next stage (b), where users can see the xml structure. ---------------------------------------------------------------------- This first release is covering what happens in the definition of a single data form. Including the addition of new fields, new sections and heading lines. A section is a sub-division of a single data entry form. A section has NOT been used previously in EpiData software and contains a number of fields. Jumps will allow jumps between sections and user access control will be at the section level. When you first start the application you will see two sections, which can be moved, edited and deleted. Jens Lauritsen EpiData Association

1 2

EpiData Manager v0.5
by epidata-list＠lists.umanitoba.ca 26 May '10

26 May '10

Good to see progress with the Manager. I have some questions and thought that this would be the appropriate forum rather than the flyspray bug reporting system. At present, is the string variable created equivalent to the variable created in Entry with the underscore? If so, will uppercase strings be supported? Is it possible to resize the section box after its creation other than through the advanced tab and changing the numbers therein? Is it possible to copy and paste fields with a view to subsequent amendment of field names? This is important with a view to rapid data-form creation. I've done a test and it seems to work. I'll post a query on flyspray with regards to opening the Help file within the Manager which I can't do. Regards, Neville ----------------------------------------- ************************************************************************** The information contained in the EMail and any attachments is confidential and intended solely and for the attention and use of the named addressee(s). It may not be disclosed to any other person without the express authority of the HPA, or the intended recipient, or both. If you are not the intended recipient, you must not disclose, copy, distribute or retain this message or any part of it. This footnote also confirms that this EMail has been swept for computer viruses, but please re-sweep any attachments before opening or saving. HTTP://www.HPA.org.uk **************************************************************************

1 0

Introduction document and help in the new Manager
by epidata-list＠lists.umanitoba.ca 26 May '10

26 May '10

The manager contains a "help" menu. On this two entries are found. : 1 short introduction 2 show shortcuts The first one (introduction) will check first if the file "epidatamanagerintro.pdf" is present in the location on your computer, where you stored the manager exe file. If so the file is opened in the local pdf reader. If not present the standard internet browser will open the document: http://epidata.dk/downloads/epidatamanagerintro.pdf If you then save the file in the same folder as the exe file, the local copy will be opened thereafter. 2 show shortcuts This will open the "wiki" documentation system directly via internet. If you have no current internet connection an error will appear in your browser. regards Jens Lauritsen EpiData Association

1 0

Few Clarifications about New Epidata Manager Developments
by epidata-list＠lists.umanitoba.ca 08 May '10

08 May '10

Dear Jens, It is heartening to hear that further developments of Epidata are going on. I just have few points (apprehensions) which I want to share with you. The ability to correct the data file by a text editor (in new system) sounds wonderful but existing system is also good. 1. Will the new system continue support the already developed relation databases in Epidata Entry ? Will it be downward compatible with the relational databases systems already working well in Epidata Entry 3.1 and Analysis 2.3 ? 2. The QES, CHK, REC file system was comparatively simple and one could change it whenever wanted, without being a software professional (programmer). With regards, Dr. Shavinder Singh

1 0

status april 2010 for rewriting of core and EpiData Manager
by epidata-list＠lists.umanitoba.ca 29 Apr '10

29 Apr '10

Dear all Since release of last trial version of the new EpiData Manager in January around 1000 copies have been downloaded from the testing.php website at epidata.dk. Since then we (Torsten Christiansen and I) have worked on ways of implementing the more subtle parts of the old rec file system in the new format, which is described at http://www.epidata.org/dokuwiki/doku.php/documentation:datafileformat:xml_v0 The description is not completely up to date, but will be updated soon. The challenge was to also include relate, encryption and principles for translation of data forms in a structured way. This has now been completed and I expect a new release for testing within some weeks. In the final file format all contents will be contained in one physical file formulated in XML and in compliance with the w3c.org validator for an xml file. The basic blocks implemented will be: - user access control block - a list of control structures, e.g. specification of relationship btw. files - a list of tables contained (each like an old rec file) - in each table a number of sections - in each section a number of fields. - each field having a number of attributes, such as type (integer, string etc), controls etc. The file will contain the combination of all current rec and chk files for a given project. User control will be at the section level. Many users will now think "Oh-no" they changed the simplicity principle of REC-CHK-QES and created a monster system with many problems. This is however NOT the case. For a simple project the file content structure is of no interest to the user and will appear simple. But by containing all in one physcal file it should become much easier to keep track of the data for a given project. Basicly with the new structure files can also be edited in a standard editor. The complete rewriting is expected to be completed in about one year from now, and funding is still welcomed for the process. regards Jens Lauritsen EpiData Association

1 0

Access violation error with Codebook command in EpiData (second try)
by epidata-list＠lists.umanitoba.ca 29 Apr '10

29 Apr '10

Hi! When trying to create a Codebook I get an access violation error. I have tried to carefully revise the check file with no result. The error seems to be related to only fields named with the pattern "xxxcom" which all are string variables. -If I choose all fields before "xxxcom" the Codebook for those variables will be created without error. -If I only check "xxxcom" --> access violation -If I check variables before and after "xxxcom" --> access violation -If I check only variables after "xxxcom" -->no error Error message: "Access violation at address 00403347 in module 'EpiData.exe' Read of address 393938FB" Epidata 3.1 (270108) Windows XP Pro Thanks for help Jonas Malmstedt, MD Department of Vascular Surgery, N1:06 Karolinska University Hospital SE-171 76 Stockholm PS I have also noticed another problem: smtimes EpiData Will not read *.not and *.rec files. I get an error telling me that the file name are not valid or the file is used. When I try to open the same file not NotePad - no problem! DS

1 1

Re: EpiData-list Digest, Vol 78, Issue 17
by epidata-list＠lists.umanitoba.ca 29 Apr '10

29 Apr '10

When you prepare the rec file for double entry better to leave the box "Match by record" unchecked. However if the double entry appears to slow or cause some frustration, perhaps it might be better to use copy structure and enter the data for comparison. Tieble On 29 April 2010 18:06, <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: Double Entry for Related Files > (epidata-list(a)lists.umanitoba.ca) > 2. Access violation error with Codebook command in EpiData > (second try) (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 28 Apr 2010 13:48:41 -0500 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] RE: Double Entry for Related Files > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: > <679902537E215D43805DEA9BE833090E042A5B80(a)NORCEX1.norc.org> > Content-Type: text/plain; charset="us-ascii" > > I understand the two different methods of double-entering data, and I do > indeed want to "prepare for double-entry". The problem is that when I > go to prepare the questionnaire for double entry, I can only choose to > prepare either the parent OR the child file. If I choose the parent > file, then a double-entry file is only created for the parent file - > when I open it to double enter the data, it relates to the original > child file, so it opens the parent double entry file along with the > original child file. Since only one of the two files is a double entry > file, the program thinks I am entering the data for the first time, and > does not compare the alues entered to the values from the original file. > > > > > I cannot seem to find a way to prepare both the parent and the child > file for double entry together. If I prepare them for double entry > separately, I run into similar problems. > > > > Sam > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Tue, 27 Apr 2010 19:13:58 +0200 > > From: epidata-list(a)lists.umanitoba.ca > > Subject: Re: [EpiData-list] Double Entry for Related Files > > To: epidata-list(a)lists.umanitoba.ca > > Message-ID: <4BD71B56.7020800(a)tbrieder.org> > > Content-Type: text/plain; charset=UTF-8; format=flowed > > > > Hi Sam: > > > > There are two approaches to double-enter: 1) independently, 2) the > second file depending on the first. You seemingly chose the latter > ("prepare for double-entry"). If you choose that option, you must enter > the records in the same sequence (I believe) and the value of each field > in the second record will be compared to the corresponding one in the > first and a discordance reported, so you can verify. Thus, no need to > enter twice. > > > > Alternatively, you enter your related file pairs independently between > first and second entry. You must have a unique identifier in both the > parent and the child file. The sequence then doesn't matter of course. > > > After you have entered parent1-child1 and parent2-child1, you validate > > parent1-vs-parent2 on the unique identifier, then child1-vs-child2 on > that identifier. > > > > Hans > > > > On 20:59, epidata-list(a)lists.umanitoba.ca wrote: > > > Hi, > > > > > > I have a questionnaire that uses two related .rec files for data > entry. > > > I want to double enter the data by checking for discrepancies as the > > > data is entered the second time. Is it possible to do this for > > > questionnaires that span two .rec files? When I try to prepare for > > > double entry, the program creates a "file1_dbl.rec" file, but relates > > > it to the "file2.rec" file rather than creating a "file2_dbl.rec" file > > > > to compare against. > > > > > > I am thinking that I will just have to un-relate the file, and enter > > > and double-enter the survey in two parts, but any help would be > appreciated. > > > > > > Thanks, > > > > > > Sam > > > > > > > -- > > 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 > > > > > > > > > > > > > > > > -- > > Samuel Haddaway > > Research Assistant, International Projects > > National Opinion Research Center > > haddaway-sam(a)norc.org > > Phone: 301.634.9423 > > > > > > ------------------------------ > > Message: 2 > Date: Wed, 28 Apr 2010 21:50:13 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Access violation error with Codebook command > in EpiData (second try) > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <OF120C2D35.551C97A0-ONC1257713.006CF7D1-C1257713.006CF7D4(a)sll.se> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi! > When trying to create a Codebook I get an access violation error. I have > tried to carefully revise the check file with no result. The error seems to > be related to only fields named with the pattern "xxxcom" which all are > string variables. > -If I choose all fields before "xxxcom" the Codebook for those variables > will be created without error. > -If I only check "xxxcom" --> access violation > -If I check variables before and after "xxxcom" --> access violation > -If I check only variables after "xxxcom" -->no error > > Error message: > "Access violation at address 00403347 in module 'EpiData.exe' Read of > address 393938FB" > > Epidata 3.1 (270108) > Windows XP Pro > > Thanks for help > > Jonas Malmstedt, MD > Department of Vascular Surgery, N1:06 > Karolinska University Hospital > SE-171 76 Stockholm > > PS I have also noticed another problem: smtimes EpiData Will not read *.not > and *.rec files. I get an error telling me that the file name are not valid > or the file is used. When I try to open the same file not NotePad - no > problem! DS > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 78, Issue 17 > ******************************************** >

1 0

RE: Double Entry for Related Files
by epidata-list＠lists.umanitoba.ca 29 Apr '10

29 Apr '10

Sam, I thought about you related file problem and perhaps there is a workaround. I thougth for example of edaverse event notification of medication use. Each patient is using one or more medications and while using these may have two or more events simultaneously such as rash nausea and vomiting. Each event will be a record in a related file. But the unique identifier is the patient record and may cause trouble in double entry. Perhaps if each related record may be a combination, you me be able to run double entry independently. Example: Main qes file --- ID ##### name ___ sex___ medication ___ related file ---- ID ##### event __ eventID ________ description _____ Related chk file eventID before entry let eventID = ID + event end end If patient 123 has three events then eventID would be 123a 123b and 123c and may uniquely identify the events and double entry may be possible by this eventID. I did not test it although. But this means you would have to type all again if you already typed it all. Or perhaps exporting editing and importing may make this easier. kind regards, Abraço forte e que a força esteja com você, Dr. Pedro Emmanuel A. A. do Brasil Instituto de Pesquisa Clínica Evandro Chagas Fundação Oswaldo Cruz Rio de Janeiro - Brasil Av. Brasil 4365 Tel 55 21 3865-9648 email: pedro.brasil(a)ipec.fiocruz.br email: emmanuel.brasil(a)gmail.com ---Apoio aos softwares livres www.zotero.org - gerenciamento de referências bibliográficas. www.broffice.org ou www.openoffice.org - textos, planilhas ou apresentações. www.epidata.dk - entrada de dados. www.r-project.org - análise de dados. www.ubuntu.com/ - sistema operacional

1 0

RE: Double Entry for Related Files
by epidata-list＠lists.umanitoba.ca 28 Apr '10

28 Apr '10

I understand the two different methods of double-entering data, and I do indeed want to "prepare for double-entry". The problem is that when I go to prepare the questionnaire for double entry, I can only choose to prepare either the parent OR the child file. If I choose the parent file, then a double-entry file is only created for the parent file - when I open it to double enter the data, it relates to the original child file, so it opens the parent double entry file along with the original child file. Since only one of the two files is a double entry file, the program thinks I am entering the data for the first time, and does not compare the alues entered to the values from the original file. I cannot seem to find a way to prepare both the parent and the child file for double entry together. If I prepare them for double entry separately, I run into similar problems. Sam ---------------------------------------------------------------------- Message: 1 Date: Tue, 27 Apr 2010 19:13:58 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] Double Entry for Related Files To: epidata-list(a)lists.umanitoba.ca Message-ID: <4BD71B56.7020800(a)tbrieder.org> Content-Type: text/plain; charset=UTF-8; format=flowed Hi Sam: There are two approaches to double-enter: 1) independently, 2) the second file depending on the first. You seemingly chose the latter ("prepare for double-entry"). If you choose that option, you must enter the records in the same sequence (I believe) and the value of each field in the second record will be compared to the corresponding one in the first and a discordance reported, so you can verify. Thus, no need to enter twice. Alternatively, you enter your related file pairs independently between first and second entry. You must have a unique identifier in both the parent and the child file. The sequence then doesn't matter of course. After you have entered parent1-child1 and parent2-child1, you validate parent1-vs-parent2 on the unique identifier, then child1-vs-child2 on that identifier. Hans On 20:59, epidata-list(a)lists.umanitoba.ca wrote: > Hi, > > I have a questionnaire that uses two related .rec files for data entry. > I want to double enter the data by checking for discrepancies as the > data is entered the second time. Is it possible to do this for > questionnaires that span two .rec files? When I try to prepare for > double entry, the program creates a "file1_dbl.rec" file, but relates > it to the "file2.rec" file rather than creating a "file2_dbl.rec" file > to compare against. > > I am thinking that I will just have to un-relate the file, and enter > and double-enter the survey in two parts, but any help would be appreciated. > > Thanks, > > Sam > -- 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 -- Samuel Haddaway Research Assistant, International Projects National Opinion Research Center haddaway-sam(a)norc.org Phone: 301.634.9423

1 0

Related files and conditional chk
by epidata-list＠lists.umanitoba.ca 28 Apr '10

28 Apr '10

Hello epidata friends, Im occasionally reading emails in the list about limitations in the related rec files. The last I remember was about double entry, which I did not read a proposition of solution. Here goes another problems that I could not solve yet. Im working with a dataset entry with two purposes: 1) to estimate a trajectory of a particular liver enzyme over time while patients is under therapy and 2) estimate the risk of liver toxicity while in therapy. The tow objectives are time dependent. In the first objective the possible result is a graph with a line conecting dots which represents the enzyme values in each time point. The second is a cox model or a exponential survival model which the outcome is liver toxicity due to therapy. In this one, the medications may change over time. Therefore I was imagining creating a main recfile with clinical characteristics of each patient that are permanent, that is, do not change over time such as HIV serology status, and create tow related recfiles with 1) data about each liver panel with correspondent date and 2) the medication in use with initial date and end date with the end status (cure, default, death etc); both may be fed with several data from different dates for each patient. Now ... one common problem with dates is that very often typing mistakes make dates incompatible such as: 1) the second liver panel was collected BEFORE the first. 2) The end of medication was registered BEFORE the beginning or the second medication started BEFORE the end of the first. To control this sort of mistake is easy with conditional checking when the dates are in the same recfile. But if I make related files the conditional checking with dates should be done in the same field (or different fields) in different records. That is ... I should ask epidata to go in other record with the same key (ID) and check if the collection date is before or after the date of this open record. The question is ... is this possible? Does anyone have a sugestion to workaround (possibly having all the dates in the main recfile and related file)? An example: ******** Main qesfile ID #### name _____ hiv # start <dd/mm/yyyy> end <dd/mm/yyyy> toxicity # ******* First related file - liver panel ID #### coldate <dd/mm/yyyy> panelnum # alt #### ast #### ****** Secodn related file - medication ID #### TBdrugs _______ HIVdrugs _______ combstart <dd/mm/yyyy> combend <dd/mm/yyyy> outcome # Kind regards, Abraço forte e que a força esteja com você, Dr. Pedro Emmanuel A. A. do Brasil Instituto de Pesquisa Clínica Evandro Chagas Fundação Oswaldo Cruz Rio de Janeiro - Brasil Av. Brasil 4365 Tel 55 21 3865-9648 email: pedro.brasil(a)ipec.fiocruz.br email: emmanuel.brasil(a)gmail.com ---Apoio aos softwares livres www.zotero.org - gerenciamento de referências bibliográficas. www.broffice.org ou www.openoffice.org - textos, planilhas ou apresentações. www.epidata.dk - entrada de dados. www.r-project.org - análise de dados. www.ubuntu.com/ - sistema operacional

1 0