Hi Bert
I am sure the technical people will respond but it is a good question. The commit time is the time that the author committed it to the system. I believe this is usually generated on the server to ensure accuracy. When there is a system with considerable delay between the clinician saving to the record and the record being stored in the EHR repository, I would use the Finish Time of the event context for the clinical commit time and leave the commit time to show when this information became visible as part of the health record. Cheers, Sam From: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org] On Behalf Of Bert Verhees Sent: Wednesday, 23 January 2013 8:50 PM To: openehr-technical at lists.openehr.org Subject: Re: Questions about commit and AUDIT_DETAILS On 01/23/2013 06:11 AM, pablo pazos wrote: The definition of AUDIT_DETAILS.system_id is: "Identity of the system where the change was committed. Ideally this is a machine- and human-processable identifier, but it may not be.". Let's say I have a CLIENT where COMPOSITIONS are created, and a SERVER where COMPOSITIONS are committed by the CLIENT. I understood this as not technically committed (that is the database-server) but conceptually committed, and that is the machine on which the client-user is typing/clicking. The client-user gives order to commit a dataset. This is different if there is an automatic feed of data, in that case, the feeder-audit is used. regards Bert Verhees -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130123/b06dd73d/attachment.html>
