On 13-11-17 13:23, Diego Boscá wrote:
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

Depends on how you define trusted.
First of course there are the rights from the other to send/receive information, second is the transparency, a patient must be able to know who has received his data and which data. Blockchain can help in legal proceedings afterwards to proof why and when and how someone or some instance received information.

I think this will be very important in the near future when there will be more and more data-exchange. Not all countries have their healthcare governed in a single organization, but have many healthcare organizations, which can work together on curing a single patient.

Someone I know has now a medical problem with one of her legs. She is receiving healthcare from five parties, just to work on that problem: a specialist, the GP, a physiotherapist, a special shoemaker and the employer which needs to arrange special working place. That is the reality today, this will become more and more soon.

Bert



2017-11-13 13:17 GMT+01:00 Bert Verhees <[email protected] <mailto:[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
    
<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
        
<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:[email protected]
        <mailto:[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]
        <mailto:[email protected]>
        
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
        
<http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org>




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




--

VeraTech for Health SL <https://htmlsig.com/t/000001C268PZ>

Twitter <https://htmlsig.com/t/000001C47QQH>LinkedIn <https://htmlsig.com/t/000001C4DPJG>Maps <https://htmlsig.com/t/000001BZTWS7>

Diego Boscá Tomás / Senior developer
[email protected]<mailto:[email protected]>
[email protected] <mailto:[email protected]>

VeraTech for Health SL
+34 961071863 <tel:+34%20961%2007%2018%2063> / +34 627015023 <tel:+34%20627%2001%2050%2023>
www.veratech.es <http://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] <mailto:[email protected]>.



_______________________________________________
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