Atmolytics Release Notes v3.07

Version 3.07 Latest Features and Functionality

This document describes the additions and changes in functionality to Atmolytics in version 3.07 of the software. This release note describes changes to Atmolytics since V3.06. For Atmoforms customers, this release is compatible with V3.07.

A note about terminology

Atmolytics enables organisations to set the terminology used in the application to what they are most familiar with. For example, one organisation’s patients, admissions and reports may be another organisation’s service users, involvements and explorations.

Your organisation might use different terminology in their implementation of Atmolytics. In these release notes, we’ve used the terminology patients, admissions/visits and reports throughout.

1 Enhanced Map Insights

Work was undertaken to improve the performance of the rendering and processing of map insights as well as introducing the support for multi-level geographical location data summaries.

Prior to the change much of the calculations were carried our within the front-end code, this has been moved to server side processing and as such the installer was also updated to import the geographical location boundary data to the application data shards.

2 Data Export on screen

The output of Data Export reports can now be viewed from within the report output screen in Atmolytics. The previous content of the Results tab has been moved to a new Cover sheet tab, with the Results tab now instead presenting the user with a table containing the results of a selected dataset:

screenshot of coversheet page

Screenshot of results page

The table includes controls for restricting the visible set of rows to a smaller subset for easier scrolling, and for scrolling directly to a specified row number:

restrict from row x to y option

The data can be sorted by clicking the heading for the column you wish to sort by. Clicking the same heading again will reverse the sort direction:

Data output

All columns are sorted as text, which may lead to unexpected results when sorting by e.g. a numeric field

The visible dataset can be changed by using the Cohort and Export dropdown fields above the table:

Export reports option dropdown menu

Datasets with subforms can be expanded so the subform data can be viewed as well:

Dataset subform option in menu

Note: reports must be re-run in order to enable the viewing of subforms.

For exports containing more than 150,000 rows, only the first 150,000 rows will be viewable in the report output UI, and any sorting will only apply to those first 150,000 rows (this number is configurable in the web application’s config file):

Information in toolbar highlighting restriction

Exports can be downloaded either from the cover sheet as before, or from the Results tab using the download button on the Export dropdown button:

Download icon on export toolbar

A new Download Data Files permission has been added to the system, to make it possible to ensure only selected roles can download exports, with the rest only able to view the exports in browser:

Download data files opinion in default role menu

3 View Identifying Data

A permission to view patient identifying data in the report output for a particular role has been added in Atmolytics. It can be toggled from the Key Permissions Section.

Key permissions option in toolbar

If permission is enabled the patient identifying data can be viewed - in this case the DateOfBirth :

Rows showing patient data

If permission is disabled the patient identifying data cannot be viewed - in this case the DateOfBirth :

Rows showing patient data

Bug Fixes

   
Reports Data Export - Field values containing double quotes in the exported CSV would not be displayed correctly when opening in Excel. This has been corrected by altering the report to “escape” quotes within field values. Reports will need to be re-run in order for the fix to apply.
Reports Data Export - Where a multiple-files export containing a form with subforms was run, the exported ZIP containing the CSV files for the main form and its subforms could end up with more than one CSV file with the same name (if the same subform was used on more than one question in the main form). This has been corrected by altering the report to include the parent question ID in the subform CSV filenames. Reports will need to be re-run in order for the fix to apply.