Hopes And Constraints Concerning Hospital Information System Dzintars

Hopes And Constraints Concerning Hospital Information System Dzintars Mozgis, Dr. med Chairman, Board, University Hospital for Children, Riga, Latvia Vladimirs Strazdins, MD Head, Nephrology, University Hospital for Children, Riga, Latvia April 7, 2005 Baltic IT&T 2005 Forum 1

Initial Expectations n n Our cultural and historical tradition is neither the best, nor the worst, but it surely determines the reality We expected (and quick) to create the electronic patient management system able to cope with: u Patient registration & scheduling u Electronic medical records u Lab management u Pharmacy management u Medical billing u Long-term care u Medical practice management, etc. April 7, 2005 Baltic IT&T 2005 Forum 2

Harsh Reality n n n We were wrong! Though with big efforts and a long time, but fortunately not investing the big money we have completed only the first step (registration) by now By constantly putting in the extensive personal efforts, time and enthusiasm we currently may probably be in the middle of completion of the next three to four steps u Patient scheduling – on the way u Lab management – on the way u Pharmacy management - on the way u Electronic medical records - slowly developing April 7, 2005 Baltic IT&T 2005 Forum 3

Main IS Principles n n n From the IT point of view the clinical (medical) workstation is an interface between the computer network and medical, patient care, and administrative processes While developing the concept of our hospital IS we decided it should provide our staff with the maximally simple (operated on the intuitive level) easily accessible data base with only basic data processing The user should not even be aware of the database structure, operating system involved, or other technicalities April 7, 2005 Baltic IT&T 2005 Forum 4

Decision-making Policy n n n Evidence-based and cost-effective treatment requires the correct account of the expense involved, and the quality management needs the comprehensive integration of the related information Only then the particular therapeutic or diagnostic issue analysis will become possible, and as a result the proven concepts of therapy, guidelines, and protocols will develop It is essential not to base those end products on the single person’s (doctor’s) opinion like traditionally done in previous years, but to make those solidly based on proven results and teamwork analysis of the quality and other parameters achieved April 7, 2005 Baltic IT&T 2005 Forum 5

Do Not Expect Wonders n It is wrong to expect the hospital IS to raise the productivity by itself n Though both hardware and software costs are dropping, the hospital IS at least initially looks more like a bottomless cavity, where you can dump the investments with actually no limits n The initial phase usually results even in productivity decline due to learning processes, especially for those with low or absent PC user skills, who are usually afraid of using the IT April 7, 2005 Baltic IT&T 2005 Forum 6

Limitations n There are enormous data quantities in medicine n The usual attempt is to collect and to store all available data in all details, and for as long as possible n The above concept is completely wrong, since no technical resources are available to store the data and make those available in a few seconds time n Attempts to develop such a system end up with a mighty expensive data graveyard! u Take your PC and look at what percentage of stored data you really use? April 7, 2005 Baltic IT&T 2005 Forum 7

Priorities n n n Therefore the most difficult and effort-consuming, but the mostly needed task is to define the priorities u Exactly what information and to what extent will certainly be (but not might be) needed in a future The above determined our decision to avoid the most usual mistake to get everything available at once We started to develop our hospital IS step by step, simultaneously learning and training ourselves u Only when one of the system components is ready, implemented, tested in daily routine and is wellaccepted by end-users, we make the next step to start another module April 7, 2005 Baltic IT&T 2005 Forum 8

Hospital IS Requirements n Therefore, we concluded that the main requirements for hospital IS are u Low cost u High stability u High data security level u Minimal possibility of virus threat April 7, 2005 Baltic IT&T 2005 Forum 9

Our Choice n n Hospital description u 600 pediatric beds in 23 specialized clinical departments (wards), supportive medical & nonmedical units Workstations u 40 Linux-based hospital IS workstations u 110 Windows-based hospital general networkstations Servers: 4 firewall-protected (Hospital IS server, General file server, WWW server, and Mail server) Connections: 100 mbps optical cable + 10 mbps UTP + 2 mbps Internet radio link April 7, 2005 Baltic IT&T 2005 Forum 10

Currently Implementing n Direct data input from automated lab analyzers u n Pharmacy database connection to hospital IS u n All lab equipment already changed to automated stations with data output modules Current database is separate and uses a different data format Outpatient clinic IS is under development from scratch u Scheduling, registration, lab data input, medical records, etc. April 7, 2005 Baltic IT&T 2005 Forum 11

Outside Connections n n n The ability to link clinical data systems between institutions is becoming more important as our society continues to develop Local area and distributed networks are the probable means of providing such a linkage Standardization of data format is crucial to facilitate the functionality of networks Considering the possible data exchange with the primary care physicians we are cautious, since the most sophisticated and expensive IS will fail until the relations between those two levels will improve It will take a long and intensive managing and psychological work to achieve the passable relations April 7, 2005 Baltic IT&T 2005 Forum 12