PubMed Health⌕ Search

PubMed · 10124535

Ways to avoid snafus while implementing a laboratory information system.

Abstract

If you are about to embark on a new or replacement LIS, your consideration of the following suggestions will help deflect problems common to LIS implementations. These suggestions have evolved over my 10 years of experience as a consultant working with laboratory information systems, and 20 years of general experience with clinical and reference laboratories. Consider these suggestions, use them, and avoid snafus.

Explore related subjects

Keep this discovery

Explore connections, maps & timelines

BibTeXRIS

J H Hengesbaugh. 1993. Ways to avoid snafus while implementing a laboratory information system.. https://pubmed.ncbi.nlm.nih.gov/10124535/

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

KEEP EXPLORING

Related citations

Management of severe hypokalemia in hospitalized patients: a study of quality of care based on computerized databases.

BACKGROUND: While administrative databases are used to assess general indicators of quality of care, a detailed audit of the process of clinical care usually requires review of hospital medical records. OBJECTIVE: To evaluate the feasibility of assessing the management of severe hypokalemia using computerized administrative and laboratory databases. METHODS: The study included all patients hospitalized in 1997 who experienced serum potassium levels of less than 3.0 mmol/L at Hadassah University Hospital, Jerusalem, Israel, a tertiary care center. Using the computerized databases, we measured the following: (1) whether a subsequent serum potassium test was performed, (2) time to the subsequent test and to normalization of the serum potassium level, (3) achievement of normokalemia, and (4) in-hospital mortality. In a random subsample of 100 patients, these measures were compared with the blinded assessment of the quality of medical management of hypokalemia, as determined from medical records, using predetermined criteria for adequate management. RESULTS: The computerized databases revealed that severe hypokalemia occurred in 866 patients (2.6% of the yearly hospitalizations): 55 patients (6.4%) had no subsequent serum potassium levels measured, and 260 (30.0%) were discharged from the hospital with a subnormal potassium level. The mean time to a subsequent test was 20 hours, and to normokalemia, 50 hours; both intervals varied by department. In-hospital mortality was 20.4%, or 10-fold that of the entire hospitalized population. A review of hospital medical records revealed inadequate clinical management of hypokalemia in 24%, which was associated with nonperformance of a subsequent test (likelihood ratio, 8.4), failure to normalize the serum potassium level (likelihood ratio, 4.2), discharge from the hospital with a subnormal potassium level (likelihood ratio, 2.1), and in-hospital death (likelihood ratio, 2.5), all of which could be determined by the computerized databases. CONCLUSIONS: The computerized laboratory database is useful in ascertaining the prevalence of severe hypokalemia and in assessing shortcomings in its management. Databases can be used to derive valid and efficient measures of the quality of the clinical management of electrolyte disorders.

Clinical Laboratory Information Systems↗

An integrated system for high throughput TaqMan based SNP genotyping.

UNLABELLED: We have developed an integrated laboratory information system that allows the flexible handling of pedigree, phenotype and genotype information. Specifically, it includes client applications for an integrated data import from TaqMan typing files, Mendel checking, data export, handling of pedigree and phenotype information and analysis features. AVAILABILITY: The SQL source code, sources and binaries of the client applications (NT and Windows95/98 platforms) and additional documentation are available at http://www.mucosa.de/.

Clinical Laboratory Information Systems↗