Maintenance and Troubleshooting of Health IT Systems
This material delves into the installation, maintenance, and troubleshooting of Health IT systems, covering topics such as effective troubleshooting procedures, downtime scheduling, communication between vendors/developers and users, system performance measurement, and diagnosing complex EHR infrastructure issues. Practical examples and guidelines are provided to address common problems and ensure seamless operations in healthcare settings.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
Installation and Maintenance of Health IT Systems Troubleshooting; Maintenance and Upgrades; Interaction with Vendors, Developers and Users Lecture b This material (Comp 8 Unit 8) was developed by Johns Hopkins University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information Technology under Award Number IU24OC000024. This material was updated in 2016 by The University of Texas Health Science Center at Houston under Award Number 90WT0006. This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-sa/4.0/. http://creativecommon s.org/licenses/by-nc-sa/4.0/.
Troubleshooting; Maintenance and Upgrades; Interaction with Vendors, Developers, and Users Learning Objectives Identify and implement an effective troubleshooting procedure for reporting, evaluating, fixing, deploying, and follow-up of errors, problems, or limitations for the system (lectures a & b). 1. 2. Integrate downtime schedule for OS, network, database, and client application maintenance and updates (lecture b). 3. Develop a process for communicating requirements and supplying updates between vendors/developer and users (lecture b). 4. Create a baseline for system performance measurement and comparison for troubleshooting (lecture b). 2
Troubleshooting: Diagnosing Complex EHR Infrastructure Issues Identify the problem Determine the scope of the issue Start Simple Seek Additional help during an Outage Remember to communicate (Halamka) 3
Troubleshooting: Diagnosing Complex EHR Infrastructure Issues (cont d) Use the logs Develop a timeline Stick to the Plan Set deadlines for escalation Stay focused on resolving the problem. Don t be too quick to declare a problem resolved. (Halamka; AHRQ, 2011) 4
Troubleshooting: An Example User contacts the EHR Helpdesk about slow EHR Start with the local machine o Recent Updates or Patches o System and Application Logs o Wireless/ Ethernet Connectivity 5
Troubleshooting: An Example (cont d) If the issue is more widespread Network or ISP Issues o Misconfigured switch, router, ISP Connectivity Erroneous OS Upgrade/ Misconfigured Server Server Hardware Error/ Upgrade Needed Application Upgrade Error o EHR Design o EHR Software Code 6
Performance Baseline Generated after completion of performance baseline testing. Shows normal operating parameters of your system under normal load conditions. Used to gauge overall system health & assist with isolating performance problems. (Wunder) 7
Performance Baseline: Testing Benchmark testing Compare performance of new server/system against standard (e.g., existing measurements or software specs). Test at regular intervals, when problem-free: System resources (server & hardware) Network architecture Operating system Database applications Client applications (Sqlserver, 2009) 8
Performance Baseline: Utilities Available Work with vendor to determine best method for your EHR. Many third-party utilities available. Windows built-in utilities: System Monitor (collect & view real-time data on usage of memory, disk, processor) Performance logs & alerts Task Manager Event Tracing for Windows (ETW; trace & log events raised by user- mode applications & kernel-mode drivers; export most SQL Server events.) Databases often require special utilities. SQL Server built-in utilities: SQL Trace SQL Server Profiler SQL Server Management Studio Activity Monitor SQL Server Management Studio Graphical Showplan Stored procedures Database Console Commands (DBCC) Built-in functions Trace flags (Microsoft, 2011; Technical, 2005) 9
Performance Baseline: Measurements & Next Steps Measurements Peak vs. off-peak hours Production-query, batch-command response times Database backup and restore completion times Next steps Compare baseline statistics to current server/system performance. Investigate if numbers far above or below baseline. (Wunder) 10
EHR Maintenance & Upgrades Upgrades crucial for extending EHR functionality & overall system lifespan. Improperly planned/managed upgrade procedures can severely damage system, reducing performance. Use highly structured approach in upgrading any major, critical production system. 11
EHR Maintenance & Upgrades: Structured Approach Upgrade team Works with vendor. Reads upgrade documentation. Analyzes functional enhancements. Works with vendor on unknown variables. Makes plan to configure & test affected applications. Technical team develops alternative testing environment (test bed). Upgrade team compiles pre-installation & installation checklists, determines downtime. After first testing, logs reviewed & errors/discrepancies reported to vendor. 12
A Structured Approach (contd) After vendor resolves issues, upgrade process retested, ensuring data integrity. Consider software to simulate workflow & users; track data for performance analysis. Unified spreadsheet to track issues. Once testing complete & upgrade approved, final documentation prepared & training scheduled. Installation team finalized & assigned roles. Upgrade scheduled during off-peak times. EHR shadow copy (read-only, without real- time interfaced results) accessible during upgrade. 13
A Structured Approach (contd - 2) Upgraded system tested immediately after completion. Once testing complete, help desk notified & systems brought back online. Dedicated team available for several business days to resolve issues. (Follow similar processes for upgrades to server OS, workstation OS, databases.) 14
Interacting with Users Stay up to date Set realistic expectations Value your user s time Be friendly, but stay on task. Listen Closely, and acknowledge the user s issue Use the opportunity to educate Be patient (Boyer, 2005) 15
Client-Vendor Relationship Essential not only for successful implementation, but also for continued success of product. Issues will arise beyond scope of your IT workforce. Routine upgrades needed. Vendor plays pivotal role in these & other events. Successful partnerships built on mutual goals, trust. In this together . Success of vendor depends on success of product. Long-term commitment between organization & vendor. Relationship becomes complex once organization dependent on fully embedded EHR. (Boyer, 2005) 16
Client-Vendor Relationship: Before Purchase Understand vendor company & culture. Visit headquarters, talk with as many as you can (including development & support). Follow the money. What drives revenue stream? Dependent on support fees? Understand support-fee structure. Financially solvent enough to provide long-term support? Hosted and SaaS (Software as a Service) solutions: understand vendor s upgrade strategy. Will it conflict with your business practices? Impressions of vendor s support staff (Boyer, 2005) 17
Troubleshooting; Maintenance and Upgrades; Interaction with Vendors, Developers, and Users Summary Performance baseline Helps gauge system health & isolate problems. Structured approach for upgrades Separate environment for testing upgrades prior to rollout. Work closely with vendor to resolve issues. Rollout during non-peak hours. Client-vendor relationship EHR purchase brings long-term commitment. Complexity once dependent on EHR. Understand vendor & culture before purchase. 18
Troubleshooting; Maintenance and Upgrades; Interaction with Vendors, Developers, and Users References Lecture b References Boyer, E. and M. Soback (2005). Production Support. Implementing an Electronic Health Record System. J. M. Walker, E. J. Bieber and F. Richards, Springer London: 95-100. http://www.springerlink.com/content/n520ghg078416463/ Event Tracing for Windows (2011). Microsoft.com. [Internet]]. http://msdn.microsoft.com/en- us/library/ff545699.aspx . AHRQ. (2011). Guide to Reducing Unintended Consequences of Electronic Health Records [Online]. https://healthit.ahrq.gov/sites/default/files/docs/publication/guide-to-reducing-unintended- consequences-of-electronic-health-records.pdf Halamka, John. 10 tips for troubleshooting complex EHR infrastructure problems. KevinMD.com. [Internet]. http://www.kevinmd.com/blog/2010/09/10-tips-troubleshooting-complex-ehr- infrastructure-problems.html. Technical Comparison of Oracle Database 10g and SQL Server 2005: Focus on Manageability, May 2005 (2005, May). Oracle [Online]. http://www.oracle.com/technetwork/database/manageability/ss-1.pdf 19
Installation and Maintenance of Health IT Systems Troubleshooting; Maintenance and Upgrades; Interaction with Vendors, Developers, and Users Lecture b This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information Technology under Award Number IU24OC000024. This material was updated in 2016 by The University of Texas Health Science Center at Houston under Award Number 90WT0006. 20
