1. Technical Perspectives Mat Jordan Steve Anderson

2. Current situation - 1 SCR will not be available for CAF messages within the lifetime of the programme No national NHS systems will be CAF enabled within the lifetime of the CAF programme* Without end-to-end systems, National Integration Centre (NIC) will not give priority to CAF messaging projects Full CAP is still required for point-to-point messaging through the Spine using TMS (a lighter CAP may be available but not for 6+ months) * There is still a possibility that TPP System 1 might be CAF enabled before March 2012.

3. Current situation – 2 GCSX / N3 Gateway is available – no need for IGSoC and separate N3 connection Specifications for all CAF messages are now available (assessment & care planning, delayed discharge and continuing healthcare assessment) All CAF messages are now ‘universal’ so can be sent by non-Spine transport mechanisms Spine can still be used for point-to-point messaging between systems using the Transaction Messaging Service (TMS) DH Technology Office have agreed to provide additional support for local messaging

4. Options Build point-to-point CAF messaging functionality based on Spine / TMS Look at local messaging options Interoperability toolkit (ITK) Data Transfer Service (DTS) NHS Mail Locally agreed interface

5. Point-to-point via Spine Both health and social care systems are required that can be CAF enabled in time: Already PDS enabled or well on the way Ready to start CAP for CAF messaging soon Functionality could possibly be built at risk for future use

6. Interoperability Toolkit Standardised web service-based interface between two systems Requires local assurance Purported to enable rapid development Technology Office have agreed to support this But: Still requires both NHS and social care systems that can be upgraded in time Does not yet include social care messages Assurance process for social care not yet defined

7. Email / DTS Crude but effective mechanisms for sharing information between organisations Cheap and widely available But: Unsophisticated Requires careful management Partial solution – may be first step towards better sharing

8. Other local interfaces Locally agreed point-to-point interfaces between systems using Universal CAF messages Agreed standards for interoperability Agreed between supplier and customers Agreed across all interested CAF sites? Ownership and maintenance of standards would need to be agreed Local assurance processes would need to be developed and agreed How can replicability be supported?

9. Key questions for sites What can be achieved locally within the demonstrator timescales 1.What tactical solutions are possible? 2.What would make sense as part of a longer term strategy? 3.What, if any, messaging requirements do you envisage (dates of build and test)? What standards will be required? What existing standards are appropriate (e.g. NHS Number)? Is a Demonstrator-wide standards group required? What support will be required from DH / CFH / Others?

10. Next steps Technical roadmap: Clear technical scope for each site Short term and long term options Informed by meetings / workshops Support requirements from DH / CFH / Others Standards – cross site agreement on standards