Scotland’s National Health and Social Care Patient Portal Tricia Duncan, Programme Manager, NHSGGC

National Patient Portal Develop a patient portal that will allow a single point of access for patients and public Build a platform to enable access to information and digital services Approach to development and implementation

National Patient Portal Commissioned by Scottish Government eHealth Directorate (follow up from Phase 1 Discovery piece) Initial funding secured for PoC and OBC Commission to be delivered by consortium of West of Scotland eHealth Leads including NHS24 Programme managed by Programmes & Strategy eHealth directorate of NHS Greater Glasgow & Clyde Governed by National Programme Board - first meeting in April 2017

National Patient Portal - Principles We will do this once for Scotland. People will have the same user experience regardless of where they live. The same baseline services will be offered to everyone and expanded incrementally over time. myaccount will be used for user authentication.

Why do we need a National Patient Portal? Multiple authentication / sign in routes

What are the potential benefits? Targeted Improvements Current Approach Future “Portal Approach” Sign posting Multiple sites and services and log ins Ease /single point of access Transactions Manual, paper based Digital, online Supporting new Models of care New models emerging - linked to clinically led transformation plans but needs technology to enable at scale More potential for: Innovation Collaboration/shared learning Patient self-management

To provide a single point of access …and new services

What have we been asked to do? Further develop the business case for an incremental approach to ‘platform’ delivery that will in time deliver a full range of services Prototype, prove and inform the design of an appropriate ‘platform’ for the range of required functionality Build a minimal viable ‘platform’ and associated products that will demonstrate the concept and provide the key features to enable the delivery of a range of agreed services Develop a framework for integration of the platform into a range of dependent applications and data sources

What we are aiming to deliver? Landing Page providing single point of access for patients (co-designed with patients) Authentication arrangements using myaccount (utilising CHI) Verification process to ensure patients have the appropriate levels of access Platform providing common building blocks (technical services) for implementation of patient services. The means to connect into multiple back end systems to locate, share and receive data (bi-directional) The means to allow clinicians’ to view relevant patient generated information in a seamless way PoC by Q3 2017 Technical services – things that patient services will use .i.e. RBAC, Multiple back end systems means back end systems such as TrakCare , Clinical Portal SCI Store etc but might also include other patient services like MDMW PatientView

Approach Proof of Concept Outline Business Case Basic Patient Portal Product Definition Myaccount integration Support Model Links to existing sites / systems Shortlist Implementation Options PoC of a minimum of two representative use cases Cost Benefit Analysis Demonstrate integration to multiple back end systems (WOS boards) Describe portal operational governance mechanism WOS centric National focus

The term service is used in many contexts in this model. In general terms a service can be defined as an encapsulated set of processes supplied by a provider to a receiver. A service might be: a “patient service” where the receiver is a patient. Eg an appointment viewing service. a “portal service” being a set of processes providing some feature on the patient portal. Eg an appointment retrieval service might provide the feature of retrieving appointments of a particular patient from the various back end systems. This service might be used by the appointment viewing service or the appointment amendment service. a “platform service” being a set of processes available within the portal platform for use by other services. Eg the “approvals service” might offer a circle of care feature to other services such as the appointment viewing service. a “technical service” might be something like a an authorisation service which would encapsulate the processes needed to control access to features within the portal and would be available to all other services within the system. A service can be considered as a black box, meaning the service recipient does not need to know what the service provider needs to do within the box for them to receive the benefit of that service.

Example Services Book/amend/cancel GP appointments Accept / Decline appointment offers. Consolidated view of hospital and other appointments. Order repeat prescriptions with your GP. Look up test results. Show a list of medication prescribed by your GP. Look up clear information that explains your test results and medication Receive letters, appointment details, etc Ask your doctor or nurse a question, using a secure written message. Get copies of letters written about your care Be notified when things happen related to your care Receive reminders by email or text Set goals for yourself, and measure your progress towards those goals. Record your own notes and measurements for doctor or nurse to see. These are just some of the services that have been proposed for the new patient portal and the likely list from which the first portal services will be drawn.

Get in touch ... John Costello, Project Manager email: john.costello@ggc.scot.nhs.uk Tricia Duncan, Programme Manager email: Tricia.duncan@ggc.scot.nhs.uk