I'm not quite sure this is the case, with regards to the Audit Trail. From a database management perspective, each time a record it changed there should be a record of:
1) the change that was made
2) who made the changes
I may be wrong, but this is not something that is easily done in MS-Access. I know with SQL Server these are managed by database triggers. Triggers are programming constructs that exist at the database level and fire in response to some change in a record. A trigger can fire;
1) for update - when a record is changed
2) for insert - when a new record is created
3) for delete - when a record is deleted.
In order to produce an audit trail a trigger (for each action) is created on each table to be audited and that trigger then creates a record in another table(s) of what was changed or deleted.
The reason I don't believe AC currently does this is because a few months ago someone raised the issue of how it handles a patient with a name change: You have to create a new record...or something to that effect, which gives me pause.
If this were in SQL Server a "PriorNames" table would exist and every time there is a patient name change, an Update Tigger would fire and write the old name and the patientID to the PriorNames table. A name search would then search both the current patient table and the PriorNames table to find the patient no matter the name change.
Last edited by gkfahnbulleh; 11/03/2008 2:04 PM.
