Merative ™ Social Program Management 7.0.2.0 iFix3

Release Notes

Abstract

Merative Social Program Management 7.0.2.0 iFix3 Release Notes

Content

IntroductionSystem Requirements
Download
Installation
Improvements, Resolved Issues and Third Party Updates
Known Issues
Notices

Introduction

Welcome to the Merative Social Program Management 7.0.2.0 iFix3 release.

This is a cumulative release which incorporates the Improvements, Resolved Issues and Third Party Updates contained in all previous 7.0.2.0 iFix releases. Details of these Improvements, Resolved Issues and Third Party Updates are included separately in the release notes for each of the previous iFix releases.

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

Full product documentation can be found in the documentation.

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/spm.

Installation

Prior to running the installer please ensure all files in your 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
Cúram Modules
Solutions

Cúram Enterprise Framework

Dynamic Evidence
Integrated Case Management

PO07650, WorkItem:223610 - Unable to open a word document if the Case Member field has not been selected

Issue Description:

An issue exists where a user is unable to download and open a Microsoft Word communication document that was created on a case. When creating a Microsoft Word communication document, a user has to select a correspondent and can also optionally select another case member in the Case Member field in the Regarding cluster if appropriate. If this optional case member was not selected, the document would still be created, but a user would be unable to download or open it.

User Interface Impact: No.

Steps to Reproduce:

1. Log in as a caseworker.
2. Register a person and create an Integrated Case.
3. On the Integrated Case, click on the Contacts navigation tab and go to the Communication in-page navigation tab.
4. Create a new Microsoft Word communication.
5. During the creation process, select a case correspondent but don't specify a case member.
6. An in-edit version of the document will appear which can be closed. This saves the document.
7. Search for the communication and from the row-level actions menu, select the "Open Microsoft Word" menu item to download the document.

Resolution:

The Microsoft Word communication document creation process has been updated and the document can now be downloaded and opened when the optional case member has not been set.

Dynamic Evidence

WorkItem:225019 - Remove the action from the Dynamic Evidence Editor that provides the ability to correct a dynamic evidence

Issue Description:

The ability to correct a Dynamic Evidence is no longer supported. For more information, refer to tech note Announcing removal of Dynamic Evidence Corrections feature.

Integrated Case Management

Eligibility & Entitlement

ELIGIBILITY & ENTITLEMENT

PO07685, WorkItem:225471 - Data does not propagate correctly under specific custom implementations of the PopulateSuccessionSetRuleObjectHook hook

Issue Description:

An issue existed in the propagation process whereby data was not propagated in a very specific circumstance. This can only arise in the situation where there is a custom implementation of the PopulateSuccessionSetRuleObjectHook hook class, in particular the calculateEffectiveDate API. If this API returns a non-null effective date which is earlier than the succession lifetime of the evidence in question, then that evidence instance was not propagated.

This problem arose on our Insurance Affordability solution where there is a specific implementation of the above hook point dealing with newborns, and this issue was specific to newborn evidence when those newborns were added after the case start date with a date of birth equal to the case participant role start date and the evidence was added at a date later than the newborn's date of birth.

No

Steps to Reproduce:

1. Login as hcrcaseworker.
2. Submit a Insurance Affordability application with 1 adult member.
3. Move the system date one day forward.
4. Register a newborn child with the same date of birth as the date in step 3.
5. Add the newborn child using Guided Wizard into the household.
6. Specify the date reported date in which the member is added to the household as the date in step 3.
7. Set the newborn child, as the 'child' of the first case member.
8. Set the newborn child as being 'tax dependent' the first member.
9. Move the system date 3 months forward.
10. Add a new Income Record of $6000, of type wages, for the newborn.
11. Clear verifications and apply changes.
12. Check the determination split for when the new born was added on to the case, navigate to Income tab.
13. The newborn child's income was not counted in household’s income from the date specified in step 6.

Resolution:

The propagation process has been updated to properly handle the situation where an effective date earlier than the start of a succession set lifetime has been returned from a custom implementation of the PopulateSuccessionSetRuleObjectHook.calculateEffectiveDate API.

Cúram Modules

Intelligent Evidence Gathering

Intelligent Evidence Gathering

PO07691, WorkItem:225732 - IEG conditional question responses are not cleared even though the control question response is changed

Issue Description:

Previously in IEG, conditional clusters controlled by a dropdown within another conditional cluster were not hidden when the controlling cluster was hidden.

**User Interface Impact: **Yes

Steps to Reproduce:

1. Login as hcrcaseworker.
2. Open the HCR Cases and Outcomes tab.
3. Open the toggle in the shortcuts menu labelled Registration.
4. Click Person. The Register Person modal will open. Click Next.
5. Enter details for any person and click Save. The person profile should open.
6. Click on the Options menu and select New Application. The Before We Start modal should open.
7. Tick the checkbox labelled "This person agrees to allow their information to be used for this application.".
8. Click Next. Select No from the dropdown labelled "Do you have a fixed address?".
9. Select No from the dropdown labelled "Are you a state resident?".
10. Select Select Yes from the drop-down labelled "Do you have a fixed address?".

Resolution:

This issue has been resolved by unsetting the value of dropdown fields when the conditional cluster they are displayed within is hidden. This ensures any conditional clusters which were displayed based on the value of these dropdowns will also be hidden.

PO07725, WorkItem:227833 - Nested IEG Conditional Cluster did not reopen when it was closed by a change in the value of its parent

Issue Description:

Previously in IEG, conditional clusters controlled by a dropdown within a previous conditional cluster did not reopen when it is closed by a change in the value of its parent.

**User Interface Impact: **Yes

Steps to Reproduce:

1. Login as hcrcaseworker.
2. Open the HCR Cases and Outcomes tab.
3. Open the toggle in the shortcuts menu labelled Registration.
4. Click Person. The Register Person modal will open. Click Next.
5. Enter details for any person and click Save. The person profile should open.
6. Click on the Options menu and select New Application. The Before We Start modal should open.
7. Tick the checkbox labelled "This person agrees to allow their information to be used for this application.".
8. Click Next. Select No from the dropdown labelled "Do you have a fixed address?".
9. Select No from the dropdown labelled "Are you a state resident?".
10. Select Yes from the drop-down labelled "Do you have a fixed address?".
11. Select No from the dropdown labelled "Do you have a fixed address?".
12. Select No from the dropdown labelled "Are you a state resident?".

Resolution:

This issue has been resolved by unsetting the value of dropdown fields when the conditional cluster they are displayed within is hidden. This ensures any conditional clusters which are opened based on the value of these dropdowns will be opened correctly thereafter.

Solutions

Income Support

Income Support

Medical Assistance

PO07685, WorkItem:224874 - Evidence created for household members added to an Insurance Affordability case on or after their date of birth is not considered when determining household eligibility

Issue Description:

Previously when a new member was added to an existing Insurance Affordability case on or after their date of birth, any evidence subsequently added for the new member such as Income evidence was not recognized and had no impact on the household's eligibility.
User Interface Impact: No

Steps to Reproduce:

1. Register a person and submit an application for Insurance Affordability on 1/1/2018 where the person becomes eligible for Streamlined Medicaid.
2. Register a new person with a date of birth of 2/1/2018 and add the person to the Insurance Affordability case on 2/1/2018.
3. Add income evidence for the new person effective 3/8/2018, and apply the evidence change.
4. The new person's income is not recognized and does not contribute to the calculation of the financial unit when determining the household's continued eligibility for Streamlined Medicaid.

Resolution:

Now when a new member is added to a existing case on or after their date of birth, evidence created for the new household member is correctly considered when determining eligibility.

MEDICAL ASSISTANCE

PO07630, WorkItem:225018 - Medicaid eligibility ends one month early when a change of circumstance occurs on the first day of the month

Issue Description:

Previously, Streamlined Medicaid eligibility was not extended out an extra month as expected in certain circumstances. When multiple changes of circumstances occurred to income within the same month eligibility for Streamlined Medicaid was not determined correctly.

**User Interface Impact: **No

Steps to Reproduce:

1. Go to, System Configuration->Application Data->Property Administration -> curam.healthCare.incomeConfiguration set to 'false'
2. Application date - 2/6/2018
3. Single person with 100/yearly income
4. Eligible for Medicaid from 2/1/2018 - 1/31/2019
5. First change of circumstance - Change income to Insurance affordability level (30,000/yearly) on 5/2/2018
6. Eligible for Medicaid - from 2/1/2018 - 5/31
7. Eligibility for Insurance affordability - from 6/1/2018 - 12/31/2018
8. Second change of circumstance - Change income to Medicaid level (1200/yearly) on 5/31/2018
9. Eligible for Medicaid - from 2/1/2018 - 1/31/2019
10. Insurance affordability - Not Eligible
11. Third change of circumstance - Change income to Insurance affordability level (31,200/yearly) on 6/1/2018
12. Client incorrectly found eligibility for Medicaid only until 5/31/2018, when eligibility should have been extended a month to 6/30/2018.
13. Results before change Medicaid eligibility ends on 5/31/2018
14. Results after this change Medicaid eligibility ends on 6/30/2018

Resolution:

When multiple changes of circumstances occur, Streamlined Medicaid eligibility is now extended out an extra month as expected.

Known Issues

See the Known Issues section in the 7.0.2.0 release notes.

Notices

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