The FHIR train never stops and neither do we. That’s why we’ve significantly improved your FHIR editing and publishing flow. Here is an overview of everything that’s new in our Simplifier FHIR tool suite:

## Updated to the latest FHIR version

Simplifier.net, Forge and Firely Terminal (formerly Torinox) now all support the latest FHIR versions: FHIR 3.0.2 and 4.0.1. See [the full overview of supported FHIR versions here](https://simplifier.net/docs/Forge/Knownissues).

## Better integration between Forge and Simplifier

Both Forge and Firely Terminal now allow you to log in with your Simplifier account. This enables you to easily synchronize your content from your local computer with your Simplifier FHIR project.

## Packages everywhere

FHIR Packages are the answer to all your FHIR versioning problems. Build on stable versions of the projects you depend on and, in turn, give your customers a stable version of your resources to build on. With packages, you version a set of coherent resources together, instead of needing to version them all individually. Our tooling is bringing support for packages everywhere!

### All the FHIR projects in the world, always up to date

We have worked with HL7 International to make sure you have access to all the most recent FHIR projects in the world via packages!

Even packages created outside of Simplifier are now always available to you, like the [core FHIR resources](https://simplifier.net/packages/hl7.fhir.r4.core) and [US Core](https://simplifier.net/packages/hl7.fhir.us.core). Together with all the packages created directly from Simplifier, like the [German](https://simplifier.net/packages/de.basisprofil.r4), [Norwegian](https://simplifier.net/packages/hl7.fhir.no.basis), [Dutch](https://simplifier.net/packages/nictiz.fhir.nl.stu3.zib2017) or the recent [UK Core profiles](https://simplifier.net/packages/uk.core.r4), they are available for use anywhere in our tools and on [our package server](https://simplifier.net/docs/package-server).

### Specify Dependencies for better project management

On **[Simplifier](https://simplifier.net/)**, specify the dependencies of your project on the project’s Dependencies page, like [here in our ACME demo project](https://simplifier.net/acmebaseprofiles/~dependencies). Select the packages containing the resources you are referring to and links from your profiles will point to exactly those versions of your parent resources.

In **[Forge](https://simplifier.net/forge)**, open a project folder and go to the Dependencies tab. Search on Simplifier for any package you need and ‘install’ it to your project. No more need for manually hunting all resources you depend on, all dependencies (and their dependencies) are downloaded automatically.

Finally, with the [command-line FHIR tool Firely Terminal](https://simplifier.net/downloads/torinox) you can create, install and validate against packages. It uses the same local package cache as Forge, so you never have to download a package version twice.

Note: If you are still depending on one of the previous `simplifier.core.stu3` or `simplifier.core.r4` packages, please change those to `hl7.fhir.r3.core` and `hl7.fhir.r4.core` respectively.

### Create your own packages

Ready to make a versioned snapshot of your project? Go in your Simplifier project to the Package page and create a new one. It will directly be available to anyone within the Simplifier and the full FHIR ecosystem.

## Other updates

You can now generate example FHIR instances based on your STU3 FHIR profiles:

> Simplifier can now generate [#FHIR](https://twitter.com/hashtag/FHIR?src=hash&ref_src=twsrc%5Etfw) example data from any STU3 FHIR profile on the platform!
>
> ↗️ Tools > Generate Empty Instance (to fill out yourself) or Generate Example (to let Simplifier make a start)
>
> Try it now on the [@HL7Germany](https://twitter.com/hl7germany?ref_src=twsrc%5Etfw) Base Patient: [https://t.co/LjwwjE5QPP](https://t.co/LjwwjE5QPP) 👥 [pic.twitter.com/qetkpdosTL](https://twitter.com/qetkpdosTL)
>
> — Ward Weistra (@WardWeistra) [December 18, 2019](https://twitter.com/WardWeistra/status/1207295952777699335?ref_src=twsrc%5Etfw)

And we’ve made file management easier with bulk deletion:

> Ever ended up with too many [#FHIR](https://twitter.com/hashtag/FHIR?src=hash&ref_src=twsrc%5Etfw) resources in your [https://t.co/ZhVQSdyMV4](https://t.co/ZhVQSdyMV4) project? 📂We've added a [#FileManager](https://twitter.com/hashtag/FileManager?src=hash&ref_src=twsrc%5Etfw) to easily find and delete unwanted files. [#NotGroundBreakingButPrettyUseful](https://twitter.com/hashtag/NotGroundBreakingButPrettyUseful?src=hash&ref_src=twsrc%5Etfw) 😉 [pic.twitter.com/nzKA7g974c](https://twitter.com/nzKA7g974c)
>
> — Ward Weistra (@WardWeistra) [February 12, 2020](https://twitter.com/WardWeistra/status/1227637481408954371?ref_src=twsrc%5Etfw)

Furthermore, we now hide validation errors that come from known issues in the official FHIR specification. We have also squashed the annoying 5003 Error “Cannot walk into unknown StructureDefinition” that impacted many of you. Sorry!

## What’s next?

We have some great new functionalities planned, including being able to refer to resources in packages from your Implementation Guides and bulk project validation. Most of all, we’d like to hear from you. So please [reach out to me](mailto:ward@fire.ly) with your suggestions!