Dependable Systems For Quality Care

Slides:



Advertisements
Similar presentations
HIPAA Security Presentation to The American Hospital Association Dianne Faup Office of HIPAA Standards November 5, 2003.
Advertisements

Enterprise Architectures
Basic Law Criminal Law Civil Law. Criminal Law  Protects the public from harmful acts.
Information Risk Management Key Component for HIPAA Security Compliance Ann Geyer Tunitas Group
HIPAA: FEDERAL REGULATIONS REGARDING PATIENT SECURITY.
CAMP Med Building a Health Information Infrastructure to Support HIPAA Rick Konopacki, MSBME HIPAA Security Coordinator University of Wisconsin-Madison.
SL21 Information Security Board Mission, Goals and Guiding Principles.
ICS 417: The ethics of ICT 4.2 The Ethics of Information and Communication Technologies (ICT) in Business by Simon Rogerson IMIS Journal May 1998.
Workshop on High Confidence Medical Device Software and Systems (HCMDSS) Research & Roadmap June 2-3, 2005 Philadelphia, PA. Manufacturer/Care-Giver Perspective.
Smart Grid - Cyber Security Small Rural Electric George Gamble Black & Veatch
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 30 Slide 1 Security Engineering.
McGraw-Hill/Irwin © 2008 The McGraw-Hill Companies, All Rights Reserved Business Plug-In B4 Enterprise Architecture.
Computer Security: Principles and Practice
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 30 Slide 1 Security Engineering.
Introduction to Systems Analysis and Design
Software Dependability CIS 376 Bruce R. Maxim UM-Dearborn.
Resiliency Rules: 7 Steps for Critical Infrastructure Protection.
Information Security Compliance System Owner Training Richard Gadsden Information Security Office Office of the CIO – Information Services Sharon Knowles.
© 2001 Carnegie Mellon University S8A-1 OCTAVE SM Process 8 Develop Protection Strategy Workshop A: Protection Strategy Development Software Engineering.
Copyright ©2011 by Pearson Education, Inc. Upper Saddle River, New Jersey All rights reserved. Health Information Technology and Management Richard.
PATCH MANAGEMENT: Issues and Practical Solutions Presented by: ISSA Vancouver Chapter March 4, 2004.
Security Professional Services. Security Assessments Vulnerability Assessment IT Security Assessment Firewall Migration Custom Professional Security Services.
Important acronyms AO = authorizing official ISO = information system owner CA = certification agent.
1 Availability Policy (slides from Clement Chen and Craig Lewis)
HIT Standards Committee Privacy and Security Workgroup: Initial Reactions Dixie Baker, SAIC Steven Findlay, Consumers Union June 23, 2009.
ISO17799 Maturity. Confidentiality Confidentiality relates to the protection of sensitive data from unauthorized use and distribution. Examples include:
April 14, A Watershed Date in HIPAA Privacy Compliance: Where Should You Be in HIPAA Security Compliance and How to Get There… John Parmigiani National.
Unit 6b System Security Procedures and Standards Component 8 Installation and Maintenance of Health IT Systems This material was developed by Duke University,
Copyright © 2009 by The McGraw-Hill Companies, Inc. All Rights Reserved. McGraw-Hill Chapter 6 The Privacy and Security of Electronic Health Information.
Eliza de Guzman HTM 520 Health Information Exchange.
Strategically Managing the HRM Function McGraw-Hill/Irwin ©2012 The McGraw-Hill Companies, All Rights Reserved.
Urban Infrastructure and Its Protection Responding to the Unexpected Interest Group Report Group Members G. Giuliano (USC), Jose Holguin-Veras (CUNY),
Working with HIT Systems
Copyright © 2016 Wolters Kluwer Health | Lippincott Williams & Wilkins Chapter 18: Design Considerations for Healthcare Information Systems Chapter 18:
Converting Policy to Reality Designing an IT Security Program for Your Campus 2 nd Annual Conference on Technology and Standards May 3, 2005 Jacqueline.
Chapter 15 : Dependable Systems for Quality care.
The IT Vendor: HIPAA Security Savior for Smaller Health Plans?
Electronic Health Record systems: U.S. Federal initiatives and Public/ private partnerships.
Public Trust in Health Information: Foundational Principles for Dependable Systems Dixie B. Baker, Ph.D. Vice President for Technology CTO, Enterprise.
 BEFORE Inefficient Costly Manually intensive Crisis-driven model of care delivery  AFTER Efficient Consumer-centric Science-based model  Changes brought.
Slide 1 Security Engineering. Slide 2 Objectives l To introduce issues that must be considered in the specification and design of secure software l To.
© Plan Plan’s Security Framework – A Refresher. © Plan Understanding Ourselves Values - Child Rights, Impartial, Neutral, Sensitive Mandate - Child Centred,
Working with HIT Systems Unit 7a Protecting Privacy, Security, and Confidentiality in HIT Systems This material was developed by Johns Hopkins University,
IS3220 Information Technology Infrastructure Security
Sicherheitsaspekte beim Betrieb von IT-Systemen Christian Leichtfried, BDE Smart Energy IBM Austria December 2011.
Information Security Office: Function, Alignment in the Organization, Goals, and Objectives Presentation to Sacramento PMO March 2011 Kevin Dickey.
Management Information System In Healthcare
 To explain the relationship between dependability and health care quality and safety.  To identify and explain five guidelines for dependability.
Important acronyms AO = authorizing official ISO = information system owner CA = certification agent.
Information Security Crisis Management Daryl Goodwin.
© 2016 Cengage Learning ®. All Rights Reserved. May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part.
Contingency Management Indiana University of Pennsylvania John P. Draganosky.
Lecturer: Eng. Mohamed Adam Isak PH.D Researcher in CS M.Sc. and B.Sc. of Information Technology Engineering, Lecturer in University of Somalia and Mogadishu.
Clinical Decision Support Implementation Victoria Ferguson, COO - Program Manager Christopher Taylor, CIO – Business Owner Monica Kaileh, CMIO – Steering.
Welcome to the ICT Department Unit 3_5 Security Policies.
Computer Security: Principles and Practice First Edition by William Stallings and Lawrie Brown Lecture slides by Lawrie Brown Chapter 17 – IT Security.
Dr. Gerry Firmansyah CID Business Continuity and Disaster Recovery Planning for IT (W-XIV)
Risks and Hazards to Consider Unit 3. Visual 3.1 Unit 3 Overview This unit describes:  The importance of identifying and analyzing possible hazards that.
Information Systems Security
Chapter 6: Securing the Cloud
Risk management.
MOBILE NETWORKS DISASTER RECOVERY USING SDN-NFV
Mary Alexander, MA, RN, CRNI®, CAE, FAAN Chief Executive Officer
Enterprise Architecture
Security Engineering.
Disaster Response – A Collaboration
Chapter 16 Nursing Informatics: Improving Workflow and Meaningful Use
HSA 520Competitive Success/snaptutorial.com
HSA 520 Education for Service-- snaptutorial.com
Presentation transcript:

Dependable Systems For Quality Care CHAPTER 15 Dependable Systems For Quality Care

OBJECTIVES: 1. To explain the relationship between dependability and health care quality. 2. To identify and explain five guidelines for building dependable systems. 3. To present an informal assessment of the healthcare industry with respect to these guidelines.

INTRODUCTION: The healthcare industry is undergoing a dramatic transformation . This transformation is driven by several factors: Skyrocketing cost of healthcare delivery Exposure of patient safety problems Aging “baby-boom” population

SOME TECHNOLOGIES IMPORTANT IN TRANSFORMING CARE DELIVERY: EHR Electronic, outcomes based decision support Wireless communication Tablet PCs, Personal Data Assistants Continuous Speech Recognition Clinical Knowledge bases CPOE Electronic Prescribing RFID tagging Enterprise Application Integration (EAI) Robotics

The International Council Of Nurses (ICN) Code of Ethics for Nurses affirms that the nurse “holds in confidence personal information” and “ensures that the use of technology is compatible with safety, dignity and rights of the people”. As IT assumes a greater role in healthcare decision making and in the provision of care, the nurse must rely on IT to help protect the patients information and safety.

System Reliability Service availability Confidentiality Data integrity DEPENDABILITY- measure of the extent o which a system can justifiably be relied on to deliver the services expected from it. It comprises the ff. six attributes: System Reliability Service availability Confidentiality Data integrity Responsiveness Safety

WHEN THINGS GO WRONG

WHEN THINGS GO WRONG: February 2003, issue of CIO - “one of the worst healthcare IT crisis in the history”. Catastrophic failure in the network infrastructure that supported CareGroup, one of the most prestigious healthcare organization in the US which resulted in the 4 hr closure of the emergency room, complete shutdown of network and network services were not fully recovered until 6 days of the onset of the disaster.

August 200, the Blaster and SoBig worm attacks invaded hospitals around the world. The bottom line is that systems, networks and software applications are highly complex, and the only safe assumption is that failures will occur. Thus, dependability is an essential factor in planning and operations. WHEN THINGS GO WRONG

GUIDELINES FOR DEPENDABLE SYSTEMS

GUIDELINES FOR DEPENDABLE SYSTEMS All computers are vulnerable to both human created threats (malicious code attacks and software bugs) and natural threats (hardware aging and earthquakes). Tolerant Systems- more practical approach to attaining dependability. It is a system that anticipate problems, detect faults, software glitches, and intrusions.

5 fundamental guidelines that can increase dependability of the healthcare systems: GUIDELINE 1: ARCHITECT FOR DEPENDABILITY A fundamental principle of system architecture is that an enterprise system architecture should be developed from bottom up so that no critical component is dependent on a component less trustworthy than itself. The simplest the design and integration strategy will be the easiest to understand, to maintain, and to recover in case of failure or disaster.

GUIDELINE 2: ANTICIPATE FAILURES Minimizing complexity is more easily said than done. MOORE’S LAW – the speed of the processors id doubling every 18 months, while the cost of the computing power is halving within the same time period. As computers are getting faster, systems are getting more and more complex and design flaws are becoming an increasingly catastrophic problem. Anticipation of failures at the infrastructure level, features that are transparent to software applications should be implemented to detect faults, to fail over to redundant components when faults are detected and to recover from failures before they become catastrophic.

GUIDELINE 3: ANTICIPATE SUCCESS The systems planning process should anticipate business success. Modeling of use case scenarios will enable the system designer to visualize the data flows, system loading, and network impact resulting from business growth and success.

GUIDELINE 4: HIRE METICULOUS MANAGERS Managing and keeping complex networks and integrated systems available and responsive requires meticulous overseers Good system administrators meticulously monitor and manage systems and network performance using out-of-band tools that do not themselves affect performance. They use middleware to manage the workload across the network They take emergency planning very seriously and procedures for managing emergencies and recovering from disasters.

GUIDELINE 5: DON’T BE ADVENTUROUS For dependability, one should use only proven methods, tools, technologies and products that have been in production, under conditions and a scale similar to the intended environment. The enterprise with a requirement for dependable systems should not be the first (or second) to adapt a new technology.

Assessing the health care industry

ASSESSING THE HEALTHCARE INDUSTRY Provides an informal assessment of how well healthcare provider organizations follow the guidelines. Conveys observation of the healthcare industry as a whole and the opinions of a passionate advocate of dependable systems for healthcare. Healthcare Architectures The HIPAA prescribes administratives, physical and technical safeguards for protecting the confidentiality and the availability of critical system services: Security management Assigned security responsibility Information access management Security awareness and training Security incident procedures Contingency planning Evaluation Business associate contracts

ANTICIPATING FAILURES The architectural complexity increases the opportunities for failures to occur. Medical applications that are hosted on PCs and PDAs have a greater likelihood of failures than applications hosted on server machines that are physically protected. Computers are increasingly being used in safety critical clinical applications and without careful and appropriate attention to software safety, we can reasonably expect that failure will contribute to the loss of human life.

ANTICIPATING SUCCESS Healthcare organizations definitely expect their software applications, computer systems and networks to work. Providers assume their systems will work well as any other medical equipment despite the fact that many of the software applications they use are running on the same kind of PCs that have failed them at home.

IT Management Many provider organizations truly do not recognize the criticality of IT to their business success. These organizations have hired IT managers who appreciates the important role of IT in a health care environment and who recognize the need for dependable systems that could anticipate and recover from failures.

ADVENTUROUS TECHNOLOGIES IN HEALTHCARE The 5th guideline “don’t be too adventurous” is more difficult to assess for healthcare. For dependable IT, the healthcare practitioner’s skepticism is a good thing. Newness and change are anathema to stability. Well planned and carefully executed changes over time are desired and expected, healthcare organizations should not be overly eager to adopt new technologies for life-critical systems.

ThE END!!!! Thankiiiee!! 