If someone is literally dying in your duty of care because noone can access any patient records, that sounds tortuous to me. A bit like the Stanford prison experiment, but replace the guards with IT contractors, and the prisoners with surgeons, doctors, and nurses.
And the person responsible is not the guy without password, bit a coward who didn't push for 5x 9 SLA.
Yes, this includes hard real life access time analysis. If failing to remember a silly password takes longer than k minutes, it should be a breach of contract. Likewise if total disruption due to password changes is too high.
It's silly to implement a horde of govt rules while neglecting the basics.
Doctors, particularly trauma and tumor surgeons, have dying patients all the time.
Often there are additional treatments available but for resource constraints. Ordinary folk die of heart disease every day, but somehow Dick Cheney lives on with an artificial heart.
I know being a doctor can be quite a stressful job and requires a certain class of personality. But still it has gone with the territory of being a doctor since the beginning of civilization.
Well perhaps that is true, but having someone who is dieing because the surgery is failing is a bit different than someone who's dieing because you can't remember some login's passcode.
And of course then these delays compound over time and adversely affect the entire system.
Designing good software which meets government legalese constraints (which are guaranteeedly absurd in certain instances, in wording, and nature (while others will make perfect sense and still be just as hard to implement)) in extremely complex situations (health care systems with millions of users with an outstanding number of providers of different sizes, with different conditions, and medications, and the stringency of the privacy requirements).
That's tough.
It'll be really neat to see the progression of software through time. It'll be neat if what we see today is the Model T to the Tesla (X?) of tomorrow (+~110 Years).
