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
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
Ward Weistra 🔥
By using variables in dynamic tables, you can now create consistent pages with widgets and tables, customized for every resource.
Ward Weistra 🔥
We look forward to collaborating with you on many more FHIR specifications in the new year.
Els van bergeijk
This eBook provides a complete overview of the relevant US healthcare regulations, implementation guides, and technologies and will help you understand their scope.
Ward Weistra 🔥
An update on new features for guides, invites and canonical claims and a resolved security issue around private packages.
Martine Berden
Execute and evaluate CQL, Clinical Quality Language, on FHIR resources