help button home button JAMIA Bigger figures
HOME HELP FEEDBACK SUBSCRIPTIONS ARCHIVE SEARCH TABLE OF CONTENTS
This Article
Right arrow Full Text
Right arrow Full Text (PDF)
Right arrow Submit a response
Right arrow Alert me when this article is cited
Right arrow Alert me when eLetters are posted
Right arrow Alert me if a correction is posted
Services
Right arrow Similar articles in this journal
Right arrow Similar articles in PubMed
Right arrow Alert me to new issues of the journal
Right arrow Download to citation manager
Right arrow reprints & permissions
Citing Articles
Right arrow Citing Articles via HighWire
Right arrow Citing Articles via Google Scholar
Google Scholar
Right arrow Articles by Hripcsak, G.
Right arrow Search for Related Content
PubMed
Right arrow PubMed Citation
Right arrow Articles by Hripcsak, G.
Journal of the American Medical Informatics Association 4:S20-S30 (1997)
© 1997 American Medical Informatics Association

Symposium

IAIMS Architecture

George Hripcsak, MD

Affiliation of the author : Columbia-Presbyterian Medical Center, New York, NY.

Correspondence and reprints : George Hripcsak, MD, Department of Medical Informatics, Columbia-Presbyterian Medical Center, 161 Fort Washington Avenue, DAP-1310, New York, NY 10032. e-mail : \|[lt ]\|hripcsak{at}columbia.edu\|[gt ]\| .

Abstract An information system architecture defines the components of a system and the interfaces among the components. A good architecture is essential for creating an Integrated Advanced Information Management System (IAIMS) that works as an integrated whole yet is flexible enough to accommodate many users and roles, multiple applications, changing vendors, evolving user needs, and advancing technology. Modularity and layering promote flexibility by reducing the complexity of a system and by restricting the ways in which components may interact. Enterprise-wide mediation promotes integration by providing message routing, support for standards, dictionary-based code translation, a centralized conceptual data schema, business rule implementation, and consistent access to databases. Several IAIMS sites have adopted a client-server architecture, and some have adopted a three-tiered approach, separating user interface functions, application logic, and repositories.




This article has been cited by other articles:


Home page
 J. Am. Med. Inform. Assoc.Home page
C. E. Kuziemsky, J. H. Weber-Jahnke, F. Lau, and G. M. Downing
An Interdisciplinary Computer-based Information Tool for Palliative Severe Pain Management
J. Am. Med. Inform. Assoc., May 1, 2008; 15(3): 374 - 382.
[Abstract] [Full Text] [PDF]

Home page
 J. Am. Med. Inform. Assoc.Home page
S. T. Rosenbloom, A. J. Geissbuhler, W. D. Dupont, D. A. Giuse, D. A. Talbert, W. M. Tierney, W. D. Plummer, W. W. Stead, and R. A. Miller
Effect of CPOE User Interface Design on User-Initiated Access to Educational and Patient Information during Clinical Care
J. Am. Med. Inform. Assoc., July 1, 2005; 12(4): 458 - 473.
[Abstract] [Full Text] [PDF]

Home page
 J. Am. Med. Inform. Assoc.Home page
W. W. Stead, R. A. Miller, M. A. Musen, and W. R. Hersh
Integration and Beyond: Linking Information from Disparate Sources andinto Workflow
J. Am. Med. Inform. Assoc., March 1, 2000; 7(2): 135 - 145.
[Abstract] [Full Text] [PDF]


HOME HELP FEEDBACK SUBSCRIPTIONS ARCHIVE SEARCH TABLE OF CONTENTS
Copyright © 1997 by the American Medical Informatics Association.