Ian McNicoll schreef: > Hi Seref, > > You said: > "What about the legal consequences? For example: I can remember being > told my multiple sources that it is not legal to store healthcare data > of a UK citizen outside of UK." > > I am not aware of any law restricting the storage of healthcare data > outwith the UK. I suspect there may be some confusion around the UK > As I read somewhere, the EU had made a aggreement with Google to store medical data for Europeans only in Europe. Maybe I can find the link again. > Data Protection legislation which prohibits 'personal' data being held > about a subject, without the organisation holding the data being > registered. I doubt if the same could be held to apply to a patient > wishing to store their own data in an overseas hosted environment. > > I can understand that many healthcare providers and national > organisations are attracted by the Google/HealthVault model as by > putting the patient in charge of the visibility of a potentially > widely accessible health record, it relieves some of the difficult > privacy and confidentiality issues. It is also fairly easy for the > various system vendors to populate the very limited set of CCR > clinical data classes via well-documented APIs. > Does someone have an opinion about the classes used by Microsoft? You can find a link to the SDK here: http://www.healthvault.com/Industry/program-overview.html
In the SDK is a Windows helpfile containing information about all classes. > The only problem I see is that this is being touted as a panacea for > all the well-known difficulties of implementing the EHR and ignores > the the necessity for a useful EHR to be 'maintained' so that it > reflects current knowledge, rather than just being a historical list > of observations and evaluations which may conflict and will certainly > not allow accurate workflow and scheduling support. > This seems true, but isn'yt it possible through the API's to add more functionality? Bert
