eHealth in Scotland 11 th June 2007

1. eHealth in Scotland11th June 2007

2. eHealth in Scotland: Programme GovernancePaul RhodeseHealth Programme Director

3. Drivers for Programme Governance • Increasing recognition from the service that there is a need for a more corporate approach: • Kerr Report • Delivering for Health • Audit Scotland Review • At a national level the eHealth programme will enable a more corporate approach through: • Leadership • Stakeholder Engagement • Programme and Project Management

4. Strategy Principles • National Approach • Convergence • Build, fill gaps • National Procurements • Co-operation, working together, facilitating the wealth of NHS Scotland experience • Robust information governance Drivers for pace • Priorities • Affordable • Capacity

5. Minister Chief Executives Group NHS Board SEHD Departmental Board eHealth Strategy Board Clinical Change Leadership Group National eHealth Programme Board Heads of eHealth (NHS Boards) Local eHealth Implementation Board National Clinical Reference Group (NHS Boards) Local Project Board Local Project Board Local Project Board National Project Board Local National Deployment

6. eHealth Programme Clinical Engagement National Level NHS Board / Local Level eHealth Strategy Board National eHealth Programme Board Clinical Change Leadership Group eHealth Implementation Board Clinical Information Groups National Clinical Reference Group RCGP Individual Local Project Boards User Groups NMAHP Design Authority SCIMP Clinical Reference Group SGPC CHD IT Group Local Clinical Leads Individual National Project Boards Stroke IT Group NMAHP Ambassadors Child Health Strategy Care Reference Group Others Others

7. Programme Executive Team eHealth Programme Director PAUL RHODES Interim Head of Change and Benefits ELAINE HESLOP Interim Head of Strategy ALAN HYSLOP Interim Head of Design Authority JONATHAN MEDDES Interim Head of Programmes ANGELA MITCHELL

8. Developments and Initiatives • Community Health Index (CHI) • Scottish Care Information (SCI) Programme • Emergency Care Summary (ECS) • Generic Clinical System (GCS) • Integrated Primary and Community Care (IPACC) • Patient Management System (PMS) • Electronic HR System (EHRS) • User Authentication and Access Control (UAAC)

9. Role of the eHealth Programme Executive Angela Mitchell Interim Head of Programmes

10. Programme Management Approach

11. Programme Executive Team Role • Sits at SEHD level and supports the whole eHealth Programme • Led by the eHealth Programme Director • Provides central leadership for: • eHealth Strategy, Blueprint and Programme Roadmap • Definition and control of the eHealth architecture and standards • Common processes and good practice programme management • Commissions delivery of projects and programmes • Benefits management • Change management • Communications • Performance monitoring and reporting • Management of inter-dependencies between programmes and projects

12. Workstreams Strategy Change, Benefits and Communications • Develops and maintains the eHealth Strategy and Blueprint • Works closely with clinicians, eHealth professionals and policy interests • Develops and maintains Programme Roadmap • Evaluates feasibility of new ideas and concept development • Maintains alignment with the strategic direction • Develops benefits management strategy and tracks benefits realisation across the Programme • Supports identification, planning and realisation of project benefits • Supports planning and managing changes to processes, roles, and structures that are required • Manages eHealth communications at a national level • Provides consistency of messages and communication mechanisms across projects eHealth Programme Executive Team Design Authority Programmes • Establishes the technology architecture • Establishes standards for applications, infrastructure, data and security • Ensures appropriate development of information governance arrangements and adherence to relevant standards • Ensures patient safety and service quality requirements are reflected in solutions • Ensures that solutions are fully aligned to the architecture and standards • Focuses on delivery of overall eHealth Programme through the constituent projects • Commissions delivery of projects • Provides the national eHealth PMO • Monitors progress against the planned activity for national projects • Sets standards for programme / project management and provides guidance • Undertakes financial management of the eHealth Programme

13. Executive Team Structure National eHealth Programme Change Benefits Communications Strategy Design Authority Programmes Project Commissioning Information Governance Service Redesign and eHealth Reqts. Market Intelligence, Research & Evaluation Data Standards & Architecture eHealth Staff Skills, Resource Management & Career Development Health Records, Information Mgmt & Data Quality Strategy Maintenance and Delivery Roadmap Service Standards Architecture Benefits Identification & Delivery Programme Management Office Definition of Project Briefs Security & Authentication Clinical Leads National Projects Applications Standards & Architecture Outline Business Case Development Communications Ongoing Contract Management (NSS) Technical Standards & Architecture User Skills Development

14. Clinical Engagement in eHealth Dr Kenneth Robertson & Heather Strachan

15. Clinical Change Leadership Group Dr Kenneth RobertsonClinical Lead IM&TSEHD

16. The Main Questions • Why do we need it? • Who will it be? • What will they do? • How will they do it? • When will they do it?

17. Why? • eHealth versus Information Technology • Different world of healthcare across boundaries • New rules of governance • New risks

18. Who? • Peter Donnelly • The “Great and The Good”

19. What and How? • Reports to eHealth Strategy Board and Liaison with Clinical Reference Group • Ambassadors for change • Identification and scrutiny of interface issues - e.g. between old and new technologies • Clarification of training requirements • Incorporation of advice into professional processes e.g. revalidation • “Carrots and Sticks”

20. When? • Very soon and in parallel to the other more technical work • Much of the preparation can begin without the need for new software and machines • Main task is to change the mindset

21. How will you know it’s working? When the tools you are given to do your job, actually help you and seem to have taken account of the way you work and your responsibilities in respect of the patient, your colleagues and your professional requirements.

22. The Clinical Reference GroupIt’s not a bunch of roses!It does what it says on the tin! Heather StrachanNMAHP eHealth Lead

23. Clinically Led and Benefits Driven

24. Clinical CLINICAL Communication Consensus Champions Convergence

25. Reference REFERENCE Representation Reality Check Raising Issues Relevant

26. Group GROUP Goals Governance Good Practice

27. “What’s in a name? That which we call a rose. By any other name would smell as sweet” Romeo and Juliet Shakespeare “It does what it says on the tin!” What’s in a name: The Clinical Reference Group