2017-01 (January 2017) Meetings
...
Agenda:
- Report work
Attending: JeffS, Thomas, Kathleen, Devon,
Kathleen: looking for definitions of "Provenance" (from Jim/Thomas). Thomas: we never did define "provenance". There is also "proof of existence" - example from JMoehrke where people wish to show they have an idea (i.e. patent) without revealing.
Thomas: how is this done today? Kathleen/Devon: example of sending a closed envelope to yourself, timestamped by the US Post Office. Thomas: can also go to a notary.
Jeff: blockchain already exists globally, so easier to use as notary.
Kathleen: new use case. New President wants services to be given to citizens only. So you could use something like blockchain.
Report status. Kathleen already written HL7. Devon working on the legal contracts. Thomas: Rose/Fullbrighrt report. Devon has read both.
Thomas: R3 is working on methods/avenues for dispute resolution. Devon: contracts have to indicate which jurisdiction it applies in, and location of dispute res.
Kathleen: possibility in future to have a court where parties need to escrow funding for post-transaction disputes.
Tuesday, January 24
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:
...