PubMed Health⌕ Search
Home/Archive/PubMed

PubMed · 2628530

A generalized laboratory software package--a prototype approach.

B Lazinger
View original source ↗Export metadata ↓

Abstract

A prototyped model of a generalized table-driven software package for laboratory testing and results registration is presented. The need to computerize dozens of laboratories performing hundreds of tests, called for a radical approach which would enable the quick addition of new laboratories to the system, as well as ease of maintenance. The generalized laboratory software package (GLAB) relies on a set of data tables, maintained by users, and a menu controlled environment interfacing GLAB with the rest of the hospital's systems.

Explore related subjects

Clinical Laboratory Information SystemsClinical Laboratory TechniquesDatabase Management SystemsHospitalsHumansInformation SystemsIsraelSoftwareJournal Article

Keep this discovery

Explore connections, maps & timelines

BibTeXRIS

B Lazinger. 1989. A generalized laboratory software package--a prototype approach.. https://doi.org/10.1007/bf00996459

Cite the original work for its findings. Save a collection to share your selection of sources.

KEEP EXPLORING

Related citations

PubMed1992

An analysis of the relationship between a pathology department and its laboratory information system vendor.

The ongoing collaborative relationship between a pathology department and the vendor of its laboratory information system is vitally important because of the strategic importance of the laboratory information system in managing the information product of the department. Laboratory information system vendors are value-added resellers in that they produce software and package it with hardware manufactured by another manufacturer. The success of laboratory information system value-added resellers in creating information systems that are highly functional depends on their forward vertical quasi-integration into pathology departments. Because of this relationship, laboratory information system value-added resellers exert a significant degree of control over departments, largely through the creation of switching costs. There are a number of strategies by which departments can exercise greater control over vendors, one of which is to serve as either an alpha- or beta-development site for the vendor's software. Such a strategy is not without risk, but it achieves the dual purpose of enhancing both the expertise of departmental personnel and the quality of the software product.

Clinical Laboratory Information Systems↗
PubMed1992

Computerised protocols for laboratory investigation and their effect on use of medical time and resources.

AIMS: To devise a computerised management system protocol which not only proposes the laboratory investigations to be performed on each patient but also performs related clinical functions. METHODS: The system was designed by senior members of staff. The protocols defined all laboratory investigations including haematology, biochemistry, immunology and cross-matching, and included static and dynamic rules. Patients can be changed to different or additional protocols, as required; likewise proposed tests can be deleted or added. The software is written in MUMPS and runs on a 386 PC running MSM MUMPS under MSDOS. RESULTS: The number of clinical chemistry tests requested per patient per day fell by 9.5% (p less than 0.01) for transplant recipients and by 28.8% (p less than 0.01) for non-transplant recipients. The average time spent by junior medical staff requesting laboratory investigations and enquiring about results fell from 10 minutes per patient per day to 4.1 minutes (p less than 0.001). CONCLUSIONS: The introduction of this system in no way abrogates clinicians' responsibility for the management of patients, because all proposed investigations must be confirmed or modified by the authorising doctor. The system allows for the audit of requesting patterns and subsequent improvement in protocols by recording any alterations made to the proposed investigations. Significant benefits in terms of better use of house officer time and medical resources were also achieved.

Clinical Laboratory Information Systems↗
PubMed1992

Implementing a regulation-complaint quality improvement program on a commercial laboratory information system.

Implementing a quality improvement (QI) program on an automated laboratory information system (LIS) in the current regulatory climate requires first that the QI program be defined and second that the selected LIS be able to capture important events and use flexible vendor-provided or user-defined routines to prepare reports. Reports key on specific monitors and thresholds defined in the QI program. The product of a pathology laboratory is communicated information. The QI program focuses on the accuracy, clarity and timeliness with which the whole information-generating process functions. To support peer review the LIS must be able to select reports for evaluation based on user-defined parameters, such as diagnosis keyed through Systematized Nomenclature of Medicine codes, or by random or pattern selection by accession number. Counting and review of revised reports will focus attention on accuracy and skill in communication since these indicators often reflect client satisfaction with the report. To link services--e.g., cytology with surgical pathology--the LIS must be able to gather cases from the accession lists of both services and to flag diagnostic inconsistencies. LIS transaction logging at every step in the information process allows tracking of work load, productivity and resource utilization by functional areas and by individual, thus meeting regulatory requirements. Transaction logging also provides management information, such as segmented turnaround time audits, pinpointing sources of delay by kind and location of work or individual involved. Critical data must be held on-line for at least five years.

Clinical Laboratory Information Systems↗