Version 4.4.0
Version 4.4.0
Released on Wednesday, April 26, 2017
FHIR Improvements
The schema used by Trifolia for "FHIR_Latest" is updated with the schema from FHIR STU3's recent publication. In the future, the Implementation Guide Type "FHIR_Latest" will be renamed to "FHIR STU3" and a new implementation guide will be created for "FHIR_Latest" that represents the latest build of FHIR.
The fixed[x] and pattern[x] fields are included in imports of StructureDefinition resources.
Default field selection for exports
The "Save As Default" functionality for "Export templates/profiles to MS Word" was not saving all fields. This is now fixed so that when you indicate to save your preferences as default, the selected templates/profiles and the sort order are persisted.
Implementation Guide Editing
Permissions management on the "Edit Implementation Guide" screen has been improved so that multiple users can be added with less effort. The "General" tab has been re-organized into two separate columns so that more fields can fit on a single screen, reducing the need to scroll to edit the fields.
When versioning an Implementation Guide, the identifier of the IG is copied to the new version.
Exporting templates/profiles to MS Word
The "Save as Default" functionality is improved so that it remembers the sort order of templates/profiles within the export, and the templates/profiles selected for export.
Template/Profile Editing
The author of a template can be changed in the template/profile editor.
A template/profile cannot reference itself as an implied template/profile anymore.
Bug fix to removing single-value binding from constraints.
Schematron Export Improvements
Several of improvements have been made to Schematron exports including:
- Minor performance improvements
- Single-value bindings within branches are tested now
- Specialized rule context for templates whose schema doesn't have the typical element used by the template predicate (ex: templateId)
- Manual Schematron is exported for primitive constraints SHALL constraints that are a child of a MAY constraint
Developer Improvements
Several improvements have been made to make it easier for developers to work on Trifolia, including:
- Using the latest version of Entity Framework, with code-first approach. This will make it easier to modify the database, and apply those modifications during installation. It is also be easier to setup new installations of Trifolia.
- Installation script improvements. Re-designing the installation script to automatically apply the database migrations, and to remove files that are no longer used by the application.
Development Log
Issue Type |
Summary |
Defect |
Versioning implementation guide does not copy identifier |
Defect |
Template Save does not display error when another template exists with same identifier |
Defect |
Branch within a branch produces incorrect Schematron rule context |
Defect |
Export to MS. Word - "Save As Default" not working |
Defect |
Display errors in user-friendly way |
Defect |
Export Templates to MS Word - Save as Default not saving unchecked templates |
Defect |
Binding does not delete once set |
Defect |
Template incorrectly allows itself as implied template |
Defect |
Schematron: Primitive SHALLs with manual Schematron are not exported when the parent is MAY |
Improvement |
Element with single-value binding within a branch does not test single-value |
Improvement |
Allow a template/profile's author to be changed |
New Feature |
Schematron US Realm addr/name etc. templates need manual search and replace contexts in the Schematron file |
New Feature |
Support multiple identifiers for value sets |
New Feature |
Easier to add permissions to an implementation guide |
New Feature |
Import fixed[x] and pattern[x] from FHIR StructureDefinition resources |
New Feature |
Allow a template/profile's author to be changed |
New Feature |
Allow zip package to be downloaded including both Schematron and Vocabulary XML |