Strategies for problem list implementation in a complex clinical enterprise.

Research output: Contribution to journalArticle

19 Citations (Scopus)

Abstract

Although the Institute of Medicine states that a patient problem list should have a prominent place in the computer-based patient record, the design and function of the problem list is not a matter of universal agreement. Developer experience with implementation has been inconsistent, in part because of confusion on data standards, uncertain user acceptance of data entry, and minimal rewards for the clinician. I propose that necessary features of the problem list include: 1) clinical focus, 2) codification of problems, 3) support for problem resolution, 4) historicity of problems, 5) support for multiple clinical views, 6) integration of maintenance functions with workflow, 7) support for administrative reporting, and 8) integration with useful clinical tools. I describe the strategies that we employed to meet these goals while implementing the problem list in a computerized patient record serving a large, complex clinical enterprise. I further report the successful achievement of those goals based upon audits six months after implementation.

Original languageEnglish (US)
Pages (from-to)285-289
Number of pages5
JournalProceedings / AMIA ... Annual Symposium. AMIA Symposium
StatePublished - Jan 1 1998

Fingerprint

Confusion
National Academies of Science, Engineering, and Medicine (U.S.) Health and Medicine Division
Workflow
Reward
Maintenance

ASJC Scopus subject areas

  • Medicine(all)

Cite this

@article{5c6e621b81f24d3f8969a164ae81a83b,
title = "Strategies for problem list implementation in a complex clinical enterprise.",
abstract = "Although the Institute of Medicine states that a patient problem list should have a prominent place in the computer-based patient record, the design and function of the problem list is not a matter of universal agreement. Developer experience with implementation has been inconsistent, in part because of confusion on data standards, uncertain user acceptance of data entry, and minimal rewards for the clinician. I propose that necessary features of the problem list include: 1) clinical focus, 2) codification of problems, 3) support for problem resolution, 4) historicity of problems, 5) support for multiple clinical views, 6) integration of maintenance functions with workflow, 7) support for administrative reporting, and 8) integration with useful clinical tools. I describe the strategies that we employed to meet these goals while implementing the problem list in a computerized patient record serving a large, complex clinical enterprise. I further report the successful achievement of those goals based upon audits six months after implementation.",
author = "Campbell, {James R}",
year = "1998",
month = "1",
day = "1",
language = "English (US)",
pages = "285--289",
journal = "Proceedings / AMIA . Annual Symposium. AMIA Symposium",
issn = "1531-605X",
publisher = "Hanley & Belfus",

}

TY - JOUR

T1 - Strategies for problem list implementation in a complex clinical enterprise.

AU - Campbell, James R

PY - 1998/1/1

Y1 - 1998/1/1

N2 - Although the Institute of Medicine states that a patient problem list should have a prominent place in the computer-based patient record, the design and function of the problem list is not a matter of universal agreement. Developer experience with implementation has been inconsistent, in part because of confusion on data standards, uncertain user acceptance of data entry, and minimal rewards for the clinician. I propose that necessary features of the problem list include: 1) clinical focus, 2) codification of problems, 3) support for problem resolution, 4) historicity of problems, 5) support for multiple clinical views, 6) integration of maintenance functions with workflow, 7) support for administrative reporting, and 8) integration with useful clinical tools. I describe the strategies that we employed to meet these goals while implementing the problem list in a computerized patient record serving a large, complex clinical enterprise. I further report the successful achievement of those goals based upon audits six months after implementation.

AB - Although the Institute of Medicine states that a patient problem list should have a prominent place in the computer-based patient record, the design and function of the problem list is not a matter of universal agreement. Developer experience with implementation has been inconsistent, in part because of confusion on data standards, uncertain user acceptance of data entry, and minimal rewards for the clinician. I propose that necessary features of the problem list include: 1) clinical focus, 2) codification of problems, 3) support for problem resolution, 4) historicity of problems, 5) support for multiple clinical views, 6) integration of maintenance functions with workflow, 7) support for administrative reporting, and 8) integration with useful clinical tools. I describe the strategies that we employed to meet these goals while implementing the problem list in a computerized patient record serving a large, complex clinical enterprise. I further report the successful achievement of those goals based upon audits six months after implementation.

UR - http://www.scopus.com/inward/record.url?scp=0032246487&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=0032246487&partnerID=8YFLogxK

M3 - Article

SP - 285

EP - 289

JO - Proceedings / AMIA . Annual Symposium. AMIA Symposium

JF - Proceedings / AMIA . Annual Symposium. AMIA Symposium

SN - 1531-605X

ER -