Merative ™ Social Program Management 7.0.0.1

Release Notes

Abstract

Merative Social Program Management 7.0.0.1 Release Notes

Content

Introduction
System Requirements
Download
Installation
Improvements, Resolved Issues and Third Party 
Known Issues
Notices

Introduction

Welcome to the Merative Social Program Management 7.0.0.1 release.

Full product documentation can be found in the documentation.

For the latest version of the release notes, see https://curam-spm-devops.github.io/wh-support-docs/spm/release-notes.

This 7.0.0.1 release incorporates content from previous 6.2.x releases, which is documented separately in the following sets of online release notes:

• [Merative Social Program Management 6.2.0.3](http://www-01.ibm.com/support/docview.wss?uid=swg27049140)

System Requirements

For information about the supported software and hardware for this release, see the Merative Social Program Management Prerequisites.

Download

See the download instructions for this release at /support/curam.

Installation

Prior to running the installer please ensure all files in Merative Social Program Management installation are writable.

The installation steps are as follows:

• Extract the contents of the zip file to a local drive location.
• Run the Merative Social Program Management installer, which can be found in the INSTALLER folder at that location.
• After installing, the appropriate build targets must be run as necessary for your installation.

Additional installation instructions can be found in the Development Environment Installation Guide.

Upgrading

If you are upgrading from a previous version, the Merative Social Program Management Upgrade Helper contains documentation and tooling to help you to upgrade your Merative Social Program Management application codebase and database to work with your new version of Merative Social Program Management. The Merative Social Program Management Upgrade Guide describes a recommended process for performing application and database upgrades. The Upgrade Helper contains tools to assist you with implementing the upgrade, including tooling to produce a schedule of required migrations for your upgrade, tooling to provide information about database schema changes and tooling to generate initial SQL scripts for applying changes to your database.

To download the appropriate version of the Merative Social Program Management Upgrade Helper, see the download instructions at /support/spm.

Improvements, Resolved Issues and Third Party Updates

Cúram Enterprise Framework

Integrated Case Management

PO06563, WorkItem:172358 - The Close Button on the Special Caution is difficult to see

Previously, when a special caution was created and a user clicked on the special caution the visibility of the close button was poor. This issue has been resolved. Now when a user selects the special caution, the close button is highlighted.

ELIGIBILITY & ENTITLEMENT

PO06522, WorkItem:170686 - Prevent the application writing redundant records to AttributedEvidence table

Data on the table ATTRIBUTEDEVIDENCE is used by Classic Rules only, it is not used by Curam Express Rules. Previously ATTRIBUTEDEVIDENCE was populated regardless of whether using Classic Rules or Curam Express Rules (CER). These records were redundant for CER yet contributed towards database size. This has been resolved, now, a check is carried out to determine which rules infrastructure is used and the ATTRIBUTEDEVIDENCE table is only populated when the product delivery case uses Classic Rules.

INCIDENTS

WorkItem:122917 - Unable to record an incident where the reporter was not the currently logged on user

Previously, only the currently logged in user had permission to be recorded as a reporter of an incident. The case worker, could not save an Incident where a different user was selected was selected as the reporter. This issue has been resolved, now all users have can be recorded as reporters of an incident.

PARTICIPANT MANAGEMENT

PO04534, WorkItem:123084 - Name of the contact not always fully visible when capturing a new contact

Previously, when a user was adding a new contact who was not previously registered on the system, if the contact's name exceeded 18 characters, the name was not fully visible to the caseworker. This issue has been resolved by extending the width of the contacts name field up to 55 characters.

Application Development Environment

WorkItem:183264 - Reduce growth rate of the application's browser memory footprint, especially in Internet Explorer Version 11

Previously, Internet Explorer Version 11 was becoming unresponsive when a user browsed through a large number of pages in the application. This was due to a memory issue that resulted in the Internet Explorer process memory increasing at a much higher rate than before. This issue has now been resolved.

CLIENT DEVELOPMENT ENVIRONMENT

WIDGETS

WorkItem:183247 - Microsoft Word does not start using Word Integration with Google Chrome 49

Users could not use the Microsoft Word integration functionality in the Curam application with Chrome version 49. Microsoft Word would not load. This was due to a change in how Google calculates timestamps for events. This has now been fixed.

Cúram Modules

FINANCIALS

PO04607, WorkItem:103298 - User unable to setup a deduction in spite of an existing active liability for the provider

Previously, when an active liability was created for a provider as a result of an over-payment, it was not getting listed on the application. This prevented the user from being able to set up a deduction against the liability.

This has now been resolved and the liability created for a provider gets listed on the list of active liabilities.

Universal Access

PO06725, WorkItem:178574 - Accessibility: Focus order of 'Back' and 'Next' buttons is reversed on some Citizen Portal pages

Previously, when a user selected the 'Apply for assistance with your Health Care' option on the Citizen Portal, the user interface on the next screen had an inconsistent tab navigation. The tab order was found to be 'right to left' instead of 'left to right'.

This has now been resolved and the user is now able to tab through the options 'left to right' as expected.

PO03827, WorkItem:181838 - The Evidence Mapping Configuration entity is missing descriptions for its attributes

Previously, some of the attributes in the 'Evidence Mapping Configuration' entity were missing descriptions or had incorrect descriptions leading to ambiguous interpretations about the utility of these attributes.

This has now been resolved by providing appropriate attribute descriptions.

PO06145, WorkItem:181840 - Life event pages suppress exceptions instead of returning errors to users

Previously, when the user performed any action on citizen life events functionality that resulted in an application exception, the exception was not getting handled appropriately. No meaningful error message was displayed to the end user.

This has now been resolved by appropriately handling the application exception and displaying a meaningful error message to the user.

PO06408, WorkItem:181877 - Application Logo not returning the user to the landing page in Arabic locale.

The 'Merative SPM Universal Access ' logo at top right corner of the Citizen Portal application, when clicked, is meant to redirect the user to the Citizen Portal landing page. This was not happening in the Arabic version of the Curam application.

This has now been resolved by redirecting the user to the Citizen Portal application's landing page when the user clicks the 'Merative SPM Universal Access' logo.

WorkItem:182726 - Change the wording of the Save or Exit Motivation page to clarify semantics of choosing to Exit

When a user resumed an existing in-progress application and then choose to quit again, the option “Quit without saving your application” did not make it clear to the user that the entire application will be deleted, not just the changes that were made after the in-progress application was resumed. The option has been renamed to “Quit and Delete your Application” to make it clear to the user that the entire application will be deleted and the user will not be able to return to the application again.

Evidence Broker

PO04222, WorkItem:122885 - Static evidence involving more than one case member should only be shared to the target case when both members exist are on the target case.

For sharing evidence which involves more than one person, one of the sharing rules is that where two case members are involved in an evidence record, the evidence should not be shared unless both case members are on the target case. Previously this sharing rule was not working when sharing static evidence. Static evidence was incorrectly being shared to the target case and the second person added as a case member. This has been resolved and the evidence sharing rules work as expected, where sharing static evidence which involves two case members, the evidence is not shared to the target case unless both case members exist on the target case.

PO05116, WorkItem:123292 - Sharing Identifications evidence to Person with empty ID Reference causes application errors when creating or editing evidence.

Previously using the non-identical flow to share Identifications evidence to a Person containing a blank ID Reference attribute, subsequently attempting to add or edit other dynamic evidence for that Person resulted in an unhandled server exception. This scenario only occurred when the design of the evidence at the source case was such that the alternateID attribute was not set to mandatory, which left the possibility of it not being populated on sharing to Person, This issue is now resolved.

PO06355, WorkItem:162029 - Unable to activate the SSN Details on an Integrated Case after accepting an incoming evidence update from the Identifcations Evidence

Previously, there was an issue with the non-identical evidence flow where Person Identifications evidence was mapped to SSN Details evidence at a case level. When Identifications evidence was modified and saved on a Person and shared to a case as SSN Details evidence, the subsequent activation of the SSN Details evidence on the target case caused an exception to be thrown. This issue has been resolved. Now, when updates are made to Identifications evidence, once the change is accepted and activated on the target case, the activation of the evidence completes successfully.

Provider Match with Watson

WorkItem:178086 - Provider Match fails to build the request to Watson Tradeoff Analytics due to localised content issues - Cost with comma

Previously, there was an issue calculating the service offering rates for locales that use the comma character to separate the decimal value (e.g. 100,00 rather than 100.00). As cost was used in the trade-off of providers, this problem caused all providers to be excluded from trade-off.

This has been fixed so that the cost value is calculated correctly, allowing Provider Match with Watson to complete the trade-off.

WorkItem:179122 - Provider Match fails to build the request to Watson Tradeoff Analytics due to localised content issues - Proximity calculation

There was a defect where the trade-off request would fail for certain locales due to the proximity calculation. This has been addressed and is now calculating the proximity correctly based on the provider address and the clients primary address.

WorkItem:179736 - The specific service selection set is not being used for provider matching

There was an issue where the default selection set for Provider Match with Watson was being used, regardless of any service specific configuration.

This was resolved by introducing a check for a valid service selection set to use in the provider trade-off. If the specific selection set is not present or is invalid (contains less than three criterion) the default criteria set will be used.

There is also a change to support the customization of the trade-off request used by Merative Provider Match with Watson. This will allow new criteria to be added and used in the provider trade-off. For more information please read Customizing the default provider selection criteria section for Provider Match with Watson in the documentation.

Solutions

Income Support

PO06014, WorkItem:178666 - Incorrect allowable and non allowable self employment expense amounts are displayed on the Integrated Case Income screen when applying for Cash Assistance

Previously, incorrect allowable and non allowable self employment expense amounts were displayed on the Integrated Case Income screen when applying for Cash Assistance. The values were displayed as a greater amount that they should have been.

Now, this has been corrected. The values are no longer being incorrectly multiplied. All Farm, Non Farm, Conservational, Feed and Purchase allowable and non allowable self employment expenses on the Income, Household and Member screens are displaying correct values.

The Employment Expense Decision Table has been updated. The expense types: Freight and Trucking, Office Expenses have now Business or Total Amount for Farm allowable expenses. The expense types: Depreciation, Transportation Costs, Meals/Entertainment have now Business or Total Amount for Non Farm allowable expenses.

Technical details:

/EJBServer/components/ISCashAssistance
/CREOLE_Rule_Sets/CashAssistanceRuleSet.xml

• Class: CASelfEmploymentIncomeHelper
  • totalAllowableEmploymentExpensesTimeline: Updated
• Class: CAEmploymentExpenseTypesDecisionTable
  • allowableFarmExpenseTypesTimeline: Updated
  • allowableNonFarmExpenseTypesTimeline: Updated
• Class: CAExcludedEmploymentExpenseTypesDecisionTable
  • excludedFarmExpenseTypesTimeline: Updated
  • excludedNonFarmExpenseTypesTimeline: Updated

/EJBServer/components/ISCashAssistance
/CREOLE_Rule_Sets/CashAssistance/ProductDisplay/
Income/Household/CAHouseholdIncomeCategory.xml

• Class: CAHouseholdIncomeCategory
  • allNonFarmCASelfEmploymentHelpersForHousehold: New attribute
  • allFarmCASelfEmploymentHelpersForHousehold: New attribute
  • partialAllowableSelfEmploymentExpensesDisplayList: New attribute
  • partialExcludedSelfEmploymentExpensesDisplayList: New attribute
  • allAllowableNonFarmSelfEmploymentExpensesDisplayList: Updated
  • allAllowableFarmSelfEmploymentExpensesDisplayList: Updated
  • allAllowableSelfEmploymentExpensesDisplayList: Updated
  • allExcludedNonFarmSelfEmploymentExpensesDisplayList: Updated
  • allExcludedFarmSelfEmploymentExpensesDisplayList: Updated
  • allExcludedSelfEmploymentExpensesDisplayList: Updated

/EJBServer/components/ISCashAssistance
/CREOLE_Rule_Sets/CashAssistance/ProductDisplay/
Income/Member/CAMemberSelfEmployment
ExpensesDisplayCalculator.xml

• Class: CAMemberSEExpensesDisplayCalculator
• selfEmploymentExpensesDisplayList: Updated

PO05750, WorkItem:178667 - Absent Parent Evidence is not being created when no address information is entered during an Intake Application

Previously, when Absent Parent evidence was entered during an Intake Application, the user was not required to enter address information. As a result, Absent Parent evidence was not created.

Now, if a user enters Absent Parent information, they cannot proceed with the application until address information has been provided.

WorkItem:178668 - Address of primary applicant is being mapped as the current date, where as the address of second applicant is mapped to date that they joined the household when creating an application

Previously, after creating an application, the value of the primary applicant's address start date was incorrectly set as the current date and prevented the applicant's address evidence from being applied.

Now, after creating an application, if the address start date of the primary applicant is after the date that the applicant joined the household, the address start date will be set as the household member evidence start date.

WorkItem:178669 - Retroactive Eligibility not displaying correct results on an Integrated Case

Previously, on the Integrated Case, the Check Eligibility results for Retroactive Medical was displaying incorrectly as "Ineligible for all programs" on the Eligible column. This was even if the member was eligible for Retroactive Medical Assistance which was correctly shown while expanding the List Page.

This has now been fixed and the correct message value, Retroactive Medical Assistance, is displaying on the referred column when the member is found eligible.

WorkItem:178828 - The Details page for the Total Countable Income of the Member Income section of a Qualified Medicare Beneficiaries program decision is not displayed

Previously, the Details page for the Total Countable Income of the Member Income section of a Qualified Medicare Beneficiaries program decision was not displayed when Check Eligibility was performed at the Application or Integrated case.

Now, this has been corrected and the page is displayed correctly to show the Total Countable Income.

Technical details:

/EJBServer/components/ISMedicalAssistance/
CREOLE_Rule_Sets/MedicalAssistance/QMB/
ProductDisplay/QMBMemberIncomeCategory.xml

• Class: QMBMemberIncomeCategory
• abdMemberCountableIncomeSubscreenName: Updated
• caseParticipantRoleRecord: New
• qmbMemberCountableIncomeSubscreens: New
• summarySubscreenNames: New

/EJBServer/components/ISMedicalAssistance/
CREOLE_Rule_Sets/MedicalAssistance/QDWI/
ProductDisplay/QDWIMemberIncomeCategory.xml

• Class: QDWIMemberIncomeCategory
• abdMemberCountableIncomeSubscreenName: Updated
• caseParticipantRoleRecord: New
• qdwiMemberCountableIncomeSubscreens: New
• summarySubscreenNames: New

/EJBServer/components/ISMedicalAssistance/
CREOLE_Rule_Sets/MedicalAssistance/QI/
ProductDisplay/QIMemberIncomeCategory.xml

• Class: QIMemberIncomeCategory
• abdMemberCountableIncomeSubscreenName: Updated
• caseParticipantRoleRecord: New
• qiMemberCountableIncomeSubscreens: New
• summarySubscreenNames: New

/EJBServer/components/ISMedicalAssistance/
CREOLE_Rule_Sets/MedicalAssistance/SLMB/
ProductDisplay/SLMBMemberIncomeCategory.xml

• Class: SLMBMemberIncomeCategory
  • abdMemberCountableIncomeSubscreenName: Updated
  • caseParticipantRoleRecord: New
  • slmbMemberCountableIncomeSubscreens: New
  • summarySubscreenNames: New

/EJBServer/components/ISMedicalAssistance/
CREOLE_Rule_Sets/MedicalAssistance/QDWI/
ProductDisplay/QDWIMemberCountableIncomeSubscreen.xml

• Class: QDWIMemberCountableIncomeSubscreen New
  • maTotalDeemedIncomeCPRCalculator: New
  • generalIncomeDisregardAmountTimeline: New
  • totalNetUnearnedIncomeTimeline: New
  • totalEarnedIncomeTimeline: New
  • remainingGeneralIncomeDisregardAmountTimeline: New
  • allCountableEarnedIncomeDisplayListItems: New
  • totalHouseholdSelfEmploymentLossTimeline: New
  • dollar65EarnedIncomeDeductionTimeline: New
  • totalImpairmentRelatedWorkExpensesAmountTimeline: New
  • earnedIncomeHalfDeductionTimeline: New
  • totalNetEarnedIncomeTimeline: New
  • totalUnearnedIncomeTimeline: New
  • allCountableUnearnedIncomeDisplayListItems: New
  • totalBoarderLodgerIncomeTimeline: New

/EJBServer/components/ISMedicalAssistance/
CREOLE_Rule_Sets/MedicalAssistance/QI/
ProductDisplay/QIMemberCountable
IncomeSubscreen.xml

• Class: QIMemberCountableIncomeSubscreen New
  • maTotalDeemedIncomeCPRCalculator: New
  • generalIncomeDisregardAmountTimeline: New
  • totalNetUnearnedIncomeTimeline: New
  • totalEarnedIncomeTimeline: New
  • remainingGeneralIncomeDisregardAmountTimeline: New
  • allCountableEarnedIncomeDisplayListItems: New
  • totalHouseholdSelfEmploymentLossTimeline: New
  • dollar65EarnedIncomeDeductionTimeline: New
  • totalImpairmentRelatedWorkExpensesAmountTimeline: New
  • earnedIncomeHalfDeductionTimeline: New
  • totalNetEarnedIncomeTimeline: New
  • totalUnearnedIncomeTimeline: New
  • allCountableUnearnedIncomeDisplayListItems: New
  • totalBoarderLodgerIncomeTimeline: New

/EJBServer/components/ISMedicalAssistance/
CREOLE_Rule_Sets/MedicalAssistance/SLMB/
ProductDisplay

• Class: SLMBMemberCountableIncomeSubscreen New
  • maTotalDeemedIncomeCPRCalculator: New
  • generalIncomeDisregardAmountTimeline: New
  • totalNetUnearnedIncomeTimeline: New
  • totalEarnedIncomeTimeline: New
  • remainingGeneralIncomeDisregardAmountTimeline: New
  • allCountableEarnedIncomeDisplayListItems: New
  • totalHouseholdSelfEmploymentLossTimeline: New
  • dollar65EarnedIncomeDeductionTimeline: New
  • totalImpairmentRelatedWorkExpensesAmountTimeline: New
  • earnedIncomeHalfDeductionTimeline: New
  • totalNetEarnedIncomeTimeline: New
  • totalUnearnedIncomeTimeline: New
  • allCountableUnearnedIncomeDisplayListItems: New
  • totalBoarderLodgerIncomeTimeline: New

The following files have been updated to show the new sub screens:

/EJBServer/components/ISMedicalAssistance/data/initial/
clob/ProductDisplay/IC/MedicareCostSharing/QMB/QMBDecision
_memberCountableIncomeDetails.properties

/EJBServer/components/ISMedicalAssistance/data/initial/clob/
ProductDisplay/PD/MedicareCostSharing/QMB/QMBPDDecision
_income.properties

/EJBServer/components/ISMedicalAssistance/data/initial/clob/
ProductDisplay/IC/MedicareCostSharing/QDWI/QDWIDecision
_memberCountableIncomeDetails.properties

/EJBServer/components/ISMedicalAssistance/data/initial/clob/
ProductDisplay/PD/MedicareCostSharing/QDWI/QDWIPDDecision
_memberCountableIncomeDetails.properties

/EJBServer/components/ISMedicalAssistance/data/initial/clob/
ProductDisplay/IC/MedicareCostSharing/QI/QIDecision
_memberCountableIncomeDetails.properties

/EJBServer/components/ISMedicalAssistance/data/initial/clob/
ProductDisplay/PD/MedicareCostSharing/QI/QIPDDecision
_memberCountableIncomeDetails.properties

/EJBServer/components/ISMedicalAssistance/data/initial/clob/
ProductDisplay/IC/MedicareCostSharing/SLMB/SLMBDecision
_memberCountableIncomeDetails.properties

/EJBServer/components/ISMedicalAssistance/data/initial/clob/
ProductDisplay/PD/MedicareCostSharing/SLMB/SLMBPDDecision
_memberCountableIncomeDetails.properties

/EJBServer/components/ISMedicalAssistance/data/initial/clob/
ProductDisplay/IC/MedicareCostSharing/QMB/QMBDecision
_memberCountableIncomeDetails.uim

/EJBServer/components/ISMedicalAssistance/data/initial/clob/
ProductDisplay/PD/MedicareCostSharing/QMB/QMBPDDecision
_income.uim

/EJBServer/components/ISMedicalAssistance/data/initial/clob/
ProductDisplay/IC/MedicareCostSharing/QDWI/QDWIDecision
_memberCountableIncomeDetails.uim

/EJBServer/components/ISMedicalAssistance/data/initial/clob/
ProductDisplay/PD/MedicareCostSharing/QDWI/QDWIPDDecision
_memberCountableIncomeDetails.uim

/EJBServer/components/ISMedicalAssistance/data/initial/clob/
ProductDisplay/IC/MedicareCostSharing/QI/QIDecision
_memberCountableIncomeDetails.uim

/EJBServer/components/ISMedicalAssistance/data/initial/clob/
ProductDisplay/PD/MedicareCostSharing/QI/QIPDDecision
_memberCountableIncomeDetails.uim

/EJBServer/components/ISMedicalAssistance/data/initial/clob/
ProductDisplay/IC/MedicareCostSharing/SLMB/SLMBDecision
_memberCountableIncomeDetails.uim

/EJBServer/components/ISMedicalAssistance/data/initial/clob/
ProductDisplay/PD/MedicareCostSharing/SLMB/SLMBPDDecision
_memberCountableIncomeDetails.uim

WorkItem:178894 - When viewing an eligibility decision of Specified Low-Income Medicare Beneficiary on an Integrated Case, the Countable Income sub-screen is not displayed

Previously, after accessing an eligibility decision of Specified Low-Income Medicare Beneficiary on an Application Case, Integrated Case or Product Delivery Case, the Countable Income sub-screen was not displayed.

To resolve this, the SLMB_memberCountableIncome
Details.properties, located in ISMedicalAssistance\data\
initial\clob\ProductDisplay\IC\MedicareCostSharing\SLMB, was updated to reference the Medical Assistance sub-screen.

Now, when viewing an eligibility decision from an Application Case, Integrated Case or Product Delivery Case, the Countable Income sub-screen is displayed.

WorkItem:179081 - Create Certification Period hook ignores the custom implementation

Previously, the Create Certification Period hook provided OOTB ignored the custom implementation and always called the OOTB class.

This has been fixed and now when a Product Delivery case is created the correct custom implementation for creating a new certification period is called.

WorkItem:179082 - Program recommendation authorization validations are to be made configurable

Previously, the following validation on program determination could not be enabled or disabled by the sysadmin:

-%1s already has an active Product Delivery for %2s in Case %3s.\nIf you want to use the current Product Delivery, please close original Product Delivery first.\n If you want to keep the original Product Delivery, withdraw the current case.

- %1s already has a Product Delivery for %2s in Case %3s which is currently inactive.\nIf you want to use the current Product Delivery, please close original Product Delivery first.\n If you want to keep the original Product Delivery, withdraw the current case.

Now, they can be enabled/disabled by the sysadmin with the following validation references:

- programrecommendationauthorization.err_
assistance_unit_members_already_in_active_pd|c|

- programrecommendationauthorization.err_
assistance_unit_members_already_in_inactive_pd|c|

WorkItem:179312 - On the Specified Low-Income Medicare Beneficiaries Decision Income tab, the Self Employment field on the Household Income screen is displaying a value when there is no Self Employment evidence for the participants on the case

Previously, on the Specified Low-Income Medicare Beneficiaries Decision Income tab, the Self Employment field on the Household Income screen was displaying a value when there was no Self Employment evidence for the participants on the case and the value should have been 0.

This has now been fixed. The Self Employment field displays 0 when there is no Self Employment evidence for the participants.

Technical Changes:

• Ruleset Path: /EJBServer/components/ISMedicalAssistance/CREOLE_Rule_Sets/
  MedicalAssistance/SLMB/ProductDisplay/SLMBHouseholdIncomeCategory.xml
  • Ruleclass: SLMBHouseholdIncomeCategory
  • Attribute: totalSelfEmploymentIncomeTimeline - Updated

WorkItem:179726 - When viewing an eligibility decision of Qualified Individual on an Application, Integrated Case or Product Delivery Case, the Countable Income sub-screen is not displayed

Previously, after accessing an eligibility decision of Qualified Individual on an Application, Integrated Case or Product Delivery Case, the Countable Income sub-screen was not displayed.

To resolve this, the QIDecision_memberCountableIncomeDetails.properties, located in

ISMedicalAssistance\data\initial\clob\ProductDisplay\IC\
MedicareCostSharing\QI, were updated to reference the Medical Assistance sub-screen. Now, the Countable Income sub-screen is displayed.

WorkItem:179833 - Earned income incorrectly includes eligible spouse's self employment gross receipts in earned income calculation when applying for Aged Blind Disabled program

Previously, when a spouse had a Self Employment evidence record, the Earned Income and Gross Income values located on the Member Income screen of the Integrated Case Income tab were incorrectly calculated when applying for the Aged Blind Disabled Program.

This has now been fixed. The Earned Income and Gross Income give the correct value on the Member Income screen.

Technical details:

/EJBServer/components/ISMedicalAssistance/
CREOLE_Rule_Sets/MedicalAssistanceRuleSet.xml
Class: MAIncomeCPRCalculator
totalGrossEarnedIncomeTimeline: Updated

WorkItem:179973 - Incorrect Total Gross Income on the Household Income section of a Qualified Medicare Beneficiaries program decision when Check Eligibility performed on Application or Integrated case

Previously, an incorrect Total Gross Income was displayed on the Household Income section of a Qualified Medicare Beneficiaries program decision when Check Eligibility was performed at the Application or Integrated case. The Total Gross Income value did not include the deemed income.

Now, this has been corrected and the Total Gross Income is displayed correctly.

Technical details:

/EJBServer/components/ISMedicalAssistance/CREOLE_Rule_Sets/
MedicalAssistance/QMB/ProductDisplay/QMBHousehold
IncomeCategory.xml

• Class: QMBHouseholdIncomeCategory
  • totalHouseholdMonthlyGrossIncomeTimeline: Updated

WorkItem:179978 - On the Household Income section of a Qualified Medicare Beneficiaries program decision, an ineligible spouse's unearned income is listed in the display under Total Deemed Income but not counted as part of the Unearned Income total

Previously, on the Household Income section of a Qualified Medicare Beneficiaries program decision, an ineligible spouse's unearned income was listed in the display under Total Deemed Income but not counted as part of the Unearned Income total. This occurred when Check Eligibility was performed at the Application or Integrated case for an application consisting of a husband and wife.

This has now been corrected and both spouse’s unearned income are displayed and counted in the decision.

The logic for the totalHouseholdMonthlyGrossUnearnedIncomeTimeline attribute was changed in the QMBHouseholdIncomeCategory.xml ruleset located in IS MedicalAssistance\CREOLE_Rule_Sets\
MedicalAssistance\QMB\ProductDisplay.

WorkItem:179980 - Ineligible Spouse Earned Income is not being included or is being displayed for a Qualified Medicare Beneficiaries program decision

Previously, the Ineligible Spouse Earned Income was not included in the total amount for Earned Deemed Income. Further to this, no Total Deemed Income was displayed on the Household Income section of a Qualified Medicare Beneficiaries program decision when Check Eligibility was performed on an Application or Integrated Case.

Now, this has been corrected and the total amount for Earned Deemed Income of the Ineligible Spouse is displayed correctly and a new row has been added to display Total Deemed Income under Earned Income.

Technical details:

/EJBServer/components/ISMedicalAssistance/CREOLE_
Rule_Sets/MedicalAssistanceRuleSet.xml

• Class: MATotalDeemedIncomeCPRCalculator
  • totalDeemedNetEarnedIncomeTimeline: New

/EJBServer/components/ISMedicalAssistance/CREOLE_
Rule_Sets/MedicalAssistance/Common/Income/
ProductDisplay/Household/MAHouseholdEarned
IncomeSubscreen.xml

• Class: MAHouseholdEarnedIncomeSubscreen
  • totalDeemedNetEarnedIncomeTimeline:New
  • listOfHouseholdCountableEarnedIncomeDisplayList:Updated
  • doesHouseholdHaveEarnedIncomeTimeline:Updated

/EJBServer/components/ISMedicalAssistance/CREOLE_
Rule_Sets/MedicalAssistance/Common/Income/ProductDisplay/
Household/MAHouseholdIncomeCategory.xml

• Class: MAHouseholdIncomeCategory
• totDeemedNetEarnedIncomeTimeline: New

/EJBServer/components/ISMedicalAssistance/CREOLE_
Rule_Sets/MedicalAssistance/QMB/ProductDisplay/
QMBHouseholdIncomeCategory.xml

• Class: QMBHouseholdIncomeCategory
• totalHouseholdMonthlyGrossEarnedIncomeTimeline: Updated
• maHouseholdEarnedIncomeSubscreen:Updated

/EJBServer/components/ISMedicalAssistance/CREOLE_
Rule_Sets/MedicalAssistance/ABD/ProductDisplay/
Income/Household/ABDHouseholdIncomeCategory.xml

• Class: ABDHouseholdIncomeCategory
• maHouseholdEarnedIncomeSubscreen:Updated

/EJBServer/components/ISMedicalAssistance/CREOLE_
Rule_Sets/MedicalAssistance/QDWI/ProductDisplay/
QDWIHouseholdIncomeCategory.xml

• Class: QDWIHouseholdIncomeCategory
• maHouseholdEarnedIncomeSubscreen:Updated

/EJBServer/components/ISMedicalAssistance/CREOLE_
Rule_Sets/MedicalAssistance/SLMB/ProductDisplay/
SLMBHouseholdIncomeCategory.xml

• Class: SLMBHouseholdIncomeCategory
• maHouseholdEarnedIncomeSubscreen:Updated

/EJBServer/components/ISMedicalAssistance/CREOLE_
Rule_Sets/MedicalAssistance/QI/ProductDisplay/
QIHouseholdIncomeCategory.xml

• Class: QIHouseholdIncomeCategory
• maHouseholdEarnedIncomeSubscreen:Updated

WorkItem:179985 - When applying for a Qualified Medicare Beneficiaries program (QMB), the Earned Income and Gross Income values on the Integrated Case Income tab Member Income screen are incorrect

Previously, when case participants were applying for a Qualified Medicare Beneficiaries program with a Self Employment evidence record, the Earned Income and Gross Income values on the Integrated Case Income tab Member Income screen were being incorrectly calculated.

Now, this has now been corrected. The Earned Income and Gross Income give the expected value on the Member Income screen.****
Technical details:

/EJBServer/components/ISMedicalAssistance/
CREOLE_Rule_Sets/MedicalAssistanceRuleSet.xml

• Class: MAIncomeCPRCalculator
• totalGrossEarnedIncomeTimeline: Updated

WorkItem:181498 - Error occurs when attempting to apply evidence changes after removing and re-adding a household member in a subsequent month

Previously, if a household member receiving assistance in an Aged, Blind and Disabled medical assistance case was removed from the household and re-added in a subsequent calendar month, an unhandled server exception occurred when applying evidence changes in the Integrated Case.

This has now been resolved and when a household member is removed and re-added in a subsequent calendar month, evidence changes will now be correctly applied.

Changes have been made to the ISProduct\CREOLE_Rule_Sets\ISProductRuleSet.xml file. The householdMemberEndDate attribute was updated and the householdMemberRecordsEnded attribute was added in the CalculationVariables class.

WorkItem:182652 - Countable Income sub-screen not displayed when viewing a determination within an Aged Blind and Disabled Product Delivery case

Previously, when viewing decision details for an eligibility determination within an Aged Blind and Disabled Product Delivery Case, the Countable Income sub-screen was not displayed.

This has been fixed. Now, when accessing a determination from an Aged Blind Disabled Product Delivery Case, the Countable Income sub-screen is displayed. The ABDPDDecision_memberCountableIncomeDetails.uim located in ISMedicalAssistance\data\initial\clob\ProductDisplay\PD\ABD was updated so that the businessObjectID property name attribute has a value of "TEXT" rather than "PAGE".

PO06762, WorkItem:185296 - Unhandled server exception occurs when checking eligibility after a household member is removed and re-added within the same month

Previously, if a member of the household was end dated and re-added in the same calendar month, an unhandled server exception was thrown when checking eligibility.

This was due to program alignment functionality which is configured in the rules to consider a member in the household until the last day of the month in which the end date is recorded.

Now, a validation has been added to prevent the user from removing and re-adding a household member in the same month. This validation is thrown on Apply Changes and Check Eligibility and displays the following message:

Household member cannot be removed and re-added in the same month as a removed member is still considered in the household until the last day of the month. If you want to re-add the member remove the end date on the member record.

The validation is implemented as a configurable validation that is enabled by default and can be disabled if program alignment functionality is not being used, by searching for and disabling the validation reference of genprogramrecommendationcheckeligibility.err_
program_recommendation_xrv_household_member_
overlapping_end_of_month|c| within the system administration application.

WorkItem:188250 - Food Assistance Rates for 2017

The FS Federal Poverty Limit rates have been updated for the following, effective Oct 1, 2016:

• HouseholdSize 1 $990
• HouseholdSize 2 $1335
• HouseholdSize 3 $1680
• HouseholdSize 4 $2025
• HouseholdSize 5 $2370
• HouseholdSize 6 $2715
• HouseholdSize 7 $3061
• HouseholdSize 8 $3408
• Over 8 add for each person $347

The CER FA Excess Shelter Deduction have been updated for the following, effective Oct 1, 2015:

• Maximum Excess Shelter Deduction $504

The CER FA Excess Shelter Deduction have been updated for the following, effective Oct 1, 2016:

• Maximum Excess Shelter Deduction $517

The CER FA Standard Deduction have been updated for the following, effective Oct 1, 2015:

• HouseholdSize 1 $155
• HouseholdSize 2 $155
• HouseholdSize 3 $155
• HouseholdSize 4 $168
• HouseholdSize 5 $197
• HouseholdSize 6 plus $226

CER FA Standard Deduction have been updated for the following, effective Oct 1, 2016:

• HouseholdSize 1 $157
• HouseholdSize 2 $157
• HouseholdSize 3 $157
• HouseholdSize 4 $168
• HouseholdSize 5 $197
• HouseholdSize 6 plus $226

WorkItem:188251 - Medicaid Rates for 2016 - 2017

The LTC rates have been updated for the following, effective July 1, 2016:

• CER LTC Minimum Income Allocation - $2002.50
• CER LTC Maximum Income Allocation - $2980.50
• CER LTC Shelter Limit - $600.75

The CER SSI Federal Payment Standard have been updated for the following, effective Jan 1, 2017:

• Individual - $735
• Couple - $1103

MEDICAL ASSISTANCE

WorkItem:104238 - Newborn details evidence is not created, if during pregnancy, the mother was not enrolled on Medicaid

Previously, newborn details evidence was not created, if during pregnancy, the mother was not enrolled on Medicaid.

Now, this has been fixed and the newborn details evidence is now created.

PO06009, WorkItem:148900 - Add link is not present in intake application script when pregnancy information is removed

Previously, the add pregnancy link on both summary pages of the case worker script caused an error when selected.

This has now been resolved and a pregnancy record can be added.

PO06600, WorkItem:173856 - Joint tax filing page is still appearing after removing spouse from Household Summary page

Previously, the status for 'Files Jointly with Spouse' was not updated when a spouse was removed from the Household Summary Page. This was the same for the Summary Pages in the Citizen Portal and IEG Script.

Now, this has been corrected. The 'Files Jointly with Spouse' label was missing on the Household Summary page. This has been re-added to the page. So when deleting a spouse from the household, the label is now reset.

Child Welfare

PO02016, WorkItem:116431 - Narrative is not shown for 'Informational and Referral' intakes with status 'Closed'

Previously, when a user created an informational and referral intake with content in its narrative section, and subsequently closed it, the narrative entered previously was getting lost when the closed intake was viewed again.

This has now been resolved and the narrative content entered prior to closing the intake, gets displayed as expected.

PO03732, WorkItem:116520 - Intake Case incorrectly displays in the Citizen Context Viewer when the participant was added and subsequently deleted.

Previously, when an Intake worker added a participant and subsequently deleted them from an Intake case, the Intake link was incorrectly found to be enabled for the deleted participant allowing the user to view the intake summary home page. Additionally, despite the participant being deleted from the Intake case, the Intake record was still being displayed in the participant's Citizen Context Viewer (CCV).

This has now been resolved so that the user interface displays expected actions alone when a participant is deleted from an Intake case.

WorkItem:177312 - Close link is not enabled as expected and closure details are not displayed on the Intake Case Home tab

Previously, following were some of the usability issues identified in the 'Close Intake' functionality -

• 'Close Case' link was enabled on the action menu of the Intake case page even after this case was closed.
• The closure details were not displayed on the Intake home tab after the case was closed.
• The comments entered during submission of the intake case were not appearing on the status history section of Administration tab.

These issues have now been resolved to ensure that the user sees expected user interface actions across the 'Close Intake' functionality.

WorkItem:179807 - Placement records not displayed for case participants on ongoing/investigation case

Previously, placement records for the members who are placed, were not getting listed on an investigation case or an ongoing case.

Now, this issue has been resolved and the placement records get listed on an investigation case or an ongoing case as expected.

Known Issues

Cúram Enterprise Framework

Integrated Case Management

WorkItem:123357 (was previously SPMP-15534) - Evidence shared from Person to case, is accepted but not activated on the case, modifying this evidence prior to activation will not share this modification back to Person

An issue exists at present with evidence that is shared from Person level to case(s). If the evidence shared from Person evidence to a case is not activated on the case, and that shared evidence is modified within that case prior to activation, the updated evidence is not shared back to Person evidence.

For example; if address evidence is configured for sharing from Person to an Integrated Case with auto-activate disabled and auto-accept enabled. On capturing a new address for a client at Person level, the address is shared to the Integrated Case and automatically accepted onto the In-Edit evidence list on that case. If a case worker modified the In-Edit address within the Integrated Case and activates this change, this address update is not shared back to Person evidence.

To work around this issue, customers have two options.

• Case workers should activate incoming evidence that has been accepted on to the case from Person evidence
• Customers can configure the evidence sharing between the Person evidence to other cases with both auto-activate and auto-accept enabled

Application Development Environment

WorkItem:37987 (was previously TEC-18014) - CDA Assessment Decision Matrix application timeout error

When an administrator is configuring a CDA assessment in Outcome Management, the Decision Matrix displays a wizard to assist the user for creating the matrix. The wizard throws a timeout error, which prevents it from being used. The workaround available is to click OK when the application timeout error appears, select the Cancel button on the wizard and then use the Questions, Outcome and Options button to create the matrix.

Cúram Modules

Provider Management

WorkItem:103350 (was previously CPM-2415) - Incorrect underpayment amount created when multiple service invoice line items reassessed due to change in service rate

When there are multiple service invoice line items created and paid for a provider using a fixed amount service rate and payment option of 'pay fixed amount', if the service rate that was used to determine the payment amount is retrospectively modified, e.g. to a higher rate, underpayments are not being generated for all of the affected service invoice line items.

Outcome Management

WorkItem:114547 (was previously CC-1100) - Administration property 'curam.outcomeplanning.referralForAgreementDays' is not working as expected

Outcome Management provides the ability to create agreements where the client(s) can agree in writing to adhere to the activities (services, referrals and actions) that form part of the agreement. A system property exists to filter out referral type activities during the agreement creation process based on a number of days from when the referral was created. This property is currently not being considered when creating an agreement. To work around this issue, the user can view the start date of the referral on the create agreement wizard to determine whether the referral should form part of the agreement.

WorkItem:115188 (was previously CC-930) - Incorrect Activity Responsibility setting when a plan is automatically created by the system.

In certain scenarios, an activity will have an incorrect responsibility setting, in that the responsibility will be set to ‘system’ instead of the appropriate user. The issue occurs for a specific set-up where:

• ‘Enable Automatic Population of Outcome Plans’ system property is set to true; and
• Outcome Plan is created automatically from referral processing; and
• An action which is configured to be automatically added, has been configured so that the responsibility is assigned to a user.

To work around this issue, the responsibility for the actions that are automatically added should be set to 'Any User', so that the planner user can edit the responsibility field when the action is added to the plan and change the responsibility from 'System' to the appropriate user.

WorkItem:148405 - Outcome Plan Activity Workspace does not refresh and display the newly created Action

When a new action is created from outcome plan activity workspace, the created action is not displayed on the workspace as the workspace does not get refreshed automatically. The workaround available is to refresh the workspace manually to see the action.

Identity Intelligence

WorkItem:179932 - UMFData.owner index is too large to support multibyte expansion

The UMFData database table has an index on the owner field. This index is currently too large to support multibyte expansion on DB2 in a z/OS environment and will not get created.

This is only an issue when running against DB2 for z/OS, where multibyte expansion is enabled.

Notices

Before using this information and the product it supports, read the information in "Notices".