I think the first point is key: I don't really see an scenario where your health data would be sent to an untrusted source. But maybe in a future where we can envision an "ebay-like" service of distributed medical services or something like that
2017-11-13 13:17 GMT+01:00 Bert Verhees <[email protected]>: > Not very far from now (looking into the future, Scotty and Captain Kirk), > health information will be a worldwide web. > Mayor players are diving into this trillion dollar business. > > Health information will need to be accessible, and blockchain can be used > to guard all interaction between systems. > You can find dozens of documents which handle about this. > > In the Netherlands Nictiz is busy with it. > > For example read this (sorry, only Dutch) > https://www.nictiz.nl/SiteCollectionDocuments/Whitepapers/ > Blockchain_in_de_zorg.pdf > > Summarizing: > - Blockchain is needed when interacting parties do not trust or know each > other > - A trusted third party cannot be found or is not desirable > - Validity en transparency of transactions is important > - Stored or interchanged data are very important > > > > On 13-11-17 13:02, Anastasiou A. wrote: > >> Perhaps an optional Blockchain capability could be added in the service >> model, at points where an >> "internal" system had to interface with one or more "external" systems. >> >> For example, you could provide access to a specific dataset and >> blockchain calls that >> modify its state. >> >> This would then also require the extension of the service model for >> verifying certain actions >> against the blockchain. >> >> Within the RM, there is the Feeder System Audit ( >> http://www.openehr.org/releases/RM/latest/docs/common/ >> common.html#_feeder_system_audit) >> >> It's a new concept, still needs use cases about it I think. >> >> All the best >> Athanasios Anastasiou >> >> >> >> >> >> >> >> -----Original Message----- >> From: openEHR-technical [mailto:openehr-technical-boun >> [email protected]] On Behalf Of Bert Verhees >> Sent: 13 November 2017 11:47 >> To: For openEHR technical discussions >> Subject: Blockchain >> >> How are the plans about blockchain for OpenEhr? Is there any plan to >> incorporate it in the standard, or is it regarded as a technical >> implementers business? >> >> Bert >> >> >> _______________________________________________ >> 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 > -- [image: VeraTech for Health SL] <https://htmlsig.com/t/000001C268PZ> [image: Twitter] <https://htmlsig.com/t/000001C47QQH> [image: LinkedIn] <https://htmlsig.com/t/000001C4DPJG> [image: Maps] <https://htmlsig.com/t/000001BZTWS7> Diego Boscá Tomás / Senior developer [email protected] [email protected] VeraTech for Health SL +34 961071863 <+34%20961%2007%2018%2063> / +34 627015023 <+34%20627%2001%2050%2023> www.veratech.es Su dirección de correo electrónico junto a sus datos personales forman parte de un fichero titularidad de VeraTech for Health SL (CIF B98309511) cuya finalidad es la de mantener el contacto con usted. Conforme a La Ley Orgánica 15/1999, usted puede ejercitar sus derechos de acceso, rectificación, cancelación y, en su caso oposición, enviando una solicitud por escrito a [email protected].
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
