I never use a filter for A/D apps beyond high frequency noise filtering.

i have two averages a) read average (RA) and b) average of avarages (AA)

I do average a number of reads, but how many vary greatly on the app. The technique below will, if you ever get a single read thingy to be reasonably stable (which I doubt). with a bit of modification work with an 'every read' setup. Note that it works on RA with a 'background AA'.

1) If RA is way outside the AA, I do not change the display, but DO include it in the AA calculation.
2) If RA is no more than (whatever you choose) different from the AA value, I do not change the display
3) some smarts need be included to avoid the result of 1) making 2) false trigger (how is a trade secret, but you can figure it out)

Erik