Data masking is currently failing for FHIR-compliant api. The formal MIME-type for FHIR resources is application/xml+fhir orapplication/json+fhir. Having said that, the content is syntactically just xml or json. It would be great to add this corner-case for Data Masking patterns for both json and xml.
Agreed @Cladius Fernando. Any thoughts @bala@apigee.com?
Multiple extensions of standard content-types, sort of one per industry, are emerging. At the same time, data masking functionality is also becoming mandatory due to data privacy requirements. This limitation is causing implementation of such content-type.
Data masking should not be strict on exact content-type match and should be implemented on the line of XML to JSON policy.
My suggestion would be to use a regex pattern like application/json* instead of application/json and application/json+fhir.
Dear @Cladius Fernando,
I have raised an internal requirement for this (APIRT-2955). I will update once it is addressed.
Thanks,
Amar
Hello @Amar Devegowda!
Can you provide any updates on the feature request above (APIRT-2955)?
Thank you.
User | Count |
---|---|
2 | |
2 | |
1 | |
1 | |
1 |