Guide to ITK Compliant Output Based Specification

Transcription

1 Guide to ITK Compliant Output Based Specification Directorate DHID Document Record ID Key Division DS&P/ITK NPFIT-ELIBR-AREL-DST Chief Technology Officer Paul Jones Status Approved Owner Keith Naylor Version 2.0 Author Michael Bond Version Date 01/07/11 Guide to ITK Compliant Output Based Specification Crown Copyright 2011

2 Amendment History: Version Date Amendment History /01/11 First draft for comment /01/11 Updated with comments after first review /01/11 Addition of section covering third party standards /03/11 Approval by NHS ITK Management Group /06/11 TRUD sub-pack names removed due to changes and modular approach Reviewers: This document must be reviewed by the following: Name Title / Responsibility Date Rae Long Standards Consultancy Group Lead, ITK Project Co-ordinator 18/01/11 Bharat Sharma Standards Consultant 01/07/11 Tim Davey Technical Architect (Principal Consultant) 18/01/11 Inderjit Singh Lead Technical Architect 18/01/11 Paul Sanderson NHS ITK Engagement Lead 18/01/11 Terry Underwood Technical Architect 18/01/11 Damian Murphy Senior Assurance Manager 18/01/11 Richard Dobson Assurance Analyst 18/01/11 Brett Marshall Assurance Manager 18/01/11 All Members NHS ITK Management Group 01/03/11 Approvals: This document must be approved by the following: Name Title / Responsibility Date Keith Naylor Head of Data Standards Implementation and Outreach 08/03/2011 Crown Copyright 2011 Page 2 of 10

3 Distribution: NHS CFH / DHID restricted until approved. On approval this document will be added to the ITK resources for distribution to NHS Trusts as required. Crown Copyright 2011 Page 3 of 10

4 Document Status: This is a controlled document. Whilst this document may be printed, the electronic version maintained in FileCM is the controlled copy. Any printed copies of the document are not controlled. Related Documents: These documents will provide additional information. Ref no Doc Reference Number Title Version Glossary of Terms: Term Acronym Definition Web Service Client Web Service Host Adapter Toolkit Adapter Application Adapter Configurable An application (or middleware) that makes use of Toolkit web services. It makes calls to invoke Toolkit web services. Note that this is a role that an application plays in the context of a specific interaction. The same application can play the role of both web service client and web service host in different interactions. An application (or middleware) that hosts a Toolkit web service implementation. Web Service Clients make calls to it to invoke processing. Note that this is a role that an application plays in the context of a specific interaction. The same application can play the role of both web service host and web service client in different interactions. An adapter converts between interface formats. This encompasses a wide variety of tasks, including, for example, protocol adapters (eg from MLLP to Web Services) and content adapters (eg to map data items into the National Standard format) An adapter that is provided and hosted as part of the Toolkit An adapter that is provided and hosted as part of the end application (for example as part of its own integration / interfacing framework). Where items are described as configurable then the term is defined as follows: A configurable item MUST be designed with the ability to Crown Copyright 2011 Page 4 of 10

5 change in mind. It MUST be possible to make the changes referred to within a single deployment, i.e. it MUST NOT be necessary to make changes to the underlying product set which impact on other deployments. It MUST be possible to invoke a change request at any time i.e. this is not tied to product release cycles. For a shrink-wrapped product then a sufficiently skilful customer MUST be able to make the change themselves, ie without the necessity to involve the product vendor or their staff. For a managed service then the supplier MUST provide a predefined process, service standard and cost structure for making the change. Health Level Seven UK HL7 Health Level Seven International (HL7) is the global authority on standards for interoperability of health information technology. HL7 UK is the affiliate organisation to HL7 International and has members from all sectors of the UK healthcare community. HL7 UK engages in education, training and marketing HL7 standards in the UK as well as developing UKspecific profiles. Other terms, acronyms and abbreviations commonly used within NHS CFH can be found in the Acronyms Guide Crown Copyright 2011 Page 5 of 10

6 Contents 1 About this Document Introduction Background Purpose Audience Scope Not in Scope Specifying ITK Compliance Specify the version number Specify the required bundles Specify accreditation Specify interoperability Specify assistance with the local framework Specify the required interface and fix costs Ensure that the Supplier is in good standing regarding rights to use third party standards Crown Copyright 2011 Page 6 of 10

7 1 About this Document 1.1 Introduction The Interoperability Toolkit (ITK) is an NHS led initiative that provides a series of standards for local integration. This includes providing system vendors with a target specification to build to, as well as providing a lightweight but rigorous conformance process which requires proof of compliance. The ITK also provides a governance framework for local NHS organisations to enact when using these standards. ITK provides a specification for the essential minimum necessary to ensure interoperability. This means that interfaces are specified in detail so that interoperability is governed by application purpose and function, as opposed to being rendered incompatible by proprietary interfaces. However detailed implementation is not specified. Indeed within the limits of enabling interoperability the specifications provide as much flexibility as possible for implementation choices. This minimises the barriers to entry for existing products, simplifies the compliance process, and enables suppliers to differentiate their products with innovative implementation approaches and additional features. Responsibility for locally detailed specification lies with the contracting organisation, as that is where the business drivers originate. By utilising ITK within that specification, whether directly or as a mediator, applications which are functionally compatible will remain interoperable, whilst reducing the need for complete system change. In order to realise the benefits that ITK offers, first of type projects utilising the ITK approach will share business intelligence and new specifications with the NHS community. Subsequent use of those specifications, where suppliers are compelled to use them, will then deliver both interoperability and cost saving. Crown Copyright 2011 Page 7 of 10

8 1.2 Background ITK is a Technology Office initiative arising from Christine Connelly's keynote speech at the British Computer Society Health Care Conference, 28 April In her speech, the Director General for informatics and Chief Information Officer for Health outlined her strategy for accelerating delivery of the National Programme for IT. At the heart of this strategy was a move from a replace all to a connect all approach and the ITK is a key enabler of this change. The ITK consists of the development and delivery of a set of technical standards and frameworks for interoperability, covering transactional and analytical services. 1.3 Purpose The purpose of this document is to provide a guide to the ITK-specific components that should be included in an Output Based Specification (OBS). This will empower Health & Social Care providers to specify ITK compliant systems from suppliers. 1.4 Audience This document is targeted at providers of Health & Social Care who wish to specify ITK compliant solutions. 1.5 Scope This document will provide text that can be used in constructing an OBS, but is not an OBS in itself. The recommendation will be to specify a level of ITK compliance locally that promotes scalable and therefore shareable results to the rest of the NHS community. 1.6 Not in Scope This document is neither a guide to writing an OBS, nor part of the ITK specifications themselves. Details that are specific to local projects are not included. 2 Specifying ITK Compliance Information about ITK, including Specifications, Accreditation and the Trust Operating Model, is available from the Terminology Reference Data Update Distribution Service (TRUD). Users will need to register and sign up for the correct 'release sub-packs'. Links to TRUD download pages are given on the registration page 1 1 TRUD registration Crown Copyright 2011 Page 8 of 10

9 2.1 Specify the version number The OBS should include direct reference to the ITK specifications and, where possible, the version number. Full details of the specifications are available to download from TRUD. The supplier will be accredited with the <latest version> of the ITK specifications. 2.2 Specify the required bundles Only those aspects of ITK specification that apply to the desired application need be applied. These aspects will be reflected in the accreditation against message bundles or services. Where known, these bundles may be specified in the OBS. Where specifications do not yet exist to meet functional business requirements ( first of type ), this needs to be raised formally, agreed and submitted through the ITK process. The supplier will implement ITK <system> specifications for <bundle><version no.> 2.3 Specify accreditation The OBS must specify that the solution should be accredited with the National Integration Centre and Assurance (NICA). The ITK accreditation process has been designed to be very straightforward and deliberately light touch, focusing very much on demonstrating technical conformance of the ITK interface against the relevant specifications and standards. In order to receive accreditation, a vendor must demonstrate the technical conformance of their product with the ITK requirements by submitting evidence of this conformance to CFH for review. This will be achieved through use of the ITK Testbench, along with completion of the Certification of Compliance to ITK requirements spreadsheets, and by providing supporting evidence. All of the relevant guidance documents, compliance spreadsheets and testing tools are available for download via TRUD. The Supplier will provide the Trust with certification of ITK NICA accreditation in this and any future releases of the offered solution or ITK specifications. In order to allow a supplier to plan costing for future ITK releases it may be reasonable to specify a time frame or number of releases the OBS should cover. ITK is currently released through TRUD every 6 months. 2.4 Specify interoperability Not only must an interface meet ITK specifications, it must also be interoperable with functionally similar interfaces, which are also ITK accredited, from any supplier. Crown Copyright 2011 Page 9 of 10

10 The supplier will ensure that any interface built to ITK specifications can connect to solutions of the Trust s choosing that are functionally similar and ITK accredited. 2.5 Specify assistance with the local framework The Trust Operating Model focuses on integration between Local Trust Systems and Spine Compliant systems, and also on integration between Local Trust Systems and / or Non-NHS Systems within a Local Health Community environment. The framework allows Trusts to define and control the level of assurance necessary to implement interoperable systems. For full details, see the ITK Trust Operating Model download from TRUD. Once the Trust Operating Model is locally defined, it rests with the local implementing Trust to enforce its use. The supplier will assist the Trust in undertaking an assessment of each interface it contracts to deploy under the Trust Operating Model. 2.6 Specify the required interface and fix costs One of the key benefits of ITK to the NHS community is the ability to share specifications and interoperable solutions. As a consequence there will be reduced development overheads for suppliers in subsequent deployments and it is reasonable to specify a fixed cost. The Supplier will, as part of its response, provide a fixed cost for additional implementations of each interface for which its product is accredited. 2.7 Ensure that the Supplier is in good standing regarding rights to use third party standards The ITK specifications incorporate licensed material, in particular HL7 standards. It is reasonable to require suppliers of interfaces that use licensed material to be acting legally in respect of such material, for example for use of HL7 standards, being members of HL7 (UK or International). 'The Supplier will, as part of its response, provide evidence of good standing in respect of rights to use third party standards used in the ITK interfaces for which its product is accredited.' Crown Copyright 2011 Page 10 of 10