avatar   wardweistra  

With the latest Simplifier releases we've caught up with all the latest FHIR releases and made it easier to generate example instances and capture feedback from people and validation algorithms.

R4B and R5 in Simplifier, Forge and Firely Terminal

All of our modelling tooling now supports the latest FHIR versions. Start your R4B or R5 Simplifier project, edit it in Forge and validate it in Firely Terminal.

Example generation

Leveraging our YAMLGen language and playground we are now making example generation available to all FHIR versions. Go to any Profile (StructureDefinition that constrains another resource) and hit the Tools button on the top right. You will see multiple options for generating an example resource:

The first two options will (if you have edit rights on the project) directly create a filled or empty example instance in an editor, where you can save it directly to your project. The third option will bring you to the YAMLGen playground to start fine tuning your own example:

Once you're happy with the generated resources you can store the YAML part as a something.gen.yaml (like this example) file in your project and use it with YAMLGen in the Bake pipeline or in Firely Terminal (yaml-gen command). Or you can just copy the JSON results and save them like any of your other example instances into your project.

Issues upgrade: Quality Control results stored, new looks and custom issue statuses

Quality Control has always been a powerful way to check your resources for validity, both with our validator and custom FHIRPath rules. Now we've added a few ways to make that even more powerful:

  • We now store the issues coming out of QC in the Issues tab of your project. Easily work through them in your own time or delete them all at once. And if you fix any of the problems in your resources, the Issue will be closed automatically on a next QC run.
  • Beta: You can now use the Java validator on your project, to catch even more issues. Create a custom QC file and use the java-validate action to try it now.
  • And finally, we've introduced custom statuses. Currently only we can configure those for you, so if you need this, reach out!

Below you can see how UK Core and Canada Baseline are using custom issue statuses to capture feedback from the public:

And more

  • Do you prefer to keep your editable private and only make published guides visible for everyone? Now your published guides will show up on the Guides tab of your 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