Search PubMed⌕ Search

Biomedical subjects

J M Teich

Publications and source records attributed to J M Teich.

At least 37 records · Page 2Linked to original sources
PubMed1998

Components of the optimal ambulatory care computing environment.

We present here a framework of core components of an ambulatory care computing environment, based on clinical and functional needs and workflow scenarios. We have established this framework through the use of two study devices: a vision of the clinical office of the future, and a survey of possible computer applications, both designed to help clinicians and practice directors communicate their information needs to systems designers. Clinicians prioritize applications based on strategic and practice goals: support for clinical users' workflow, improved quality of care, reduced cost of care, and the ability to measure performance and status. By reorganizing the needed functionality from a clinical viewpoint into a technical viewpoint, we are able to identify core information components for systems design. Based on this analysis, information needs in the ambulatory environment can be divided into five primary functions: patient data retrieval, documentation, communication, knowledge resources, and aggregate reporting. Three other fundamental processes--knowledge-based interventions, information integration, and confidentiality--run through all of these front-line functions. Component applications and data structures built with this framework in mind will afford a maximum combination of functionality and flexibility to handle future changes in the clinical environment.

Ambulatory Care↗
PubMed1998

Clinical information systems for integrated healthcare networks.

In the 1990's, a large number of hospitals and medical practices have merged to form integrated healthcare networks (IHN's). The nature of an IHN creates new demands for information management, and also imposes new constraints on information systems for the network. Important tradeoffs must be made between homogeneity and flexibility, central and distributed governance, and access and confidentiality. This paper describes key components of clinical information systems for IHN's, and examines important design decisions that affect the value of such systems.

Computer Communication Networks↗
PubMed1998

A software architecture to support a large-scale, multi-tier clinical information system.

A robust software architecture is necessary to support a large-scale multi-tier clinical information system. This paper describes our mechanism for enterprise distribution of applications and support files, the consolidation of data-access functions and system utilities stored on the data access tier, and an application framework which implements a coherent clinical computing environment. The software architecture and systems described in this paper have been robust through pilot testing of our applications at Massachusetts General Hospital.

Computer Security↗
PubMed1998

Modifiable templates facilitate customization of physician order entry.

Physician order entry is a key factor in improving the quality of healthcare, while simultaneously reducing its cost. This paper describes an editor, a database, and a run-time system for creating and executing highly customized, user modifiable, order entry templates. The system allows non-programmers to create new order entry templates rapidly. Over the past 18 months, the templates have been used on over 2500 patients to enter over 40,000 separate orders.

Database Management Systems↗
PubMed1998

P-CAPE: a high-level tool for entering and processing clinical practice guidelines. Partners Computerized Algorithm and Editor.

The Partners Computerized Algorithm Processor and Editor (P-CAPE) is a high-level tool intended to remove the programming bottleneck for implementing practice guidelines in our computer-based record system, and to integrate guideline-based advice into the clinician's workflow. P-CAPE has three major components: 1) An Editor that allows an analyst to enter the parameters of a guideline in the form of an algorithm; 2) A Navigator that processes the steps of the guideline and logs all transactions in a patient-specific file; and 3) A clinician Notifier that sends messages to a patient's covering clinician, seeking data or presenting recommendations and order sets that can be processed by the system. P-CAPE's guideline object model was adapted from the InterMed Collaboratory GuideLine Interface Format (GLIF).

Algorithms↗
PubMed1998

A graphical user interaction model for integrating complex clinical applications: a pilot study.

We have developed and implemented a multi-faceted, graphical user interaction model for an advanced clinical information system. This paper describes a classification scheme for applications used by clinicians in their daily work, discusses the way clinicians interact with these applications, and the issues that arise during these user interactions. Through its emphasis on support for application interoperation, the graphical user interface that implements the model presents a single, consistent, context to the user, and thereby helps maintain patient safety and ensure ease of use.

Computer Graphics↗
PubMed1997

A critical pathway for management of patients with acute chest pain who are at low risk for myocardial ischemia: recommendations and potential impact.

BACKGROUND: Use of resources for patients with acute chest pain may be improved with clinical strategies that integrate research, Bayesian analysis, and expert opinion. OBJECTIVES: To 1) develop a critical pathway for management of patients with acute chest pain who are at low risk for complications of ischemic heart disease and 2) assess the potential effects of implementation of the pathway on patient safety and resource use. DESIGN: Evidence-based consensus and prospective cohort study. SETTING: Urban teaching hospital. PATIENTS: Patients at least 30 years of age who were seen in the emergency department for chest pain and who did not have a history of trauma or abnormalities on radiologic study. INTERVENTION: Physician-opinion leaders defined criteria for patient inclusion in the pathway and for remaining on the pathway after 6 or 12 hours of observation. Criteria were defined for appropriateness of direct admission, direct discharge, or 6 hours of observation followed by exercise treadmill testing. MEASUREMENTS: Number of patients admitted to the hospital, number of days that patients were hospitalized, and clinical outcome. RESULTS: 2898 of 4585 patients (63%) were admitted to the hospital; of the 2898, 1152 (40%) were classified as potentially eligible for the pathway and 1068 (93%) had a benign clinical course during the initial observation period. The 1068 patients had a mean length of stay of 2.8 +/- 4.8 days. If 47% of these patients had been discharged after observation and exercise testing, implementation of the pathway would have reduced the number of admissions by 505 (17%) and days of hospitalization by 1407 (11%). CONCLUSIONS: Retrospective analysis suggests that a critical pathway for patients with acute chest pain may substantially reduce resource use. Prospective study is needed to ensure increased efficiency without increased adverse outcomes.

Acute Disease↗
PubMed1997

Does the computerized display of charges affect inpatient ancillary test utilization?

BACKGROUND: The computerized display of charges for ancillary tests in outpatients has been found to affect physician-ordering behavior, but this issue has not been studied in inpatients. OBJECTIVE: To assess whether the computerized display of charges for clinical laboratory or radiological tests affected physician-ordering behavior. PATIENTS AND METHODS: Two prospective controlled trials, randomized by patient, were performed. Each trial included all medical and surgical inpatients at 1 large teaching hospital during 4 and 7 months: 3536 intervention and 3554 control inpatients in the group with clinical laboratory tests, and 8728 intervention and 8653 control inpatients in the group with radiological tests. The intervention consisted of the computerized display of charges for tests at the time of ordering. MAIN OUTCOME MEASURES: The number of clinical laboratory and radiological tests ordered per admission and the charges for these tests. RESULTS: For the clinical laboratory tests, during a 4-month study period, patients in the intervention group had 4.5% fewer tests ordered, and the total charges for these tests were 4.2% lower, although neither difference was statistically significant. Compared with historical controls from the same 4-month period a year before, the charges for the tests per admission had decreased 13.3%, but the decrease was temporally correlated with a restriction of future ordering of tests, and not with the introduction of the display of charges. For the radiological tests, during a 7-month period, the intervention group had almost identical numbers of tests ordered and charges for these tests. CONCLUSIONS: The computerized display of charges had no statistically significant effect on the number of clinical laboratory tests or radiological procedures ordered or performed, although small trends were present for clinical laboratory tests. More intensive interventions may be needed to affect physician test utilization.

Computer Systems↗
PubMed1997

Advanced alerting features: displaying new relevant data and retracting alerts.

We added two advanced features to our automated alerting system. The first feature identifies and displays, at the time an alert is reviewed, relevant data filed between the login time of a specimen leading to an alerting result and the time the alert is reviewed. Relevant data is defined as data of the same kind as generated the alert. The other feature retracts alerts when the alerting value is edited and no longer satisfies the alerting criteria. We evaluated the two features for a 14-week period (new relevant data) and a 6-week period (retraction). Of a total of 1104 alerts in the 14-week evaluation, 286 (25.9%) had new relevant data displayed at alert review time. Of the 286, 75.2% were due to additions of comments to the original piece of alerting data; 24.1% were due to new or pending laboratory results of the same type that generated the alert. Two alerts (out of 490) were retracted in a 6 week period. We conclude that in our system, new clinically relevant data is often added between the time of specimen login and the time that an alerting result from that specimen is reviewed. Retractions occur rarely but are important to detect and communicate.

Data Display↗
PubMed1997

Preserving context in a multi-tasking clinical environment: a pilot implementation.

The Partners Clinical Application Suite (CAS) is a multi-tasking software architecture that facilitates the development, deployment, and use of advanced clinical information management applications. This paper describes 1) a software shell in which clinical applications run; 2) an application programming interface (API); and 3) development of a set of "Look & Feel" guidelines. Through its emphasis on support for multi-tasking and application interoperability, CAS facilitates preservation of the user's context.

Hospital Information Systems↗
PubMed1996

An information system to improve the safety and efficiency of chemotherapy ordering.

We developed a computer application to support the ordering of chemotherapy. Key goals were to guard against errors in chemotherapy ordering and dosing, to, coordinate the outpatient and inpatient chemotherapy services, and to support the overall process flow of a chemotherapy cycle. In a six-month period, 512 daily-dose and 386 weekly-dose warnings were generated; 167 (19%) resulted in a cancellation or re-evaluation of the dose. The system has been well accepted, and has helped to coordinate the efforts of the many members of the oncology care team.

Antineoplastic Agents↗
PubMed1996

WWW-based interfaces to clinical information systems: the state of the art.

Nine WWW-based interfaces to clinical information systems were reviewed. Five have progressed past the proof of concept phase and into alpha testing in the clinical environment. All key features desirable in an advanced clinical information were present in at least one interface, however many implementations were rudimentary. Much human computer interface research and WWW tool development needs to occur before implementation of a WWW-based interface to a clinical information system should be considered for a mission-critical, production environment.

Computer Communication Networks↗
PubMed1996

A comprehensive inpatient discharge system.

Our group has developed a computer system that supports all phases of the inpatient discharge process. The system fills in most of the physician's discharge order form and the nurse's discharge abstract, using information available from sign-out, order entry, scheduling, and other databases. It supplies information for referrals to outside institutions, and provides a variety of instruction materials for patients. Discharge forms can be completed in advance, so that the patient is not waiting for final paperwork. Physicians and nurses can work on their components independently, rather than in series. Response to the system has been very favorable.

Continuity of Patient Care↗
PubMed1996

Detecting alerts, notifying the physician, and offering action items: a comprehensive alerting system.

We developed and evaluated a system to automatically identify serious clinical conditions in inpatients. The system notifies the patient's covering physician via his pager that an alert is present and offers potential therapies for the patient's condition (action items) at the time he views the alert information. Over a 6 month period, physicians responded to 1214 (70.2%) of 1730 alerts for which they were paged; they responded to 1002 (82.5% of the 1214) in less than 15 minutes. They said they would take action in 71.5% of the alerts, and they placed an order directly from the alert display screen in 39.4%. Further study is needed to determine if this alerting system improves processes or outcomes of care.

Attitude to Computers↗
PubMed1995

Representing hospital events as complex conditionals.

We have developed an approach to medical knowledge representation whereby simple medical concepts are combined to yield complex statements of testable medical logic. The logic is created from a small number of generic medical concepts that are instantiated and combined to create the rules. Rule writing is done through a rule editor and requires knowledge of the system's data dictionaries, though no programming is required. We have used the approach to create a large knowledge base including panic lab alerting rules, drug-laboratory interaction alerting rules, an adverse drug event monitor, and a drug-age interaction detection program. The rules have been used as part of an alerting system and for data collection to determine the frequency of events of interest. The scheme is extensible and yields a readable form of the created knowledge. The scheme holds great promise as a durable form of medical knowledge representation.

Artificial Intelligence↗