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 Russell,
Thank-you for your comments outlining more details regarding your concerns.
SPM provides a framework for integrating with the federal hub / external services. We will continue to support this framework.
The framework consists of a set of interfaces to support integration of federal hub data into SPM.
OOTB we deliver 1) a set of default empty implementations for these interfaces, and 2) a set of initial concrete implementations leveraging a specific version of the CMS SOAP APIs.
The version of the SOAP APIs being called in the concrete implementations are initial versions that have not been updated, as it was intended that customers would provide their own implementations within the framework to replace OOTB and to take on the latest CMS updates to these SOAP APIs over time.
With REST, customers will be able to create (or update) custom implementations to call CMS REST APIs instead of SOAP.
SPM will continue to call these custom implementations within the bounds of the framework:
https://www.ibm.com/docs/en/spm/8.0.0?topic=systems-customizing-external-system-implementations
The concrete implementation is the one for which there are plans for deprecation, as it has not been updated with CMS updates since about 2014 and we have no plans to update.
Also, while the other RFE 151741 'Support for Outbound RESTful Webservices' is related to this RFE, it is a more generic API request that we are evaluating separately.
I hope these answers address your concerns and thanks again for sharing your ideas with us.
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.
Hey Shame,
Thanks for your review our FRE. I noticed that it got declined
Checked latest release, it appears that the SPM V8.0.0 still supports federal hub verification services
https://www.ibm.com/docs/en/spm/8.0.0?topic=systems-supported-federal-hub-verification-services
It appears that this is not an enhancement, rather requirements to continue to support existing features.
If we understand your review comments correctly, due to the SOAP APIs will be decommissioned in March 2024 by CMS, SPM will drop the support of existing federal hub verification services in the furfure release. Does that mean that these OOTB features will not work anymore, or SPM will drop these existing features?
Just noticed that our RFE 151794 is the same as an existing RFE 151741 – Support for Outbound RESTful Webservice, raised by State of Missouri. The RFE 151741 is still under consideration.
Very appreciated for your reconsideration.
Regards,
Russell
P.S. Please find the attached for the email from CMS to all states.
===========
Dear States,
Earlier this year CMS conducted a survey on state capabilities to support Representational state transfer (REST)/ JavaScript Object Notation (JSON). CMS is planning to upgrade/modernize our HUB services from Simple Object Access Protocol (SOAP)/Extensible Markup Language (XML) to either REST/XML or REST/JSON to take advantage of native AWS functions and features sometime in March 2024.
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)
============
Hi Russell,
We have reviewed your enhancement suggestion. Based on the information provided, our understanding of your request is as follows:
You are requesting that the CMS Federal Hub integration points provided in product be updated to support the new CMS Federal Hub Services REST APIs planned for upcoming releases as CMS transitions their webservices from SOAP/XML to either REST/XML or REST/JSON.
We acknowledge the benefit of the proposed enhancement. However, the integration points available in product provide a framework that is best customized locally by each client to meet their specific needs.
In addition, clients will be able to implement the outbound REST API calls that will be required using 3rd party jars like Jersey and Jackson that are already provided with the SPM product.
We are closing this request and do not plan to take any further action. If you believe we have misunderstood your request please respond within 7 days with clarifications.
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.
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.
Hi Russell,
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 in order to complete our evaluation, we will send you a request for more information.
Thank you,
Shane McFadden, SPM Offering Management team
You can find more information on the request process here.
Attachment (Description): HUB Services REST/JSON Transition Schedule