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
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,
Post an idea
Upvote ideas that matter most to you
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 product management 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 notification 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.
DataStage MDM Connector - Single Sign On (SSO). Current Client (MHD - Missouri HealthNet Division) has a requirement for SSO on all client applications including DS MDM Connector. Currently this is not support
We are implementing MDM SE 11.6 at our client MHD - Missouri HealthNet Division and they have a business requirement for all client connections use SSO. Currently only Inspector (and now Web Reports) has this capability so we need the DataStage MD...
IBM MDM with AWS RDS: Support other AWS RDS databases in the future such as DB2, AWS RDS Open DB support, Postgres, MySQL.
This is second part of the orignial idea: MDMSEAE-I-129 submitted by Sowjanya Tumuluru (firstname.lastname@example.org): Part 1: We are constantly getting a new requirement from many customers to use IBM MDM with AWS RDS Database. We would like to inquire whe...
Let the MDM Docker containers use environment settings from outside the image
The current Docker installable containers use static environment settings for for example database server, ldap server, kafka server, etc. This means we need to create an image for every environment increasing the possibility to have different cod...
IBM MDM with AWS RDS : Support SQL server on Linux
We are constantly getting a new requirement from many customers to use IBM MDM with AWS RDS Database. We would like to inquire when can IBM support support SQL server in Linux as new SQL Server ODBC connector for Linux was released in April 2020 -...
MDM SE Support for latest verisons of MSSQL JDBC Driver
MDM SE only seems to support the MSSQL drivers version 7.4 (the docs say 6.2.2, but IBM support says 7.4). Since then, there have been a number of newer releases from Microsoft, and we would like to use newer versions of the driver in accordance w...
Allow consent to be recorded for Organizations in MDM
Currently, attempts to record consent against an contact in MDM classified as an organization yields the following error: <?xml version="1.0" encoding="UTF-8"?> <TCRMService xmlns=" http://www.ibm.com/mdm/schema " xmlns:xsi=" http://www.w...
Sample scenarios: An adult (parent, guardian) provides consent on behalf of a child. The child is a client, the adult is not. A company officer provides consent on behalf of an organization For both scenarios the following five cases are material:...
Two use cases: Operational use cases are typically interested in the set of active consents for a given client. Some use cases only have an interest in a specific consent. Typically these use cases will know client ID and Processing Purpose Type Code
Enhancing Patient Safety when Potential Overlay is Identified Using IBM MDM
Issue: The MDM application leaves a PO record in an entity. This allows a search based off the PO ID or the PO Demographics to return an incorrect patient. Currently the application prevents returning the ID when requested which helps prevent send...
Do not place IBM confidential, company confidential, or personal information into any field.