PopMedNet Distributed Query Tool

Release Notes

Based on Release 5.2

January 11, 2016

Releases

Introduction

These release notes cover PopMedNet version 5.2. Enhancements, bug fixes, and other changes are listed below.

A new desktop DataMart Client is only required if using Question Engine requests. All legacy requests do not need a DataMart Client update.

• Question Engine Requests: Requests can now be "question engine" based or "legacy" based. "Question Engine" is a generic term for the new back-end request infrastructure. The infrastructure allows for a flexible, menu driven interface for constructing queries. "Legacy" requests are those request types that existed prior to the Question Engine. Every request submitted prior to version 5.2 was considered a legacy request. Not all networks will utilize question engine requests. If you submitted or received legacy requests in the past, you will continue to be able to do so, and will be unaffected by the question engine infrastructure. This functionality is data model dependent and therefore not possible on all networks.  As of release 5.2, only the PCORnet network is able to utilize the question engine.
  
  Second, this infrastructure transfers much of the functionality in the DataMart Client from the desktop application to the model adapters. Adapters are downloaded to the DataMart Client when a request is opened, and  inform the DataMart client how to respond to the request. Adapters can now be updated without installing a new DataMart Client, minimizing the need for frequent DataMart client updates.
  
  Utilizing question engine requests requires the configuration of an additional DataMart within the DataMart Client desktop application. 
  
  
  
• Role Based Workflow Engine: Requests can now be created and submitted via a workflow engine. This allows for the following capabilities. (1) Assignment of roles to users on individual requests that inform tasks users are responsible for on each request. (2) Storage, iteration, and review of request related documents. (3) More granular workflow-related notifications, including the ability to send notifications to non-users. Requests utilizing a request workflow use the question engine infrastructure on the back end; a workflow cannot be applied to a "legacy" request.