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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Delivered
Created by Guest
Created on Jan 20, 2020

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 the outbound Interchange is not really sufficient to satisfy the following TR3 requirements.

* The BHT03 is the number assigned by the originator to identify the transaction within the originator's business application system.
* The inventory file number of the transmission assigned by the Information Source's system. This number operates as a transaction (batch) control number.

We would like to suggest that the mapping be changed to populate BHT03 with a literal of "277X214" + the Transaction Set Control Number in ST02 of the current 277CA transaction set. This would be minimally compliant with the TR3 requirements and would allow us to avoid custom modifications to the compliance check components.

What is your industry? Healthcare
How will this idea be used?

As a the originating source of the 277CA transaction (generated by HIPAA X12 Compliance Check when Claim Level Rejection is enabled), I need to be able to provide BHT03 element content that is distinguishable to that it can be used as a transaction (batch) control number.

  • Guest
    Nov 17, 2020

    Delivered in v10.1