Search PubMed⌕ Search

SEARCH · Search PubMed

Results for “Clinical Laboratory Information Systems”

Search indexed PubMed citations on genomics, clinical trials, systematic reviews and public health. Explore titles, authors and supplied subject terms, then open the PubMed record.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 19 recordsLinked to original sources
PubMed2005

[Research and development of a clinical laboratory information system].

A clinical laboratory information system consists of two parts--the information system and the management system. Its development is based on scientific and rational lab-workflow, consulting the international standard HL7 Protocol, and combined with barcode technique and instrument communication. The information system mainly manages the data which come from the whole lab testing process while the management system is dominating the lab office work and management decisions.

Clinical Laboratory Information Systems↗
PubMed1989

Long-term data storage in a clinical laboratory information system.

The clinical laboratory is pressured on one side by physicians and regulators who want the laboratory to keep more detailed patient records available for longer periods and on the other side by physical space and cost constraints which favor rapidly transferring such records to Medical Records or a warehouse from which retrieval is slow and difficult. Various forms of inactive data storage and archiving in machine-readable form are available to address this dilemma, yet these solutions can create even more difficult problems. Two different approaches were developed within the framework of Relational LABCOM to address both the intermediate and long-term storage of data. In this paper we examine the two methods as solutions to the problems, discuss their limitations, and determine why one is superceding the other in the installation base.

Clinical Laboratory Information Systems↗
PubMed1991

Expert systems and the clinical laboratory information system.

Many of the tasks of the clinical laboratory involve the application of knowledge and experience to patient-specific problems. Expert systems that have ready access to patient data and expert knowledge have the potential to support many laboratory processes, especially those that involve the repetitive and reasonably predictable application of knowledge. Quality assurance and utilization improvement efforts requiring constant vigilance and surveillance of an array of laboratory processes especially may benefit. Expert system technologies, trends of their use in the clinical laboratory, their role in the total testing process, and their potential for influencing physician use of the laboratory through timely feedback are discussed.

Clinical Laboratory Information Systems↗
PubMed1993

A clinical laboratory information systems survey. A challenge for the decade.

In 1990, the College of American Pathologists Informatics Committee surveyed 14,785 laboratorians for their experiences with a clinical laboratory information system. A 16.25% response rate was achieved, representing 2402 questionnaires that were analyzed. Despite the perceived satisfaction of the clinical laboratory information system users with more expensive systems, no economy of scale was demonstrated with increasing system cost through either laboratory staff reduction or increased number of specimens per day. The strongest predictors of system satisfaction were (1) vendor success measured by number of installations and (2) a selection process that involved the pathologist/laboratory director and included a formal request for proposal. The need for integration of clinical laboratory information systems with hospital information systems, as well as the universal adoption of standard productivity terminology, including work load units, was evident.

Clinical Laboratory Information Systems↗
PubMed1996

A new clinical laboratory information system architecture from the OpenLabs project offering advanced services for laboratory staff and users.

The OpenLabs project aims to improve the efficiency and effectiveness of clinical laboratory services by integrating decision support systems with laboratory information systems and equipment. Standards for electronic data interchange between laboratories and other medical systems using the EUCLIDES/OpenLabs coding scheme and an open architecture for clinical laboratory information systems have been specified. This article gives an account of the proposed architecture and outlines new software applications being developed using the architecture which provide advanced services for ordering and reporting of laboratory tests, advanced instrument workstation and laboratory management services, including an OpenLabs Service Manager application which co-ordinates the available services.

Chemistry, Clinical↗
PubMed1988

The development of a third generation system for entering microbiology data into a clinical laboratory information system.

Increased demands on technologists' time and the desire to have electronic storage of patient information have led to numerous computer-based efforts to manage microbiology data. Our approach to the design of a new microbiology subsystem has been to maximize the functionality without requiring unusual input devices. DEC VT100-compatible terminals are used for data entry and display. Data are displayed taking advantage of such features of these terminals as reverse video, highlighting, and scroll windowing. Numerous single-key instructions for invoking functions and changing cursor positions have been implemented to minimize keystrokes and to anticipate the entry sequences of the technologists. A program that allows the quick location and display of specimens and results is also included in the package.

Clinical Laboratory Information Systems↗
PubMedDate not supplied

Regulation of clinical laboratory information systems after the 1990 amendments to the Food and Drug Act.

Clinical laboratories are among the most sophisticated software users in the modern hospital. The 1990 Medical Device Amendments to the Food and Drug Act caused a significant change in the legal regulation of medical software. The Act replaces the earlier emphasis on premarket approvals with postmarket surveillance. Hospitals and other institutional users are now required to report to the Food and Drug Administration (FDA) product defects that cause injuries or death. The Act also provides for civil penalties. The combination of these factors may lead to enhanced FDA supervision of medical software, particularly with unregistered producers. Clinical laboratories must understand both the regulatory system and their own responsibilities under the Act.

Clinical Laboratory Information Systems↗
PubMed1991

Migrating a clinical laboratory information system between technologies.

The technical revolution that has strongly driven events in the clinical laboratory for the last thirty years is now threatening to make obsolete what has become the central pillar of operation in many laboratories, the minicomputer-based laboratory information system. Some of its functions could easily be absorbed by the personal computers which are proliferating in the laboratory, but any single step leap between systems risks replacing order with chaos. Appropriate use of networking tools, together with essential software development, can provide a systematic migrational path for both the administrative and technical computer support from one environment to another without the trauma of a massive replacement step.

Clinical Laboratory Information Systems↗