@ndhm in health-ids causing issues while creating consent requests

Do we have to migrate all our internal databases to use @abdm instead of @ndhm in all references?

We are seeing a pattern where the consent requests are failing when raised for @ndhm health ids.

Getting either of the below responses during the consent-on-init call.

Response 1

{
"code": 2500,
"message": "Unknown error occurred"
}

Response 2

{
"code": 2500,
"message": "Invalid Provider or Care Context."
}

Sample consent request ids.

  • ddbcddad-4b4d-43a2-bdfa-e1d530df1157
  • 8fd58347-954d-4042-8c4a-dfb8f3253332

Please let us know if we should replace all the @ndhm based health-id address to @abdm?

@sunchu kindly look.

@skvasanth please check