Hawaii - Systemic IT Failure - Decision Makers Hog-Tied
•
0 likes•38 views
It's bad now, and it's going to get worse in the very near future. There is still a window of opportunity to tamp it down, but that window is closing. We really have to act now. - Thomas Frieden
![INFORMATION AND COMMUNICATIONS SYSTEMS
INFORMATION AND COMMUNICATIONS SYSTEMS
THE BACKBONE OF THE HEALTH CARE DELIVERY SYSTEM
THE BACKBONE OF THE HEALTH CARE DELIVERY SYSTEM
BUILDING A BETTER DELIVERY SYSTEM
BUILDING A BETTER DELIVERY SYSTEM
National Center for Biotechnology Information (NCBI)
National Center for Biotechnology Information (NCBI)
U.S. National Library of Medicine
U.S. National Library of Medicine
<https://www.ncbi.nlm.nih.gov/books/NBK22862/>
[Extract]
SOFTWARE DEPENDABILITY
In systems in which software is an element in the critical path, a variety of serious problems
have plagued organizations, including lack of dependability and/or usability, the high cost of
system failure, high maintenance requirements, and difficulties in updating systems. Because
software-intensive systems perform valuable functions, the consequences of failure are
generally serious. For example, developers may assemble modules, each apparently
dependable, but, when they are integrated, problems and weaknesses emerge. Usability
failures are also an issue. For example, if there are too many steps in a program for a user to
follow or if a program is too complicated, various “work arounds” will be developed, and
patient safety or some other critical parameter may be compromised.
In some cases, the initial software-intensive system may be dependable, but changes in
use over time may lead to changes in the software that lead, in turn, to unnoticed side
effects that can introduce weaknesses in the system. Another type of failure can occur when
cost overruns in the development process prevent the project from ever reaching the
commercialization stage. In some instances, noncritical software that interacts directly or
indirectly with critical functions introduces failures and weaknesses (NRC, 2004; Rae et al.,
2003). As these and other forms of software-system failure show, investments in clinical
information systems must be complemented by investments in research on software
dependability.
_______________________________________________________________________](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
More Related Content
Similar to Hawaii - Systemic IT Failure - Decision Makers Hog-Tied
Similar to Hawaii - Systemic IT Failure - Decision Makers Hog-Tied (20)
More from Clifton M. Hasegawa & Associates, LLC
More from Clifton M. Hasegawa & Associates, LLC (20)
Recently uploaded
Recently uploaded (20)
Hawaii - Systemic IT Failure - Decision Makers Hog-Tied
- 1. NEUTRAL ZONE A volume of space not claimed by any political power Created as bufer zones and borders _______________________________________________________________________ CASE IN POINT 455 cases...only 4210 tests...AND this is only a PARTIAL count due to ANOTHER failure in DOH's reporting system. 13 additional deaths reported today We are being led down an unsustainable & devastating path to catastrophe that is completely avoidable. HOPE and INACTION are NOT effective STRATEGIES #hawaiicovid19 #ActNow George White – Politics in Hawaii – Facebook, September 1, 2021 <https://www.facebook.com/georgeorrwhite>
- 2. INFORMATION AND COMMUNICATIONS SYSTEMS INFORMATION AND COMMUNICATIONS SYSTEMS THE BACKBONE OF THE HEALTH CARE DELIVERY SYSTEM THE BACKBONE OF THE HEALTH CARE DELIVERY SYSTEM BUILDING A BETTER DELIVERY SYSTEM BUILDING A BETTER DELIVERY SYSTEM National Center for Biotechnology Information (NCBI) National Center for Biotechnology Information (NCBI) U.S. National Library of Medicine U.S. National Library of Medicine <https://www.ncbi.nlm.nih.gov/books/NBK22862/> [Extract] SOFTWARE DEPENDABILITY In systems in which software is an element in the critical path, a variety of serious problems have plagued organizations, including lack of dependability and/or usability, the high cost of system failure, high maintenance requirements, and difficulties in updating systems. Because software-intensive systems perform valuable functions, the consequences of failure are generally serious. For example, developers may assemble modules, each apparently dependable, but, when they are integrated, problems and weaknesses emerge. Usability failures are also an issue. For example, if there are too many steps in a program for a user to follow or if a program is too complicated, various “work arounds” will be developed, and patient safety or some other critical parameter may be compromised. In some cases, the initial software-intensive system may be dependable, but changes in use over time may lead to changes in the software that lead, in turn, to unnoticed side effects that can introduce weaknesses in the system. Another type of failure can occur when cost overruns in the development process prevent the project from ever reaching the commercialization stage. In some instances, noncritical software that interacts directly or indirectly with critical functions introduces failures and weaknesses (NRC, 2004; Rae et al., 2003). As these and other forms of software-system failure show, investments in clinical information systems must be complemented by investments in research on software dependability. _______________________________________________________________________