146s Abstracts P58 THE BENEFITS OF AN INTRANET AS A COORDINATING CENTER TOOL FOR MULTI-CENTER RESEARCH PROJECTS: THE EPIDEMIOLOGY DATA CENTER INTRANET Jeffrey P. Martin, John A. Winegarden, Kimberly C. Beringer and the New Technologies Group University of Pittsburgh Pittsburgh, Pennsylvania lntranets are appearing in many organizations. With the proliferation of inexpensive and easy-to-use Internet tools (e.g., Web browsers, HTML editors, Web servers, etc.), organizations are recognizing the potential (and virtually limitless) benefits of designing, implementing and maintaining an Intranet for internal use. An Intranet, by definition, is the utilization of Internet/Web and network tools for the access of an information repository within an organization. With the integration of Internet tools on virtually every desktop in the Epidemiology Data Center (EDC) and the creation of the EDC lntranet, we have provided an information repository for EDC staff by which they can access frequently used information rapidly and directly from their desktop. This information includes but is not limited to part-time staffing schedules, Help Desk, PC troubleshooting database, phone lists, conference room scheduling, EDC reference library database, etc. Specifically, the EDC Intranet is utilized for the training of new personnel. New personnel can readily gain access to policy documentation related to such things as security and data management practices. This poster will present a colorful picture of our Intranet and outline the benefits of maintaining an Intranet. P59 DESIGN AND IMPLEMENTATION OF A CLINICAL RESEARCH DATABASE IN CLIENT/SERVER ARCHITECTURE Daniel Wu, Kai-Hsiung Lii, Mohan Nibhanupudi, Sprinagesh Agrawal, Rita Krishtul, John Speakman, Jun Yan, Collette Houston, Elinor Miller and Colin Begg Memorial Sloan-Kettering Cancer Center New York, New York In 1991 we began an initiative to create a comprehensive Clinical Research Database (CRDB). The first prototype was installed in 1992 and since then several major upgrades have been completed. In this presentation we describe our experience in upgrading to a client/server architecture, completed in November 1996. The system now contains data from 960 research protocols, of which 340 are actively accruing patients, and over 37,000 patients. Over 250 clients are attached to the system. ln this presentation, we describe the challenges faced in designing and developing the new technology. The goals and problems can be summarized as follows: (1) development of consistent conventions for GUI applications while minimizing the negative impact on user friendliness; (2) implementation of real time access to data from other systems, in the face of performance and compatibility problems; (3) execution of complex reports on clients, a task that can consume the client computer resources for extensive time periods; (4) creation of an optimal configuration of views to facilitate ad hoc queries; (5) development of a functioning system of automatically generated e-mail from the CRDB in the face of clients which run various e- mail applications; (6) distribution of new or upgraded applications to clients efficiently, in a setting in which clients are connected to ten LANs; (7) optimization of distributed processing.

P58 The benefits of an intranet as a coordinating center tool for multi-center research projects: The Epidemiology Data Center Intranet

Download PDF Report

Upload
jeffrey-p-martin
View
212
Download
0

Embed Size (px)

Citation preview

146s Abstracts

P58 THE BENEFITS OF AN INTRANET AS A COORDINATING CENTER

TOOL FOR MULTI-CENTER RESEARCH PROJECTS: THE EPIDEMIOLOGY DATA CENTER INTRANET

Jeffrey P. Martin, John A. Winegarden, Kimberly C. Beringer and the New Technologies Group

University of Pittsburgh Pittsburgh, Pennsylvania

lntranets are appearing in many organizations. With the proliferation of inexpensive and easy-to-use Internet tools (e.g., Web browsers, HTML editors, Web servers, etc.), organizations are recognizing the potential (and virtually limitless) benefits of designing, implementing and maintaining an Intranet for internal use.

An Intranet, by definition, is the utilization of Internet/Web and network tools for the access of an information repository within an organization.

With the integration of Internet tools on virtually every desktop in the Epidemiology Data Center (EDC) and the creation of the EDC lntranet, we have provided an information repository for EDC staff by which they can access frequently used information rapidly and directly from their desktop. This information includes but is not limited to part-time staffing schedules, Help Desk, PC troubleshooting database, phone lists, conference room scheduling, EDC reference library database, etc. Specifically, the EDC Intranet is utilized for the training of new personnel. New personnel can readily gain access to policy documentation related to such things as security and data management practices. This poster will present a colorful picture of our Intranet and outline the benefits of maintaining an Intranet.

P59 DESIGN AND IMPLEMENTATION OF A CLINICAL

RESEARCH DATABASE IN CLIENT/SERVER ARCHITECTURE

Daniel Wu, Kai-Hsiung Lii, Mohan Nibhanupudi, Sprinagesh Agrawal, Rita Krishtul, John Speakman, Jun Yan, Collette Houston, Elinor Miller

and Colin Begg Memorial Sloan-Kettering Cancer Center

New York, New York

In 1991 we began an initiative to create a comprehensive Clinical Research Database (CRDB). The first prototype was installed in 1992 and since then several major upgrades have been completed. In this presentation we describe our experience in upgrading to a client/server architecture, completed in November 1996. The system now contains data from 960 research protocols, of which 340 are actively accruing patients, and over 37,000 patients. Over 250 clients are attached to the system. ln this presentation, we describe the challenges faced in designing and developing the new technology.

The goals and problems can be summarized as follows: (1) development of consistent conventions for GUI applications while minimizing the negative impact on user friendliness; (2) implementation of real time access to data from other systems, in the face of performance and compatibility problems; (3) execution of complex reports on clients, a task that can consume the client computer resources for extensive time periods; (4) creation of an optimal configuration of views to facilitate ad hoc queries; (5) development of a functioning system of automatically generated e-mail from the CRDB in the face of clients which run various e- mail applications; (6) distribution of new or upgraded applications to clients efficiently, in a setting in which clients are connected to ten LANs; (7) optimization of distributed processing.