- EpiData-list - University of Manitoba Mailing Lists

Change the colour of data entry form; and entering contact number for each person
by epidata-list＠lists.umanitoba.ca 16 Mar '10

16 Mar '10

Dear colleagues, I am designing relational database and would like the data entry staff to be able to enter the identification number (idno) and not to have to type in the contact number of each idno (person). The field for the contact number should be field automatically for each idno. More importantly, it should start with one for each idno. For example for idno 001 contact 1; 2; 3; 4; 5; 6; 7; 8; 9; 10 for idno 002 contact 1; 2; 3; ..................................100 Clearly, given that idno is a string; I have tried the following command which IDNO AFTER ENTRY IF IDNO=IDNO THEN LET CONTACTNUM=1+RECORDCOUNT ENDIF END The result is not different from automatic contact number. Any suggestions will be appreciated. Thank you for your time and suggestions Tieble

1 1

Re: Re: FW: Suggestion for automatic checks in new Epidata manager
by epidata-list＠lists.umanitoba.ca 12 Mar '10

12 Mar '10

Hi I would like to share my experience on the following suggestion by Jamie < A great addon or standalone module will be a simple XML editor for recxml files, to be used at our own risk. I don't know if such things exist in other areas, but there must be.> I have only recently started using epidata (Epidata Entry, the stable release) and must say the simple check file format was a great relief. The one thing lacking in the check file editor was lack of tools that can assist while writing the Check file codes (syntax highlighting). What i did was to start using a third party text editor (notepad++) and created a custom scheme that included coloured codes for if-then loops, various commands, comments shading etc. Immediately I was able to collapse the if-then loops, check if my commands were complete etc. I found it quite helpful in writing the CHK code. I can see if there is a way that it can be shared with the group. >From here on, I am afraid a wishlist starts :-) Having a XML editor within Epidata Manager I believe is a great idea. As a personal choice, for an XML editor for Epidata, I would like to have the following features w.r.t. check code: 1. Assistance that creates a termination code as soon as a command is inserted. Will help in creating compete codes 2. Syntax highlighting: Will decrease spelling mistakes and omission of closing sections (use of multiple brackets, END, ENDIF etc ), 3. Variable list: Will decrease spelling mistakes ! 4. Command list and assistance: type initial letters and the possible commands come as a dropdown ! An XML template can also probably be developed that has sections on: 1. Legal values and codes 2. Missing values 3. Before file commands 4. Before Record commands 5. Variable specific Commands: Calculations, If-then loops, Hide, Unhide, Key Unique 6. After Record commands 7. After File Commands But I agree that this would be probably a very low priority task. Wishlist ends ! Regards Vivek

1 0

Suggestion for automatic checks in new Epidata manager
by epidata-list＠lists.umanitoba.ca 11 Mar '10

11 Mar '10

Hi All, Jens was here at Epicentre to discuss some of the future plans for Epidata, and we had a brief overview of Epidata manager. As someone who writes qes/chk files using a text editor, I was disappointed to hear that it would not be possible to do this using Epidata manager (although the possibilty is there to import pre written qes files). In discussion with Jens, we talked about a solution to how a pre-written chk file can also be incorporated with Epidata manager. My suggestion is to have a data dictionary, where you not only specify the variable name, variable label, value labels and the data format, but you also add attributes for missing values, range checks , legal values etc. The dictionary could be a CSV file, that can be easily created using excel. Something along the lines of ..... Ideally however, what I would like is to have more flexibility, where you can assign the same attribute to the variables concerned in one statement, rather than listing one by one as a above, for example For all variables whose value 9 should be treated as missing, the attribute missing can given using for example the for loop as in stata, for gender locat type case { missing=9 } Also for those variables that share the same labels, you should be able to define one label and then assign to the variable concerned. Once the dictionary is imported into Epidata manager, you can then use the graphics device to organise the data entry screen. Food for thought, I hope? All the best Sarala

1 2

Can Epi Data be used on a Macbook
by epidata-list＠lists.umanitoba.ca 04 Mar '10

04 Mar '10

Just wondering if Epi Data can be run on a Apple Mac machine. Any experiences?? Thanks for any input Conrad

1 4

Re: [EpiData-list] Outbreak analysis/gnerating attack rate tables
by epidata-list＠lists.umanitoba.ca 02 Mar '10

02 Mar '10

thanks Jamie - that is great. Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 >>> <epidata-list(a)lists.umanitoba.ca> 2/03/2010 2:42 p.m. >>> You can do this using the menus. When you select TABLES on the Analysis task bar, the dialogue box you get can be expanded by dragging the lower left corner. Then the full set of options appears. You can check Compact for the Table Type and then choose RR or OR, etc. Jamie Hockin Ottawa -- 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://smx.co.nz ______________________________________________________________________________

1 0

Outbreak analysis/gnerating attack rate tables
by epidata-list＠lists.umanitoba.ca 01 Mar '10

01 Mar '10

Hi I have recently upgraded to version 2.2.171 of epidata analysis. I mainly use Epidata analysis to analyse disease outbreaks and with this new version I am finding it more difficult to ask for the attack rate table that is such a useful tool. Perhaps I am getting confused because I have not used epidata analysis for a while, but I thought that in earlier versions, it was possible to select an attack rate table (with relative risk, CI and pvalue for all exposures of interest) using options from the analysis menu. This time I had to search around the help menu and try and find the code. The code I used was tables SICK VARIABLE 1 VARIABLE 2 etc /CT/oa. Is there some way I can ask for this table through the menus? The reason I am asking is that I want to show other people in our unit how to use epidata to create an attack rate table and I think they will find it easier to go through a menu. thanks very much Christine istinfo/epidata ( 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..." Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 -- 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://smx.co.nz ______________________________________________________________________________

1 1

remove me from this list
by epidata-list＠lists.umanitoba.ca 23 Feb '10

23 Feb '10

remove me from this list

1 0

Status and plans for development (as of February 2010)
by epidata-list＠lists.umanitoba.ca 22 Feb '10

22 Feb '10

This is a brief status of developments - (rather technical in content) It is reassuring to see, that the interest in testing is rather large (Approximate download counts for latest version: Linux 50 , Mac 75 and Windows 300). Few comments have been given on the list, but I take that as a positive indication - I hope I am right, otherwise please notify on the list. The short story is: We are definitely moving forward - the basic way of working in graphic mode with data definition is more or less in place. But we must spend time on implementing related data structures and finding a final data structure. Therefore the first EpiData Entry Client based on the new principles will not come out until some time from now. The longer story is: During the most recent decade use of standardised data formats in public sectors and research has become an increasingly important issue. The idea of this is that data should be usable in any application and system based on published verifiable standards (XML based). XML is one of the structured information formats for machine readable information published by the W3C organisation - and is very complex - other ones from W3C are css and html. The published standards for XML based data documentation and storage of data as such are unfortunately plenty, a few of these are DDI (see DDI-alliance.org), CDISC ODM (see cdisc.org), SDMX (see sdmx.org). It seems as medicine, national statistics and the social sciences each have developed their own. The only common denominator seems to be in relation to overall descriptions such as "title", "contributor", abstract etc. These terms are well known from citations and are based on a metadata set called Dublin Core Metadata (see http://dublincore.org/specifications/). For implementation of a XML based file format in the EpiData Software it would seem obvious to NOT develop a new one, but instead use one or more of the mentioned ones. Therefore there have been discussions with data documentation specialists at the Danish Data Archives (see http://samfund.dda.dk/default-en.asp). Following these discussions and after studying several published standards it has been decided that the EpiData Software XML format will conform to the overall principles of the mentioned standards, but also that we must work with a restricted set of these. The nature of the EpiData project is to be focused on simplicity and we must stick to this principle. Otherwise we would be lost in months of generalisation, of no interest to the general user and also completely unrealistic within the economical and personal resources available. The time frame for the next phases are uncertain, but I will give orientation on this list as improvements are made and obstacles removed. Most likely there will be a meeting in the second week of March in Paris for detailed discussions on some of these issues. More information on that later. regards Jens Lauritsen EpiData Association

1 0

Re: Copy and Paste an Entry
by epidata-list＠lists.umanitoba.ca 17 Feb '10

17 Feb '10

Hello YC, Though i appreciate the solution YMP is giving you, i think you can also think of using the repeat command, since it is more easy play around with. With that you can be able to enter a field once and the next recode the field comes with the previous entry as a default which just needs your confirmation. All the best Edson BN On Tue, Feb 16, 2010 at 10:00 AM, <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. RE: Copy and Paste an Entry? (epidata-list(a)lists.umanitoba.ca) > 2. Re: Copy and Paste an Entry? (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 15 Feb 2010 18:51:52 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: RE: [EpiData-list] Copy and Paste an Entry? > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: <00bf01caae67$8ee97710$acbc6530$@martin-prevel@ird.fr> > Content-Type: text/plain; charset="utf-8" > > Hello, > > I think the best way to get round this problem is to have a relational data > base with two files: > (i) the "Master" file with patient's information > (ii) the related file with daily information > > There are several examples of such related data entry and how it works on > the Epidata website > > Hope this helps > > YMP > > > -----Message d'origine----- > De : epidata-list-bounces(a)lists.umanitoba.ca [mailto: > epidata-list-bounces(a)lists.umanitoba.ca] De la part de > epidata-list(a)lists.umanitoba.ca > Envoyé : lundi 15 février 2010 17:38 > À : epidata-list(a)lists.umanitoba.ca > Objet : [EpiData-list] Copy and Paste an Entry? > > > Hello. I was wondering if it is possible to copy and paste an entry? I am > entering data for patients at a hospital by day, and each time I enter a > new day's entry I have to re-type the patients' information. Is there a way > to copy a previous entry for a patient and paste it on the new entry? > Please help me as this adds a large amount of time to my work. > > Thank you, > YC > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > > ------------------------------ > > Message: 2 > Date: Mon, 15 Feb 2010 13:22:33 -0500 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Copy and Paste an Entry? > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <BLU0-SMTP79433833F8433A3AF41361FD4A0(a)phx.gbl> > Content-Type: text/plain; charset=us-ascii > > See the example titled "Relate example - Clinical Study with four forms" on > the Examples page - click on the link on the main page at epidata.dk > This is how to structure the related files. > See the example titled "Relate example - Household, Person, Visit" to see > how to copy information from one entry screen to another--you do this with > GLOBAL variables. > > This is a very common set up for clinical records. > > Jamie Hockin > Ottawa > > On 2010-02-15, at 11:40 AM, epidata-list(a)lists.umanitoba.ca wrote: > > > > > Hello. I was wondering if it is possible to copy and paste an entry? I am > > entering data for patients at a hospital by day, and each time I enter a > > new day's entry I have to re-type the patients' information. Is there a > way > > to copy a previous entry for a patient and paste it on the new entry? > > Please help me as this adds a large amount of time to my work. > > > > Thank you, > > YC > > _______________________________________________ > > EpiData-list mailing list > > EpiData-list(a)lists.umanitoba.ca > > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 76, Issue 3 > ******************************************* > -- Edson Byamukama Po Box 12027 Kampala, Uganda Office : +256 414251025 Mobile: +256 712202650

1 0

Re: EpiData-list Digest, Vol 76, Issue 3
by epidata-list＠lists.umanitoba.ca 16 Feb '10

16 Feb '10

Hi there, As I am not sure what information you have in your hands, I assume you could add check before the data entry and chose the *repeat* option for the required field information. Consequently, the information will remain until you changed it. Best wishes Tieble On 16 February 2010 18:00, <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. RE: Copy and Paste an Entry? (epidata-list(a)lists.umanitoba.ca) > 2. Re: Copy and Paste an Entry? (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 15 Feb 2010 18:51:52 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: RE: [EpiData-list] Copy and Paste an Entry? > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: <00bf01caae67$8ee97710$acbc6530$@martin-prevel@ird.fr> > Content-Type: text/plain; charset="utf-8" > > Hello, > > I think the best way to get round this problem is to have a relational data > base with two files: > (i) the "Master" file with patient's information > (ii) the related file with daily information > > There are several examples of such related data entry and how it works on > the Epidata website > > Hope this helps > > YMP > > > -----Message d'origine----- > De : epidata-list-bounces(a)lists.umanitoba.ca [mailto: > epidata-list-bounces(a)lists.umanitoba.ca] De la part de > epidata-list(a)lists.umanitoba.ca > Envoyé : lundi 15 février 2010 17:38 > À : epidata-list(a)lists.umanitoba.ca > Objet : [EpiData-list] Copy and Paste an Entry? > > > Hello. I was wondering if it is possible to copy and paste an entry? I am > entering data for patients at a hospital by day, and each time I enter a > new day's entry I have to re-type the patients' information. Is there a way > to copy a previous entry for a patient and paste it on the new entry? > Please help me as this adds a large amount of time to my work. > > Thank you, > YC > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > > ------------------------------ > > Message: 2 > Date: Mon, 15 Feb 2010 13:22:33 -0500 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Copy and Paste an Entry? > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <BLU0-SMTP79433833F8433A3AF41361FD4A0(a)phx.gbl> > Content-Type: text/plain; charset=us-ascii > > See the example titled "Relate example - Clinical Study with four forms" on > the Examples page - click on the link on the main page at epidata.dk > This is how to structure the related files. > See the example titled "Relate example - Household, Person, Visit" to see > how to copy information from one entry screen to another--you do this with > GLOBAL variables. > > This is a very common set up for clinical records. > > Jamie Hockin > Ottawa > > On 2010-02-15, at 11:40 AM, epidata-list(a)lists.umanitoba.ca wrote: > > > > > Hello. I was wondering if it is possible to copy and paste an entry? I am > > entering data for patients at a hospital by day, and each time I enter a > > new day's entry I have to re-type the patients' information. Is there a > way > > to copy a previous entry for a patient and paste it on the new entry? > > Please help me as this adds a large amount of time to my work. > > > > Thank you, > > YC > > _______________________________________________ > > EpiData-list mailing list > > EpiData-list(a)lists.umanitoba.ca > > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 76, Issue 3 > ******************************************* >

1 0