If you look at the healthcare space, you will realize interoperability only exists because it was mandated by government programs that the patient owns their data and must be provided timely access to all of that data; and also defines specifies the format of that data (open source definitions).
You might also define "exists" in some sort of way that makes sense. And you can also realize that payers are encroaching on every aspect of interoperability data exchange.
It was mandated because, in some cases, getting data from the patient is actually harmful. A CT scan is not benign. So to ensure that CT scans from manufacturer A could be read on a review station of manufacturer B, the DICOM standard was created.
But there is a real health element to it. Although I perfectly agree that standards are good for the consumer, the incentives here are not as strong.
I know nothing about IT project management for healthcare, but just the other day over here in the local news there was a mention that the all-singing-all-dancing healthcare application that the region (with ~1M inhabitants) has been spending years and around 800 million euros to get into production has been so poorly received that they're considering starting over from scratch. I'm so happy seeing my tax money well spent...
This is an implementation of something called MUMPS, which is apparently some US system that is very arcane but widely used.
Again, I'm not an expert on this topic, but it indeed seems like standards, API's, file formats and whatnot would be keys to a system where decoupled components can be evolved step-by-step over time instead of the current system which seems to be a humongous monolith.
I don't think this is "better" for him really. He didn't win any money afaik. He spent a lot of time defending himself against something that could have easily gone in a different direction given a different jury.
It successfully located a submerged car in a bayou. (Note, this is a known finding, and nothing reportable). So I think there are some possible positive use cases here. I'm curious what other unsolved mysteries are now solvable with computation.
In my city they synchronized the light so that each one turns red just as the pack of cars is reaching it. To be clear the obvious implication I'm making is that they did this to increase the chance someone would run the light and increase revenue.
This does mean that if you're in the front of the pack and go about 15 over the speed limit, you won't "catch" the red light.
When you're not in the front of the pack it can be frustrating trying to travel just 3 or 4 miles with the red lights not even a full half mile from each other. Even late at night if you follow the speed limit, you are penalized. You will sit at every red light and look at the vast stretch of nothingness that has the right of way.
If they didn't do this to generate red light revenue, they could have done this to generate more revenue from the gas tax they collect by making people start & stop more often, and from sitting in traffic longer. But I suppose both things could be true. And no, I won't accept any other plausible explanations (/s, but holy heck is government awful here).
I haven't run into those (I mostly drive in rural areas--in fact, there's no stoplight in my county) -- but I do run into some lights that just change in the middle of the night, for no reason, and then take a really long time to change back to green, despite not even a single car being present / going through.
reply