FHIR Implementation Guides in Simplifier.net

Earlier today we released version 13.5 of the FHIR Registry Simplifier.net. This version contains a number of bugfixes and minor improvements plus two major features in Beta: the Implementation Guide Editor & Viewer and GitHub Integration. Let’s focus on the first. Implementation Guides (IGs) are an important communication channel for interoperability projects. It’s where people (developers, architects, product owners etc.) go to learn how FHIR is implemented in a certain use-case. IG support contains a big chunk of functionality, which is why we chose to release this feature in BETA and ask users for input (see previous blog post). Some nice features of IG support are drag&drop, auto-generated titles, improved help, sort, and a preview button, which brings you directly to the IG Viewer.

IG support is a feature of the paid plans of Simplifier.net (although free for Beta testers!). Lately, we got a lot of questions from the community about the plans and our pricing policy. We decided to put the first version of the feature page and the pricing page on-line. Not all features have been implemented yet. For instance, we are working hard on validation and collaboration. We hope to release these features by the end of this year, early next year. Simplifier.net will be the one-stop-shop for FHIR projects.


How to publish your profile – within one hour

By Ardon Toonstra – After completing your FHIR profiles, the next step will probably be to make them available to the world. Publishing your profiles will enable, for instance, app developers to build on your work. It may even be possible that your published profiles become the cornerstone of nationwide IT infrastructure for decades!

Assuming you have used Forge to author your profiles it will be very easy to publish your work thanks to the integration of Forge with Simplifier. Besides Simplifier, Forge is able to publish to any FHIR server with the click of a button. In this post, however, we will elaborate on publishing profiles to Simplifier. Simplifier is a registry for all FHIR resources. It facilitates you in using FHIR more efficient because of the ability to search and use previous work. Moreover, Simplifier can be used as platform to work on your profiles with multiple developers. I will come back on this shortly, but let me first demonstrate you how to publish your profile in two steps!

Forge: upload to Simplifier

After finishing your profile in Forge go to ‘File’ at the top menu and click ‘Publish to Simplifier.net’ (or press Ctrl + U instead). In the following screen you will be asked to give your Simplifier.net credentials. In case you do not have a Simplifier account, just register here. Create a project by going to your personal portal, the tab ‘your projects’ and click the button ‘create a new project’. Next, after you provided your credentials click Connect and wait a second until the Status says ‘Passed’. Now, you can select your project in which you want to publish your profile. Click the save button to finish the upload.

01_How to Publish

Forge integration with Simplifier

Simplifier: publish

Forge returns to its editor screen and your profile is now online at Simplifier. If your profile is truly ready for the world you can publish it at Simplifier. The next step will be to find your just uploaded profile in your project at Simplifier. Go to your personal portal on Simplifier and select the project under ‘Your Projects’. Click on your uploaded profile which can be found under the tab ‘Resources’. In your profile page, click the ‘Publish’ button in the top right beneath your username. That’s it, your profile is online and marked as published at Simplifier!



I promised you to continue about using Simplifier as a platform to work on your profiles with different users/developers. One of the reasons this works is the integration of Forge and Simplifier. Imagine that you would like to get feedback on your designed FHIR profiles. To arrange this, just upload the profiles to Simplifier and provide the desired users with the project name or link to your project. In this way you show them the rendered profiles in a coherent way and provide them the ability to download the profiles in XML or JSON format. Members of the same project, assuming they have the necessary user rights, can easily update the profiles by importing them into Forge and upload them again as described above. Thereby making FHIR even simpler!

If you have any questions, feel free to comment or contact us at simplifier@furore.com.

Create my first FHIR Implementation Guide using Simplifier

The much appreciated beta testers of Simplifier can use the new Implementation Guide (IG) editor. To become a beta tester, follow the instructions on this link! In this blogpost I will show you how to make an IG using Simplifier. For your IG, you can use your own resources and/or any of the publically available resources placed on Simplifier. This IG makes use of my project’s resources  which I uploaded by a link to my GitHub repository. In a former blog, I showed how to link a project to a GitHub repository.

Step 1 – Create an IG

As a beta tester the ‘Implementation Guides’ tab in your portal will be visible. Click the big green button and provide a title to create your first IG. The IG will appear in the menu with the options Browse, Edit and Delete. The Edit button opens the IG editor.


Personal portal in Simplifier

Step 2 – Define the outline of your IG

The IG editor opens with the root page. On this page you can adjust the title and select one of two IG rendering format. For now, we leave it at the default ‘Two Level Menu’. Feel free to experiment! Add a child page to the root element by clicking the icon that appears when you hover above the tree elements in the left section of the IG editor. Give the newly made page an appropriate name. Add more base and child pages to make the outline of your IG.

In our ‘Two Level’ rendering format, the first level elements will form the navigation bar in the top of the IG. If you add child pages to one of those elements, that section of the navigation bar will have a dropdown menu, which will include it’s child pages. A third level will form the different paragraphs, including a navigation menu on the side. Please experiment with these multiple levels of pages, and let us know what you think!

Step 3 – Provide the content of your IG

You can fill the IG content in a fast and good-looking way thanks to the Markdown based editor and Simplifier’s resources. For the use of Markdown features in this editor I would like to refer you to this page or Google. Use the preview on the right section to see the progress of your work of the current page. Click on the “Preview” button to preview the entire IG. Simplifier automatically saves your work so don’t worry if you leave the editor or if you cannot find the save button (it is not there!). In the last part of this blog, I will elaborate further on how to include publicly available resources on Simplifier.

Step 4 – Include rendered resources from Simplifier

In my IG, I want to include the rendered trees and tables of the FHIR StructureDefinitions in my project SIG. One of them is a profile on an Observation resource named LabObservationNorway and is located at https://simplifier.net/SIG/LabObservationNorway4. Therefore, I type the statements {{tree:SIG/LabObservationNorway4}} and {{table:SIG/LabObservationNorway4}} in the editor on the page named ‘LabObservationNorway’. To see the result in the preview section press  ‘Ctrl+Enter’ or refresh the page with the button on the right. Next, let’s include a link to an example instance of this profile. This works in a same manner using the location on Simplifier. The statement {{link:SIG/Observation-example9}} will give a link to that particular example.

The IG editor has more statements that can be used. The {{structure:project/resource}} statement gives another version of the rendered tree. For example, it has a different layout and allows you to collapse the tree. This rendering, however, is at the moment still work in progress. Moreover, it is possible to include table of contents anywhere in the IG. There are two variations, one contains all pages of the IG ( {{index:root}} ) and the other contains a table of contents of the current pagee( {{index:current}} ). Lastly, {{namingsystems:project}} will list all the NamingSystems of a project. More options within the IG editor will follow. If you have any suggestions, let us know!


IG Editor


Simplifier’s IG editor lets you combine FHIR resources together with textual guidance in an fast, coherent and straightforward way, thereby creating a useful and easy to read IG. The above mentioned example IG can be found here. If you haven’t done so already: become a beta tester to create your own IG and play around yourself. Keep in mind that the IG editor is still a beta feature and improvements can be expected. Feedback is much appreciated and can be easily provided through the feedback button on the top right.

Use your GitHub repository to automatically render and share your work with the FHIR community

Recently Simplifier released new features for the early FHIR adopters. Become a beta tester to get access to these features. One of these features is the ability to link your project with a GitHub repository. GitHub integration fetches your resources from a repository in GitHub and adds them to your Simplifier project.  Sharing and rendering your resources online and keeping them up-to-date has never been simpler!

Let me show you how easy it is.

Let’s assume you have a GitHub repository, that contains resources ready to upload to Simplifier. You can start the linking process by logging in to your account on Simplifier and create or select a project in your portal. In your project page, go to Options and click ‘Link to GitHub Repository’.


You will be redirected to the GitHub login or, when you are already logged in in GitHub, straight to the page where you will be asked by Github to authorize that Simplifier can access your repository.


After you authorized Simplifier to your GitHub repository, you are redirected back to Simplifier where you will be asked to select which repository and which branch you want to link to your project.

You can also configure how to deal with files that cannot be imported and whether to also remove resources from your project when they are removed from your repository. By clicking on the create button all the resources from the linked repository are instantly added to your project.


At any later time, you can check the status of the link with Github and modify it if necessary by going to your project, options and clicking on ‘GitHub WebHook Status’. This brings you to a page where an overview of the uploaded files and current settings are given.


That’s it! Your project is now linked to a GitHub repository. In a next blog, I will show how an implementation guide can be made using Simplifier. Feel free to give any feedback by using the feedback button located at the top of the page in Simplifier.

Clinical research enters the sharing economy with #FHIR

The famous examples of the sharing economy are, of course, Airbnb, Uber, BlaBlacar, Peerby etc. A less prominent example is Sync for Science. In Sync for Science patients share their medical data with clinical researchers. The idea is brilliant and simple: more patients in trials, more data points, less cost, less burden on the healthcare system. Just what is needed for research in precision medicine. No wonder the US Government launched Sync for Science to support its Precision Medicine Initiative.

Standardization is a key component of Sync for Science. The people involved in Sync for Science chose for the SMART on FHIR approach of open FHIR APIs. No new standards, stick to where the health IT market is heading, which means the FHIR data model, the REST protocol for data exchange and OAuth for security.This is the set of standards that participants in the Argonaut project adhere to (you know, Argonaut, the US initiative to accelerate interoperability using FHIR). The list of participants in Argonaut is as impressive as it is US oriented. Europe is lagging behind.

Luckily, Josh Mandel from Harvard Medical School, one of the driving forces of Sync for Science, will be in Amsterdam during the FHIR Developer Days 2016 (16-18 November). We asked him to elaborate on Sync for Science when he is here. We believe Sync for Science may well be a breakthrough project for FHIR and deserves to be followed in Europe.

More about FHIR Developer Days 2016, click here. President Obama on precision medicine and Sync for Science, click here. Obama is prevented from attending DevDays.

Apple ResearchKit, Android ResearchStack and #FHIR

One the exciting topics at FHIR Developer Days 2016 is the use of FHIR in medical research. Expert in this field is Pascal Pfiffner (bio), who will talk, among other things, about ResearchKit and ResearchStack. ResearchKit (Apple) and ResearchStack (Android) are open source frameworks for researchers to inform and consent patients, and to collect personal health data from participants in trials. ResearchKit/ResearchStack have out-of-the box functionality for patient consent, surveys for Patient Reported Outcomes and collecting health data from sensors in the phone or devices connected to the phone.

However, ResearchKit/ResearchStack have no facilities to integrate this data further upstream, e.g. to the EHR of the doctor or the system of the researcher. This is where FHIR comes into play. Pascal Pfiffner’s research in this realm has been focused on a standardized way of integrating ResearchKit/ResearchStack data with back-end systems, using FHIR. He calls this C3-PRO: the Consent, Contact, and Community framework for Patient Reported Outcomes (http://c3-pro.org).

During FHIR Developer Days Pascal will elaborate on the progress of his team in this field and facilitate developers during a hackathon session focused on medical research.


The architecture of C3-PRO

For more information, here is the link to the track.


SMART on FHIR and the Personal Health Record

The PHR is the holy grail of health IT. Whereas the EHR belongs to the doctor, the PHR – the Personal Health Record – belongs to the patient. The PHR combines your own data and data from your healthcare providers into one single overview, which you can share with physicians of your choice.

In May, during eHealth Week in Amsterdam, the Dutch patient federation NPCF (with support of the government) launched a project to create a PHR specification framework. This is a set of requirements any Dutch PHR will have to comply to. These include an infrastructural specification, judicial and financial arrangements, and the format of the data that is being shared.

Another important part of the specification is the way third party apps can access (read or write) data from a PHR. Based on one national open API, third party apps will integrate with any PHR without having to conform to a proprietary API each time they want to integrate with a new system.

One challenge here is how to give which app access to which part of the data? And what rights do they get? This is the same problem that EHR’s currently face. They want to open up their system, but only to trusted apps, and only those pieces of data that a particular app or person has the rights and needs for. In the US, major EHR vendors conform to the guidelines of SMART on FHIR for this purpose. Last Friday David Hay posted a blog about SMART on FHIR. In a nutshell: SMART on FHIR is a generic, standardized solution for apps running in an EHR. Any EHR.

To make it easy for developers to get started building apps based on the SMART standards, open source libraries are available that simplify and streamline the use of these standards in real world apps. Currently, libraries are available for HTML5/JavaScript, iOS and Python. This would be great for PHRs as well, since they face these exact same issues, and will now have a great way to safely open up their data to third party applications.

If you want to know more about SMART on FHIR, visit FHIR Developer Days 2016 in Amsterdam from 16-18 November. DevDays will host a specific SMART on FHIR track that focuses on app integration with the EHR according to the SMART on FHIR concept. Josh Mandel from Harvard Medical School / Boston Children’s Hospital (the inventor of SMART on FHIR) will explain the principles of SMART on FHIR and guide a hacking session. Two separate hacking sessions within this track will focus on app integration in the Epic and Cerner EHRs. These will be guided by interop experts from Epic and Cerner.