8:30 am Doors open, registration, coffee
9:00 am Rachel Dunscombe: Welcome
9:15 am Ewout Kramer: An introduction to FHIR
In his keynote Ewout Kramer, one of the three founders of the FHIR standard, explains the origins of FHIR, why it is there, how it fits in the API economy, how FHIR is already changing the healthcare IT space, what’s going on right now with FHIR around the world and what lies ahead. After Ewout’s talk there will be room for Q&A.
10:15 am Break
10:45 am Calvin Beebe, Chris Grenz: The hospital approach: FHIR at Mayo Clinic
In an early adoption of FHIR, Analysts and Mayo Clinic partnered to build a platform capable of integrating any clinical data found in the Mayo Clinic enterprise. Using FHIR as a centerpiece, this platform is in-production as a Clinical Registries System for clinical analytics in specialty practice.

Moving forward, Mayo has established an Enterprise FHIR infrastructure on top of a Unified Data Platform (UDP) to provision the Registries System, enable a Historical Data Viewer application and form the basis of its future FHIR based innovation. Chris and Calvin will share their implementation experience and Mayo’s future directions in terminology, systems architecture, and organizational alignment, and their collaboration with HL7 and the FHIR community.

11:45 am Niklas Svenzén: Clinical views through FHIR widgets
As a downstream HL7 system the norm is that you can only display what you are fed. To be able to provide the end user with a richer set of informatics tools, as a vendor you are faced with the constant struggle to either expand your applications information model, go proprietary, or to restrict the user to launch into another application for additional data.

With the introduction of FHIR a new world of possibilities for standards based integration is opening up to provide the end user with a much tighter integration with applications higher up in the food chain. In his talk, Niklas will elaborate on some of the areas where Sectra as a diagnostic imaging vendor has seen a great interest from its customers with regards to the adoption of FHIR based integrations.

12:30 am* Lunch
1:30 pm Richard Kavanagh: FHIR policy and projects at NHS Digital
NHS Digital has recognized the potential of FHIR at a very early stage. Richard Kavanagh’s team at NHS Digital runs several FHIR projects at the moment and collaborates with other stakeholders on national FHIR profiles and tooling. In his speech Richard dwells on the FHIR policy and FHIR projects of NHS Digital and the relevance of these efforts to the NHS trusts.
2:15 pm Gary Leeming: Creating slipstreams of care: How interoperability will transform our health services
Building on learning within Greater Manchester across care and research Gary Leeming will present on the work of the DataWell and Connected Health Cities programs, and how using standards accelerates how we can improve care.
3:00 pm Break
3:30 pm Rachel Duncscombe: Panel Discussion
The speakers of the event are being questioned by Rachel and by the room.
4:30 pm Drinks
5:30 pm Doors close

* Those who registered for the training courses have a separate programme in the afternoon:

1:30-4:30 pm Mirjam Baltus: Workshop FHIR for Developers
Mirjam provides a crash course FHIR for Java and/or C# Developers, which is a condensed version of the two-day FHIR training Mirjam has given numerous times throughout Europe. Bring your laptop and favorite IDE.

Required knowledge: FHIR none, software development skills, preferably familiar with healthcare information exchange and HL7.
Note: limited access; first come, first served; NHS Trust employees have precedence.

1:30-4:30 pm Michel Rutten: Tutorial FHIR for Specifiers
In this tutorial Michel explains the principles of FHIR profiling, the conformance resources involved in profiling, the tools to be used, the why and how of Implementation Guides and what’s new in FHIR STU3.
Required knowledge: FHIR none, preferably familiar with healthcare information exchange and HL7.
Note: limited access; first come, first served; NHS Trust employees have precedence.