3.8.0 (9-17-2020)

Leaf version 3.8.0 adds some exciting new features, and requires an upgrade from .NET Core 2.2 to the .NET Core 3.1.x Runtime.

New features

• #364 - You can now configure Leaf to either run Find Patients queries using the past Common Table Expression, or CTE approach, where Leaf wraps each panel's query in a single CTE, or instead run individual queries for each panel in parallel. The latter can be useful in cases where you find patterns of one particularly expensive panel's query slowing down the entire CTE.

For example, given the hypothetical query:

Leaf would generate SQL similar to (formatted for readability):

Note that in either case, the number of patients found is exactly the same but the strategies to find the cohort are different. Using the CTE option, Leaf combines all panel queries into a single query and leverages the SQL engine to find the intersect of the queries. Using the Parallel option, Leaf runs each query in parallel (or technically, concurrently) and map/reduces the results of each query to find the cohort in the Leaf API.

These options can be set in a new subsection of the appsettings file, under Db.CLin.:

• #4 - CSV exports are now available! A long-requested feature, Leaf can now export directly to CSV, in addition to the traditional REDCap export. Leaf will generate a CSV file for each Patient List dataset loaded.

• #359 - The "@<scope>" portion of the username exported to REDCap can now be omitted by setting the Export.REDCap.IncludeScopeInUsername setting to false:

Bug fixes

• #358 - If an ampersand ("&") appeared in the body of the data exported to REDCap, REDCap would throw an error when deserializing from JSON. Ampersands are now converted to empty spaces.

Upgrading to 3.8.0

1. IMPORTANT - Leaf 3.8.0 now requires the .NET Core 3.1.x Runtime, which must be installed and replace the previously used .NET CORE 2.2.
2. Client app and server API - Download and deploy the latest client and server compiled files under Assets, included in this release (or compile on your own as described in the Leaf installation instructions), making sure to first remove any previously deployed instances.
3. Database - execute the 3.7.2__3.8.0 database update script on your Leaf application database. Note that in this release there are no structural database changes; this simply updates the Leaf version.