Trifolia Workbench

Version 5.0.5

Released on Monday, October 2, 2017

VSAC Integration

We integrated Trifolia within VSAC to allow users to import value sets from VSAC. A new button is available in Browse > Terminology that allows users to specify an OID to import from Trifolia.

The ability to import from VSAC and view implementation guides containing VSAC-imported value sets requires a license to the UMLS, issued by the NLM.

See the help documentation's Getting Started > User Profiles, and Importing > Terminology sections for more information.

Export UI re-design

As a result of the VSAC integration, the Export screen(s) have been re-designed, and consolidated into a single Export screen.

• A more consistent UI across the various export formats
• Allows saving default settings (if permitted by implementation guide permissions)
• Always performs validation of the design and structure of the implementation guide, which includes ensuring the user has a license to UMLS if the implementation guide contains VSAC content

Implementation guide test status

In the free-to-use installation of Trifolia (https://trifolia.lantanagroup.com) there are approximately 40 implementation guides with "test" in their name. As a result, we felt it was appropriate to create a separate workflow status for implementation guides to be labeled as "test". When creating an implementation guide, users have the opportunity to indicate that the implementation guide is a "test" implementation guide, and not intended for use outside of the designer's discretion. If at a later point in time the designer of the implementation guide decides the implementation guide should be shared with others, it can be transitioned to other statuses (such as "draft") via the "View Implementation Guide" screen's "Workflow" drop-down.

Multiple contained templates/profiles

A constraint can now reference multiple templates/profiles. This is inspired by FHIR's native structure for supporting multiple "types" of resources referenced in an element/constraint. The template editor's constraint panel now has a list of contained templates/profiles, that can be added to or removed from.

Patch Notes

• MS Word export incorrectly references templates/profiles in the context table which are not included in the export
• Bug in saving templates where "existing" references in constraints aren't being found.
• Bug where changing identifier of template does not update references to it
• Modifying template editor so that it uses a dash (-) for the bookmark white-space replacement when working with a FHIR profile due to a warning message suggests that dash (-) be used instead of underscore (_).
• Hiding link to "Add contained template" if the constraint properties fields are disabled
• Cleaning up ValueSet FHIR export so that it properly shows compose vs. expansion. Exports <compose> when Trifolia is the tool that authored the value set. Exports <expansion> when the value set is imported
• Creating FHIR Build package with lower-case resource type directory names under "resources" directory
• Bug in MS Word generation where the contains column of the context table is never filled in

Development Log