Hi Karsten,

a) these repos are not the primary sources of the data. Hence, the deadlines do not apply!

b) Implementing such a process was demanded by the state data protection commissioner. I'm not sure how realistic this would be, but such a network heavily relies on patients' trust. If there is doubt, you lose.

Besides: we implement openEHR in a distributed data warehouse scenario. Most data will be integrated locally from application systems. To be able to share data with other sites, we need to consider patients' consent. If a patient withdraws, we don't have any purpose to keep this 'secondary use data' within the data warehouse/openEHR system. Besides the legal questions, being able to physically delete data from such a database is also necessary for practical development and maintenance reasons.

For operative systems, this is a whole different story. I recently was told that physically deleting records should not be possible when you want your software to be certified as a medical product according to German law.

Birger
--
Diese Nachricht wurde von meinem Android Mobiltelefon mit 1&1 Mail gesendet.
Am 05.11.17, 5:54 PM, Karsten Hilbert <Karsten.Hilbert@gmx.net> schrieb:
On Sun, Nov 05, 2017 at 05:31:50PM +0100, Birger Haarbrandt wrote:

> just a short remark: we were involved in a regional EHR (in the sense of a
> health information exchange network) project in the state of Lower-Saxony,
> Germany. While this might be a different use case, we clearly had to be able to
> physically delete patient data from all IHE XDS repos and registries in the
> case of a patient's withdrawal.

a) The repositories were likely not the primary repositories
intended for immediate clinical care ?

in which case the deadlines don't apply

b) had you suspected that a withdrawing patient intends to sue
the health information exchange network you would likely have
had the right to retain data regardless

But, yeah, physical deletion certainly seems necessary even
if only, say, 50 years post mortem ...

Karsten
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346

_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Reply via email to