Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider adding a philter debug/audit mode #177

Open
mikix opened this issue Feb 24, 2023 · 0 comments
Open

Consider adding a philter debug/audit mode #177

mikix opened this issue Feb 24, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@mikix
Copy link
Contributor

mikix commented Feb 24, 2023

We are considering adding built-in philter support (#77). Inevitably that support will probably be allow-listed or block-listed in some fashion.

Another thought is to additionally add an "audit" mode where we run philter on everything unconditionally, and report on any differences. So like, let's say we only run philter on notes. The audit mode could run it on every string field anywhere, or the raw json maybe. And report on anything it caught over and above our normal mode.

This way, we could periodically test whether we should be philtering even more.

Similarly, there could be a mode that detects whether it found PHI in the fields it normally scrubs - like a mode to say "should I normally run with --philter or not?"

@mikix mikix added the enhancement New feature or request label Feb 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant