System Fixes

PEAK Updates - Knowledge Base Articles by Month

February 2017

Performance Improvement - PEAK System

While monitoring the error logs internally, the PEAK Development Team found a null pointer exception being thrown. The system was modified to improve system performance, but otherwise, the fix has no direct impact to the user experience in PEAK.

User Action: There is no PEAK user action required for this fix.(02/16/2017)

PEAK Mobile App - Incorrect Head of Household Displayed

There was a discrepancy between the Head of Household (HOH) in PEAK and PEAK mobile. The HOHs being displayed in these two sources were different. The PEAK Mobile App was updated to show the correct Head of Household - the same as what is displayed in PEAK and CBMS.

User Action: There is no PEAK user action required for this fix.(02/16/2017)

American Indian/Alaska Native Page - Checkbox Issue

When completing an Apply for Benefits (AFB) in PEAK, and a user clicked on the No One checkbox on the American Indian / Alaska Native page (to identify if the household consists of any Members of Federally-recognized Tribe), this checkbox value was not always being saved. This value was lost when the user moved to another page. The system was modified to ensure that this value is always saved.

User Action: There is no PEAK user action required for this fix.(02/16/2017)

Mesa County - Update to PEAK Contact Information

The Contact Us page in PEAK had multiple phone numbers listed for MESA County. Mesa County requested it to be updated to just one number: (970) 265-2458.

User Action: There is no PEAK user action required for this fix.(02/16/2017)

Special Characters - Incorrectly Sent from PEAK to CBMS

Self-employment records sent from PEAK to CBMS contained certain special characters that were not allowed in CBMS. This was causing several issues when updating and/or adding Employment History data, including an error: 237:Error in Function setRequestData-null. A check was added on PEAK pages to restrict entry of these special characters, preventing them from being inserted into CBMS.

User Action: There is no PEAK user action required for this fix.(02/16/2017)

Account Creation Page - Text Updates

Program Areas provided updates to text found on the Account Creation page in PEAK. This text was updated to ensure that it is relevant and correct.

User Action: There is no PEAK user action required for this fix.(02/16/2017)

January 2017

Contact Info Details Page - PO Box Removed from the Field Names for Street #, Street Name, and Apt #

On the Contact Info Details page for new applications (Apply for Benefits), the following error message was shown to the user when an invalid email address was entered: Only the special characters of forward slash (/) and dash(-) can be entered for Mailing Address PO Box# or Street Number.The text 'PO Box#' was not relevant to this page and needed to be removed. The error message was updated as follows:Only the special characters of forward slash (/) and dash (-) can be entered for Mailing Address or Street Number.

User Action: There is no PEAK user action required for this fix. (01/12/2017)

Household Income Text Font - Different for Connect for Health Colorado and PEAK Users

The font for the Household Income table on the Household Summary (Summary of Your Information) page within PEAK was different than the standard font for users navigating from Connect for Health (C4) to PEAK. The Summary of Your Information page text is now consistent for all users whether they originate from C4 or PEAK.

User Action: There is no PEAK user action required for this fix. (01/12/2017)

Getting Started Page - PO Box Removed from the Field Names for Street #, Street Name, and Apt # On the Getting Started page for new applications (Apply for Benefits), the following error message was shown to the user when an invalid email address was entered: Only the special characters of forward slash (/) and dash(-) can be entered for Mailing Address PO Box# or Street Number.The text 'PO Box#' was not relevant to this page and needed to be removed. The error message was updated as follows:Only the special characters of forward slash (/) and dash (-) can be entered for Mailing Address or Street Number.

User Action: There is no PEAK user action required for this fix. (01/12/2017)

About Your Income Help Page - Capitalization Corrected

The text on the About Your Income Page help page read as follows: 'peak' instead of 'PEAK'. The page label was updated to reflect the capitalization of PEAK.

User Action: There is no PEAK user action required for this fix. (01/12/2017)

My Benefits Help Page - Content Updates
The My Benefits help page contained outdated text, which is no longer relevant. The text was updated with the correct data to help assist users.

User Action: There is no PEAK user action required for this fix. (01/12/2017)

Other Bills Page - Text Updated

Confusing/misleading text was present on the Other Bills page in PEAK. Previously, the text on this page read: Does anyone in your home have any Child or Adult Care Bills, Child Support Obligations, or Medical Costs? This label implied that users should be able to enter a Child Support Obligation amount on this page. However, based on the design, Child Support Obligation amounts were not entered on this page. The label will now read: Does anyone in your home have any Child or Adult Care Bills, or Medical Costs? to prevent any future confusion.

User Action: There is no PEAK user action required for this fix. (01/12/2017)

DOC PEAK Users - Not Routed To Correct Page If Client Was Already Active for MA

When a Department of Corrections (DOC) PEAK user attempted to create an application for a citizen with an existing case, the DOC user should have been directed to the Report My Changes page (ABRMC). Instead, PEAK was allowing the DOC user to proceed with completing the application. PEAK was modified to ensure that DOC users are directed to the RMC page when processing information for a citizen who already has an active Medical Assistance (MA) case.

User Action: There is no PEAK user action required for this fix. (01/12/2017)

Duplicate Client ID - Incorrectly Created by Real-Time Eligibility (RTE)

Per requirements, an individual, who has an active MA case already present in CBMS, should not be allowed to create another MA application (Apply for Benefits). Individuals should be directed to report changes to an existing case, rather than be allowed to submit a new application. PEAK was erroneously allowing individuals to create and submit a new application on an existing case. This led to creation of duplicate clients in some instances. The system was corrected to not allow active MA clients to create a new AFB application.

User Action: There is no PEAK user action required for this fix. (01/12/2017)

Accessing PEAK from C4 - Users Were Able To Submit a Change Report Form Containing No Changes

Users accessing PEAK directly from Connect for Health Colorado (C4) were incorrectly able to generate a Change Report Form (CRF) without indicating that there were any changes. As a result, blank CRFs were being sent to PEAK. The issue was corrected by requiring users to select a reason for initiating a Change to ensure no blank CRFs are created.

User Action: There is no PEAK user action required for this fix. (01/12/2017)

December 2016

PEAKHealth App - App Users Unable To Modify Existing Recurring Payments

When recurring payments are set-up in PEAKHealth, they are assigned a unique value known as a token and a separate value known as a Request ID. In order for the recurring payment to be modified, the original token must be sent to CBMS. PEAKHealth was erroneously only sending the Request ID and not the original token, preventing App Users from being able to modify the payment a second time. This issue was fixed by modifying PEAKHealth to submit the original token each time a payment is modified.

User Action: There is no PEAK user action required for this fix. (12/18/2016)

PEAKHealth App - Change Orders Fail To Include Income Coverage Year

Change Orders being submitted from the PEAKHealth App were not considering the coverage year for any Job or Income, so the Income Summary was not sent to CBMS and appeared blank. The PEAKHealth App was modified to now include the coverage year when there is a change to an individual's Job or Income.

User Action: There is no PEAK user action required for this fix. (12/18/2016)

PEAKHealth App -Closed and Pending Programs Were Included in Change Reports

PEAKHealth was incorrectly sending programs that were Closed or Pending in the Change Report when the only programs that should have been included were those in Approved status. Because only Approved programs are shown in the column in the PEAK Inbox, the Change Reports representing Closed and Pending programs were showing up blank. The issue was resolved by ensuring that only programs attached to a case in Approved status are sent to the PEAK Inbox.

User Action: There is no PEAK user action required for this fix. (12/18/2016)

2017 Income Entered in PEAK - Not Being Retained after Save

When PEAK users reported a change to their 2017 annual income in PEAK Report My Changes (RMC), the change was not being recorded. Instead, it was being erased. The issue was fixed by ensuring that changes made by the PEAK user to 2017 annual income are recorded and saved.

User Action: There is no PEAK user action required for this fix. (12/18/2016)

Contact Information Text - Different Formatting for C4HCO Users

The font for the Contact Information table on the Household Summary (ARSUM) page within PEAK was different than the standard font used for PEAK users navigating from C4HCO to PEAK. The font was updated to match the standard font for C4HCO users in PEAK.

User Action: There is no PEAK user action required for this fix. (12/18/2016)

Spanish Application Details Page - Not Entirely in Spanish

The Application Details page within PEAK was not translating all text on the page to Spanish. The page will now show all text in Spanish when the PEAK user selects the Español button.

User Action: There is no PEAK user action required for this fix. (12/18/2016)

Individual's Payment Account - Incorrect Payment Deducted

In certain instances, once the individual paid for the CHP+ Enrollment Fee, the original payment was not being deducted. Because of this, the system erroneously deducted a separate payment within the same 12 month period. PEAK was modified to ensure that first time payments are marked and registered in the system.

User Action: There is no PEAK user action required for this fix. (12/18/2016)

PDFs - New Applications Duplicated Demographic Information

The PDF displayed for Apply for Benefits (AFB) and Report My Changes (RMC) was duplicating the Demographic Information due to an incorrect system configuration within PEAK. This issue was addressed by ensuring the correct configuration is present to show the demographic information once in the AFB and RMC PDFs.

User Action: There is no PEAK user action required for this fix. (12/18/2016)

Upload Document Page - Awkward Spacing

The Types of Proof page was difficult to read due to the spacing. Spaces were included to separate the titles more clearly from the body text of each document requested.

User Action: There is no PEAK user action required for this fix. (12/18/2016)

PEAKPro - MA Applications Statistics Missing from Report

The AFB Report Summary report was incorrectly configured to exclude MA applications, resulting in the Applications Submitted for MA column displaying '0' for the month of September. The report was reconfigured to include MA applications.

User Action: There is no PEAK user action required for this fix. (12/18/2016)

HCPF - CRM Modifications
The Submit a Question test page in the HCPF CRM, a separate website, needed to have the 'SSN' text updated. Additionally, the Question Type had outdated menu options. Modifications were made to the Submit a Question page within the HCPF CRM to change the SSN field to Social Security Number and actualize the Question Type fields.

User Action: There is no PEAK user action required for this fix. (12/18/2016)

RMC Individual Details Page - Text Revisions

Inconsistent and superfluous text was present on the Individual Details page in the Report My Changes (RMC) module that needed to be removed. This text consisted of the labels Here is a summary of what you have told us. If you would like to change your answers or finish a section, click on Edit. If you would like to remove something, click X and This table displays a list of people in your home who ~, which were only present on a few selections. The above text was removed for all selections on the Individual Details page.

User Action: There is no PEAK user action required for this fix. (12/18/2016)

Special Character Message - Stated Invalid Characters Were Valid

If a PEAK user entered an invalid special character such as a period ('.') or a hashtag ('#') in the Street Name, Street Number, or Apt Number fields, an error message appeared that stated these characters were valid. As such, there was confusion as to what special characters were allowed. The error message was updated to clearly state that, other than the standard alpha-numeric characters, only the forward slash and the dash characters are accepted.

User Action: There is no PEAK user action required for this fix. (12/18/2016)

Non-Mobile PEAK Site - Links not Active When Accessed from iPhone

When PEAK users accessed the non-mobile PEAK website on their iPhone, the Get Started and Learn More links were not working due to a compatibility issue. These links are now compatible with the iPhone.

User Action: There is no PEAK user action required for this fix. (12/18/2016)

DOC PEAKPro - Search Criteria not Limited by Entered DOC Number

When Department of Corrections (DOC) PEAKPro users entered a DOC Number in the Search field, the search was not displaying the correct results. The system was modified to ensure the results take into account the DOC Number.

User Action: There is no PEAK user action required for this fix. (12/18/2016)

PEAK Users - Able To Bypass RMC Safeguards To Submit AFBs

If an individual who is known to CBMS on an MA-Only case attempts to submit an MA-only application, the Routing to RMC page will display as a way to prevent duplicate Client IDs, State IDs, and cases being made. The Development Team found an issue where individuals were able to bypass this page by clicking Back, and then moving forward with the new application by clicking Next. To ensure that individuals are correctly going to Report My Changes (RMC) to make changes to an active MA case, the Routing to RMC page was modified so that it cannot be bypassed in this specific scenario.

User Action: There is no PEAK user action required for this fix. (12/18/2016)

November 2016

SSN Question - Asterisk Removed

On new applications for benefits with MA, clients were being required to enter a value for the Does ~ have a Social Security Number? field, even if he or she was not requesting MA on an individual level. The Does ~ have a Social Security Number? field is now optional for individuals who are not requesting MA, and the red asterisk was removed from the field.

User Action: There is no PEAK user action required for this fix. (11/17/2016)

2015 Client Correspondence - Internal Exception Occurred When Viewed in PEAK

PEAK users attempting to view correspondences older than 2015 through their PEAK accounts were inadvertently causing a CBMS issue when they clicked on the same correspondence more than once. The issue had no impact to the client in PEAK. The error was addressed to optimize the performance of CBMS.

User Action: There is no PEAK user action required for this fix. (11/17/2016)

New IP Address - Provided by Cybersource

Cybersource, the system used to make electronic payments in PEAK, changed the IP address on one of its new servers. As a result, payment information was not mapping to PEAK correctly. The new Cybersource server IP address was added to PEAK so that payment information can be up-to-date.

User Action: There is no PEAK user action required for this fix. (11/17/2016)

Felony Convictions Questions - Appeared on Non-CDHS PDFs

Questions pertaining to felony convictions for CDHS programs were appearing automatically on all application PDFs, even if there was not a CDHS program present. To avoid potential confusion, the felony conviction questions will only appear on application PDFs that have CDHS programs present.

User Action: There is no PEAK user action required for this fix. (11/17/2016)

County of Residence - Additional Clarification Added

When certain PEAK users were initiating a Change Order in PEAK to indicate that they were moving out-of-state and had a change in address, they were confused with the In what county do you live? label on the Contact Information Details page. To avoid further confusion, the label was updated to read In what county do you live in Colorado? in both English and Spanish to ensure users know that the county only applies to Colorado.

User Action: There is no PEAK user action required for this fix. (11/17/2016)

Individual Changes Page - Displayed Individuals Who Were Not Reporting a Change

When a change to the American Indian/Alaska Native Details was made to a particular individual on a case that had multiple household members, the Individual Changes page incorrectly showed that all household members had changes. This issue was resolved by ensuring that only the individual whose details were updated are displayed on the Individual Changes page.

User Action: There is no PEAK user action required for this fix. (11/17/2016)

Time Limit for Reviewing Applications Page - Update To Ensure Spanish Translation Is Displayed

The Time Limit for Reviewing Applications page was automatically loading in English even if the application was in Spanish. The page is now translating correctly to Spanish if the prior page is in Spanish.

User Action: There is no PEAK user action required for this fix. (11/17/2016)

Application Review Page - Text Updated To Reflect 2017 Tax Year

The paragraph on the Application Review page had the wrong tax year of 2015 listed. The correct tax year, 2017, is now listed.

User Action: There is no PEAK user action required for this fix. (11/17/2016)

Responses To Questions Submitted - Could Not Be Viewed

Within PEAK, when clients submitted questions to the HCPF Call Center, responses to the questions once the ticket was closed were not able to be viewed by the client. This issue was corrected by ensuring that worker responses are able to be viewed even if the question has closed.

User Action: There is no PEAK user action required for this fix. (11/17/2016)

Application Review Page - PEAK User Not Logged Out as Expected after Clicking Exit Button

When logged-in PEAK users were clicking the Exit button on the Application Review page in either Apply For Benefits (AFB) or Report My Changes (RMC) after application submission, the system did not correctly log the PEAK user out. When the PEAK user attempted to enter the account, the user received an error message stating that he or she already logged in. This issue was fixed by ensuring that PEAK users are correctly logged out regardless of the page on which they choose to log out.

User Action: There is no PEAK user action required for this fix. (11/17/2016)

Annual Income Estimate for Tax Credits and Cost Sharing Reductions Page - Fields and Error Message Updated

The radio buttons on the Annual Income Estimate for Tax Credits and Cost Sharing Reductions page were not required to continue with an MA application in Apply for Benefits (AFB) or Report My Changes (RMC). According to the current requirements, this was incorrect functionality. An error message will now display if the fields are left blank: Please select one of the options below before proceeding with the application.

User Action: There is no PEAK user action required for this fix. (11/17/2016)

Application for CCAP - Teen Parent Not Displayed

On CCCAP only applications, individual parents under 18 years old were not able to add details for the Child Support option on the Child Care and Support page. The page was modified to allow for individuals under 18 years of age to add Child Support information.

User Action: There is no PEAK user action required for this fix. (11/17/2016)

Medical Card - Pop-Up Did Not Appear When Requested in PEAK

On the Request Health First Colorado Medical Card page, the confirmation message was not displaying the first time that a user attempted to have his or her medical card mailed. The confirmation message will now appear.

User Action: There is no PEAK user action required for this fix.

PEAK User Unable To Move Forward after Marking Individual on Case Disabled

PEAK users reporting a change in their home due to a disability, blindness, or inability to work because of illness or injury were unable to proceed with their applications due to an incorrect error message displaying on the Changes in Your Home page: Please choose a value for 'Check the box (or boxes) to tell us who became disabled, blind, or unable to work because of illness or injury'. The error message will no longer appear.

User Action: There is no PEAK user action required for this fix. (11/17/2016)

Size of NFP Logo Displayed Incorrectly - NFP PDF

The size of the Nurse-Family Partnership (NFP) logo was displaying incorrectly and affecting the readability of the NFP PDF. The NFP logo was resized to enhance readability of the NFP PDF.

User Action: There is no PEAK user action required for this fix. (11/17/2016)

PEAK Users Able To Upload Document Type That Is Not Acceptable Type in CBMS

When users submitted an application in either Apply For Benefits or Report My Changes and further verification documents were needed, users had the option to upload certain Document Types on the Types of Proof page. Users were incorrectly allowed to upload a Date of Birth document, but this was not an acceptable Document Type in CBMS. As such, the logging mechanism that tracks errors would frequently report errors that certain documents were not accepted. This issue was fixed by ensuring that the Date of Birth Document Type is no longer displayed as an option on the Upload Document menu on the Types of Proof page.

User Action: There is no PEAK user action required for this fix. (11/17/2016)

October 2016

Page Not Popping Out/Label Incorrectly Bolded on Certain PEAK Pages

When the PEAK user clicked on the Verifications Needed button on the Types of Proof page, the results should have been displayed in a new window. This did not happen due to a missing component for the webpage. The system was updated, so the page opens in a new tab. In addition, the header for the Spanish translation is no longer in bold font.

User Action: There is no PEAK user action required for this fix.(10/16/2016)

System Logs - PEAK Updated To Allow for Better Monitoring

An internal issue was identified with the current logging capabilities of the system. This had no client impact. The system was updated to allow for better tracking of defects and enhanced monitoring capabilities.

User Action: There is no PEAK user action required for this fix. (10/16/2016)

Employer Address - PEAK User Unable To Enter

If a user linked an existing case to their PEAK account that contained a special character such as a '.' in the Street Name field and then they attempted to end this record in Report My Changes (RMC), an error message displayed to the user. This prevented the user from ending the record. The system was modified to allow for addresses that were created in CBMS with a special character in the Street Name field to be ended without displaying an error message.

User Action: There is no PEAK user action required for this fix. (10/16/2016)

Montezuma County -- Contact Information Updated

The contact number was out-of-date for Montezuma County. The contact number was updated.

User Action: There is no PEAK user action required for this fix. (10/16/2016)

Non-Citizenship Fields Displayed Twice, Fields Filled Out That Should Have Been Blank

The Does this person have eligible immigration status and Lived in the US since 1996? fields were automatically displaying on the submitted application PDF with the response as No, even if these fields were not selected. This was corrected by ensuring that these fields will display as blank unless modified.

User Action: There is no PEAK user action required for this fix. (10/16/2016)

Warning Message Pop-Up - Displayed Despite Fields Already Entered

On the Contact Information and Correspondence Notification page in Apply for Benefits (AFB), an error message appeared for users to enter a contact number even if a number was present in the Mobile or Work phone fields. The pop-up condition was updated to display the important message pop-up: Providing a phone number will allow us to contact you to assist you regarding your application. when Home Phone, Message/Work Phone, or Cell Phone fields are blank.

User Action: There is no PEAK user action required for this fix. (10/16/2016)

Report Changes Button - Multiple Clicks Caused Internal Exception in PEAK

When PEAK users clicked multiple times on the Report Changes button on the Account Overview page in PEAK, more than one Change Request was being initiated. This caused a mismatch between the system and PEAK, and it thus displayed an error message. Multiple clicks on the Report Changes button were disabled to ensure multiple records are not created.

User Action: There is no PEAK user action required for this fix. (10/16/2016)

SafeCare Banner - Displayed Even after Changing Program

When users were informed that their county did not offer SafeCare on the Getting Started page in Apply for Benefits (AFB) and they then navigated back to change to a different program, the same message appeared indicating that they were in-eligible for SafeCare even if no SafeCare was being requested. The pop-up message has since been fixed to only appear if SafeCare is on the case.

User Action: There is no PEAK user action required for this fix. (10/16/2016)

Errors - Updates To Correct How Errors Are Logged

There was an issue with the system logs that was causing error logs to be present for non-existent errors. This had no client impact. The logging mechanism has been corrected to better track errors.

User Action: There is no PEAK user action required for this fix. (10/16/2016)

Non-Citizen Information - Not Being Wiped after Client Stated That He or She Was a Citizen

When users selected Yes, after selecting No, for the Citizenship Status radio button on the Citizenship page in Apply for Benefits (AFB), the information was not being wiped out. The system was modified to ensure that information is cleared when a user changes their selections.

User Action: There is no PEAK user action required for this fix. (10/16/2016)

Login - Client Was Unable To Log In to PEAK

In certain instances, if a PEAK user had multiple unique PEAK IDs (not seen to the PEAK user), an additional ID was being created each time a PEAK user attempted to log in to PEAK. To correct this issue, if a PEAK user has multiple unique IDs existing on his or her account, no new additional IDs will be created. For all existing users with multiple IDs, a separate data fix has been conducted to remove the extraneous IDs.

User Action: There is no PEAK user action required for this fix. (10/16/2016)

Self-Employment Page - Required Fields Not Displaying Red Asterisks

The required fields, What is the name of ~'s self-employment business?, How many owners are there (including ~)?, and What percent of the business does ~ own? on the Report My Changes (RMC) More About ~'s Self-Employment page were missing red asterisks. The red asterisks were added to these fields to ensure that users do not leave them blank.

User Action: There is no PEAK user action required for this fix. (10/16/2016)

In-Kind Income - Displaying Error Message for Field Marked as Not-Mandatory

The When was the last in-kind income received? field was missing the red asterisk. Therefore, whenever the user left the field blank, an error message populated indicating that the field must be completed. A red asterisk was added to the When was the last in-kind income received? field to indicate that it is mandatory.

User Action: There is no PEAK user action required for this fix. (10/16/2016)

Self-Employment Detail Page - Fields Missing Mandatory Mark

There were missing red asterisks for the required fields What type of self-employment does ~ have? and What percent of the business does ~ own? on Apply for Benefits (AFB) More About ~'s Self Employment. Red asterisks were added to these fields so that users know to not leave these fields blank.

User Action: There is no PEAK user action required for this fix. (10/16/2016)

SafeCare Colorado - Receiving Applications That Did Not Meet Minimum Criteria

SafeCare was not being removed from certain applications that contained CDHS programs due to eligibility criteria that were not applied correctly to applications submitted early. This issue has been resolved by ensuring that SafeCare will be removed from the application if the SafeCare eligibility criteria are not satisfied.

User Action: There is no PEAK user action required for this fix. (10/16/2016)

Questions About Your Job Page - Job Search Date Field not Converted to Spanish Date

Data entered in the Job Search Date field on the Spanish version of the Questions About Your Job page was not displayed correctly in the Spanish date convention. The system was modified to ensure that the date is displayed per the correct date convention.

User Action: There is no PEAK user action required for this fix. (10/16/2016)

Connect for Health Colorado Payload - FIPS Code (County Code) Not Correctly Mapping

Certain county addresses were not populating correctly when customers were coming from Connect for Health to PEAK. The system was corrected to ensure that the correct county is populated for all addresses when coming to PEAK from Connect for Health.

User Action: There is no PEAK user action required for this fix. (10/16/2016)

September 2016

Services by County Information - Link Updated

The link on the website was incorrect. The links were updated to direct to the correct location.

User Action: There is no PEAK user action required for this fix. (09/18/2016)

System Performance - Improvements

Periodically, there is 'junk data' that builds up in Salesforce that presents performance issues in the back-end. As such, this 'junk data', which is composed of such items as incomplete guest applications, needs to be eliminated to optimize performance. This had no client-facing impact. Screen driver logs were added in the query, and the screen driver was deleted while pending application deletes.

User Action: There is no PEAK user action required for this fix. (09/18/2016)

Moving Out Of State Page - Required Fields That Have Since Been Removed

The page was incorrectly requiring fields to be present that were removed. As a result, error messages for these absent fields were being displayed, and the user was not able to continue. The fields that were missing have since been added.

User Action: There is no PEAK user action required for this fix. (09/18/2016)

System Performance -- Improvements

An issue was occurring in the back end of PEAK that affected performance. This had no impact to the client. A check was added to see if Individuals list is empty prior to accessing it.

User Action: There is no PEAK user action required for this fix. (09/18/2016)

Error Message Displayed Regarding a Field That Was Not Displayed

An error message was incorrectly displayed when users attempted to end their in-kind income when reporting a change. The page was updated to remove any reference to non-visible fields on the page.

User Action: There is no PEAK user action required for this fix. (09/18/2016)

Error Message Displayed Regarding a Field That Was Not Displayed

Users were seeing an error message for a field not shown on the page when attempting to end date a TRICARE, Peace Corps, Other Health Insurance record in Report My Changes (RMC). The page was updated to no longer include reference to non-existent fields and to instead only consider the visible fields.

User Action: There is no PEAK user action required for this fix. (09/18/2016)

Error Message Updates

Issues related to error messages on the COBRA, Retiree, Railroad Retirement, Veteran Health Plan page in PEAK Report My Changes (RMC) were discovered. One required field was not generating an error message, and another error message had an extraneous hyperlink. Both of these issues were corrected on the RMC page.

User Action: There is no PEAK user action required for this fix. (09/18/2016)

Application for CDHS Program - Assigned To MA Site Instead of County of Residence

When PEAK sends Change Reports to CBMS, it sends the County Code as the one received from CBMS when the user initiates the Report My Changes process. When the PEAK user attempted to add any CDHS program to his or her case, the Change Report was being routed to the original county, instead of his or her current County of Residence. PEAK logic was modified to send CDHS applications to the current County of Residence.

User Action: There is no PEAK user action required for this fix. (09/18/2016)

Legal Information Page and Legal Summary - Appeared Blank for Food Assistance (FA) RRRs

The Legal Information and Legal information Summary were displaying as blank in RRR mode for a Food Assistance case. A condition was added to not queue Legal Information and Legal information Summary if the client is in RRR mode.

User Action: There is no PEAK user action required for this fix. (09/18/2016)

AFB Incomplete Page Report - Updated To Prevent It from Not Being Generated

Within PEAK, the number of characters allowed for one of the Statistical fields exceeded the maximum allowable size, which caused an error when attempting to compile the report. As such, the report was not displaying in PEAK. The length of the Statistical fields for this report was increased to allow for more characters.

User Action: There is no PEAK user action required for this fix. (09/18/2016)

Medical Costs Page - Error Message Not Displayed If Required Fields Left Blank

When PEAK users were editing Medical Cost records in Report My Changes (RMC) with a blank type, the page was not allowing them to proceed due to the type being required. The code was corrected to make Medical Cost Type optional.

User Action: There is no PEAK user action required for this fix. (09/18/2016)

Grant/Scholarship - PEAK User Might Have Been Unable To Continue in PEAK after Entering

School Type was being required in Edit mode in PEAK Report My Changes (RMC) for Grant and Scholarship records. If the type was blank in CBMS, this was causing the user to not be able to proceed past the page. The code was corrected to make School Type optional.

User Action: There is no PEAK user action required for this fix.

PEAK PDF - Did Not Indicate Whether or Not a Citizen is Homeless

For homeless clients, the PEAK PDF was just showing a blank home address instead of showing an indicator that the client said he or she was homeless. A new Homeless field was added to the Apply for Benefits (AFB) and Report My Changes (RMC) PDFs.

User Action: There is no PEAK user action required for this fix. (09/18/2016)

PEAK RRR Page - New Benefits Section Displayed as Blank

After the Change Selection page design was modified in the June 2016, clients initiating RRRs were seeing a blank New Benefits tab. Clients could not add new programs through RRR. The page was corrected to skip this tab for RRRs.

User Action: There is no PEAK user action required for this fix. (09/18/2016)

Report My Changes - Users Might Have Seen an Error Message When Adding Three or More Individuals

When users attempted to add three or more individuals to an existing case in Report my Changes (RMC), an error message appeared due to a behind the scenes performance issue. The PEAK system was modified to allow for three or more individuals to be added to RMC applications.

User Action: There is no PEAK user action required for this fix. (09/18/2016)

August 2016

PEAKHealth App - Phone Numbers Entered in App Not Correctly Formatted for CBMS

When PEAK users made changes to their phone numbers through the PEAKHealth App, a Change Report was being auto-populated with dashes in the Phone Number field. The presence of the dashes, which are not allowed in the Phone Number field, caused CBMS to recognize the new phone number as invalid. Thus, PEAK users were unable to update their phone numbers from the PEAKHealth App. Changes were made to the PEAKHealth App, which prevent dashes from being included in the Phone Number field. A data fix was applied to all affected cases.

User Action: There is no PEAK user action required for this fix.(08/18/2016)

July 2016

Payments Scheduled by Citizens in PEAK - Cancelled When CBMS Was Down

If CBMS was down during the time a PEAK Batch Job checked CBMS for payment details, the scheduled payment was being marked as cancelled. Following the fix, if CBMS is down, no status change will be made for the payment transaction.

User Action: There is no PEAK user action required for this fix.(07/24/2016)

Number of Characters Allowed - Limited in Certain Fields

Back-end data issues were addressed within the PEAK system. There was no noticeable error for the client. Exceptions were fixed by modifying the maximum length allowed for field on page and object.

User Action: There is no PEAK user action required for this fix. (07/24/2016)

Income Page - Invalid Error Message Displayed

An extraneous error message was displayed on the RMC Job Income Detail page, preventing the PEAK user from proceeding. The code was corrected to ensure the error message no longer appears.

User Action: There is no PEAK user action required for this fix.(07/24/2016)

Email Verification Code - Process Updated

Exact Target was generating duplicate verification codes for verifying email addresses in Apply for Benefits (AFB) and Report My Changes (RMC)/RRR, causing the verification email to not be sent to the client. A fix was implemented to avoid this duplicate verification code issue.

b>User Action: There is no PEAK user action required for this fix.(07/24/2016)

PEAK Payment History Page - Did Not Reflect Overpayments

The Overpayment Amount was not used to do the balance calculation in the Payment History of Medicaid Buy-in. The Balance Owed Amount is calculated from subtracting the Overpaid Amount from Total Amount Due. Considering the Overpaid Amount resolved the issue of displaying the wrong Balance and Owed Amounts.

User Action: There is no PEAK user action required for this fix.(07/24/2016)

Back-End Updates - To Improve System Performance

A back-end data error was occurring related to the Coverage Type field on the Health Insurance pages in PEAK. There was no front-end effect on the client due to this issue. This back-end data error was corrected to ensure maximum system performance.

User Action: There is no PEAK user action required for this fix.(07/24/2016)

Cooling/Heating Record - Created in CBMS, But Not Entered by PEAK User in PEAK

Due to a PEAK issue, duplicate cooling/heating utility expense records were being created in CBMS. The code was corrected to fix this duplication issue.

User Action: There is no PEAK user action required for this fix. (07/24/2016)

New Income Record - Created by PEAK User for an Income Source Already Present in CBMS

When a PEAK user edited a Social Security Disability Income record through Report My Changes (RMC), one data field was not being sent to CBMS, which was causing a duplicate entry. The code was updated to send Received Date to avoid this duplicate entry issue.

User Action: There is no PEAK user action required for this fix. (07/24/2016)

June 2016

Internal Exception - Encountered When Duplicate PEAK Sessions Opened

A backend exception was occurring when a user created a duplicate session (by duplicating the Browser tab) and then navigated to the Communications tab in the duplicate tab. The code was modified to correct this backend data exception. This data exception was not visible to end users in PEAK.

User Action: There is no PEAK user action required for this fix. (06/26/2016)

PEAK Logo - Updated in Cybersource Profile

The PEAK profile in Cybersource had an old logo, causing printed receipts to reflect the wrong logo. The new PEAK logo was added to Cybersouce.

User Action: There is no PEAK user action required for this fix. (06/26/2016)

Medical Card - Unable To Print

The Print Medical Card button on the Report My Changes Results page was not functioning correctly. The code was corrected to ensure that the user is routed to the Medical Card page when the Medical Card button is clicked on the Report My Changes Results page.

User Action: There is no PEAK user action required for this fix. (06/26/2016)

Middle Initial - PEAK Truncated When Received from CBMS

Since PEAK only allows a Middle Initial instead of a full Middle Name, the system was receiving a full middle name from CBMS but only sending back the initial. This was causing issues in CBMS. PEAK was modified to not truncate the Middle Name when receiving data from CBMS.

User Action: There is no PEAK user action required for this fix. (06/26/2016)

RTE - Resource Disposition Not Completed

PEAK was sending the incorrect two letter code value to CBMS for the Disposition Type of Scrapped/Junked when users were end dating vehicle asset records through PEAK Report My Changes. PEAK was updated to send the correct two letter code to CBMS for Scrapped/Junked.

User Action: There is no PEAK user action required for this fix. (06/26/2016)

Determine Life Change Events Page - Information Not Displayed

In PEAK Report My Changes, the systematically determined LCE of 'Birth' was not correctly displaying when users reported a birth along with another change. The code was corrected to display the Birth LCE in this situation.

User Action: There is no PEAK user action required for this fix. (06/26/2016)

Payment Scheduled Date - Sent Incorrectly for 12/30/2015 and 12/31/2015

Several payments that were scheduled for the end of December 2015 were processed in Cybersource with a scheduled date of December 2016 due to a date error. The PEAK Team worked with Cybersource to correct this date issue to ensure it does not happen in December 2016.

User Action: There is no PEAK user action required for this fix. (06/26/2016)

County Code - Not Populating Correctly for Certain Addresses

The county code for certain addresses was not populating correctly when users were coming from Connect for Health to PEAK. The code was corrected to ensure that the correct county is populated for all addresses when coming to PEAK from Connect for Health.

User Action: There is no PEAK user action required for this fix. (06/26/2016)

May 2016

Report My Changes (RMC) - Not Routed to the Inbox Timely

Multiple Report My Changes (RMCs) submitted via PEAK were not routed to the county properly due to CBMS not sending the county code. The system was modified to resend these specific applications and make sure future applications are routed properly regardless of whether the county code was sent by CBMS or not.

User Action: There is no PEAK user action required for this fix. (05/22/2016)

Adams County - Contact Information Updated

Adams County requested an update to the contact information in the Contact Us PDF in the My Account section. PEAK was updated with the new contact information for Adams County.

User Action: There is no PEAK user action required for this fix. (05/22/2016)

Hyperlinks Updated

The URLs for Services by County on the PEAK Home page and the Food Assistance paper application in the Am I Eligible module needed to be updated. PEAK was modified with the updated links.

User Action: There is no PEAK user action required for this fix. (05/22/2016)

AFB Incomplete Page Report - Missing Page Descriptions

A few descriptions for recently added pages were missing on the publicly available Apply for Benefits (AFB) Incomplete Page report. PEAK was modified to add the page descriptions.

User Action: There is no PEAK user action required for this fix. (05/22/2016)

PDF Error - When Too Many Individuals on Case

PEAK users received an error when opening a Change Request Form PDF with more than nine individuals on the case. PEAK was modified to fix the date limit issue that was causing this error.

User Action: Reopen the affected PDF. (05/22/2016)

April 2016

Internal Errors Found When Users Completed Certain Pages in PEAK

Backend data errors were occurring in PEAK when PEAK users were completing the Medical Cost Detail and Health Insurance Detail pages when applying for benefits (AFB). This was a backend system issue only. PEAK users were able to proceed past the page without issues. PEAK was modified to eliminate the backend errors.

User Action: There is no PEAK user action required for this fix. (04/24/2016)

Tax Dependent Placed Incorrectly under Tax Filer Not Claiming Child When Reporting a Divorce

In a situation where a PEAK user entered Report My Changes (RMC) to report a marital status change (divorce) and a subsequent change in tax filing status for the household, PEAK was incorrectly not sending the tax dependent data to CBMS for the child whose dependency changed. The code was modified to ensure that tax dependent information is sent correctly to CBMS in these situations.

User Action: There is no PEAK user action required for this fix. (04/24/2016)

End Dating Health Insurance - Validation Not Enforced

In PEAK Report My Changes (RMC), the 60 day validation for end dates on the Health Insurance Detail page was not working properly. PEAK was corrected to properly enforce the 60 day validation for Health Insurance end date (will not allow > 60 days in the past or > 60 days in the future).

User Action: There is no PEAK user action required for this fix. (04/24/2016)

Submit Application Button - Not Enabled after HLPG Was Selected

In PEAK Apply for Benefits (AFB), the Submit button was not enabled on the left hand navigation bar after a PEAK user chose to add Food Assistance, Colorado Works, or Adult Financial on the Registration Summary page. The code was updated to ensure that the Submit button becomes enabled if a client adds Food Assistance, Colorado Works, or Adult Financial from the Registration Summary page.

User Action: There is no PEAK user action required for this fix. (04/24/2016)

American Indian/Alaska Native Page - Incorrect Hover Text Language Displayed

On the American Indian/Alaska Native page, Spanish hover text was displaying on the English page, and English hover text was displaying on the Spanish page. The code was corrected to ensure that the correct language displays for hover text on this page.

User Action: There is no PEAK user action required for this fix. (04/24/2016)

County Code Not Sent When Address Updated During Completion of RMC or RRR

County Code was not being sent when PEAK users were updating their address information in Report My Changes/RRR modules. In some instances, this caused enrollment coverage information for 2017 to be displayed. The system was modified so that all household/mailing address changes will be sent when PEAK users update their address information (including County Code).

User Action: There is no PEAK user action required for this fix. (04/24/2016)

Grant and Scholarship Information Not Displayed - RMC/RRR PDF

Grant and Scholarship information was not displaying on the Report My Changes/RRR PDF. The code was corrected to ensure that grant and scholarship information displays properly for all Change Reports and RRRs.

User Action: There is no PEAK user action required for this fix. (04/24/2016)

In-Kind Income Record - Citizens Were Able To End Date before Its Begin Date

PEAK was allowing PEAK users to enter an End Date for In-Kind income that was before the Begin Date of the income record in CBMS, causing data issues upon upload. A validation was added to the In-Kind income page to not allow users to enter an End Date that is before the Begin Date.

User Action: There is no PEAK user action required for this fix. (04/24/2016)

Mismatch in Number of Characters Allowed in CBMS vs PEAK

The PEAK system was experiencing a couple data errors due to fields coming from CBMS with too large of a field size. These issues were discovered during regular production monitoring. Fields on the Employer Health Coverage, Authorized Rep, and Contact Information pages in RMC were updated to match CBMS to prevent these errors.

User Action: There is no PEAK user action required for this fix.(04/24/2016)

Other Income Type Drop-Down - Options in PEAK Did Not Match CBMS

Certain other income record types that were present in CBMS were not present in PEAK, causing these records to display a blank type on the Other Income Summary page in Report My Changes (RMC)/RRR. The six missing values were added to PEAK as non-selectable values, meaning they will be mapped back to RMC and displayed on the Summary page but will not be selectable by the PEAK user.

User Action: There is no PEAK user action required for this fix. (04/24/2016)

PO Box - Citizen's Address Sent from PEAK Containing PO Box Twice

PEAK was sending the PO Box label with the number for the PO Box tag. The PO Box label was removed, so it will send only the PO Box number in that tag.

User Action: There is no PEAK user action required for this fix.(04/24/2016)

PO Box - PEAK Sent PO Box Address to CBMS Containing More Than 20 Characters, Causing an Internal Error in CBMS

When users designated an address as a PO Box, PEAK was appending 'PO Box' on to the data sent to CBMS, causing the value to exceed 20 characters in certain situations and causing an error in CBMS. PEAK will no longer be appending 'PO Box' on to the data sent to CBMS. For PO Boxes, only the number will be sent.

User Action: There is no PEAK user action required for this fix. (04/24/2016)

PEAK Annual Reports - Did Not Contain Any Information

The PEAK Change Report Summary, AFB Report Summary, and Medical Card Requests Annual Reports were not generated correctly at the beginning of 2016 due to an error. A data fix that was completed to correctly generate this year’s as well as next year’s reports.

User Action: There is no PEAK user action required for this fix. (04/24/2016)

RMC Queue - Error Received

An incorrect error message was being displayed on the COBRA, Retiree, Railroad Retirement, Veteran's Health Plan Information page in Report My Changes (RMC). The code was corrected to display the correct error message on the page.

User Action: There is no PEAK user action required for this fix. (04/24/2016)

Uploaded Document - Error Received When Attempting To View

PEAK was allowing users to upload documents that had a 0 KB file size. This was causing errors in the CBMS side when workers were attempting to open the document. PEAK will no longer allow users to upload documents that are 0 KB in size. An error message will be thrown if a PEAK user attempts to upload a 0 KB file size.

User Action: There is no PEAK user action required for this fix. (04/24/2016)

March 2016

Mail Center Page - Unnecessary Label

There was an extraneous label appearing on the Mail Center page that referred to an old page layout that has since been changed. The label was removed from the page.

User Action: There is no PEAK user action required for this fix. (03/20/2016)

APTC Expedited Income Path - Not Queued in RMC

The Expedited Income Path in Report My Changes was not being queued for new individuals being added to an APTC-approved Expedited case. Code was corrected so that the Expedited Path will queue in Report My Changes for new individuals added to APTC-approved cases.

User Action: There is no PEAK user action required for this fix. (03/20/2016)

Pueblo County - Contact Information Updated

Pueblo County requested their contact information displayed on the PEAK website be updated. Pueblo County phone number on the PEAK Contact Us page was updated to (719) 583-6160 or (719) 253-7850.

User Action: There is no PEAK user action required for this fix. (03/20/2016)

Self-Employment Page - Value Missing on Drop-Down

Sale of items of Indian cultural significance was missing as a drop-down value for Self-Employment Type in Apply for Benefits. The missing drop-down value was added to the Self-Employment page in Apply for Benefits.

User Action: There is no PEAK user action required for this fix. (03/20/2016)

PEAKHealth App Submissions - Information Not Included on PDF

The PDF generated after a PEAKHealth App user submitted a Change Report via the PEAKHealth App did not contain the name of the Head of Household or the time/date submitted. This occurred when an individual entered a gross income amount containing a space. When a space was entered, the resulting Change Report PDF was blank. The PEAKHealth App was modified, so users will be unable to submit a gross income amount containing a space. When a space is found in the income amount, the system will automatically prompt the individual to correct the information entered.

User Action: There is no PEAKHealth user action required for this fix. (03/20/2016)

Mobile App - Electronic Signature Text Shown When Submitting Changes

Change Report PDFs submitted through the PEAKHealth App incorrectly displayed the electronic signature section I am electronically signing my Change Report.... The PDF template for Mobile App Change Report submissions was updated to not include the electronic signature text, as a signature is not required for PEAKHealth.

User Action: There is no PEAKHealth user action required for this fix. (03/20/2016)

Citizenship Page - Spanish Translation for Document Type Missing in Drop-Down

The Spanish translation was missing from Document Type drop-down on the Citizenship page in PEAK. PEAK was modified to add the Spanish translation for this drop-down.

User Action: There is no PEAK user action required for this fix. (03/20/2016)

PEAKHealth App - Special Characters Entered Caused Batch Job Failure

When reporting a change via the PEAKHealth App, PEAK users were able to enter special characters in certain fields (e.g., - ñ or é). These characters were not recognized by CBMS and would cause various batch jobs to fail if they were present. Following this change, PEAK users will not see any change to current functionality. PEAK users will still be able to enter special characters through PEAKHealth. However, CBMS was modified to automatically convert special characters to a character recognized by CBMS when they are present in changes reported via the PEAKHealth App (i.e., ñ is changed to n).

User Action: There is no PEAKHealth user action required for this fix. (03/20/2016)

County Code - Not Correctly Populated

When a citizen entered PEAK from Connect for Health Colorado (C4), PEAK was using a County Code based on what was already present in CBMS. For example, C4 might have been reporting that a citizen lived in Broomfield County, but because data entry in CBMS might have shown that the client lived in Custer County, PEAK would populate a County Code for Custer County. The County Code should be populated based on what the citizen has most recently reported. PEAK was modified to run the address validation service to populate a new County Code based on the information received from C4 rather than what is presently in CBMS.

User Action: There is no PEAK user action required for this fix. (03/20/2016)

Apply for Benefits (AFB) Report Summary - Displayed No Information Regarding Spanish Applications

The Spanish Applications Submitted column was displaying as blank on the public-facing AFB Report Summary in PEAK. This was due to an error in the report query. The query was corrected to ensure that the Spanish Application column populates correctly.

User Action: There is no PEAK user action required for this fix. (03/20/2016)

Date Conversion - Issue When Changing Language from English to Spanish

Certain dates in PEAK Apply for Benefits (AFB) and Report My Changes (RMC) were not getting converted to the correct format when changing the language from English to Spanish or Spanish to English causing errors. Updates were made in AFB and RMC to ensure that all dates are properly formatted between English and Spanish.

User Action: There is no PEAK user action required for this fix. (03/20/2016)

Living Arrangement Code - Present in PEAK But not in CBMS

The Not In Home drop-down value on Household Member Detail page in PEAK needed to be removed to match with CBMS. The Not in Home drop-down value on the Household Member Detail (ABHMD) page in PEAK Apply for Benefits (AFB) was removed to match with CBMS.

User Action: There is no PEAK user action required for this fix. (03/20/2016)

Page Loaded in English Instead of Spanish - Issue with Back Button on Browser

When translating a PEAKMobile website page to Spanish and then using the mobile browser or phone Back button, the previous page was being translated back to English. This issue was fixed to ensure that all Back button functionality within the PEAKMobile website does not change back to English when Spanish is selected.

User Action: There is no PEAK user action required for this fix. (03/20/2016)

February 2016

Request Medical Card/Manage My Account Button - Not Displaying Correctly

The Request Medical Card section of the PEAK Apply for Benefits Results page was not displaying correctly since the October 2015 build. The page was modified to ensure that the Medical Card section displays properly for Medical Assistance applicants.

User Action: There is no PEAK user action required for this fix.(02/18/2016)

Details Page - Benefit Information in PEAK Did Not Match CBMS

PEAK was incorrectly displaying current and next month eligibility in the My Benefits Section of PEAK My Account. PEAK was updated to correct this issue to ensure that users are able to see their current and next month eligibility.

User Action: There is no PEAK user action required for this fix. (02/18/2016)

Contact Information - Updated for Adams County

Adams county contact information needed to be updated on the PEAK Contact Us page. An updated phone number and email were added for Adams County.

User Action: There is no PEAK user action required for this fix. (02/18/2016)

PEAK Change Report Form -- Displays New Individual Requested All Programs When Only MA Was Requested

The PEAK Change Report PDF was incorrectly showing that all new individuals added to a case were requesting all four programs (Food Assistance, Medical Assistance, Colorado Works, and Adult Financial). The system was modified, so the PDF will correctly display only the programs that someone requests on an individual level.

User Action: There is no PEAK user action required for this fix. (02/18/2016)

Citizenship Page - PEAK User Unable To Save Changes

A PEAK user was stuck on the Citizenship page due to PEAK requiring nine digits for Non-Citizen Number. However, CBMS was sending it to PEAK with eight digits. If the Non-Citizen Number sent by CBMS is less than nine digits, PEAK will add leading zeros for the Non-Citizen Number to prevent this error.

User Action: There is no PEAK user action required for this fix.

Information Updated through Report My Changes (RMC) - Incorrect Error Message Displayed

An incorrect error message was being displayed on the COBRA, Retiree, Railroad Retirement, Veteran's Health Plan information page in Report My Changes (RMC). PEAK was modified to display the correct error message on the page.

User Action: There is no PEAK user action required for this fix. (02/18/2016)

Funeral Preference Information - Displayed under Multiple Headings on PDF

The Report My Changes PDF was incorrectly populating a common label for 'Funeral Preference' under multiple other headings. Each section that had the incorrect label populating was updated with its own label.

User Action: There is no PEAK user action required for this fix. (02/18/2016)

Change Report - Sent to CBMS with Incorrect County Code

When users on Expedited cases were adding Food Assistance through RMC, PEAK was incorrectly sending the Change Report to CBMS with the County Code '99&' even though there was a CDHS program being added. PEAK will now send the County of Residence to CBMS for Change Reports on Expedited cases that add a CDHS program.

User Action: There is no PEAK user action required for this fix. (02/18/2016)

Denied APTC and Approved QHP/CYA - Coverage Begin Date Not Displayed

PEAK users found that the Coverage Begin Date in PEAK was showing as blank when citizens were denied for APTC and approved for Qualified Health Plan/Colorado Young Adults (QHP/CYA). PEAK was modified to show the Benefit Year if the Coverage Begin Date is blank.

User Action: There is no PEAK user action required for this fix. (02/18/2016)

Expedited Income Path - PEAK Users Not Routed as Expected

PEAK users were not being routed to the Expedited Income Path in Report My Changes (RMC) when there were CDHS programs in Denied or Discontinued Status. Changes were made so that PEAK users are able to go through the Expedited Path in RMC if there are CDHS programs in Denied or Discontinued Status.

User Action: There is no PEAK user action required for this fix. (02/18/2016)

Effective Denial Date - PEAK Displays a Different Date Than Reflected on Correspondence

The Effective Date was not displaying correctly in the Denial Reason on Denial Correspondence. The system was modified to show the Effective Denial Date as the first of the month for which the Denial Reason was received. PEAK was modified to show the Effective Denial Date as the first of the month for which the Denial Reason was received.

User Action: There is no PEAK user action required for this fix. (02/18/2016)

January 2016

Case - Not Assigned to a Caseload

When a PEAK application was manually processed, and the Application Date was set to a future date (i.e., application was received after 5:00 p.m.), the case was not assigned to a caseload. The system was modified to validate applications containing a future Application Date, guaranteeing that the case will be assigned to a valid caseload.

User Action: There is no PEAK user action required for this fix. (01/10/2016)

Annualized APTC Income - Updated in PEAK, But Not in CBMS

CBMS was not updating Annualized (APTC) Unearned Income when updated from PEAK/Connect for Health Colorado. The system was modified to ensure CBMS is updated when an individual updates Unearned Income on the PEAK website.

User Action: There is no PEAK user action required for this fix. (01/10/2016)

MA RRR - Set Out at Three Years Incorrectly

When an RRR was submitted from PEAK, it was starting the MA RRR even when it was not due within the next 60 days, causing the RRR Date to push out many years into the future. The system was modified so that when an individual submits an RRR in PEAK, the MA RRR will only be started if the Due Date is within 60 days.

User Action: There is no PEAK user action required for this fix. (01/10/2016)

Case with an Invalid Program - PEAK Users Able To Create a PEAK Account Linked to Case with Invalid Program

CBMS/PEAK allowed individuals to create a PEAK account linked to a case that contained invalid PEAK programs (i.e., Presumptive Eligibility, Family Medicaid, and/or Family Preservation). The system was modified to ensure that, when an individual's case is validated by PEAK, it will only allow the user to link the case to a PEAK account if the following programs are present on the case: FS, CW, AF, CD, and/or MA.

User Action: There is no PEAK user action required for this fix. (01/10/2016)

Medical Costs Page - Users Looping

A field that is present in Report My Changes on the Medical Costs page was not present on the Apply for Benefits (AFB) page. This was causing an error where the page was missing information needed to complete the data transaction, causing the user to be unable to proceed past the page. The system was modified to correctly handle this missing information, being able to complete the transaction as expected, so users can move past the page.

User Action: There is no PEAK user action required for this fix. (01/10/2016)

Account Overview Page - Blank on PEAK Website

There was a discrepancy between what CBMS allows for Verification Case Comment length and what PEAK allows. This caused the Account Overview page to display as blank for certain users. PEAK was updated to match CBMS to prevent this error.

User Action: There is no PEAK user action required for this fix. (01/10/2016)

Application for Medical Assistance - PEAK User Not Given Option

When Connect for Health users entered PEAK Report My Changes to add an individual, the Program Selection heading was being incorrectly displayed on the Household Member Detail page. Since Connect for Health users can only apply for Medical Assistance, this section has now been hidden completely as MA is selected by default. This change does not impact the application (Apply for Benefits/AFB).

User Action: There is no PEAK user action required for this fix. (01/10/2016)

Character Limits in PEAK Fields - Did Not Match CBMS Character Limits

Mismatches between allowable character lengths in PEAK and CBMS were causing data issues in CBMS. PEAK was corrected so that the below character lengths match those in CBMS:

  1. School Enrollment Page - School Credit Pursuing now is limited to 50 characters.
  2. COBRA, Retiree, Railroad Retirement, or Veteran's Health Plan Information - Former Employer Name is now limited to 30 characters.
  3. Long Term Care - DoctorPhone Number is now limited to 10 characters.
  4. Child Support Details - Docket Court Case Number is now limited to 25 characters.

User Action: There is no PEAK user action required for this fix. (01/10/2016)

Login Error

An error in retrieving the Date of Birth for certain cases from CBMS was causing an error in PEAK when users attempted to log in. The following error message displayed: Your session has ended because of an error. PEAK code was modified to prompt the user to reenter his or her case number to relink his or her case if the birthday is received as blank from CBMS.

User Action: There is no PEAK user action required for this fix. (01/10/2016)

Unable To Upload Documents -- File Name Contained Comma (,)

PEAK was allowing users to upload documents containing a comma, which was causing an error in CBMS. PEAK will now not allow users to upload documents with a comma in the file name.

User Action: There is no PEAK user action required for this fix. (01/10/2016)

Medicaid Buy-In Premium Summary - Did not Match CBMS

Users found that they were seeing different amounts in PEAK and CBMS for the Buy-In Premium Amount Due information. The Buy-In Payments Due were displaying differently in PEAK than in CBMS because CBMS displayed cumulative amounts whereas PEAK was doing another round of calculations on the cumulative amounts first, making them significantly higher than the Actual Amount Due. The system was modified, so the service that sends the Premium Amount Due to PEAK will now send the Payment Due by month, instead of sending the cumulative amounts.

User Action: There is no PEAK user action required for this fix. (01/10/2016)

December 2015

Report My Changes (RMC) - Routed to County of Residence Instead of C4HCO

An RMC application that is eligible for APTC only should go to the Connect for Health Colorado PEAK Inbox, but when an RMC application contained an Address Change, the application was being routed to the County of Residence instead. The system was modified so that all APTC-only applications will go to the Connect for Health Colorado PEAK Inbox, even when Address Change is reported as part of an RMC.

User Action: There is no PEAK user action required for this fix. (12/13/2015)

Non-Citizen Number Field - PEAK Allowed Non-Numeric Characters

A mismatch between what PEAK allows for Non-Citizen Numbers and what CBMS allows was causing problems with application uploads in CBMS. PEAK was updated to only allow numbers in the Non-Citizen Number field on the Citizenship page in Apply for Benefits and Report My Changes.

User Action: There is no PEAK user action required for this fix. (12/13/2015)

Applications and Change Reports - Spanish Birthdate Error Prevented Submission

An error was occurring in certain situations where the Head of Household's date of birth had a double digit day in it. This was preventing users from submitting applications and change reports in Spanish. The error has been corrected to ensure that all PEAK users can submit applications and change reports in Spanish mode. The error was corrected to ensure that all PEAK users can submit applications and change reports in Spanish mode.

User Action: There is no PEAK user action required for this fix. (12/13/2015)

Medical Expenses - Allowed End Dates That Were Before Begin Dates

PEAK was allowing users to enter an end date for Medical and Dependent/Elder case expense records that was before the Effective Begin Date. This was causing an application upload issue in CBMS. Changes have been made so that PEAK now saves the Effective Begin Date of Medical and Dependent/Elder care expense records and validates it against the entered end date. If the end date is before the Effective Begin Date, an error message will be displayed. Changes were made so that PEAK now saves the Effective Begin Date of Medical and Dependent/Elder care expense records and validates it against the entered end date. If the end date is before the Effective Begin Date, an error message will be displayed.

User Action: There is no PEAK user action required for this fix. (12/13/2015)

Medical Assistance Details Page - Displayed Incorrect Eligibility Information

A user reported that when completing a Report My Change, the NOA and Initial Results page showed one start month, but the Medical Assistance Details page showed a different start month. In certain situations where a PEAK user was not receiving Medical Assistance benefits for the current month and was receiving benefits for the next month, PEAK was displaying both months as receiving benefits. The page was updated to ensure that when there are different eligibility statuses for the current month versus the next month, both are displayed correctly.

User Action: There is no PEAK user action required for this fix. (12/13/2015)

ELE Applications - Failed in RTE

A data error was causing Express Lane Eligibility applications that were initiated in PEAK to fail Real Time Eligibility (RTE). The system was modified to ensure all Express Lane Eligibility applications receive valid RTE responses.

User Action: There is no PEAK user action required for this fix. (12/13/2015)

Individuals - Unable to Add to a Case

In certain situations, PEAK users on CDHS-only cases were unable to add individuals to their case due to the Newborn and New Individual checkboxes being hidden on the Change Selection page in RMC. Display conditions were updated to ensure that users on CDHS-only cases can add newborns and individuals to their existing cases.

User Action: There is no PEAK user action required for this fix. (12/13/2015)

November 2015

90-Day Condition -- Not Applied to Connect for Health Colorado-Initiated Applications

PEAK was allowing users to re-enter applications that were initiated in the Connect for Health Colorado System that were greater than 90 days old upon login. This was causing them to see error screens. A 90-day purge policy was implemented to not allow users to reenter pending C4-initiated applications that are greater than 90 days old.

User Action: There is no PEAK user action required for this fix. (11/22/2015)

My Account -- Benefit History Error

An error was occurring when PEAK was receiving benefit history data from CBMS that caused the Questions tab to be hidden in the Communications area of PEAK My Account for closed Medical Assistance cases. The error was corrected to ensure that all users with closed MA cases can see the Questions tab in My Account.

User Action: There is no PEAK user action required for this fix. (11/22/2015)

Date of Birth - Spanish Date Format Transferred to CBMS Incorrectly
In certain situations, Dates of Birth entered in the Spanish format on the Head of Household page in PEAK were not populating correctly on the Household Member Detail page corresponding to the same individual. The system was corrected to ensure that all Dates of Birth entered in the Spanish format are displayed correctly on the Household Member Detail page.

User Action: There is no PEAK user action required for this fix. (11/22/2015)

PO Box - Validation Should Have Been Alpha And Numeric

When PEAK users were checking the PO Box checkbox and then typing 'PO Box' in the Address field, this was causing an error in CBMS when the data was uploaded. All pages where address is present in Apply for Benefits and Report My Changes were updated to remove the words 'PO Box' in the data sent to CBMS when the user also selects the PO Box checkbox.

User Action: There is no PEAK user action required for this fix. (11/22/2015)

Medicare - Unable To Edit Existing Records through RRR

Individuals with existing Medicare expenses records in CBMS were unable to edit these records through RRR mode in PEAK due to a page queuing issue. The system was modified to ensure that the Medicare Expenses page is automatically queued in RRR mode so that users can add new records or edit existing records.

User Action: There is no PEAK user action required for this fix. (11/22/2015)

Am I Eligible Calculator Page -Not Translated to Spanish

The Calculator page in Am I Eligible was not translating properly to Spanish. The code was modified to ensure that the entire page translates to Spanish when the user selects Español.

User Action: There is no PEAK user action required for this fix. (11/22/2015)

Payment Record Page - Spanish Help Text Missing

The Help page for the Payment Record page in PEAK My Account was missing Spanish. Spanish help text was added to the page.

User Action: There is no PEAK user action required for this fix. (11/22/2015)

Long Term Service and Assessment Pages - Spanish Version

When the Long Term Service and Support Assessment pages were translated to Spanish, the entire page was not translating properly. The system was modified to ensure that the entire page translates to Spanish when the user chooses to do so.

User Action: There is no PEAK user action required for this fix. (11/22/2015)

Income Page - PEAK Users Received an Error Message When Moving between Pages in PEAK

Citizens reported receiving your session has ended because of an error when attempting to navigate past the Income page while completing an application on the PEAK website. The error was only occurring on applications where the user answered No for having Job Income. PEAK was updated to correct this issue.

User Action: There is no PEAK user action required for this fix. (11/25/2015)