SAES-422 Multistate Research Activity Accomplishments Report

Status: Approved

Basic Information

Participants

Abdulkadri, Abdullahi (abdulka5@msu.edu)-Michigan State University; Anliker, Jean (janliker@nutrition.umass.edu)-University of Massachusetts; Auld, Garry (auld@cahs.colostate.edu)-Colorado State University; Baker, Susan (sbaker@cahs.colostate.edu) -Colorado State University; Barale, Karen (kbarale@wsu.edu)-Washington State University; Betts, Nancy (nancy.betts@okstate.edu)-Oklahoma State University; Koszewski, Wanda (wkoszewski1@unl.edu)-Michigan State University; Lambea, Maria (lambea@osu.edu)-Ohio State University; Misner, Scottie (misner@ag.arizona.edu)-University of Arizona; Orr, Robin (raorr@illinois.edu)-University of Illinois; Procter, Sandy (procter@ksu.edu)-Kansas State University; Sutherland, Barbara (bsutherland@ucdavis.edu)-University of California-Davis; Tschida, Pat (ptschida@umn.edu)-University of Minnesota; Wardlaw, Mary Kay (wardlaw@uwyo.edu)-University of Wyoming; Welsh, Susan (swelsh@csrees.usda.gov)-CSREES; Wilson, Mary (wilsonm@unce.unr.edu)-University of Nevada-Reno

Because this was NC1169 first annual meeting and included a number of scientists not part of the writing team, we began with a review of the proposal, objectives, proposed activities and timelines. Subsequently, the bulk of the time was spent in small group work (divided by project objectives). Administrative guidelines for publications and use of data were drafted and will be confirmed by whole committee. Scientists (2-3) who take the lead on writing are first authors with others involved listed alphabetically after leads. Given size of group, it is unlikely that everyone can be listed on each publication but all will be included in acknowledgements. Presentations at professional meetings will follow similar guidelines. NC1169 data is for the use of the entire committee but individual states can analyze and publish state data. Data, publications, and presentations from spin off projects are under control of those conducting those projects. New officers were elected and a policy for staggering leadership was set. 2008-2009 executive committee: co-chairs (S. Baker, G. Auld), secretary (S. Procter), co-vice chairs (W. Koszewski, M. Wilson), objective leaders (N. Betts, W. Koszewski). A project website and list serve will be developed when all involved stations/scientists are confirmed. Discussion and identification of different station support for NC1169 - support varies from about $1000 to cover travel to $6000 to $12,000 to support research activities, graduate assistants, and participant incentives. Objectives 1 and 2  in context of identifying new or modified evaluation tools for testing, discussed issues related to paraprofessional training, need (or not) for specific nutrient analyses, pre/post vs. retrospective pre/post testing, quality of match between behavior checklist items and best practices as well as correspondence with common curricula. Overall goal refined to integration of a dietary assessment and behavioral checklist that addresses the Dietary Guidelines and accurately measures changes in behaviors related to the Dietary Guidelines. States involved with objective 3  (9) are piloting the Quality of Life (QOL) instrument among paraprofessionals (n = 75) and/or participants (n = 200). The pilot should be complete by fall 2008 in time for next annual meeting. Procedures for conducting free listings, and focus groups with paraprofessionals, stakeholders and program graduates being drafted as are procedures for conducting phone interviews with EFNEP professionals (supervisors of paraprofessionals). A Spanish translation of QOL will be drafted by Arizona. Existing QOL tool being piloted is too long for regular EFNEP evaluation but could be used with subsets of participants or shortened based on the pilot work. Agreed that 2009 meeting will be held in Chicago at Illini Center in October.

Accomplishments

Short-term Outcomes: None at this time. Outputs: None at this time. Activities: (Completed) formed workgroups by objectives; designed and started quality of life pilot research project; established conference call schedules by objective (monthly) and executive committee (quarterly). (Planned) confirm involvement of scientists who were not at meeting; develop project website and list serve; collect quality of life pilot data Milestones: (Completed) implementation of quality of life pilot research project; appointment of executive committee and draft of processes for writing/authorship of publications. (Future) Objectives 1 and 2  compile annotated bibliography related to evaluation of EFNEP and dietary assessment; consolidate behavior checklist items for testing; identify criteria for judging validity and practicality of behavior check list and dietary assessment. Objective 3 Complete quality of life pilot data collection and analyses; develop focus group and professional interview protocols; develop and implement free listing and/or flip chart protocols.

Impacts

  1. The literature review described above will be available to other community nutrition programs targeting limited resource audiences.
  2. The validated dietary assessment tools, including the behavior checklist, linked to the Dietary Guidelines will be appropriate for use by EFNEP and other community nutrition programs.
  3. Confirmation that the value of EFNEP extends beyond nutrition related knowledge and behavior, i.e., Quality of Life, might be critical to more accurately assessing EFNEPs impact and identifying influences on participants who make lifelong, sustainable changes in their lives.
  4. Indicators: As a result of this project, EFNEP (and other community nutrition programs) will have valid and reliable evaluation tools to use in measuring programs effectiveness (knowledge gained, behaviors changed) that will include Quality of Life indicators.

Publications

Project has just begun; no publications at this time.
Log Out ?

Are you sure you want to log out?

Press No if you want to continue work. Press Yes to logout current user.

Report a Bug
Report a Bug

Describe your bug clearly, including the steps you used to create it.