identifying the patient that is the subject of the data,
identifying the user requesting patient data,
recording and auditing the authorization to release the patient data,
establishing the authenticity of the data that is being released,
paying for the service that delivered the patient data,
controlling and auditing that the shared data was used as expected.
Many blockchains and standards
Yes, a great chart by Bart. Most applications get kicked out of the blockchain sphere on:Both are directly affected by identity. As I understand it, identity management, GDPR etc. have the goal of making the answers be "no" and "yes" as often as possible.
- the second condition - "does it require shared write access," which will ordinarily be no, or
- on the third condition "are writers known and trusted," which will ordinarily be yes.
--On Fri, Sep 30, 2016 at 11:37 AM, Eve Maler <eve.maler@forgerock.com> wrote:This is extremely good -- and it's written by Bart S, before his exit from Philips Blockchain Lab. Interesting. (BTW, I've used that "Dilbert" before, but it's actually fake...)The lower part of the flowchart is, as yet, unproven, and that's what we're unpacking:
- Do you need to control functionality? Does he mean "Do individuals need greater control in the transaction?" or something similar? And if so, what if you're trying to solve for that simultaneously with a business model in which it makes most sense for "writers to be known and trusted" a la my ATM example yesterday?
- Do you want transactions to be private or public? There's a big logic leap here, since there are only two choices and they both lead to some sort of blockchain. :-)
Eve Maler
ForgeRock Office of the CTO | VP Innovation & Emerging Technology
Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl
ForgeRock Summits and UnSummits are coming to London and Paris!On Fri, Sep 30, 2016 at 7:57 AM, John Wunderlich <john@wunderlich.ca> wrote:This is the posting that contains a"Do you even need a blockchain" flowchart that fits into discussions of scope etc.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.
_______________________________________________
DG-BSC mailing list
DG-BSC@kantarainitiative.org
http://kantarainitiative.org/mailman/listinfo/dg-bsc
_______________________________________________
DG-BSC mailing list
DG-BSC@kantarainitiative.org
http://kantarainitiative.org/mailman/listinfo/dg-bsc
@commonaccord
_______________________________________________
DG-BSC mailing list
DG-BSC@kantarainitiative.org
http://kantarainitiative.org/mailman/listinfo/dg-bsc