We are excited to announce the release of Simplifier 31.4, packed with technical improvements smaller features to enhance your experience. Here’s a closer look at what’s new in this release:
Quality Control Enhancements
We've introduced new rules and filters to improve quality control:
- unique-filename: Checks for duplicate files in package builds.
- assert: Can now check for any issue or issues of specified severity (warning, error, or info).
- New predicates: exists, min, max, count, and cardinality.
- manifest: Evaluates the correctness of
package.json. - dependency: Provides a full analysis of your dependency closure, including upgrade suggestions.
Here is an example of the new rules for checking the package manifest and package dependencies, as part of the minimal validation rules:
We've also made all rulesets used by Simplifier publicly visible in our Assets project, like these minimal rules. (Note that it is not yet guaranteed that Forge and Firely Terminal use the exact same version of the rules.)
Rendering Improvements
- Markdown Rendering: Now available in all rendering components.
- Enhanced rendering of pattern elements: When a pattern was set on a parent element, child elements were mistakenly rendered as being
fixedinstead of being affected by apattern.
Other Enhancements
- YamlGen: Now generates random content for backbone elements.
- FQL: Can now filter on categories "Profile", "Example", "Extension".
- FQL syntax update: Correctly parses the FhirPath expression
(<expression>).not(). - Numerous textual improvements and fixes.
- Guides markdown frontmatter (YAML) IntelliSense: Typing
canonical:will trigger autocomplete for the canonical URLs in scope. - Improved package publication, allowing users to upload/publish packages directly through the Simplifier API.
Versioning Update
Starting from the next release, our versioning will follow the current year followed by the release number. The next release will be 2024.5.
Stay tuned for more updates and improvements in the upcoming releases. Thank you for being a valued user of Simplifier!
See the Simplifier release notes in the Docs for the full story.
Other news from Firely
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.