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 countbased on drugs selected. If there is none then 0 will be shown. (#81601).
    • The system shall not remove existing drugs on the list when a keyword is added. (#81590).
  • 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.

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)

 

Release 7.4

Release Notes: Release 7.4 (Deployment Date = 11/02/2018)

Connect Enhancements:

  • Drug Exclude: The system shall have a configuration (per payer/per LOB) that will allow the user to identify drugs that cannot be “entered” in a regimen search. (#75011)
  • Drug Exclude: The system shall allow the user to search for the drug (auto populate the drug name as the user is typing the drug) on Connect. (#75013)
  • Drug Exclude: The system will display a message when the user selects a drug that was identified to be excluded. (#75014)
  • Drug Exclude: The system will not pull the excluded drug in the chemo and supportive care drug “buckets” that appear on the search screen. (#75015)

Analyzer Enhancements:

  • FN Risk Analyzer: The system shall trigger a new Error message when the user enters a growth factor drug and the current warning message “Drugs not Found in Regimen” is triggered. (#75008)
  • FN Risk Analyzer: The system shall recognize the “Drugs Not Found” message then look to see if a growth factor drug was entered then trigger the new error message. (#75009)
  • FN Risk Analyzer: The system shall not display the “Drug Not Found in Regimen” message when the new Growth Factor Error message should appear. (#75010)
  • FN Risk Analyzer: It will not run on CTP Treatment Plan on any situation. (#75274)

System Enhancements:

  • Add support for DI Service locater in .net full framework (#75984)
  • Address compiler warnings for XML comments (#76007)
  • Update Drug loading process for AIM Beta3 Environments (#75670)
  • Add encryption and external configuration support. (#75566)
  • Security Update: Fix Web services exposing IIS Version # (#75507)

 

Release 6.6

Release 6.6 Release Notes (Deployment Date = November 17, 2017)

Connect Enhancements:

  • Modify Add Drug Requests from the Medical Office Dashboard: The internal Medical Office will have the ability to make modifications to Add Drug Requests that were submitted by provider admins. The Medical Office will have the ability to make modifications to the drug’s Dose, Cycles/Cycle Range and Days of Administration (57609, 57610).
  • Updates to the Payer Configuration in Connect: the Eviti Admin can modify Analyzer Deviations (Error, Warning or Info) that is associated to Analyzer Deviations (57611). The system will allow the Eviti Admin to do the following:
    • Analyzer Deviation Defaults:
    • Analyzer Deviation Groups
    • Analyzer Exception by Drug
  • Aetna (Kentucky) Eligibility: Aetna will be providing their patient eligibility information via Database Membership Eligibility. Modifications were made to the system to ensure we do not need a custom solution to receive this data. Please note, this does not include the actual eligibility file (59372).

AIM’s Workflow Enhancement:

  • Updates to the Cycle Analyzer to display Warnings when Cycles are less than allowed and Errors when cycle range for a drug is increased (57785).

Allscripts Web Services Enhancement:

  • Allscripts Integration with CTCA: The Regimen Webservices was updated to include the External Comments that are associated to the Clinically Significant updates to regimens (57723).

Medispan Updates:

  • New route “IE” introduced by the medispan weekly feed this morning needs to be added to the system.  There is currently only one drug using the new route – generic name: “Lidocaine 5% in 7.5% Dextrose Intraspinal Soln”, product name: LIDOCAINE HCL/DEXTROSE (58265)
  • Remove drug Mircera from drug feed (58749)

KB Web Enhancements:

  • The View Version and Read Only Review History links that appear on the Audit Tab in “edit mode” were both enabled so the content team can view the information was updated Audit Tab. When editing enable the read-only View Version and the read-only Review History (57790)
  • Performance Enhancements for Template Management: Backend updates were made to Template Management to improve the speed in which the page functions and renders results (57846).

 

Support Bug Fixes:

  • REST10 Regimen Search Lite returning empty set when PageSize and CurrentPage are sent in a request (55726).
  • Eviti Connect Webservice Log report not filtering (58666).
  • Oral JCode J8705 being swithed for IV JCode J9351 HYCAMTIN, TOPOTECAN HCL (57706)
  • Analyzer throwing deviation Errors for drug-level justification in ForAddDrugs subtemplate during initial tx entry (59418)

Release 6.6

Release 6.6 Release Notes (Deployment Date = November 17, 2017)

Connect Enhancements:

  • Modify Add Drug Requests from the Medical Office Dashboard: The internal Medical Office will have the ability to make modifications to Add Drug Requests that were submitted by provider admins. The Medical Office will have the ability to make modifications to the drug’s Dose, Cycles/Cycle Range and Days of Administration (57609, 57610).
  • Updates to the Payer Configuration in Connect: the Eviti Admin can modify Analyzer Deviations (Error, Warning or Info) that is associated to Analyzer Deviations (57611). The system will allow the Eviti Admin to do the following:
    • Analyzer Deviation Defaults:
    • Analyzer Deviation Groups
    • Analyzer Exception by Drug
  • Aetna (Kentucky) Eligibility: Aetna will be providing their patient eligibility information via Database Membership Eligibility. Modifications were made to the system to ensure we do not need a custom solution to receive this data. Please note, this does not include the actual eligibility file (59372).

AIM’s Workflow Enhancement:

  • Updates to the Cycle Analyzer to display Warnings when Cycles are less than allowed and Errors when cycle range for a drug is increased (57785).

Allscripts Web Services Enhancement:

  • Allscripts Integration with CTCA: The Regimen Webservices was updated to include the External Comments that are associated to the Clinically Significant updates to regimens (57723).

Medispan Updates:

  • New route “IE” introduced by the medispan weekly feed this morning needs to be added to the system.  There is currently only one drug using the new route – generic name: “Lidocaine 5% in 7.5% Dextrose Intraspinal Soln”, product name: LIDOCAINE HCL/DEXTROSE (58265)
  • Remove drug Mircera from drug feed (58749)

KB Web Enhancements:

  • The View Version and Read Only Review History links that appear on the Audit Tab in “edit mode” were both enabled so the content team can view the information was updated Audit Tab. When editing enable the read-only View Version and the read-only Review History (57790)
  • Performance Enhancements for Template Management: Backend updates were made to Template Management to improve the speed in which the page functions and renders results (57846).

Support Bug Fixes:

  • REST10 Regimen Search Lite returning empty set when PageSize and CurrentPage are sent in a request (55726).
  • Eviti Connect Webservice Log report not filtering (58666).
  • Oral JCode J8705 being swithed for IV JCode J9351 HYCAMTIN, TOPOTECAN HCL (57706)
  • Analyzer throwing deviation Errors for drug-level justification in ForAddDrugs subtemplate during initial tx entry (59418)

Release 6.4 Release Notes (Deployment Date = 8/11/2017)

Baseline Connect and AIM Workflow:

  • Modification to the “Add Drug” Workflow to allow users to modify the cycle range of the supportive drug that is being added to the approved care plan. This includes updates to the treatment plan builder (549009) and to the Analyzer (55684).

eviti|Advisor:

  • Modifying how Justifications are displayed in Advisor (54933).
  • Updating the Clinical Trials Index and UI to display more details to support the clinical trials summaries (54491 & 54477)

eviti|Advisor Enterprise:

  • Updated the Provider Dashboard to include a Provider Type Column (Medical Oncologist or Radiation Oncologist) (54268)

KB Web:

  • New Medical Policy Rule: Supportive Care Hide Rule (52585)
  • Creation of new reports:
    • FDA Approvals Report (55755)
    • Medical Policy QA Report (55681)
    • Pathway Policy UAT Report (54932)
  • Modifications to the following reports:
    • Medical Policy Maintenance Report (54636)
    • Clinical Significant Report (56649)
  • Addressed outstanding issue associated to copying templates (55742)

AIM EMR Integration (FHIR):

  • Update FHIR format for CancerType and MedicationOrder (55887)
  • FHIR Data with only cancer type failing due to no observation (56346)

Web Services:

  • Decommissioning the SOAP10 Web Services (56400)

 Data Center Migration:

  • Production Waltham deployment setup (55731)
  • Deployment Processing Performance Improvements (55722)

 Miscellaneous Bug Fixes:

  • Med Policy rules are being applied multiple times in certain scenarios (54838)
  • Med Policy Maintenance Report – The “Submit” button is too far to the right (54318)
  • EvTaskProcessor – reference command causes log error during serialization (56628)
  • Generic javascript error on attachments page (54591)
  • REST: api/advisor/transaction/create does not require an NPI (54968)
  • KB: Unable to Add Space or Special Character when Editing Omic Value or Omic Target name (55060)
  • Soap11 Documentation showing at version 10 (56470)
  • Payer-Specific value not retained when copying supportive subtemplates (56985)
  • Incorrect trial listing+server error on ‘View location’ pop up when searching using an invalid trial ID for eviti(for e.g.foreign trial,inactive trial without sites etc.) (55693)
  • Search result is not cleared when valid trial search is followed by an invalid trial search (55694)
  • Server error when searching using invalid trial ID in combination with zip code search (55695)
  • Sub templates are not being pulled when searching with brand name or HCPC during Supportive Drug Exclude Rule creation (55081)

Release 6.2 Release Notes

Release 6.2 Release Notes (Deployment Date = 4/7/2017)

Notable Enhancements:
• Background Processing: Update Local Cache and Emails to Leverage Active MQ (Micro Services) (52310)
• Separation of SOAP and REST Services (53180).
• Modify Alternative Regimen Search & Advisor Search so that Her2Neu BioMarker Takes Precedence and only Returns Regimens with Her2Neu Requirement and Corresponding Value (53202).

Support Bug Fixes & Tasks to Support Existing Functionality by Application:

AIM Workflow:
• Server Error When Accessing Regimen Print Screen via CaseID (53339).
• Duplicate BioMarker Issue (53171)
AIM EMR Integration (FHIR):
• Update Append FHIR Webservice Results to Report When Treatment Intent = Metastatic and Stage <>Recurrent (53236).
• Create a Warning Message and Send to AIM when Add Drug is Attempted via FHIR or MR Integration; block user in UI from Continuing and Display Message that Add Drug is Not Allowed via EMR Integration (53237).
• When We Receive Data that Maps but isn’t Clinically Appropriate (violates filters) Display the Warning Message that the Data Could Not be Mapped and Do No Pre-populate Value (53239).

eviti|Connect:
• “In Situ” Pathologies on Landing Page Currently Allows for All Stages to be Selected (53238).
• Deleted Drug via Drug Revision is Displayed on Regimen Search Page During Next Add Drugs, although Deleted Drug is not Present on Treatment Plan (24359).
• All linked Chemo Drugs are Displayed on Regimen Search Page While Adding Drugs (*When the User Searches Using Linked Drug Rather Than the Original from Regimen to Pull it) (30364).
• CPT Code Lookup File Does Not Open in IE11 (eviti Modification Screen) (46672).
• Erroneous Justification for Regimen: Pertuzumab, Trastuzumab (Herceptin) and Docetaxel (Taxotere) (Metastatic/Recurrent, First Line) (47369).
• Javascript error when trying to print from the RegimenSearch page (53352).
• “Thread was being aborted” error at Enter Dates page (53353).

eviti|Advisor:
• Re-ordering of the Trial Type Names that Appear in the “Filter by Trial Type” Dropdown Box (53641).
• Modify the Message that Appears on the “Loading” Pop up Window (53651)
• Change the Cancer Moonshot Trial Icon to Cancer Breakthroughs Trial Icon (53720)
• Server Error when Searching for Trial by Zip Code After Filtering by Trial Name and/or ID (53724).

Webservices:
• Add “IsActive” Property to REST Services Results (53172).
• Regimen/Search Make Supportive-Only Filter Nullable in Rest Services (53229).
• Update REST regimens/history to return Parent Templates that are associated to Sub-Templates that Receive Clinically Significant Updates (50567).
• REST services that Produce (500 Server Errors) Include Stack Traces (52208)
• Update Copyright Statement to Reflect Current Year and NantHealth, Inc. (53290).
• Remove Antiemetic and Growth Factor Costs Fields from Lower Level Objects in Rest Services (53486).
• Webservices 9.0 Account Status Unable to be Set to Inactive (42561).
• Add Drug Cache Check to Webservice Ping Method (46387).
• SECURITY: Exceptions are shown in all 500 REST errors (53372).

KB Web:
• Supportive Drug Exclude Rule Only Removes One Instance of Drug From Regimen (53003).
• Clinically Significant Sub Template Updates to Update Parent Templates (50932).
• Supportive Drug Exclude Rule is Not Being Applied to Regimen (Supportive Drug Exclude Rule is Applied on Top of Supportive Care Override Rule) (53074).
• Change Max Dose of HCPC Code J9218 tot 1 in hcpcselector table (53547).