Products

Task 400 – Recipe Maintenance

This task begins by prompting for the file name. Files that exist already will be listed and the one desired selected. If the new… choice is selected a new file name needs to be entered. New file names must start with a letter, have no spaces within the name and have 8 characters (letters or numbers) or less.

Recipe files can contain the definition of many recipes. Each recipe is identified by a code of up to 7 digits. As recipe files may eventually be converted to foods it is a good idea to use the same convention for their codes as are used for food codes.

T400 REC FILE

A food code is entered here. If the code exists already, the next prompt will be the options prompt where the recipe information can be modified. Otherwise a message will appear prompting for the creation of a recipe. Again, the options prompt will appear allowing the entry of recipe information.

T400 REC CODE

T400 NEW CODE

The various parts of a recipe can be defined using the recipe options listed here. The ingredient editing options change the same ingredient data, there are two ways of editing these for convenience.

T400 REC CODE OPTIONS

Attributes define a recipes profile. There can be two preparations for each recipe to be used as desired. Some will use preparion one for imperial units and preparation two for metric units. Some will use preparation one for a recipe with a small number of servings and preparation two for a much larger number of servings. Each preparation has its own profile and its own quantities for each ingredients. Other uses of preparations are up to the imagination and needs of the user. Of course, a single preparation can be used as well.

The fields defining a recipe are as follows:

  1. Recipe name: A description for the recipe. Remember this will also be used as a description for the food if the recipe data is ever converted to a food.
  2. Remarks: Any remark specific to this recipe. It serves as additional documentation to the recipe and is not used in conversion to a food and is an optional field.
  3. Hints line 1::Any hint specific to this recipe. It serves as additional documentation to the recipe and is not used in conversion to a food. Also an optional field.
  4. Target % H2O: This is used to compensate for cooking method. The recipe nutrient data will be adjusted to force this % moisture in the final recipe. It consists of a single number like 8.5 or 10 or 33.8, etc.  It this field is not used for target moisture it can be used for additional hint data and is an optional field.
  5. Where used:,Product Group:,Main Product: These are arbitraty and optional descriptions used to further define the profile of recipes. To use these fields as selectors in future report groupings a consistent set of descriptions must be developed and used. 
  6. Number of servings: A number, required to calculate nutrients per serving.
  7. Serving size: Specified in grams. 
  8. Unit of measure: This is always 0, the unit code for grams.
  9. Density: If known, is entered here as a number of grams per 100 ml. Is used in conversion to food. A food with a density can be used with volumetric units.
  10. Dates: The date created is automatically entered here. The other dates are optional and can serve as record keeping to monitor the progress of the recipe through its phases. Dates are entered using the format yyyymmdd.
  11. Recipe Type Code: These codes are arbitraty and optional and can be used as selectors in future report groupings. This requires a consistent set of descriptions to be developed and used 
  12. Preparation Time (mins): A number of minutes, again, used as selectors in future report groupings

T400 REC ATTRIBUTES

Ingredients are inserted and modified using either of the two following panels. Fields describing each ingredient are:

  1. Ingredient code: Ingredient codes come from food files and must exist there before they are used. Food codes for ingredients are found using the F6 information key with a keyword search term. Multiple keywords can be used. If seperated by spaces each keyword must be present, separated by commas, one or the other keyword can be present. The result of the search is a list of foods satisfying the search parameters. Choosing the desired food inserts its code in the ingredient code field.
  2. Unit code: This code is specific to the ingredient and a list of possible codes are accessed using the F6 information key. Choosing the desired unit code inserts its code int he unit field.
  3. Quantity: This is the quantity of the ingredient required for the recipe in “unit code” units.
  4. The E/F and the % Yield fields are not presently used and are reserved. The concept behind the E/F field was as an “each” parameter as in each of the servings would have this quantity of the ingredient. The total quantity of the ingredient would thus depend on the recipe’s profile information.

T400 REC INGREDIENTS 1

The above panel consists of multiple lines of entry per ingredient. As you tab from field to field you will see the space highlighted for each.

T400 REC INGREDIENTS 2

The above panel consists of a single line of entry per ingredient. Again, As you tab from field to field you will see the space highlighted for each.

The preparation panel is used to describe the preparation of the recipe. It is mostly meant to be used in managing cookbooks and is not used in the conversion of recipes to food codes. It consists of arbitrary text and it too is an optional field.

T400 REC PREP

Once all the data has been entered pressing the Esc key will save all the recipe data automatically and navigate back to the previous step or menu.

Recipes & CANDAT

Recipes are another source of food information. Not all foods can be found in food databases, There is a limitless number of recipes and thus a limitless number of foods. You only need to look at the number of recipe books that are available to have an idea of the number of foods that are possible.

A good study needs to be able to identify commonly used recipes in the target populations and find suitable foods to code for those recipes. Where there are no suitable codes, the ingredients of the recipe need to be identified and a suitable food defined from these ingredients. CANDAT has tools to do this and to manage the consequent data

The following are the two menu selections needed manage the tasks in the recipe module.

This from the main CANDAT menu and

menu main 4

this from the choices then presented:

menu recipes 400

The standard startup choices below are presented after the selection of a task and

T400 REC FILE MAINT ACT

are explained in Appendix A (click on the screen to see the explanation). The prompts that follow activating “START the task”  control the options for the task in question and are explained in the appropriate task chapter.

The list of tasks in the task menu area are listed in the order one would use them. More detailed information about each task can be found in that task’s chapter.

  1. 400 Recipe file maintenance – this is where recipes are defined, copied, modified, listed, etc.
  2. 410 Recipe file validation – once recipes have been created this task validates that the ingredients exist and that proper units have been specified for quantities
  3. 420 Recipe nutrient calculations – nutrients are calculated for each recipe and listed on a total and per ingredient basis. Ratings of recipes based on system Recommended Daily Intakes (RDI) are listed here as well
  4. 430 Recipe to food file conversion – to use recipe data as part of subject recalls or even as ingredients in other recipes, they must be made into foods using food files. The foods in these food files can then be used as input to subject data or recipe data and managed like regular food files
  5. 100 Food file maintenance – this task is part of the food files module. It is included here as a convenient link to food files once recipes have been converted to foods
  6. 440 Recipe reports by types – part of the definition of foods has optional fields which define attributes of the recipe. The reports in this task allow listing of recipes that satisfy those attributes.

How can I identify when and where my subjects ate their food?

The researcher can enter meal codes from 1 to 999. A typical way of using these codes is to set 1 to 9 as the first digit, 0 to 9 as the second digit and 0 to 9 as the third digit. For instance this could make 100 breakfast, 110 breakfast away, 111 breakfast at MacDonalds, etc… of course, any scheme is possible using these 3 digits.
The researcher can enter this data in a table of meal codes which are used to prompt data entry personnel and provide output in validation reports. This table is subject file specific. A meals table can thus be specific to each study.
Meal codes and descriptions appear in all meal detail reports. Meal codes are included in export files and can thus be used in spreadsheets and statistical packages.

View food and meal descriptions by pressing “F1” over the code

When reviewing data input it is now possible to see the descriptions of the food and the meal codes that have been entered. Pressing the “F1” key at the top left of the keyboard will show the description for about 2 seconds. If that is too long for you simply press another key. A quick way to go through all your input for foods is to simply go to the first food code, press F1, glance at the result and then press the arrow down key to go to the next food. You will need to press the arrow down key twice (if you are fast), once to remove the description of the active food and once to go to the next food. Pressing “F1” again shows you that food’s description. It can become a quick two finger action, very efficient.

The time the description is shown can vary. You can set a longer time using the system message utility. Again, pressing any key will remove the description and allow you to proceed.

The F1 key has also been implemented for the quantity field. Pressing F1 while in that field will show the food quantity in grams and its energy value based on the quantity and unit codes entered.

Recalls and reports

A typical Candat scenario

The navigation shown below is a good example of the navigation available throughout CANDAT. You will get used to using the function keys, particularly the keys “F6”, “F5”, “F1” and “Esc”.

Modules and tasks

The first to appear once Candat is started is the TASK MODULES screen. It contains a list of the modules available in CANDAT. Within each module is a list of tasks, each prefixed with a task number. For example, in module 3. Subject files… you will get a series of 300 level tasks. These tasks are related to subject entry, validation, reporting, etc… but all tasks that have to do with subjects.

You will see 300 related tasks in module 5. Questionnaire definition and input. That is because some of those tasks work with questionnaire data once it has been converted to subject files. Just an added convenience if you happen to be working with questionnaire data.

For now, choose the Subject module so that we can enter a simple recall to see how CANDAT works.

Subject files maintenance and reports

Subject file maintenance

 

This is where subject data is entered, on a per day, per meal basis. You can also configure general information about this subject file here.

Once you have started the task you may choose a user food file to activate. As you enter food codes this will allow CANDAT to automatically validate foods that may not be in the Master food file or Institute food file.

The next step allows you to select an existing subject file or create a new one.

We have chosen to create a new subject file which we have called “demo”, for the purposes of this tutorial. Please note that subject files can hold an unlimited number of subjects.

When first created we need to know whether this subject file will be used for questionnaires. Questionnaire subject files have a few more components to them. These can also be added later if you wish.

Up to 25 subject variables can be created per subject. This is where you define what those variables are. The variable names will serve to identify the data on reports.

 

This menu shows you what can be done with subject files. A bit overwhelming at first but necessary as your study evolves and you need to manage more and more of your data. For now we will just concentrate on entering subject recall data.

 

Candat allows up to 10 characters for a subject code. We have tried to make this a bit meaningful, as you can probably see from the characters. This can also be another place for you to classify the subjects. You must, however, make sure that the code you create is unique.

 

This is where you would populate the variable data that you defined before. Note that the definitions are specific to the subject file though the variable data changes from subject to subject (of course).

…and now we are able to enter actual food recall information, up to 7 days per subject. Specify the date using yyyymmdd coding. The date is important as Candat uses it to figure out the day of the week in “week-weighted” reports.

This is the main data entry screen for food data. You can also change the date here. A convenient way to navigate this screen is through the tab key and the arrow cursor controls. The “F6” key is especially convenient:

  • in the Meal Code field it will give you a selection of valid meal codes (note that you can define your own meal codes, up to 999 or them!)
  • in the Food Code field it will allow you to search foods. It will insert the code of the food you choose
  • in the Unit Code field it will give you a list of valid units for that food and insert the code of the one you choose

    All you have left to enter is the Quantity. The Food Frequency field is not used in recalls, it is meant for questionnaire data.

The next few screen pictures will show you data at various stages as well as detail information of your input you can see by pressing the “F1” key.

 

 

This screen shows a few foods entered for a breakfast. The highlighted area shows the foods that were entered. It was generated by pressing the “F1” key on the date field. It could also have been generated by pressing the “F1” key on the Unit Code field. Pressing the “F1” key on the other fields will translate the code for the information it generates. For example, if pressed on the “1” under Meal Code, it would show “Breakfast”, if pressed on the food code “28730” it would show “Coffee Brewed”.

How do you know which codes to enter? You just use the “F6” key. The “F6” key pressed in the Meal Code field would give you a list of valid meals (the list you defined if you did that). By selecting the meal you wish the code is automatically inserted. Under the Food Code field “F6” generates the same search it did in the Food Profile area above. The selected food has its code inserted. “F6” in the Unit Code field lists all the units valid for that code. Again, selecting the desired unit inserts its code in the right place and generates the description.

Experiment a bit, add a few more code, fill in the day. When you are done simply press Esc to be prompted for another day of entry.

You can continue entering intake dates until you have the maximum of 7 per subject or you can stop at this point by entering a “0” for the date.

 

A “0” date will bring up the subject editing menu where you can perform other actions on this subject.

When you are done simply press the Esc key repeatedly until you reach the menu to choose another task:

At this point the prompts become intuitive. In a big study we would do a lot of data entry, perhaps even by multiple data entry clerks. Their subject files could be combined, all the data validated using tasks 310 and 330, the nutrient data compiled and reports produced using task 340.

The validation from task 310 is shown here… if we had made entry errors they would appear in the last column. This validation is also a good way of checking against your entry data to make sure the right foods were coded and none were missed.

and then we simply skip to task 340 to show you some of the possible ways of reporting.

 

Toggle the Options to Yes for those you would like to see in reports. There are many ways of setting your options.

  • “Ctrl Y” selects them all to “Yes”,

  • “Ctrl N” selects them all to “No”,

  • “Y” make a “Yes”

  • “N” makes “No”

  • Just pressing “Enter” changes an entry back and forth.

For this example we will choose them all, “Ctrl Y”

…and press Esc to go to the next screen.

This allows us to select the nutrient we wish to see in the report.

We can add as many nutrients as we wish, pressing “F6” (standard now) on a code field allows us to choose nutrients we want to add. This process is shown below.

Here we have added LUTEIN, nutrient 837, you should see it in your reports, along with the others.

You can also choose to view other data in your reports, you can see the expressions and ratios we have chosen here…

The next few prompts allow you to select the subjects you wish to analyze and other reporting options such as printing, files to save, etc… they are explained below;

As you use Candat the above 4 screen shots will be very familiar to you. They are the standard selection sequence of database records, whether they be subjects (as they are here) or foods, recipes or questionnaires, the main databases used in Candat.

You can choose to sort by one of your selected nutrients, in this case we will leave the first nutrient, protein, as our sorting nutrient. Note that if you sort by nutrient and you view your reports at the food detail level, the foods will not be in the order entered but in the order of the selected nutrient value.

A nutrient report title which will appear on your printed reports…

In Candat you can define your own food groups. Food groups you define are stored in “category” files, each category file containing a list of food groups defined for that category and each food group containing a list of foods. Pressing “F6” here gives you a choice of available category files. Candat comes with the Canadian and USA category files pre-defined.

In this case we will bypass the category file selection by pressing Enter. This will have the effect of cancelling the reporting by food groups we previously selected.

 

The next few screens ask us for the name of the files to store the results. You can use the same name for each, very convenient as the same name can represent a particular part of your study or some particular purpose for the report, as here, “demo”

 

At this point Candat produces all the reports, ends the task and provides you with this friendly reminder.

You can then proceed to Start the task again (if you want to produce reports with other options) or choose another task.

View Reports

Of course, once you reach this stage you will probably press the “F5” key to look at your results. We go through this with you in the screens beginning on the next page.

Pressing Enter here lists all the text files (.TXT) and, in this case, gives the only file there.

The menu below is presented when you press the slash (“/”). You can then choose one of the presented options to manage the selected file.

This is the printed results file that was generated by Candat. For the columns to line up properly in external programs the font must be a fixed font, for example Courier New.

This file can be opened with a word processor or a text editor and printed from there if needed. Most of the time these files are not printed. We recently examined a file of 82 subjects and it had over 3,600 pages. That file included each food and showed detail by subject, by day and by meal with a meals summary at the end of each day and a days summary at the end of each subject.

In specifying default printers for CANDAT you can use a printer driver that creates .pdf files directly. This is very convenient as CANDAT allows you to specify very large page sizes which can be viewed in landscape (sideways) mode. If you do not have a .pdf printer driver you can still create this very large .txt file and then convert it using freely available .txt to .pdf converters. One that we have found very useful can be found at

http://www.verypdf.com/app/text-to-pdf-converter/

You can then use your favorite pdf reader application to easily browse through all the data.

You scan the .txt or the .pdf files to verify that the data you needed has indeed been generated. Once you are ready to use the data you can access it directly through the files in the SAVE folder. Those files can be imported directly either into a spreadsheet program or in a statistical program. Please see the next pages for examples of those files.

Once you have viewed the text files, you can proceed to the “save” files, the files that you can use to import your data into other programs.

Pressing Enter here give you a list of the save files generated by Candat.

Notice that the name of these files are the names we specified when we ran the reports. Some of these files document the layout of the data so that it can be provided to external programs that require that layout.

Most programs today will accept delimited files. Candat uses the “tab” character as a delimiter. The first row of these “tab-delimited” files contains a variable name which corresponds to the data in the following rows. You can change these variable names in three ways, if desired:

  • within Candat by changing the short description of the nutrient names;

  • by using an editor and changing the first row of the data file;

  • within the program you are using to view the data, using the features of that program (in spreadsheets you would change the first row, in statistical packages you would change the variable names).

The following pages are screen captures from these files and show what the information looks like. Remember, these files are formatted for computers to read, they may look a bit strange to you.

Some of the following files are wider than a screen. In Candat you view them by using the Ctrl-{arrow-right} key. In this case we have just done a screen capture of each screen that came up as we scrolled to the right. Remember, these files are meant to be used by computer programs.

1 of 5

2 of 5

3  of 5

4 of 5

5 of 5

1 of 4

2 of 4

3 of 4

4 of 4

This file has 25 fields, the first 10 only are shown here. No data was input after the weight field.

1 of 3

2 of 3

3 of 3

1 of 4

2 of 4

3 of 4

4 of 4

The DEMO.TXW and DEMO.WTD files look like the above DEMO.TXS files and are not reproduced here for simplicity. They would be different if there were multiple days in the week and some of the days in the week included weekend days as well.

I am sure that when you enter your own data and start looking at these reports you will get a good feeling for how thorough and accurate they really are.

A small aside but important note: You will notice that some of the values in the reports are negative. These are missing values generated by foods that did not have values for particular nutrients. In totals they are counted as zero. Statistical software usually treats missing values differently than regular values and take them into consideration in some calculations.

This concludes the “getting started” tutorial. By now you should have acquired the keyboarding skills required to get your information into and out of Candat and be sufficiently confident to explore the other areas of Candat.

Remember we are here to answer each and every one of your questions. Candat is the calculation engine that generates your data. You can now use whatever software you wish to complete your analyses and present or publish your data.

If you have any difficulties with the software please contact us and let us know. It is the only way we can help.

Subjects

Subjects are the source of information in a food consumption study. What did they eat and when did they eat it. Do we have just recall data or did they keep track of what they were eating? Are we looking at short term intake, the last day, the last week, the last 3 days?

How many subjects are needed for a good study? What other information to we need to get from them? How many researchers are collecting the information? Are they all using the same techniques for identifying food?

There are many questions to be answered here and we will tackle them in the following posts.

Recommended intakes

This is an area that has changed over the years. The ultimate flexibility requires that one be able to set levels by age and sex, by activity level and by pregnancy status. These levels can then be used to report on the adequacy of an individuals nutrient intake. Scores can then be given for individuals and average scores then derived for populations under study.

How do I know that all the foods in my study fall into my defined food groups?

In Task 300 you can create a table of unique food codes that appear in your subject file. Candat will go through all of your selected subjects and store the unique codes found in a table of your choosing. Once done you can go to task 210, the food groups definition task and choose the food category of interest. By pressing slash (“/”) you will get a secondary menu which allows you to work with the categories. One of the options here is the “Validate group definitions” option. This will create a listing for you which will show, for all the foods in your unique foods table, the group in which they will fall. If there is no code beside a food it means it will fall outside the defined groups and appear as such in your nutrient reports by group feature (Task 340).

Food Groups in CANDAT

Candat has a sophisticated food group analysis function. Food groups are lists of foods which belong to a specific group. These lists are defined as individual food codes or ranges of food codes. Definitions of multiple food groups taken together are stored in what Candat calls a “Category” file. It is thus possible to have category files for many different kinds of food groupings. For instance you could have a category file for groupings of interest to diabetic subjects or particular kinds of cancer subjects or heart disease subjects. There is no limit to the kinds of category files that you can define and, once defined, can use in all your studies.

Folate and Vitamin A and other nutrients in CNF 2010

The most recent version of the Canadian Food File (CNF) deals with Folate and Vitamin A differently. Please read the User guide (a free download with the trial version of CANDAT10) to get an understanding of the logic behind the changes. Once you have done this simply run a Food Profile within CANDAT and look at the available nutrients and their codes. This will give you an insight into the changes in this new version of the CNF. You can also run a nutrient distribution report (Task100, Option 3) to see all the available nutrients and their relative presence in the foods.

call: +1 (877) 977-2664 (toll free)