1. 1 Using and Sharing Information

2. 2 Where do we want to take Information Sharing? What are the expectations, concerns and wants of service users and carers? What would practitioners and service managers like to do to benefit users? How can we be sure we are talking about the same service user? If we ask for consent to share information – what is the service user signing up to?

3. 3 Where do we want to take Information Sharing? How do we safely share information across a partnership, an area or a region? What are the resulting data controller / processor responsibilities? How do we spread practice incrementally? How do we govern what’s going on?

4. 4 EducationSocial Services Health YOT Police Housing Connexions Other Information Hub ISA Information Hub

5. 5 EducationSocial Services Health YOT Police Housing Connexions Other Information Hub Child Protection Information Hub

6. 6 EducationSocial Services Health YOT Police Housing Connexions Other Information Hub SAP Information Hub

7. 7 EducationSocial Services Health YOT Police Housing Connexions Other Information Hub Housing & Benefits Information Hub

8. 8 Health Visitor Social Worker Housing Officer Voluntary Worker Youth Offending Team Worker ASBAT Worker Connexions Worker Doctor A&E CAMHs worker GP Educational Psychologist PRU SENCO Teacher School Nurse But life’s not like that

9. 9 Hub need to talk to other hubs

10. 10 National Federation

11. 11 Let’s start with the partnership The purpose of the partnership is to achieve a range of outcomes for users The partnership must have powers to: –Plan - and deploy people and resources –Procure –Manage pooled budgets and projects –Govern its activities properly –Govern information sharing

12. 12 Partnership agreement A promotional group will need to negotiate a written agreement with member agencies: –commitment to the vision/values/outcomes –approval processes for business cases –resources and administration –proper processes - information governance –delegated responsibilities –recommendations to member agencies –member agency scrutiny and reporting

13. 13 Meanwhile at the coalface Practitioners and managers need to: –involve service users and carers –decide the scope of the service –decide on the location of the service –develop multi agency practice –undertake training in information sharing, implement the ISP, joint assessment –develop the scope of the IT systems –implement/train practitioners to use IT

14. 14 Sources of advice/help Who knows about: –Good communications? –User participation? –Scanning websites to collect legislation, policy and guidance? –Drafting partnership agreements and can talk about legalities? –Drafting the ISP?

15. 15 Sources of advice/help Who knows about: –Financial, procurement and audit processes? –Drafting job specs? –The issues and can design/deliver training? –The information governance toolkit?

16. 16 Tensions Partnership working always produces tensions – perhaps divided loyalties Information sharing practice takes time to develop - reassurance and supervision IT must suit the users – not vice versa It takes time to understand ‘indexes’ ‘portals’ ‘switches’ ‘infrastructure’ ‘Federation’ is different to ‘integration’

17. 17 Practice The FAME Generic Framework text addresses these issues. You can access selected text through the RAT You can access the jigsaw pieces through the website.

18. 18 Using the RAT - 2 Reporting to your directorates on –“Information sharing” A,B,C –“Governance” D,E,F Groups C+D Leadership/Policy & Strategy Groups E+F People/Partnership Resources Groups A+B Processes/ Internal + External Results List the key actions you need to take to get to level 3/4 How long will those actions take to achieve

19. 19 The Context: We have focussed on partnership working We have also focussed on caring services These are the harder cases, The FAME approach applies just as compellingly to a single authority. It is a concrete and practical framework. But…

20. 20 What is this session about? A strategic approach to planning and procurement. The management of future-proofing and legacy.

21. 21 How not to procure an application… Power supply Hardware Operating System Database Application …or subsequent applications

22. 22 How not to procure an application… Power supply Hardware Operating System Database Application …or subsequent applications Capacity for future applications Platform

23. 23 But the nature of applications has changed… Power supply Hardware Operating System Database Application Increasing interdependence Increasing use of common functionalities Hub Platform

24. 24 Common and cross cutting functions: some examples Authentication, identities, preferences and consents. Knowledge management, CRM Case management and workflow, Web catalogue, publication, e-transaction Etc, etc… These are not applications…we need a new name for them.

25. 25 WEB “services”: A way of making capabilities available to current and future applications. Using the same web services delivers –Integration within domains –Federation across domains Portal, switch & index, hub and spoke are ways of classifying the web services we need –What they do –Where they put and who delivers them. A web services approach is cheaper and more effective in the medium term.

26. 26 Again: how not to do it: Create a purple “solution”, a blue “solution” and a red “solution”. Package them up as “products”. Require Authorities to deploy one of each. Just more “super-silos”

27. 27 But the nature of applications has changed… Power supply Hardware Operating System Database Applications

28. 28 Three levels of systems provisioning Power supply Hardware Operating System Database Applications Web Services Applications Platform Intra, Extra, Inter-net, Mobile, DTV, Face-to face,… Channels & media

29. 29 But all this applies to the single Authority What about partnership?

30. 30

31. 31

32. 32 Federation services

33. 33 Federation Service Systems Partnership Hub Systems Partner Enterprise Systems

34. 34 The general trends: Appropriate record information is shared through syndication and publication services. Case and process management make use of common message and transaction services. Basic information such as directories, gazetteers and registers migrate to the federation level. Configuration and re-configuration become governance processes in the user domain not in the supplier domain. Information about information is published and used to develop new process and practice.

35. 35 Lets take an example of how this could be put into practice: A virtual social care record But…

36. 36 This approach applies to any complex multi-agency service: Business support, economic development, health, crime reduction, dead badgers, etc… All of these require: –Information to be gathered –Assessments and decisions to be made –Options to be selected, planned, monitored and evaluated. –Records, accounts and audit trails to be maintained. Individual service elements may be provided internally or externally, in partnership or through commercial supply.

37. 37 An example from social care The school nurse scenario

38. 38 Local Hub Systems Gateway MainfamilylocalPane 4 Achievement Record Summary Case History John Henry Smith PCT Acute Trust Social Services Education Remote Systems National Systems AnnSchool NurseW Voluntary NPfIT Gateway

39. 39 HP School Nurse emergency routine worry case SS E MainfamilylocalPane 4 Achievement Record Summary Ann Case History John Henry Smith School NurseW individual user specific role context particular client Involved Agencies Education Health Social Services Police SS Push items SS Pull items SS Alerts SS Offers Publication Profile Summary Case History Achievement Record Presentation Profile What Social Services and the client have agreed to make available to school nurses wanting to explore a concern about a child. How available information is to be presented to a nurse exploring a concern.

40. 40 This is not just a shared record system Implements evolving ISPs through configurable syndication services. Provides role, context and relationship based access and session control. Combines this with: –Groupware services for joint assessment and decision making and planning. –Offer, booking and transaction services for the implementation of service plans.

41. 41 How do we apply WEB services to deliver this? What are the functions needed to deliver a virtual, syndicated record? Which of them would be useful in other applications and contexts? What are the data controller and data processor responsibilities? What do these considerations imply for the location of a WEB service: –Internal partner system –Shared Hub System –In a Federation System

42. 42 Some services User and systems register Authentication service Subject registers and identification services Relationship discovery service –Service provider register –Relationship index Consents and identity management services Publication and syndication services Catalogue, booking and event handling services. Smart Cards ISA “index” CRM Citizen Account Portals

43. 43 A practical strategy for procurement: The business case must be based on more than the current project. We must identify the reusable components and specify them as web services. We must anticipate the availability of services at the Regional and National levels. We must ensure that the service interface is open and is published: a community good. This is what we do in the case of our ICT platforms and infrastructure today: we are simply redefining the line.

44. 44 Strategic procurement: Split the specification into components: –The parts that are dedicated and specific in the long term. –The parts that could be reused in the implementation of further hubs. –The parts that might represent universally useful services. Maintain the distinctions Demand reusability Separate suppliers exposes interfaces.

45. 45 First generation procurements: Federation services do not exist yet. Legacy applications are not web service oriented but some are web enabled. A complete set of functionality is required to deliver user benefit. This means that there is a strong argument to: –Combine services, e.g. register, index & record. –Optimise platform resources, e.g. data warehousing This is optimising the business case over a single “application”.

46. 46 Acquiring the ICT Which staff, from which partners, need to be involved in the procurement of a web services architecture? –Not just a question of process mapping and use case development. Which parts of your partnership system can be reused in other contexts? How do we produce strategic business cases for strategic procurements? How do we engage suppliers and develop the market?

47. 47 Using the RAT - 3 Reporting to your directorates on –Infrastructure A, B, C. –Federation D, E, F. Groups E+F Leadership/Policy & Strategy Groups A+B People/Partnership Resources Groups C+D Processes/ Internal + External Results List the key actions you need to take to get to level 3/4 How long will those actions take to achieve