Table 3 |
||||||||
|
IDSRN task order outcomes by project type, FY 2000- FY 2003 |
||||||||
| Impact of task order on delivery systema |
Other outcomes |
|||||||
|
|
|
|||||||
| Type of project |
Number of awards |
Number complete |
Noneb |
Local |
Other IDSRN teams |
External |
Peer-reviewed paperc |
Follow-on task order awarded by AHRQ |
|
|
||||||||
| Total |
58 |
50 |
20 |
19 |
1 |
10 |
12 |
9 |
|
|
||||||||
| Tools |
17d |
15 |
3 |
4 |
1 |
6 |
1 |
4 |
| Research with IDS data |
12 |
11 |
8 |
2 |
0 |
1 |
5 |
1 |
| Clinical intervention |
12 |
9 |
2 |
7 |
0 |
1 |
1 |
0 |
| IDS systems review |
8 |
7 |
2 |
3 |
0 |
1 |
3 |
1 |
| Data capacity |
4 |
4 |
2 |
2 |
0 |
0 |
0 |
3 |
| Research, no IDS data |
3 |
3 |
3 |
0 |
0 |
0 |
2 |
0 |
| Dissemination vehicle support |
2 |
1 |
0 |
1 |
0 |
1 |
0 |
0 |
|
Source: MPR analysis of available information. a We classified impact based on evidence that the task order has had some operational impact (broadly defined) in the following settings: (1) locally within the delivery system in which the task order occurred, (2) among other delivery systems within IDSRN, or (3) external to IDSRN. In cases where a task order had an impact in multiple settings, we classified as highest setting (e.g., those with lcoal and external impacts were classified as external). b Reflects projects where there was no explicit evidence of impact. Because site visit time was limited, we could verify many but not all the outcomes for each task order with IDSRN partners/collaborators. c Number of tasks with 1+ publication. Only publications that are known to be published or accepted for pubilcation are included. d The 17 task orders reflect 12 separate bodies of work. The 17 include two sets of projects with an initial and follow-on task order and one set of four sequential projects. | ||||||||
Gold and Taylor Implementation Science 2007 2:9 doi:10.1186/1748-5908-2-9 |
||||||||
