Getting 500 Internal Server Error - While doing reindex job for Single resource in Azure Health Data Service - FHIR service

P, Pioline (Cognizant) 195 Reputation points
2023-10-06T08:58:29.1366667+00:00

Hi

I was creating custom search parameter for claim resource to locate all resource with certain diagnosis code.

I was able to successfully create the custom search parameter using POST {{fhirurl}}/SearchParameter

The following request also showed the custom search parameter that I created in a list[]:
GET {{fhirurl}}/Claim/{{claim_id}}/$reindex

But, when I tried reindexing the custom search parameter for single resource (as mentioned in documentation https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/how-to-do-custom-search) using following request:
POST {{fhirurl}}/Claim/{{claim_id}}/$reindex

I am getting 500 Internal Server Error. May I know the reason for this?

Please let me know soon.

Azure Health Data Services
Azure Health Data Services
An Azure offering that provides a suite of purpose-built technologies for protected health information in the cloud.
148 questions
{count} votes

1 answer

Sort by: Most helpful
  1. navba-MSFT 17,280 Reputation points Microsoft Employee
    2023-10-17T03:52:58.2366667+00:00

    @P, Pioline (Cognizant) We sincerely apologize for the delay in getting back. Due to the complexity of this issue, we had involved the Product Group team on to this. Here is the update from them:

    Update:
    This is a known issue that should be fixed in the next release.

    Link to the fix: Single resource Reindex fixed by rajithaalurims · Pull Request #3522 · microsoft/fhir-server (github.com)

    Once the fix is released, the issue shouldn't reoccur again. The ETA for fix would be one or two weeks.

    ** UPDATE**
    Fix for this issue has been released and the issue hasn't occurred for more than a month now.

    **
    Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

    0 comments No comments