Generic Framework Toolkit

1. Generic Framework Toolkit Mike Martin Centre for Social and Business Informatics Newcastle University

2. This session • Hubs, spokes and axles: integration and federation. • Joining up information: messages events and transactions. • Security, authentication and consent: Identity management. • Services architecture: the key to reuse of infrastructure.

3. Applications Database Hardware Middleware The shape of the technology..

4. Portal Finding & accessing The Hub Marshalling & dispatching Front office Switch Recognising & naming Index Application Adaptors Applications Back office Database Hardware Single Authority The WEB, new channels and media Middleware

5. Publication & collaboration space. Agency systems with local records. Partnership The WEB, new channels and media Portal Finding & accessing The Hub Marshalling & dispatching Switch Recognising & naming Index

6. Other hubs Hubs must talk to hubs The WEB, new channels and media Portal Finding & accessing The Hub Marshalling & dispatching Switch Recognising & naming Index

7. Joining up at the regional and national levels Publication and syndication. Identity and consent across boundaries of established trust Workflow crossing local partnership boundaries Federation services

8. Hubs, spokes and axles • This is a way of thinking and talking about current technology: Gateway, LGOL-net, Government connects… • “Integration” and “seamlessness” are single enterprise terms - public service is a multi-agency world. • “Seams” do an important job – especially when things start to go wrong. • We need to be able to create, change and maintain appropriate boundaries. • Practitioners, clients and managers shouldn’t be dependent on technicians to do this for them.

9. But how do we join up the records?

10. An example from social care.

11. Remote Systems Acute Trust Social Services National Systems Voluntary Education PCT Gateway John Henry Smith Ann School Nurse W Gateway Main family local Pane 4 Case History Summary Achievement Record Local Hub Systems

12. Joining up: • Information is gathered and presented according to: • The client’s needs, interests and consents • The service provider/practitioner needs • At the time and in the specific service context • Data controller responsibilities remain with the individual record holding agencies. • Delivering “data integration” implies data processor responsibility only. • We need to think about publication and syndication.

13. Remote Systems Acute Trust Social Services National Systems Gateway Voluntary Education PCT John Henry Smith Ann School Nurse W Gateway Main family local Pane 4 Case History Summary Achievement Record Local Hub Systems

14. Identity, consent and data protection

15. Talking about identity • Enormous temptation to keep it simple. • Let’s pretend that we can allocate and maintain a unique universal identifier. • The best we could achieve is 95% coverage and quality. • If the problem is a child’s welfare, this is not good enough. What is the alternative?

16. Register 1 Allocate a new, locally unique identifier Collect identity information Record initial content

17. Register 1

18. Portal Finding & accessing The Hub Marshalling & dispatching Switch Linking Identifiers Index Register 1

19. Registrars create and maintain identities Portal Finding & accessing The Hub Marshalling & dispatching Register 2 Switch Identity Managers make these links Record holders manage content Register 1 Linking Identifiers Index

20. Data controllers for identity information Portal Finding & accessing The Hub Marshalling & dispatching Register 2 Switch Data controllers for service content Register 1 Data processor Linking Identifiers Index

21. But what does this mean? • For practitioners, managers and strategists this is all getting a bit technical…. • For technical people it is all to abstract and high level. • Publication and syndication imply a WEB services approach. Let’s take a quick look…

22. User & Systems Register Service Subject Register Service Provider Register Hub Index Service Subject consents & Identity management Service User Authentication Service Subject Identification Service Relationship Discovery Service Publication Location Service Meta-Data Publication Service Service Relationship Offer Type Session Subject User Presentation Service Subject Network Service Provider Role Offer Instances & content Context Hub Process and WF tables Event Handling Service Service Event

23. So what do we do? • The first generations of hubs have to do everything for themselves. • An ISA/IRT “index” is a register, index and a record in FAME terms. • How do you future proof this investment? • How do you make its components reusable and sharable? • How do we ensure that the next hub and the one after that do not have to start from scratch?

24. Building the federal approach. • The challenge of the business case for infrastructure. • The picture is too big and too complicated… • The benefits are in the future… • Keep It Simple Stupid: just tick the boxes and draw a line! • What vehicles are appropriate to deliver federation services? • Sub-region, region, super-region and national. • How do we approach governance and participation?

25. The way forward: • The FAME framework describes how systems and practice are evolving using today's technologies. • This is being adopted now by Local Authorities. • Suppliers are beginning to buy-in. • There are emerging examples of federation. • FAME phase II will develop the business case for Regional Federation. Early adopters have a critical role in shaping the future of FAME.