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.

Compliance Check App - Consistently create REF(D9) Segment in the 277CA to tie Claim Ack back to the original good/bad 837.

Our organization needs the capability for the HIPAA Pack's Compliance Check application to consistently generate a 277CA (005010X214) with a REF (D9) segment for both good and bad claims so that the 277 Claim Ack may be tied back to the original claim. Our interpretation of the TR3 situational notes in the X214 Implementation Guide is that the REF (D9) segment needs to be created with the REF02 value provided as received in the original 837, and that it shouldn't matter whether the claim was for a patient who is the subscriber or the dependent. The IG states that the 2000D loop is situational. The Compliance Check has been designed for performance reasons not to create the 2000D because it is not required, and that if all claims are accepted, that only the provider level is created and not the patient level. But without the REF02 segment for either subscriber or dependent level claims, we cannot tie the 277CA back to the good or bad claim it is acknowledging.
  • Guest
  • Jan 9 2018
  • Delivered
DeveloperWorks ID DW_ID105578
Link to original RFE
What is your industry? Healthcare
  • Guest commented
    27 Aug, 2019 05:09pm

    Delivered with ITX Pack for Healthcare 9.0.2

  • Guest commented
    14 Nov, 2018 04:10pm

    We plan to incorporated in a future release

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.