EpiData-list

epidata-list@lists.umanitoba.ca

1828 discussions

Almost releasable new pre-public version of Analysis (please test)

by EpiData development and support

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.

3 years, 10 months

Screen backgrounds

by EpiData development and support

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 

3 years, 11 months

New version

by EpiData development and support

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

3 years, 11 months

Remote storage/access to data collected in EpiData

by EpiData development and support

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

3 years, 11 months

HELP ON EPPIDATA ENTRY

by EpiData development and support

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

4 years

EpiData classic v3.1 in 2020? Under 64bit?

by EpiData development and support

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

4 years

Defining Entry Rights EpiData Manager v4.6.0.2

by EpiData development and support

Hello, I am testing the EpiData system as a possible solution for data management for a nutrition cohort study. I have been able to set up a dataform and create groups and users using the Extended Access capabilities. I am however unable to define entry rights (CTRL E) on the my test data form, when I click on it using the point click option or control E absolutely nothing happens and the window I expect to show up as shown in the page 4 (Step 3) of attached PDF does not appear. Anyone else experienced this problem? Or am I missing something? Edna

4 years, 2 months

Export to R from epidata

by EpiData development and support

Dear Jens Is it possible to export the data in epidata to R data? Perhaps it can but i am not sure how Please could you advice again, much appreciate your teams tremendous works new year greetings Thambu

4 years, 4 months

Re: [EpiData-list] Export to R from epidata (EpiData development and support)

by EpiData development and support

I have exported from EpiData to R successfully. I used both Stata-files to preserve value labels and CSV files. Work fine. Kind Regards Henning Langen Stokmo Consultant (Nuclear Medicine) // Department of Medical Imaging, Vestre Viken HF, Drammen Hospital Radiology Resident // Department of Medical Imaging, Vestre Viken HF, Drammen Hospital PhD-student // Department of Nuclear Medicine, Oslo University Hospital | Oslo University Functional and Molecular Imaging Research Group ( https://www.ous-research.no/revheim/) ResearchGate: https://www.researchgate.net/profile/Henning_Langen_Stokmo On 11 January 2020 at 19:01:02, epidata-list-request(a)lists.umanitoba.ca ( 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. Export to R from epidata (EpiData development and support) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 11 Jan 2020 04:51:46 +0000 > From: EpiData development and support > <epidata-list(a)lists.umanitoba.ca> > To: "epidata-list(a)lists.umanitoba.ca" > <epidata-list(a)lists.umanitoba.ca> > Subject: [EpiData-list] Export to R from epidata > Message-ID: <1578718346010.92724(a)cmcvellore.ac.in> > Content-Type: text/plain; charset="iso-8859-1" > > Dear Jens > Is it possible to export the data in epidata to R data? > Perhaps it can but i am not sure how > Please could you advice > again, much appreciate your teams tremendous works > new year greetings > Thambu > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 188, Issue 2 > ******************************************** >

4 years, 4 months

new public release of Analysis, Manager and EntryClient released

by EpiData development and support

Dear all Yesterday we moved the "pre-release" version announced on December 31st 2019 to the official public download page. You may review the changes in the announcement on that day. So from now please install and use the updated versions. Some important errors have been identified in previous versions of EntryClient, so you should update. You may always test which version you have in the help menu "check version online". EpiData Analysis: 1.6.0.0 EpiData EntryClient: 4.6.0.2 EpiData Manager: 4.6.0.2 You might have to contact a central IT office if there are restrictions on installation and use of software. E.g. in our hospital I have to install from a local network drive while having a local administrator right for 30 minutes. We have not had any major issues reported - but a few minor aspects were identified in-house and fixed. E.g. A lacking !label abbreviation in a command and a change when importing csv files (string variables identified shorter than about 70 characters will now be string and not memo). Four observations that you should know of: 1 In analysis the command keys have been changed a bit. Check the "window" menu and notice that in the editor "ctrl+a" will run all commands and "ctrl+d" will execute the current command or a block if you have selected a block of commands. 2 If in new analysis you wish to create a memo or upper variable these are found as options to the "new variable" command as options (!memo !Upper): e.g. new variable txt string !memo. 3 If you are creating password protection in Analysis, this is done at the project level, not at the variable or dataset level. An example of this is shown below. 4 Currently I am doing many SPC (Statistical Process Control) graphs in my work at the hospital for hip fracture patient quality assurance. The way this is done is that we extract from the main hospital registration system a number of variables for all hip fracture patients. This is saved once a day on a central server as a csv file. Then I import this file with the new analysis and save it for table analysis in new analysis with many variables including time and memo variables (analysisNew.epx). But when I need to do the SPC graphs in Classic Analysis the epx file is not read, since Classic Analysis cannot read this type of variable. The remedy is to save a separate epx file (analysisClassic.epx) and use that for the graphs. Then I can just copy the graphs to a common folder and an html file shows the current results. The principle is an extension of a system developed with Norwegian Colleagues recording data for local municipal reporting from health centers (Thanks Vegard Högli). best wishes to all Jens Lauritsen EpiData Association Denmark new p !l:="test project" !size:=100; New project created: test project .... (output omitted - project with 1 dataset and 100 observations created) // to add a password encryption on all data: edit p !pw:="test"; // to verify this : list p; (output omitted - exect for info on "encryption"): Project Encryption: simple password (data only); // to remove a password: edit p !pw:=""; list p; (output omitted - exect for info on "encryption"): Project Encryption: none

4 years, 4 months

← Newer
1
2
3
4
5
6
7
8
...
183
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

EpiData-list