Patient Deidentification Works for One Container but not in Another

Question

Patient Deidentification Works for One Container but not in Another

Will Shirley 0

Hey there!

We're running into an issue where we see patient exports successfully coming back anonymized within one container, but not within another.

The Setup:

Both containers are set up identically, with a anonymization config json in each
Both container exports are being interacted with via Postman calls (with the second container's parameters being updated appropriately)
Both export calls return a 202

The Problem:

Exported, anonymized patient data does not appear in the second container
When investigating the export path via Postman, we see this processing error, export operation failed for reason: Anonymization configuration '<filename>.json' not found."

Any advice for troubleshooting this would be greatly appreciated!

MuthuKumaranMurugaachari-MSFT 8,566 Reputation points

2023-03-02T17:49:23.0566667+00:00

Will Shirley Thanks for posting your question in Microsoft Q&A. Can you elaborate more about the endpoint for container exports via Postman (removing sensitive data), full exception details/stack trace for export operation etc.?
Will Shirley 0 Reputation points

2023-03-07T22:07:49.6366667+00:00
For sure! We are making a GET request to the following endpoint:
https://<SAS_Internal.net>/$export?_container=anonymization&_anonymizationConfig=anonymization_config.json&_anonymizationConfigEtag=<ETAG>&_type=Patient

We successfully get a 202 regardless of which container we are pointing it to, but with the second container, no exported file appears in the directory. When we make a subsequent GET request to the Content-Location that is returned by the 202, we receive the error message(despite the file being in the same corresponding location within the second container):

{ "resourceType": "OperationOutcome", "id": "<ID>", "meta": { "lastUpdated": "2023-03-07T20:05:10.002805+00:00" }, "issue": [ { "severity": "error", "code": "processing", "diagnostics": "export operation failed for reason: Anonymization configuration '<filename>.json' not found." } ] }
Will Shirley 0 Reputation points

2023-03-22T20:34:24.7366667+00:00

@GeethaThatipatri-MSFT would it be possible to have your assistance with this? One of my team members recommended reaching out to you directly since you have previously worked with our teams.
MuthuKumaranMurugaachari-MSFT 8,566 Reputation points

2023-03-23T14:15:25.2233333+00:00

Will Shirley We are really sorry for the delay on this. Based on the exception, it appears an issue with the file path, and I understand the file path is same in second container. This requires investigation from our backend logs to find exact cause and the best way is to open a ticket to our support team.

If you don't have support plan, please send an email to azcommunity@microsoft.com referencing this thread with your subscription ID, details and subject as "Attn: Muthu". I will assist you with next steps.
MuthuKumaranMurugaachari-MSFT 8,566 Reputation points

2023-03-24T13:19:46.55+00:00

Will Shirley Just a follow up to get your thoughts on how we can assist you with your issue.

MuthuKumaranMurugaachari-MSFT 8,566 Reputation points

2023-03-02T17:49:23.0566667+00:00

Will Shirley Thanks for posting your question in Microsoft Q&A. Can you elaborate more about the endpoint for container exports via Postman (removing sensitive data), full exception details/stack trace for export operation etc.?
Will Shirley 0 Reputation points

2023-03-07T22:07:49.6366667+00:00

For sure! We are making a GET request to the following endpoint:
https://<SAS_Internal.net>/$export?_container=anonymization&_anonymizationConfig=anonymization_config.json&_anonymizationConfigEtag=<ETAG>&_type=Patient

We successfully get a 202 regardless of which container we are pointing it to, but with the second container, no exported file appears in the directory. When we make a subsequent GET request to the Content-Location that is returned by the 202, we receive the error message(despite the file being in the same corresponding location within the second container):

{ "resourceType": "OperationOutcome", "id": "<ID>", "meta": { "lastUpdated": "2023-03-07T20:05:10.002805+00:00" }, "issue": [ { "severity": "error", "code": "processing", "diagnostics": "export operation failed for reason: Anonymization configuration '<filename>.json' not found." } ] }
Will Shirley 0 Reputation points

2023-03-22T20:34:24.7366667+00:00

@GeethaThatipatri-MSFT would it be possible to have your assistance with this? One of my team members recommended reaching out to you directly since you have previously worked with our teams.
MuthuKumaranMurugaachari-MSFT 8,566 Reputation points

2023-03-23T14:15:25.2233333+00:00

Will Shirley We are really sorry for the delay on this. Based on the exception, it appears an issue with the file path, and I understand the file path is same in second container. This requires investigation from our backend logs to find exact cause and the best way is to open a ticket to our support team.

If you don't have support plan, please send an email to azcommunity@microsoft.com referencing this thread with your subscription ID, details and subject as "Attn: Muthu". I will assist you with next steps.
MuthuKumaranMurugaachari-MSFT 8,566 Reputation points

2023-03-24T13:19:46.55+00:00

Will Shirley Just a follow up to get your thoughts on how we can assist you with your issue.

Patient Deidentification Works for One Container but not in Another

Activity