This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
We need to build a map where the input will be an excel file, but the information is retrieved from different sheets.
Each file received contains a different number of sheets and the information will be retrieved by cells assigned in another inp...
We have upgrading the Partner Manger to ITXA and Presently in the Trading manager we have option to see the transaction report( see attached transaction report for details) we are looking not exact similar functionality but want to check if their ...
ITXA-Expand MapName max length to 240 chars for Sterling Integrator maps imported to ITXA
Existing maps from Sterling B2B integrator are imported to ITXA. Map names follow company's naming standard which is expecting up to 240 characters currently allowed in Sterling. ITXA has limit of 50 characters. Impact of this limit prevents seaml...
Claim Level Reject at the Provider, Subscriber or Patient Level
We have received the explanation that claim level rejection works as designed in the 2300 Loop of the 837 and does NOT have rejection capability in the Provider, Subscriber and Patient Loops. Based on our competitors’ capabilities and our client n...
Expanding the map name field will help us us maintain standard Map naming convention with proper description of the map function and the associated standards. The current limitation of 32 bytes is not sufficient. Other mapping tools like Sterling ...
Creation of an ANSI X12 type tree that supports Plan Member Reporting.
The transaction is actually an 834 but is different from the 005010X220A1 834 used for Benefit Enrollment and Maintenance. The GS08 value for this transaction is 005010X318 and the TR3 was releases in November 2016.
Enhacning the ITX imorter to be able to generate type tree from ddf or native usage of ddf would be an useful advantage. Many a times migrating from Sterling mapper to ITX is not straight forward when there is no industry standard being used.
Compliance Check map to include the CTX segments in the 999 Negative Acknowledgement
the usage of the CTX segment in the 999 would utilized in the LOOP ID - 2100 - AK2/IK3 ERROR IDENTIFICATION. where the Business Unit Identifier can correctly show the transaction error. TR3 rules state "Required when the error reported in this IK3...
Do not place IBM confidential, company confidential, or personal information into any field.