ITK Technical Forum Wednesday 26 th January pm 16.30pm National Motorcycle Museum, West Midlands, B92 0EJ

Transcription

1 ITK Technical Forum Wednesday 26 th January pm 16.30pm National Motorcycle Museum, West Midlands, B92 0EJ

2 Agenda Introductions and Objectives Inderjit Singh Keynote Speech Liberating the NHS & the Challenges for System Vendors & The role of Technology Office, ITK & the Standards Agenda Paul Jones ITK Background & Overview ITK Groups & Relationships & output from NHS User Forum Inderjit Singh The NHS View of ITK Mark England ITK Management Group Direction & Priorities Ben Dunlop Coffee and Networking Current Priorities Accreditation Richard Dobson Technical Design Strawman - Correspondence & Spine Mini Services Tim Davey Open Invitation for Involvement Paul Sanderson Questions & Feedback All AOB Inderjit Singh

3 Welcome, Introductions & Objectives Inderjit Singh Lead Technical Architect Technology Office Department of Health Informatics Directorate /systemsandservices/interop

4 Local NHS Integration Simplify and standardise on a NHS code of Connection Provide technical support for Liberating the NHS strategic objectives Share best practice solutions and requirements Engage with industry to adopt common technologies and APIs Build a viable market around ITK based information sharing

5 ITK Approach Specification Standards Infrastructure Operating Model Conformance A set of standards and frameworks for vendors to build against Either core product or using adaptors Common technical standards XML Web Services Standardised envelopes and wrappers Standard patterns and application behaviours Standardised message structures NHS Organisations operating considerations Provides guidance, processes and governance for use when using the standards Vendors will be required to attain a conformance certificate for applications claiming to be compatible with ITK NHS Organisations should ask for this when procuring systems Community User Forum Technical Forum

6 ITK News ITK User Forum established 97 NHS organisations attended ITK NHS led Management Group established 16 NHS ICT Directors and Integration Leads ITK now has a long list of topics to address from the forum ITK at the heart of the new Information Strategy... More from Paul Jones and the team shortly

7 Liberating the NHS & the Challenges for System Vendors & the Role of the Technology Office, ITK & The Standards Agenda Paul Jones Chief Technology Officer Technology Office Department of Health Informatics Directorate /systemsandservices/interop

8 Questions

9 ITK Groups & Relationships & Output from the NHS User Forum Inderjit Singh Lead Technical Architect Technology Office Department of Health Informatics Directorate /systemsandservices/interop

10 ITK Community DHID SMT ITK Forum Management Group NHS ITK User Forum Common NHS Business Requirements NHS Trusts and Consortia DHID ITK Team ITK Technical Forum Accredited Systems Vendors Common Technical Specifications Modelled on Continua working groups

11 Roles and Objectives NHS ITK User Forum NHS Front line led ITK Requirements Management Group drawn from this forum Co-ordinated by DHID ITK Team Develop and agree common business requirements Advise of prioritisation of specification development Share project information and vendor intelligence Develop business accreditation criteria for solutions

12 Roles and Objectives ITK Forum Manage ment Group NHS ICT Directors and Senior NHS Representatives Chairman John Thornbury (Director of ICT Services Worcestershire) Represent the NHS User Forum membership and direct priorities for development within ITK Evangelise ITK to NHS and industry Ensure sign-off of solution with Requirements Team

13 Roles and Objectives ITK Technical Group NHS ICT Teams, Vendors, Standards Organisations, DHID Technical Team Co-ordinated by DHID ITK Team Develop and agree technical specifications to address the business requirements Develop technical accreditation criteria for solutions Ensure sign-off of solution with Requirements Group

14 Roles and Objectives DHID ITK Team Coordinate activity in User and Tech Forum Publish ITK Specifications QA standards developed for consistency Provide accreditation services Shaping the solution(s) and stewardship for First Of Type projects Provision of specialist skills where appropriate

15 Roles and Objectives Vendors Develop applications to ITK standards Ensure solutions are accredited Deploy accredited systems Provide input into the technical specification development process Provide feedback regarding the usability of the specifications

16 Roles and Objectives NHS Trusts and Consortia Ensure that front line problems are brought to the requirements forum (User forum) Commit vendors to ITK standards when letting contracts Enforce accreditation Provide a market for vendor ITK based solutions First of Type new standards and specifications Call off ITK Interfaces from LSP contracts

17 ITK Community DHID SMT ITK Forum Management Group NHS ITK User Forum Common NHS Business Requirements NHS Trusts and Consortia DHID ITK Team ITK Technical Forum Accredited Systems Vendors Common Technical Specifications Modelled on Continua working groups

18 ITK and the NHS November 16/17 th ITK User Forum (Leeds and London) 97 English NHS organisations come together to discuss ways to solve common business interoperability problems through ITK - More from Ben Dunlop shortly

19 Questions

20 The NHS View of ITK Mark England Head of Information Technology Luton & Dunstable Hospitals NHS Foundation Trust January 2011

21 Some Context:

22 Agenda The ITK (integration toolkit) is important to the wider NHS and my Trust because: 1. Change is inevitable therefore agility is a pre-requisite 2. Money is too tight to mention 3. Monolithic has failed 4. Are we serious?

23 Who Says There Will Be More Change?

24 Immense Architectural Challenges within NHS!

25 Our HealthBus: An Enterprise (Service) Bus The ITK ITK

26

27 Monolithic has failed......away from an approach where we expect every organisation to use the same system, to one where we connect and join up systems. (Information Strategy Consultation October 2010 DoH)

28 Is it real?

29 How does the NHS move the ITK forward? The Supplier will comply with <latest version> of the ITK specifications. (v1.1) The Supplier will comply with NICA accreditation in this and future releases within X months of release The Supplier will ensure that for each interface they are satisfied the Trust Operating Model checklist has been completed.

30

31 ITK Management Group Direction & Priorities Ben Dunlop Technical Project Manager NHS Yorkshire and the Humber

32 ITK Management Group NHS Representatives from: ITK User Forum ITK Technical Forum (this session) DHID Project and Technical Support Chair John Thornbury, Director of ICT, Worcestershire Health ICT Services

33 Initial Meetings First Meeting 7 th December 2010 Draft Terms of Reference and Governance Structure Initial Requirements Prioritisation Second Meeting 11 th January 2011 Election of Chair ITK Technical Forum engagement

34 Group Terms of Reference Core Responsibilities: Setting Strategic Direction and Priorities for the ITK Oversight of ITK User Group and Technical Forum Engagement with Vendors and Trusts Promotion of ITK Standards for take-up

35 ITK Management Group Priorities Establish ITK Groups and Governance Structure Ensure appropriate NHS representation Engage with Vendors and Standards Bodies Formalise Process for ITK Standards being established Manage Expectations around Time-Frames and Deliverables from the ITK

36 ITK User Forum Feedback Survey of NHS organisations to identify existing challenges and suggestions for direction for the ITK 40+ responses received 80+ current challenges reported

37

38

39 ITK Initial Priorities Correspondence identified as quick-win Establish ITK User Forum sub-groups to identify and develop ITK requirements for: General Correspondence Patient Correspondence Referrals

40 ITK Technical Forum Sub-groups will be established to support the User Forum requirements developed for correspondence Opportunity for Vendors or NHS technical reps to input around existing projects and potential standards

41 ITK Implications for Vendors Why should we want to do it? Opportunity to increase the value of your solution by enabling it to connect to more systems Supplier preference in NHS procurement decisions Standardised requirements for NHS Trusts Reduce support overheads with consistent approach towards integration between systems

42 ITK Implications for NHS Trusts What do we get out of it? Better integration off-the-shelf between core systems and simplified Departmental systems integration Easier transition when migrating systems Criteria to assess capabilities when purchasing new systems (ITK compliance) Vendor influence with NHS-wide requirements

43 What next? Manage development of correspondence ITK standards Determine next areas for prioritisation Promote use of the existing ITK standards bundles Build materials to assist with ITK adoption across NHS Case studies on implementations Identifying future potential projects/sites

44 Questions?

45 Coffee & Networking /systemsandservices/interop

46 Interoperability Toolkit (ITK) Accreditation Process Richard Dobson Senior Assurance Analyst National Integration Centre Technology Office Department of Health Informatics Directorate /systemsandservices/interop

47 Background National Integration Centre and Assurance (NICA) have been operating NASP, LSP and ESP assurance and compliance processes since the inception of the NPfIT; these are primarily aimed at systems wishing to connect to the National Spine and its directly connected infrastructure. But with local interoperability in mind ITK pilots concluded successfully providing useful data for taking this initiative forward to wider rollout One of the learnings from the pilots is vendors of ITK conformant products want to be part of an Accreditation program NHS CFH is working in partnership with vendors, providing guidance, support and ultimately Accreditation.

48 Interoperability Toolkit Accreditation Scope Accredited System Scope Provider system (e.g. PAS, GP Systems etc) upgrades to support ITK services ITK Middleware ITK Consuming Applications and Devices Accreditation Testing Scope Positive functional interface testing Negative functional interface testing Key expected behaviours e.g. error handling Key Aim: evidence the adherence to ITK requirements Accreditation Testing Out of Scope SPINE connectivity (currently, use CAP) General Application functionality Non-functional testing End to end business testing e.g. UAT Information Governance e.g. Authentication, Audit checks etc. Clinical Safety Key Point; this is about demonstrating that the ITK accredited products have interfaces that interoperate it s the interface that is accredited.

49 The Catalogue and Other Services Accreditation entitles vendor systems to be listed in the ITK Accreditation catalogue that purchase decision makers can access to help select appropriate interoperability products. Accreditation Advantages Accreditation brings a number of potential advantages for vendors and purchasers Purchase decision makers can be sure that product interfaces are interoperable with other suppliers products that have ITK Accreditation for the same message bundles This needs to be a key factor in the purchasers decision making Going through the Accreditation process will also entitle vendors to access other services and support from NICA, designed to help them get products accredited and ready for market as quickly as possible.

50 So what are we doing right now? The accreditation process has been established. The accreditation catalogue is up and running, and we have ~25 vendors expressing interest is attaining accreditation with the list growing A number of vendors you will probably be familiar have already been accredited including Intersystems with Ensemble, INPS/EMIS with their Medical Interoperability Gateway (MIG), and PCTI with EDT Server Orion are currently being accredited for their Rhapsody product Other vendors indicating January 2011 timescales include; Street Heavers, Fiorano, and iplusit.

51 Questions

52 Technical Design Strawman Correspondence & Spine Mini Services Tim Davey Technical Architect Technology Office Department of Health Informatics Directorate /systemsandservices/interop

53 Overview In order to keep up the momentum generated by the pilots, work is already in progress on two key areas identified as priorities: Clinical Correspondence Building on the Discharge Summary demonstrated by the pilots Strawman design work aimed at increasing flexibility and allowing any type of clinical content to be carried Spine Mini Services Providing a simplified, lightweight mechanism for accessing key Spine functionality Initial focus on read-only access to PDS to assist with patient tracing Design is well underway, and initial pilots in progress The intention is to transition this technical design work over to the Technical Forum as soon as it comes online

54 Clinical Correspondence - Goals Goals Ability to carry any kind of CDA document Ability to include attachments with a document Ability to carry non-cda content (eg PDF, TIFF) Ability to transmit metadata describing key aspects of the document (sender, recipient, patient, time etc) And also other enhancements to support end-to-end addressing, audit, tracking etc

55 Clinical Correspondence - Enhancements Send Discharge Summary HTTP Header SOAP Header Send CDA Document HTTP Header SOAP Header Distribution Envelope Header Payload Pilot Payloads Payload Payload Latest 1. Service name made more generic ready to send any type of content 2. Distribution Envelope added to store additional end-to-end details 3. Multiple Payloads possible enabling attachments / metadata to be added The next few slides explain further

56 Clinical Correspondence Distribution Envelope Distribution Envelope Header Original Service Requested Address List Manifest Audit Identity Tracking Id Payloads Payload Payload Payload An end-to-end business address Allows the type and content of potentially multiple payloads to be described Allows a user identity to be passed end-to-end for audit purposes Facilitates end-to-end message tracking The Distribution Envelope provides technical support for more complex end-to-end usage scenarios

57 Clinical Correspondence Attachments and Metadata Attachments Distribution Envelope Header Payloads Payload Attachment Attachment Non-XML content, and Metadata Distribution Envelope Header Payloads Content Metadata Payload Opaque Payload Attachments (eg image) can be embedded within a CDA document Payload need not be CDA, nor even XML. Opaque payloads may be sent (eg PDF, TIFF) A metadata structure and taxonomy and structure has been drafted This allows key facts about the payload to be provided (eg from, to, patient etc) Attachments and Metadata open the way to rapidly automating a wide range of existing scenarios

58 Spine Mini Services - Goals Goals Make it easier to connect to key Spine services Easier technical interface Easier accreditation Identify high-value Spine services to open-up Provide ease of use - and limit risks - by constraining the available functionality (80/20) Start with read-only access to PDS

59 Spine Mini Services - Concept PDS PDS Modified CAP Assurance Middleware must ensure Spine is protected regardless of app behaviour E2E CAP Assurance ITK Middleware ITK Interface Accreditation A restricted set of functionality, appropriate to this lighter assurance approach (e.g. read only) App App Only appropriate for apps that would not otherwise be PDS connected at all

60 Spine Mini-Services - Status Draft Service Definitions Verify NHS Number Get NHS Number Get Patient Demographics Get Patient GP Practice Details Get Patient Demographics and GP Practice Details The plan is to continue the successful ITK approach of working closely with real NHS projects to finalise the mini-services specifications

61 Spine Mini-Services - Status Progress Concept agreed Interface defined Supporting behavioural specifications defined Operating Model implications defined Assurance and Accreditation approach drafted Real-world pilot projects initiated The plan is to continue the successful ITK approach of working closely with real NHS projects to finalise the mini-services specifications

62 Questions

63 Open Invitation for Involvement Paul Sanderson NHS Engagement Lead Technology Office Department of Health Informatics Directorate /systemsandservices/interop

64

65 Provides the NHS ITK User Community with a web presence Encourages everyone to get involved both open and closed networks and forums WebEx and other collaboration tools available Provides an opportunity for the NHS, DHID, vendors and other stakeholders to share information, latest news and project intelligence Supports the work of the ITK NHS and Technical Forums and sub groups Open invite for all to get involved and contribute Go to and register

66 Questions

67 Questions & Feedback Inderjit Singh Lead Technical Architect Technology Office Department of Health Informatics Directorate /systemsandservices/interop

68 Questions

69 Any Other Business /systemsandservices/interop