>>>Immutable here means no in-place update, you have to update using an "errata" record.
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?
Make up your mind. First, you said these properties were useless, now you're saying these properties have been in use for a long time using relational database, which means they're really useful.
>> Do you really want multiple copies of your personal medical records on some public blockchain?
No I don't. This thread's starter and I never said that these properties can only provided by "blockchain", neither did we said that "blockchain" should be used. We only said that these properties were useful and people wanted them.
>> 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?
For example, a fraudulent specialist with access to your data can modify your prescription so they can steal money from your insurance provider and also take these extra medicine to sell on the black market.
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.