“There’s great excitement and huge investment around what blockchain technology can do to improve the delivery of health care…” BUT “…not everyone is equally optimistic that this technology is more than a passing fad”
My concern goes to Gartner Hype Cycle conflation. Crypto financial transactions need, minimally, only four data elements, short and sweet:
(And, of course, implicit in the foregoing are the (often pseudonymous) “Private Key” ID linkages to the transactors’ “Public Keys” that are used to validate the transaction, reflected via the DateTimeStamp. (Oh, and, gotta mention the “security hash” code linking the blocks.)
- The typical ambulatory EHR houses between 3,500 and 4,000 variables in its RDBMS schema (to say nothing of huge inpatient systems). A typical patient encounter may reflect hundreds of them (or more, comprising both structured alphanumeric data, imaging, and open-ended text narratives). There were 60 vars in my most recent bloodwork alone. A typical “ROS” (Review of Systems data) houses 140 or so variables. And, all of these are typically “1 to n,” i.e. one-to-many longitudinal per patient (i.e., “progress note” stuff);
- Given that the ostensible “virtue” of the blockchaining architecture is its “immutability” (i.e., validated blocks cannot be modified once added), how do we handle the inevitable errors that plague all database systems? Find mistake(s)/omission(s), have to “append” execute a new block transaction (which is again “distributed” to everyone in the aggregate “ledger”/”wallet” population)?
- HIPAA 45.CFR.164.3,4,5 et seq data security, breach notification, and privacy requirements governing CE’s and their BA transactors (and also 42.CFR.2)?
- What of the continuing (lack of) “interoperability” problem (which I often irascibly refer to as “interoperababble”)? What of the clinical workflow implications? Clinicians are already drowning in data as they traverse the never-ending “productivity treadmill.”. How will the data variables in the validated new ‘blocks” be viewed by recipients? Will we need new, custom “download APIs?”
- Blockchain transactions are not “free,” they require payment of “transaction fees.” Crypto transaction fees have been on a steady, significant rise. Will they be reasonable (and stable) for health data transactions? Will such fees be bandwidth-consumption based?
Dunno. I have concerns. More inefficient IT Geek playground stuff w/respect to Health IT?