As ReportStream, I need to be able to deidentify messages of PHI/PII before sending to certain jurisdictions, like the CDC.
Description/Use Case
The DEX project has a table of values that need to be redacted, which is based off the HL7v2 ELR spec. We need to look up the HL7v2 RadxMars ELR spec and see if that list matches, and then implement that for the DEX receiver.
Risks/Impacts/Considerations
We can create a placeholder DEX receiver if one is not already created by the time this ticket is picked up and create a follow on ticket to configure the DEX receiver.
Dev Notes
We need to design a good way to deidentify messages. My first thought is to use receiver transforms on the FHIR before translation. We may need to expand our transform functionality/strategy to support this. Receivers like the CDC could have these transforms set if they need to receive deidentified data.
Acceptance Criteria
[x] Deidentification strategy exists
[x] Deidentification "configuration" (could be transform) created for DEX that follows the RadxMars ELR spec
User Story
As ReportStream, I need to be able to deidentify messages of PHI/PII before sending to certain jurisdictions, like the CDC.
Description/Use Case
The DEX project has a table of values that need to be redacted, which is based off the HL7v2 ELR spec. We need to look up the HL7v2 RadxMars ELR spec and see if that list matches, and then implement that for the DEX receiver.
Risks/Impacts/Considerations
We can create a placeholder DEX receiver if one is not already created by the time this ticket is picked up and create a follow on ticket to configure the DEX receiver.
Dev Notes
We need to design a good way to deidentify messages. My first thought is to use receiver transforms on the FHIR before translation. We may need to expand our transform functionality/strategy to support this. Receivers like the CDC could have these transforms set if they need to receive deidentified data.
Acceptance Criteria