Hey Paul, welcome to the community!
Confusingly, there are two disability filters that are not easy to distinguish.
The one you need is labelled:
"Long-term health condition/disability"
That should give you the sample you’d like. Let me know if that doesn’t work!
And we’d love to get to know you a bit better, so when you can, introduce yourself to the community 
Hi Josh,
That is the one I had already clicked on, and as far as I can see only filters for people with the disability not those without.
If you type in ‘disability’ to the custom filters search bar, it should give you two options:
The first option will give this filter:
By selecting ‘No’, you should get the sample you need.
Is this what you’re after? Apologies if I’ve misunderstood.
And I realize how unhelpfully they’re labelled! We’ll make them clearer.
Great, thanks. That will filter out more than I need (unless you can select no on that one, and then pick the disability you want them to say no to on the list), but I expect I will still have a big participant pool.
They are confusingly labelled. It would make more sense to have the option of choosing yes or no for the relevant disability on the option that gives a list of disabilities to filter on.
They are very confusingly labelled. I’m going to flag it with our team for change, and pass along your feedback about improving the functionality of this filter. Your suggestion is great.
Sorry about any trouble caused! 
Let me know if I can help in any other way.
No problem. Thanks for your speedy reply.
Hello, I was wondering if there was any update on this kind of filtering—either in Prolific itself or if you’d found a workaround for it. My lab group is also looking for a way to screen out a subset of the conditions listed in “longer-term health condition or disability”, and want to be able to check yes/no for each condition provided.
Hey @rpkarlin, welcome to the community! Glad you’ve joined us 
We’re currently working on changing the way filters can be applied to samples, but it’s in the design stage of development right now. So, unfortunately, this problem still remains.
I’m sorry that I don’t have better news! I’ll keep you updated on how it progresses
