Releasing the source code would actually made it worse for the compatibles - in order to prevent infringement, the clones had to reverse engineer the BIOS in a clean room fashion, so no looking at the source code at all.
But I've gotten 6 or 7 MBps downloads. I'm not that concerned about uploads though I haven't had a problem with them.
Just like open source developers.
Because they're afraid they might sustain injury by cow (other) and need treatment.
Think of makers more as open source software developers - it'll scratch the itch they have. It may or may not be suitable for someone outside the community, and it would be a lot of work to make use of it. Doesn't make it bad, just different.
Know, ask, or was able to find out? In some cases the doctor will pre-approve you for a procedure. In doing to, they should be sending what will be happening and what they will bill for.
That sounds more like a problem with the insurance company than the medical provider. I have a high-deductible insurance and I've been notified well in advance of the amount they covered and the amount that I'm responsible for (which itself may be different than what the original bill amount was). Looking at a cough may be a simple transaction, but if it turns out the person has lung cancer the ICD-10 codes will start piling up. By describing procedures in a consistent way you can ensure that billing is actually more open, since you can go to various providers and say "how much for a V97.33XD?" and get an answer back on what they'd bill.
It's not easy now, and ICD-10 was only recently implemented in a lot of places (despite being out for 20 years), but it should make things easier over time.
So how does a makerspace address this? Don't get me wrong, I like going to the one near me as I help them with Linux and they help me with electronics, but they don't have Solidworks installed to do the simulations described up top.
I gave an example and backed it up with my personal experience with the caveat that this is about EMRs and not wait times, which an EMR can't really help much with. I'm not seeing much in the way of examples to counter the statements I made.
IOW "Government did it, government can't do anything right, therefore I don't like it" - I find that attitude disappointing and shortsighted as well.
EMRs are dangerous in the hands of lazy doctors,
I'll grant you that. I think you'll see that over time doctors get better at it especially as older doctors retire and newer ones take their place. My daughter's pediatrician walks around with a tablet PC that he drops the information into and has already recorded things like the pharmacy we go to. "Still go to the CVS on Boston Road? Ok, it'll be ready when you get there"
and having seen most of the programs available and their output, a lot of it is because of lazy programming that makes simple tasks difficult.
That's just bad design. When I worked at the VA there was a good bit of discussion between developers and the people that actually used the software. Granted, this was 1993ish so they were all text-based, but there were a number of things that developers put in to make it easier for users to enter the data they had to. Don't know how that's changed in the past 20 years, probably for the worse.
That's an ICD-10 code, and the Feds don't generate them, WHO does.
If anything, codes like that standardize care, reporting, and billing. This way, two systems that are otherwise incompatible can have the following conversation:
What was the cause of injury? Sucked into an airplane engine
What treatment did the patient receive? (insert set of ICD codes for treatment)
Insurance company pays rates based off the ICD codes, done.
There's 68,000+ codes in ICD-10. There's going to be a few odd ones in there.
Nice. I worked for the VA for a few years in the early 90s, which is why I know at least how they operate. I think the bigger issue in the future is going to be translating records between institutions, just like the DoD and VA can't easily move records. When each system grows organically over time and doesn't think it'll need to communicate with others, it creates a huge problem when you do.
From an EMR standpoint? I find that attitude disappointing and shortsighted.
Intel CPUs are not defective, they just act that way. -- Henry Spencer
