Sorry, maybe I was a bit fast. What I meant was you have an application that supports Twain so it can be used on any Twain compliant scanner (could be an expensive document scanner, a small simple Brother, an MFD or whatever). This application does the scan and process the document automatically, PDF/A, OCR, remove blank pages ..) so you have the full functionallity you need for your documents. So it does not matter if you buy a new model of your scanner, you get the same result out. This application puts the the “finished” documents to a folder for importing into your medical system, database system or whatever it is. Typically, in a good designed such system, it supports some kind of automatic import so the scanning application reads barcodes on the documents and names the outputfiles according to the barcodes making an automatic import possible – this will in most cases save a lot of manual work and reduces costs. But here we are more into a good design of the medical/database system, not so much Twain. The scanning application should also be able to support folder import so instead of scanning with Twain it automatically picks up files coming into a folder from MFDs, processes them and put them to the importfolder of the database system. This also opens up for the possiblity to scan with any scanning application and have “proper” documents go into storage in the database whatever the source is, like maybe you get a Tiff file on mail form some customer but you have standardized on PDF/A in your database you just drop the file in a folder and it will be converted and imported. I totally agree with you there is no single solution here, different needs. However the “scanning and import” application should be flexible enough to handle most situations and be configurable in both ends, the source and the destination. Hopefully this clarified a bitt