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.
NCPDP Compliance Check Enhancement
Enhance the NCPDP compliance checker to provide situational compliance checking for the entire transaction. Some examples are: We would expect a transaction to fail compliance when the Compound segment (AM10) is sent and field 436-E1 in the Claim ...
999 ISA Control Number
Currently the ISA control number (ISA) always has a value of 000000001 in every 999 transaction that is generated out of compliance. X12.5 Interchange Control Structure section 5.1.2 requires a unique number within a reasonably extended time frame...
Develop a compliance check for the 277CA
It is common for claims processor to do pre-adjudication business editing in addition to doing transaction compliance checking. The results of the pre-adjudicated processing are reported on the 277CA. Currently there is not a compliance map for th...
Type 5 editing based on date of service for medical code sets
Currently type 5 editing is based on processing. Medical codes are based on the date of service and not processing date. We are requesting an enhancement for at least all of the 837 transactions to include the PACDR to edit medical codes sets (ICD...
Claim level reject enhancement
Currently with claim level rejection if there are duplicate CLM01 values, claim level rejection is not possible. We would like the recommend an enhancement to check the entire CLM segment for duplication which may eliminate the duplication of the ...
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...
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 b...
WTX service discloses detail software versions & file system
WTX service discloses detail software versions & file system - Cases - IBM Support
The Launcher process uses three TCP/IP ports. The first port is for status, the second port is for monitoring and the third ...
JSON Native schema - Enabling Mandatory Fields
Currently, when using the native JSON type tree, it is not possible to make elements to be mandatory. We will not always use JSON importer to create type tree and there are cases where we use JSON file directly as native schema. This enhancement w...
Transformation Extender Advanced validation for Envelope service needs to include invalid enveloped documents
Customer requires that invalid outbound data, the inbound data that caused the issue, and the translation report showing the errors in the outbound data. Current behavior returns the inbound data, the translation report, but not the outbound data ...
Do not place IBM confidential, company confidential, or personal information into any field.