190 likes | 284 Views
Through a Glass, Clearly – The Future of the Information Services Department. Paper By Dominic Covvey President & Director National Institutes of Health informatics Presented By Shirley Fenton Vice President & Director National Institutes of Health informatics. Dominic Covvey.
E N D
Through a Glass, Clearly – The Future of the Information Services Department Paper By Dominic CovveyPresident & DirectorNational Institutes of Health informatics Presented By Shirley FentonVice President & DirectorNational Institutes of Health informatics
Dominic Covvey • Adjunct Professor, University of Waterloo and University of Ontario Institute of Technology. • President and Director, National Institutes of Health Informatics.
Classic IS The historic view of the IS Department (ISD) and its role. • Leadership: Role of the CIO/VPIS/ISD Director • Position in the organization: reporting and its issues • Activities and responsibilities: service vs development/initiation • Latitude of action and decision-making • Interface(s) to the functions of the institution • Local vs distributed vs centralized personnel • Role of the vendor(s)
Classic IS The challenges targeted by the classic IS department. • Push vs Pull or both • IT/IS planning • Project management • Technology management • Procurement • Implementation • Maintenance • User assistance • Liaison (with vendors, departments, admin, other institutions)
Classic IS The classic complement of the IS Department. • Analysts • Trainers • Project managers • Tech experts (apps, op sys, DBMS, systems, networks, …) • Sometimes: communicators, negotiators, flow-charters, business types, … • Rarely: industrial engineers, management experts, educators,…
Classic IS The classic organization of the ISD.Admin Head – often VP Finance. • CIO/VPIS • Director IS • Managers of various groups • Classic operational groups (e.g., implementation, maintenance, etc.)
The Demands of the Future Today’s + future’s new demand on IS Department. • Dealing with the full set of implementation issues (See Koppel research) • Recognizing and addressing true complexity • Contributing to institutional strategic planning • Disruptive approaches and budgeting • Delivering departments and enterprises • Focusing on processes and workflow • Minimizing the negative impacts of changing technologies • Dealing with the human element • Regionalizing, provincializing and nationalizing IS • Embracing reuse
Co-Factors of Technology The crucial role of the co-factors of technology. • Re-engineering • Management of Change, including adoption and cultural assessment • Education and Training • HR and Role Restructuring • Organizational Restructuring • Quality and Information Systems Assurance • Transitional Counseling
New Competencies The need for new competencies. • Quick review of competency definition. • New competencies base on new roles and co-factors • How to acquire new competencies: options • Attitudes – key competencies • How do you know if you are competent? • The AHI Self-Assessment System: http://www.nihi.ca/hi/index.php.
Organization Organizational models for the ISD in its new roles. • The local model – likely obsolete or transitional at best • The single vendor shared models • The multi-vendor shared models • The regional model • Other alternatives
Organization Human resources structure and function. • Some thoughts about HR structural rigidity • Approaches that address complexity • Hybrid and alternative models
The Extended ISD The role of super-users and users: The ISD without walls. • Specialist users as extensions of the ISD • Engaging providers in the IS organization • The distributed ISD: eHealth Team
Questions?Your Experience, Ideas & Suggestions • Dominic Covvey, dcovvey@uwaterloo.ca • Shirley Fenton, sfenton@nihi.ca
Implementation Implementation in all its detail -1 (some from Dr. Ross Koppel). • Best practices for working with vendors • Identifying measures for a “successful” implementation • Approaches to assuring a successful implementation • Workflow re-engineering planning and analysis • Governance • System content implementation • Managing users: adoption, management of change, education/training • Optimal approaches to documentation (maybe).
Implementation Implementation in all its detail -2 (some from Dr. Ross Koppel). • Assuring safe use of HIT • Data quality (maybe) • Fitting the system and the workflow to each other • Using HIT to support the quality mission of the organization • Issues in moving from one EHR to another (vs from paper to an EHR) • Meaningful use assurance • Testing and acceptance • Optimization • Dealing with upgrades, patches, outages.