avatar   wardweistra  

Here's a long list of what was released this week with Simplifier 31.2! Any questions? You can reach us via the FEEDBACK button above or simplifier@fire.ly.

You may not notice the main work behind this release directly, but we are now capturing the amount of views and downloads on all FHIR entities (packages, projects, resources, guides, organizations). This follows the start of tracking of FHIR package views and downloads last October, and based on this data we are refining our Simplifier search to show you the most used FHIR content first. This valuable information will also be surfaced directly to our users later, so you can track (and show to your stakeholders) how popular your work is.

Jurisdictions for packages

FHIR packages support adding a jurisdiction; generally a country for which it is relevant. From this release we will prefill the package jurisdiction for any newly created package based on the jurisdiction selected in your project. Not happy with that one? You can overwrite this with any package jurisdiction defined directly in the package.json file.

Release date placeholder

We added a placeholder for the release date of your Implementation Guide to be used in guide pages or your custom template. Insert it with {{publish-date}} or set your own date format with {{publish-date, format:yyy-MM-ddd}}.

Want to set the publish date or date format manually for a page? You can do so with these variables in your front matter (the part of your Markdown page above the --- line):

  • publish-date: 2024-01-01
  • date-format: yyy-MM-ddd

Rendering improvements

Other fixes

  • Package version numbers can now contain a + sign, to comply with https://semver.org/#spec-item-10
  • When going to a package page without specifying a version, we will take you to the latest version. This now aligns with the label latest on the package versions, including ignoring any newer unlisted versions.
Other news from Firely
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.
Ward Weistra 🔥
New quality control rules, markdown rendering, major infrastructure upgrades, and improved package publication, along with a new year-based versioning system.
Ward Weistra 🔥
A marketplace for healthcare knowledge encoded in FHIR and an overview page for every country publishing FHIR models.
Jay Salvemini
Learn key FHIR terms and concepts with our comprehensive FHIR Glossary, essential for navigating the complex FHIR landscape.
Rob Langezaal
Better handling of preferred file format (XML/JSON), faster loading time for projects with large dependencies and support for JSON output preview.
Ward Weistra 🔥
You may not notice the main work behind this release directly, but we are now capturing the amount of views and downloads on all FHIR entities (packages, projects, resources, guides, organizations).
Martine Berden
To support the fast-growing demand for FHIR solutions in the US, we have scaled up our presence by establishing a new company: Firely USA Inc.
Els van bergeijk
Two new free Firely e-learning courses available, including FHIR Profiling Introduction