Program

Opening

More about James Agnew

FHIR Introduction
This tutorial provides a brief introduction and overview of the FHIR specification. We will examine the basic concepts of FHIR resources and supported interoperability paradigms. An instructor led demo will illustrate a FHIR-in-action scenario. If you are new to FHIR, this is a great place to start.

More about Simone Heckmann

Let's Build! A FHIR Client with Java
During this session, we will explain several parts of the API. Code examples will be provided for creating resource instances, sending requests to servers and inspecting the responses. And you will be able to build your first FHIR client together with us!

More about James Agnew

Let's Build! .NET FHIR Library
Come and build your first FHIR client together with us! Using the FHIR .Net API library, we will create a simple FHIR client that retrieves a Patient resource from a FHIR server. Next we can change some details in the Patient data and send the updated resource to the server again. After these first steps, we will create a search query and look at the server’s response.

More about Mirjam Baltus

Developing FHIR Applications in the Microsoft Azure Cloud
Microsoft offers both an open source FHIR server and a managed FHIR service in the cloud. This tutorial focuses on the tools that are available to accelerate your development of FHIR applications in the cloud. We will demonstrate how FHIR applications can be built on managed platform services that allow you to focus on the code you are writing while leaving the operations and management tasks to the cloud provider. The tutorial will show the basic steps of deploying a FHIR API, patient dashboard applications, data analysis pipelines, SMART on FHIR apps and more. Scripts and templates will be provided to allow attendees to provision their own environments after the tutorial.

More about Michael Hansen

A new phenomenon at DevDays is the Patient Innovator Track. This track shows that patients can and should be the ultimate beneficiaries of FHIR. The Patient Innovator Track provides a stage to patients who have taken control of their health by using the data of their disease and their treatment, or app developers who enable patients to do so.

The following finalists will present their achievement:
- BloodNumbers – Track Your Blood Counts
John Keyes
- Using Readily Available Health Monitoring Devices To Track And Report Real-Time Symptoms
Brenda Denzler
- Solved Interoperability Through Patient Centricity
Ardy Arianpour, Seqster
- Health 29 – Interoperable Data Platform For Rare Disease Patients
Francisco Javier Logrono, Foundation 29

Methods for transforming content from V2 and CDA to FHIR and vice versa
Almost everyone implementing FHIR starts with information that already exists in another format; this information must be converted to (and from) the FHIR resource format. Of particular interest to the HL7 community is content in V2 messages and Clinical Document Architecture (CDA) documents. Grahame will describe the facilities built into FHIR that can be used to convert between the formats and also look at other tools and community projects that do the same. Mantra: mapping should not be a solitary activity.

More about Grahame Grieve

Health Records on iOS
Learn how to integrate the Health Records API into your health app on iOS. Get your questions about the feature answered by Apple engineers.

Let’s Build using Health Records on iOS!
Learn how to integrate the Health Records API into your health app on iOS. Discuss your apps and integrations with Apple engineers. Please bring your Mac with Xcode installed to get the most out of this session!

Requirements
MacOS 10.14+
Xcode 10.0+

Managing Multiple FHIR Versions
There have been three major releases of FHIR and the production of FHIR systems are spread across releases R2, R3 and R4. Grahame will discuss the features in the FHIR specification itself that relate to supporting multiple versions and will describe some of the major implementation decisions relating to which version(s) to support.

More about Grahame Grieve

Data Privacy in AI using Federated Learning on FHIR
Will Federated Learning reconcile machine learning and data privacy? This talk describes this emerging machine learning technique, which enhances data privacy, and presents a FHIR-based implementation in three French hospitals.

Interoperability, which is at the heart of FHIR, allows health data to be shared across multiple healthcare facilities to improve patient care. It also provides a guarantee on data formatting when services or algorithms access it. Rich standards such as FHIR allow a single model to be trained on multiple local health datasets.
This is the core principle of Federated Learning, a state-of-the-art technique to train Machine Learning models where health data is not uploaded to the cloud or a central server but is stored locally in healthcare facilities and only the model is shared. This improves data confidentiality and facilitates large scale analyses that are particularly needed to study disease evolution and drug toxicity.

We will describe how FHIR and Federated Learning help solving real life problems by training and evaluating Deep Learning models using common frameworks such as PyTorch and TensorFlow in a federated manner while preserving patient privacy. We will share our feedback on our research projects in French hospitals using Arkhn's open-source tools.

More about Thomas Walter

Flicker or Bonfire – How Design Choices Affect FHIR’s Power
FHIR is very popular because of its promise of faster/cheaper/more interoperable. As well, FHIR provides alot of design options to ensure that it can be used in the broadest possible group of settings. However, the design choices you make can make a significant difference around how much of the faster/cheaper/more interoperable promise will actually be delivered. As well, sometimes the FHIR solution that's fastest/cheapest for the one writing a FHIR specification isn't necessarily fastest/cheapest/most interoperable for the community at large. The presenter will identify design choices that can undercut FHIR's power and describe the alternatives that may take more work or require a shift in thinking up front, but will lower costs and increase uptake in the long term.

More about Lloyd McKenzie

FHIR Documents
FHIR Documents, next to REST, is the most commonly used exchange mechanism for FHIR resources. This tutorial will help you understand the core characteristics of a FHIR Document, the need to balance the use of narrative versus the use of structured data, when to use FHIR Documents rather than any of the other FHIR exchange mechanisms, as well as a brief overview of the relationship with the HL7 CDA standard.

More about Rene Spronk

FHIR Introduction (repeated session)
This tutorial provides a brief introduction and overview of the FHIR specification. We will examine the basic concepts of FHIR resources and supported interoperability paradigms. An instructor led demo will illustrate a FHIR-in-action scenario. If you are new to FHIR, this is a great place to start.

More about Simone Heckmann

Building a sustainable SMART on FHIR test environment that is NL-Ready!
During this presentation, Michael will present the approach, plans and experiences so far regarding building a sustainable SMART-on-FHIR environment, called the Virtual Hospital Environment. This environment is configured for the Dutch specific situation.
We will build on the shoulders of giants. To achieve this we took the open source SMART-on-FHIR sandbox from SmartHealthIT and populated it with Dutch specifications from e.g. Nictiz, the Dutch center for expertise for eHealth, and with actual representative datasets.
Participants can take our approach and experience and copy it to their realm specific situation and can learn how to use the sandbox in their day job.
The greater goal is to help developers from small and medium businesses, not just healthcare specific, get up-to-speed with FHIR and SMART. Resulting in tested apps that are properly using the open standards so that they can be deployed seamlessly in any healthcare real world situation, such as a hospital EHR.

More about Michael van der Zel

FHIR Facade Building
In a perfect world, there is a 100% match between the specification for the FHIR resources that you want to expose from an existing application and the (internal) data model for and capabilities of that application. In real life, you will probably find it much harder to create a proper FHIR façade for an existing application. During this presentation, we will look into issues you might face and provide guidelines on deal with these. We will discuss and give examples of:
1. Which resources do you need / want to expose?
2. How to find the right resource that match your existing data?
3. Strategies for dealing with imperfections in resource mapping
4. Which interactions should you support?
5. Search with filtering, sorting, paging, chained parameters, _include and _revinclude
6. Strategies for create and update
7. Dealing with references and referential integrity
8. Dealing with concurrency using resource versioning
9. Dealing with transactions and batches
10. Setting up the CapabilityStatement
11. Use of profiles
12. Dealing with API security and authorization


More about Theo Stolker

FHIR Profiling Overview
In this session you will get a broad overview of the FHIR conformance layer and its principal components, such as profiles, extensions and implementation guides, and learn about its benefits and capabilities. We will explain collaborative authoring and publication workflows, discuss related concepts such as FHIR registries, package management and versioning and introduce available tooling.

More about Mirjam Baltus

Argonaut Provenance Collaboration
US regulation is proposing to add new required data elements for exchange (USCDI United States Core Data for interoperability). One of the data elements being proposed in exposing author information. This has posed interesting challenges for representing this data in an interoperable manner, and what author data elements mean in the context of healthcare. Argonaut is focusing on defining profiles for provenance on how to expose authors and custodians. The presentation would be to discuss the decisions being made, solicit feedback, and to discuss some of the difficult conversations occurring.

More about Yegor Hanov

FHIR Profiling - Changes since FHIR R4
This session presents the important/subtle changes in the profiling layer introduced by FHIR R4, including:
o Changed: Canonical references
o Changed: Element type profiles
o Changed: Type slicing
o New: ElementDefinition.sliceIsConstraining
o Changed: StructureDefinition.context


More about Grahame Grieve

FHIR Resources for Medication Definition
EMA and FDA are extending FHIR for their upcoming SPOR and PQ/CMC projects. Prepare for those by exploring the new Medication Definition set of resources. These cover the scope of IDMP and regulatory information for the Pharmaceutical industry and will form the next generation of drug submission in Europe.

More about Rik Smithies

Introduction to DICOM for Imaging and its FHIR integration
This session provides a formal introduction to DICOM for medical imaging. The session then proceeds to explore how DICOM integrates with FHIR to compliment the patient record. It will cover basic interactions with FHIR and DICOMweb to query for and retrieve images.

More about Mohannad Hussain

FHIR Projects
This session consists of two community presentations, which focus on the implementation of best practices of their project/product. These presentations are NOT a product showcase - the aim is to have max. 5 minutes to introduce a product/project, followed by a deep dive in things like the architectural approach, tools used, good/bad experiences with FHIR. The aim is for software implementers (even if they're not using the same architecture nor development platform) to learn from the development approach as used in other projects.

Time: 16:00-16:20
Using FHIR to Operationalize Genome Sequencing in the English National Health Service
The 100,000 Genome Project sequenced genomes from around 85,000 NHS patients affected by a rare disease or cancer. Although primarily a research project, actionable findings were found in 1/4 in 4/1 in 5 rare disease patients, and around 50% of cancer cases contained potential for therapy or a clinical trial. Transitioning from a research-driven project to create a Genomic Medicine Service offering genome sequencing as a mainstream test has required mapping new services to existing flows and replacement of bespoke interfaces with FHIR messaging.
Speaker: Aled Greenhalgh, Answering Digital

Time: 16:20-16:40
Implementing and Extending FHIRCast Brief Description
Three big players in the medical software industry have recently started collaborating on implementing and where necessary extending the evolving FHIRCast specification for near-real-time clinical context sharing and tight integration between EMR, Imaging and Reporting systems. Although the journey has just begun, there are already plenty of valuable experiences to share.
Speaker: Arpad Metzing, Evosoft

FHIR Projects
This session consists of a community presentation, which focuses on the implementation of best practices of their project/product. These presentations are NOT a product showcase - the aim is to have max. 5 minutes to introduce a product/project, followed by a deep dive in things like the architectural approach, tools used, good/bad experiences with FHIR. The aim is for software implementers (even if they're not using the same architecture nor development platform) to learn from the development approach as used in other projects.

Time: 16:50-17:10
A FHIR-Based Platform for FHIR Training
CENS (Chile) has created an interoperability Platform (API) to support FHIR training. The training platform has a decoupled MVC architecture, which is organized with an administrator for the creation training activities, an evaluation engine (API developed on top of the HAPI-FHIR library) which evaluates the CRUD operation (a Request/Response pair from a HAPI-FHIR or VONK server) and the web client (where the student accesses a visualization of the test with a description and feedback from the evaluation engine). With this platform, one can create, modify, run and evaluate FHIR based exercises.

More about Sergio Guinez-Molinos

Devices on FHIR ... everywhere!
Devices are ... everywhere! From the operating room to the enterprise to home & mobile applications. And now regulated Software as a Medical Device (SaMD) AI / Machine Learning software tech + Health & Wellness Apps quality standards are all converging to impact device-related informatics and interoperability ... everywhere! Even the meaning of a "device" is increasingly challenging to nail down. At the same time, HL7, IHE Devices & PCHA "Continua" are working together at a new level. Devices on FHIR is at the forefront in addressing these challenges, especially when coupled with Service-oriented (WS-*) Device Connectivity (SDC) for the toughest high risk applications.

More about Todd Cooper

FHIR for Clinicians
This presentation is an introduction to FHIR for the clinical and business user. We'll talk about what FHIR is, why it was developed and the benefits that it brings to clinicians and others. We'll talk about the main parts of FHIR - resources, connections between resources and terminology as well as touching on profiling - making FHIR work for you! The objective is to prepare a clinician for participating in FHIR related projects.

More about David Hay

Let's Build! Modeling a Clinical Scenario
This session follows from the introduction and uses freely available tooling--clinFHIR--to build collections on resources that represent real clinical scenarios. We'll start with a short demonstration, then it's hands on! There will be a number of scenarios to choose from and you'll be able to continue your work after the session -- and, indeed, after the event. You'll need a computer with a modern browser (we recommend Chrome) and a desire to learn!

More about David Hay

Use Cases to FHIR – a Pragmatic Modeling Approach
Picture this: You're the only engineer in room with 20 clinicians and now you need to create a FHIR IG that captures their problems and needs. What do you do?
A good approach for translating clinical speak to technical terms is not always clear, and there's little guidance on how an implementer can create a FHIR model in a way that speaks to clinicians also keeps them engaged throughout the process.

This presentation will step the audience through a tested and implemented process which starts with a clinical use case, derives its clinical data requirements, creates the conceptual model, and presents an approach to translate it to a resulting FHIR logical model. The process will be shown with an actual example of how it was applied for creating the minimum Common Oncology Data Elements (mCODE) FHIR model. A process toolkit which includes the templates used for capturing and translating clinical data requirements will be provided.

More about May Terry

How and When to Use FHIR Terminology Service APIs
This talk will present the FHIR Terminology Service, starting with the different usage scenarios for using it – from clinical data entry, to analytics, to authoring your own terminology resources, including defining terminology bindings for profiles and implementation guides, to integrating terminology when building other kinds of FHIR servers. We’ll then show you the different parts of the Terminology API, and how they can be used to help you solve these problems, and some of the governance issues you should consider when you do.

More about Jim Steel

Let's build! How and When to Use FHIR Terminology Service APIs
In this session you will be guided in using the terminology service APIs to build sample tools for clinical data entry and data validation scenarios. We will also work through the process of defining your own terminology resources and mapping them to standard terminologies such as SNOMED CT and LOINC. The exercises will use HTML and Javascript, and CSIRO’s Ontoserver terminology server, but if you would like to join in with other languages and/or tools, you’re very welcome.

More about Jim Steel

International Patient Summary - Opening new horizons for global clinical data exchange
The HL7 International Patient Summary (IPS) specification provides a minimal and non-exhaustive health record extract that is specialty agnostic and condition independent, clinically relevant and global in scope. The content may be delivered as a clinical document for unscheduled, cross-border care of a patient (e.g., European cross-border services) and other scenarios or potentially as individual data components (FHIR profiles). The tutorial provides an introduction and overview of the recently published HL7 FHIR Implementation Guide: International Patient Summary, Release 1 specification, including examples of FHIR IPS documents and individual data components.

More about Rob Hausam

Workflow
FHIR includes a transversal workflow mechanism that supports the range of workflow behaviours one can expect in implementations: from simple workflows (like simple lab order and fulfillment) to complex plans (like treatment plans involving care teams), including workflow deviations and other events.
This tutorial will describe:
1. The workflow patterns and resources
2. The workflow communication patterns (ad-hoc and managed workflows)
3. How to use the workflow resources like requests, events and tasks
4. How to document workflow specifications and examples using FHIR resources
5. An example from a practical implementation

At the end of this tutorial, participants are expected to
. Understand the FHIR resources for describing and managing workflows
. Know what resources to use in their implementations
. Know how to define and document workflows and examples using FHIR resources

More about José Costa Teixeira

Genomics on FHIR
This session will provide an introduction to the Clinical Genomics Reporting Implementation Guide using the example of an oncological genomic report. It will also cover how to get to a FHIR based report coming from source data like VCF, and the order entry process between a hospital and a genomic lab.

More about Patrick Werner

Cerner's Developer Program
This session will provide an overview of Cerner’s Open Developer Experience. Cerner operates an open developer ecosystem designed to facilitate creation of standards-based applications and adoption of those applications by Cerner’s healthcare clients.

More about Yegor Hanov

How Norway Uses FHIR and REST to Modernize Healthcare Interoperability
Norway's approach of using modern international standards to modernize how healthcare interoperability works: - The history of message based infrastructure and Norwegian specific standards - Utilizing other communication paradigm's to develop interoperability in healthcare - Overview of the national projects using FHIR so far - What we do, and what we don't - no-basis profiles and building a Norwegian FHIR community - How to make it interoperable national and international

More about Thomas Rosenlund

Second presentation to be announced.

PractitionerRole vs Practitioner
Grahame will discuss a design problem in FHIR R4, related to PractitionerRole vs Practitioner, and the design of the participations more generally.

More about Grahame Grieve

The FHIR implementer's Safety Check List
At this tutorial, Diego will go through some of the more relevant items in the FHIR implementer safety check list (https://www.hl7.org/fhir/safety.html) , exploring the risks, and the avoidable consequences of the lack of assessment / mitigation.
Some of the items will be demoed through client/server artifacts, and the participant's task will be to investigate and implement some proposed solutions.

More about Diego Kaminker

Let's Build! The FHIR implementer's Safety Check List
Let's work together on exercises.

More about Diego Kaminker

Let's Build! The FHIR implementer's Safety Check List
Let's work together and investigate and implement the suggestions the speaker gives during this Let's Build!

More about Diego Kaminker

Vonk Plugin Building


More about Christiaan Knaap

Let's Build! Vonk Plugin Building

In its latest version, FHIR covers a lot of different topics: REST API, terminology services, mapping language. However, organizations often have unique constraints that require a set of custom operations when adopting FHIR.
This Let's build! session provides you with a practical walkthrough covering the following topics:
* How to extend the functionality of the Vonk FHIR server
* How to customize already existing services provided by the Vonk FHIR server
* How to connect to external web services and FHIR servers to retrieve information

More about Christiaan Knaap

Python for FHIR
There are few open-source FHIR libraries for Python. During the tutorial, Ilya will present the overview of the current status for python libraries in FHIR world. He will show some problems in the existing implementations and provide more details about the reason for the decision to develop a new library from scratch rather than contribute to existing. He will show what benefits you will get from the library which Beda created. Finally, Ilya will discuss how Beda can contribute to the existing projects.

More about Ilya Beda

FHIR Mapping Language
Learn how to use the FHIR mapping language and its updated syntax with an overview of the language, key concepts and practical examples.
You can use the FHIR mapping language to transform content such as V2 and CCDA to/from FHIR, though due to time constraints that will not be covered - join the "Lets build!" session for that.

More about Vadim Peretokin

More about Alexander Zautke

Let's build! FHIR Mapping Engines
The FHIR specification defines a mapping language, allowing its users to define transformations between FHIR versions, or to convert content from different data models (HL7 v2, CCDA, Custom resources) to FHIR.
This Let’s build! session provides a practical introduction to the mapping language and its use cases. You will learn to:
- Write FHIR Mapping Language rules to transform content to FHIR
- Convert a Mapping Language Script to a StructureMap resource
- Execute a StructureMap using the Firely FHIR Mapper and Vonk FHIR server

Prerequisites: Install Forge and Postman

More about Vadim Peretokin

More about Alexander Zautke

We sit too much and move too little. This is creating tension and pain in our body. That is why yoga at work is evolving fast. Yoga creates space in your body, so body fluids can regenerate the tissues and joints and keep them healthy.

Chair yoga
During this short class, you will learn a sequence of movements you can do daily at your office. These yoga poses will focus on releasing your upper back and shoulders and help you increase your focus, enhance productivity and body awareness and release feelings of stress. By doing this, you reduce the risk of RSI and burnout.

We sit too much and move too little. This is creating tension and pain in our body. That is why yoga at work is evolving fast. Yoga creates space in your body, so body fluids can regenerate the tissues and joints and keep them healthy.

Hip series
During this short class, you will learn a sequence of movements that you can do daily at your office. In these series, we will open up your hips and your lower back. These poses will energize your body and bring you more body awareness. By doing this, you will release pain and tension in your lower back and reduce stress and the risk of burnout.

Working with SQL-on-FHIR
Did you know FHIR data can be stored in a relational database? SQL-on-FHIR is FHIR data ported to a relational database and accessed via SQL. In this session we will review methods to access that data with SQL and avoid common pitfalls when working with complex schemas. While this session will be focused on standard ANSI SQL, we will be using the Google Cloud Platform to demonstrate these capabilities.

More about Alexander "Sasha" Sicular

Let's Build! Working with SQL-on-FHIR
Building on the previous session, join us as we work directly with SQL queries against a sample FHIR dataset in Google Cloud's BigQuery.

More about Alexander "Sasha" Sicular

Remote Decision Support with CDS Hooks
CDS Hooks is an HL7 specification that leverages both FHIR and SMART to provide developers an open and interoperable standard for performing remote clinical decision support. Using CDS Hooks, you can provide guidance to the clinician such as a better medication to order, critical information about the patient, or push a SMART app that should be run. This session will provide a technical overview of CDS Hooks, how it aligns with existing HL7 efforts and standards, and what the future holds.

More about Dennis Patterson

Let's Build! CDS Hooks Services
Come build decision support services to provide guidance within an EHR or other CDS Hooks client system. In this "Let's build!" session, you will stand up your first CDS services and integrate with the public CDS Hooks sandbox. You'll leave with a better understanding of the APIs involved and things to consider when building services for production.

More about Dennis Patterson

Time for the group photo! Please join all.

Small but Mighty: A Guide to Building Tiny Teams That Solve Big Challenges
Start-ups have a reputation for revolutionizing arcane industries previously dominated by big corporations. In recent history, transformative changes in industries like transportation, banking, and education have come at the hands of teams the size of corporate micro-departments.
Technology helps ordinary humans create extraordinary change. Every day, the power of technology expands the realm of what is possible, allowing small teams to circumvent the challenges of limited manpower. And with non-traditional approaches to complex problems come non-traditional routes to success.

Huda Idrees knew that tackling Healthcare would not be an easy feat. Today, her 2.5yo start-up, Dot Health, is changing the way Canadians access their health information by making it easier and faster to request medical records from any provider across the country.

Small is synonymous with fast, nimble, and powerful. Huda’s entrepreneurial journey tells a story of turning shortcomings into superpowers and finding creative ways to deliver impactful solutions.

More about Huda Idrees

CDS

SMART on FHIR
This talk introduces the SMART on FHIR app platform. We will provide a overview of the platform architecture including APIs, security and EHR integration. We will describe ongoing implementation efforts with major EHR vendors and large US-based hospitals. We will demonstrate platform resources including the SMART App Gallery, Sandbox Server, sample data and developer tools and documentation.

More about Josh Mandel

Full-stack Apps FHIR with Javascript
Javascript has been the dominant language in web development. With NodeJS, many production applications use Javascript on the server. With frameworks like Electron, we can build native desktop apps. And with React Native and Ionic, Javascript and web technology allow us to build mobile apps.

This talk focuses on building FHIR apps completely with Javascript. We will cover:
• Architectural patterns
• Connecting and querying FHIR data repositories
• Working with FHIR using FHIRPath
• Mapping FHIR data
• Launching apps with SMART and CDS Hooks

More about Brian Kaney

Let's Build! A Native App with React Native
We will all build a native mobile app using React Native that you can try out right on your phone. This will include a standalone launch that can connect to an EHR sandbox. During this session, the audience will be engaged to come up with a new feature that we can build together.

More about Brian Kaney

Join us for the social event, one of the highlights of DevDays!

On Thursday evening, we are heading for IceAmsterdam, a venue right in the heart of Amsterdam, close to the Rijksmuseum.

At IceAmsterdam, you can drink, eat and socialize with colleagues and friends, while watching the ice skaters on the ice rink. If you wish, you can even skate yourself!

Program
17:30-17:45 - Gathering for social event outside the venue B1
17:45-18:00 - Travel by bus to Museumplein
18:00-21:30 - Social event and dinner at IceAmterdam

At 21:00 hrs, One bus will make one trip to the following hotels: Hotel Corendon and Hotel Artemis (first come, first serve)

IHE XDS: Adding Two Tablespoons of FHIR
What happens if one combines the strengths of XDS with those of FHIR? XDS is mainly used for the exchange of documents between organizations. FHIR is mainly used for the exchange of resources with apps. This talk explores how this combination is currently leveraged by various projects, and how XDS & FHIR could be used if one extrapolates the current usage of both XDS as well as FHIR. Topics include MHD (the FHIR version of XDS), FHIR documents, full text search in XDS documents, the link with RESTful DICOM, the exchange of random FHIR bundles instead of documents, as well as the power of on-demand documents. In short: a delicious dish comprised of a pinch of XDS with lots of added FHIR.

More about Rene Spronk

Interceptors and Subscriptions in HAPI FHIR
HAPI FHIR 3.8.0 introduces some significant improvements in the way that event notification is done. This includes a brand new interceptor framework, as well as a newly rewritten subscription module. This tutorial explores both of these new features and covers how to get started with event notifications using either framework. It also covers built-in interceptors for security, authorization, productivity and more.

More about James Agnew

Care Planning and Management Using FHIR Patient Care and Protocol Resources
Care planning is needed to manage medically complex and/or functionally impaired individuals as they interact with the health care system. Often, these individuals require real time coordination of the care as they receive care from multiple care providers and care settings. This tutorial will provide an overview of the FHIR resources for patient care (CarePlan, CareTeam, Goal, Condition, and others), the definition of computable clinical guidelines and protocols (PlanDefinition, ActivityDefinition) guided by clinical decision support, as well as some examples to illustrate how FHIR supports the care planning process.

More about Rene Spronk

Packages and versioning
Everything that defines FHIR can be found through a Canonical URL. While FHIR was still draft, this was good enough. With real collaboration emerging and multiple versions of the same conformance resources (StructureDefinitions, Extensions, Valuesets, etc), groups of resources that evolve together, the solution is Packages. This tutorial will tell you how can you consume, create and publish packages and how we see a tooling ecosystem emerge for packages.

More about Martijn Harthoorn

Using LOINC with FHIR
FHIR and LOINC go together like chips and salsa! FHIR’s standardized resources and API are the perfect delivery vehicle for clinical data coded with LOINC, the freely available international vocabulary standard for identifying health measurements, observations and documents. LOINC is now ubiquitous in health data systems worldwide and is an essential ingredient of system interoperability. In this session, we’ll get acquainted with the basics of LOINC, tour the common FHIR resources where you can make use of LOINC coded health data, and explore how to use the main FHIR terminology resources to interact with the LOINC terminology.

More about Daniel Vreeman

Clinical Decision Support in FHIR
The ability of healthcare IT systems to react quickly and effectively to emerging public health concerns is a significant challenge. See how the FHIR Clinical Reasoning Module can be used to help address this challenge by enabling the exchange of executable decision support.

More about Chris Schuler

CDS Hooks and SMART Web Messaging for Advanced Imaging Orders
SMART Web Messaging can be used to create seamless integrations between an EHR and an external SMART app. This talk will illustrate a real problem in US healthcare (wasteful spending on diagnostic imaging) and how SMART Web Messaging plays a role in an elegant solution to it. There is a companion codelab that will be introduced during the presentation, and participants are welcome to work through it afterward.

More about Carl Anderson

Type-Safe, Efficient and Convenient FHIR Development Using Protos
We are excited to present the 1.0 release of Google's Open Source FHIR-on-Protocol-Buffers platform. This combines an efficient, strongly-typed data format with a robust library of functionality to provide a FHIR development environment with strong compile-time guarantees, fast and convenient data access, and a fraction of the bytes on disk or on the wire. We’ll provide an overview of the capabilities including ingesting JSON FHIR data into proto form, custom profiling, and processing into inputs for machine learning models.

More about Nick George

SNOMED and FHIR
This session will provide information and discussion on the clear exchange of health information for all using a universal, codified, clinical terminology (SNOMED CT) leveraging FHIR Terminology Services. The session will focus on an introduction to the SNOMED CT model and the specifics and differences that are useful to be aware of when using SNOMED CT and FHIR together. Specific areas covered will include using SNOMED CT Reference Sets with Valuesets, working with the SNOMED CT Expression Constraint Language (ECL) and SNOMED URI standards as applicable to FHIR.

More about Rory Davidson

Validation of FHIR data
Are you a modeler or profile author? Do you use tools like Forge but you want to learn about the mechanics behind validation and the StructureDefinition resource? In this tutorial, Mirjam will show how familiar concepts translate into the StructureDefinition resource and how you can use validation tools to immediately try out the profiles you are creating.

More about Mirjam Baltus

IG Publisher Introduction and Trifolia


More about Lloyd McKenzie

Representing and Using Personal Health Device Data in FHIR
There are many situations where a health care provider will find it advantageous to monitor a patient at home. Instead of making multiple trips to the health care facilities or being retained in the health care facility, the patient can use one or more personal health devices (blood pressure monitors, pulse oximeters, weight scales, glucose monitors, thermometers, etc.) to take needed measurements at home.
What remains is to get these measurements back to the health care provider without requiring the patient to return to the health care provider. Continua/Personal Connected Health Alliance has been working with a number of SDOs to define a means of getting the device data back to the health care provider in a standardized manner. Given that personal health devices tend to have limited resources, typically run on batteries, and have a need to be portable and of low cost, the solution has been to have a single gateway application that communicates with these devices, converts their data to an HL7 form that all can understand, and delivers it to the health care facility where it can be read by the health care provider.
In this tutorial we will examine the PCHA Personal Health Device Implementation Guide which defines a standardized representation of Personal Health Device (PHD) data in HL7 FHIR resources. We will examine the scope of information that PHDs provide and where in the FHIR resources this information is placed.
The goal is to give participants enough background to use this data in their own profiles where ever PHD data is needed and in applications. Example applications might be a remote patient monitor that simply informs the health care provider that a patient has taken a measurement or an alert monitor that signals the health care provider that a measurement has crossed a certain threshold. To help in this endeavor a simple console-based Java project is provided that uses websockets to subscribe to uploaded measurements from a given patient and prints the content to the screen. The project provides the rudimentary building blocks all such FHIR data readers need; we leave it up to your genius and imagination to make something good out of it.
It is important to point out that there is also a Point of Care Devices Implementation Guide being developed by the Health Care Devices working group. Point of Care Devices (PoCDs) are typically used in hospitals and are run by medical professionals. PoCDs can be very complex but in their simplest form can mirror PHDs. This relation makes sense given that PHDs are modeled on the IEEE 11073 20601 standard which is a subset of the IEEE 11073 10201 standard used by PoCDs. The consequence of all this standards jargon means that the FHIR representation of PoCD and PHD device data has been harmonized as much as possible. The degree of harmonization has been vindicated by the fact that the above console application, designed for PHDs, successfully handled simulated PoCD measurements in recent HL7 connectathons.


More about Brian Reinhold

FHIR NPM Packages
Now that profiles are the corner stone of real world solutions, there is a rising need for version and distribution management. FHIR Packages help you solve that challenge.
There is now an official FHIR Package specification, there is a FHIR Package server, there is tooling, and there are real FHIR packages. The FHIR standard is now distributed as packages.
This tutorial will tell you how can you consume, create and publish packages and show you the ecosystem that is emerging around packages.

More about Martijn Harthoorn

More about Grahame Grieve

Startup Team Presentations
Come and listen to the presentations of the selected startup companies. A jury will judge the presentations of their innovative product..

Startup Track Finalists
Come and listen to the presentations of the nominated startup companies:
- Pact Care
- Nuvyta
- Tell Health
- Medeo
- Arkhn

A jury will judge the presentations of their innovative product.

Student Team Presentations
Student teams all over the world competed in an online hackathon for the Student Track Cup Amsterdam 2019. Three nominated student groups will pitch their products in a short presentation (ten minutes + two minutes for questions per group). A jury of FHIR experts will judge each team based on effective use of standards, originality of their solution and their presentation. The final winners will be announced during the award session that takes place from 16:40 - 17:20.

Winners of Student and Startup Track
Announcement and awards for the winners of the Student Track and the Startup Track. The winners will pitch their products to the audience before heading out to the social night out.

SNOMED and FHIR
This session will provide information and discussion on the clear exchange of health information for all using a universal, codified, clinical terminology (SNOMED CT) leveraging FHIR Terminology Services. The session will focus on an introduction to the SNOMED CT model and the specifics and differences that are useful to be aware of when using SNOMED CT and FHIR together. Specific areas covered will include using SNOMED CT Reference Sets with Valuesets, working with the SNOMED CT Expression Constraint Language (ECL) and SNOMED URI standards as applicable to FHIR.

More about Peter Williams

Let's Build! SNOMED and FHIR
Introduction to developing with SNOMED International's FHIR enabled open source SNOMED CT terminology server through useful examples and exercises to get used to access SNOMED CT through FHIR Terminology Services. This session is hands-on covering topics discussed in the SNOMED CT Overview session including using SNOMED CT reference sets with valuesets, working with the SNOMED CT Expression Constraint Language (ECL), and SNOMED URI standards as applicable to FHIR.

More about Peter Williams

Let's Build! Customizing IG Publisher Templates
The HL7 IG Publisher has undergone a shift to a template-based publication approach. These templates allow implementation guides (IG) to be published with a variety of aesthetics. The tutorial will examine the different pieces of a template and show how they work when publishing an implementation guide.

More about Lloyd McKenzie

Let's Build! Subscriptions

Let's Build! Implementation Guides in Simplifier
This Let’s Build! session demonstrates how to build a FHIR Implementation Guide (IG) using the IG editor of Simplifier.net. The given exercise provides the opportunity to create your own IG with guidance of the speakers.

More about Ardon Toonstra

R on FHIR: Let’s build a Cohort Counter that investigates multiple FHIR servers
In this Let’s build session we will build a Cohort Counter with R on FHIR. With this R app you can assess how many patients you can include in your research without transferring the actual research data. We will cover the following topics: connecting to a FHIR server with R on FHIR, constructing a search with the inclusion criteria, fetching and showing the number of possible inclusions, and expanding the search over multiple FHIR servers.

Requirements:
Laptop with a browser.
Installation of R Studio is handy, but not needed.

More about Sander Laverman

Hacking Interoperability in Healthcare with AI
During this session, you will learn how Lifen scaled from 0 to 100k daily predictions, served to healthcare practitioners to help them communicate more efficiently, by structuring information in free form medical notes.

Speaker: Félix Le Chevallier, Lifen

FHIR Projects
This session consists of a community presentation, which focuses on the implementation best practices of their project/product. This presentation is NOT a product showcase - the aim is to have max. 5 minutes to introduce a product/project, followed by a deep dive in things like the architectural approach, tools used, good/bad experiences with FHIR. The aim is for software implementers (even if they're not using the same architecture nor development platform) to learn from the development approach as used in other projects.

Time: 16:40-17:00
Laboratory Test Ordering on FHIR
Lab Test Ordering is a complex process, which includes not only the ordering phase but a large number of preparation steps like:
- Receive catalog
- Calculate the number of containers
- Get Answers on the Order Entry questions
FHIR R4 has introduced a set of new profiles and Resources, which can be used to build these interactions. We will demonstrate how to use these Resources to build API for a Laboratory Provider. We will mention some issues in FHIR R4 and point out the way FHIR R5 is going to fix them.

More about Aleksandr Ivanov

Opening Startup and Student Track
Delegates participating in the Startup and Student Track will be welcomed to the FHIR DevDays.

Pyrog: an open-source mapping tool and ETL for FHIR
Data integration is an essential task in building a more interoperable world, yet translating already existing data into FHIR can be a difficult task. Pyrog was built to help you do this! It is an open-source app which helps developers explore structured databases and map them to FHIR. It enables building complex queries so as to fetch data from already existing databases and structure this information using the FHIR syntax.
Mappings designed with Pyrog are also shared, which allows for users to group in communities of experts. Database schemas can be easily uploaded, and teams who have already performed data integration of their own database into FHIR can share their work on Pyrog.
During this presentation, we will present the main ideas which led to coding Pyrog, the community behind it and how it is used in France. The main features of Pyrog - versioning, profiling, etc - will also be displayed and we will briefly discuss the evolution of this software.

More about Corneliu Malciu

FHIR for Clinical Research – the same but different
Clinical Research has been slower to embrace FHIR than clinical care. Some of that is cultural and some is down to the difference in approach required in some apparently familiar areas. This session will run through some of the projects that are currently ongoing, and the developments in FHIR resources specific to Clinical Research. It will also outline some of the special considerations around data handling and the particular requirements imposed by the regulators.

More about Hugh Glover

Build OpenUI5 Apps based on FHIR
OpenUI5-FHIR is a community driven open-source project initiated by SAP to connect FHIR® and OpenUI5/SAPUI5, aka UI5, THE user-interface framework to build beautiful and enterprise-ready web applications based on the SAP Fiori Design Guidelines.
As OpenUI5 is open-source, it’s possible for everyone in the world to build OpenUI5 applications based on any server API, because it’s protocol independent. The OpenUI5-FHIR project offers the FHIR® protocol specific functionality to speed up the application development and decreases the lines of code on application side, because OpenUI5-FHIR takes care of requesting FHIR® resources, displaying the content on the user interface and submitting changes to a FHIR® endpoint.
In this session, the OpenUI5-FHIR project will be introduced by presenting the basic concepts and best practices while developing web applications with OpenUI5, OpenUI5-FHIR and a FHIR® endpoint. Using OpenUI5 and OpenUI5-FHIR makes web application development based on FHIR® endpoints such easy.

More about Kishore Kumar Vivekanandan

FHIR Shorthand
FHIR Shorthand (“FSH”) is an author-friendly language for defining the content of IGs, including profiles, extensions, value sets, examples, and search parameters. FSH is interpreted by SUSHI (“Sushi Unshortens ShortHand Inputs”), a compiler that creates FHIR artifacts ready for the FHIR IG Publisher.
Why a shorthand notation? Experience has proven that creating and maintaining complex software projects is best managed as a set of text files. But, FHIR StructureDefinitions are too unwieldy for this. As a purpose-designed language, FSH is concise, easy to understand, and aligned to user intentions. If you want to fix a value, you say “clinicalStatus = active” and if you want to constrain a choice, you say “value[x] only Quantity”. Slicing and extensions are also achieved through simple declarative statements.
FSH files are ideal for source code control, providing meaningful differentials, support for merging and conflict resolution, and distributed development. These features allow FSH to scale up in ways that visual editors and spreadsheets cannot.
FHIR Shorthand is an active HL7 project sponsored by FHIR Infrastructure Work Group. We will share the current design and proposed syntax and solicit your input.

More about Mark Kramer

Time:15:50-16:10 hrs
Using a Single FHIR Backend Repository on a FHIR/SMART on FHIR Compliant Patient Follow-Up System
Edge consulting developed a patient/practitioner interaction and follow-up system for the Norwegian clinic Evjeklinikken, specializing on the treatment of obesity. The system is 100% FHIR/SMART on FHIR compliant and runs on Smile CDR in a Microsoft Azure environment. The talk will detail the use of FHIR Resources for a patient follow-up system with apps for Patients and Practitioners, the use of a single multi-tenant FHIR backend with no additional API middle layers, as well as the security architecture for the system: Microsoft Azure Security, 2FA, IP-restrictions, SMART-on-FHIR, Consent, and AuditEvent.

The talk will also share and discuss the lessons learned:

* FHIR works well as a repository of data including administrative aspects
* A single backend made it easy to set up multi-tenant endpoints
* Challenges with indexing and performance on the database
* Challenges with integrating third-party 2FA-architecture with SMART on FHIR security flow
* Challenges with SMART on FHIR scopes relating to compartments

Data Analytics with FHIR: Scalability and Security
FHIR is an optimal format for transmission of high volumes of clinical data, leveraged by researchers and practitioners for healthcare related analytics. Instead of storing FHIR records in databases, we take the approach adopted by many companies in the big data analytics space, that store the information in files with columnar (e.g. Apache Parquet) format. File storage is inexpensive and scalable. Moreover, Parquet format is designed to accelerate analytic workloads, by implementing advanced data filtering capabilities and compression inside the files. Also, Parquet is already being considered by the FHIR standard (in a different context, as a candidate for efficient bulk data transfer). Parquet support for nested columns allows for direct mapping and storage of FHIR messages.

We take a leading role in Apache Parquet community work on an encryption mechanism that protects sensitive column data. The specification of this mechanism has been recently adopted by the community as a part of the Parquet format standard. We also take part in a joint project with European hospitals where we explore application of the FHIR and Parquet standards for healthcare usecases. In this presentation, Gidon will outline our Parquet-based approach to secure and scalable storage, transfer and analysis of FHIR data.

More about Gidon Gershinsky

Building and Testing SMART on FHIR Apps with HSPC Sandbox 2019
The Health Services Platform Consortium (HSPC) was founded in 2013 by Intermountain Healthcare, Louisiana State University and the Veteran’s Administration to improve health by creating a vibrant, open ecosystem of interoperable platforms, applications, and knowledge assets. This tutorial will provide an overview of the HSPC Developers Portal, HSPC Sandbox and HSPC Gallery. The participants will learn how to effectively use the latest HSPC platform, SDKs and libraries, application samples, and documentation to set up their personal SMART on FHIR sandbox in the cloud. We will explore the steps for populating the sandbox with realistic clinical data. Finally, we will demonstrate the process of developing and testing health applications and CDS Hooks services in the sandbox environment that we created.

More about Nikolai Schwertner

Let's Build! Building and Testing SMART on FHIR Apps with HSPC Sandbox 2019


More about Nikolai Schwertner

Subscriptions on FHIR
The Subscription resource in FHIR has seen quite a few changes recently. In this session we will cover a brief history of the changes, where we are today, and where we still need some work.

More about Gino Canessa

Let's Build! FHIR Subscriptions
This session will allow developers a chance to build functioning Clients or Servers around FHIR Subscriptions. Building on the information provided during the previous session, we will briefly cover the implementation details for common scenarios and then be available to work through any questions or issues. Reference implementations for Clients and Servers will be available for testing against.

More about Gino Canessa

Implementing Population Health Management and Care Coordination in a Hybrid Application Environment
In today's health care environments, care programs are no longer delivered to the patient through a single homogeneous organization using a single application. More and more, there are multiple specialized applications delivering care programs for specific patient populations, and sometimes separate organizations supporting the patients in each program. This leaves the healthcare organization that wants to coordinate care across there care programs with a big challenge, e.g.
- What care programs are available and applicable for a certain patient group
- How to assign an available care program to an individual patient
- How do I keep track of the progress of the patient within the care program

In this tutorial we will look into the architecture required and FHIR resources available for Care Coordination, and mechanisms to make this work in a scalable manner.

More about Theo Stolker

1. The Swedish national architecture for information exchange based on FHIR
Inera is a limited company owned by Swedish county councils, regions and municipalities, as well as the Swedish Association of Local Authorities and Regions.
Since 2007 we have delivered a national architecture for information exchange in Sweden, allowing thousands of caregivers to share health care information between themselves and to patients. The architecture is SOAP/messaging based and relies on three principles:
1. Loose coupling and logical addressing
2. Aggregation and minimizing API calls
3. Standardized information formats and content - Using a common, national standard for information format and content, based on the greenCDA concept, interoperability is greatly facilitated.
For several reasons there is a need to move towards a new architecture based on FHIR that is still compliant to the principles. Work has been done at Inera during 2019 to form a goal architecture and a strategy for moving towards that goal. We will present that work and the PoC for testing the architectural components.
The goal with this work is to establish a common framework that enables information exchange on a national as well as regional level between caregivers, patients and researchers, with components in place to enable data to flow based on the three principles mentioned above.
Developers are very welcome to attend, but it won't be a developer focused presentation.

More about Viktor Jernelöv

2. Insights into the use of FHIR in Finland
At this presentation, the focus is on the Kanta PHR, a national, centralized personal health record platform for citizen-generated well being data stored with well being applications. We will talk about the development process for Kanta PHR profiles and the challenges we have faced, and the plan for building support for R4 next to current STU3 support in Kanta PHR.
We will also share experiences from the developers of the first well being apps connected to the PHR and present an open source library developed to assist app developers in getting their apps connected with the PHR.
In addition, we take a brief look on FHIR based Scheduling specifications, and how FHIR plays a part in active and future EHR projects.

More about Anna Korpela

16:40 - 17:00
Vonk as integration middleware using custom plugins
At Radboudumc, Vonk server will be used as an Integration middleware platform to enable FHIR STU 3, with Medmij profiles on top (at this time only observation resources) messaging. The resources will forwarded to in internal message broker (Cloverleaf) and finally the results will be stored in Epic.The goal is to be independant form Epic in terms of supported FHIR version en supported profiles.
The presentation will be about how the idea was born, how it was designed, and finally how it was realized.

More about Pascal van Nispen


17:00 - 17:20
Artificial Intelligence – Semantic Similarity Network – Applications for FHIR interoperability
FHIR is the base for clinical data ecosystems. Semantic harmonization and intelligent mapping still required expert human efforts (error prompt, time, effort, and cost for each new integration). This is a road block for the expected exponential grow of ecosystems. This short presentation introduces Artificial Intelligence - Semantic Similarity Network and its applicability to simplify semantic matching for semiautomatic FHIR interoperability.

More about Fawsy Bendeck

We sit too much and move too little. This is creating tension and pain in our body. That is why yoga at work is evolving fast. Yoga creates space in your body, so body fluids can regenerate the tissues and joints and keep them healthy.

Chair yoga
During this short class, you will learn a sequence of movements you can do daily at your office. These yoga poses will focus on releasing your upper back and shoulders and help you increase your focus, enhance productivity and body awareness and release feelings of stress. By doing this, you reduce the risk of RSI and burnout.

We sit too much and move too little. This is creating tension and pain in our body. That is why yoga at work is evolving fast. Yoga creates space in your body, so body fluids can regenerate the tissues and joints and keep them healthy.

Hip series
During this short class, you will learn a sequence of movements that you can do daily at your office. In these series, we will open up your hips and your lower back. These poses will energize your body and bring you more body awareness. By doing this, you will release pain and tension in your lower back and reduce stress and the risk of burnout.

How to Add a FHIR API to an Existing Database
Learn how you can build a data provider for the FHIR Server for Azure to put a FHIR ApI over an existing data store

More about John Stairs

Hacking FHIR Server for Azure
Do you have an existing data store that needs a FHIR API, or looking for a flexible FHIR server to prototype new features? FHIR Server for Azure is an open source project hosted on Github, it provides an out-of-the-box REST API and support for multiple databases (CosmosDB and SQL). Come and learn your way around the codebase, how to contribute and extend it with new features.

More about Brendan Kowitz

IoMT - Supporting High Frequency Data in FHIR
A deep dive into the challenges associated with ingesting data from Internet of Medical Things (IoMT) devices. Cover lessons learned and explore possible solutions leveraging the FHIR specification high frequency data sets with low latency.

More about Dustin Burson

More about Nate Malubay

Let’s Build! – IoMT Data to FHIR
Build an end to end solution for ingesting high frequency IoMT (Internet of Medical Things) data into a FHIR Server. Using open source tools, we will walk through configuring and deploying a FHIR server, an IoMT to FHIR connector and an iOS application that will send high frequency Apple HealthKit data to the FHIR Server.

Prerequisites:If you want to participate in building the end to end solution, please have a Mac with XCode 11 or greater installed, and create a free Azure account https://azure.microsoft.com/en-us/free prior to the start of the session.

More about Dustin Burson

More about Nate Malubay

Graphql
The RESTful API is the foundation of the FHIR standard and has proven very popular. But it's not always the answer. Both graphQL and the GraphDefinition resource offer different ways of building on the RESTful API to make for more efficient communications. Grahame will describe and compare the two approaches, and advocate for their wider usage.

More about Grahame Grieve

Valuing Patient Stories: Amplifying the patient voice through hard data
There are few user-friendly tools designed to support patient daily care, manage appointments, and leverage patient-generated data at home and in the clinical setting. The MITRE corporation is working to transform data into insights to reinvent the healthcare experience and pioneer a healthier future for patients and their care teams. This mother and daughter presentation describes how one patient story began a quest to amplify the patient voice and create an evidence-based tool for capturing and communicating patient and caregiver data. It offers both patient and caregiver insights into managing chronic conditions, the value of patient-generated data, tangible strategies and solutions used to support recovery, and the patient empowerment research that was inspired by their experience.

More about Kristina Sheridan

More about Kate Sheridan

Let's build! Machine Learning Predictions with FHIR and Healthcare API
In this session, you will create a prediction pipeline for FHIR resources using Google's Cloud Healthcare API and AI Platform.
You will learn
- To create Cloud Healthcare API datasets and FHIR stores
- To train a TensorFlow model on FHIR data
- To serve predictions from your model using AI Platform and Cloud Functions

There are no prerequisites, although previous experience with Google Cloud Platform and the Cloud Shell environment are an advantage.

More about Frank Yang

More about Nik Klassen

Let's build! Machine Learning Predictions with FHIR and Healthcare API - continued
This session is a continuation of the session at 16:00 hrs, where you learn to create a prediction pipeline for FHIR resources using Google's Cloud Healthcare API and AI Platform.

There are no prerequisites, although previous experience with Google Cloud Platform and the Cloud Shell environment are an advantage.

More about Frank Yang

More about Nik Klassen

The closing remarks summarize DevDays 2019 and the overall state of the FHIR Community and where we are going. During this session, the winner of the Patient Innovator Track will be announced.

More about Grahame Grieve

Consumer Access / Advanced Oauth
How do we move beyond a "core data set," giving consumer apps the power to securely access diverse health data stored in disparate back-end systems? We'll take imaging data as a case study, showing a technical architecture that allows a client to register with a single institutional endpoint and request authorization to connect with multiple FHIR servers (e.g. a clinical data server and an imaging data server). We'll demonstrate an open source reference architecture, explore challenges for client and server developers, and review a set of OAuth-based specifications to enable this kind of rich ecosystem. Topics will include dynamic client registration, PKCE, App-Claimed https URLs, token introspection and token exchange.

More about Josh Mandel

Birds of a Feather: Using Data Instead of Gut Feeling to Drive Efficiency in a Health Practice
There is a trove of analytical in FHIR resource in a health system’s data, which can be leveraged to drive operational efficiency and patient satisfaction. Some examples: How long are your patients having to wait to get an appointment at your institution? What is your report turn around time for lab work, radiology…etc? How long does a patient have to wait once they show up to their appointment?

More about Mohannad Hussain

Structured Data Capture STU3
An overview of the changes and enhancements to questionnaire support provided by the new Structured Data Capture (SDC) implementation guide, including looking at support for complex questionnaire rendering, adaptive forms, complex behavior, form population and data extraction. Lloyd will also look at where the Questionnaire space is likely to go next. The "hands on" portion will leverage the U.S. National Library of Medicine's authoring tool to create questionnaires that can be auto-filled from existing EHR data.

More about Lloyd McKenzie

Terminology-Aware Analytics with FHIR
So, you’ve managed to get access to some FHIR data. Now you want to use it to solve some real-world problems, probably using some complex analytic queries and machine learning algorithms.
Let us take you through some worked examples that involve using FHIR-based data sets for notebook-based data science tasks. We’ll show you some techniques for joining your FHIR data with clinical terminology knowledge, which may help you to feed your models with better data.
We’ll also provide some tips and tricks that deal with issues that come up in real data sets, such as historically coded records, CodeSystem versioning and achieving various different types of categorisation when grouping and filtering.

More about John Grimes

Integration Apple HealthKit Data Into Mobile Apps Powered by a FHIR Server
Thanks to Apple, patients can get their medical data to their phones from thousands of healthcare organizations. Modern iPhone apps can access this data via Apple HealthKit API.
In this tutorial, Mike will show how to integrate your mobile app with Apple HealthKit API, persist all the data received from Apple HealthKit to a FHIR server, and visualize this data in the UI. He will indicate challenges and how to overcome them and share sample open-source code that every engineer can use and benefit from.

More about Mike Poluboyarinov

Bulk data, import/export


More about Josh Mandel

FHIR R5


More about Lloyd McKenzie

In Search of FHIR Backend: Transforming Legacy to FHIR
Tips and tricks about refactoring your existing system to FHIR-first architecture.

More about Nikolai Ryzhikov

Resource Graphs are key to achieve interoperability
A GraphDefinition is a formal computable definition of a graph of resources and makes rules about the relationships between the resources in the set. Amongst other things GraphDefinitions are used to specify the structure of a FHIR Document or FHIR Message, and when used in conjunction with StructureDefinition it provides allows for validation of graphs of resources. This tutorial will cover the need for the GraphDefinition resource, how it differs from StructureDefinition and other conformance resources, and how it could be used for use cases such as the definition a graph of resources to return in a query, and the definition of graphs of logical models.

The attendees are assumed to have some knowledge of the FHIR conformance resources.

More about Rene Spronk

Time: 11:55-12:15
Balancing Act: Exposing Legacy Data in FHIR
This session covers best practices for exposing legacy data in a FHIR api to support both local business requirements and public accessibility. The key issue in this context is understanding the relationship between the rigid requirements of existing business processes and the vision of more broadly intelligible information. Issues include technical mapping tasks-such as distinguishing between standardizable and non-standardizable elements, handling mandatory elements, and ad hoc namespaces for local elements-and organizational alignment tasks such as tactics for building long-term consensus and for addressing near-term risks.
We present examples of these issues and their solutions in the context of a production EHR.
Who should attend:
Representatives of organizations looking to exchange clinical data with partners
Architects and project leads who make decisions about how to support conflicting requirements

More about Jay Lyle

FHIRPath
FHIRPath is a path traversal and extraction language much like XPath. It is used --amongst other things-- for validation of instances. Learn about its syntax and structure so you can author FHIRPath expressions with confidence.

More about Mirjam Baltus

Time: 14:50-15:10
Creating a Tool to Map FHIR to OMOP
This talk will discuss some of the challenges and best practices related to the mapping of FHIR R4 to OMOP CDM version 5.2.2. The presentation will cover the semantic as well as the syntactic mapping, using the HAPI-FHIR library to map Patient, Condition, Encounter, Procedure, Observation FHIR resources to Person, Condition_Occurrence, Visit_ Occurrence, Procedure_ Occurrence, Measurement OMOP tables, respectively.
The Mapping between different Value sets is performed using ConceptMap resource. The differences between these standards and the limitations in expressing a mapping will be covered as well.

Speaker: Sohrab Hejazi, University Hospital Carl Gustav Carus Dresden

FAST CDA: FHIR Tool Stack For CDA
FHIRs first letter stands for fast, can this also be applied to the implementation of CDA-based solutions? Which tools and implementation support of the huge FHIR ecosystem can be used for CDA?
The tutorial will cover the FHIR CDA Logical Model which enables to parse/generate and validate CDA documents. With FHIRPath information from CDA documents can be directly extracted with a FHIR client. There is also support in the java reference implementation for transforming CDA narrative to xhtml and back. Different mapping strategies are presented for CDA and FHIR, from programmatic approaches to functional programming (XSLT and FHIR Mapping Language).

More about Oliver Egger

Let's Build! FAST CDA: FHIR Tool Stack for CDA
FHIRs first letter stands for fast, can this also be applied to the implementation of CDA-based solutions? Which tools and implementation support of the huge FHIR ecosystem can be used for CDA?
In the LET’S BUILD tutorial we will convert an Art-Decor CDA specification into an equivalent FHIR composition, build the corresponding mapping and validate the CDA document.

More about Oliver Egger

FHIR Facade


More about Christiaan Knaap

Let's Build! A FHIR Facade
Vonk FHIR Server can expose data from your existing system as FHIR resources. This session wil teach you how to build a plugin to make that work. We’ll use an example legacy system and build a Facade on top of it. This includes mapping data to FHIR resources and mapping search parameters to queries to the legacy system.

More about Christiaan Knaap

FHIR Profile Editor Forge
Learn how to work with Forge, the desktop tool for building FHIR Profiles.

Prerequisites:
Install Forge on your laptop.

More about Ward Weistra

1. Enterprise Readiness of FHIR Based Applications
When building standard enterprise applications like SAP Patient Management one needs to provide a set of non-functional qualities that make them usable in a wide range of contexts.
The most important are
• Internationalization/Globalization: Supporting multi-language texts and country specific address and name formats
• Interoperability: Exchanging data within a customer system landscape
• Adaptability: Extending standard resource types towards the country specific/customer needs
The FHIR® standard provides a general methodology that enables the implementation of these aspects. Based on examples we will demonstrate how the above requirements can be handled in a compliant way based on the FHIR® rules.

More about Mohammed Unewisse

2. Adding FHIR Interfaces to Legacy Systems
Many applications that have been developed in the pre-FHIR era are looking to add FHIR API. There are several ways of doing this:
-implement a FHIR interface to translate FHIR REST calls to queries to the underlying database or services of the original system
-synchronize data in your database with the data in the generic FHIR server that will do rest of the work
During this presentation, we will explore the pros and cons of both approaches on the example of real-life use cases.

More about Pavel Smirnov

The Dutch profiles
In the Netherlands, healthcare IT is heavily involved in FHIR, invoked and supported by national programs and subsidiary arrangements. The Dutch Health and Care Information Models and their related FHIR profiles are used as a foundation in these programs. This tutorial gives a brief overview of Dutch national programs that stimulate interoperability based on FHIR and zooms in on the Dutch profiles. We will go into detail on how these profiles are created and maintained and also cover the lessons learned. After this session, two ‘Let’s Build!’ sessions allow you to get hands-on with the Dutch profiles.

More about Ardon Toonstra

Dutch profiles: testing and qualification
FHIR profiles are used to express the required data model and for validation, but by themselves they are not enough to successfully enable interoperability. Implementers should be able to test their systems. In addition, some Dutch programs require proof of correct implementation of relevant FHIR profiles.
This Let’s Build! session demonstrates a testing and qualification environment in use by Nictiz. After a short demo you can hook up your own system or follow one of the exercises to test your conformance to the Dutch Profiles.


Prerequisites:
- Have a FHIR client or HTTP tool such as Postman ready
- Or your own FHIR server accessible through the internet
- Preferred: registered account on Touchstone

More about Ardon Toonstra

Dutch profiles in a package
The Dutch profiles are versioned and distributed with the use of FHIR NPM packages. This session starts with a short recap of what FHIR packages are, why we need them and how they are used in the Dutch context. Then we go hands-on with packages. We will create, publish, consume and use packages to fully understand the package mechanism.

Prerequisites:
- Install Torniox for STU3 (https://simplifier.net/downloads/torinox)
- Install Forge for STU3

More about Ardon Toonstra

Comparison of Big National FHIR Initiatives
Big national initiatives around the world arise to enable interoperability, for example Argonaut, the International Patient Summary and the Dutch/Finnish PHR programs. How interoperable are those different programs at an international level? Imagine what would happen if a big tech company from the USA, active in healthcare IT, start operations abroad: for example, participating in the Dutch PHR program. As a discussion starter we briefly go over a comparison of Argonaut and the Dutch PHR program. It should start a discussion about the effort it requires to overcome national specified FHIR conformance resources and implementation guides when acting international.

More about Ardon Toonstra

Repeated Session
This slot is reserved for a session which will be repeated. The session will be announced in Amsterdam.

Terminology Services: Taking a Closer Look at Applying $closure
The typical FHIR Terminology Service operations of $expand, $validate-code, $lookup, $subsumes and $translate have been widely implemented and are relatively well understood. The $closure operation, while quite powerful and potentially quite useful, has so far received much less attention and use and generally is not very well understood. The idea of $closure is to support the creation and ongoing maintenance of a client-side transitive closure table, which can be very useful when designing applications that require high performance when searching and reasoning with hierarchical terminologies. This tutorial explores the rationale and potential applications of this operation, including live examples and suggestions for how you may want to use it in your applications. The Let’s Build session at 10:15 hours provides a further opportunity for live demonstration and hands on familiarity with $closure and how you can use this powerful capability in your FHIR applications.

More about Rob Hausam

Let's Build! Terminology Services: Taking a Closer Look at Applying $closure
The typical FHIR Terminology Service operations of $expand, $validate-code, $lookup, $subsumes and $translate have been widely implemented and are relatively well understood. The $closure operation, while quite powerful and potentially quite useful, has so far received much less attention and use and generally is not very well understood. The idea of $closure is to support the creation and ongoing maintenance of a client-side transitive closure table, which can be very useful when designing applications that require high performance when searching and reasoning with hierarchical terminologies. The Let’s Build session provides a further opportunity for live demonstration and hands on familiarity with $closure and how you can use this powerful capability in your FHIR applications.

More about Rob Hausam

Quality Measurement in FHIR
Clinical quality improvement is a critical aspect of healthcare delivery and relies on the ability to both measure and influence clinical care. See how the FHIR Clinical Reasoning Module can be used to describe and evaluate quality measures as well as a brief introduction to Clinical Quality Language (CQL).

More about Chris Schuler

Let's Build! CQL
This session will build running examples of quality measures and decision support rules using FHIR and Clinical Quality Language (CQL), exploring implementation challenges and surveying the landscape of tools and techniques currently available. We will build off the examples presented in the Quality Measurement in FHIR and Clinical Decision Support in FHIR sessions. In this hands on session, see how the FHIR Clinical Reasoning Module can be used to share computable clinical knowledge and how that knowledge can be dynamically delivered through services using CDS Hooks.

More about Chris Schuler