Pysched, you are doing some nice work, there. Yes, there is frustration that abounds. Again, just some thoughts to throw out there to you:
Realizing that since there is not stringent specifications, you have some flexibility in what is in your scope and what is not. To your point, if it is a functionality that you are not using, then you don't need to validate it (just make notation to that). If you are not going to submit electronic records, you will need to assure the data is not archived/stored in any way, and disable the electronic signature feature.
What you might could do is validate fairly extensively one station. Assure revision control/ etc. in that all stations have the same program/ information on it. Then, perform random verifications at each station.
Others may have another input on this one, but lean on thicker instead of thinner for validation projects. If you get too lean and an auditor was to walk in, they may raise an eyebrow. Too, hopefully your validation project is not just a dust collector. It will have helpful reference material for your software project to be used when revision time comes up, and when a problem arises.
Eventually, this software program will be replaced. Hopefully, your validation package will be as such that it will provide a great foundation for the new application.
Again, I am not in validation. So take these for what they are worth (which is about

)
