IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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

Post 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


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.

IBM Employees should enter Ideas at https://ideas.ibm.com


ADD A NEW IDEA

All ideas

Showing 15491

Contract with VA to use thier 9 million active (as well as former) member medical history in regards to data on prostate cancer. There have been very limited studies on prostate as to cancer cause and follow up. Mainly because disease is for 50 and up (60 mostly). Those that get cured drift away. Others die off. There are only 3 stnd methods of treatment all poor. There is zero concensus after a 100 years. Some believe its low testosterone as one ages. Others believe its testosterone itself that cause prostate cancer. Others believe its DHT converted testosterone. Others believe its first a low testosterone and then the testosterone is increased. The VA give blood tests called labs regularly to all 9 million members several times a year. They should include as standard labs for PSA marker, testosterone, DHT, estrogene and lutinizing. Shortly if not already available Watson could generate data on 9 million plus millions that have passed on to determine which of the named hormones/issues contribute directly to diagnosed prostate cancer. In my case, had a pituitary benigh tumor where testosterone dropped to nothing. After removal, testosterone back in normal range. Then PSA shot up dramatically, then leveled off. Then pituitary had issues again with testosterone low. Took prescribed testosterone. Then/since PSA keeps increasing dramatically. Biopsy indicated cancer. I have 5 years of labs for PSA, testosterone, DHT. I think its pathetic now that there is cloud computing and easy mgnt of data that using the VA a perfect captive market analysizing data each of these markers/hormones. VA captures weight every visit and other particulars. Those using the VA do not fade away once cured or even with slow growth cancer so data is massive as nearly all VA patients are older than 50. Donate this effort for humanitarian and get tax write off. Related idea for health. Set up a self serve as well as comprehensive data base for all diseases. Most doctors are not nearly up to date in the myriad of data or studies on all the diseases in their field. Develop 2 apps. One for patients, Show image of front/back and sides. Let them click on part of body they have pain/problem with. Then have Watson (after web crawling world data base of all diseases) display all the symptons for this disease. Let patient check off those they think they have. Next, let them list all other existing issues just like every stupid form you have to fill out over and over and over again at every doctor, dentist etc.Then IBM could sell this app to medical health companies to funnel traffic to them. Same type of version could be used for a doctor during/after a visit. Dr could enter by voice/transcribe what patient said. Watson could come back after reviewing all the diseases in the world against the listed symptoms and make determination of what disease(s) it is and recommend testing/treatment and most recents trials/studies. I dont want some doc trying to keep up with all the health/medical information being developed. Actually, most first line doctors could be eliminated or at least first vists be more productive. Medical health could reach around the world just like mobile phone. This will make people take ownership of their health- dis/ease. This is what is recommened before you visit doctor anyway. List all symptoms, pain, questions and related to be discussed at first meeting. Dont sit their like a log and have him guess which of the 100s of thousands of diseases you have. I was the one reading my labs with the PSA going up over the years not any of the doctors assigned to me. I

I gave all that info in the idea above. Cull the VA for prostate cancer data via the blood labs on 9 million vets that use the VA health care service until they die so that trials and studies can be continuous and on going. Benefit is pro bono tax...
over 6 years ago in watsonx Assistant 1 Not under consideration

List view to see annotation results for each type system

In order to create a good mode, we need to annotate with consistency and need to have enough training data for each entity and relation. Currently there is no tool or view to see what kind of words and how many words were annotated for each entiti...
over 6 years ago in Watson Discovery 0 Not under consideration

List view to see all annotated documents

Right now, in order to view annotated documents, we have to click each document and close them. A UI view where you can see all the annotated documents are preferred. With such view, instead of clicking each documents, annotators can double check ...
over 6 years ago in Watson Discovery 0 Not under consideration

Rate Limiting Headers are missing

The headers are missing in the response as stated in https://www.ibm.com/watson/developercloud/assistant/api/v1/curl.html?curl#rate-limiting .
over 6 years ago in watsonx Assistant 1 Not under consideration

Add a hook in ingestion API to get latest document security information from 3rd party API

If ingestion API supports adding a hook or callback to add an "access control meta-data" enrichment, it could stream integration with custom content with strict permission requirements. Our customer can provide us with an API (hosted in their site...
over 6 years ago in Watson Discovery 0 Not under consideration

error sys-date

when you tap "Septiembre 15" in spanish sys-date, gets @sys-date:2015-09-01, should be @sys-date:2018-09-15
over 6 years ago in watsonx Assistant 0 Not under consideration

Negated Operators for nested queries

The Discovery Query Language doesn't allow negated operators for nested querys (ticket existed but hast been closed). Negated operators within a nested query work fine: attributeList:(id::“KEY:9553”,value_string:!Quad-Core-Prozessor),attributeList...
over 6 years ago in Watson Discovery 1 Not under consideration

Modify sys-date "mi" in spanish

The system entitie is recognized when you write "mi" in spanish language, that's because mi is refered to "miercoles", the next Wednesday of the week. Is confuse used that because if i said "mi tarjeta" I'm refered to my.
over 6 years ago in watsonx Assistant 0 Not under consideration

When you select a workspace, add workspace's name to each WKS panel

When you select a workspace, add workspace's name to each WKS panel; if you have several workspaces, the risk is to forget what workspace you are working on
over 6 years ago in Watson Discovery 0 Not under consideration

Query results for entities extracted with a WKS should include a list of all mentions that are in the entities coreference chain

Currently entities are reported in query results with only one "text" field, even if they are part of a coreference chain (and hence count > 1). This is problematic if you need to search parts of the query results for this entity since it may h...
over 6 years ago in Watson Discovery 0 Not under consideration

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.