2017-01 (January 2017) Meetings

...

Thursday, January 19

Agenda:

• Report work

Attending: Eve, Devon, JohnW, Adrian, Colin L.

We discussed the CommonAccord section in the report. John created a diagram (file name "BSC DG Decision-Making Power 2017-01-19.png" on Eve's computer) to describe the opportunity to even things up. Eve suggests creating an Observations section talking about contractual mechanisms and tensions around them, with the diagram as a centerpiece; it would pull in a lot of mentions of the tech/techs. Some Recommendations that may fall out could do with strengthening the connection between legal and smart contracts in a formal way.

We discussed the Legal Contracts section. We debated the order of tech/tech sections; it would be nice to have Smart Contracts and Legal Contracts very near each other. The notion of "fully executed legal contracts" brings them together conceptually. 

Next Tuesday: Look at Manu's answers on Verifiable Claims, and look at Eve's putative new sections, and look at the User-Submitted Terms section from JohnW.

(NOTE: Eve can't make next Thursday's call because she'll be doing a Data Privacy Day event in SF, and hopes Thomas can run it.)

Tuesday, January 17

Agenda:

...

Hence seemingly a good match for our use case criteria. Colin will introduce them to Eve in email, and she'll send them the questionnaire. SecureKey has gotten investment for blockchain-based efforts, and they are on the Kantara board, so let's at least ask them for feedback on our report, if not as well contributing a use case; Colin will reach out and cc Susan (whose connection is through Mary Hodder and IDESG). Susan can also send the questionnaire to Bitpesa, and we'll see how much time we have to combine what we get.

Discussion of the prescription use case submitted by Adrian (which Eve will forward to the list, for full context): By "The current introduction of hospitals and other institutional intermediaries into the prescription order process" is meant identity management/authentication (for checking the physician's identity) and the management of EHRs (because the prescription is generated within the EHR system). There is rent-seeking by the systems that have performed this consolidation. The goal with the use case is to have the clinician use as many as three apps or more, e.g. one for login, one for proving you deserve to prescribe, one for payment, etc. The idea is that they're horizontal and you'd have way fewer in total.

Adrian has commented that the Sedona report's logical model of EHR discovery trust (p. 64 here) doesn't account for decentralization, which blockchain can enable. Sedona is an influencer on e-discovery; lawyers and Google and MSFT and others do pay attention to it.  So we may want to reflect on this in our Observations section, given that we have several use cases that have implications for health. We recognize that health data itself wouldn't be stored on a blockchain, but the generally accepted approach would be to store a transaction record stating something happened, then a later transaction record stating something else happened (or even some previous record had to be corrected), etc.

Tuesday, January 3

Agenda:

...