help button home button JAMIA Bigger figures
HOME HELP FEEDBACK SUBSCRIPTIONS ARCHIVE SEARCH TABLE OF CONTENTS

This Article
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 Zielstorff, R. D.
Right arrow Search for Related Content
PubMed
Right arrow PubMed Citation
Right arrow Articles by Zielstorff, R. D.

Journal of the American Medical Informatics Association, Vol 2, 191-196, Copyright © 1995 by American Medical Informatics Association


ARTICLES

Capturing and using clinical outcome data: implications for information systems design

RD Zielstorff
Department of Nursing, Massachusetts General Hospital, Boston 02114, USA.

There is an urgent need to capture and record data related to clinical outcomes, but there are many barriers. The range of problems includes lack of agreement on conceptualization of the term "outcome," inadequate measures of outcomes, and inadequate information systems to capture and manipulate data that would reflect outcomes. This article focuses on information system requirements to capture, store, and utilize clinical outcome data. For greatest accuracy, outcome data should be captured as close to the source as possible, including direct data capture from patients themselves and from their families. To make maximum use of outcome data, systems must be designed to 1) store data in multipurpose databases; 2) share data across different platforms; 3) link outcome data to other data that might influence or explain outcomes; 4) allow querying of the data by authorized personnel; and 5) protect patient confidentiality.


This article has been cited by other articles:


Home page
The Diabetes EducatorHome page
M. Peeples, D. Tomky, K. Mulcahy, M. Peyrot, L. Siminerio, and on behalf of AADE Outcomes Project and AADE/UMPC D
Evolution of the American Association of Diabetes Educators' Diabetes Education Outcomes Project
The Diabetes Educator, September 1, 2007; 33(5): 794 - 817.
[Abstract] [Full Text] [PDF]


Home page
J. Am. Med. Inform. Assoc.Home page
J. C. Niland, L. Rouse, and D. C. Stahl
An Informatics Blueprint for Healthcare Quality Information Systems
J. Am. Med. Inform. Assoc., July 1, 2006; 13(4): 402 - 417.
[Abstract] [Full Text] [PDF]


Home page
The Diabetes EducatorHome page
M. Peeples, K. Mulcahy, D. Tomky, and T. Weaver
The Conceptual Framework of the National Diabetes Education Outcomes System (NDEOS)
The Diabetes Educator, July 1, 2001; 27(4): 547 - 562.
[Abstract] [PDF]


Home page
J. Am. Med. Inform. Assoc.Home page
C. A. Gassert
The Challenge of Meeting Patients' Needs with a National Nursing Informatics Agenda
J. Am. Med. Inform. Assoc., May 1, 1998; 5(3): 263 - 268.
[Abstract] [Full Text]




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