Merative Ideas Portal

Shape the future of Merative!

We invite you to shape the future of Merative, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the Merative team to refine your idea

Help Merative prioritize your ideas and requests

The Merative team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at Merative works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at Merative, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.


Merative External Privacy Statement: https://www.merative.com/privacy

Add a new idea Subscribe
Status Not under consideration
Categories Income Support for Medical Assistance
Created by Guest
Created on Mar 6, 2017

RELATED IDEAS

Allow Case Workers to Create Incomplete HCR Applications

Currently, when a case worker begins a new Application Form with incomplete information, it is possible to 'Save & Exit' the incomplete application form. This incomplete application form is tracked only on the person level, is not searchable, does not prevent the creation and submission of new application forms, does not provide functionality to inform a client of missing information, and makes it difficult for case workers to identify missing information.

The following enhancements are being requested to address the above issues:
1. Allow a case worker to bypass mandatory field validations on pages within the application IEG.
2. Allow the submission of an Application Form from the Case Worker Portal even when there are unanswered mandatory fields on the application. This could be an option from within the application form, or an action menu item for the incompleted form after a user clicks 'Save & Exit'.
3. Generate an Application Case from the incomplete application form, with a new status indicating the application is incomplete.
4. Indicate on the Application Case which pieces of information are missing (i.e. which mandatory fields were bypassed in Step 1).
5. Create a notice indicating which missing information must be requested from the client
6. Add functionality to track how long it has been since the application has been submitted, and deny the application after a period of time. This could take the form of a workflow with a task raised on incomplete application submission, and deadline processing resulting in Application Case closure.

Customer Name Minnesota
  • Attach files
  • Guest
    Reply
    |     Jul 11, 2017

    Closing this RFE by request from customer.

  • Sigitas Jakucionis
    Reply
    |     Jul 5, 2017

    we at MN would like to withdraw this RFE.
    Sigitas

  • Guest
    Reply
    |     Jun 1, 2017

    There is both an online "Health Care Application" and an internal "Health Care Application" application configured. Although they share the same schema they have separate scripts.

    The mandatory questions are controlled in the script and not in the schema so because there are separate scripts for the portal and case management side, you should be able to modify the mandatory questions in one and not the other.

    Can we get more detail on what you mean when you say there is a single application script that applies to both the online citizen and internal case worker application forms as long as the motivation type is the same.

  • Guest
    Reply
    |     May 26, 2017

    Thank you for your response.

    The problem is that this functionality is requested for internal users of the system (case workers) - who often have to work with partially-completed applications, fill in applications during phone calls, etc. So, per your approach we'd want to remove mandatory fields from the internal application (Person Data Case-->Action Menu-->New Application-->Health Care Application)

    However, we would not want to make these fields optional for the online application that citizens see - they should fill out all mandatory information in order to submit an application.

    Right now, there is a single application script that applies to both online citizen and internal case worker application forms as long as the motivation type is the same. To achieve the approach you're proposing, can we disable mandatory validations only for one application path without altering the other?

  • Guest
    Reply
    |     May 23, 2017

    Customer has the ability to modify IEG scripts to set which fields are mandatory and which are not which gives them the ability to create incomplete applications. Applications, once submitted can be verified for missing information. and requests can be made for the information. Automatic closing of case is also configurable. What business exact business problem is this solving?

  • Guest
    Reply
    |     Mar 8, 2017

    Hi Sigitas,

    Thank you for your enhancement request.
    We require some further analysis to determine whether or not this enhancement can be considered in a future release.
    I will provide another response when our investigation is complete.

    Thank you,
    Eloise O'Riordan, Cúram SPM Offering Management team