There is the situation of an EHR-system and the situation of an EHR- extract.
In an EHR-system physical deletion MUST NOT be possible. Deletion after attestation will be in all situations legally not allowed. Because of rights citizens have it must be possible to logically delete them. A new version must be created depicting the new situation. When information is sent between two EHR-systems the EHR-extract is used. Here are two situations: - a handover of a complete patient file because of a change of practitioner. - a document produced by one practitioner is transported to an other practitioner. In the first situation the complete record is transported. Including all logically deleted parts. In the second situation only the 'active' parts are transported. All logically deleted parts are not sent in the EHR-extract. What is exactly in the openEHR specs I don't know. Gerard -- <private> -- Gerard Freriks, arts Huigsloterdijk 378 2158 LR Buitenkaag The Netherlands T: +31 252 544896 M: +31 654 792800 On 16-apr-2006, at 11:13, Bert Verhees wrote: > Let me enlighten my question > > Bert Verhees schreef: >> Thanks again for the help with the authorization-question, I was >> lost in the wrong document of the specs. >> I must say, reading the specs, really is not something for a rainy >> afternoon, but it is worth it. >> >> I have another question, probably it also is in the specs, but I >> didn't find it. >> ------------------ >> Is it possible to delete a composition in a way that is not >> traceable anymore? > What happens on deletion of a composition, will there be created a > new version, which indicates the non-existence, and are old > versions kept? > Or is it possible to delete all versions of a compositions. > > I guess, this is not possible, but I am not sure > > (I mean this when using the openehr structure) > > Thanks, > Bert Verhees -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060416/0c93de9b/attachment.html>
