WebCIS: large scale deployment of a Web-based clinical information system.

George Hripcsak, James J. Cimino, S. SenguptaPubMed 1999

TL;DR

This paper details the deployment of WebCIS, a web-based clinical information system at Columbia-Presbyterian Healthcare. It addresses the challenge of making vast amounts of clinical data accessible and usable across a large institution, demonstrating how a web architecture can integrate with existing systems to improve functionality and availability, despite significant deployment hurdles.

What Problem Does This Paper Address?

The paper tackles the challenge of providing widespread, timely access to electronic medical records within a large healthcare institution. Traditional clinical information systems often have clunky, outdated interfaces and are difficult to scale or update. The emergence of the World Wide Web offered a promising new paradigm for user interfaces, but its effectiveness for large-scale, mission-critical deployments like clinical information systems was still largely unproven. The authors aimed to replace a legacy character-based system (DHIS) with a modern web-based interface (WebCIS) that could leverage the existing robust clinical data architecture while offering improved usability and accessibility. This includes overcoming issues like the need for new hardware, user training for web technologies, and ensuring performance and security in a distributed environment.

Methods

WebCIS is built upon Columbia University's existing clinical information system architecture. This architecture includes a centralized clinical repository, a Medical Entities Dictionary (MED) for managing coded data, an HL7 interface engine for data transfer, and an Arden Syntax-based event monitor for decision support. WebCIS itself is implemented using Common Gateway Interface (CGI) programs written in C, running on a UNIX web server. These CGI programs generate HTML and JavaScript, which are then delivered to the client web browser. The system communicates with the mainframe-based repository via TCP/IP sockets. Key security features include token-based authentication, LDAP for authorization, SSL encryption, permanent audit logs, and application timeouts.

Datasets

Not discussed in the paper. The paper focuses on the system architecture and deployment rather than specific datasets used for training or evaluation.

Key Insights and Ideas

  • Web as a Unifying Interface: The web browser, with its ubiquity and user familiarity, provides a powerful and cost-effective interface for accessing complex clinical data, bridging the gap between sophisticated backend systems and end-users.
  • Leveraging Existing Architecture: WebCIS demonstrates that a new web-based front-end can be successfully layered onto a well-established, albeit older, clinical information system architecture with minimal changes, preserving the investment in the existing infrastructure.
  • The MED as a Central Hub: The Medical Entities Dictionary (MED) plays a crucial role, not only in defining coded data but also in defining "clinical views" and spreadsheets. This allows for flexible data presentation and easier incorporation of new data types from various sources, including other institutions.
  • Deployment Challenges are Significant: While web development is fast, the practicalities of large-scale deployment—hardware upgrades, user training, and managing diverse user environments—remain substantial and costly.
  • Security is Paramount and Complex: Implementing robust security measures (authentication, authorization, encryption, auditing) is critical for clinical systems, especially when accessed over the internet, and requires careful consideration of user behavior and system vulnerabilities.

Key Results

  • User Adoption: As of June 1999, WebCIS was used by 810 physicians, with a target of 4300 users by the end of the year.
  • Performance: While the legacy DHIS system had sub-second response times, WebCIS aims to provide similar performance. The paper notes that existing web servers are expected to meet the demands, and while database throughput might be a challenge, no significant load increase had been detected at the time of writing.
  • Security Features: WebCIS incorporates multi-factor authentication, role-based authorization, SSL encryption, and permanent audit trails.
  • Deployment Scope: The system is deployed across nursing stations, clinics, administrative offices, physician offices, and even users' homes.

Limitations and Future Work

  • Hardware Requirements: A significant portion of the deployment cost involved replacing older computers that could not run modern web browsers.
  • User Training: Training users who are unfamiliar with web technologies has been a challenge, requiring demonstrations and informal sessions.
  • Browser Incompatibilities: WebCIS requires specific browser versions (Netscape 4.04+) due to JavaScript implementation differences, which can be a barrier for users who prefer other browsers like Internet Explorer.
  • Technology Obsolescence: The authors acknowledge that web technologies evolve rapidly, and a system built on CGI and JavaScript today might require significant updates in the future.
  • Future Work: The paper highlights the potential for multi-institution support, aiming to merge clinical information from various hospitals into a single repository and use WebCIS as a common viewer. This requires ongoing efforts in data definition and integration.

Summary updated

Abstract

WebCIS is a Web-based clinical information system. It sits atop the existing Columbia University clinical information system architecture, which includes a clinical repository, the Medical Entities Dictionary, an HL7 interface engine, and an Arden Syntax based clinical event monitor. WebCIS security features include authentication with secure tokens, authorization maintained in an LDAP server, SSL encryption, permanent audit logs, and application time outs. WebCIS is currently used by 810 physicians at the Columbia-Presbyterian center of New York Presbyterian Healthcare to review and enter data into the electronic medical record. Current deployment challenges include maintaining adequate database performance despite complex queries, replacing large numbers of computers that cannot run modern Web browsers, and training users that have never logged onto the Web. Although the raised expectations and higher goals have increased deployment costs, the end result is a far more functional, far more available system.
BibTeX
@inproceedings{hripcsak1999webcis,
  author = {George Hripcsak and James J. Cimino and S. Sengupta},
  title = {{WebCIS: large scale deployment of a Web-based clinical information system.}},
  booktitle = {PubMed},
  year = {1999},
}

Loading related content...

Figure