January 2020 - EpiData-list - University of Manitoba Mailing Lists

Jumps in Epidata Entry
by epidata-list＠lists.umanitoba.ca 15 Jul '26

15 Jul '26

Dear list, I have two questions regarding Jumps in EpiData Entry. 1) I want to jump to variable v10 if de score for v8 is 1 to 7. Of course this works: v8 RANGE 1 9 COMMENT LEGAL USE oplcat JUMPS 1 v10 2 v10 3 v10 4 v10 5 v10 6 v10 7 v10 END MUSTENTER END Is a shorter syntax possible and if so, how? 2) Is it possible to make a jump defination that depends on the value entered in a previous question? For example: After entering the value for variable v5 I want to jump to v8 if the answer on question v3=1. Kind Regards, Pieter van Groenestijn The Netherlands

2 3

fill fields from COMMENT LEGAL file
by epidata-list＠lists.umanitoba.ca 15 Jul '26

15 Jul '26

I'm studying the copydata example to learn how to extract several variables from a file identified in a COMMENT LEGAL statement. In A3.chk, the statement "TYPE COMMENT atransfer" appears. What is atransfer? I don't see where it has been defined as a variable and I don't find it as a system variable. Further, the program seems to be parsing the string in atransfer according to the position of punctuation. Where is the format of this string defined? Perhaps to be a bit more explicit: I have file with a list of CHWs: District, Village, CHW name and a survey conducted by the CHWs. As the data is entered for the survey, I'd like to present pick lists to facilitate entry. The data is quite strictly hierarchical: Villages occur within Districts, an CHWs live in villages. Thank you,

2 3

Export to R from epidata
by EpiData development and support 11 Jan '20

11 Jan '20

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

1 1

Re: [EpiData-list] Export to R from epidata (EpiData development and support)
by EpiData development and support 11 Jan '20

11 Jan '20

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 > ******************************************** >

1 0

new public release of Analysis, Manager and EntryClient released
by EpiData development and support 09 Jan '20

09 Jan '20

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

1 0