Patient Deidentification Works for One Container but not in Another

Will Shirley 0 Reputation points

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!

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