- EpiData-list - University of Manitoba Mailing Lists

Update of most recent public version of Analysis (due to error in the editor)
by EpiData development and support 03 Jul '20

03 Jul '20

Dear All Unfortunately there was an undisclosed bug in the public version released last week of new Analysis. One could exit Analysis without being asked to save an unsaved pgm file in the editor. This is now fixed. The most recent public version is therefore: _Manager_ *v4.6.0.2* _EntryClient_ *v4.6.0.2* _Analysis_ *v3.0.0.1* And the combined one for Windows: setup.all-in-one.4.6.0.5.exe The lacking finding of the error has been added to the pre-test for coming analysis. best wishes and apologies. Jens Lauritsen EpiData Association, Denmark

1 0

SPSS Export
by EpiData development and support 03 Jul '20

03 Jul '20

Dear Torsten, dear Jens, Epidata-Manager does the SPSS-Export in a indirect way. A SPSS-Syntax-File and a CSV-Data-File are created. You have to run the Syntax in SPSS to create a SPSS-Datafile. This is the current proceeding. For this proceeding I have some questions: - Is it very hard to create a SPSS-Datafile at once? - Why is the SPSS-CSV-Data-Export-File different to a direct CSV-Data-Export-File? The Structure is different. In my opinion it will be easier and a clear way to have ONE (adjustible) CSV-Data-Export-File. For that I recommend to replace the second Tab in " Tools/Export.../Type: SPSS 'SPSS-Options' " with the 'CSV-Options' (except for "Export Value Labels" because this is a great advantage of EpiData! Perhaps this Item stands better one the first Tab.) - Is it possible to change the default given SPSS-Syntax? The "Data List"-Command still works, but it is a little bit out of date. It does not work with the qualifier for Textvariables. So you have to edit the csv-File or have to write a new Syntax. "GET DATA" is the current Command. With kind regards Michael

1 1

Epidata 3.1 - Not Showing Correct Date
by EpiData development and support 02 Jul '20

02 Jul '20

Good morning. I received a ticket from one of our Epidata users. The user is using Epidata 3.1. According to her, the data entry sheets usually self-populate with the correct date. However, it seems to be stuck on 20/04/2020. Please see attached. Troubleshooting done: 1. Clear personalization and profile. 2. Re-install the software. Info: 1. There are 2 users of Epidata in this department. The 2 of them are experiencing this. 2. They are using VDI pool to access Epidata. What do you think is the problem and how it can be resolved. Thank you. Noel Bermejo Technical Analyst - Information Technology Yorkton Regional Health Centre - Yorkton Saskatchewan Health Authority | 306-786-0159 This email message may contain confidential and/or privileged information. It is intended only for the addressee(s). Any unauthorized disclosure is strictly prohibited. If you are not a named addressee you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system.

1 1

Epidata Analysis 3.00 and background colour
by EpiData development and support 28 Jun '20

28 Jun '20

Dear Jens and Team,                    Congratulations for this next step of Epidata Analysis 3.00 development. You have very kindly added the functionality of;Output background colour,Command background colour from Edit -- Colour pull down menu.I am not technically sure of the difficulties involved in adding "Editor background colour" option also in the software with cross platform compatibility.However if possible, please try to add that also in the next development release.Our rock solid Classical Epidata Analysis 2.2 ver was developed after year of hard work by Epidata Team. Replicating all those and additional functionalities in the new Epidata Analysis is a daunting task. However Epidata team has shown real perseverance .With regards and best wishes,Shavinder Singh   

1 0

Almost releasable new pre-public version of Analysis (please test)
by EpiData development and support 25 Jun '20

25 Jun '20

Dear list-readers A new updated version of EpiData Analysis (v1.7.99.1) has been placed for your testing on http://epidata.dk/testing.php Please find below a summary of the changes. In particular notice that the requirement of [_n] in pgm's has been removed, unless you refer to a given observation. I expect the release as public in the coming week or the week after. Please test and report to this list. As part of my job as a clinical epidemiologist and professor at the Odense University Hospital here in Denmark I have extensively tested the software during the last three months. We now use the pre-public version on a daily basis. Now we have a running system in new EpiData Analysis. It is run by secretaries, who have no experience in programming. They just click an icon to accomplish: a.import a csv file saved daily from our main IT-patient registration system (EpiData Analysis) b. merge with previously controlled observations to evaluate only new observations (EpiData Analysis) c. quality securing coding in the patient journal. (EpiData EntryClient) d. create SPC graphs in classic analysis (EpiData Analysis Classic) e. create lists for audit of patients where the quality standards were not met. To run the system in the revised new analysis we only lack possibility of creating graphs, which I expect to include in the coming months, if all goes well ready by the end of this year. One other aspect we need to tackle is the increasing demand for safety certificates and documentation in relation to secure systems. If any of you are experienced in this area please write me an e-mail (jl at epidata.dk) . Without the efforts of Torsten Bonde Christiansen (Software design and programming), Jamie Hockin (testing, programming, Mac adaptation) and Hans L. Rieder (testing, approving solutions) the software would not continue to develop. Please look into the website for inspiration: https://tbrieder.org/epidata/epidata.html Best wishes Jens Lauritsen, coordinator and initiator. EpiData Association, Denmark -------------------------------------------------------------------------------------------------------------------------------- Changes since v1.6.0.0 Major improvement: - [_n] is no longer needed, except when desired. - editor: Completely new. Many aspects improved. Works better in MacOs - new !output option with save command - allows saving output content as html - new "set" option to control format of saved output html|txt - new "set" option allows user definition of css styles in saved html output - new "set" option defines internal css or external reference to css file in html output - extended fast createdate function allows conversion of date strings with named months. - extended createdate function allows use of national month naming defined in set Other new aspects: - mergevar added as the last in a merged dataset - default dataset used after merge is the merged one - keyboard shortcuts unified and simplified. - main window opens immediately if started with a pgm - many commands: unified option naming, e.g. !l is labels Bug fixes: - all solved - keep : if used in a "for loop" errors could occur - Assignment: incorrect control of missing in string variables - validate duplicate : error if a variable was missing - many minor other bugs or inconsistencies Bug fixes: - partially solved - errors in calculations when dividing by zero. fixed in Linux and MacOS, but not in windows always. Known issues at this point: - Analysis does NOT handle header "variables" at all (except keeping defined ones). - Sometimes windows 10 gives a "list - index out of bounds" error in particular when running a selected block from the editor or when running several pgm files within a pgm.

1 1

Screen backgrounds
by EpiData development and support 14 Jun '20

14 Jun '20

Dear Jens,                  Great work is being carried out of developing New Epidata Analysis. I was just exploring new release ver 1.7.99.1  One suggestion as request;                 We had relatively simple system of changing background to either black or white from pull down menu (Screen Font Option from window pull down menu ) in Classical Epidata Analysis.Tweaking Start.pgm is not everyone’s cup of tea. We work in the main output screen and Editor screen for long time. Dark (black) background are not stressful to the eyes while white background are. If possible please retain that feature  (of changing background to either black or white from pull down menu) in New Epidata Analysis also.With regards,Shavinder Singh 

1 0

New version
by EpiData development and support 12 Jun '20

12 Jun '20

Dear Jens Thank you. Are there any simple podcasts you could do perhaps 5 mins each explaining the new features? Much obliged Thambu David

1 1

Remote storage/access to data collected in EpiData
by EpiData development and support 03 Jun '20

03 Jun '20

Dear EpiData users, I have designed a relational data system for a nutritional cohort study in Nigeria and was wondering if anyone on this forum has any tips or recommendations for how best to establish a server/cloud based back up of the system so that the PI's can have remote access to do additional data quality assurance. More specifically, are there freely accessible or at least affordable secure servers or data storage facilities that you would recommend if neither ourselves or implementing partner have that facility in place? With kind regards, Edna Ogada

1 2

HELP ON EPPIDATA ENTRY
by EpiData development and support 10 May '20

10 May '20

Sir/Madam I am Ibrahim from Ghana. I face a challenge while developing a data base with epidata entry. I have different regions and each region has a number of different districts under it. I want to link the each region to the specific districts under it so that at data entry mode, when a particular region is selected, only the districts under it will appear at the districts field for selection. I will really appreciate a support from anyone on this issue. I don't mind calling for more information if a phone number is provided for me. Thank you

1 1

EpiData classic v3.1 in 2020? Under 64bit?
by EpiData development and support 06 May '20

06 May '20

Dear EpiData list members, Use EpiData classic v3.1 in 2020? (last release in 2008) YES - that's what I have just been doing, based on good experience a decade ago under Windows 7 pro 32bit, and on guidance found regarding EpiData v4.6 versus v3.1 on <http://www.epidata.dk/download.php> (see below). HOWEVER, one important feature no longer seemed to be working under Windows 7 pro 64bit: DEFINEd variables were only locally available (i.e. in the same record), but not GLOBALly (i.e. across RELATEd tables). Question: Is anything known about this problem, or even a work-around? This would be important, because: 1- EpiData v3.1 uses a parsimonious language easy to retain e.g. for researchers who only occasionally are in the situation to program themselves a data entry tool (but then typically like to get it working quickly w/o learning new software); 2- According to http://www.epidata.dk/download.php (accessed today), "In special situations or when a given function is not yet developed in Manager, EntryClient and Analysis you could need ... EpiData (Classic) Entry v3.1 (get it here) (only for programmed checks, before/after end blocks)". HOWEVER, MANY will find essential what can be done with BEFORE/AFTER FILE/RECORD/(field) blocks and apparently can not (yet?) be done with v4.6; 3- The feature "DEFINE variable GLOBAL" is necessary for multiple-level hierarchies and longitudinal databases (and it proved feasible and effective when I did it 10 years ago under Windows 7 pro 32bit, communicating only by email between North-America and sub-Saharan Africa). Thanks in advance Rolf

1 1