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:
Post your ideas
IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.
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,
1. Post an idea
2. Upvote ideas that matter most to you
3. Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM 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 IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notifications on the decision
Some ideas can be implemented at IBM, 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.
Utility to check compatibility and compliance of maps when upgrading to a new ITX version
ITX to provide an utility that can check if th existing maps are compatible with the new version of ITX or needs recompilation/modification. For shops with hundreds of maps this will identify the maps that need some action, hence improving the mig...
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...
BHT03's in Claim Level Rejection 277CA Results Should be Distinguishable
For HIPAA Compliance Check with Claim Level Rejection and 277CA Enabled, the BHT03 values are not distinguishable within the outbound Interchange created by the application.Mapping a hard-coded value of "277X2140001" to multiple BHT03 locations in...
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_ONOF...
Allow the HIPAA Compliance Reports to be formatted in JSON vs HTML
In the age to REST and Angular Web technologies, having the Compliance report formatted as a JSON Object vs the existing HTML, would be of significant benefit for modern Web / REST interfaces to be able to process the Compliance Report should it ...
For the HIPAA Compliance Report, only include the lines relative for the document / Claim/Payment/Enrollment etc where the Failure was detected.
Currently the HIPAA Compliance report is produced in two parts, the Summary and the X12 Lines, which currently include ALL the X12 lines in the Interchange, and when have an Interchange of 50-100MB, this poses a problem for the Browser to load. If...
To have functionality that will update all X12 string (A/N) data element to not allow trailing spaces if the minimum data element length has been met.
Currently, in order to turn on not allowing trailing spaces when the minimum X12 data element length has been met on an A/N data element, it is necessary to individually update each data element. It would be nice to have functionality that could...
ITX for PEPPOL
PEPPOL is a set of artifacts and technical specifications enabling cross-border eProcurement within the EU. Would be good if ITX comes with the support for PEPPOL standards. There could be huge business with validation and compliance check.
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.