Trifolia Workbench

Version 4.2.0

Released on Wednesday, Oct  5, 2016

Open-Source Authentication

The existing Active Directory and custom HL7 authentication has been replaced with a generic authentication method (OAuth 2.0). OAuth is an open standard for authorization, commonly used as a way for Internet users to log in to third party websites using their Google, Facebook, Microsoft, GitHub, etc. accounts without exposing their password.    

As part of this migration, all existing Trifolia user accounts have been added/imported to the new OAuth Trifolia directory. Existing Trifolia users will receive a Password Reset link via e-mail that will allow them to use their Trifolia credentials when logging in using the Auth0. Clicking on the link in the email will direct the user to auth0.com and prompt the user to create a new password for your Trifolia account.    

When users click the "Login" option in Trifolia version 4.2.0, they will now see the Auth0 login form. Existing users can use their Trifolia credentials to login, and pre-existing permissions to implementation guides, templates, value sets, code systems, etc., will persist. Each authentication method (Facebook, Microsoft Account, Username/Password, etc.) represents a separate user in Trifolia, with separate permissions. In the future, Trifolia may support linking these multiple authentication methods to a single account.

Trifolia open source Github support request

Three options are now available for support requests, that are configurable

•     JIRA, when JIRA is configured and enabled
•     Email, when a support email address is specified
•     If a support request is initiated in Trifolia, but JIRA is not configured and enabled, and a support e-mail address is not configured, a redirect URL will

          be opened in a separate window to allow users to log a ticket in GitHub.

Lantana's installation of Trifolia (https://trifolia.lantanagroup.com) re-directs all users to the Github Trifolia repository's issues page.

Remove association between User and Organization

Users and groups are not organization-specific; they are now managed individually. Each user can have their own groups that they can assign members to. Any user can request to join any group.

When editing an implementation guide, the user no longer needs to select an organization prior to selecting a user/group; searching is performed globally and returns any matching user or group.

Group disclaimers

Group Disclaimers can now be added in a new option called My Groups when the logged-in user clicks on their name.  Users can see disclaimers for groups they are associated with by clicking "Disclaimers" from the Help menu.

Identifier/Base identifier field for Implementation Guides

In FHIR implementation guides, it is important to have a base identifier for the implementation guide that each profile follows. A new field has been added to the implementation guide editor which will require identifying a base identifier for all existing implementation guides.

FHIR data type

The MS Word and web-based Implementation Guide exports will now include a column for the "Data Type" of the constraint in the "Constraints Overview" tables.

FHIR build export

Trifolia has a new option under Export XML/JSON to export a "FHIR Build" package. The "FHIR Build" package option is only available for FHIR-based implementation guides. The export produces a ZIP file that includes all files pre-configured to run the FHIR IG Publisher.

Development Log