6.5 Release Notes
PopMedNetTM Distributed Query Tool
Release Notes
Based on Release 6.5
Releases
| Networks Updated | Sentinel | HDC | PCORnet | |
|---|---|---|---|---|
| Date of Release | 6/28/17 | 9/27/17 | Not Released | |
| DataMart Client Update | *Not Required | *Not Required | NA |
Introduction
PopMedNet version 6.5 is a significant update to the PopMedNet distributed query tool. It contains several bug fixes and includes new distributed regression functionality. It is also the first release in which the question engine infrastructure and menu driven interface and is fully production ready for Sentinel.**
*DataMart Client (DMC) 6.0+ is required to receive and respond to requests sent from the version 6.5 of the distributed query tool.
**This infrastructure will allow Sentinel partners to take advantage of an menu driven, workflow-capable interface for modular program and summary table queries. Enabling this infrastructure is dependent on further discussion with SOC and partners. No changes to the query process are being made at this time.
The Sentinel Query Tool mailing address has changed – mail from the Query Tool will now be sent from noreply@sentinelsystem.org rather than admin@mini-sentinel.org. All applicable mail whitelists should be updated to reflect the change in address in order to ensure mail delivery. Bug Requests with a status of Re-submitted do not appear in the DMC 6.5 DMC only DataMart client connection settings would not save when connecting only 1 adapter from a DataMart that supports multiple adapters 6.5 DMC only Previously, when configuring a DataMart client connection to a Database for an MDQ or Summary table query, the configurations would not save if previous configuration setting existed. For example, if a user had configured the summary table prevalence, summary table incidence, and summary table MFU adapters to a new database, and later connected just one of those adapters to a new database, the new connection would not save as the DataMart would not know which connection to use. This has been fixed so each adapter in a DataMart that supports multiple adapters can be configured and saved without needed to configure and save all adapters. If users wish to make use of the flexible, menu driven interface (first introduced in 5.2 for PCORnet), for constructing queries, summary tables databases that are currently stored in Microsoft Access will need to be converted to Microsoft SQL server. The question engine infrastructure that supports the menu driven interface is not compatible with Access.Enhancements
Update Description Updated Terms and Conditions Per FISMA requirements, the terms and conditions for using the query tool are now displayed directly on the sign on page and are not hidden behind a terms and conditions link. This applies to the Sentinel query tool only Updated query tool email address Bug Fixes
The re-submitted request status was missing from the status filter in the DMC. This has been addressed; all statuses are now available in the filter dropdown. Filter sub menus in the query tool disappear unexpectedly In the query tool grids, the filter sub-menu in which users enter their filter criteria often closes/disappears unless the user keeps the mouse directly on the sub-menu. This has been corrected via an update to the filter widget used across all PopMedNet query tool grids. Viewing results from the history window in a legacy file distribution request causes an error When users view the history of a request, users with the correct permission can click "view responses" right from the pop-up window displaying the request history. The view responses button was producing an error, this has been corrected so responses are now accessible via that link. Contact us email address is incorrect The contact us email on the SSO page for the Sentinel query tool was incorrect. It has been updated to support@popmednet.org Applying a filter to a grid in the query tool causes all rows to disappear. If a user navigated away from a page in the query tool after applying a filter to a grid and subsequently navigate back to that page, the grid in which the filter was applied would be blank. For example, if a user filter toe request grid to show all requests submitted between 1/1/17 and 3/1/17, navigated to another page in the query tool and back to the home page, the request grid would be completely blank, even if requests matched the filter criteria. This has been corrected, filters work properly and will remain applied until removed by a user. Sub-terms in the menu driven interface are not highlighted when hovered over them with the mouse The menu driven interface select a set of terms and stratification as parameters in a query. Certain terms represent groups of terms and have sub-menus with additional terms. (For example, sub terms of the demographics term include age, sex, etc). The sub-terms did not appear highlighted when moused over, thus it was unclear to a user if they were actually going to select the term. This has been corrected to terms at all levels are highlighted when moused-over Forgot password functionality Previously, passwords would not save when created using the forgot password functionality. This has been corrected so the forgot password functionality can be used to log in when a user forgets their password. Auto-filing fields when registering as a new user causes an error during registration New registrants that used auto-fill to populate some user user registration fields received an error when trying to submit their registration. This has been fixed so auto-filling fields will not cause an error Known Issues
Issue Workaround Question engine requests, and therefore the new menu driven interface first introduced in 5.2, require the configuration of an additional DataMart. If a user wants to run a request using the menu driven interface, the Data partner receiving the request configure an additional DataMart to receive question engine requests. A network administrator must also configure the portal so that users are able to distribute question engine requests. Legacy requests can still be sent to Data Partners' existing DataMarts. This only impacts the PCORnet network as they are the only network utilizing question engine request types. Summary table queries will continue to be run via the legacy interface against an Access database. The size limitations of Access are unrelated to the requirement to use SQL server for menu driven querying.