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 IBM 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.
CMS is transitioning all of their webservices from SOAP/XML to either REST/XML or REST/JSON.
However, Curam does not support outbound REST API calls. And, per support ticket WH00012171, IBM's view is "any customer can implement their own strategy for this, by either using 3rd party jars like Jersey and Jackson that are already provided with the SPM product or an RFE can be created to request for this outbound Curam REST APIs to be available in OOTB."
As it is highly irresponsible to ask each customer to come up with their own implementation for supporting outbound REST API calls in Curam, we are requesting IBM to provide a standard implementation to allow Curam to call external REST APIs.
 Dear States,
Please see the attached schedule for releasing services in REST/XML or REST/JSON. This schedule is subject to change and notifications/reminders will be sent out periodically. The BSD's will be available in zONE in the CMS FDSH Services Repository community. The HUB Service landscape ID will begin with RJ instead of H, e.g. The Social Security Administration (SSA) Composite HUB service's SOAP/XML landscape ID is H03, the REST/JSON version landscape ID is RJ3.
If you have any questions please reach out to your State IT PMS.
Regards, Niki Lelis Lead Information Technology Specialist Centers for Medicare & Medicaid Services (CMS)