5.6.1 Release Notes

PopMedNetTM Distributed Query Tool

Release Notes

Based on Release 5.6.1



Releases

Date of Release8/14/16Not Released12/18/168/28/16Not Released
Networks UpdatedSentinelNIH DRNHDCMDPHnetPCORnet
DataMart Client Update

Not Required


*Not Required

*Not Required

*Not Required

Not Required


*DataMart client versions 5.0.5 and above will still function after the upgrade, but users are strongly encouraged to update to version 5.6+. Many new features are not compatible with older versions, and certain known issues (listed below) may cause an error when attempting to run a request in the 5.0.5 DataMart client.


Introduction

This is a minor patch being released to address some recently discovered bugs with summary table queries. No new features or enhancements, outside of the bug fixes, are included.

A new desktop DataMart Client is NOT required. 

Enhancements

None

Bug Fixes

Bug

Description

Codes Selected for Summary Table Queries Do Not Save When the Request is Saved as Draft

Previously, when saving a Summary Table request that uses Drug Codes or Drug Names, then re-opening the request, the list of codes that were previously added to the request would disappear.

Clicking the "Select" button to edit the code selection will always bring up a blank selection, even if a user had previously added codes and saved the request as a draft.

This has been addressed, once a summary table query is saved as a draft, it can be re-opened and the selected codes will still appear as selected.

Commas in Code Names Cause Summary Table Pharmacy Dispensing Queries to Run Incorrectly 

Previously, the presence of a comma in a summary table drug class query would break the query into two distinct drug classes. For example, if a query contained the drug class, "Beta Blockers Cardiac Selective, All" the summary table query will split that drug class into 2 separate drug classes, "Beta Blockers Cardiac Selective," and "All," when running the query. 

This has been addressed; commas in drug class names will no longer cause the drug class to be split.


Known Issues

NOTE: These known issues are not related to the bugs being fixed in this patch release, however, they still exist for versions 5.6 and above.

IssueWorkaround
Versions 5.6 DataMart Client and above are designed to work with Microsoft .NET version 4.6.1 and above. Previous versions of the DataMart client were designed to work with .NET 4.5.2 and below. In rare instances, users who have .NET 4.5.2 and below may experience an error when attempting to run a Summary Table request sent to the 5.0.5 DataMart client after the Sentinel Query Tool is updated to version 5.6+.
  • If you do experience an error when running a request, it is strongly recommended that you download the 5.6 version of the DataMart client. Microsoft .NET 4.6.1 is included with the DataMart client download.
  • If you are not yet able to download the 5.6 version of the DataMart client, contact your PopMedNet administrator for assistance in running requests.
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 must set up an additional DataMart that is configured 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 the question engine request types.

If users wish to make use of the flexible, menu driven interface (first introduced in 5.2), 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.

Summary table queries can continue to be run via the legacy interface against an Access database.
The "configuration settings" screen in the DataMart client shows selectable settings for modular program request types, even though no settings need to be configured. This is due to the nature of the question engine infrastructure and will be addressed in a future release.No settings need to be configured for modular program requests. The process to configure a DataMart client to accept modular program requests is unchanged. Click "ok" to exit the configuration settings window, do not apply any settings.






Contact Us

PopMedNet Service Desk