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 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 needs, we need to be able to reject claims (not entire transactions) for data in the Provider, Subscriber and Patient Loops.
An 837P transaction file containing 5000 claims is received, client wants to reject if Subscriber or Patient ID is not valid (not found on file in the database). Only those claim for that Subscriber/Patient should reject and all other claims for other Subscribers/Patients should continue to process and be accepted if there aren't any other failures.
An 837P transaction file containing 5000 claims is received, client wants to reject if the Provider ID is not valid (not found on file in the database). Only those claims for the Provider that fails should reject and all other claims for other Providers continue to process if there aren't any other failures.
Other software vendors have this capability and it is essential for our new clients trying to eliminate other software such as Edifecs.
|What is your industry?||Healthcare|
How will this idea be used?
New business to reject claims at the Provider, Subscriber or Patient level.
Do not place IBM confidential, company confidential, or personal information into any field.