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 Page | The project page has been redesigned so that network administrators can more quickly update project configurations and permissions. | | Clear Filters | Users can now clear all filters from any grid in the query tool (web portal). | | Update file type for downloads to XLSX | All 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 sequentially | Changes 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| Update | Description |
|---|
| "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 desk | Clicking 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 groups | Previously 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. - Find your current Network Settings file in the following location: C:\Users\USERNAME\AppData\Roaming\LincolnPeak\PMN
- Copy the NetworkSetting.xml file
- Navigate to the new DataMart Client folder at the following location: C:\Users\USERNAME\AppData\Roaming\PopMedNet\PMN
- 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 date | Previously, 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 attached | Investigators now are able to submit QE File Distribution requests even when no file is attached. |
Known Issues| Insert excerpt |
|---|
| Known Issues |
|---|
| Known Issues |
|---|
| nopanel | true |
|---|
|
|