avatar   wardweistra  

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:

Dependency checking with Quality Control

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 fixed instead of being affected by a pattern.

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
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.