Not quite 30 years....HL7 has only been around for 22 years or so...I remember the 20th anniversary happening. But there are working interfaces that appear not to have changed for at least fifteen years. They've been doing this stuff before you young whippersnappers could spell "ex em el"....besides, it's not "transferability", the correct word is "interoperability"... now get off my lawn.
This is total nonsense. HE did the crime. HE should pay for his defense. If he is not in a position to do that, he can either pass around a hat or cop a plea like everyone else does. The idea that taxpayers should pay for his every want and need while he engages in a protracted legal battle is rubbish.
Unix was full of cryptic shorthand commands. Ie, "help" vs "man -k", "search" vs "grep", "edit" vs "vi" or "ed" or "ex", etc.
I worked on multics systems for a few years back in the 80s. I loved the logical command names in multics. I hate the baby-talk nonsense that passes for command names in eunuchs. And the eunuchs think that they are *so cool* because they can use "grep" and "awk" like they are real words. If I want to display the contents of a file on a multics terminal, I type "show_file baz.foo" or "sf baz.foo". Even the abbreviations for commands make sense. Why the eunuchs think that the command "cat baz.foo" makes sense to perform this same function is something that I never got.
Get off my lawn!
It should be a common sense thing....... the problem is that "common sense" is all too rare. If we could rely on common sense, we wouldn't have to remind people that coffee is hot.
No. You should hire a timpanist to follow you around and play when you want the sound. Don't be using technology to put a starving musician out of work:-)
Ford has tried to sell its eurocars in the US, and folks would not buy them. They sold the Mondeo (and the Mistake...er Mystique, the Mercury badged version) for a while, but there were not that many buyers for a model between the Escort and the Taurus. I don't think they every sold the Ka over here, but I do remember seeing a few on the roads around Dearborn (Ford's HQ) and they looked to be positively suicidal sharing the roads with Excursions and Expeditions.
Just because the Euros will buy something does not mean that Americans will. One size does not fit all.
I was wondering who the US National Highway Safety Administration was, but when I RTFA, I realized that the agency the did the work was the US National Highway Traffic Safety Administration, better known as NHTSA. I'd actually heard of them:-)
I primarily blame the ridiculous concept we have that our employers should pay for our health insurance.
The reason that employers pay for health insurance in the US is that wages were frozen during WWII, and when companies needed to compete for scarce labor, they did so by offering benefits, like healthcare.
Who would you have pay for your health insurance?
I think what it really means is probably some funding for academic programs that examine the fusion of medical training for IT people and vice versa.. like, maybe you could be a programmer with a specialty in medicine such that you aren't a doctor per se, but you know enough about how medical information is organized so that you can represent things.
There are a number of Medical Informatics programs out there that are doing this today. The program that I am in includes clinicians who learn a bit about information technology, and IT folks like me who get to learn a bit about how medicine works. The dynamics of group projects in this setting are quite a learning experience.
Maybe an understanding of the roles of the organizations would help. They do not compete with each other. NeHC publishes a number of "value cases" each year (think of these as use cases). HITSP finds the appropriate standards and specs for meeting those use cases. CCHIT certifies that products perform as expected in various care settings. HL7 is an international SDO, so their standards are intended to work outside of the US. HITSP publishes IGs that are constrained versions of the standards that will meet the use cases that NeHC publishes. So, NeHC sets the priorities. HITSP publishes specs based on the available standards. CCHIT uses those as the basis for product certification. The problem is too big for a single, centralized ministry to manage effectively.
Simply installing technology isn't the fix (I know...this is slashdot, and that statement is bad). The workflow changes that take advantage of the new technology is where the big problems are. a significant portion of EHR implementations that fail do so because they overlooked workflow or training (or both).
There is a great deal of work being done on this. NeHC, HITSP, CCHIT and HL7 are some of the organizations involved. HL7 has a Functional Model for EHR Systems that CCHIT uses to certify products in various care settings. HITSP selects the standards to be used in interoperable exchange of data between EHRs.
The stimulus package will reimburse docs and hospitals that can demonstrate "meaningful use" of HIT. They haven't defined that yet, but it will probably include ePrescribing, participating in a Health Information Exchange (HIE) and reporting quality metrics to the feds.
There are a lot of smart, well intentioned people working hard to make this happen.
"We are declaring today a public health emergency," Secretary of Homeland Security Janet Napolitano said today...
What will she declare tomorrow to be?
Slashdot Mirror
You mean it can go lower than zero? Who new.
The funding for the laptops came from a government grant. So, US Taxpayers paid for the laptops...
Not quite 30 years....HL7 has only been around for 22 years or so...I remember the 20th anniversary happening. But there are working interfaces that appear not to have changed for at least fifteen years. They've been doing this stuff before you young whippersnappers could spell "ex em el"....besides, it's not "transferability", the correct word is "interoperability" ... now get off my lawn.
This is total nonsense. HE did the crime. HE should pay for his defense. If he is not in a position to do that, he can either pass around a hat or cop a plea like everyone else does. The idea that taxpayers should pay for his every want and need while he engages in a protracted legal battle is rubbish.
Unix was full of cryptic shorthand commands. Ie, "help" vs "man -k", "search" vs "grep", "edit" vs "vi" or "ed" or "ex", etc.
I worked on multics systems for a few years back in the 80s. I loved the logical command names in multics. I hate the baby-talk nonsense that passes for command names in eunuchs. And the eunuchs think that they are *so cool* because they can use "grep" and "awk" like they are real words. If I want to display the contents of a file on a multics terminal, I type "show_file baz.foo" or "sf baz.foo". Even the abbreviations for commands make sense. Why the eunuchs think that the command "cat baz.foo" makes sense to perform this same function is something that I never got. Get off my lawn!
... and it will probably be 450k new union members, paying dues and voting for democrats.
What makes you so certain that the TSA won't have checkpoints at these train stations by the time that this gets built?
It should be a common sense thing ....... the problem is that "common sense" is all too rare. If we could rely on common sense, we wouldn't have to remind people that coffee is hot.
No. You should hire a timpanist to follow you around and play when you want the sound. Don't be using technology to put a starving musician out of work :-)
Ford has tried to sell its eurocars in the US, and folks would not buy them. They sold the Mondeo (and the Mistake...er Mystique, the Mercury badged version) for a while, but there were not that many buyers for a model between the Escort and the Taurus. I don't think they every sold the Ka over here, but I do remember seeing a few on the roads around Dearborn (Ford's HQ) and they looked to be positively suicidal sharing the roads with Excursions and Expeditions. Just because the Euros will buy something does not mean that Americans will. One size does not fit all.
I was wondering who the US National Highway Safety Administration was, but when I RTFA, I realized that the agency the did the work was the US National Highway Traffic Safety Administration, better known as NHTSA. I'd actually heard of them :-)
I primarily blame the ridiculous concept we have that our employers should pay for our health insurance.
The reason that employers pay for health insurance in the US is that wages were frozen during WWII, and when companies needed to compete for scarce labor, they did so by offering benefits, like healthcare. Who would you have pay for your health insurance?
I think what it really means is probably some funding for academic programs that examine the fusion of medical training for IT people and vice versa.. like, maybe you could be a programmer with a specialty in medicine such that you aren't a doctor per se, but you know enough about how medical information is organized so that you can represent things.
There are a number of Medical Informatics programs out there that are doing this today. The program that I am in includes clinicians who learn a bit about information technology, and IT folks like me who get to learn a bit about how medicine works. The dynamics of group projects in this setting are quite a learning experience.
Maybe an understanding of the roles of the organizations would help. They do not compete with each other. NeHC publishes a number of "value cases" each year (think of these as use cases). HITSP finds the appropriate standards and specs for meeting those use cases. CCHIT certifies that products perform as expected in various care settings. HL7 is an international SDO, so their standards are intended to work outside of the US. HITSP publishes IGs that are constrained versions of the standards that will meet the use cases that NeHC publishes. So, NeHC sets the priorities. HITSP publishes specs based on the available standards. CCHIT uses those as the basis for product certification. The problem is too big for a single, centralized ministry to manage effectively.
Simply installing technology isn't the fix (I know...this is slashdot, and that statement is bad). The workflow changes that take advantage of the new technology is where the big problems are. a significant portion of EHR implementations that fail do so because they overlooked workflow or training (or both).
There is a great deal of work being done on this. NeHC, HITSP, CCHIT and HL7 are some of the organizations involved. HL7 has a Functional Model for EHR Systems that CCHIT uses to certify products in various care settings. HITSP selects the standards to be used in interoperable exchange of data between EHRs. The stimulus package will reimburse docs and hospitals that can demonstrate "meaningful use" of HIT. They haven't defined that yet, but it will probably include ePrescribing, participating in a Health Information Exchange (HIE) and reporting quality metrics to the feds. There are a lot of smart, well intentioned people working hard to make this happen.
"We are declaring today a public health emergency," Secretary of Homeland Security Janet Napolitano said today ...
What will she declare tomorrow to be?
Try this link. It tracks news stories about infections from various sources. http://www.healthmap.org/en