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
Ward Weistra 🔥
The latest Forge release introduces support for extensions on element definition properties, like the Translation and Obligation extension. Further improvements include more project synchronization control via the .simplifierupload file, and numerous UI enhancements that collectively streamline the FHIR profiling workflow.
Ward Weistra 🔥
Starting June 1st, we're updating our Simplifier license plans to bring more flexibility and features, including the introduction of a new 60-day free Professional Plan trial. Learn what these changes mean for you and what new features are being introduced.
Ward Weistra 🔥
Join us on our next product update webinar showcasing all the latest changes across Simplifier.net, Forge, and Firely Terminal. We will be demonstrating the new online resource editor, private FHIR packages and explaining the 60-day free trial.
Ward Weistra 🔥
See the new FSH editing capabilities in Simplifier's Resource Editor! And learn how to navigate the choice between Forge's visual modeling and FSH's code-based approach for your FHIR projects.
Ward Weistra 🔥
We just dropped a game-changing suite of tools for FHIR developers, including private package feeds and a zero-install FHIR Shorthand editor that promises to make FHIR modeling a breeze. Whether you're a seasoned FHIR expert or just getting started, these powerful new features might just revolutionize your healthcare data modeling workflow - read on to discover how.
Ward Weistra 🔥
And changes to installing and publishing private packages via Firely Terminal
Ward Weistra 🔥
Learn how the Dutch centralized cancer registry is using FHIR and Simplifier.net
Ward Weistra 🔥
Learn from Dutch and German cancer registries how they streamline data collection from EHRs, plus get latest FHIR insights from Firely CEO (free, online).
Ward Weistra 🔥
Most mistakes in FHIR data modeling are easily resolved in a later iteration of your guide. But there are some that are better done right the first time. One of them? FHIR canonical URLs, the unique identifiers for your models.
Jay Salvemini
The Product team showcase all the latest updates in FHIR, Simplifier.net, Forge, and Firely Terminal in our October webinar.