2019.5 Release Notes

PopMedNetTM Distributed Query Tool

Release Notes

Based on Release 2019.5



Releases

Networks UpdatedSentinelHDCPCORnet
Date of Release

11/18/2019

11/19/2019

11/12/2019

DataMart Client Updatenot required

not required

not required

Introduction

This release includes 

Enhancements


release notes
Loading...
Refresh


Bug Fixes


release notes
Loading...
Refresh

Known Issues



Issue
Workaround
Downloading Metadata Search results in Excel format may result in an error

Some requests may include an extra invisible character in a metadata field. This can occur if a piece of metadata was copied and pasted from another document into a metadata field of a request that appears in the Metadata Search result set. Excel cannot interpret the invisible character, so an error appears when the Metadata Search result set is downloaded from the query tool.

If you experience this error, please download the Metadata Search result set in CSV format. 

The DataMart Client will not run on a Windows 10 virtual session installed on a Linux machine

The DataMart Client is compatible with Windows 7 and newer. However, the PopMedNet team at HPHCI has limited ability to replicate this issue as our technology stack does not include Linux server.

 Therefore, we recommend that the DataMart Client be directly installed and used on Windows machines where possible.

Filters in the DataMart Client occasionally get stuckThe DataMart Client has three filter options: DataMarts, Status, and Dates.  Occasionally the filters will get stuck and will not change to the new selection.  This can be resolved by closing and re-starting the DataMart Client.  If re-starting the DataMart Client does not work, please contact the help desk for further instructions.
"Age as of last encounter" criteria will not execute against Oracle 11 databasesWhen creating a MDQ, the Investigator is given the option to determine how the patients' age is calculated.  However, one of the many options, to calculate based on patients' last encounter, does not work with Oracle 11 databases.  DataMart Administrators that run MDQs against an Oracle 11 database will receive an error when running an MDQ with that calculation.  This calculation works on the other supported RDBMS platforms such as, Oracle 12, SQL Server 14, SQL Server 16, PostGres 9.5, and Postgres 9.6
MDQ stratification for Observation Period does not execute against Oracle 11 databasesMDQs have the option to include stratifications of the results.  The only stratification that Oracle 11 databases cannot execute is the Observation Period stratification.  All other stratifications will execute against Oracle 11.  All other supported RDBMS platforms will successfully execute all possible stratifications. 
Checking for NULL ADMIT_DATEs in PCORnet Menu-Driven QueriesThe Observation Period term in PCORnet Menu-Driven Queries fails to check that ADMIT_DATEs are not NULL if both minimum and maximum dates are left blank when creating the query. To avoid this, always enter a minimum and/or maximum date when using the Observation Period term in PCORnet Menu-Driven Queries. This is expected to be fixed in PopMedNet 6.7.
Column resize issue on the home page in Chrome

This is a known issue with Kendo front end scripts and will be resolved when updated: https://github.com/telerik/kendo-ui-core/issues/3623

In order to step around the issue please follow the instructions listed here: https://www.techrepublic.com/blog/windows-and-office/get-a-better-view-in-windows-7-by-adjusting-dpi-scaling/


By Clicking the windows key and typing Display

Select the Smaller option 100% (default) and click apply.

You will be prompted to restart your computer which can be put off until a more convenient time 

After restart using chrome should allow you to resize columns 

Error when double-clicking on a request file in the DataMart ClientWhen a DataMart Administrator opens a new file distribution or modular program request, they must click on that file in order to download it.  In many instances, if the user double-clicks on that file, an error appears and the DataMart Client closes.  to avoid this, all users should single-click on any files for download in the DataMart Client. 
Recent changes to the FireFox web browser are not compatible with secure PopMedNet sites

Users will need to use another web browser, such as Chrome or Internet Explorer to access the Query Tool.  This affects the following sites:

Response Detail Web Portal tab resizing

In Internet Explorer and Edge, the Response Detail tab for Question Engine-based requests may occasionally not resize properly to accommodate viewing a large number of DataMart responses at once. This will prevent the user from being able to view results directly on the PMN Web Portal, but it does not prevent the user from downloading results. Two workarounds have been identified:

  • Use Chrome or Safari web browsers when viewing results on the PMN Web Portal. These browsers are not affected by this issue.
  • If the user does happen to encounter this issue in Firefox, right-click the contents of the Response Detail tab and click This Frame>Reload Frame.
Intermittent Script Error in DataMart Client

When opening a request in the DataMart Client, there is occasionally a script error when loading the request.  This message appears immediately upon opening the request and will prevent the request details from properly loading.  If the user closes the request and attempts to open it several minutes later, the error will likely have resolved itself.

Approving "Completed" routings will change status to "Results Modified"Response Reviewers select DataMart routings with the status "Awaiting Response Approval" and view the results in order to approve or reject them.  In the case that a Response Reviewer accidentally selects an  "Awaiting Response Approval" routing AND a "Completed" routing, then views the results and approves them, the status of the "Completed" routing will change to "Results Modified".  The results of this routing are not changed in any way; only the status has changed.
Error when exporting 'Metadata Search' results to excel formatFor 'Metadata Search' requests that produce a large amount of results, exporting to either "Excel - Summary" or "Excel - Detail" produces an excel file that is corrupted and needs to be repaired. As a workaround, users should export to "CSV - Summary" or "CSV - Detail" instead.



Contact Us

PopMedNet Service Desk