Hi,
Many of the tables currently do not have a field for the date of entry: To us this is a big gap in tracking data entry and generating reports. It is our recommendation that we add a date of entry field in all tables. Maybe even add another field for date_modified. I would also strongly recommend that this requirement be made a mandatory part when creating new tables, be it in forms or otherwise.
I’m in favor of adding this information to most tables. I’ve found it useful in the past on other applications to include this type of information, typically both a timestamp for creation and for last modified, and often the id or login name of the account responsible.
I can’t figure offhand if it’s necessary to do for ALL tables, or just many.
Is this something we can wrap up in a central place without having to edit every SQL call?
(This is one of those places where it would probably be nice if we were using some kind of ORM library.)
OpenEMR tables have more Insert operations than the Update operations. For the tables with pure Insert (& delete) only operation, there is a field ‘date’. The maximum of the ‘date’ can be the last updated on.
There are tables (for instance notes, immunizations, documents) which records the last updated as CURRENT TIMESTAMP. For few tables, it is updated from the Application (for instance process_date in billing) and hence the updated on can be extracted.
Regarding the loginID, when the auditing is enabled the access info will get captured (including users/loginname). Could you pls share why loginID is requested for each table?