avatar   wardweistra  

Here's a long list of what was released this week with Simplifier 31.2! Any questions? You can reach us via the FEEDBACK button above or simplifier@fire.ly.

You may not notice the main work behind this release directly, but we are now capturing the amount of views and downloads on all FHIR entities (packages, projects, resources, guides, organizations). This follows the start of tracking of FHIR package views and downloads last October, and based on this data we are refining our Simplifier search to show you the most used FHIR content first. This valuable information will also be surfaced directly to our users later, so you can track (and show to your stakeholders) how popular your work is.

Jurisdictions for packages

FHIR packages support adding a jurisdiction; generally a country for which it is relevant. From this release we will prefill the package jurisdiction for any newly created package based on the jurisdiction selected in your project. Not happy with that one? You can overwrite this with any package jurisdiction defined directly in the package.json file.

Release date placeholder

We added a placeholder for the release date of your Implementation Guide to be used in guide pages or your custom template. Insert it with {{publish-date}} or set your own date format with {{publish-date, format:yyy-MM-ddd}}.

Want to set the publish date or date format manually for a page? You can do so with these variables in your front matter (the part of your Markdown page above the --- line):

  • publish-date: 2024-01-01
  • date-format: yyy-MM-ddd

Rendering improvements

Other fixes

  • Package version numbers can now contain a + sign, to comply with https://semver.org/#spec-item-10
  • When going to a package page without specifying a version, we will take you to the latest version. This now aligns with the label latest on the package versions, including ignoring any newer unlisted versions.
Other news from Firely
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.
Ward Weistra 🔥
New on Firely: a deep‑dive blog and whitepaper on how FHIR Obligations sharpen the long‑standing Must Support flag into explicit, actor‑specific, and machine‑readable conformance rules—moving interoperability from narrative intent to testable behavior in real‑world FHIR implementations.
SUBSCRIBE