avatar   matthijsvanderwielen  

Guide Versioning

With this release, guides are now defined by a folder structure and a central guide.yaml file. As a result, guides are now easy to copy to the same project or even to a different project (there is a button for that!). As a consequence, with this change it's also easy to have multiple versions of a guide.

This was a very hard and complex project, due to ensuring full backward compatibility, the size of guide end guide editing as an existing feature, and correct working and testing of migration tooling.

Because of it's impact and complexity, the feature is released as beta, but we (support) will already start guiding some of our customers with production level guides.

Quality Control

We added a snapshot evaluator for Quality Control, that evaluates if snapshots can be correctly generated on any structure definition (within a given filter).

This is an example you can add to your QC rules:

- action: snapshot 
  files: profiles/*.xml

For more information on Quality Control, please read our blog post. This blog post about Quality Control takes you step by step on how to set up your own rules to validate full FHIR specifications in one click.

FQL

With this release, also comes and upgrade to FQL, for custom tables in implementation guides. FQL 3, which you might already know from Firely Terminal, brings a lot more syntax expressiveness, like order by (desc), group by repeating select, group unwrapping, and node-level join. For more information, see our FQL documentation

Technical upgrades

We migrated to .NET 5 and ASP.NET 5, which gave us a big performance boost in key areas, an improved GC, and a smarter and adaptive JIT.

Note: Specifically the close to factor 20 perf improvement of RegEx parsing, which we use for guide page rendering.

With this release we also switched to endpoint routing, which brings a big performance boost and reduced GC in resolving urls.

Preparation

While building this feature, we also had to do a lot of preparation for features that are not yet in this release, but will be in a future release. Among these are guide publishing (static and versioned), topics (linking resources to pages), templates (one page for many resources), and documentation bridges (making it possible to link a guide to a package or a project).

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