You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?"
The text was updated successfully, but these errors were encountered:
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?"
The text was updated successfully, but these errors were encountered: