PubMed Health⌕ Search
Home/Archive/PubMed

PubMed · 10384607

An object-modeling method for hospital information systems.

K Seto·T Kamiyama·H Matsuo
View original source ↗Export metadata ↓

Abstract

Our goal is to increase the software productivity of hospital information systems (HISs) by applying object-oriented technologies. We propose a new object-modeling method for HISs that combines three general methods--an object modeling technique (OMT), class responsibilities collaboration (CRC) cards, and a use-case approach--to extract objects effectively. Our method also takes HIS functionality characteristics such as history and patient-staff linking into consideration to increase the reusability of objects. To test this method, we applied it to several HISs such as a drug-history system, a nursing-support system and an electronic patient record (EPR). We found that the software productivity of the drug-history system was more than doubled by using the combined method. Also, more than 40% of the logic classes could be reused in the nursing-support system and EPR. These findings confirmed that the proposed method can significantly increase the software productivity of HISs.

Explore related subjects

Clinical Pharmacy Information SystemsEvaluation Studies as TopicHospital Information SystemsHumansMedical Records Systems, ComputerizedModels, TheoreticalSoftwareJournal Article

Keep this discovery

Explore connections, maps & timelines

BibTeXRIS

K Seto, T Kamiyama, H Matsuo. 1998. An object-modeling method for hospital information systems.. https://pubmed.ncbi.nlm.nih.gov/10384607/

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

KEEP EXPLORING

Related citations

PubMed2002

Creating a culture of medication administration safety: laying the foundation for computerized provider order entry.

BACKGROUND: Computerized provider order entry (CPOE) systems are recognized as an effective tool for reducing preventable adverse drug events; however, implementation is a complex process that involves much more than installing new software. The literature addresses the use of these systems in large tertiary care hospitals and university settings; yet there is little information on their implementation and use in smaller hospitals. Beaver Dam Community Hospital, a small, rural hospital, set about laying the foundation for implementing CPOE. Actions were taken in terms of context (the culture and attitude, acceptance, and importance regarding the change), process (roles, workflow, and policies relating to the change), and content (how-to, such as procedural steps and rules). USE OF THE RAPID-CYCLE IMPROVEMENT PROCESS: The team elected to use the rapid-cycle improvement process for implementation to allow it to move ahead quickly, adjusting changes as necessary for maximum success. Each change was considered an individual Plan-Do-Check-Act cycle, with its own action plan and measurement for successful implementation. PLANNING ACTUAL IMPLEMENTATION: The Patient Safety Committee has begun the planning of actual implementation--Phase II. Issues addressed include how to phase in the system--in which units to bring up first, how to structure the transitional period, how to redesign workflow, and how to plan role changes. SUMMARY: The changes already implemented contribute to medication safety and are important from that perspective alone, without the use of CPOE. The addition of an electronic system will enhance the organization's ability to provide safe, accurate medication administration.

Clinical Pharmacy Information Systems↗
PubMed2002

Mobile computing acceptance grows as applications evolve.

Handheld devices are becoming more cost-effective to own, and their use in healthcare environments is increasing. Handheld devices currently are being used for e-prescribing, charge capture, and accessing daily schedules and reference tools. Future applications may include education on medications, dictation, order entry, and test-results reporting. Selecting the right handheld device requires careful analysis of current and future applications, as well as vendor expertise. It is important to recognize the technology will continue to evolve over the next three years.

Clinical Pharmacy Information Systems↗