Update | Description |
---|
The column order of summary table results do not match between the Query Tool and DMC | In diagnosis and procedure code queries , the "event" and "members" columns were not displayed in the same order in the query tool and DataMart client. For pharmacy dispensing generic name and drug class queries, the "days supply" and "members" columns were not displayed in the same order. These errors have been corrected and all result columns appear in the same order across the query tool and DMC.
|
The behavior of the breadcrumb trail on the requests page of the query tool is not consistent with the other pages | The Home link on the breadcrumb trail on the Requests page was not clickable. This has been corrected, users can now click on the home link on the breadcrumb trail on the requests page. |
Certain request statuses were mislabeled in request metadata search results | Some requests with a status of "awaiting request approval" would appear to have a status of submitted when exported as part of the results of a metadata search request. This has been corrected, all request statuses are accurate when metadata search results are exported. |
Column sorting remained even after it was cleared and the user logged out and logged back in | This has been corrected. Once a user clears any sorting they applied to any column in the query tool, the sorting will not be re a |
Summary Table Observation Period selection boxes provided a dropdown of available date years | A dropdown of available years appeared as the observation period selection boxes were populated via a back end database table in PopMedNet that contained the available date ranges for each data partner. That table is no longer needed or updated. Therefore, the lookup that presented a range of available years has been removed. Observation period selection boxes will now accept any 4 digit numeric string and will not suggest a range of years. |
Unable to filter the user list by the "active/inactive column | This has been fixed, users with appropriate permission can now filter the user list by active or inactive. |
Request results were downloaded in xls format when excel was selected as the export format. This produced an error for users who have excel 2007 or later installed, but did not prevent the file from opening. | Results now export in xlsx format when excel is selected as the export format, so no error should appear for users with excel 2007 or later. |
Cancel button removed from the upload results dialogue in the DataMart client. | After clicking upload results in the DataMart client, a loading bar is presented. This loading bar previously had a cancel button next to it. Occasionally, data partners would click this cancel button, but results had already been uploaded. They would later upload results again, as the DataMart did not record that the request was complete even though results were uploaded to the query tool. This caused results to be uploaded twice and added together in a single result file for that request for that data partner. The cancel button has been removed to prevent this scenario. Data partners still have the ability to review and reject a request before uploading results, the cancel button was duplicative of these functions. *Cancel button removed in DataMart client 6.7 +* |
Unable to delete draft requests in the query tool. | Observation period is a required field in any summary table request. Previously, when a draft request was created and saved without an observation period, it could not be deleted. The system expected all required fields even when attempting a deletion. This validation has been corrected so a draft request can be deleted without an observation period. |
PCORnet MDQ Fixes | - The 'Age as of the request submission date' calculation has been corrected
- Investigators can no longer submit a MDQ that has a blank observation term. Previously, a query with a blank observation period could be submitted, and if a DataMart tried to run the query, an error would occur. The fix now alerts the Investigator to the blank term and will not allow the query to be submitted until at least one date (start date and/or end date) is entered in the term
|
Question Engine File Distribution only has the ability to view results on an individual basis | When viewing results for a query, the Investigator has the option to view results in aggregate (across all DataMart responses in the request) or in individual view (each DataMart's results on its own). For MDQs it makes sense to have both options, but in the case of File Distribution requests, viewing the results in aggregate is not possible. We have removed the option to view File Distribution results in aggregate to avoid confusion |