avatar   wardweistra  

In this release we added support for showing translations and added many more widgets to your Implementation Guide editing!

Translations

FHIR has multiple functionalities to help users translate their resources in multiple languages. On the resource level the lang attribute specifies in which language the attributes of a resource are documented. With the Translation extension an author can add additional translations in other languages to elements that are translatable. With this release we will now parse those translations and show a language switcher for every detected language: As you can see, the resource shown above has a Dutch translation (nl-NL) which will show the user the Dutch translations of the Short Description and Definition in the details panel. Below we will also show how to add translated renderings to your Implementation Guide.

New functionality in the guide editor

Besides translation, we are also adding multiple long requested features to the Implementation Guide editor:

  1. An easy way to add tabs to your page with the <tabs> html code. Define your titles and their content to easily make this Tree / XML / JSON switcher.
  2. Also for FQL, you can now use HTML style tags, <fql>, to embed FQL code into your page. This will allow for more rendering parameters later.
  3. An easy way to show the differential / hybrid / snapshot switcher that you know from Simplifier resource pages. Just add the buttons parameter to your tree widget.
  4. In the 'front matter' of your Markdown page (the part between those --- lines) you can define parameters for your entire page. We already had support for defining the topic parameter for making stable page links. Now you can also define the subject of your page here: the resource name or canonical that this page is about. When you have done that your tree, xml en json widgets in the page will no longer need an individual parameter, making it a lot easier to create and maintain.
  5. And finally, we've also handed you control over how far the resource tree should be expanded by default! This can be handed directly to the tree widget, or can be set on the top of the page for all trees. Set expand to yes for full expansion, or choose the numeric expansion level of your choice.

With the lang attribute in tree widget you can also control which translation is shown, and this one too you can define on top of the page for all your trees at once.

Other updates

  • When editing the metadata expressions for your project (the FHIRPath expressions that decide what the title, description and URLkey of your project will be) you can now directly apply them to all existing resources.
  • You can now also spin up a full Firely Server from FHIR R5 projects on Simplifier.

See the documentation for the full release notes.

Other news from Firely
Ardon Toonstra
Simplifier now keeps every version of a package that your dependencies bring in and resolves your references predictably across them. This release also redesigns the guides overview and starts retiring DSTU2.
Ardon Toonstra
Earlier this year, we asked the Simplifier community how they use Simplifier, Forge, and Firely Terminal in their day-to-day FHIR work. First of all, thank you to everyone who took the time to participate.
Ardon Toonstra
Simplifier now runs entirely on Firely .NET SDK 6. This release brings a list of rendering improvements for your conformance resources, and consolidates our documentation in one place.
Ardon Toonstra
Forge 2026.2.0 upgrades the profiling engine to .NET 10 and Firely .NET SDK 6.2.1, adds support for the suppression extension, and speeds up loading of complex profiles. Quality Control now runs solely on the current Firely validator, and the Project view's Structure Type filter has been streamlined. Note that .NET 10 may need to be installed by your IT department on managed machines.
Ardon Toonstra
Simplifier.net now hosts country-specific results from the 2026 State of FHIR Survey, letting you explore how HL7 FHIR is being adopted in each participating jurisdiction.
Ardon Toonstra
This release lets you pin canonical references when creating a package, locking each one to the exact version it resolved to so your packages stay reproducible. Simplifier honours the version in a reference when resolving, with two new quality-control rules to help you pin safely. On top of that, the platform has moved to .NET 10, alongside a set of UI improvements and bug fixes.
Ardon Toonstra
The 2026 Simplifier User Survey is now open, and we need your input. Tell us which tools and features drive real value in your FHIR workflow, and where the platform can do better. It only takes a few minutes, and your response shapes what we build next.
Ward Weistra 🔥
Use this new skill to combine Firely Terminal with your AI-driven workflows to give your agent real tools to perform FHIR validation and not just guess.
Ward Weistra 🔥
This latest Forge 2026.1.0 release introduces significant updates, focusing on advanced modeling capabilities, more robust validation, and improved package management to enhance your profiling workflow.
Ward Weistra 🔥
The latest Simplifier.net release revolves around safety and productivity. While we have implemented new measures behind the scenes to protect accounts, we introduce important innovations for professionals in metadata management, validation and user-friendliness. In this note we explain the improvements and outline what they mean for your FHIR projects.