-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathspine_nhs_overview.html
260 lines (238 loc) · 11 KB
/
spine_nhs_overview.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Spine and NHS Digital - Overview</title>
<meta name="description" content="A walk-through of the history of the major NHS programmes">
<meta name="author" content="Martin Sumner">
<meta name="apple-mobile-web-app-capable" content="yes" />
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no, minimal-ui">
<link rel="stylesheet" href="css/reveal.css">
<link rel="stylesheet" href="css/theme/black.css" id="theme">
<!-- Code syntax highlighting -->
<link rel="stylesheet" href="lib/css/zenburn.css">
<!-- Printing and PDF exports -->
<script>
var link = document.createElement( 'link' );
link.rel = 'stylesheet';
link.type = 'text/css';
link.href = window.location.search.match( /print-pdf/gi ) ? 'css/print/pdf.css' : 'css/print/paper.css';
document.getElementsByTagName( 'head' )[0].appendChild( link );
</script>
<!--[if lt IE 9]>
<script src="lib/js/html5shiv.js"></script>
<![endif]-->
</head>
<body>
<div class="reveal">
<!-- Any section element inside of this container is displayed as a slide -->
<div class="slides">
<section>
<blockquote cite="http://www.independent.co.uk/voices/commentators/oliver-wright-the-potential-was-huge-but-so-were-the-problems-2330925.html">
“The possibilities are enormous if we can get this right”
</blockquote>
</section>
<section>
<h2>Overview</h2>
<p align="left">Brief history, overview of structure</p>
<p align="left">Focus on evolution of national services - Spine</p>
<p align="left">Current positives</p>
<p align="left">Current constraints</p>
</section>
<section>
<h2>Brief History</h2>
<p align="left">pre-2003 - local spend increasing, limited integration</p>
<p align="left">2003 - contract five local service providers (LSPs) and national services (NASPs)</p>
<p align="left">2006 - existing providers fill gaps from LSPs</p>
<p align="left">.... LSPs suffer on appetite for change management, and technology delays</p>
<p align="left">2012 - expensive success in NASPs, costly failure in LSPs</p>
<p align="left">2016 - bespoke NASPs move in-house, commodity NASPs re-contracted, LSPs wound down</p>
</section>
<section>
<h2>Brief History - Benefit Realisation</h2>
<p align="left">2012 National Audit Office review - expected benefit realised</p>
<p align="left">Commodity services (e.g. network, mail, PACS) - 80% to 95%</p>
<p align="left">Bespoke national infrastructure (i.e. NASPs) - 69% to 72%</p>
<p align="left">Change programmes enabled by NASPs - 2% to 47%</p>
<p align="right">....Note that volume on Spine has nearly trebled since 2012</p>
<p align="left">Bespoke local services (i.e. LSPs) - 2% to 14%</p>
</section>
<section data-background="#A3C2FF">
<h2>NASP Success Story - Spine</h2>
<p align="left">Split between:</p>
<ul>
<li><p align="left">Core - the big volume heart of the Spine</p></li>
<li><p align="left">Identity - authentication, authorisation of professionals</p></li>
<li><p align="left">Secondary Use - focused on tariffing for secondary care</p></li>
</ul>
</section>
<section data-background="#A3C2FF">
<h2>NASP Success Story - Spine Core </h2>
<p align="left">Services supported:</p>
<ul>
<li><p align="left">Electronic Prescriptions (Primary Care)</p></li>
<li><p align="left">Demographics</p></li>
<li><p align="left">Summary Care Record</p></li>
<li><p align="left">Consent and subject access alerting, reporting and analysis</p></li>
<li><p align="left">GP2GP, eReferral, Pathology messaging</p></li>
</ul>
</section>
<section data-background="#A3C2FF">
<h2>Spine Core - History</h2>
<p align="left">to 2005 - Fast delivery, questions over stability</p>
<p align="left">to 2008 - Slow and expensive expansion, 2000 people</p>
<p align="right">... issues with incentives to use</p>
<p align="left">to 2013 - Availability/Scale at high cost ... </p>
<p align="right">... with functional lock-down</p>
<p align="left">2014 - transition to solution re-engineered in-house</p>
<p align="left">to 2017 - Availability/Scale at low cost ... </p>
<p align="right">... now with rapid functional evolution</p>
</section>
<section data-background="#A3C2FF">
<h2>Spine Core - The In-House Solution</h2>
<p align="left">Took <strong>100 man years</strong> from inception to 1-years service</p>
<p align="left">Requires just over <strong>100 commodity 1RU servers</strong> in live</p>
<p align="left">Release costs are <strong>< 0.1%</strong> of previous release costs</p>
<p align="left"><strong>90%</strong> reduction in operating costs</p>
<p align="left">Total running team of <strong>35</strong> people supporting and ...</p>
<p align="left">... Managing more than <strong>£10m</strong> pa of change backlog</p>
</section>
<section data-background="#A3C2FF">
<h2>Spine Core - The In-House Solution</h2>
<p align="left">(Nearly) like-for-like functional replacement ...</p>
<p align="left"><strong>99.999%</strong> available since go live</p>
<p align="left">Supports over 300 message interactions, five UI applications</p>
<p align="left"><strong>43M</strong> messages a day<p>
<p align="left">Provides accesss to <strong>2bn</strong> records and documents</p>
<p align="left">The NHS waits more than <strong>1,000 working days less</strong> each day</p>
</section>
<section data-background="#A3C2FF">
<h2>Spine Core - The Change in Approach</h2>
<p align="left">Technology - learn the lessons of Google etc</p>
<p align="left">Contractual - accept risk, make incentives natural</p>
<p align="left">Management - embrace Agile/LEAN ethos</p>
<p align="left">Operations - a consistent response to failure<p>
<p align="left">Delivery - automation everywhere</p>
<p align="left">People - focus on value, not unit cost</p>
<p align="left">Architecture - continuous improvement in simplicity</p>
</section>
<section data-background="#A3C2FF">
<h2>Spine Core - The Change in Approach</h2>
<p align="left">Bending on the previous principles has led to reduced success</p>
<ul>
<li>Identity Services - operational cost, opportunity cost</li>
<li>eReferrals - go-live stability, operational cost</li>
</ul>
<p align="left">There exists continuous pressure to bend on principles</p>
</section>
<section data-background="#E6E68A">
<h2>Current Positives</h2>
<p align="left">Flexibility at scale</p>
<ul>
<li>Reduce the cost of experiment</li>
<li>Reduce the fear of success</li>
</ul>
<p align="left">Growth without incentives</p>
<ul>
<li>Volumes doubled, systems reach 100% reach</li>
<li>Suppliers cannot retreat to blaming the centre</li>
</ul>
<p align="left">Symbiotic success</p>
<ul>
<li>EPS penetration ... eases transition of SCR to pharmacy</li>
<li>PDS penetration ... eases transition to eReferrals</li>
</ul>
</section>
<section data-background="#E6E68A">
<h2>Current Positives</h2>
<p align="left">Evolving standards</p>
<ul>
<li>Adding HL7 FHIR, plus other RESTful services</li>
<li>Maintaining legacy interfaces at low cost</li>
</ul>
<p align="left">Platform Extensibility</p>
<ul>
<li>Zero change to Spine operational cost for new applications</li>
<li>Now looking at broader integration, public-facing services</li>
<li>Landing of M&V, PCRM, FGM, CPIS, DTS, NOOM onto Spine Core ... add an app per quarter</li>
<li>Same patterns/teams/approach driving Flu Pandemic Service, SUS+ etc</li>
</ul>
</section>
<section data-background="#E6E68A">
<h2>Current positives</h2>
<p align="left">Integration complexity improvements</p>
<ul>
<li>Consistency of response time vital at centre</li>
<li>Spine as a point of triage truth</li>
<li>Spine adding layers rather than suppliers adding layers</li>
<li>The slow process of validation enforcement ... legacy of history means Spine complexity for bad data handling</li>
</ul>
<p align="left">Identity</p>
<ul>
<li>Migrating from model dependent on smartcards</li>
<li>Need to be mobile friendly</li>
<li>Emerging options for identifying citizens</li>
</ul>
</section>
<section data-background="#E6E68A">
<h2>Current Challenges</h2>
<p align="left">Culture catch-up</p>
<ul>
<li>People & processes wedded to predictions</li>
<li>People & processes wedded to slow speed of change</li>
</ul>
<p align="left">System depends on customer-systems</p>
<ul>
<li>Customer-systems not engineered to same standard</li>
<li>Customer-systems not fast to change</li>
</ul>
<p align="left">Legacy of LSP failure</p>
<ul>
<li>Fear of national initiative</li>
<li>as pre-2003 - local spend increasing, limited integration</li>
</ul>
</section>
<section data-background="#E6E68A">
<h2>Current Challenges</h2>
<p align="left">Summary Care Record may not be the answer</p>
<ul>
<li>Investigating Record Locator service</li>
<li>Investigating GP system connector</li>
<li>... but perhaps SCR is under-appreciated</li>
</ul>
<p align="left">Hard to drawback the legacy of necessary assurance</p>
<ul>
<li>Assurance <b>used to</b> protect the service</li>
</ul>
<p align="left">Centralisation and fear</p>
<ul>
<li>Security, safety and consent under the microscope</li>
</ul>
</section>
</div>
</div>
<script src="lib/js/head.min.js"></script>
<script src="js/reveal.js"></script>
<script>
// Full list of configuration options available at:
// https://github.com/hakimel/reveal.js#configuration
Reveal.initialize({
controls: true,
progress: true,
history: true,
center: true,
transition: 'slide', // none/fade/slide/convex/concave/zoom
// Optional reveal.js plugins
dependencies: [
{ src: 'lib/js/classList.js', condition: function() { return !document.body.classList; } },
{ src: 'plugin/markdown/marked.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
{ src: 'plugin/markdown/markdown.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
{ src: 'plugin/highlight/highlight.js', async: true, condition: function() { return !!document.querySelector( 'pre code' ); }, callback: function() { hljs.initHighlightingOnLoad(); } },
{ src: 'plugin/zoom-js/zoom.js', async: true },
{ src: 'plugin/notes/notes.js', async: true }
]
});
</script>
</body>
</html>