Earlier quoted context omitted.
>"immutable, distributed, cryptographically-verified database" >Byzantine fault tolerance, public consensus, and mining Why would I want ANY of these things associated with the system that manages my medical records? I don't want them to be immutable, if there's an error I want it corrected. Clearly there should be security to control who (my provider) can update them, and perhaps turn on the database transaction log…
>> I don't want them to be immutable, if there's an error I want it corrected. Immutable here means no in-place update, you have to update using an "errata" record. This is the requirement for many type of official documents, even before computers were used. >> I don't want my medical records to be distributed for obvious reasons. Distributed here means no single point of failure. >> Encrypted, sure, but "cryptograph…
Yes, and people have been building financial systems with relational databases using this journaling principle (updates and deletes handled by inserting new records and timestamping) for decades.
>>>Distributed here means no single point of failure.
Which can be done with most standard RDBMS or NoSQL databases and clustering/sharding. Not that the scale of medical records is anywhere near requiring any of this. Do you really want multiple copies of your personal medical records on some public blockchain?
>>>Encryption without authentication opens up many types of attack. You almost always want authenticated encryption
For financial transactions, sure, but for medical records? For what purpose? Other than me and my provider (and any specialist I select) why would anyone else even need to access my medical records? Who would be faking them?
None of this makes any sense for medical records.