Blazing New Trails: Mechanisms and Objectives of CCNR Data Sharing
BLAZING NEW TRAILS: MECHANISMS AND OBJECTIVES OF CCNR DATA SHARING
Author 1
Author 1 Title
Author 1 School
Author 1 University
Author 1 City, State
Author 3
Author 3 Title
Author 3 School
Author 3 University
Author 3 City, State
Author 2
Author 2 Title
Author 2 School
Author 2 University
Author 2 City, State
Author 4
Author 4 Title
Author 4 School
Author 4 University
Author 4 City, State
Aim: The aim of this presentation is to describe efforts to design and develop the University of Colorado (CU) Patient Initiated Data system, or CUPID. CUPID is a data analysis system designed to extract near-real-time patient-outcome metrics from electronic health record (EHR) data and deliver trending metrics back to hospitals for operational decision-making. The purpose of CUPID is to improve the efficiency and quality of patient care by (a) integrating nurse-sensitive patient-outcome data and (b) representing data in useful formats for decision-making.
Background: There is a need for distributed data sharing that enables analysis of patient data aggregated from multiple hospitals to answer operational research questions - especially those questions related to patient outcomes such as HRQOL. The University of Colorado College of Nursing (CON) is leading the effort to develop such a data sharing system, in collaboration with regional hospitals and other stakeholders.
| Figure 1. Overview of System Process Flow
|
Approach: The Colorado Collaborative for Nursing Research (CCNR)
provides research leadership for connecting specific modes of acute care
nursing to desired patient-outcome trajectories. The CCNR technical team has
deep experience in nursing research, informatics, and system design. The
current goal of the team is to specify data-sharing system requirements and
evaluate candidate systems that will meet these requirements. Our design
approach is informed by a reusable design philosophy through which we are
leveraging existing systems and infrastructure to meet system goals. Outcomes: We have created a general system process flow (Figure 1). A partial list of CUPID usage includes (a) isolating patient-outcome metrics and trends that predict 30-day hospital readmission and (b) capturing nursing work as it relates to HRQOL and other patient outcomes.
Conclusion: CUPID sets up a mechanism for (a) establishing nurse-sensitive patient-outcome metrics; (b) extracting EHR data to operationalize those metrics; (c) converting extracted data to a common format; (d) providing features for statistical analysis; and, (e) delivering timely results back to decision-makers at data-contributing hospitals. The CUPID system design permits near-real-time tracking of nurse-sensitive patient outcomes and evaluation of nursing interventions. This presentation will cover system design principles, project collaborators, and project progress.