Based on Release 3.2.12 - August 26, 2013
This update applies to all networks powered by the PopMedNetTM Release 3.x Software and includes enhancements and bug fixes to the PopMedNetTM software. This release includes updates to both the PopMedNetTM Portal and the DataMart Client. A new DataMart Client is available to download. It is recommended that you download the new client, but that is not required to execute queries.
These release notes cover software versions 3.2.0 through 3.2.12. The enhancements and bug fixes are listed below.
Update | Type | Description |
Projects | Portal - Feature | Project based request processing and administration. Groups, organizations, DataMarts, request types, and users can be organized into a project and access controls enforced on the entities specific to the project. |
SQL Distribution | Portal - Feature | Allows users to submit raw SQL code to data partners. Agnostic to data model. |
Results output export file name | Portal - Enhancement | File names of result outputs exported from the portal are now identified by the query type and unique query ID. |
Resources page | Portal – Enhancement | Documentation is updated on the resources page. |
Contact Us link on login page | Portal – Enhancement | A Contact Us link is displayed on the login page. |
Horizontal scrolling in the DataMart Client | DataMart Client – Enhancement | Horizontal scrolling is enabled for results displayed in the DataMart Client. |
Email notifications | Portal – Bug | Users will now receive email notifications after enabling them on their profile. |
Lock out warning and error message | Portal – Bug | Fixes a bug where users were not notified before being locked out of their accounts. Now users see a warning when the password is entered incorrectly four times and an error message when they are locked out after five tries. |
Results output column order | Portal – Bug | Columns for summary table results are now in the same order as they were in the results output in version 2 of the software. |
Column header repeat in CSV exported results files | Portal – Bug | Column headers no longer repeat in results files exported in the CSV format. |
Strong password enforcement at registration | Portal – Bug | Strong passwords are now required during registration. Strong passwords require a combination of upper case and lower case letters, numbers, and symbols, and a minimum length of 8 characters. |
Messages remain after approval | Portal - Bug | Fixes an error that caused messages uploaded with results from the DataMart Client to disappear after the results have been approved. |
DataMart Client proxy server compatibility | DataMart Client - Bug | DataMart Client can now connect to the portal through a site’s proxy server. |
“Invalid Data Set: Value was either too large or too small for an Int32” error | DataMart Client – Bug | Fixes an error that caused queries to return results with “Invalid Data Set: Value was either too large or too small for an Int32” error messages. |
Notification options allow the user to manage events that are triggered due to actions performed by the user or related to the user’s role. Notifications are sent to the email address associated with the user’s account and are displayed in the Notifications panel on the Portal home page.
All users must reset their notification settings via the Notification panel on their Profile page. Navigate to this page by clicking the Profile tab on the Portal.
Below are the recommended notifications to subscribe to, based on user roles. Please note the frequency of the notifications.
Notification | Description | Frequency |
Password Expiration Reminder | Notifies the user that his or her password is about to expire. | One notification per day for 7 days prior to the password expiring. NB: Passwords expire every 6 months. |
My Profile Updated | Notifies the user that his or her profile has been updated. | One notification per change. |
Notification | Description | Frequency |
Request Status Changed | Notifies an investigator that the status of his or her request has changed to completed, awaiting approval, or rejected. | One notification per DataMart per change per request. |
Results Reminder | Notifies an investigator that there are results waiting to be viewed on the portal for his or her request. | One notification every 24 hours per results awaiting viewing. |
Notification | Description | Frequency |
New Request Submitted | Notifies a DataMart Administrator that a new request has been sent to his or her DataMart. | One notification per request. |
Routing Status Changed | Notifies a DataMart Administrator that the status of a request in his or her DataMart has changed to completed, awaiting approval, or rejected. | One notification per DataMart per change per request. |
Submitted Request Awaits a Response | Notifies a DataMart Administrator that a request is waiting for a response in his or her DataMart. | One notification every 24 hours per DataMart per request awaiting response. |
Request Status Changed (for DataMart Administrators submitting requests) | Notifies a DataMart Administrator that the status of his or her request has changed to completed, awaiting approval, or rejected. | One notification per change per request. |
Results Reminder (for DataMart Administrators submitting requests) | Notifies a DataMart Administrator that there are results waiting to be viewed on the portal for his or her request. | One notification every 24 hours per results awaiting viewing. |
New DataMart Client Version is Available | Notifies a DataMart Administrator that a new DataMart Client version is available on the portal for download and installation. | One notification per DataMart Client update. |
DataMart Change | Notifies a DataMart Administrator that a change has been made to his or her DataMart. | One notification per change. |
Notification | Description | Frequency |
New Request Submitted | Notifies a Group DataMart Administrator that a new request has been sent to his or her group’s DataMarts. | One notification per request. |
Routing Status Changed | Notifies a Group DataMart Administrator that the status of a request in his or her group’s DataMart has changed to completed, awaiting approval, or rejected. | One notification per DataMart per change per request. |
Submitted Request Awaits a Response | Notifies a Group DataMart Administrator that a request is waiting for a response in his or her group’s DataMart. | One notification every 24 hours per DataMart per request awaiting response. |
Uploaded Result Needs Approval | Notifies a Group DataMart Administrator that a response from his or her group’s DataMart awaits approval on the portal. | One notification per DataMart per request. |
Issue | Workaround |
View responses one DataMart at a time. | |
Contact the requestor via email. | |
If a response is required, resend the request to the DataMart. | |
View the login page using Internet Explorer or Google Chrome. | |
Ignore the first “Results reminder” email. Subsequent reminder emails are sent every 24 hours. | |
None. | |
None. | |
Select any other organization during registration and Network Administrators will correct it when approving the registration. | |
Export as Excel or change values in the exported CSV file. | |
None. | |
Export results as an Excel file. | |
None. |
The Portal is designed to work with Internet Explorer (IE) 8 or later. Earlier versions of IE may not display the user interface properly. Although IE8 is the only officially supported browser, other browsers such as Firefox and Chrome will also work. Firefox and Chrome have been used extensively during testing.
The DataMart Client application allows the DataMart Administrator to view queries distributed to the DataMart, execute queries locally, review the results, and upload the results to the Portal. The DataMart Client is a .NET/C# Windows desktop application developed by LPP that is installed locally on an Administrator’s desktop. Note the DataMart Client requires Microsoft .NET 4 to be installed on the user’s desktop – see the next section for install information. All communications between the DataMart Client application and the Portal use HTTP/SSL/TLS connections to securely transfer queries and results between the application and the Portal. The application uses ODBC connections to the local DataMart databases used to process queries and generate results.
Microsoft .Net 4 is required to run the DataMart Client. The free download for Microsoft .NET4 is available at the following link: http://www.microsoft.com/en-us/download/details.aspx?id=17851
Not sure if you have Microsoft .NET 4? If you do not, you will receive an error message when you try to open the DataMart Client.
Register for an account in order to receive login credentials to the query tool portal.
Download the DataMart Client from the Network Portal.
For more information on configuring your DataMart Client see the /wiki/spaces/DPM/pages/491582.
To see a summary of the data available about the network, go to the Resources tab and click on “Query Types by DataMart”.
Once logged in to your Network Portal, the Resource Tab offers helpful contact information, documentation, and related links, as shown below. If you have trouble accessing the Web Portal or your user account, click on the Contact Us link in the right-hand corner of the screen and describe your issue to request help from the PopMedNet support staff.
Microsoft Silverlight is required to upload files for file transfers. If you do not have Silverlight installed, you will see a message to download and install it under “Upload Files” in the Request window.
If your site created a new database, use these steps to update your ODBC connection. Note: if the new file has the same name and is in the same location, skip to step 8.
For information on uninstalling the DataMart Client see the /wiki/spaces/DPM/pages/491677.