This happens when the annotation matched against is no longer associated with an Encounter or an Individual but still used for matching, such as when an Encounter is deleted but the annotation remains in our database cache. This can be ignored, though we are working to prevent these from appearing.
We do have some logic to prevent some detectable instances of this, but there are some edge cases that may still get through, such as very old scan results or results where the Encounter was only very recently deleted.
If you’re able to reproduce this after re-running the scan, then this may be an edge case we can investigate and prevent in the future.
