Evaluation Reporting Template for Interactive Health Communication Applications,Version 1.0, Science Panel on Interactive Communication and Health
Sections:I. Description of ApplicationII. Formative and Process Evaluation III. Outcome Evaluation
2. Name(s) of developer(s): 3. Relevant qualifications of developer(s): 4. Contact(s) for additional information: 5. Funding sources for development of the application (e.g., commercial company, government, foundation/nonprofit organization, individual): 6. Category of application (e.g., clinical decision support, individual behavior change, peer support, risk assessment): 7. Specific goal(s)/objective(s) of the application (What is the application intended to do? List all, as applicable): 8. Intended target audience(s) for the application (e.g., age group, gender, educational level, types of organizations and settings, disease groups, cultural/ethnic/population groups): 9. Available in languages other than English? Yes No (specify): 10. Technological/resource requirements of the application (e.g., hardware, Internet, on-site support available): 11. Describe how confidentiality or anonymity of users is protected: 12. Indicate who will potentially be able to get information about users:
2. Are the specific original sources of information cited within the application? Yes No 3. Describe the methods of instruction and/or communication used (e.g., drill and practice; modeling; simulations; reading generic online documents, interactive presentations of tailored information, specifying methods used): 4. Describe the media formats used (e.g., text, voice/sound, still graphics, animation/video, color): 5. For each applicable evaluation question below indicate (i) the characteristics of the sample(s) used and how they were selected, (ii) the method(s) of assessment (e.g., specific measures used), and (iii) the evaluation results: 6. If text or voice is used, how was the reading level or understandability tested? 7. What is the extent of expected use of the application (e.g., average length and range of time, number of repeat uses)? 8. How long will it take to train a beginning user to use the application proficiently? 9. Describe how the application was beta tested and debugged (e.g., by what users, in what settings):
(iv) the evaluation results: 2. How much do users like the application? 3. How helpful/useful do users find the application? 4. Do users increase their knowledge? 5. Do users change their beliefs or attitudes (e.g., self-efficacy, perceived importance, intentions to change behavior, satisfaction)? 6. Do users change their behaviors (e.g., risk factor behaviors, interpersonal interactions, compliance, utilization of resources)? 7. Are there changes in morbidity or mortality (e.g., symptoms, missed days of school/work, physiologic indicators)? 8. Are there effects on costs/resource utilization (e.g., cost-effectiveness analysis)? 9. Do organizations or systems change (e.g., resource utilization, effects on "culture")?
2. Do any of the evaluators have a financial interest in the sale/dissemination of the application? Yes No (specify): 3. Funding sources for the evaluation(s) of the application (e.g., developer's funds, other commercial company, government, foundation/nonprofit organization): 4. Is a copy of the evaluation report(s) available for review on request? Yes No (how to obtain):
* Formative evaluation is used to assess the nature of the problem and the needs of the target audience with a focus on informing and improving program design before implementation. This is conducted prior to or during early application development, and commonly consists of literature reviews and reviews of existing applications and interviews or focus groups of "experts" or members of the target audience. Process evaluation is used to monitor the administrative, organizational, or other operational characteristics of an intervention. This helps developers successfully translate the design into a functional application and is performed during application development. This commonly includes testing the application for functionality and also may be known as alpha and beta testing. ? Outcome evaluation is used to examine an intervention's ability to achieve its intended results under ideal conditions (i.e., efficacy) or under real world circumstances (i.e., effectiveness), and also its ability to produce benefits in relation to its costs (i.e., efficiency or cost-effectiveness). This helps developers learn whether the application is successful at achieving its goals and objectives, and is performed after the implementation of the application. ? Design types are grouped according to level
of quality of evidence as classified by the U.S. Preventive Services Task
Force and the Canadian Task Force on the Periodic Health Exam. (U.S. Preventive
Services Task Force. Guide to clinical preventive services. 2nd
ed. Washington, DC: US Department of Health and Human Services, 1996.)
Source: Wired for Health and Well-Being.
|