Release 7.8

Release Date: May 17th 2019

Connect Enhancements:

  • Smart Regimen Search:
    • The system shall show chemo drugs suggestion list on regimen search after a chemo drug entry. (#81598).
    • The system shall recalculate the drug suggestion list if the chemo drug list changes. (#81599).
    • The System shall display the number of regimen count based on drugs selected. If there is none then 0 will be shown. (#81601).
  • Regimen Search by Keywords:
    • Create regimen search by keywords administration page. One keyword can contain multiple drugs. Generic or Brand names can be added to a keyword. (#81585).
    • These keywords will be searchable on the same drug search box on regimen search page. After selecting a keyword, all drugs related to the keyword will be added to the selected drug section (#81587).
    • The system will display all warnings based on payer treatment configuration. (#81589).
    • The system shall not remove existing drugs on the list when a keyword is added. (#81590)
  • Payer Configuration: Remove 3 Week Cushion from Treatment End Date
    • The system shall include a configuration per payer that will remove the three-week cushion that is built into the Treatment End Date.
    • The system shall default to include the three-week cushion built into the Treatment End Date for treatment plans.
    • The system shall default the Treatment End Date to the actual end date of the treatment in the Treatment End Date field on the Enter Treatment Plan Dates screen when the payer is configured to have the three-week cushion removed.
    • The system shall display the following text on the Enter Treatment Plan Dates screen when the Payer is configured to remove the three-week cushion from the Treatment End Date:
      • Note that a 3 week-cushion has not been calculated into the treatment’s valid date range. 
    • The system shall not apply the new configuration to remove the 3 week cushion to clinical trials.
  • Add Logging to capture what users access Medical Records from the Provider, MO and Payer Dashboards.
  • Fix BCG Live Intravesical cost calculation.

KBWeb Enhancements:

  • Pathway UAT Report:
    • The system shall include a start and end date option in the search criteria when generating the Pathway Policy UAT report in KB Web.
    • The system shall not set any default dates for the Start or End Date in the search criteria for the Pathway UAT report.
    • The system shall require the user to enter an end date if the user enters a Start date in the search criteria for the Pathway UAT report.
    • The system shall only include any pathways/preferences that were added, modified or deleted within the start and end dates that were entered in the search criteria of the Pathway UAT Report.
    • The system shall include any newly added, removals or updating of preferences of a parent LOB when an LOB is sync’d with a parent LOB.
    • The system shall not include any pathways/preferences that were not newly created or modified during the start and end dates that were entered in the search criteria.
    • The system shall recognize the addition of a new Level to a regimen as a modification and shall be reflected in the Pathway UAT report.
    • The system shall include any regimens that are associated to a Level that was deactivated in the Pathway UAT report.
    • The system shall not include the addition or deletion of any Level(s) that are not associated to any regimens in the Pathway UAT report.
    • The system shall have the start and end date fields in the search criteria of the Pathway Policy UAT report as optional data fields.
    • The system shall include all Pathway Regimens (aka Preferred Regimens) that are included in Preference Management and any Pathway Regimen that was Deleted in the Pathway UAT report when the user does not enter a start and end date in the search criteria for the report.
    • The system shall include a Last Modified Date column in the Payer UAT Report.
    • The system shall display the date when the Pathway Regimen or its details associated to the Pathway/Preferred regimen was modified (newly created, modified or inactivated).
  • New Actions on Workflow Management:
    • The system shall include two new actions in the “Select an Action” dropdown in Workflow Management:
      • Send to Rules Review
      • Rules Review Completed
    • The system shall associate these new workflow action items with regimens (chemo, RT, Supportive Care and Justification Templates)
    • The system shall not associate these new workflow actions with Evidence.
    • The system shall list these new actions in between the “MD Reconcile Complete” action and the “Publish” Action.
    • The system shall pop up a window when the user clicks “Send to Rules Review” and shall include the following:
      • Assign to dropdown
      • Notes field (optional)
      • Cancel Button
      • Submit Button
    • The system shall assign the regimen to the user that was selected in the Assign to dropdown on the Send to Rules Review pop up window after the user clicks Submit.
    • The system shall display Send to Rules Review in the WF State and who the regimen is assigned to on the workflow management dashboard after the user completes the Send to Rules Review pop up and clicks Submit.
    • The system shall pop up a window that includes an optional notes field, a Cancel Button, Save Draft Button and Publish Button when the user selects the “Rules Review Complete” from the Actions dropdown.
    • The system shall allow the user to Publish a regimen from the “Rules Review Complete” pop up window.
    • The system shall include the following options in the WF State dropdown in the Search filters on Workflow Management:
      • Send to Rules Review
      • Rules Review Complete
    • The system shall capture when the regimen is associated to the “Send to Rules Review” or “Rules Review Complete” in the Audit tab of a regimen.
  • Medical Policy View Tab:
    • The system shall have the ability to view medical policy transformation metadata within the template view window when viewing a regimen from the medical policy management pages.  The metadata shall contain modifications information of the regimen due to the medical policy as well as any rules that may have been ignored.

Omics-Guided Eviti:

The system shall have the ability to extract PGx findings from the GPS JSON file. Each PGx finding includes the following information:

  • Gene – Allele (patient’s result)
  • PGx Drug
  • Explanation/recommendation text

The system will consult the GPS result (JSON) to determine if any Eviti regimens in the search result have pharmacogenomics omics guidance. The system will look to see if any drugs in the pharmacogenomics screening section of the JSON (PGx drugs) are mapped to drugs within the regimen search result (as defined in the drug mapping).

The system will display an Eviti regimen as having a pharmacogenomics warning in the Omics Guidance column when a PGx drug maps to a drug within any of the Eviti regimens in the search result set. This is applicable to both the Treatments and Eviti Library tabs only.

The system will not use the JSON PGx drugs for any search criteria or to filter any regimens or to sort any regimens.

The system will display section 3 text from the JSON (cropped to 30 characters) in the Omics Guidance column for any Eviti regimen that has a pharmacogenomics warning.

The system will have a pop-up (e.g., “Learn more…”) on the Omics Guidance text for any Eviti regimen that has a pharmacogenomics warning. The pop-up will include the sections 1, 2, and 3 text from the JSON.

If more than one drug from different findings map to the same Eviti regimen, an icon for each mapped drug and each finding’s text should be displayed. (e.g., two (warning) icons and two different texts)

If there is more than one PGx drug in a single finding, the system shall attempt to map each drug individually to see if the drugs are in any Eviti regimens in the search result set. If more than one drug from the same finding maps to the same regimen, the (warning) icon and associated text should only be displayed once. (i.e., the text should cover both drugs/genes)

Web Services:

  • REST10: ClinicalTrialSearch – Error when sending LineofTreatmentGuid