6.9 Release Notes

Owned by Zac Wyner (Unlicensed)
Last updated: Jan 10, 2019 by Kimberly Barrett
5 min read


PopMedNetTM Distributed Query Tool

Release Notes

Based on Release 6.9


Releases

Networks UpdatedSentinelHDCPCORnet
Date of ReleaseN/A12/27/201811/30/2018
DataMart Client Update*Not Required

*Not Required

*Not Required

Introduction

This is a planned release with bug fixes and new functionality.  This is not a required DataMart Client update and users may continue to use their current DataMart Client.  However if you are interested in using some of the new DataMart Client functionality in this release, you will need to download the 6.9 DataMart Client.

Enhancements



Capability to save results locally i.e. response caching

A new feature for the 6.9 DataMart Client that will save results in the Client. A user can now enable the ability to retain results locally for individual requests. In the DataMart Settings, a user can select "Enable Response Caching". When this is enabled, a user can run a query or attach a file to a request, and the DataMart Client will retain those results after the Request Details Window has been closed. Those results will be stored locally and will not be visible or uploaded to the Query Tool until the user selects "Upload Results". The user can also remove the files or re-run the query prior to upload. 

Additional options in the DataMart Settings, allow the user to:

  • Set the duration for which the DataMart Client will retain those results
  • Manually clear stored results for all requests submitted to that DataMart or select "Enable explicit cache removal" which will allow the user to open a request and clear the results for that individual request without affecting any other requests for that DataMart.

For more information on this feature: PMN User's Guide: Configuring Unattended Operations and Cache Settings

Capability to set DataMart Client to auto-run queries, but not upload the results

A new unattended operation has been added to the 6.9 DataMart Client for Menu-Driven Queries (MDQs). DataMart Administrators can now set their DataMarts to: "Process new queries automatically, but do not upload results". By selecting this option in the DataMart Settings, the DataMart Client will begin to execute any "Submitted" MDQ requests for that DataMart once the Client has opened. After the request is executed, the DataMart Client will store the results locally according to the Cache Settings. These results will not be uploaded automatically, and require that the DataMart Administrator select the "Upload Results" button.

Note: If a user wishes to use this functionality, they will also need to enable response caching described above.  

For more information on this feature: PMN User's Guide: Configuring Unattended Operations and Cache Settings

Capability to upload code lists when creating Menu-Driven Queries (MDQs) When composing a Menu-Driven Query, users can now import a comma-separated values (csv) or Excel file of procedure and diagnosis codes. For each code, users can specify the criteria group and procedure/diagnosis code type, along with whether to search for an exact match or any code that begins with the code specified. This file can either append existing codes already in the query, or clear out all existing codes and replace them with those specified in the file.
Saving Project Details PageThe project page has been redesigned so that network administrators can more quickly update project configurations and permissions.
Clear FiltersUsers can now clear all filters from any grid in the query tool (web portal).
Update file type for downloads to XLSXAll excel files downloaded from the query tool now download in XLSX format, rather than XLS. This eliminates an error users of excel 2007+ were seeing when downloading XLS format files from the query tool.
Improved auto processing so that requests can be processed concurrently then sequentiallyChanges have been implemented to introduce concurrency into the execution of requests for faster processing. Here's a quick summary of the overall changes: 
  • PMN can now support independent auto-processing queues per network. This change supports each network having it's own refresh rate as described below. 
  • RefreshRate configuration has been added to the DataMart Client (DMC) Network Configuration screen to allow the rate to be defined per PMN instance (i.g. network). This ensures that each network's requests are refreshed at the defined interval. 
  • The DMC Network List is refreshed as per the configured Refresh Rate per Network. The default is set to 300 seconds, i.e. 5 minutes. 
  • The automatic processing fires up at the minimal interval defined per network i.e. if two networks are configured in the DMC with the Refresh Rate of one set to 10 seconds and the second set to 300 seconds, the Auto-Processor will check for and execute requests across the networks every 10 seconds (with the requests list being updated with new requests from PMN as per configured Network Refresh Rate). 
  • The Auto-Processor keeps track of requests being executed and processes multiple requests concurrently rather than sequentially. 

Bug Fixes

UpdateDescription
"Total Enrollment In Strata" column calculation is inconsistent across Summary Table Request Types

Previously, the "total enrollment in strata" column was calculated differently for drug queries and procedure/diagnosis queries. For drug queries, all members with drug coverage were included. For diagnosis and procedure queries, all members with medical coverage were included. Now, the "total enrollment In strata column" will include all members with medical AND drug coverage for all summary table queries.

This update only affects Sentinel and HDC as only those networks utilize the summary table query types.

Note, this was originally fixed in 6.7.1.1

The Contact Us link on the Home page of the Query Tool now directs to the service deskClicking Contact us in the Query Tool used to open an email to our now deprecated email account. Now it will open a new tab directed towards the service desk. 
Can no longer submit MDQs with empty criteria groupsPreviously it was possible to submit MDQ's with empty criteria groups.  Empty criteria groups serve no function to the query and prevent the DataMart Administrators from running the query. The querytool has been updated to check that there are values present in all the criteria groups before a query is submitted and will notify the Investigator of the issue. 
Change to Network Settings config file

The PopMedNet team no longer works with Lincoln Peak Partners, so references to Lincoln Peak have been removed from the Datamart client program files.

If you upgrade to DataMart 6.8 (or later) from DataMart 6.7 (or earlier), you must follow the steps below in order to save their network and DataMart Client settings. The steps below are only for users who choose to update their DataMart Client - all other users do not need to do these steps.

  1. Find your current Network Settings file in the following location: C:\Users\USERNAME\AppData\Roaming\LincolnPeak\PMN
  2. Copy the NetworkSetting.xml file
  3. Navigate to the new DataMart Client folder at the following location: C:\Users\USERNAME\AppData\Roaming\PopMedNet\PMN
  4. Paste the NetworkSetting.xml file into this new location


In MDQs the age calculated as of observation period end date despite set to calculate as of start datePreviously, when the 'age as of start date' calculation is in the second criteria group of a MDQ, the age of patients was actually calculated off of the end date of the observation period in that criteria group. This has been fixed to calculate off of the start date.
Can submit a QE File Distribution request type with no file attachedInvestigators now are able to submit QE File Distribution requests even when no file is attached.

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