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.

Usage tracking and Search

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

• We added a button to show the common elements that are hidden by default, just like in Forge:

• Added rendering of which language a designation in a ValueSet comes from:

• Now rendering OperationDefinitions and CodeableReference in R5:

• Now rendering additional bindings from the Additional Binding extension:

• Added a dedicated rendering for MessageDefinitions.

• Added a mouse-over message explaining why some extensions can be expanded in-line and some cannot (when they are inherited and not changed):

• And finally, many improvements to CapabilityStatement and other resources, based on your feedback!

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.