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
Using DB2 for performing SNIP Type 5 (External Code Set) validation in compliance check map
We have requirements for performing SNIP Type 5 validation and we use DB2 for our client. But we understand from ITX support team that the hipaa_data_compliance map is designed to use MONGO DB for performing SNIP Type 5 validation (External Code S...
Include ISA information in either the data passed to the hcsvu exit for implementing a type 7 rule in the qualifier file or in the data passed to a type 7 custom user exit
We currently have a requirement to compare one of ISA value to 1000A NM1 values to ensure they are same and it is currently no doable in ITX. We received this as a suggestion from support ticket TS005672303
ITXA-Please add the following indexes to the SPE_HIPAA_RULES table.
Please add the following indexes to the SPE_HIPAA_RULES table. CREATE INDEX "B2BADMIN"."I_SP_HRLS_GS08_VALUE" ON "B2BADMIN"."SPE_HIPAA_RULES"("GS08_VALUE" ASC) COMPRESS NOINCLUDE NULL KEYS ALLOW REVERSE SCANS; CREATE INDEX "B2BADMIN"."I_SP_HRLS_ON...
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...
We need a Tool to Identify the Cause of HIPAA X12 Compliance Exceptions
Tool to Identify the Cause of HIPAA X12 Compliance Exceptions
NASCO routinely receives very large HIPAA X12 transmissions from their business / trading partners. (Very large meaning millions of segments and tens of thousands of transactions.) Onl...
Do not place IBM confidential, company confidential, or personal information into any field.