-
Notifications
You must be signed in to change notification settings - Fork 3
/
news.php
258 lines (215 loc) · 19.1 KB
/
news.php
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
<?php include('includes/header.php') ?>
<div class="row">
<div class="col-md-8">
<h1 class="page-heading news-heading">News</h1>
<div class="news-list">
<div id="28apr">
<p class="news-title">INTEROPen Governance proposals from interoperability networks</p>
<p class="news-meta">28 April 2017 Amir Mehrkar</p>
<div class="news-text">
<p>
The following interoperability networks BCS, CCIO/CIO Network, C4H, HL7UK, IHE, NHS Digital, NHS England, NHS Hack Days, OpenEHR, PRSB and techUK have all joined INTEROPen, agreeing to its terms and conditions.
</p>
<p>
Discussions amongst leaders of these networks have led to the <a href="content/2017-04 INTEROPen Governance notes.pdf">following agreement</a>. INTEROPen members are encouraged to review and comment so we can progress the governance work and establish a new INTEROPen board to lead the interoperability standards work collaboratively.
</p>
</div>
</div>
<div id="14mar">
<p class="news-title">Request for Governance feedback</p>
<p class="news-meta">14 March 2017 Amir Mehrkar</p>
<div class="news-text">
<p>At the recent <a href="http://www.interopsummit.com">interopsummit</a> panel debate, it was announced that leaders of interoperability networks (C4H, HL7UK, techUK, PRSB, BCS, IHE, CCIO/CIO network, OpenEHR, NHS Digital, NHS England) have agreed to
work to establish how they can come together under an umbrella group called INTEROPen, whilst keeping the INTEROPen T+C/values/purpose/aims.
</p>
<p><a href="content/INTEROPen%20governance%20discussions.pdf">This is a request to the INTEROPen membership</a> for OPEN feedback – via the <a href="https://interopen.ryver.com/index.html#forums/1106270">RYVER GOVERNANCE FORUM CHAT</a> - on how our governance structure could evolve.</p>
<p>INTEROPen has been established for just over 1 year and continues to grow with organisations (vendor, provider, standards and clinical) joining weekly.</p>
</div>
</div>
<div id="27feb">
<p class="news-title">Request from INTEROpen to HL7UK</p>
<p class="news-meta">27 February 2017 Amir Mehrkar</p>
<div class="news-text">
<p>INTEROPen request a HL7UK ballot on the draft INTEROPen CareConnect profiles(extensions and valuesets)</p>
<p>Click <a href="content/INTEROPen%20to%20HL7%20UK%20CareConnect%20FHIR%20profile%20ballot%20request%20and%20response%20from%20HL7UK.pdf">here</a> for the full details. Discuss <a href=https://interopen.ryver.com/#posts/1281147> here </a>on RYVER</p>
</div>
</div>
<div id="12jan">
<p class="news-title">2017 Interop Summit Agenda</p>
<p class="news-meta">12 January 2017 Amir Mehrkar</p>
<div class="news-text">
<p>The Interop 2017 Summit agenda is now available <a href="https://docs.google.com/document/d/1-ZaZw5Y69cNigQ4iPb2pr6Qz4Ksp6Tf-anaCEfNaLsk/edit">here</a></p>
</div>
</div>
<div id="17jan">
<p class="news-title">Code4Health Interoperability Community Board (C4H CIB) - Response to "Emerging Target Architecture" paper</p>
<p class="news-meta">17 January 2016 Luke Readman, Chair C4H CIB</p>
<div class="news-text">
<p>Members of the C4H CIB responded to the <a href="content/Interoperability%20Summit%20-%20Emerging%20Target%20Architecture%20v1-0.pdf"> Emerging Target Architecture paper</a> by NHS England CIO, Will Smart. </p>
<p>Click <a href="content/Letter%20to%20Will%20Smart%20190117.pdf">here</a> for the paper. Discuss <a href=https://interopen.ryver.com/#posts/1249360> here </a>on RYVER</p>
</div>
</div>
<div id="16jan">
<p class="news-title">Code4Health Interoperability Community Board Briefing - FHIR Tooling</p>
<p class="news-meta">16 January 2016 Amir Mehrkar</p>
<div class="news-text">
<p>The Code4Health Interoperability Community Board endorsed this paper and its recommendations. FHIR tooling is not quite mature enough to drive the clinical engagement to help define clinical user requirements and use cases. This is an opportunity for members to share their initial thoughts on this paper. The NHS Digital team plans to initiate this in collaboration with community input. This should be an exciting project to help further popularise and engage clinicians and technician in FHIR.</p>
<p>Click <a href="content/C4H Briefing - FHIR Tooling v1.2.pdf">here</a> for the paper.</p>
</div>
</div>
<div id="29dec">
<p class="news-title">Interoperability and Population Health Summit: Emerging Target Architecture</p>
<p class="news-meta">29 December 2016 Will Smart, NHS England CIO</p>
<div class="news-text">
<p><a href="content/Interoperability%20Summit%20-%20Emerging%20Target%20Architecture%20v1-0.pdf">This is a paper</a> summarising the outputs from an Interoperability and Population Health Summit that was convened by Will Smart, NHS England CIO, in November 2016.</p>
<p>The purpose of the summit was to bring together national and international experts to explore the challenges associated with enabling data to flow across the health and social care system to support the provision of the best possible care to citizens.</p>
<p>The purpose of the target architecture paper is to explore the design of such a target architecture, to support the direction of travel to</p>
<ul>
<li>OPEN APIs (e.g. CareConnnect)</li>
<li>(Near) Real time data access for direct patient care</li>
<li>Near real time data access for analytics</li>
</ul>
<p>A key recommendation is that a target architecture (or platform for sharing) is at a regional level of populations from 2 to 5 million, adopting national standards (e.g. CareConnect), supported by national capabilities and integrated also with the emerging National Data Platform.</p>
<p>INTEROPen members are recognised stakeholders in providing feedback - please log in to RYVER for details on how to provide feedback by noon Monday 16th January.</p>
<p>Click <a href="content/Interoperability%20Summit%20-%20Emerging%20Target%20Architecture%20v1-0.pdf">here</a> for the paper.</p>
</div>
</div>
<div id="18dec">
<p class="news-title">FHIR Proof of Concept Evaluation Report</p>
<p class="news-meta">18 December 2016 Amir Mehrkar</p>
<div class="news-text">
<p>A key aim of this project was to support faster development of UK standards for the exchange of health and care information in FHIR, drawing on existing work nationally and internationally and collaborating with the interoperability community to bring a greater focus on implementation of the standards.</p>
<p>Click <a href="content/FHIR PoC Evaluation Report FINAL.docx">here</a> for the final report.</p>
</div>
</div>
<div id="19oct">
<p class="news-title">Developing Community FHIR Profiles (Webinar slides)</p>
<p class="news-meta">19 October 2016 Amir Mehrkar, Orion Health & Richard Kavanagh, NHS Digital</p>
<div class="news-text">
<p><a href="content/C4H%20-%20CareConnect%20Profiles%20V4%20Amir%20Richard.pdf">Click here to see the presentation given to the Code4Health Interoperability Community on Developing Community FHIR Profiles</a>.</p>
</div>
</div>
<div id="17oct">
<p class="news-title">INTEROPen October 2016 Newsletter</p>
<p class="news-meta">17 October 2016 Amir Mehrkar</p>
<div class="news-text">
<p><a href="content/2016%20October%20INTEROPen%20Newsletter%20Final.pdf">Click here to read the INTEROPen October 2016 Newsletter</a>.</p>
</div>
</div>
<div id="12sep1">
<p class="news-title">CareConnect candidate FHIR profiles online</p>
<p class="news-meta">12 Sep 2016 Amir Mehrkar</p>
<div class="news-text">
<p>NHS Digital and Endeavour Health have submitted FHIR profiles. They have been working together to agree convergence and these are published on our website at:</p>
<p><a href="http://interopen.org/candidate-profiles/convergence/">http://interopen.org/candidate-profiles/convergence/</a></p>
<p>EMIS and TPP have also been involved in the initial GPConnect FHIR profile work.</p>
<p><b><span class="red">ACTION FOR MEMBERS:</span></b> Please start using the Slack general channel for any discussion points on the profiles.</p>
</div>
</div>
<div id="12sep2">
<p class="news-title">PRSB clinical validation of FHIR profiles</p>
<p class="news-meta">12 Sep 2016 Amir Mehrkar</p>
<div class="news-text">
<p>The PRSB has been commissioned to provide a clinical validation review of the <a href="candidate-profiles/convergence/CareConnect-Problem-Condition-1.html">CareConnect–Problem–Condition candidate profile</a> over three workshops, with a view of reviewing the rest of the CareConnect profiles as they are published.</p>
<p>On Friday 23rd September 9-10.30 am we plan to have a <a href="events#cccpw">webinar discussion of the CareConnect candidate profiles</a> and to share any PRSB learning points.</p>
<p><b><span class="red">ACTION FOR MEMBERS:</span></b> Please email <a class="emaila" href="">.</a> if you are keen to be part of this webinar: you must review the profiles ahead of this to inform your contribution.</p>
</div>
</div>
<div id="12sep3">
<p class="news-title">Proposal for INTEROPen to “OPEN" its membership [HAVE YOUR SAY]</p>
<p class="news-meta">12 Sep 2016 Amir Mehrkar</p>
<div class="news-text">
<p>Since INTEROPen4 in July, a growing number of non-vendor organisations and individuals with valuable technical and clinical knowledge of the technologies we supply, and the standards needed to enable interoperability, have requested to contribute to INTEROPen’s important standards work.</p>
<p>Unfortunately, we have not been able to invite them to our membership. These include NHS provider and commissioner IT teams.</p>
<p>However, our mission statement makes it clear that we are here to work together to accelerate the development of open standards for interoperability, whilst putting commercial interests aside.</p>
<p>In addition, the recent report, <a href="https://www.gov.uk/government/uploads/system/uploads/attachment_data/file/550866/Wachter_Review_Accessible.pdf">Making IT Work</a>, chaired by Dr Robert Wachter, focused heavily on “interoperability”, specifically stating:</p>
<ul>
<li>"National standards for interoperability should be developed and enforced, with an expectation of widespread interoperability of core data elements by 2020”</li>
<li>"Widespread interoperability will require the development and enforcement of standards, along with penalties for suppliers, trusts, GPs, and others who stand in the way of appropriate data sharing."</li>
</ul>
<p>It, therefore, appears that the role of INTEROpen, is set to become an even more vital piece in the transformation of our NHS for safer and more efficient patient care.</p>
<p>As a result, <b>a proposal has been put forward that we OPEN our MEMBERSHIP to non-vendor organisations and individuals with technical and clinical expertise in health and social care interoperability standards development.</b></p>
<p><b>The proposal has been supported enthusiastically by the following members:</b></p>
<p>Blackpear, Cerner, Emis Health, Endeavour, Healthcare Gateway, IMS Maxims, InterSystems, Microsoft, Orion Health, TPP, including NHS Digital.</p>
<p><b><span class="red">ACTION FOR MEMBERS:</span> If you have any objection to this please contact us at <a class="emaila" href="">.</a> <span class="red">by 16/09/2016</span> with your justification, or use SLACK to discuss openly.</b></p>
<p><b>If no objections are raised we will open up the SLACK forum without delay and update our website and twitter feeds accordingly.</b></p>
</div>
</div>
<div id="12sep4">
<p class="news-title">Welcome Liam King, from Healthcare Gateway, to our PM team</p>
<p class="news-meta">12 Sep 2016 Amir Mehrkar</p>
<div class="news-text">
<p>Liam King has kindly volunteered to support INTEROPen’s work in a management capacity, helping to assist Paul Cooper from IMS Maxims.</p>
<p>We are delighted to have Liam's contribution to our community!</p>
<p><b><span class="red">ACTION FOR MEMBERS:</span> If you have capacity to support our work, please get in touch at <a class="emaila" href="">.</a></b></p>
</div>
</div>
</div>
<h1 id="media" class="page-heading news-heading">In the media</h1>
<div class="news-list">
<div id="05jan">
<a class="news-title" href="http://www.healthdatamanagement.com/news/2017-emerges-as-pivotal-year-for-fhir-interoperability-standard">2017 emerges as pivotal year for FHIR interoperability standard</a>
<p class="news-meta">05 Jan 2017 healthdatamanagement.com</p>
<p class="news-summary">Health Level Seven International’s Fast Healthcare Interoperability Resources (FHIR) application programming interface is moving closer to becoming a mature standard, with the “normative” version slated for release sometime in 2017.</p>
</div>
<div id="3nov">
<a class="news-title" href="http://www.digitalhealth.net/infrastructure/48240/ade-memoire:-all-mod-cons">Ade Memoire: all mod cons</a>
<p class="news-meta">3 Nov 2016 digitalhealth.net</p>
<p class="news-summary">In 1998, Adrian Byrne's trust decided the future was the web. The modern world says it was right, the world of healthcare software that it was wrong. Now, he's got the private hell of deciding where to go on mobile...</p>
</div>
<div id="6sep">
<a class="news-title" href="http://www.digitalhealth.net/integration/48036/calling-the-fhir-brigade">Calling the FHIR brigade</a>
<p class="news-meta">6 Sep 2016 digitalhealth.net</p>
<p class="news-summary">Philip Scott, a senior lecturer in information systems at the University of Portsmouth, and chair of HL7 UK, discusses the evolution of the HL7 FHIR standard, some projects in which it is already being used in the NHS...</p>
</div>
<div id="17aug">
<a class="news-title" href="http://www.digitalhealth.net/cio/47975/ade-">Ade Memoire: how long?</a>
<p class="news-meta">17 Aug 2016 digitalhealth.net</p>
<p class="news-summary">Adrian Byrne, the director of informatics at University Hospital Southampton NHS Foundation Trust, wonders whether five years is enough to realise the government’s ‘paperless’ vision. Barely, if a trust has yet to do order comms, e-prescribing, and information sharing, he reckons....</p>
</div>
<div id="15aug">
<a class="news-title" href="https://www.england.nhs.uk/2016/08/tracey-grainger-5/">Fantastic digital developments as we aim to go paperless</a>
<p class="news-meta">15 Aug 2016 england.nhs.uk</p>
</div>
<div id="23jun">
<a class="news-title" href="http://www.buildingbetterhealthcare.co.uk/news/article_page/INTEROPen_accelerates_development_of_NHS_interoperability_standards/118951">INTEROPen accelerates development of NHS interoperability standards</a>
<p class="news-meta">23 Jun 2016 buildingbetterhealthcare.co.uk</p>
<p class="news-summary">Twenty-nine industry-leading organisations have come together to create INTEROPen, a supplier action group aimed at accelerating the development of open standards for interoperability in the health and social care sectors...</p>
</div>
<div id="20jun">
<a class="news-title" href="http://tech.newstatesman.com/big-data/qa-nhs-england-open-data">Q&A: NHS England’s new drive for open data standards in healthcare</a>
<p class="news-meta">20 Jun 2016 tech.newstatesman.com</p>
<!--<p class="news-summary">Speaking this week at the NHS Confederation’s annual conference, Stephen Dorrell, the organisation’s chair, said: “To improve the standard of care that we deliver to people we must better integrate our health and social care services.”...</p>-->
</div>
<div id="14jun">
<a class="news-title" href="http://www.governmentcomputing.com/news/uk-health-authorities-back-supplier-it-interoperability-group-4922630">UK health authorities back supplier IT interoperability group</a>
<p class="news-meta">14 Jun 2016 governmentcomputing.com</p>
<p class="news-summary">INTEROPen action group is expected to build on NHS England's work around developing technology and data standards to help meet wider care transformation aims...</p>
</div>
<div id="27may">
<a class="news-title" href="https://isthereafuture.wordpress.com/being-interopen-care-coordination-is-not-an-option-for-providers-and-footprints/">Being INTEROpen Care-Coordination is not an Option for Providers and Footprints...</a>
<p class="news-meta">27 May 2016 isthereafuture.wordpress.com</p>
</div>
<div id="24may">
<a class="news-title" href="http://www.digitalhealth.net/integration/47724/interopen-supplier-group-launched-to-promote-open-standards">INTEROpen supplier group launched to promote open standards</a>
<p class="news-meta">24 May 2016 digitalhealth.net</p>
<p class="news-summary">A supplier-led interoperability group has been launched to promote the exchange of data across healthcare through the adoption of open standards.</p>
</div>
<div id="1may">
<a class="news-title" href="http://interoperability.code4health.org/2016/05/01/latest-newsletter-published/">INTEROPen accelerates development of NHS interoperability standards</a>
<p class="news-meta">1 May 2016 interoperability.code4health.org</p>
</div>
<div id="29apr">
<a class="news-title" href="http://www.techuk.org/insights/news/item/8393-call-for-action-interoperability-implementation-at-scale-interopen">Call for Action: Interoperability Implementation at Scale (INTEROPen)</a>
<p class="news-meta">29 Apr 2016 techuk.org</p>
</div>
</div>
</div>
<div class="col-md-4">
<h1 class="news-heading">Tweets</h1>
<a class="twitter-timeline" data-width="400" data-height="800" href="https://twitter.com/INTEROPenAPI" data-chrome="noheader nofooter"></a>
</div>
<script async src="http://platform.twitter.com/widgets.js" charset="utf-8"></script>
</div>
<?php include('includes/email.php') ?>
<?php include('includes/footer.php') ?>