Teams: User Management for FHIR Projects Made Simple

Many large-scale organizations, such as SAP, KBV, and NHS Digital, are using Simplifier.net to host their FHIR development and publishing workflow. With a growing number of projects and packages published by these organizations, the user management side of the process can become challenging. To overcome this, we are introducing a new feature called Teams!

Teams in Simplifier.net allow you to set up access levels once for a Team and reuse these settings for many FHIR projects and packages. The Team members will have read, write or administration rights on these resources, according to their rights with the Team.

This change allows for multiple new important use cases:

1. One place to manage access for many resources

First of all, Teams allows you to reuse the access settings of one project and apply them to many other projects and packages. Instead of managing readers, writers and admins for every individual entity, you can directly manage this once on Team level.

2. Publish packages from a private project

With Teams we added explicit access rights for both projects and packages. You now have the option to keep your Simplifier.net development project private, while still publishing public, stable packages from this project. This can be useful when you don’t want anyone to accidentally use your in-development resources or if you are not ready to share in-progress resources publicly.

Similarly, public projects can test their package release process by first publishing to a private package until they are completely happy with it.

3. Publish one package from multiple projects

Another use case we are enabling is the creation of new releases for one package from multiple Simplifier.net development projects. This allows different projects to represent different branches of your FHIR specification (maybe even linked to different branches of the same GitHub project) and still their releases end up under one package name for your customers.

Why would you need this? Imagine you have one major version of your specification in production and you need to continue bringing out small improvements for it. At the same time, you are also developing the next major release of the standard and want to bring out beta-versions of that to already start collecting feedback.

Just go to your project’s Packages tab and create a new version for any of the packages you have the rights to edit.

Setup your Teams

With every new project you can create a new Team, or reuse a Team you have already set up. Our enterprise customers can also create their Teams from their Organization page, on the Teams tab.

However, it is likely you already have plenty of Teams. With the introduction of this feature, we have made sure to maintain your current access settings, so we added one Team for each of your projects. Now is the time to simplify this authorization situation!

Organizing your access controls is easy:

• Just take a Team that you want to use as a basis and give it a great name. For example, the ‘ACME Core Profiling Team’.
• Now go to each project or package for which you want to have the same access settings and update their Team to the one you have created.

• Finally, remove the Teams that you no longer need! If there are projects or packages still managed by the Team you will not be able to delete it. Just transfer those items to another Team to continue.

You are now ready to get started with Teams! We hope you will enjoy our streamlined access management experience on Simplifier.net.