- DG-BSC - mailman.kantarainitiative.org

Fwd: Here's the Norton Rose White Paper
by Eve Maler 17 Jan '17

17 Jan '17

Susan told me it was okay to forward these -- sorry I took so long to do so! *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl ---------- Forwarded message ---------- From: Susan Joseph <susan.joseph1786(a)gmail.com> Date: Tue, Jan 10, 2017 at 8:39 AM Subject: Here's the Norton Rose White Paper To: Eve Maler <eve.maler(a)forgerock.com> Eve, Here's the R3/Norton Rose Smart Contracts White Paper. And if you have not read their prior white paper on Smart Contracts, here is that one as well. Susan

1 0

Info about the Taqanu use case
by Eve Maler 15 Jan '17

15 Jan '17

Thanks to Colin's outreach, Balázs Némethi of Taqanu responded with enthusiasm to my request for a use case writeup. His brief one-pager response to the questionnaire is attached. I suggested that he's welcome to provide additional links, diagrams, etc. to ensure we get the detailed picture -- we just can't publish a 10- or 20-page writeup... If you have questions, please send 'em in in this thread, and we can collect them and share them along. *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl

1 0

Notes from BSC telecon Thursday, January 12
by Eve Maler 12 Jan '17

12 Jan '17

http://kantarainitiative.org/confluence/display/BSC/2017-01+%28January+2017… Agenda: - Report <https://docs.google.com/document/d/1HOVJ3lKqOIjwCqPt5jFxfLr7wEoJ0ZVNbMGsdsW…> work Attending: Eve, Thomas, Kathleen, Devon, Adrian, Colin, JohnW The current exercise is to rationalize the entire ToC and outline. Devon has moved over all the text from the old report – thank you, Devon! We started discussing Verifiable Claims again; Adrian has gotten some more information about the role of Linked Data as a differentiator vs. JWT. Devon and Kathleen are working on OPAL/Enigma content. Kathleen has gotten the okay to bring on HL7 work around creating trust contracts on the fly for, e.g., a research repository controller and a researcher (or anyone) comes with a "safe query" (for differential privacy). Devon offers to fill in the Legal Contracts section. Excellent! AIs for Tuesday's meeting: - Eve: Write UMA and Sovrin section - Devon: Write Legal Contracts section - Kathleen: Work on HL7 subsection - Kathleen: Expand JohnW's use case section - JohnW: Continue working on his technology/technique sections - Eve: (stretch goal) Revise Intro We agreed it's a good idea for us to have our own Skype chat room and not barge in on UMA chat room, so if anyone has a Skype handle that Eve ("xmlgrrl") doesn't know about, please feel free to send an invite to her. *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl

1 0

Notes from BSC telecon Tuesday, January 10
by Eve Maler 10 Jan '17

10 Jan '17

http://kantarainitiative.org/confluence/display/BSC/2017-01+%28January+2017… Agenda: - Report <https://docs.google.com/document/d/1HOVJ3lKqOIjwCqPt5jFxfLr7wEoJ0ZVNbMGsdsW…> work Attending: Eve, Adrian, Matisse, Thomas, Susan, JohnW Eve gave an update on the efforts to move to the new report doc. Devon is helping Thomas and Eve with some key overall editing tasks. Adrian described the value proposition of Verifiable Claims: It "kills the need for federation" because, in a triple-blind manner, the RP can verify a claim directly from the issuer. Thomas's and Eve's analysis didn't find this to be true in any special way; the technology looks extremely similar to JWTs, for example, and the notion of an RP is a federation notion and requires trust to be established somehow. Adrian will review, discuss with Manu (the draft spec author), and get back to the group. Thomas has filled out the OPAL/Enigma section; no analysis section yet. What's the best way to drive to consensus on the analysis of each section? Thomas, Eve, and Devon will continue editing, and will draw the DG's attention to new sections for timely review. Scheduled meetings will focus on analysis and review. *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl

1 0

Timely perspective on our eRx Use Case
by Adrian Gropper 05 Jan '17

05 Jan '17

http://www.healthitoutcomes.com/doc/the-e-prescribing-evolution-today-s-ben… Note that the author ignores the patient perspective, and imagines there will be a source for the decision support information that combines genomic and financial data with the health record. -- Adrian

1 0

Notes from BSC telecon Tuesday, January 3
by Eve Maler 04 Jan '17

04 Jan '17

http://kantarainitiative.org/confluence/display/BSC/2017-01+%28January+2017… Agenda: - Report <https://docs.google.com/document/d/1HOVJ3lKqOIjwCqPt5jFxfLr7wEoJ0ZVNbMGsdsW…> work Attending: Eve, Thomas, Kathleen, Matisse, Thorsten, Adrian, Susan, Devon (finishing law school, studying data privacy), SteveO, JohnW Our DG's life is extended just for this next month. Kathleen points to the 21st Century Cures Act (house bill link <http://docs.house.gov/billsthisweek/20161128/CPRT-114-HPRT-RU00-SAHR34.pdf>). It calls for a trust framework. Adrian notes that it mentions longitudinal health records, which is a novel challenge in the patient context vs. clinical research (subjects). See his blog post <http://thehealthcareblog.com/blog/2016/12/16/making-the-physician-patient-r…> . To pick a fintech use case, can we find one with an individual perspective vs. an institutional perspective? Can we pick one from Sedona <https://thesedonaconference.org/> that has the right characteristics? Susan notes that Everledger is working to ensure that the ethical diamond use case is protecting workers etc., not just tracking the diamonds. What about BanQu <http://www.banquapp.com/> ("Dignity Through Identity") as a financial use case for empowerment? Susan has talked to the principal. *AI:* Eve to send the questionnaire to Susan for sharing with the BanQu person and to Adrian for sharing with the Consensys people. *AI:* Thomas: Fill out the questionnaire for Enigma/Opal. *AI:* Adrian: Fill out the questionnaire for his use case (and/or write the full use case! ). *AI:* Eve: Flesh out report outline (hopefully together with Thomas), completing AIs in report comments, before our Thursday meeting. *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl

2 4

Sedona EHR Use Case fails in terms of how individuals interact more equitably and efficiently
by Adrian Gropper 03 Jan '17

03 Jan '17

https://s3.amazonaws.com/IGG/EHR.pdf When the individuals involved are a licensed professional and a patient, the Logical Model (p62) makes almost no sense at all. The EHR could be compiled from source and patient owned as long as: (1) the licensed professional's claims can be verified by the patient against their issuers (2) the licensed professional can put a digital signature on a detailed log entry created by the EHR (3) the timestamped hash of the log entry can be put on a distributed public ledger (4) the licensed professional may keep a copy of their log entry and the timestamp proof in case of dispute where the patient "loses" their copy. An effective individual-centric solution depends on substitutability and therefore standards. There are standards being worked on for many of these steps: (1) W3C Verifiable Claims https://www.w3.org/2017/vc/charter (2) Rebooting Web of Trust Decentralized Identifier (DID <https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2016/blob/…>) is being implemented by 4 separate groups (3) Chainpoint http://www.chainpoint.org/ and Open Timestamps <https://petertodd.org/2016/opentimestamps-announcement> are being combined in Rebooting Web of Trust (4) is just a personal data store like Dropbox The HIE of One Use Case and reference implementation http://hieofone.org/ is in the process of implementing this whole stack. (a) The patient-controlled EHR is done. (b) The patient-controlled controller of the EHR and other resources is a personal UMA AS and is done. (c) The physician's DID and secure signature are initially demonstrated using uPort <https://www.youtube.com/watch?v=FNlAkGauIdw&list=PLn9P7BiqUmmjk09q4I57cvPwy…> and being upgraded and integrated. (d) Verifiable Claims is not yet implemented. The Use Case paper <https://www.healthit.gov/sites/default/files/7-29-poweringthephysician-pati…> won an ONC Blockchain Health prize. (e) Timestamps of the physician's interaction with the EHR are not yet implemented. I believe this shows a licensed individual writing a prescription or curating a patient-centered longitudinal health record in the absence of any particular federation or trust framework. Adrian -- Adrian Gropper MD

1 0

Reminder: BSC telecon series starts up again tomorrow (Tuesday)
by Eve Maler 02 Jan '17

02 Jan '17

Happy 2017, all! Our focus is completing the report, so please consider these to be working sessions, with Thomas and me wielding the main pen. Especially if you have a writing assignment, please come prepared and try to review the link and last set of notes I sent out. Eve (from my iPad)

1 0

Book Review
by John Wunderlich 02 Jan '17

02 Jan '17

For your holiday reading pleasure. This might be of interest to the Legal UMA group and some on the BSC DG. It's a review <http://www.rogerwhitson.net/?p=3501>of Benjamin Bratton’s The Stack: On Software and Sovereignty <https://www.amazon.ca/Stack-Software-Sovereignty-Studies-ebook/dp/B01D1Q44HE> John Wunderlich, BA, MBA IAPP Fellow of Information Privacy CISA, CIPM, CIPP/C, PbD Ambassador @PrivacyCDN <https://twitter.com/PrivacyCDN> & Privacist -- 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.

2 1

Results from this week's editing sessions
by Eve Maler 22 Dec '16

22 Dec '16

Thomas and I want to thank Kathleen for joining today's editing session. We have been working in a *new GDoc version of the report* because of problems with the Confluence wiki version; that's probably better all around anyway. You can find that version *here* <https://docs.google.com/document/d/1HOVJ3lKqOIjwCqPt5jFxfLr7wEoJ0ZVNbMGsdsW…>. This should give you view access; those with writing assignments can request edit access. Our current plan is to extend our meeting schedule (which nominally should have ended on January 5, six months to the day after our first meeting) by a month so that we can press ahead and complete our report. If you're so inclined, *please take a look at the draft report* -- particularly the outline, which is what we concentrated on during this week -- in preparation for our *Tuesday, January 3* meeting. We wish you all *happy holidays and a wonderful new year*! Your co-chairs :-) *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl

1 0