- EpiData-list - University of Manitoba Mailing Lists

RE: EpiData-list Digest, Vol 84, Issue 17
by epidata-list＠lists.umanitoba.ca 01 Nov '10

01 Nov '10

Hello, Are there plans in future EPIDATA MANAGER : - To change the font for a word or phrase without changing police from the another parts of a questionary? - To open multiple pages in a questionary? Thank you Bernard Branger, Nantes, France PS The link to "Course materials in French" in EPIDATA ENTRY / FRENCH is : http://www.reseau-naissance.com/joomla/index.php?option=com_content&task=vi… -- J’utilise la version gratuite de SPAMfighter pour utilisateurs privés. Jusqu’à présent SPAMfighter a bloqué 2235 courriels spam. Nous avons en ce moment 7 millions d’utilisateurs de par le monde entier. Les utlisateurs payants n’ont pas ce message. Vous pouvez télécharger la version gratuite: http://www.spamfighter.com/lfr

1 0

An error message while executing the command in Epidata analysis
by epidata-list＠lists.umanitoba.ca 29 Oct '10

29 Oct '10

Dear all, I got an error message while executing commands of Epidata analysis on a new machine with Windows 7. Please see the message within the quotation marks. " Cannot open file "C:\Users\Gateway\AppData\Local\Temp\TMPCC04.Tmp". The process cannot access the file because it is being used by another process " This happened when I hit F8 or F9 and the command was not executed. But it did work when I hit F8 for several times. Could anybody tell me why it happened and how to solve this problem? Thank you for your support. Zaw Myanmar

1 1

Datetime conversion resource
by epidata-list＠lists.umanitoba.ca 27 Oct '10

27 Oct '10

Hi list members From time to time on the list we have discussed the value of having a datetime variable in Epidata. This is something I would find like, as the 'epidemic curve' is something that is an important part of any outbreak investigation. For short outbreaks that carry on over more than one day both the time and date are useful so youcan show numbers becoming ill every 6 hours for example over two or three days. The ability to map by datetime is one reason I often use EpiInfo for outbreak analysis, although I enter data in Epidata. I wanted to let any interested members know that a colleague has developed a simple text file that can be run as a programme in EpiINfo that coverts data entered in EPidata to a single datetime for use in EPiInfo. If you have entered an onset date as a date and onset time as a number with a decimal (e.g. 15.30) the programme converts the information into a single datetime variable - it can then be mapped using the EpiInfo histogram graph. Jens if you think this is useful at all would you like me to post this somewhere? Also is there any thought of creating a time field in Epidata? thanks Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 >>> <epidata-list(a)lists.umanitoba.ca> 22/10/2010 10:47 p.m. >>> For all users Today new versions of Entry Client and Manager have been placed on thehttp://epidata.dk/testing.php page for general download and testing. Apart from some minor points and errors reported to the Flyspray bug database the current release is what we see as the first release candidate for general usage following key developments mentioned below. level 1: Basic functionality at field level level 2: Extended functionality with value labels, basic checks etc We are at level 1 now and production release will include level 2. Main news since last release are: a. bug fixes and enhancements b. availability of two file formats: epx: the basic xml structure containing all information for a given project epz:The same file, but zipped, which often reduces the overall size to about 10-30% of the epx file c. export of data to stata d. short introduction to the EntryClient Currently the users should find and test the following: Manager a. all aspects of creating new projects with one database table/file per project a1. importing (loading) old rec files and stata files a2. Pasting from qes files or editor files onto a dataform a3. Saving these data as a project file with options for entry b. exporting data to Stata (regardless of whether you have Stata) EntryClient b. data entry of project files created with manager b1. Securing that data are saved and shown as read b2. Editing and browsing in data b3. Backup of files after entry b4. Timed recovery function if systems break down during entry What are the next steps ? c1. Adaptation of EpiData Analysis to be able to read the xml structured files (epz and epx) c2. Following users tests in the coming weeks further error removal will be done in EntryClient and Manager Please report if possible to the flyspray database system. (But also if you cannot get the flyspray system to work let us know on this list) Kind regards Torsten Christiansen, Jens Lauritsen EpiData Association -- 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 ** ______________________________________________________________________________ This email has been scrubbed for your protection by SMX. For more information visit http://smxemail.com ______________________________________________________________________________

1 1

Input for decision of sequence in development of new functionality, please comment
by epidata-list＠lists.umanitoba.ca 26 Oct '10

26 Oct '10

Priority of developments The current sequence of developments until the first production release contains these elements. 1. Release of test version of EpiData Analysis, which can read EXP files (possibly EXZ) - expected this week. 2. "show structure" form to Manager 3. Control structures level 1 (value labels, range) --- test release 4. Multi language in forms and labels 5. Control structures level 2 (mustenter, jumps, "type comment") 6. Control structures level 3 (define unique key and search in data) --- test release 7. Solve known deficiences (from Flyspray and list) - e.g. idnum fields 8. Printing of dataforms in EntryClient --- test release 9. Enhancements for production of fast datasets, e.g. copy from question banks 10. Further developments, e.g. GCP (Good Clinical Practice Principles). Please discuss on this list at what level of function You find first release should be made - provided obviously at that level the function as such is stable. My current decision is after point 8. It would also be good to get statements during the coming months of which decisions you make locally on the conversion to the new principles - e.g. you are ready to use it at that moment, or you find the current EpiData Entry better for your purpose, or you decided to start using other software and the reasons for that. Regards Jens Lauritsen EpiData Association Denmark

1 1

Re: [EpiData-list] New test versions available for EpiData EntryClient and EpiData Manager
by epidata-list＠lists.umanitoba.ca 26 Oct '10

26 Oct '10

Hi Jens and the Epidata team thank you for all the work you are doing on the new development. In terms of the timeline I am wondering about when the new build might be stable enough to be used for training courses? At the moment I teach one or two courses a year to public health staff on using Epidata and EpiInfo to investigate disease outbreaks. They use the current version of Epidata and I am wondering about when I should try and change to the new version. thank you Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 >>> <epidata-list(a)lists.umanitoba.ca> 22/10/2010 10:47 p.m. >>> For all users Today new versions of Entry Client and Manager have been placed on thehttp://epidata.dk/testing.php page for general download and testing. Apart from some minor points and errors reported to the Flyspray bug database the current release is what we see as the first release candidate for general usage following key developments mentioned below. level 1: Basic functionality at field level level 2: Extended functionality with value labels, basic checks etc We are at level 1 now and production release will include level 2. Main news since last release are: a. bug fixes and enhancements b. availability of two file formats: epx: the basic xml structure containing all information for a given project epz:The same file, but zipped, which often reduces the overall size to about 10-30% of the epx file c. export of data to stata d. short introduction to the EntryClient Currently the users should find and test the following: Manager a. all aspects of creating new projects with one database table/file per project a1. importing (loading) old rec files and stata files a2. Pasting from qes files or editor files onto a dataform a3. Saving these data as a project file with options for entry b. exporting data to Stata (regardless of whether you have Stata) EntryClient b. data entry of project files created with manager b1. Securing that data are saved and shown as read b2. Editing and browsing in data b3. Backup of files after entry b4. Timed recovery function if systems break down during entry What are the next steps ? c1. Adaptation of EpiData Analysis to be able to read the xml structured files (epz and epx) c2. Following users tests in the coming weeks further error removal will be done in EntryClient and Manager Please report if possible to the flyspray database system. (But also if you cannot get the flyspray system to work let us know on this list) Kind regards Torsten Christiansen, Jens Lauritsen EpiData Association -- 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 ** ______________________________________________________________________________ This email has been scrubbed for your protection by SMX. For more information visit http://smxemail.com ______________________________________________________________________________

1 1

Re: [EpiData-list] New test versions available for EpiData EntryClient and EpiData Manager
by epidata-list＠lists.umanitoba.ca 22 Oct '10

22 Oct '10

For all users. A critical bug had sneaked into the builds of Mac versions of EpiData EntryClient (thanks to Jamie Hockin for fast feedback). The Intel and PowerPC version have both been fixed and new versions (though with the same version no.) have been placed on the testing website. Regards, Torsten Bonde Christiansen. EpiData Association. On 2010-10-22 14:35, Jamie Hockin wrote: > Hi Torsten, > > The Mac (Intel) version of the Client is corrupted - the .app is not > executable (error that the .app file is damaged or incomplete). It is > the same size/date as the previous version. File date is Friday, > September 10, 2010 8:31 AM > > Jamie >

1 0

New test versions available for EpiData EntryClient and EpiData Manager
by epidata-list＠lists.umanitoba.ca 22 Oct '10

22 Oct '10

For all users Today new versions of Entry Client and Manager have been placed on thehttp://epidata.dk/testing.php page for general download and testing. Apart from some minor points and errors reported to the Flyspray bug database the current release is what we see as the first release candidate for general usage following key developments mentioned below. level 1: Basic functionality at field level level 2: Extended functionality with value labels, basic checks etc We are at level 1 now and production release will include level 2. Main news since last release are: a. bug fixes and enhancements b. availability of two file formats: epx: the basic xml structure containing all information for a given project epz:The same file, but zipped, which often reduces the overall size to about 10-30% of the epx file c. export of data to stata d. short introduction to the EntryClient Currently the users should find and test the following: Manager a. all aspects of creating new projects with one database table/file per project a1. importing (loading) old rec files and stata files a2. Pasting from qes files or editor files onto a dataform a3. Saving these data as a project file with options for entry b. exporting data to Stata (regardless of whether you have Stata) EntryClient b. data entry of project files created with manager b1. Securing that data are saved and shown as read b2. Editing and browsing in data b3. Backup of files after entry b4. Timed recovery function if systems break down during entry What are the next steps ? c1. Adaptation of EpiData Analysis to be able to read the xml structured files (epz and epx) c2. Following users tests in the coming weeks further error removal will be done in EntryClient and Manager Please report if possible to the flyspray database system. (But also if you cannot get the flyspray system to work let us know on this list) Kind regards Torsten Christiansen, Jens Lauritsen EpiData Association

1 0

NIH requirements for Data management
by epidata-list＠lists.umanitoba.ca 20 Oct '10

20 Oct '10

Dear EpiData friends, Recently I was talking to a friend about the professionalism of research x professor-student structure in research and then he showed me a past call of NIH grant wich in part I pasted here. I was somehow surprised, because I didnt know that all these should be in a project. Data and Biostatistics Core: Required. Each application must include a The Data and Biostatistics Core is a resource to the multi-project application, providing for the data management and statistical support of the overall Center and individual research projects. The Data and Biostatistics Core has several components: an electronic data management system, a data management implementation plan, and biostatistics support. A full-time Data Manager must be present onsite at the Center or at the place where the electronic data management system is hosted and statistical expert(s) should be available as needed. Applications must provide a detailed description of the existing or planned data management system. The data management system must be capable of collecting and managing data from the participating study sites in order to ensure uniformity of procedures and high quality data. The data management system should reside at the endemic area site(s) and data management staff will be responsible for the design, development and testing of databases and data management software, validation of the data system, training of data management and field personnel on data collection procedures and activities, maintenance of the database and software systems, documentation of changes, and preparation of data dictionaries and standard operating procedures for all aspects of data management. Each TMRC and related field sites should have computers, connectivity to the internet and communications capabilities. For sites without such capabilities, funding for such infrastructure should be budgeted in this core and the infrastructure should be in place before the end of the first year of the grant. The data management system should include, but is not limited to: • security features for controlled access to all project data; • a tracking system for data forms, activities, and study samples; • date and time stamping of all data records; • audit trails to track all changes made to data records; and • a reporting system that generates error reports and summary information reports. If applicants do not have the capability for the data management system at the time of application submission, the applicant should describe a plan for designing and implementing a fully operational data management system based on the system requirements, including provisions for the time frame for design, development, testing, validation, and training activities. Plans and procedures must be in place to provide security against anticipated risks, including loss of confidentiality of subject electronic records and data summaries. Each TMRC should have staff with data management (Data Manager) expertise at each site. The Center should have access to dedicated statistical expertise that informs the research study design and provides the ability to conduct statistical data analysis. They should provide for activities such as study design and protocol development and where appropriate, generating interim tables, preliminary statistical analyses for progress reports, and assisting with statistical issues related to laboratory testing and results. 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 1

Exporting problems
by epidata-list＠lists.umanitoba.ca 20 Oct '10

20 Oct '10

Dear all, When I try to export my data into SAS, all my variables appear into a single column (in SAS). What could be happening? When I export the data into Excel and then to SAS it does work perfect. Is there any difference from exporting a data file directly from EpiData into SAS other than EpiData into Excel and then SAS? Thanks in advance for your help. Rafael

1 11

BMI Calculation
by epidata-list＠lists.umanitoba.ca 14 Oct '10

14 Oct '10

I am having trouble calculating BMI in Epidata. Height is measured in feet (separate) and inches (separate). I tried to create a new variable (BMI), which it did, but it is labelled as "Float," and unusable. Please help! Ali Ali B. Mansaray, MPH, PhD.c OMH, SCDHEC (803) 898-0263 (Days) *MANSA CS* [(803) 446-6958 (On Call) *"To be or not to be: that is the question...?" (Shakespeare),* especially in public health, minority health and health disparities in these United States.

1 0