each doctors surgury strand of chain. hass a block or UTXO header that gets added to a master chain. and so the network is not validating what the clear text says. but validating the hashes add up.
and its the doctors and patients in their smaller subchains that validate that personal stuff
ok, but the real question is WHY?!!!
it is not about how it is done it is about whether doing it that way is better than how we are currently doing things.
imagine each doctors clinic/surgery have a little black memorystick that is plugged into a electric wall socket with a usb outlet
that memory stick. is the node. now realise each doctors clinic/surgery has one.
now the health care system can sack all the auditors and data security guys. and just get a janitor replace a memory stick if one develops a fault.
letting doctors be doctors and let more of the treasury funds be used for healthcare instead of administration
walk into any doctors clinic and ull see less non-medical staff shuffling papers.
less surgery/clinic managers fiddling with numbers so they can vacation 48 weeks a year at others expense
...
now with all that said there are many places where blockchains are useless, but when there is a scenario that data needs to be in more than one location and edit/append data to it from more than one location. then there can be some advantages.
the more wider field of multiple locations and multiple entities needing more than just viewing privileges. the more a blockchain can be seen as beneficial.
that doesn't exactly answer my question though. it only talks about how the blockchain technology is going to used in this particular case.
my question is basically why would you use it instead of regular methods. you mentioned less paperwork and less staff. ok, lets make it digital with a database and a server. but that doesn't still have to be a blockchain.