New Features in 5.6

Improvements to column filtering functionality in the query tool

All panels in the query tool now have the same filtering capabilities. Users can filter any column in any grid by an exact or boolean match. Columns can also be hidden and will remain hidden until manually made visible again by the user. All filtering or hiding of columns is specific to a user and will remain in effect even after logging out.

Ability to view all requests for a given data partner

There is now a new grid on the home page that displays all requests by data partner. The grid is located directly below the existing request grid. Click the arrow to the left of each DataMart name to display a table of all requests sent to that data partner along with their associated information. The same permissions apply to the Request grid and the DataMart grid, so users will see the same requests in both grids. Users that have permission to view all DataMarts may see DataMarts in the DataMart grid that are not relevant to them, but they will not be able to see requests sent to those DataMarts.

Improvements to password logic and reset functionality

A variety of password problems were causing frequent system lockouts for many users. Password logic reset functionality has been improved in the following ways:

New tools available via Single Sign On

Users can now access more tools, (shown in the screenshot below), from the PopMedNet Sentinel Single Sign On page. Clicking on one of the links on the Single Sign On page will bring you to that tool without the need to sign in again. You must have an active username on the tool to which you are navigating to access it.

The Single Sign On page URL is: https://sso.mini-sentinel.org/.

The existing URL: https://querytool.mini-sentinel.org/ will redirect users to the Single Sign On page. An update is planned for after the release of 5.6 that will allow users to access the main URL directly.

Ability to subscribe to notifications for only the requests to which you are assigned (Question Engine Only)

Users can now subscribe to notifications on a request level. If you wish to subscribe to notifications on a single request, navigate to that request and add yourself as an observer via the notification tab. When you click add, you will be able to choose the specific notifications you want to receive. Users with the appropriate permission will also be able to assign request-level notifications to other users.

Additions and Improvements to workflow roles (Question Engine Only)

A new role, "Requestor," has been added for use in requests that use a workflow. The requestor role can now be assigned to a user to designate them as the originator of the request, even if that person did not physically create the request in the PopMedNet system.

Ability to edit request metadata after a request is submitted

Users with the appropriate permission can now edit request metadata for requests at any point in the request cycle, even after the request has been completed. Click the "Edit Metadata" button below the request metadata to bring up a screen in which the request can be edited. Saving changes will trigger a notification detailing the edits to users who are eligible and subscribed.

Integration between the PopMedNet Query Tool and the Medical Code Management Tool (MCM) (Sentinel - June 2016; HDC - December 2016)

The Medical Code Management (MCM) tool, developed by Commonwealth Informatics, is now integrated with the PopMedNet Query Tool. The MCM is always updated with the most recent sets of diagnosis, procedure, and NDC codes available to various PopMedNet networks. The MCM will now automatically sync with the Sentinel PopMedNet network every Sunday at 7:00 AM so the Sentinel network will always have the most up to date codes available in the MCM. In addition, a new column for the code expiration date will be visible in the code selector windows within PopMedNet.

Manual synch URL: https://[NetworkAPIURL]/users/updatelookuplists?username=[username]&password=[Password

Addition of Source Task Order fields

There are now 6 total fields available in PopMedNet for entering Task Order information. The fields with the "Budget" prefix previously existed; they are the fields previously used to enter all Task Order information. The fields with the "Source" prefix are new. Users can now enter budget and source task order information separately. On the initial release, requests will not have any information in the source fields, as they are new. All 6 fields are synced with the Task Order Matrix (TOM). The list of values in the drop-downs in PopMedNet will be the same for each pair of fields. For example, the list of values in the source task order field is the same as the list of values in the budget task order field.

Networks can choose to hide the Task Order fields if desired. If you wish to have any of the Task Order fields hidden from users on your network, please email support@popmednet.org.

Modifications to the purpose of use request metadata field

Two changes have been made to the "Purpose of Use" field:

1. There are now 3 additional options to choose from: Clinical Trial Research, Prep-to-Research, and Observational Research.
2. The field now displays the full text of the purpose of use value, rather than the code. For example, Clinical Trial Research will show up as "Clinical Trial Research" instead of "CLINTRCH."
   
   

Ability to manually change the DataMart routing status of a request

Users with the appropriate permissions will now be able to change the routing status of a request for one or more DataMarts before the routing has been completed. Click "Edit Routing Status" below the Incomplete Routings panel in any request to bring up a window in which the routing status can be modified. A change will trigger a "Request DataMart Routing Status Changed" notification to users who are eligible and subscribed.

Streamlined request creation process

Users now have the ability to select the project in which to create a request immediately after clicking the "New Request" button. Once "New Request" is clicked and project is selected, a window displaying all request types available to that user, in that project, will appear.

Ability for Data Partners to re-upload responses to file distribution and modular program requests

Users now have the ability to re-upload responses to modular program and file distribution requests, eliminating the need for the request to be re-submitted. Once a modular program or file distribution request has been responded to, the upload button is re-labeled "re-upload." If a modified response file is added to the request, it can be uploaded to the PopMedNet query tool by clicking re-upload. Re-uploading a response will change the routing status of the request in the DataMart and the query tool to "results modified."

A new request ID field, separate from request name, to provide more clarity to requests

There are now a request name field and a request ID field, rather than just a single request name field."Request ID" is a new field.

• On initial release, all data that exists in the "Request Name" field will be duplicated into the "Request ID" field.
• The field previously labeled “Request ID” in PopMedNet is now labeled “System Number.” 
• Request Name no longer enforces uniqueness, Request ID does.
• Request ID will be blank on request creation. If the field remains blank after the initial save of the request, the system will populate request ID with this value: "Request [System Number]"
• If request ID is hidden from a user, that user won't see request ID in the edit metadata dialogue, but it will still be populated with "Request [System Number]"
  

Networks can chose to use one, both, or neither field for their requests. If you wish to have either of the fields hidden from users on your network, please email support@popmednet.org.

Ability to see notifications to which users are assigned on their profile page

Users now have the ability to see the areas in which they are eligible for notifications. For example, when subscribing to the "New Request Submitted" notification, users could view the notifications for which they are eligible at the Project, Organization, and DataMart w/in Project level. On the notification tab of your profile page, click the + next to a notification to view the areas in which you are eligible for that notification.

System administrator users can view the areas in which others users are eligible to receive notifications. This will make troubleshooting notification issues much simpler.

Ability to customize the request metadata fields that are shown to certain groups of users

Request metadata fields can now be made required, optional, or completely hidden from certain groups of users when composing a request. For example, investigators on a network could see all request metadata fields, but observers could only see a subset, such as Request Name, Request ID, and Description. All fields still appear in notifications, regardless of the fields the user receiving the notification can see on the portal.

If you wish to make certain request metadata fields required, optional or hidden for certain groups of users on your network, please email support@popmednet.org and we will evaluate your request.