not required

not required

Release Notes

Users can now run Menu-Driven Queries against Oracle 18 databases. Going forward PopMedNet will support Oracle 18 for MDQs in addition to Oracle 12, while dropping official support for Oracle 11. In order to run MDQs against Oracle 18, users must uninstall and reinstall the DataMart Client once the network has been updated to PMN 2020.4.

Whitespace is now trimmed at the beginning and end of request metadata text strings.

A new "Lab: LOINC" term has been added to the Menu-Driven Query (MDQ) request type, allowing investigators to query the "LAB_LOINC", "SPECIMEN_DATE", "RESULT_DATE", “ LAB_ORDER_DATE” , “RESULT_NUM”, “RESULT_QUAL”, and “RESULT_MODIFIER” fields of the LAB_RESULT_CM table within the PCORnet CDM v5.1.

· Lab: LOINC term behavior:
     - Once the Lab: LOINC term is added to the MDQ, Investigators can type in LOINC codes.  LOINC codes within the same MDQ criteria group are ORed together.  In order to have the AND operation between codes, they will need to be in different criteria croups.
     - LOINC codes will also be ORed with any Diagnosis, Procedure, or Prescribing codes within the same criteria group.  In order to have the AND operation between LOINC AND diagnosis/procedure/prescribing codes, the terms will need to be in different criteria groups
     - The MDQ will search for patients with at least one record of the specified codes.  If the LOINC term is added to the MDQ and no codes are specified, the query will run an existence check and return any patients that have a record in the LAB_LOINC field.
     - In order to further define the query by prescribing record dates, the Observation Period term will need to be added to the MDQ.

· Observation Period term behavior:
     - Date ranges for the LOINC term are defined by adding an Observation Period term to the same MDQ criteria group. If an Observation Period term is not combined with a LOINC term in the same MDQ criteria group, LOINC dates will not be queried.
     - The date hierarchy for the LOINC term is as follows: MDQs with both the Prescribing term and Observation Period term use "SPECIMEN_DATE" as the primary date variable for the Lab table. If the "SPECIMEN_DATE" variable is NULL, the MDQ will assess the "RESULT_DATE " variable. If "SPECIMEN_DATE" and "RESULT_DATE " are both NULL, the MDQ will assess the "LAB_ORDER_DATE" variable. If "SPECIMEN_DATE", "RESULT_DATE ", and "LAB_ORDER_DATE" are all NULL, the record will be skipped/not counted. If any combination of "SPECIMEN_DATE", "RESULT_DATE ", and "LAB_ORDER_DATE" are populated, only the field highest up in the hierarchy is assessed.
     - In addition to defining the LOINC term date range, the Observation Period term simultaneously limits results to participants who have an Encounter table "ADMIT_DATE" value within the defined date range.  This encounter does not need to be present in the Lab table or linked to a Lab record—the MDQ simply looks for an encounter that falls within the date range specified. 

Release Notes

Fixed bug where if a Prescribing term and a Setting term were added to the same MDQ criteria group, they did not "AND" correctly and would return incorrect results. The MDQ Prescribing and Settings terms now combine correctly when included in the same criteria group.

Fixed attachment arrow in response detail tab so that it is now facing the correct direction

Aggregate view option is now removed for PopMedNet request types that have the "File Distribution" data model selected in the request type settings.

Fixed bug where certain users were incorrectly able to copy Question Engine request types in PopMedNet.