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 Social Program Management Platform
Created by Guest
Created on Oct 5, 2017

RELATED IDEAS

An adapter based design for supporting multiple geocoding APIs in Curam

Present OOTB Cúram application uses Google Maps APIs for geocoding of addresses in Cúram and display of such geocoded addresses on a map interface. If we are to change the mapping provider in an OOTB Cúram application, from Google Maps to some other public mapping APIs like Bing Maps or an in-house enterprise mapping solution using software like ESRI; quite a lot of changes are needed across server and client level Cúram artefacts. This extra effort is presently required, every time a Cúram application needs to move from one mapping provider to another one.
With the help of this adapter, goal is to standardize the OOTB geocoding and mapping functionality; and offer better control over changing a mapping provider within Cúram. Once this design is in place, this adapter will provide a fundamental implementation of all geocoding and mapping features needed within Cúram application. Developers will be required to prepare mapping service implementations, to enable a specific mapping provider like Bing, ESRI, etc. Any time a mapping provider is supposed to be changed, a developer will just need to change (or implement a new) service implementation; and not need to touch the underlying infrastructure of the adapter itself. It will be easier to maintain such service implementations later, as a pluggable artefact.

Here in State of MN, we have implemented an adapter based design and I have attached it with this request, if in case it helps in understanding this enhancement request in more details.

I know there have been few other projects that have requested to customize the OOTB support for Google Maps - San Diego county and Singapore (I think). I think an adapter based design should certainly be a good value add-on to our clients and make the process of customizing the geocoding solution easier than it presently is.

Customer Name Minnesota, San Diego County Health & Human Services Agency, Singapore, MSF - Singapore
  • Attach files
  • Guest
    Reply
    |     Sep 20, 2021

    Hi Siddharth,

    As part of our efforts to be transparent about our intentions with each enhancement suggestion, the offering team has initiated an annual process to carefully review the list of open enhancements.
    As agreed through the account manager for Minnesota, we are closing this RFE as it was confirmed that it is no longer required.

    We acknowledge the benefit of your suggested enhancement and although we will not take any further action at this time your suggestion will be available in our ideas repository for future consideration.

    We value your feedback and thank you for allowing us the privilege of partnering with you in developing our products.

    Regards,
    Shane McFadden, SPM Offering Management team
    You can find more information on the request process here.
    Note: we are currently in the process of improving your RFE experience and will soon transition to an Ideas Portal provided by our trusted business partner Aha!
    Further communications with additional details will be shared shortly.

  • Guest
    Reply
    |     Nov 28, 2017

    Hi Siddharth,

    We acknowledge that this enhancement request has been accepted for consideration. It may not be delivered within the release currently under development and we have no short term plans to provide this enhancement. However, the theme is aligned with our current multi-year strategy and will be considered for a future release.

    IBM may consider and evaluate any RFE Community feedback for this request through activities such as voting.

    IBM will update this request in the future.

    Thank you for your interest in the Cúram product.
    Eloise O'Riordan, Cúram SPM Offering Management team

  • Guest
    Reply
    |     Oct 13, 2017

    Thanks Eloise.

    Please feel free to reach out to me at any point if more details are needed for the high level design that I attached to this request.

    As Sigis stated, HIPAA regulation played an important role here in MN to decide to go with an in-house mapping API. However, there have been other clients like County of San Diego, for whom Google was just too costly compared to other public mapping APIs like Bing.

    Regards,
    Sid

  • Guest
    Reply
    |     Oct 9, 2017

    Hi Siddharth,

    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

  • Sigitas Jakucionis
    Reply
    |     Oct 5, 2017

    One reason customers don't accept Google Maps or another public service is that HIPAA and similar regulations do not permit sharing sensitive information. Therefore customers choose in-house geo coding and mapping services, where they can control who accesses the address data.

  • Guest
    Reply
    |     Oct 5, 2017

    Attachment (Description): This is the high level design that was created for State of MN while implementing an adapter based mapping API solution.

    MN_Curam_Geocod...
    MN_Curam_GeocodeMappingAdapter_Design_ForPD.docx
     MN_Curam_GeocodeMappingAdapter_Design_ForPD.docx
    Open full size
    MN_Curam_GeocodeMappingAdapter_Design_ForPD.docx