Skip to Main Content
IBM Sterling


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 updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Aug 31, 2018

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.

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
    Reply
    |
    Jul 30, 2019

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