Document Move does not move the document itself

[tmccormi]

The operation in the documents tree for moving a document from one patient to another only updates the document table file path. It DOES NOT actually move the document from the documents/OLDID to documents/NEWID/ on the disk.

That is a big issue in my mind. I just discovered one user/account that has 12,000+ attachments under the patient ZZTEST which have been "moved" to the real patient record, but not really. This issue is invisible to the user, but an issue if there are system problems with something like a corrupted SQL and attempting to re-attach documents from the file structure.

[aethelwulffe]

It is a huge issue. A certain lab interface has that issue as well. I think this was blushed over due to conflicts with my.cnf/my.ini server configurations dis-allowing the process.

[aethelwulffe]

ALERT: Someone PLEASE take a look at this. This is IMPORTANT. Patient data directories should be maintained so that all the docs under a directory named for the patient ID actually BELONG to that patient. There are several features that would benefit from this, including migrations and the like. Aside from that, it is just dangerous.