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.
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 (I...
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
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...
Reactivate 824 ACK creation from HIPAA data compliance map
Reactivate 824 ACK creation from HIPAA data compliance map as this is still being used by one of our major clients:1. Updating the hipaa_data_compliance_parameter.JSON file to include 824 ACK2. Uncommenting the 824 creation logic from the rules.3....
HIPAA Pack Compliance Check – stop compliance when error threshold is reached.
IBM ITX HIPAA Compliance Check has a parameter that limits the number of Errors reported on the x12 999, but compliance continues to execute even when the 999 reporting limit has been reached. The result is that Compliance can run for more than an...
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...
Do not place IBM confidential, company confidential, or personal information into any field.