IBM Sterling Ideas

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.

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.) Only a very small percentage of the transaction content is expected to fail compliance checking. Occasionally, however, we find that there are situations where the majority of the transactions end up getting rejected because one or more instances of non-compliance recurs throughout the transmission. When this happens, the standard acknowledgement processes are likely to generate lots of output without necessarily providing the insight needed to resolve the problem.  


It would be helpful to have an application that could to identify the root cause of compliance exceptions that recur throughout the HIPAA X12 transmission. This information could then be used to request changes on the part of the trading partner that has sent the data or to provide guidance on rules that need to be disabled using configurable rules.

  • Guest
  • Aug 31 2018
  • Not under consideration
What is your industry? Healthcare
How will this idea be used?

Identifies the Cause of HIPAA X12 Compliance Exceptions when NASCO receives huge files from their Trading Partners / Plans with NON-HIPAA Compliant errors.

  • Guest commented
    30 Jul, 2019 05:46pm

    Better geared to a services engagement. LIkely a good use case for machine learning, but no current (18mos) plans to productize

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.