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,
Post an idea
Upvote ideas that matter most to you
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
Hi Faisal,
We have reviewed your enhancement suggestion.
Based on the information provided, our understanding of your request is as follows:
Your are enquiring about whether there are plans to change the way in which rules are developed in the Cúram application, this is not aligned with our product strategy
For 20 years now, Curam (and indeed the wider HHS software industry) has consciously adopted and embraced a low-code, no-code approach. For those areas of our customer’s business which change and/or evolve on a regular basis (e.g. Rules, Evidence, Scripted Questions), Curam provides infrastructure to allow content in these areas to be configured rather than coded. This is important for our customers, in that they do not want to have to rely on IT departments or SI partners to release new versions of their systems on an going basis; rather they want to push data and metadata into production in response to these regular changes.
As such, we took the decision many years ago to step away from development-time Rules development in favour of a metadata-driven approach (currently CER, but even classic rules were metadata-driven at the end).
We feel it would be a step backwards in the market to return to the era of defining legislation in policy in static, deployed code. and as such are not considering this enhancement request for a future release. We would of course be happy to consider and schedule enhancements to our existing metadata-driven approaches to help our customers and partners in their experience in defining content in these areas.
We are therefore closing this request and do not plan to take any further action.
Thank you for taking the time to share your ideas with us. Although we cannot pursue all the submitted suggestions, we are committed to involving our users in building our product roadmap and appreciate your ideas.
Thank you.
Graham McCrindle, SPM Product Management Team.
Hi Faisal, I have been discussing this with our Chief Architect and will have a formal response for you shortly, sorry its taking a little longer than 30 days to respond on this but with annual leave etc its been difficult to align the correct people to discuss.
Thanks
Graham McCrindle, SPM Product Management Team.
Hi Faisal ,
Thank you for taking the time to share your ideas with us. We are committed to involving our users in building our product roadmap and appreciate your suggestions.
We will review the information you have provided and get back to you within 30 days. If additional details are required to complete our evaluation, we will send you a request for more information.
Thank you,
Sheryl Brenton, SPM Product Management Team