Skip To: Main Content | Subnavigation |
 
DHS Systems and IT Updates MnCHOICES

MnCHOICES Support Plan v18.4.1 Release Known Issues

9/18/2018, updated 1/11/19

Search tab

  1. Error message locking text fields
  • Issue: Text fields may become locked and an error message appears on the screen.
  • Workaround: Hit F5 to refresh the page.
  1. Middle initial does not display for person
  • Issue: The middle initial for the person may not display in the search results table.
  • Workaround: The middle initial does display on the Person Information tab.
  1. Two Modified By fields do not display properly
  • Issue: The Modified By and Modified by Delegate/Lead Agency fields may not display properly.
  • Workaround: None.
  1. Columns sort incorrectly
  • Issue: Some Plans, Names and ID columns do not sort properly.
  • Workaround: Use more detailed search criteria to find the person.
  1. Assessments only appear in results if assigned
  • Issue: Assessments will only appear in the search results table if the assessment has been assigned in the assessment application.
  • Workaround: Verify the assessment is assigned to an assessor in the assessment application.
  1. Unable to use enter button to perform search
  • Issue: Users cannot click the enter button to perform a search in the Find Assessment # or Open Plan # text fields. Nothing will happen.
  • Workaround: Users must click the Go! Button next to the Find Assessment # or Open Plan # text field to conduct the search.
  1. PMIs not updating on documents when person’s PMI changes
  • Issue: A person changes PMI numbers. Previous documents created for the person will remain associated with the old, incorrect PMI number, even after re-clearing previously created documents.
  • Workaround: Users must report to the Help Desk. The Help Desk works with the technology team to update the document ID to reflect the current and correct PMI number manually.
  1. Error message when selecting the Create CSP button
  • Issue: Users receive an error message when locating an assessment and selecting the Create CSP button. The error message states, “Eligibility must be determined while online in the MnCHOICES Assessment before the CSP can be created.”
  • Workaround: Users must return to the MnA and run eligibility in online mode. Then, return to the MnSP, go to the Search tab under the My Plans tab and search for the person or the document. Then, select the Create CSP button and the CSP will be created. An update occurs from running eligibility between MnA and MnSP.

My Plans tab

  1. NEW (7/24/2018) – Recently added plan aide not displaying when selected as designated plan aide
  • Issue: When users assign themselves as a plan aide, save the plan, navigate to the My Plans tab and select the view to show “assigned to me as plan aide,” they should see the plan assigned to them. The plan is not assigned to the user in the list.
  • Workaround: User must create the service agreement first and then add a plan aide.

Person Information tab

  1. Non-descriptive error message that does not indicate error section
  • Issue: When users enter and attempt to save information with errors in this tab, a non-descriptive error message may display that does not indicate which section has the error.
  • Workaround: Users must open each window to find the error. Users must correct the error and resave their work.
  1. NEW (7/24/2018) – Effective date field does not display the correct date when pasting a date
  • Issue: When users paste a date with a single digit into the Health Insurance and Payers table, the date does not display correctly. For example, if the user pastes the date 11/1/2018 into the table, the system will automatically change it to 11/11/2018.
  • Workaround: Users must copy and paste dates that have at least two digits in each field, such as 11/01/2018. Or, the user must manually type the date into the field.
  1. NEW (7/26/2018) – Changes in name field do not change on header after save button is clicked
  • Issue: Users make a change to the name field in the plan and the information does not change on the header after the user clicks the save button.
  • Workaround: The user must make the change, click save and then navigate away from the page. The change will show in the header.

Services tab – none to report

Service Agreement screen

  1. Resolved – [Begin strikethrough text]Application does not account for leap day in 2016 agreements

Issue: When entering agreements with 2016 dates, the system does not account for the February leap day. This is not an issue for agreements with a 2017 date.
Workaround: None. [End strikethrough text]

Service Line screen

      1. User might see difference of $0.01 for calculated rates
  • Issue: Final rate difference is still under the threshold but the user might see a difference of $0.01 for rates calculated in 2015, 2016, 2017 and 2018. Years 2016, 2017 and 2018 were updated on Dec. 18, 2017.
  • Workaround: None.
      1. Fields not formatted as currency fields
  • Issue: Average Monthly Cost/Total Service Cost fields are not formatted as currency fields. Example: $1.00 displays as 1. This is scheduled for resolution in release 18.3.
  • Workaround: None.
      1. NPI numbers entered and saved before rates calculate
  • Issue: User can enter an NPI and save it before calculating a rate.
  • Workaround: None.
      1. Authorization Date field shows TBD
  • Issue: Authorization Date field states TBD.
  • Workaround: This field may be left blank in MMIS.

Service Agreement report – none to report

Rate Input report

      1. Resolved in 18.4 – [Begin strikethrough text]Does not display date the report was modified

Issue: The Rate Input report shows the date the report was created but does not show the date modified. This is scheduled for resolution in release 18.4.
Workaround: None. [End strikethrough text]

Rate Inputs – none to report

Goals tab

  1. Provider name may still appear after deleting NPI
  • Issue: A user enters a provider NPI number and then deletes it. The provider name may still appear to the right of the NPI text field. If a user deletes the NPI number for a goal, the provider name will not appear on the screen when he or she clicks Add/Save.
  • Workaround: None.

Needs Summary tab

  1. Duplicate data
  • Issue: Some data is listed twice.
  • Workaround: None.
  1. New bullet added if commas are used in checkboxes in MnA
  • Issue: If the user enters commas in the MnA in the Strengths, Challenges, Support Instructions or Preferences sections, the system will enter a new bulleted item in the Needs Summary in the MnCHOICES Support Plan (MnSP). This only occurs if the user enters a comma in the “other” checkboxes in the MnA.
  • Workaround: Do not enter commas in these sections of the assessment.

Eligibility tab – none to report

Next Steps tab

  1. Text entry fields may appear uneditable
  • Issue: Text entry fields may look like they cannot be edited even when they are editable.
  • Workaround: None.
  1. Inconsistent printing of check boxes
  • Issue: Check boxes inconsistently print in the person’s CSP.
  • Workaround: Review the printed CSP. Users check the appropriate boxes manually on the printed CSP before it is mailed to the person if boxes are not correct.

About Plan tab

  1. Team assignments not saved
  • Issue: When the user navigates away from the Team Assignments section, the team assignments are not saved. The team assignments feature is not supported currently. It will be used in a future version of MnSP.
  • Workaround: None.
  1. Data does not save when changing status of plan and date document mailed
  • Issue: When the user simultaneously changes the status of a plan to complete and enters a date in the Document Mailed field, the data does not save. The system responds as if the date saved, but if the user leaves the About Plan tab and then comes back, the Date Mailed field is empty. This only occurs the first time a date is entered in the Date Mailed field. The user must enter the date and change the status to Complete at the same time before saving to cause the error.
  • Workaround:

Users must get the field back to being editable:

    1. Change the CSSP status to Open
    2. Navigate away from the About Plan tab
    3. Navigate back to the About Plan tab

Then, save the date:

  1. Add the date in About Plan
  2. Save while the CSP/CSSP is in Open status
  3. Change the status to Complete
  4. Print the report
  1. Plan owner phone number error when opening new CSSP
  • Issue: The primary owner becomes the person who creates the new CSSP. The application removes the phone number associated with the primary owner when a new CSSP is created from a CSP or CSSP. All other Assignment section data will copy from the previous document.
  • Workaround: None.
  1. NEW (7/26/2018) - Changes in plan owner field do not change on header after save button is clicked
  • Issue: Users make a change to the plan owner field in the plan and the information does not change on the header after the user clicks the save button.
  • Workaround: The user must make the change, click save and then navigate away from the page. The change will show in the header.

Printing

  1. Preview all shows incorrect title
  • Issue: When the user clicks “Preview all” in the LTSS evaluations, the preview should say “Program Type: DD” but it shows as only “DD.”
  • Workaround: Users should preview each evaluation separately.

Caregiver

  1. User not prompted to save
  • Issue: The application does not prompt the user to save new data when navigating away from the Caregiver tab. This is not a loss in the functionality.
  • Workaround: User should click the save button before navigating away from the tab.
  1. Caregiver table does not default open and appears uneditable
  • Issue The Caregiver table in the Caregiver tab does not default to open. The table looks like users cannot edit it even though users can make edits.
  • Workaround: Users must click on the Add Caregiver button to display the editable table. Users can enter information in this table. Users must click the save button after entering information but before navigating away from the Caregiver tab.

Risks

  1. Changes not made without clicking save button
  • Issue: The user is not prompted to save and the delete will not occur if a user only changes an Identify Remaining Needs value and then navigates away from the page without hitting save first.
  • Workaround: Users may change any other data field on the page, navigate away and the prompt to save will appear. Or, the user may click save before navigating away.

Support instructions – none to report

Evaluations

  1. LTSS evaluation remains open when provider and CSSP evaluation documents are closed and abandoned
  • Issue: The LTSS Evaluation stays open when all person evaluations of providers and CSSPs are complete or abandoned. This happens only when a specific order of steps occurs:
  1. Open an LTSS Evaluation
  2. Close or abandon either the provider or CSSP evaluation
  3. Abandon the other provider or CSSP evaluation
  4. Enter notes in the notes field
  5. Click the save button

The individual evaluations display a status of closed in the table but the main level LTSS evaluation re-opens and displays open status under the Type/Status header.

  • Workaround 1: Follow these instructions:
  1. Close or abandon the first provider or CSSP evaluation
  2. Enter notes in the notes field
  3. Click the save button
  4. Abandon the second provider or CSSP evaluation – do not click save
  5. Navigate away from the About Plan page
  6. Return if you need to leave more notes
  7. Click the save button
  8. The LTSS evaluation remains closed.
  • Workaround 2: Follow these instructions:
  1. Close or abandon the first provider or CSSP evaluation
  2. Abandon the second provider or CSSP evaluation
  3. Navigate away from the About evaluations tab
  4. Navigate back to the About evaluations tab
  5. Enter notes in the notes field
  6. Click the save button
  7. The LTSS evaluation remains closed.

General (applies to more than one tab)

        1. Error message appears when using hypens on Social Security or telephone numbers
  • Issue: An error message appears if a hyphen is used when entering Social Security or telephone numbers.
  • Workaround: Do not use hyphens when entering Social Security or telephone numbers.
      1. Existing demographic information cannot be deleted
  • Issue: A user needs to remove a phone number, address or email. The information cannot be deleted.
  • Workaround: Enter generic data such as 0000000000 to replace the old data.
      1. User is not always offered confirmation when deleting information
  • Issue: The user is not always presented with a confirmation message before the deletion occurs when deleting content. As an example, goals are deleted immediately after you click the delete button.
  • Workaround: None.
      1. Confirmation message appear more than once when making changes
  • Issue: Some confirmation messages will appear more than once when making changes and saving rates, services and agreements.
  • Workaround: None.
      1. “Invalid name and password” message appears when changing middle initial
  • Issue: The error message “Invalid name and password” appears briefly on the screen after updating the person’s middle initial and then saving.
  • Workaround: None.
  1. Commas not showing in dollar amounts
  • Issue: Commas do not display for dollar amounts over $1,000. For example: $1,000 displays as $1000.
  • Workaround: None.
  1. Characters used in MnA notes are not displaying correctly in the MnSP
  • Issue: If the user entered a hyphen in the assessment notes, it displays as an upsidedown question mark in the support plan.
  • Workaround: None.
  1. Header bar not updating changes while in the document
  • Issue: The header bar with the person’s name, ID, status, etc. might not update changes while the user is in the document. For example: Plan status does not update after you change the status and click save on the About Plan tab.
  • Workaround: Close and reopen the document.
  1. Field validation does not happen until screen saved
  • Issue: Some field validation is not immediate and only validates when the content on the current screen is saved. For example: The error message “no letters allowed in this field” will be visible after the save button is clicked.
  • Workaround: None.
  1. Wait message is not always visible
  • Issue: Not all pages display a wait message while the system is performing some functions.
  • Workaround: Only click buttons once and wait. Look for the spinner near the browser address bar to see if a page is loading.
  1. Please wait message appears while page loads
  • Issue: The “Please Wait..” message may appear on the screen very briefly while the page is loading.
  • Workaround: None.
  1. Not all screens prompt user to save
  • Issue: Not all screens prompt the user to click save before navigating away from the page to a new tab. This is scheduled for resolution in release 18.4.
  • Workaround: Click the save button before navigating to a new tab if you changed or added any content and there is a save button on the screen.
  1. Multiple clicks needed to navigate between text fields
  • Issue: The user must click multiple times when using the keyboard to navigate between text fields. The field label is highlighted when the user clicks tab the first time and the text field is highlighted when tab is clicked again.
  • Workaround: Click the tab key twice to move between text fields.
  1. Buttons and header can wrap and items become invisible
  • Issue: The header at the top of each tab is flush with the menu bar and may be hidden using a laptop that causes buttons to wrap. Sometimes the header also wraps and the tab you need is not visible.
  • Workaround: Reduce resolution.
  1. Assessment question change notification
  • Issue: Users may see “!!” before a question in MnSP because of MnCHOICES efficiencies. This indicates the question text in the assessment has been changed.
  • Workaround: None.
  1. NEW (6/26/2018) – Microsoft known issue with multiple browser sessions
  • Issue: Inadvertent data transfer might occur if a user has two of the same browser windows open and is working on a document in each window.
  • Workaround: Users should use one browser window at a time when updating plans. If a user needs to work in two browser windows, he or she must open browsing windows in two different browser applications. For example, a user opens Internet Explorer to work on Plan A and then opens Google Chrome to work on Plan B.
  1. NEW (7/18/2018) – User access expiring to agency/agency combinations
  • Issue: On 2/2/2022, the majority of users who have access to agency/agency combinations in MnSP will lose their access.
  • Workaround: MnCHOICES MNIT team will update code to change the date to expire in the year 2050.
  1. NEW (7/26/2018) - User continuously presses log in button and error message displays
  • Issue: Users press the login button multiple times and an error message displays saying, “Logon conflict detected, please close you browser and try again.”
  • Workaround: Click the login button one time only.
  1. (NEW-1/11/2019) Changing password adding special character error
  • Issue: When a user changes his or her MnSP password and uses a caret (^) in the new password, the application does not record the password change. No error message displays to indicate the change was not made.
  • Workaround: Do not use the caret (^) symbol in a new password. Acceptable special characters include: dollar sign ($), percentage (%), underscore (_), dash (-), asterisk (@), exclamation point (!) or question mark (?).

Report this page