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
Ward Weistra 🔥
R4B and R5 are now available throughout Simplifier, Forge and Firely Terminal.
Martine Berden
The Call for Presentations for HL7 FHIR DevDays2023 is now open. Got a FHIR-related topic you think would interest your peers? Submit your proposal before February 1
Rob Langezaal
Forge is now officially supports the R4B FHIR release and can help you migrate from R4 to R4B. All versions now support opening and fixing resources in bulk.
Ward Weistra 🔥
Improvements to the Guide editing experience, PlantUML directly in your pages and a truck load of smaller fixes.
Rob Langezaal
Forge now supports Quality Control (already available in Simplifier and Firely Terminal) to improve the quality of your FHIR projects. In addition, you can now see all the file types supported by Simplifier in the project list view.
Ward Weistra 🔥
Join us on June 6-9 in Cleveland or online. These are the talks that focus on Forge and Simplifier.net →
Rob Langezaal
This minor Forge release mostly fixes a bunch of bugs, but there are some feature improvements as well, like making it easier to get your FHIR Shorthand files on Simplifier and adding new elements to logical models.
Marco Visser
Read all about the breaking changes, code clean-up, and code improvements we implemented
Matthijs van der Wielen
Synchronize your Simplifier projects with your local folders in Forge with one click.
Matthijs van der Wielen
The Firely Team is happy to announce the latest update to Firely Server.
SUBSCRIBE