- EpiData-list - University of Manitoba Mailing Lists

Problem with AUTOSEARCH
by EpiData development and support 20 Aug '17

20 Aug '17

Dear friends, When I enter a duplicate data in a field configured with autosearch, the dialog box displays three option buttons: YES, NO and CANCEL. When pressing the NO button, nothing happens but the other options work normally. The other dialog boxes similar to this one are working normally. Does anyone know if this is a bug in EpiData (Classic) Entry v3.1? How can I resolve this? I need to set up a variable like AUTOSEARCH varID varPERSON. Where varID is the identification variable and varPERSON is the number given to each person in the household. Grateful for attention! Márcia

1 0

Reg Epidata Manager 4.0.2.101
by EpiData development and support 03 Aug '17

03 Aug '17

This is a very basic question. 1) I am not able to automatically calculate the number of hours from the calculate option. I have input date and time and entered it into the calculate option but it is not giving me the correct answer. e.g. I have input date of injury and time of injury; and date of presentation and time of presentation. I need to calculate the number of hours of delay in presentation. I am not able to do that. 2) Is it possible to change the time option and exclude the seconds? Thank you, With regards, Madhurita

1 3

error message
by EpiData development and support 21 Jul '17

21 Jul '17

Dear all When comparing two datasets with Epidata Manager (double entry) I receive the error: "index out of bounds 108". Does somebody know what this means? Thank you very much, Nicole Dr. med. Nicole Bender Senior Research Fellow Evolutionary Morphology and Adaptation Group Institute of Evolutionary Medicine (IEM) University of Zurich Winterthurerstrasse 190 CH-8057 Zurich, Switzerland Office Y42 G86b Phone +41 44 635 05 31, Fax: +41 44 635 57 02 nicole.bender(a)iem.uzh.ch http://www.iem.uzh.ch/en/people/admin/Nicole-Bender.html

1 4

Read and Merge “rec” file commands and few suggestions in New Epidata Analysis (0.7.3.0)
by EpiData development and support 09 Jul '17

09 Jul '17

Dear Jens,                                     It is heartening to see the Epidata Analysis development progressing. Our favourite “qes/chk/rec” file  systm  seems fading  on the horizon. Our old applications are still functional in Classic Epidata Entry. It is comparatively easy to upgrade to the new”epx” file if one is using the FLAT file. However, the relational “rec” files cannot be upgraded to the new  ”epx” file. There was a line written in the mail that  one can read “rec” file but not write it in the new Epidata Analysis. Hence I request you to kindly preserve the read and merge (rec files) commands in the new Epidata Analysis.The Command and Function Reference Guide 2.1 is fairly exhaustive. Command “Merge” is perhaps not introduced in the prototype version, hence not mentioned in the Command and Function Reference Guide.It is possible to generate by the available Graphics in the Epidata Analysis ver 2.2.3 (build 187) by command syntax  generated by using  “Diaglogue boxes”.  Available options in the graphical output are excellent. However some tweaking is still required to get the final graph. PGMs is a wonderful feature with infinite possibilities. Gratitude to Epidata team for the sustained effort .With regards,Dr.  Shavinder Singh 

1 0

Test version of new EpiData Analysis released (v0.7.0.3) - please assist in testing.
by EpiData development and support 08 Jul '17

08 Jul '17

Exciting News Today we have released a test version of the rewritten analysis, which for the first time approaches functionality resembling the final first version to be released later. You may download the test version from http://www.epidata.dk/testing.php Please notice that it is still premature to use the new analysis for production every day use, but we urge users to challenge the new analysis. You could for instance replicate data-management procedures you do with ordinary Classic Analysis v2.2. rel 3 (Build 187) The intention is to release the new analysis for production when the following has been developed: A: all functionality for data management (new projects, new variables, labels and editing of these). B: append and merge. C: basic reporting - e.g. for logfile overview Already now you may test many of these aspects. After download and unzipping (files are provided in zipped archives) you will see the commands and syntax documentation. We attempt to maintain the same syntax that you know, but to allow for the modernization some changes are needed: e.g. read and write epx, csv and dta files ; work on all operating systems (Linux, Mac, Windows) ; accept UTF-8; extend with special functions; sort data; manage encrypted data. You can read rec files, but not write them. Use epx for saving data. We also aim for standardization across commands. E.g. number of decimals in output is always !Dx, where x is the number of decimals 0,1,2 etc. For data analysis these commands are implemented: count , means, freq, Some changes: use := instead of = . Put texts in " " . End all command lines with ;. Selection works on a single block. Options are mentioned with ! instead of /. Some enhancements: A copy of all executed commands is saved (commandlog.pgm). Recent pgm in editor filelist. Multiple pgm sorting ascending and descending and more. See datasets (F2) in a project. Open encrypted files. A frequency table of v17: freq v17 !vl !cum ; // would show labels and values plus cumulative percentage. To do the same table among those younger than 40 with no decimals. select (age < 40) do freq v17 !vl !d0; To remove all observations with age above 68. Use the command drop: select (age> 68) do drop data; A new construct is a loop, e.g. : new global integer i ; for i:=1 to 5 do ? "This is a number counting: " + i ; Which can be used to show means or frequencies for subgroups of another variable: new global integer i ; for i:= 1 to 5 do select (area = i) do means age !by:=sex !t; Please challenge function within WHAT is already implemented. Also notice that output format is still rather crude. Rest assured more will come during autumn. But do remember that you should NOT use production data - work on copies of real data. Please also discuss function and problems on this list. Best wishes for fruitful testing Torsten Christiansen Jens Lauritsen EpiData Association, Denmark

1 1

Updated versions of EntryClient and Manager (4.2.0.0)
by EpiData development and support 21 Jun '17

21 Jun '17

For all list users. We have released next versions of EpiData Manager and Entryclient: Major news: 1 Saving data is now per observation. The principle of writing data was changed completely. From this version onwards all changes to single observations (records) are saved after the user responds "Yes" to the question of saving of that observation on a given dataform. All saving to disk is performed in the background, such that entry can continue. But all data are still in memory, such that speed of browsing etc should be the same. A visual feedback button indicates current state: green = current state is saved correctly yellow = save in progress red = error in save. The user most intervene if this persists. The "red state" could occur if you loose connection to a network drive, e.g. due to time-out failure. In such cases the user can save a copy of the project with EntryClient ("save as" in the file menu). It is the responsibility of the user to secure proper handling afterwards, e.g. decide with a manager what should happen. To find out which project file is optimal for continued entry the "count observations/records by id" function in Manager - documentation, is a good way to get an overview. 2 Status bar have new common items. Make sure to get a new "default status bar" to see this. (default preferences) 3 Valuelabels are now possible for Date and Time variables. 4 A number of bugs have been fixed in relational data and other special situations. 5 Implementation of logging: extended access The content of the logfile system is now a standard dataform within the project. If a user have administrative rights the log file content can be seen in Manager, for all other users it is hidden. This allows analysis and export of the data in a logfile. All writing to the logfile is performed in the background, such that it does not interfere with ongoing entry. The logging function allows assessment of which users had access to data, at what time and see before/after values if an observation was edited after first save. For details, see the specific texts: Manager:http://epidata.dk/epidatamanager.changelog.txt EntryClient:http://epidata.dk/epidataentryclient.changelog.txt Common functions:http://epidata.dk/epidatacore.changelog.txt Unfortunately we have discovered a few bugs after the first (4.2.0.0) elease, so please make sure to download and install again if you have downloaded the new version before the 21st of June. Please verify that your changes to data are actually saved, We have obviously tested the new "save each observation" principle "in-house", but there could be examples in which this is not working correctly. Do not hesitate to report problems to this list or < info at epidata.dk > Development continues with re-writing analysis for complete data-management features. The new analysis can read the logfiles created with extended access. Expected to be available for all users in open testing within a few weeks. After that we will continue with implementation in EntryClient of extended scripting during entry. Please consider adding funding to cover development - e.g. at the level of what alternative software acquisitions would have cost. The funding principle continues as "attain funding-release without fee-release as open-source when we have completed development". Always acknowledge those giving funding (see http://www.epidata.dk/credit.htm and http://www.epidata.dk/funding.htm) We need help in creation of sample cases that could be used as part of the quality assurance programme. Currently the testing is thorough for Manager and Analysis, but still not sufficient for EntryClient. best wishes Jens Lauritsen & Torsten Christiansen EpiData Association Denmark

1 0

Make a Cascades and calculate some fields
by EpiData development and support 21 Jun '17

21 Jun '17

Dear All,I have 2 problems.1. Please somebody can help me to do a cascade in Epidata?My database have 4 levels (Region, District, Health Aeria and Village). I want to make a cascade model. So, when i select one region, i want to only have the district linked to the r?gion. The same for district and health aeria and village.2. How to have results with addition of some fields (Integer). In this Epidata version, we can calculate hours and concatenate. Best Regards?_______________________________________Konan Diby JP, MD, MPH Attaché de Recherche Labo. Biostatistique & Informatique Médicale UFR Sciences Médicale, Univ. F. Houphouët-Boigny 22 BP 1041 Abidjan 22, Côte d'Ivoire Tel./Fax: (+225) 22 401 403 GSM: (+225) 05 994 326 / 07 250 561 skype's: dibykonanjp

1 1

Re: [EpiData-list] EpiData-list Digest, Vol 159, Issue 2 Message 1
by EpiData development and support 20 Jun '17

20 Jun '17

You can develop relational data form to have this kind of structure. Use "RELATE" command in EpiData entry. Here's a simple example on my blog. https://myominnoo.blogspot.com/2016/03/creating-relational-form-in-epidata-… You can also use EpiData Manager and EntryClient to have this kind. All the best -- *Myo Minn Oo* Operational Research Fellow *International Union Against Tuberculosis and Lung Disease (The Union)* 36, 27th Street, Between 72nd and 73rd Streets, Mandalay, Myanmar Tel: +95 11-201182, 2 71082 Fax: (+95) 2 71082 www.theunion.org worldlunghealth.org <http://www.worldlunghealth.org/> *Tel:* (+95) 99705 45333, 94513 35581 *Skype:* myoetc *Email:* myominnoo(a)theunionmyanmar.org, dr.myominnoo(a)gmail.com

1 0

Re: [EpiData-list] EpiData-list Digest, Vol 159, Issue 2
by EpiData development and support 19 Jun '17

19 Jun '17

Dear All,Please somebody can help me to do a cascade in Epidata?My database have 4 levels (Region, District, Health Aeria and Village).I want to make a cascade model. When i select one region, i want to only have the district linked to the région. The same for district and health aeria and village.Best Regards _______________________________________Konan Diby JP, MD, MPH Attaché de Recherche Labo. Biostatistique & Informatique Médicale UFR Sciences Médicale, Univ. F. Houphouët-Boigny 22 BP 1041 Abidjan 22, Côte d'Ivoire Tel./Fax: (+225) 22 401 403 GSM: (+225) 05 994 326 / 07 250 561 skype's: dibykonanjp Le Vendredi 14 avril 2017 17h00, "epidata-list-request(a)lists.umanitoba.ca" <epidata-list-request(a)lists.umanitoba.ca> a écrit : 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: Reg Epidata Manager 4.0.2.101 (EpiData development and support) 2. Re: Reg Epidata Manager 4.0.2.101 (EpiData development and support) 3. AUTO: CN=Louise Cullen/O=NWHB is out of the office. (returning 18/04/2017) (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Thu, 13 Apr 2017 13:24:16 -0400 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: EpiData List <epidata-list(a)lists.umanitoba.ca> Subject: Re: [EpiData-list] Reg Epidata Manager 4.0.2.101 Message-ID: <6576F7E6-6E13-4FA0-AD4D-EF24A964BA2A(a)bell.net> Content-Type: text/plain; charset=utf-8 1) Can you wait and do this in Analysis or another software? Unless your data entry logic depends on this time difference, it should not be necessary to do the calculation in EntryClient. 2) It would be nice, but not in this version. You certainly don?t have to enter the seconds - they will always show up as 00. Jamie > On Apr 13, 2017, Madhurita wrote: > > 1) I am not able to automatically calculate the number of hours from the calculate option. I have input date and time and entered it into the calculate option but it is not giving me the correct answer. e.g. I have input date of injury and time of injury; and date of presentation and time of presentation. I need to calculate the number of hours of delay in presentation. I am not able to do that. > > > 2) Is it possible to change the time option and exclude the seconds? > ------------------------------ Message: 2 Date: Thu, 13 Apr 2017 19:26:49 +0200 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] Reg Epidata Manager 4.0.2.101 Message-ID: <8C5A0DE3-7509-4108-9EE8-CFDC4C789894(a)epidata.dk> Content-Type: text/plain; charset=utf-8 Have you made the target variable a float? That is say length 6 and two or three decimals? Best wishes Jens Lauritsen On 13 April 2017 19:24:16 CEST, EpiData development and support <epidata-list(a)lists.umanitoba.ca> wrote: >1) Can you wait and do this in Analysis or another software? Unless >your data entry logic depends on this time difference, it should not be >necessary to do the calculation in EntryClient. > >2) It would be nice, but not in this version. You certainly don?t have >to enter the seconds - they will always show up as 00. > >Jamie > >> On Apr 13, 2017, Madhurita wrote: >> >> 1) I am not able to automatically calculate the number of hours from >the calculate option. I have input date and time and entered it into >the calculate option but it is not giving me the correct answer. e.g. I >have input date of injury and time of injury; and date of presentation >and time of presentation. I need to calculate the number of hours of >delay in presentation. I am not able to do that. >> >> >> 2) Is it possible to change the time option and exclude the seconds? >> > >_______________________________________________ >EpiData-list mailing list >EpiData-list(a)lists.umanitoba.ca >http://lists.umanitoba.ca/mailman/listinfo/epidata-list -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ------------------------------ Message: 3 Date: Thu, 13 Apr 2017 22:02:39 +0100 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] AUTO: CN=Louise Cullen/O=NWHB is out of the office. (returning 18/04/2017) Message-ID: <OF5889B08C.4B83D5E6-ON80258101.00739980-80258101.00739980(a)mailb.hse.ie> Content-Type: text/plain; charset="ISO-8859-1" I am out of the office until 18/04/2017. Please contact Tracey McCole on 071 9852900 if you require further assistance, otherwise I will attend to your email when I return Note: This is an automated response to your message "EpiData-list Digest, Vol 159, Issue 1" sent on 13/04/2017 18:00:15. This is the only notification you will receive while this person is away. *************************************************************************** "T? an fhaisn?is sa r?omhphost seo (ceangalt?in san ?ireamh) faoi r?n. Baineann s? leis an t? ar seoladh chuige amh?in agus t? s? ar intinn go bhfaighfidh siadsan amh?in ? agus gurb iadsan amh?in a dh?anfaidh breithni? air. M?s rud ? nach tusa an duine ar leis ?, t? cosc ioml?n ar aon fhaisn?is at? ann, a ?s?id, a chraobhscaoileadh, a scaipeadh, a nochtadh, a fhoilsi?, n? a ch?ipe?il . Seains gurb iad tuairim? pearsanta an ?dar at? san r?omhphost agus nach tuairim? FSS iad. M? fuair t? an r?omhphost seo tr? dhearmad, bheadh muid bu?och d? gcuirfe? in i?il don.Deasc Seirbh?s? ECT ar an nguth?n ag +353 71 9820555 n? ar an r?omhphost chuig ICT.Helpdesk(a)hse.ie agus ansin glan an r?omhphost seo ded' ch?ras." *************************************************************************** "Information in this email (including attachments) is confidential. It is intended for receipt and consideration only by the intended recipient.If you are not an addressee or intended recipient, any use, dissemination,distribution, disclosure, publication or copying of information contained in this email is strictly prohibited..Opinions expressed in this email may be personal to the author and are not necessarily the opinions of the HSE. If this email has been received by you in error we would be grateful if you could immediately notify the ICT Service Desk by telephone at +353 71 9820555 or by email to ICT.Helpdesk(a)hse.ie and thereafter delete this e-mail from your system" *************************************************************************** ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 159, Issue 2 ********************************************

1 0

Re: [EpiData-list] Problem defining the key variable for a relational
by EpiData development and support 25 May '17

25 May '17

Thank you Jamie, that would appear to be the problem. I'll try to redo the structure from scratch. -Ruwan -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list-request(a)lists.umanitoba.ca Sent: Wednesday, May 24, 2017 1:00 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 160, Issue 1 Send EpiData-list mailing list submissions to epidata-list(a)lists.umanitoba.ca To subscribe or unsubscribe via the World Wide Web, visit https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.umanitoba.ca_mail… 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. Problem defining the key variable for a relational database (EpiData development and support) 2. Re: Problem defining the key variable for a relational database (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Tue, 23 May 2017 21:10:26 +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] Problem defining the key variable for a relational database Message-ID: <MWHPR1201MB01589C72CC80AFF050E2F45696F90(a)MWHPR1201MB0158.namprd12.prod.outlook.com> Content-Type: text/plain; charset="us-ascii" Hi there, I have a relational database with three key variables (district_id; health facility_id; patient_id). It is relational as there are three forms: Patient Demographics, Patient Progress, Laboratory. For the Progress form, for some reason, when try to enter the variables in the key (Right click form>Define key), I cannot add anything more than the patient_ID. The other options are greyed out. For all other forms, entering multiple variables in the key is no problem. I'd appreciate some advice on what (obvious) option I am missing. Thank you! Ruwan ------------------------------ Message: 2 Date: Wed, 24 May 2017 11:35:46 -0400 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: EpiData List <epidata-list(a)lists.umanitoba.ca> Subject: Re: [EpiData-list] Problem defining the key variable for a relational database Message-ID: <89B424E3-7B17-4F75-8E4B-8106D0CD3AD1(a)bell.net> Content-Type: text/plain; charset=utf-8 I assume that your structure is like this: Demographics form \?> Progress form (1-many) \?> Laboratory form (1-many) Once you define a key(s) in demographics, it automatically defined for the child forms because it(they) define the relation. When you define a new key in progress, they key or keys you defined for Progress show, but are greyed out because you cannot remove them. So in progress, you can add a new key, which will be automatically defined for laboratory. You MUST know what your relationships and keys are before you start. Once you have created a subform, you cannot change the keys in the parent form. I find it best to set up the data forms with just the keys and maybe a couple of other fields first, to make sure the structure works for you. You can defined the type of relationship (1-1 or 1-many) and try out the flow of data entry from one form to another and back again. Then add in the rest of the fields. Jamie > On May 23, 2017, at 17:10, EpiData development and support <epidata-list(a)lists.umanitoba.ca> wrote: > > I have a relational database with three key variables (district_id; health facility_id; patient_id). It is relational as there are three forms: Patient Demographics, Patient Progress, Laboratory. > > For the Progress form, for some reason, when try to enter the variables in the key (Right click form>Define key), I cannot add anything more than the patient_ID. The other options are greyed out. For all other forms, entering multiple variables in the key is no problem. > > I'd appreciate some advice on what (obvious) option I am missing. ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.umanitoba.ca_mail… End of EpiData-list Digest, Vol 160, Issue 1 ********************************************

1 0