v1.5.0
Release 1.5.0
Project/Context
After logging in, users must now select a project (an ImplementationGuide) to work with prior to seeing any Browse screens. All screens (except Browse > Other Resources) have been modified to respect the context of the project the user has selected, and will only show resources that are related to that project. When creating new resources or importing resources from an external source (such as a file on your computer), they are automatically associated with the project that you are working on.
Note that permissions still apply; if you don't have permission to access a resource, you won't see it in the browse screens.
Authentication
Behind-the-scenes, how ToF handles authentication has changed quite a bit. ToF used to be bound specifically to auth0.com so that only auth0.com can be used as an authentication provider. Now, however, we have replaced that functionality with more generic functionality to allow any OAuth2-compatible authentication provider to be used with Trifolia-on-FHIR. We have specifically tested authentication with auth0.com, KeyCloak, and Okta.
Additionally, we have added support for an "administrator" role that allows you to configure specific users to be an administrator of ToF. These administrators have complete access over the installation of ToF. More information on configuring various authentication providers and how to setup administrator users can be found on the ToF GitHub repository's WIKI: https://github.com/lantanagroup/trifolia-on-fhir/wiki/Authentication.
Paging "Other Resources"
Prior to this release, the screen would only show the first 10 resources stored on the server. Now, users are given paging options when there are multiple pages of resources.
Profile Mappings
Enhancements have been made to the "Edit Profile" screen that make it easier for users to construct mappings within the profile.
Development Log
|
Key |
Type |
Summary |
|
New Feature |
Select Project/ImplementationGuide Context |
|
|
New Feature |
Add an administrative role that overrides all permissions |
|
|
New Feature |
Make authentication generic to OAuth 2.0, not bound specifically to auth0.com |
|
|
Defect |
Profile editor doesn't allow expanding PlanDefinition.action.action |
|
|
Defect |
Change the element definition panel's alias property to repeat (allow multiple) |
|
|
Defect |
Cannot set value set binding on R4 profile's element |
|
|
Defect |
"Add" button for R4 capability statement REST tabs doesn't work |
|
|
Defect |
Can't expand a brand new slice |
|
|
Defect |
ServiceRequest vs. ServiceDefinition for CapabilityStatement > REST > Resource > Type |
|
|
Defect |
Multiple publish boxes on published implementation guide's main page |
|
|
Defect |
Change editor to only display constraints in the current profile's differential, regardless of base profile |
|
|
Improvement |
User interface allows profiling fields that shouldn't be profiled |
|
|
Improvement |
Add support for paging in the "Other Resources" screen |
|
|
Improvement |
Element mappings reference profile mappings |
|
|
Improvement |
Automatically delete IG references when deleting resources |
|
|
Improvement |
Automatically set ID of new resources to the leaf/end of the URL |
|
|
Improvement |
Add "supported profiles" to R4 capability statement editing screen |
|
|
Improvement |
Getting latest ig publisher doesn't work due to HL7/FHIR process changes |
|
|
Improvement |
Automatically associate new resources to IG in context |