On Fri, 18 Feb 2011 16:30:08 -0500, Elpidio Latorilla
<elpidio.latori...@gmail.com> wrote:

> have you seen this document? Very interesting. It uses the Care2x
> system as specimen to present their ideas of patient information
> privacy. It even proposes improvements on the Care2x system.

>From that paper's "5.Conclusions": 
"Privacy is a fundamental issue in hospital information systems. In
fact most of the involved data are sensible and therefore their access
and manipulation is strongly regulated."

And from "3.3 Weaknesses":
"Care2x cannot be considered a privacy-aware system"

Using 'modus tollendo tollens', we can easily conclude from 3.3
and 5., that Care2x could not yet be proved to be a safe hospital
information systems supporting software package.
Meaning that in countries were there is regulation, it will be not possible to 
support any hospital information
system using the Care2x package.

After years following the Care2x project one wonders why it
could not solve this basic problem, that other projects
(http://www.oemr.org/ for instance) which had by then much less
resources, where able to solve easily in a few weeks (using the same
available open source ancillary resources).

As a matter of fact, I do believe that Care2x (which is more
directed towards hospital care support) would have much to
learn from (and could reuse lots of code from) if it could
find some way of establish a close cooperation with the said openemer
project (which is more directed to the private practice office).

Also it would be useful to find what turns Care2x in such an elusive
golden egg chicken and, either kill the chicken, or tell all those
would be gold diggers that this project will never lay eggs made of
gold.

At most what Care2x will do is help some lucky healthcare
providers to keep their patients safer while avoid the costs of
software vultures. And that 'per se' would be reason enough to keep
Care2x alive.


r.

JA

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Care2002-developers mailing list
Care2002-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/care2002-developers

Reply via email to