prunus
Tick tock.
I'd possibly be able to go much further with my comments if I knew what the structure and tech was like myself. But certainly its easy to imagine all sorts of ways to crudely work around this, even if it was only fit to be a temporary solution pending a more impressive update. Duplicate some tables so as not to risk messing up the originals (or use a dev copy of the system and data), add some fields, write and run some scripts to reprocess existing data as a result. Or depending on what sort of processing they do on raw data sources, if they are even in charge of that side of things within that system, there may be some relatively straightforward code changes that could get the job done.
Yes, I have found myself designing and maintaining databases for a living, by mistake, 20 years, man and boy etc. Something can always be kludged, especially if it’s output only (like the dashboard).
My blindness is that it’s not clear to me how one could structure the data in the first place such that adding an A/not-A/all filter on a binary* attribute wouldn’t be close to trivial. In fact in many (perfectly sensible) structures it would be harder to exclude 2nd and subsequent infections. But maybe I’m lacking in imagination.
* even if it’s an ordinal or first-count it’s still going to be A/not-A at the output I guess.