Abstract

OBJECTIVES/SPECIFIC AIMS: To develop a social network model of collaborations within and external to the University of Rochester Medical Center (URMC) CTSI using data from the annual Research Performance Progress Report (RPPR) as well as other sources, to provide longitudinal evaluation of the CTSI’s engagement with key stakeholder groups. METHODS/STUDY POPULATION: The annually submitted RPPR follows a specific format with well-defined sections. The Highlights, Milestones and Challenges Report includes areas in which CTSI function leaders provide details about program integration and innovation, including collaborations with other functions or external groups. The Highlights, Milestones and Challenges Report was qualitatively coded to identify function-collaborator dyads. Each entity in the dyad became a node in the network. Nodes were connected by edges named by the dyads. The network included two types of nodes. The first were CTSI internal functions/programs, i.e. the entities that submitted RPPR sections and formed an interconnected sub-network. The second type of nodes were entities external to the CTSI (collaborators, internal or external to the CTSI site). These entities were named by functions submitting RPPR narratives. External nodes with similar meanings were consolidated. Duplicate edges were removed. CTSI-external nodes were grouped into five stakeholder categories: URMC, University of Rochester (UR), community, other CTSA institutions, CTSA consortium. Thus, these nodes were connected to the CTSI internal nodes, but not to each other. A second source of collaboration data was function-reported internal metrics. As part of the internal metric data collection, functions list partners who play a role in improving metric data or who are responsible for providing data. Partners identified in the internal metrics data, but not specified in the RPPR, were added to the network. RESULTS/ANTICIPATED RESULTS: Twenty-three internal CTSI functions submitted an RPPR and represent the CTSI internal nodes. Internal CTSI functions identified 235 collaborations (edges): 125 collaborations with other CTSI internal functions, 57 collaborations with URMC entities, 14 with UR entities, 15 with the external community, 15 with other institutions (CTSA hubs and other universities), and 9 with CTSA consortium entities. Thirty-eight of the collaborations were identified in the internal metrics partners section. In total, the network comprised 104 nodes. Graph density was.022 for full network and.21 for the CTSI internal sub-network. The global clustering coefficient, a measure of connectivity, for the CTSI internal sub-network was.252. DISCUSSION/SIGNIFICANCE OF IMPACT: The RPPR provides an underutilized source of data for annually repeated analyses of internal and external CTSI collaborations and is a way to enhance use of this routinely collected information. Analyses of the network yield metrics for measuring CTSI reach and impact on stakeholder groups over time. For example, measures such as number of nodes representing entities external to CTSI and average vertex degree of the CTSI Internal nodes track aspects of CTSI collaborations. Visualizations using different layouts or highlighting different sub-networks provide a representation of CTSI engagement with the communities of stakeholders as well as insights to relationships between functions, regions of collaboration, and areas of gaps. These data also provide an important new mechanism to engage the CTSI leadership and function leads in understanding how their work contributes to the overall network and synergies they have with each other.

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.