6.6.1 Release Notes
PopMedNetTM Distributed Query Tool
Release Notes
Based on Release 6.6.1
Releases
| Networks Updated | Sentinel | HDC | PCORnet |
|---|---|---|---|
| Date of Release | 3/1/18 | 3/1/18 | 2/24/2018 - Web Portal |
| DataMart Client Update | Not Required | Not Required | Not Required |
Introduction
PopMedNet version 6.6 .1 is a minor update to the PopMedNet distributed query tool. A full list of new features and bug fixes can be found here.
Enhancements
| Update | Description |
|---|---|
| NA | NA |
Bug Fixes
| Update | Description |
|---|---|
| Correction to prevent users from downloading responses which are labeled "Awaiting Response Approval" | When clicking download all after selecting a datamart that has Awaiting response approval we expect that the data will not be eligible to be downloaded |
| Address issue when users receive 401 error in web portal | Authentication error when trying to download Results from a Question Engine based Query |
| Metadata request search: fix to address data in Request Status and Routing Status columns | The Metadata Request Search will continue to search based on Request Status. However, in the results, there is both a "Request Status" column and a "Routing Status" column. The "Routing Status" column displays each DataMart's individual Routing Status for that request. |
Known Issues
| Issue | Workaround |
|---|---|
| Multiple DataMart Clients set to auto-upload | If a single DataMart has multiple DataMart Clients set to auto-upload, it may cause two result sets to be uploaded. It is advised to only use a single primary DataMart Administrator at a time for each DataMart to avoid this issue until it is fixed. |
| Response Detail Web Portal tab resizing | In Firefox, 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:
|
| Checking for NULL ADMIT_DATEs in PCORnet Menu-Driven Queries | The 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. |
| Modifying DataMart Client refresh rate | The foundation and user interface for user-changeable DataMart Client refresh rates was implemented in the PopMedNet 6.6, but a new refresh rate value will not save successfully if a user tries to modify it. This feature will be full implemented in PopMedNet 6.7. |