The appliance ships with UDP port 8812 allowed through the firewall. The port correlates to an internal service that routes messages between backend processes. To authenticate access to this service, all messages must be encrypted with a secret key [...] These two default keys are
123456789ABCDEF0123456789ABCDEF0 and 0123456789ABCDEF0123456789ABCDEF.
One of the applications that is exposed through the port 8812 message routing service executes a system command without sanitizing the arguments provided by the requesting application. This allows arbitrary commands to be executed on the appliance. Combined with Issue #1, this allows remote, unauthenticated command execution on the appliance as the
"soggycat" user, which is root equivalent
The secure shell daemon is running by default and the system is configured with static passwords for a number of root-equivalent accounts. The "soggycat" user account [...] also has two SSH keys configured for passwordless login. These keys were generated over eight years ago.
All internal services communicate through UDP services bound to the 0.0.0.0 address. This exposes the internal workings of the appliance to an attacker with network access to the system. For example, a local user account without administrative rights would still be able
to escalate privileges by communicating with these internal services.
The rsync daemon allows read/write access to the "soggycat" home directory. Since this user account is root-equivalent, any attacker than talk to the rsync daemon can take full control of the appliance.
This is amateur hour, though still better than what runs our power grid and water treatment plants.
No. They are, however, funding and marketing games, and getting them on store shelves and Steam/Origin/UPlay/et al. I assume they're doing this for the same reason Netflix is making original content--to make sure they're not dependent on third-party content to keep their shelves stocked.
I'm also guessing they don't see much of a future in retail, so they're trying to pivot into the publishing business before they die off, which is probably more profitable anyway.
Why would I care about a new distributor?
You probably don't, unless you're a game studio looking for someone to finance your next game. In that case, you probably do, especially if you're not big enough to get the time of day out of one of the AAA publishers, or if "we do not involve ourselves in the creative process" sounds appealing.
In the abstract, you should probably care a little because more publishers funding games means more games get made, and GameStop has the potential (the potential) to fill an interesting middle ground between too-big-to-fails like Call of Battlefield Eleventy and no-budget, bottom-of-the-barrel, I-compiled-this-with-two-pirated-rubber-bands-and-kickstarter "indie" games. As in, budgets small enough to be able to take interesting creative risks without worrying about a twenty-brazillion dollar screw-up tanking the company, yet not so small that you have to resort to gimmicky pixel-art shit to get a hipster/10 rating on your Steam Greenlight.
And if nothing else, it's unusual for a large company to see the writing on the wall ahead of time, and actually try to do something about it before plowing head-on into the iceberg. This is kind of a man-bites-dog moment--we're witnessing the incumbent horse-buggy manufacturer trying their hand at self-driving cars.
If MS put real effort into providing good security [...]
You're bitching about an OS with mandatory access controls, DEP, ASLR, virtualized filesystem access, application whitelists, secure boot, and that runs its own authentication daemon in a VM so that not even the kernel itself can directly manage password hashes. You're doing this bitching in an article about a tool they maintain so you can harden and sandbox third-party programs, even when those programs weren't built with stack smashing or ASLR or all those neat Visual Studio canaries in mind.
[...]it would destroy the lucrative market for anti-malware software.
They bundle anti-malware software with the OS. They're, clearly, very concerned about not destroying all that filthy McAfee lucre.
There's no proof, and the "Global Competitiveness" crap in TFA is irrelevant to the millions of Japanese SMEs, because they are not competing globally.
Japan is on the edge of a demographics crisis. 25% of their population is over 65, compared with 59% that work. Having only ~2.36 people paying into public healthcare and social insurance for each person drawing out is not a good ratio, and with their notoriously low birth rates, is only going to worsen as time goes on.
So, what does this mean? It means productivity is really fucking important. If your aging population has fewer than 2 workers to cover each retiree, those workers better be really fucking productive or those healthcare costs are going to be an incredible burden. If you need to import 94% of your energy at great expense, you better put that energy to really fucking good use--i.e., be productive--or otherwise you're spending everything on coal and petrodollars instead of your own people. If your government debt is skyrocketing, but has fewer and fewer taxpayers to pay it down, those people better be really fucking productive or you're not going to have a government.
That latter point is especially important. Japan can get away with its debt load because of Japan's famously high savings rate--lots of people (or banks using people's savings) buying savings bonds means you can issue those bonds really cheaply. But, when people retire, they by necessity stop saving and start drawing on their savings instead. The government has double their yearly income in what's essentially an adjustable-rate mortgage, and the interest rates are going to skyrocket right as fewer people are there to pay it down.
He's right though. We spend much more per person on healthcare than even the yuuros do, and we die sooner despite that (fig 1). That's not to say that our hospitals are bad (though some states really fail at not killing people), or that we aren't awesomely good at treating specific diseases, but none of that means you'll live any longer than the slackers across the pond.
Even worse, despite being a nominally private healthcare system, our government still spends more per person than even the UK (fig 3). As in, we'd have less government in medicine if we went full-retard universal care.
That's not to say I'm a fan of single payor systems--our nanny state is already trying to micromanage how many ounces are in a soda even when they're not paying for your fat ass. But, it's simply wrong to say that the single-payor systems don't provide better care for less money.
That said, I'd much rather we emulate Singapore. They make you pay for everything out of pocket from a savings account drawn off your paycheck. Paying cash for everything keeps prices in check, the mandatory contributions mean no one's "uninsured," and no insurer or HMO limits what you can buy. Subsidies help the truly indigent, and you can draw on it like a 401(k) in your dotage should you prove unusually resilient.
The Little Red Dot lets you be as much of a fat-ass as you care to pay for, and ain't that the American way. Japan, in the meanwhile, has an honest-to-God fat tax.
My parents tech support needs are very little, even without reboots and Mac Minis, and I help them readily, thankyouverymuch. That doesn't mean I need their computers to break before spending time with them, or that I wish their computers broke more often.
You raise a good point, but constantly fixing someone else's computer problems is draining, especially if the help is one-way and never reciprocated. It does nobody's relationship any good if you dread every call for the hour it's going to take to fix whatever broke.
Imagine instead if their computers actually worked, and you could therefore instead talk about whatever you wanted instead of why the printer isn't working. "Spending time with your child" is one thing, but I'm welcome to visit even when the Internet isn't broken; and, when visiting, I'd rather spend the time with them instead of their computer. Likewise, my folks are welcome to visit me even when I don't have a busted clutch slave cylinder or leaking fuel tank; and, likewise, the time is better spent on discretionary projects we want to tackle for the purposes of fun and/or bonding as opposed to helping with an emergency.
I have no idea what you can expect from big box phone support, or if "good" phone support even exists. There are a bunch of things you can do to make tech support easier, however, if you haven't done them already.
The best thing you can do (again, if you haven't already) is take away the Administrator account. I used to get weekly calls about my grandparents' PC, which saw a lot of use by relatives and grandchildren, until I did that. Suddenly, all the toolbars, viruses, Bonzi Buddies, random driver issues, and how-does-that-even-break issues just stopped. The occasional call to go type in the password and install something was much quicker than the frequent calls to uninstall something added by a well-meaning uncle or a young cousin.
Yes, some people were angry that they couldn't install things any more. But, they didn't want to take the support phone calls, so they didn't get the admin password. Everyone else was happy that the communal PC was suddenly much more likely to work when they wanted to check e-mail or play Facebook games.
Install Team Viewer. It's free for non-commercial use. When they call you with a problem, you tell them to click the big Team Viewer icon on the desktop and give you the code. Then you remote in and fix whatever broke--and the set of breakable things is much smaller on a limited account than on an admin.
If you still have issues, purchase a copy of Faronics Deep Freeze--absent a password, it prevents any changes to the file system outside of certain allowed areas, like My Documents and the rest of the user profile. When I was an IT monkey, we used this in our computer labs, and it worked great--people could install whatever they wanted, delete whatever they wanted, vandalize the Windows install in whatever way they could think of, and it'd all be gone with a reboot.
If you have more hardware issues ("the printer stopped working"), think about getting new hardware. I have a Phaser 6125N, for example, which is overkill for most anything, really, but toner lasts forever and the drivers are completely free of crapware--you just plug in an Ethernet cable and forget about it. If their printer frequently causes issues, weigh the cost of a newer, more enterprise-y printer with the time saved by not having to fuck with it every week.
Ditto for modems, routers, whatever. If you have to walk them through rebooting their router every week, weigh the cost of a more reliable router over the time saved helping them turn it off and back on again.
Finally, work on your phone support. If you ask someone if the network cable is plugged in, they'll always say "yes," especially if they're a professor too proud to crawl underneath his desk and check for a lowly IT monkey.
Instead, ask them if it's plugged in the right way, because Ethernet cables are directional, you see. Make them flip it around (which, coincidentally, verifies a solid connection at both the wall and the PC). If that fixed the issue, they'll forever believe that Ethernet cables actually are directional, but it'll save you the trip to push a cable that last 1/8" into the jack.
This is necessary because most people--even family--are loathe to actually check e.g. what color some lights are, especially if checking involves some modicum of effort. While most people won't outright lie, they'll give you whatever they think is correct, or whatever answer sounds good off the top of their head, which is especially easy to do for yes/no questions.
So, never ask "is it plugged in"--the answer's always "yes," because of COURSE they plugged it in they're not an idiot and checking is effort. Ask them to switch the cable around. Don't ask if the lights are on--ask what color they are. Don't ask them to reboot their computer--ask them if their computer makes a noise when they hold the power switch for ten seconds.
It's harder than you're probably giving it credit for, especially for miles-long freight trains, where a hill can mean one segment of the train is accelerating while another is decelerating. We're just about there, though, insofar as we have software that automatically drives throttle, brakes, and other controls. Link:
Norfolk Southern, an American rail operator, now pulls roughly one-sixth of its freight using locomotives equipped with "route optimisation" software. By crunching numbers on a train's weight distribution and a route's curves, grades and speed limits, the software, called Leader, can instruct operators on optimum accelerating and braking to minimise fuel costs. Installing the software and linking it wirelessly to back-office computers is expensive, says Coleman Lawrence, head of the company's 4,000-strong locomotive fleet. But the software cuts costs dramatically, reducing fuel consumption by about 5%. That is a big deal for a firm that spent $1.6 billion on diesel in 2012. Mr Lawrence reckons that by 2016 Norfolk Southern may be pulling half its freight with Leader-upgraded locomotives. A competing system sold by GE, Trip Optimizer, goes further and operates the throttle and brakes automatically.
The article's a bit short on details, but this is where I expect autonomous driving to take off first--long-haul trucking. Controlled-access highways present fewer complications like pedestrians, four-way stops, and the like, and I imagine automating that would take care of 80% of the driving. Even if you still needed a human driver to reel 'er in at the warehouse gates or even the city limits, it still strikes me as a huge improvement.
Laws and liability are going to be the biggest limiting factor to commercial deployment, especially if they boil down to "a human must be ready to intervene at any time," but I think there are fudges around that. You could have one human operator in a remote control center "driving" multiple trucks, kind of like a cross between drone pilot and remote ICU monitoring.
Not that even a human sitting in the seat with hands on the wheel would be likely to intervene effectively should something go wrong after eight hours of idle monotony. But, having a human somewhere supervising in some capacity would soothe the more irrational fears that also serve as part of the reason we still keep human pilots flying planes, while still yielding the benefits that come with automation--self-driving trucks are much less compelling if each one still needs a full-time human driver to comply with laws.
EHRs absolutely do do all of those things, including checking drug interactions, allergies, and pregnancy and lactation warnings, and there absolutely is scholarly evidence of their effectiveness if you care to Google. Here's one concluding barcoding and CPOE are "vital."
If your EHR doesn't do those things, then that's a defect peculiar to whatever software you're using.
The medication lists are ALWAYS wrong or misleading as they are huge and hard to read, harder to update
You think they were any shorter, easier, or more up to date on paper? A bad computer system can make med rec harder, but even a good one can't make anyone give a shit about the patient's PTA meds. Nor can a hospital losing Joint Commission accreditation, apparently.
results from another EMR is always incompatible, so you have to scan it in
Yes, that's very common. It doesn't have to be the case, but it usually is.
Have you read an EMR progress note?
Yes. I have read lots and lots of EMR progress notes. I've seen notes filled with pages of stale labs because computers make it easy to copy forward the entire chart. I've seen notes flagged by the built-in plagiarism tools because copy-pasting an old note (and getting paid when you file it!) is easier than actually rounding on the patient. I've seen SOAP notes filed with weeks-old vitals because one group of residents preferred copying things into and out of Microsoft Word, which didn't exactly have the latest telemetry. I've seen notes with assessments that weren't done, filed on patients that weren't rounded on, because easy money.
But you know what? You can read them. And so can the doctor who sees the patient after you.
Certain kinds of errors have decreased dramatically. Computers reduce wrong patient/wrong medication errors dramatically, especially in systems that require you to scan the patient's barcode (to make sure you have the right patient), and then scan each medication's barcode (to make sure you've got the right meds). There's a lot of scholarly research available if you search for EHR medication errors, but this is one of the first non-paywalled things that pops up in Google.
Other issues are more challenging. You might have grabbed the right IV bag, and the computer might have confirmed that it had the right barcode, but that alone doesn't prevent pharmacy from filling the bag with the wrong fluid in the first place, or putting the wrong barcode on the wrong bag. It also doesn't stop a harried nurse from failing to mix both diluent and active ingredient of a vaccine when filling a syringe, or from using the same insulin pen on multiple patients; nor do computers keep toddlers from digging fentanyl patches out of the trash, overdosing on painkillers, and dying.
TL;DR most kinds of medical errors are decreasing, and computers tend to help--they're good at checking meds, and good at counting how many sponges you had in the OR field before and after cutting the patient up. Others are still around--handwashing compliance can still be flakey, silk neckties encounter years of sick people yet are never laundered, and "nosocomial infections" are still troublesome. Pick your favorite kind of medical error and give it a Google for recent stats.
I hear you--even within a hospital system, and even where standards exist, it's a pain. Ultrasound machines (for those that aren't imaging informaticists) are supposed to speak DICOM, but some do it creatively--one technically sent DICOM messages over the network, but most of what they contained was wrapped inside a proprietary XML blob rather than standard DICOM fields. What standard fields were implemented were implemented strangely, waffling between spelling out measurements ("centimeters") or using their abbreviations, mixing case, and reporting measurements to absurd precision (dozens of zeroes after the decimal point, for a bone measured in millimeters).
Sharing charts between hospitals is a mire of politics. There's the government's own Direct standard, which they mandated every hospital use to send charts, without any indication of what the recipient is supposed to do--a lot pipe them to/dev/null, because the vaguely defined content of the message is often useless and redundant with existing methods of communication. They're now working on legalese to require that you "do something" with the messages you receive, but exactly what that is (and how to objectively prove that you did it) they're still figuring out.
Then there are organizations like Commonwell, trying to monetize a data-sharing "standard" not even their founding members could be bothered to implement. They haven't sent a single chart as far as I know, but that doesn't stop them from issuing press releases praising their "interoperability" with the same frequency AT&T issues press releases praising their gigabit fiber.
Then there are HISPs (centralized, sometimes quasi-public, repositories of patient information). Some have managed to legislate themselves as mandatory middlemen, and, having done so, have proceeded to extract monopoly rents over the transmission of outdated and incorrect patient information. Even better is provider look-up--if they give you the wrong fax number for a physician, you are responsible for the HIPAA violation when a random gas station gets someone's medical information. This causes them to care as much as you'd expect about the integrity of the data they peddle (and that you're required to buy).
It's frustrating, because medical information has to be shared for it to be of use--there's no use having a mammography if no one will read the results, or if the people treating you can't access the study and have to order their own.
Being licensed profession will stop clueless management from force stuff to be so easy to hack / not willing to pay the costs to have be done right.
If you're going to make it illegal for literally anyone else to write software, then maybe. I'd love to see you square your favorite licensing regime with anything resembling open source development.
You really don't. I've shilled for EHRs before, but the TL;DR is
Paper charts kill people. They don't check for drug interactions; they don't double-check that you've got the right patient when you're operating or administering medications; in the case of a recall, they can't tell you who received a bad batch of a vaccine; and they certainly can't tell a first responder that unconscious you is allergic to blue dye, unless they already happen know your regular clinic and have a fax machine in the ambulance.
Paper charts are useless for patient care. The hospitalist trying to reconcile what you were taking at home with what they want to give you in the hospital can't actually determine whether they're about to kill you if the cardiologist treating your heart attack happened to take the only copy of the chart to enter his notes. If they made a second copy for the cardiologist, there's no guarantee his notes and medications will ever get entered into the hospitalists copy, or into pharmacy's copy, who might also wonder why two different doctors plus your PCP are trying to dose you on blood thinners, or into your regular doctor's copy, who might be totally unaware of the cardiologist's findings
Paper charts are expensive. If nobody knows that you already had a lab or an X-Ray, they're going to order it again. If they do know you had one of the above, you're going to have to wait for a fax, or for them to mail negatives. Because handwriting and general disorganization, especially over a long admission, tends to make them write-only, it's much harder to know exactly what they gave you and why, which makes it harder to justify to the government or an insurance company why they should pay your tab.
That doesn't mean the electronic versions don't have terrible, even maddening, flaws, but even the worst are better than paper.
I won't disagree that medical billing is still a nightmare, but it's not the fault of CPT codes. No insurance company will sign a blank check and ask the doctor to fill in the amount; they all have a maximum they'll reimburse for, say, a broken leg, and they'll reimburse "broken leg" differently for a simple fracture than an unexpected amputation that took a crack team of surgeons 32 hours to reattach.
The codes are just a standard way to quantify exactly what was done. The "standard" part is important since most docs wouldn't be able to deal with more than a single insurance company if they all spoke a different code set. Absent a code set, it's much harder to determine how much your treatment should have when all you have are subjective descriptions from multiple doctors about what each thought they did. Codes remove that ambiguity, which insurance companies otherwise use to delay paying you and the hospital for as long as possible.
Generating the codes in the first place is complicated in the clipboard world, where a medical coder has to pore over sometimes hundreds of pages of scribbles to find out whether your vitals ever spiked into a danger zone that would have required more frequent nursing attention (at a higher cost), whether you were ever given certain kinds of medication, and, more subjectively, trying to divine what you actually had from the doctor's free-form notes, and what codes best describe that particular malady. Since this requires examining linear yards of flowsheet annotations (where an individual, critical cell might be missed) and subjective interpretation (does this description of a fracture qualify for Break-1 or Break-2?), different medical coders can end up coding the same chart differently.
Computers, in theory, can solve this. The computer knows exactly which medications you were given, how often, and at what cost. It knows exactly how often nursing took care of you, and can unambiguously determine your acuity. It knows every human in the operating theater, how long they were there, how much they cost, and every roll of gauze they used. Even free text notes are often templated, with doctors filling in blanks on standardized forms with multiple-choice answers, each of which can be unambiguously evaluated. Computers can instantly and unambiguously determine who too care of you, exactly how much it cost to take care of you, what codes best describe those services, and can communicate that information electronically to your insurers.
Where this falls down is a lot of computer systems grew organically--first a program for scheduling, then a program for billing, then a program for tracking clinical notes, then a program for monitoring vitals, etc., rather than some comprehensive monolith springing forth fully-formed right at the start. This means that to bill for a pregnancy, a medical coder might have to hunt through a dozen different systems: An ADT suite to determine where the patient was roomed and for how long, since a regular bed costs much less than intensive care. A specialty labor and delivery system, to gather the myriad of data states and to defend against lawsuits. An often separate fetal heart monitoring suite. An often separate ultrasound modality, with its own operating system that may or may not speak industry standards, that may or may not pair with a separate vendor-specific image viewer on computer workstations. A separate OR suite for doing documenting personnel, and doing counts and checks (to make sure you're billed for the roll of gauze they did use, not billed for the one they didn't, and that neither were left inside you.) A still-separate anesthesia suite, to make sure they don't gas you to death. An inpatient system for tracking medications and vitals, which may or may not be missing the medications and vitals collected by the labor and delivery suite, which may or may not have the vitals collected by the fetal heart monitor, which may or may not have the vitals collected by the OR suite for your C
Clipboards have a bunch of known deficiencies. They're effectively write-only, especially if no one else can read the doc's handwriting.
Then, they're hard to duplicate. Should you end up in the hospital (heaven forbid), hopefully you're conscious enough to explain your drug allergies to the EMT, because it'll take a while to find out which clinic you normally see and get a copy of their clipboard. Then the copy of the clinic clipboard ends up in the hospital's clipboard, but the stuff in the hospital clipboard probably won't make it back to the clinic clipboard.
There's also only one copy of the hospital clipboard, so the cardiologist treating your heart attack can't put notes in your clipboard if the hospitalist took it to figure out what meds you were (or should be) on. If they do make copies, someone has to make sure the cardiologist's annotations make it into all of them without error. Those charts then have to be stored in a giant bunker somewhere, forever.
Clipboards are also bad at medication safety. When you're giving millions of med administrations to millions of patients, eventually you end up giving the wrong drug to the wrong one. Clipboards can't verify that you nabbed the right patient or the right drug, which kills people once you scale up the mistakes that would have happened to a national level.
Even before the nurse gives the meds, a clipboard can't tell the doctor that one of the medications he's ordering will interact with the medications someone else ordered. That also kills people. If one lot of those medications was tainted and recalled, it's also really, really hard to find out who was affected if all your administrations are documented on paper.
Finally, it's really hard to bill correctly if all of your documentation is on paper. If the coder going over the clipboard misses a charge, the hospital loses out on money. If the coder invents a charge, you lose out on money. If the coder can't find whatever documentation a kafkaesque insurance company demands to justify a procedure, you both lose out on money. Also harder to reject a claim for not being written in blue pen with block caps when the claim is electronic.
There's a bunch of other ways clipboards suck, and a bunch of ways the clipboard-replacements suck, but the former tends to suck a lot more than the latter.
John Scalzi isn't selling iPhones; he's selling e-books. Those actually do earn more profit--for everyone involved--when they don't cost more than a hardcover.
Unlike price elasticity, autorectogenesis is entirely responsible for that tortured non-expression and the verbification of "pence." Idea was that there hasn't been that much shilling since before decimalization.
Exactly! Or from seeing Valve's success with their Steam sales, or Apple's success with lower iTunes prices, or from any other number of things obvious to you and I and everyone but John Scalzi.
While we believe 35% should go to the author and 35% to Hachette, the way this would actually work is that we would send 70% of the total revenue to Hachette, and they would decide how much to share with the author. We believe Hachette is sharing too small a portion with the author today, but ultimately that is not our call.
Slashdot Mirror
Holy shit, you weren't kidding. Quoting selected bugs:
This is amateur hour, though still better than what runs our power grid and water treatment plants.
Can anyone else decipher this press release?
I'll give it a shot.
Are they setting up a Steam clone?
No. They are, however, funding and marketing games, and getting them on store shelves and Steam/Origin/UPlay/et al. I assume they're doing this for the same reason Netflix is making original content--to make sure they're not dependent on third-party content to keep their shelves stocked.
I'm also guessing they don't see much of a future in retail, so they're trying to pivot into the publishing business before they die off, which is probably more profitable anyway.
Why would I care about a new distributor?
You probably don't, unless you're a game studio looking for someone to finance your next game. In that case, you probably do, especially if you're not big enough to get the time of day out of one of the AAA publishers, or if "we do not involve ourselves in the creative process" sounds appealing.
In the abstract, you should probably care a little because more publishers funding games means more games get made, and GameStop has the potential (the potential) to fill an interesting middle ground between too-big-to-fails like Call of Battlefield Eleventy and no-budget, bottom-of-the-barrel, I-compiled-this-with-two-pirated-rubber-bands-and-kickstarter "indie" games. As in, budgets small enough to be able to take interesting creative risks without worrying about a twenty-brazillion dollar screw-up tanking the company, yet not so small that you have to resort to gimmicky pixel-art shit to get a hipster/10 rating on your Steam Greenlight.
And if nothing else, it's unusual for a large company to see the writing on the wall ahead of time, and actually try to do something about it before plowing head-on into the iceberg. This is kind of a man-bites-dog moment--we're witnessing the incumbent horse-buggy manufacturer trying their hand at self-driving cars.
If MS put real effort into providing good security [...]
You're bitching about an OS with mandatory access controls, DEP, ASLR, virtualized filesystem access, application whitelists, secure boot, and that runs its own authentication daemon in a VM so that not even the kernel itself can directly manage password hashes. You're doing this bitching in an article about a tool they maintain so you can harden and sandbox third-party programs, even when those programs weren't built with stack smashing or ASLR or all those neat Visual Studio canaries in mind.
[...]it would destroy the lucrative market for anti-malware software.
They bundle anti-malware software with the OS. They're, clearly, very concerned about not destroying all that filthy McAfee lucre.
There's no proof, and the "Global Competitiveness" crap in TFA is irrelevant to the millions of Japanese SMEs, because they are not competing globally.
Japan is on the edge of a demographics crisis. 25% of their population is over 65, compared with 59% that work. Having only ~2.36 people paying into public healthcare and social insurance for each person drawing out is not a good ratio, and with their notoriously low birth rates, is only going to worsen as time goes on.
In the meanwhile, Japan's racking up shittons of debt, and has to import nearly all of their energy.
So, what does this mean? It means productivity is really fucking important. If your aging population has fewer than 2 workers to cover each retiree, those workers better be really fucking productive or those healthcare costs are going to be an incredible burden. If you need to import 94% of your energy at great expense, you better put that energy to really fucking good use--i.e., be productive--or otherwise you're spending everything on coal and petrodollars instead of your own people. If your government debt is skyrocketing, but has fewer and fewer taxpayers to pay it down, those people better be really fucking productive or you're not going to have a government.
That latter point is especially important. Japan can get away with its debt load because of Japan's famously high savings rate--lots of people (or banks using people's savings) buying savings bonds means you can issue those bonds really cheaply. But, when people retire, they by necessity stop saving and start drawing on their savings instead. The government has double their yearly income in what's essentially an adjustable-rate mortgage, and the interest rates are going to skyrocket right as fewer people are there to pay it down.
You idiots don't even know the first thing about medical bills and you think you're qualified to comment on critical public policy.
Odds are I wrote the software that gave you that bill, you insufferable mong. Your anecdote sure is compelling, though.
He's right though. We spend much more per person on healthcare than even the yuuros do, and we die sooner despite that (fig 1). That's not to say that our hospitals are bad (though some states really fail at not killing people), or that we aren't awesomely good at treating specific diseases, but none of that means you'll live any longer than the slackers across the pond.
Even worse, despite being a nominally private healthcare system, our government still spends more per person than even the UK (fig 3). As in, we'd have less government in medicine if we went full-retard universal care.
That's not to say I'm a fan of single payor systems--our nanny state is already trying to micromanage how many ounces are in a soda even when they're not paying for your fat ass. But, it's simply wrong to say that the single-payor systems don't provide better care for less money.
That said, I'd much rather we emulate Singapore. They make you pay for everything out of pocket from a savings account drawn off your paycheck. Paying cash for everything keeps prices in check, the mandatory contributions mean no one's "uninsured," and no insurer or HMO limits what you can buy. Subsidies help the truly indigent, and you can draw on it like a 401(k) in your dotage should you prove unusually resilient.
The Little Red Dot lets you be as much of a fat-ass as you care to pay for, and ain't that the American way. Japan, in the meanwhile, has an honest-to-God fat tax.
My parents tech support needs are very little, even without reboots and Mac Minis, and I help them readily, thankyouverymuch. That doesn't mean I need their computers to break before spending time with them, or that I wish their computers broke more often.
You raise a good point, but constantly fixing someone else's computer problems is draining, especially if the help is one-way and never reciprocated. It does nobody's relationship any good if you dread every call for the hour it's going to take to fix whatever broke.
Imagine instead if their computers actually worked, and you could therefore instead talk about whatever you wanted instead of why the printer isn't working. "Spending time with your child" is one thing, but I'm welcome to visit even when the Internet isn't broken; and, when visiting, I'd rather spend the time with them instead of their computer. Likewise, my folks are welcome to visit me even when I don't have a busted clutch slave cylinder or leaking fuel tank; and, likewise, the time is better spent on discretionary projects we want to tackle for the purposes of fun and/or bonding as opposed to helping with an emergency.
I have no idea what you can expect from big box phone support, or if "good" phone support even exists. There are a bunch of things you can do to make tech support easier, however, if you haven't done them already.
The best thing you can do (again, if you haven't already) is take away the Administrator account. I used to get weekly calls about my grandparents' PC, which saw a lot of use by relatives and grandchildren, until I did that. Suddenly, all the toolbars, viruses, Bonzi Buddies, random driver issues, and how-does-that-even-break issues just stopped. The occasional call to go type in the password and install something was much quicker than the frequent calls to uninstall something added by a well-meaning uncle or a young cousin.
Yes, some people were angry that they couldn't install things any more. But, they didn't want to take the support phone calls, so they didn't get the admin password. Everyone else was happy that the communal PC was suddenly much more likely to work when they wanted to check e-mail or play Facebook games.
If you have more hardware issues ("the printer stopped working"), think about getting new hardware. I have a Phaser 6125N, for example, which is overkill for most anything, really, but toner lasts forever and the drivers are completely free of crapware--you just plug in an Ethernet cable and forget about it. If their printer frequently causes issues, weigh the cost of a newer, more enterprise-y printer with the time saved by not having to fuck with it every week.
Ditto for modems, routers, whatever. If you have to walk them through rebooting their router every week, weigh the cost of a more reliable router over the time saved helping them turn it off and back on again.
Finally, work on your phone support. If you ask someone if the network cable is plugged in, they'll always say "yes," especially if they're a professor too proud to crawl underneath his desk and check for a lowly IT monkey.
Instead, ask them if it's plugged in the right way, because Ethernet cables are directional, you see. Make them flip it around (which, coincidentally, verifies a solid connection at both the wall and the PC). If that fixed the issue, they'll forever believe that Ethernet cables actually are directional, but it'll save you the trip to push a cable that last 1/8" into the jack.
This is necessary because most people--even family--are loathe to actually check e.g. what color some lights are, especially if checking involves some modicum of effort. While most people won't outright lie, they'll give you whatever they think is correct, or whatever answer sounds good off the top of their head, which is especially easy to do for yes/no questions.
So, never ask "is it plugged in"--the answer's always "yes," because of COURSE they plugged it in they're not an idiot and checking is effort. Ask them to switch the cable around. Don't ask if the lights are on--ask what color they are. Don't ask them to reboot their computer--ask them if their computer makes a noise when they hold the power switch for ten seconds.
...But, yanking a
It's harder than you're probably giving it credit for, especially for miles-long freight trains, where a hill can mean one segment of the train is accelerating while another is decelerating. We're just about there, though, insofar as we have software that automatically drives throttle, brakes, and other controls. Link:
Norfolk Southern, an American rail operator, now pulls roughly one-sixth of its freight using locomotives equipped with "route optimisation" software. By crunching numbers on a train's weight distribution and a route's curves, grades and speed limits, the software, called Leader, can instruct operators on optimum accelerating and braking to minimise fuel costs. Installing the software and linking it wirelessly to back-office computers is expensive, says Coleman Lawrence, head of the company's 4,000-strong locomotive fleet. But the software cuts costs dramatically, reducing fuel consumption by about 5%. That is a big deal for a firm that spent $1.6 billion on diesel in 2012. Mr Lawrence reckons that by 2016 Norfolk Southern may be pulling half its freight with Leader-upgraded locomotives. A competing system sold by GE, Trip Optimizer, goes further and operates the throttle and brakes automatically.
The article's a bit short on details, but this is where I expect autonomous driving to take off first--long-haul trucking. Controlled-access highways present fewer complications like pedestrians, four-way stops, and the like, and I imagine automating that would take care of 80% of the driving. Even if you still needed a human driver to reel 'er in at the warehouse gates or even the city limits, it still strikes me as a huge improvement.
Laws and liability are going to be the biggest limiting factor to commercial deployment, especially if they boil down to "a human must be ready to intervene at any time," but I think there are fudges around that. You could have one human operator in a remote control center "driving" multiple trucks, kind of like a cross between drone pilot and remote ICU monitoring.
Not that even a human sitting in the seat with hands on the wheel would be likely to intervene effectively should something go wrong after eight hours of idle monotony. But, having a human somewhere supervising in some capacity would soothe the more irrational fears that also serve as part of the reason we still keep human pilots flying planes, while still yielding the benefits that come with automation--self-driving trucks are much less compelling if each one still needs a full-time human driver to comply with laws.
Keep searching, m8. There really is a lot of stuff out there: Medication errors: prevention using information technology systems
It doesn't do ANYTHING you are talking about
EHRs absolutely do do all of those things, including checking drug interactions, allergies, and pregnancy and lactation warnings, and there absolutely is scholarly evidence of their effectiveness if you care to Google. Here's one concluding barcoding and CPOE are "vital."
If your EHR doesn't do those things, then that's a defect peculiar to whatever software you're using.
The medication lists are ALWAYS wrong or misleading as they are huge and hard to read, harder to update
You think they were any shorter, easier, or more up to date on paper? A bad computer system can make med rec harder, but even a good one can't make anyone give a shit about the patient's PTA meds. Nor can a hospital losing Joint Commission accreditation, apparently.
results from another EMR is always incompatible, so you have to scan it in
Yes, that's very common. It doesn't have to be the case, but it usually is.
Have you read an EMR progress note?
Yes. I have read lots and lots of EMR progress notes. I've seen notes filled with pages of stale labs because computers make it easy to copy forward the entire chart. I've seen notes flagged by the built-in plagiarism tools because copy-pasting an old note (and getting paid when you file it!) is easier than actually rounding on the patient. I've seen SOAP notes filed with weeks-old vitals because one group of residents preferred copying things into and out of Microsoft Word, which didn't exactly have the latest telemetry. I've seen notes with assessments that weren't done, filed on patients that weren't rounded on, because easy money.
But you know what? You can read them. And so can the doctor who sees the patient after you.
Certain kinds of errors have decreased dramatically. Computers reduce wrong patient/wrong medication errors dramatically, especially in systems that require you to scan the patient's barcode (to make sure you have the right patient), and then scan each medication's barcode (to make sure you've got the right meds). There's a lot of scholarly research available if you search for EHR medication errors, but this is one of the first non-paywalled things that pops up in Google.
Other issues are more challenging. You might have grabbed the right IV bag, and the computer might have confirmed that it had the right barcode, but that alone doesn't prevent pharmacy from filling the bag with the wrong fluid in the first place, or putting the wrong barcode on the wrong bag. It also doesn't stop a harried nurse from failing to mix both diluent and active ingredient of a vaccine when filling a syringe, or from using the same insulin pen on multiple patients; nor do computers keep toddlers from digging fentanyl patches out of the trash, overdosing on painkillers, and dying.
TL;DR most kinds of medical errors are decreasing, and computers tend to help--they're good at checking meds, and good at counting how many sponges you had in the OR field before and after cutting the patient up. Others are still around--handwashing compliance can still be flakey, silk neckties encounter years of sick people yet are never laundered, and "nosocomial infections" are still troublesome. Pick your favorite kind of medical error and give it a Google for recent stats.
I hear you--even within a hospital system, and even where standards exist, it's a pain. Ultrasound machines (for those that aren't imaging informaticists) are supposed to speak DICOM, but some do it creatively--one technically sent DICOM messages over the network, but most of what they contained was wrapped inside a proprietary XML blob rather than standard DICOM fields. What standard fields were implemented were implemented strangely, waffling between spelling out measurements ("centimeters") or using their abbreviations, mixing case, and reporting measurements to absurd precision (dozens of zeroes after the decimal point, for a bone measured in millimeters).
Sharing charts between hospitals is a mire of politics. There's the government's own Direct standard, which they mandated every hospital use to send charts, without any indication of what the recipient is supposed to do--a lot pipe them to /dev/null, because the vaguely defined content of the message is often useless and redundant with existing methods of communication. They're now working on legalese to require that you "do something" with the messages you receive, but exactly what that is (and how to objectively prove that you did it) they're still figuring out.
Then there are organizations like Commonwell, trying to monetize a data-sharing "standard" not even their founding members could be bothered to implement. They haven't sent a single chart as far as I know, but that doesn't stop them from issuing press releases praising their "interoperability" with the same frequency AT&T issues press releases praising their gigabit fiber.
Then there are HISPs (centralized, sometimes quasi-public, repositories of patient information). Some have managed to legislate themselves as mandatory middlemen, and, having done so, have proceeded to extract monopoly rents over the transmission of outdated and incorrect patient information. Even better is provider look-up--if they give you the wrong fax number for a physician, you are responsible for the HIPAA violation when a random gas station gets someone's medical information. This causes them to care as much as you'd expect about the integrity of the data they peddle (and that you're required to buy).
It's frustrating, because medical information has to be shared for it to be of use--there's no use having a mammography if no one will read the results, or if the people treating you can't access the study and have to order their own.
Being licensed profession will stop clueless management from force stuff to be so easy to hack / not willing to pay the costs to have be done right.
If you're going to make it illegal for literally anyone else to write software, then maybe. I'd love to see you square your favorite licensing regime with anything resembling open source development.
I wish I could request paper records.
You really don't. I've shilled for EHRs before, but the TL;DR is
That doesn't mean the electronic versions don't have terrible, even maddening, flaws, but even the worst are better than paper.
And as a developer who know what he's doing, I can't fucking wait for all the clowns to be weeded out of my profession.
You can't be that great if you haven't heard of Dunning-Kruger.
I won't disagree that medical billing is still a nightmare, but it's not the fault of CPT codes. No insurance company will sign a blank check and ask the doctor to fill in the amount; they all have a maximum they'll reimburse for, say, a broken leg, and they'll reimburse "broken leg" differently for a simple fracture than an unexpected amputation that took a crack team of surgeons 32 hours to reattach.
The codes are just a standard way to quantify exactly what was done. The "standard" part is important since most docs wouldn't be able to deal with more than a single insurance company if they all spoke a different code set. Absent a code set, it's much harder to determine how much your treatment should have when all you have are subjective descriptions from multiple doctors about what each thought they did. Codes remove that ambiguity, which insurance companies otherwise use to delay paying you and the hospital for as long as possible.
Generating the codes in the first place is complicated in the clipboard world, where a medical coder has to pore over sometimes hundreds of pages of scribbles to find out whether your vitals ever spiked into a danger zone that would have required more frequent nursing attention (at a higher cost), whether you were ever given certain kinds of medication, and, more subjectively, trying to divine what you actually had from the doctor's free-form notes, and what codes best describe that particular malady. Since this requires examining linear yards of flowsheet annotations (where an individual, critical cell might be missed) and subjective interpretation (does this description of a fracture qualify for Break-1 or Break-2?), different medical coders can end up coding the same chart differently.
Computers, in theory, can solve this. The computer knows exactly which medications you were given, how often, and at what cost. It knows exactly how often nursing took care of you, and can unambiguously determine your acuity. It knows every human in the operating theater, how long they were there, how much they cost, and every roll of gauze they used. Even free text notes are often templated, with doctors filling in blanks on standardized forms with multiple-choice answers, each of which can be unambiguously evaluated. Computers can instantly and unambiguously determine who too care of you, exactly how much it cost to take care of you, what codes best describe those services, and can communicate that information electronically to your insurers.
Where this falls down is a lot of computer systems grew organically--first a program for scheduling, then a program for billing, then a program for tracking clinical notes, then a program for monitoring vitals, etc., rather than some comprehensive monolith springing forth fully-formed right at the start. This means that to bill for a pregnancy, a medical coder might have to hunt through a dozen different systems: An ADT suite to determine where the patient was roomed and for how long, since a regular bed costs much less than intensive care. A specialty labor and delivery system, to gather the myriad of data states and to defend against lawsuits. An often separate fetal heart monitoring suite. An often separate ultrasound modality, with its own operating system that may or may not speak industry standards, that may or may not pair with a separate vendor-specific image viewer on computer workstations. A separate OR suite for doing documenting personnel, and doing counts and checks (to make sure you're billed for the roll of gauze they did use, not billed for the one they didn't, and that neither were left inside you.) A still-separate anesthesia suite, to make sure they don't gas you to death. An inpatient system for tracking medications and vitals, which may or may not be missing the medications and vitals collected by the labor and delivery suite, which may or may not have the vitals collected by the fetal heart monitor, which may or may not have the vitals collected by the OR suite for your C
What was so bad about clipboards again?
Clipboards have a bunch of known deficiencies. They're effectively write-only, especially if no one else can read the doc's handwriting.
Then, they're hard to duplicate. Should you end up in the hospital (heaven forbid), hopefully you're conscious enough to explain your drug allergies to the EMT, because it'll take a while to find out which clinic you normally see and get a copy of their clipboard. Then the copy of the clinic clipboard ends up in the hospital's clipboard, but the stuff in the hospital clipboard probably won't make it back to the clinic clipboard.
There's also only one copy of the hospital clipboard, so the cardiologist treating your heart attack can't put notes in your clipboard if the hospitalist took it to figure out what meds you were (or should be) on. If they do make copies, someone has to make sure the cardiologist's annotations make it into all of them without error. Those charts then have to be stored in a giant bunker somewhere, forever.
Clipboards are also bad at medication safety. When you're giving millions of med administrations to millions of patients, eventually you end up giving the wrong drug to the wrong one. Clipboards can't verify that you nabbed the right patient or the right drug, which kills people once you scale up the mistakes that would have happened to a national level.
Even before the nurse gives the meds, a clipboard can't tell the doctor that one of the medications he's ordering will interact with the medications someone else ordered. That also kills people. If one lot of those medications was tainted and recalled, it's also really, really hard to find out who was affected if all your administrations are documented on paper.
Finally, it's really hard to bill correctly if all of your documentation is on paper. If the coder going over the clipboard misses a charge, the hospital loses out on money. If the coder invents a charge, you lose out on money. If the coder can't find whatever documentation a kafkaesque insurance company demands to justify a procedure, you both lose out on money. Also harder to reject a claim for not being written in blue pen with block caps when the claim is electronic.
There's a bunch of other ways clipboards suck, and a bunch of ways the clipboard-replacements suck, but the former tends to suck a lot more than the latter.
How can somebody trademark a name that is a geological feature?
Because they aren't marketing a competing line of geological features, mayhaps?
John Scalzi isn't selling iPhones; he's selling e-books. Those actually do earn more profit--for everyone involved--when they don't cost more than a hardcover.
Unlike price elasticity, autorectogenesis is entirely responsible for that tortured non-expression and the verbification of "pence." Idea was that there hasn't been that much shilling since before decimalization.
Exactly! Or from seeing Valve's success with their Steam sales, or Apple's success with lower iTunes prices, or from any other number of things obvious to you and I and everyone but John Scalzi.
It's almost like Amazon is aware of that: