11 June 2007 Version 1.0

1. eHealth Design Authority“What is it for, how does it do it, and the role of standards in taking forward eHealth” 11 June 2007 Version 1.0

2. Agenda • Welcome • The current situation • The eHealth Design Authority – what does it do? • The eHealth Design Authority – how does it do it? • Exercise 1 – what are the challenges? • The eHealth Design Authority and the role of standards in taking forward eHealth • Exercise 2 – the role of standards • The project lifecycle • Questions and Answers 2

3. The current situation • National perspective: • Duplication of effort? • Good practice and innovation not easy to transfer? • Lack of benefits of scale? • Too fragmented? • Local perspective: • Lack of central guidance? • National initiatives not joined up? • Too fragmented? • Crossing regional boundaries: • Current silos won’t support clinical networks? • Need for unambiguous and robust national standards? • Need for central eHealth Design Authority. 3

4. The current situation? 4

5. A key stream of the eHealth programme. Provides the Architecture and Design governance of the eHealth programme. Establishes a current ‘as is’ baseline and a roadmap for transition to the ‘to be’. Maintains a library of approved standards and promotes these within the eHealth Programme. References, evaluates, and coordinates with specialist groups. Ensures that the solutions align to the strategy and benefits aspirations of NHSScotland. Scope: Applications. Technical (infrastructure). Data and information. Security. Methodology. Service. Information Governance. The eHealth Design AuthorityWhat does it do? 5

6. The eHealth Design AuthorityHow does it do it? Architecture Steering Group Design Authority Architecture Principles Provides Strategic Direction eHealth Leads Used to Approve Updates Clinical Change Leadership Group Design Knowledge Base Design Authority Architecture Model Used to Approve Updates Maintains and Reviews Against Delegates Responsibility Provides Guidance and Approval National and International Standard Organisations Specialist Working Group Specialist Working Group Seeks Guidance and Approval Informs Specialist Working Group Reports to Specialist Working Group Project Solution Owner 6

7. Primary contact for eHealth projects to: Catch ‘errors’ early in the project lifecycle. Ensure the application of best practice. Provide consistency in the solutions delivered by the eHealth programme. Identify strategies for collaboration, resource sharing, and other synergies. Maintains the: Design Knowledge Base. Architecture Model. Works within the Architecture Principles. Regular Design Review and Approval Panel to: Provide design review and support to the programme, for example: Advice to projects early in the project lifecycle. Coordinates the ‘coming together’ of similar projects. Ongoing contact maintained between project ‘solution owner’ and prime contact in the DA. Provide design approval against standards, with outcomes of: Compliant. Non-compliant but exempt. Non-compliant. Design Authority (DA)Overview Design Authority (Red Box) 7

8. Exercise 1What are the challenges? • There are a number of challenges faced by NHSScotland IT projects, we would like to know what they are and how the eHealth Design Authority can help you with these challenges. • Each table will have a pack titled ‘Exercise 1’. • In groups (by table): • Identity the challenges faced by NHSScotland (the ones you think the Design Authority could assist with). • What you would like the eHealth Design Authority to do and how you would like to interact. • Pick the two biggest challenges and present to the wider group. • You have 10 minutes. • What we will do with your responses: • A quick around the room to capture the ‘big ones’. • Review and respond to your responses after today’s workshop. 8

9. Clinical Lead: Provides clinical input into the Design Authority. Information Governance Lead: Provides Information Governance input into the Design Authority and the wider eHealth and NHSScotland Information Governance. Security Lead: Responsible for the Security aspects of eHealth solutions. Head of Design Authority: Reports to the eHealth Programme Director. Overall responsibility for the Architecture and Design of eHealth solutions. Enterprise Architects: Broad skills, but lead assigned for Applications, Technical, Data and Service. Design AuthorityThe team Proposed Design Authority (Red Box) Clinical Change Leadership Group Information Governance Board Head of Design Authority Information Governance Lead Clinical Lead Security Lead Enterprise Architect – Applications Lead Enterprise Architect – Technical Lead Enterprise Architect – Data Lead Enterprise Architect – Service Lead 9

10. Specialist Working Groups (SWG)The role of standards Forums (Blue Boxes) • Covers all relevant specialist domains and standards organisations. • Works for the DA to: • develop and maintain standards in a particular area. • can recommend standards to be enhanced or created. • Decisions taken are reviewed and owned by the DA. • Provides expert advice to DA on the review of projects, e.g. on remedial actions to be taken. • Number of SWGs are envisaged, some already exist, some new and will replace current arrangements - deprecated bodies will, stop or become sub-groups. 10

11. Specialist Working GroupsAn Example Forums (Blue Boxes) Test and Validation Standards Infrastructure Standards Ad Hoc Groups as required Design Authority Service Standards ? ? ? Interoperability Group Information Standards Group Responsible for the NHSScotland Messages and NHSScotland Interfaces. Advise eHealth Programme on the timing and testing of releases. Responsible for the NHSScotland Information standards. Responsibility for sub groups for specific standards, e.g. NCDDP. 11

12. Exercise 2The role of standards • Standards and the bodies that define them are key to providing consistent eHealth solutions. • Each table: • Will have a pack titled ‘Exercise 2’. • Will focus on a particular standards area (e.g. infrastructure, applications, information, information governance, security, interoperability): • In groups (by table): • Identify the existing ‘Specialist Working Groups’ that the Design Authority should engage with: • Name of the group. • A brief description. • If possible, a Point of Contact. • Suggest additional groups that should be established. • If we don’t know about the groups – What’s gone wrong? How do we communicate better in the future? • You have 10 minutes. • What we will do with your responses: • Use them to establish connections with Stakeholders. 12

13. The eHealth Design Authorityand the Project Lifecycle Design Authority works with the Strategy Workstream to develop a concept aligned to the Architecture Roadmap and develop the Solution Outline. Design Authority provides input into the business and technical requirements. Design Authority provides guidance and reviews/approves the (LL) Solution Design for standards conformance. Initial Concept Concept Development Project Initiation Project Delivery – Procurement Project Delivery – Implementation HLD = High Level Design LLD = Low Level Design Design Authority provides input to help ensure the feasibility of the OBC Solution Outline. Design Authority provides guidance and reviews/approves the overall Solution Architecture and (HL)Design for standards conformance. Post-implementation review conducted. Project material collated and eHealth standards/designs updated. 13

14. What was really needed… 14

15. Questions and Answers • Over to the floor… 15