In Azure Health Data Services, $Patient-everything operation is not returning the associated resources

P, Pioline (Cognizant) 195 Reputation points
2023-07-04T07:16:23.9566667+00:00

Hi

$Patient-everything operation in Azure Health Data Services is not returning everything associated with the Patient resource.

Can you support.

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.
149 questions
0 comments No comments
{count} votes

Accepted answer
  1. MayankBargali-MSFT 68,656 Reputation points
    2023-07-05T10:44:17.67+00:00

    @P, Pioline (Cognizant) Thanks for reaching out.

    If the $Patient-everything operation in Azure Health Data Services is not returning everything associated with the Patient resource, there could be several reasons for this. Here are a few things you can check:

    Verify that the Patient resource has all the necessary data. The $Patient-everything operation returns all the resources associated with a Patient, but only if those resources are present in the FHIR server. Make sure that all the resources you expect to see are present in the server.

    Check the permissions of the user or application making the request. The $Patient-everything operation requires the patient/*.* scope, which allows access to all resources associated with a Patient. Make sure that the user or application making the request has this scope.

    Check the FHIR server configuration. The $Patient-everything operation relies on the FHIR server's ability to traverse the relationships between resources. Make sure that the server is configured correctly and that all the necessary relationships are defined.

    Check the query parameters of the $Patient-everything operation. The operation allows you to specify query parameters to filter the results. Make sure that the query parameters are correct and that they are not excluding any resources that you expect to see.

    If none of these steps resolve the issue, you may need to troubleshoot further by looking at the FHIR server logs or using a FHIR client tool to diagnose the issue.

    0 comments No comments

0 additional answers

Sort by: Most helpful