On 24 Oct 2004, at 5:14 PM, Thomas Beale wrote:
will ross wrote:
On 22 Oct 2004, at 7:32 PM, Thomas Beale wrote:
It is completely designed around the idea that the data / work being done on the virtual computer is individual, and only ever a sink...like email. I would love one of these for travelling. But it won't work for EHRs which by their nature require to be connected to a health computing framework at times when you are not using it directly at point of care. As a data repository, the EHR is not like email...
... but the EHR repository is like a smart inbox displaying messagess sent from clinicians (or from devices) on a health computing framework.
no, it's not. Only you can see your email. The idea of an EHR is that everyone (relevant) can see it. It's not a private resource, it's a shared resource with controlled privacy.
We agree about shared access to the ultimate EHR repository, which is not like private access to an individual email box. That wasn't my point, which was poorly made, for which I apologise. I should have said that while the EHR repository itself is not like a private email account, the workflow queue of incoming EHR content (or action items) resembles a shared email inbox. I was speaking about the way an email *inbox* (as a gateway to a respository) organises inbound EHR content from various sources (both human and bot), not about the way an email account controls user access to the *content* of the inbox. It occurred to me because I'm working on a clinical messaging middleware project which uses an email paradigm to provide practice level access (as opposed to individual clinician access) to queued EHR content one step before it flows into the EHR, or in the case of some EHRs, as workflow events to be viewed from within the EHR.
[wr]
- - - - - - - -
will ross phoenixpm.org project manager [voice] 707.272.7255 http://www.phoenixpm.org
- - - - - - - -
