The first salvo in the legislative fight for the next Congress has just been fired. Max Baucus (D – Montana) is the chair of the Senate Finance Committee, and given that this committee controls the money coming into the government and half of the money going out gives him enormous control over social policy. The fight over healthcare will happen there, so it’s well worth reading
Ezra Klein’s profile of Baucus in general, but especially if you want to get into the nuts and bolts of healthcare.
In general Baucus hasn’t been an especially inspiring Democrat, but he really seems to have his game face on here. He’s been holding public hearings (9 of them at last count) and has been meeting privately with Kennedey and others. And to formally kick of the policy fight, and more importantly frame the debate,
Baucus has released a white paper laying out his positions.
There’s a lot of the Obama plan in there, though he adds quite a bit including an individual mandate. The plan runs just shy of 100 pages, and I don’t’ think anyone has read the whole thing yet, but the quick and dirty summary paragraphs from the executive summary are:
Like a sturdy stool, the Call to Action has three equally important legs: (1) a policy that ensures meaningful coverage and care to all Americans; (2) an insistence that any such expansion be coupled with an emphasis on higher quality, greater value, and — over time — less costly care; and (3) an absolute commitment to weed out waste, eliminate overpayments, and design a sustainable financing system that works for taxpayers as well as for the nation’s recipients and providers of health care.
....
Beyond measures to refocus the system on primary care, reward quality care, and invest in critical research and technology, the Baucus plan would endorse direct steps in five additional areas to curb excess health care spending. The plan would invest more to detect and eliminate fraud, waste, and abuse in public programs. The plan would address overpayments to private insurers in the Medicare Advantage program. The plan would increase transparency of cost and quality information and would require disclosure of
payments and incentives to providers by drug or device makers that may lead to biased
decision-making. The plan also considers careful reforms of medical malpractice laws that could lower administrative costs and health spending throughout the system, while ensuring that injured patients are compensated fairly for their losses.
The full executive summary follows below. There's a lot of good stuff here, though right off the bat I'm somewhat dubious about any talk of malpractice lawsuit reform (though it's certainly debatable). The points about reducing cost either seem glossed over or of questionable value, which I think could be a big issue both legislatively and with the real world application. Besides making it palatable, we do need to rein in costs and improve care, and ramping up access, though important, is only a first step.
Posts
In addition, as Klein's article points out, MT politics have shifted significantly. I've joked that the MTGOP selected the people running against both Baucus and Schweitzer were picked by drawing straws - with the guys drawing the short ones getting the job of being the electoral sacrificial lambs. This means that it's going to be hard to pressure him from the right.
I do have some reservations about the ability of any plan to reform the current structure and be sustainable, as opposed to just ripping everything out and starting from scratch, but given reality I'm feeling good about this. I also worry about funding, because even if everyone overall comes out ahead when you compare the amount they currently pay versus the revenue the government will have to collect to maintain the system it's a pretty potent potential cudgel for the Republican's to use.
Who else is (or should be)? EVERY OTHER INDUSTRY THAT IS STUCK WITH THIS ALBATROSS.
Pharma is a powerful lobby, but hot damn you would think Big Business would throw their hat into the ring on this one. They can only win.
It's in there. I was especially glad to see it, since it guarantees me a lucrative career through the next decade
Last paragraph of improving healthcare quality and value
edit2: Though I'm personally dubious about it's cost savings value. It's fairly pricey to implement (currently prohibitively so in small practices) and you aren't talking a huge savings in personnel expenses to move from a large staff of lower skilled workers to a smaller staff of skilled IT support. I'm sure there are relevant studies out there that get more specific, but I don't think the front end savings are all that appreciable.
Now in terms of improving quality of care and moving healthcare to a more evidence based and standardized model, I can't rave about electronic records enough. The kind of shit that slips by currently would scare the hell out of you, and IT can be a huge help there.
Just looking at my father's office, and the offices in Miriam Hospital, makes me want to cry. Endless reams of yellowing, barely-readable paper. Digitizing would go at least a short distance towards making it easier on everyone to actually communicate.
About cost-saving, yeah it would probably be minimal if at all, but damn it would be worth it.
Ah, I skimmed right over that somehow. Awesomesauce. :^:
I'm skeptical that it wouldn't save money, though. How many man-hours would be saved in not having to physically dig through file cabinets for this shit, through not having to fuck with a fax machine to send records, through not having to physically cart these things around the building, through not having to recreate the form you just lost because you put it down somewhere en route to the cafeteria?
The thing is in most modern hospitals or major clinics that's done by either unpaid volunteers or low paid secretarial staff. And you have to balance that against a pricey implementation and ongoing IT hardware and staff costs. There are some savings, and the actual benefits to care can't be overstated, but it's not currently a money maker.
Now, if the government started throwing tax incentives around, or some more of the current plan for e-perscribing (percent bonuses to all medicare/medicaid payments if you use it, gradually decreasing and turning into a penalty after a certain number of years) all that math might change.
I work on the side where the claims have to go out to be paid, and dealing with paper claims uses up not just more time having them keyed in to be sent electronically to insurance companies, but there is a much higher rate of error that leads to rejected claims when things are sourced on paper which takes even more time to straighten out. We might not make as much off of health claims that come to us electronically, but they move through the system so much easier.
So did Clinton. Look where that went, and the insurance is even more powerful now than they were then.
I entirely anticipate that the whole thing will be stuck in committee indefinitely, if even that. The answer we'll get is "Yeah, we need reform, but 'they' (obscure 'they') won't agree on what needs to or can be done." It makes it look like they're trying to do something, and an unnamed "they" are blocking it (likely to be blamed on the Republicans, but the block will come from both sides).
The Clintons went out of their way pissing off all kinds of Congresscritters when they were trying to do this, which isn't exactly comparable to having the chair of the Senate Finance Committee introducing the damn thing and it having the moral force of Ted Kennedy's legacy project behind it.
Also, there was less public outcry for a solution to the health care crisis. It's now more expensive and more people are going without it. A lot of the free market uber alles crowd are currently sitting around unemployed with no health care benefits and a stark fear of contracting terminal ass cancer. That tends to move hearts and minds.
Like I said, this is why they will possibly let it go to committee, then let it languish there indefinitely. I gives the appearance that they're working on it, without actually passing anything. The insurance lobby will pretty much devote themselves to destroying any congressman or senator that votes for such a bill in the next election.
Ah, so you're a cynic who thinks Washington is broken and there is no hope.
Realistic based on experience, rather than hopeful based on...uh, hope?
Believe me, nothing would please me more than to actually see it work and genuine progress be made, but because of past experiences, I can't reasonably have faith that it'll happen.
The big problem is what happens when two systems collide. If someone from North Carolina is over in California when they fall ill and NC and Cali use different computer systems for storing patient records there's a non-trivial data interchange problem. The history of IT projects in the British NHS is one of near constant failures and massive cost overruns, and we're a pretty compact nations with a sixth of the population of the USA.
I made a game, it has penguins in it. It's pay what you like on Gumroad.
Currently Ebaying Nothing at all but I might do in the future.
I've had at least four sets of dental x-rays done unnecessarily because I move around a lot and each new dentist would rather x-ray than wait for the previous x-rays to be mailed.
Privacy concerns.
That's the kind of thing you just need to impose through regulation, especially if you're going to mandate usage. There are already at least nominally a couple of regulatory boards devoted to ensuring interoperability. There's also HL7, which sets international standards for formatting and data exchange of medical information that is probably where the solution lies. You and I might have wildly different systems, but as long as we're both required to have at least some minimum set of data for every possible record and we have to send the data in constant, discrete ways you can set up interfaces between any two systems.
The wikis are actually a pretty decent overview for Electronic records and HL7.
Why wouldn't you want other doctors and hospitals to have access to your patients' records?
|EDIT| And it's not like you'd have to actually store the data in a centralized location; just make sure everyone is using the same program so that when they do want to exchange information, they can do so quickly and easily.
You don’t need a centralized data warehouse you just need a standardized schema. Create a national health care storage standard and mandate that all systems conform (can import and export) to the standard so you can have distributed data stores and even different competing software manufacturers but they can all share data.
EDIT: Werehipppy got there first and with an existing schema.
My guess is that if healthcare institutions are going to be mandated to go digital and they are spending money to do it they are going to want to get more bang for their buck.
By this I mean if I own my own practice and I am mandated to become digital. Let's say I have a couple of options. A) Barebones solution that just stores and distributes the data law requires or a system that lets me do other things my practice handles like appointment scheduling and billing in addition to the government required digitization of records.
So long as option B is proportionally priced to option A then I think there would be a competitive market for it.
Point being that while the government will mandate the digitization they won’t be providing the software or hardware to do it (maybe a tax credit at most) so that means private industry will step in to fill that role. The thing that I think needs to be mandated is the format that the data is required to be (transmitted not necessarily stored) in.
I defer to the superior technological expertise of just about everyone else on the forum.
In theory, there's nothing wrong with it.
The front end would need a ton of work to be usable, and then on top of that you'd want to build a lot of logic to do safety checks (are you sure you want to give 1000x the lethal dosage of that med? or are you sure you want to cause that fatal drug interaction? are good questions), best practice suggestions (are you sure you don't want the recommended drug for this symptom or are sure you don't want a CT scan for that head trauma?), and then if you're feeling fancy you put in stuff like Medicare requirements or standard practices (your 60 year old female patient hasn't had a mammogram, you've ordered a MRI for a runny nose, the patient has already had a CMP this month, and so on). At the end of the day, that's what all the major systems are, they just all have different implementations of the front end, different structures to store the data on the back end, and most of them are using archaic database languages because they've been in production for 3 decades (the only places on either that use MUMPS are banks and hospitals).
HL7 is basically what you suggested for a file format to transfer information. A whatever (patient admission, results, medical notes, what have you) being transferred is sent (sent being actual direct transmission or loading from a file) as a set string of data, and each discrete chunk is separate by a standard character, and each chunk is a specific predefined piece of information. That lets anyone get the stream of data and their application should have a systematic way to take each chunk and then put it in the appropriate place to recreate the records in the their system.
Mandating 1 software program would essientally cut out business for the companies, who do you pick? Epic? IDX/GE? McKession? All of these compainies and their products, while similar have particular strengths and weaknesses that allow them to have market share.
I can say that companies would likely welcome some further govt. regualtion on how to do e-records, but I do not see how congressmen/women would be qualified to lay out technical specifications for such a thing.
There is a push to a 'universal' patient identifier/number, but I don't have a lot of detail on it to share at this time.
This was so interesting to me I had to regeister and break my usual lurk/silience ruels for large forums. I'd rather not share which company I work for as I am not 'authorized' to be an offical representativebut would be happy to give some perspective as to how daunting a problem this really is. We have customers across the US and no two sites are the same or even all that similar....
What would be the problem with requiring a format for the data supported by off-the-shelf products, when any hospital could still pay to have someone custom-build a package that used that format? To use an example I actually know something about, let's say the data had to be in a simple spreadsheet. You require that all data be exportable in a comma-delimited text format. So if someone wants to just go pick up Excel, they can do that. If someone wants to create a robust management system that handles all manner of tasks, they can do that, and just ensure that it can export in a comma-delimited text format. Each place can spend as much or as little as they want on the solution, and you'd likely have a huge boom in the software industry as hospitals nationwide start demanding custom management and record-keeping apps.
Seems win-win to me. Am I missing something?
This is why the people in our government would talk to "evil special interests" (read: experts) about how to design legislation that would outline the requirements for such a format.
I think the difference between this time and last on health care reform is that Obama is going to be better at bringing everyone together, and the general public is clamoring for a solution to high health care costs.
The system works really well. Using this information I can plug my equipment into any modern car and do a thorough diagnosis of the vehicle's engine management, emission controls, safety equipment, air conditioning, radio, or any of a number of other standard pieces of equipment using one scan tool.
The equipment on the vehicle is manufactured by whoever the auto manufacturer chooses to use. GM has its own company that does this, most European cars use Bosch, Japanese cars tend to use Nippon-Denso, etc. The equipment used to plug into the car can be made by anyone such as Snap-On, Mac, Matco, etc.
What I'm getting at is, these systems work really well, have standard data sets used for control and diagnosis, can be transmitted easily, and have standardized regulations for equipment manufacturers. Why on earth can't we do something just like this for medical records?
HL7 does exactly what your example does, with the added caveat that the order of the coma delineated data is set (so for example first bit of data is last name, then a comma, then first name, coma, middle name, etc).
Xandar is right that it's currently a beast getting two systems to talk to each other, but I'm of the opinion that's just because it hasn't previously been worth it. When there were 50 hospitals in the US that used an electronic system why spend all the time, effort, and money required to take electronic transfers of information when you can just route that stuff through the same paper based channels you have to maintain for the thousands of non-electronic record sites. As systems spread there's more incentive to take advantage of the the benefits of speeding up and automating information exchanges.
You're still likely to always have some issues (look at all the trouble making matches between different systems we currently have, like social security and voter registration rolls) but it's going to get much much closer to a true pure electronic record system in the near to mid future. Something like 50-60% of healthcare systems supposedly have some sort of electronic record budgeted for implementation to start over the next few years, though it take a few years to get a system up and an economic downturn is going to put the breaks on discretionary capital investments.
Even if there is a comma-delimited format someone still has to set that format and ensure that everyone uses it the same way. So, if there is going to be a standardized format why not use an XML Schema Definition or some other technology that can be used to verify format compatibility. You would want to ensure that the system you are using will always reliably created the agreed schema.
If there is a mandate to move to electronic documents then there should be an agreed upon industry standard format for keeping and transmitting the information. Any software that claims to be compliant should get a government certification that it can handle the format.
There is no reason Microsoft or any other company cannot add this output type to their product and get it certified though.
No, in essense this is the 'right' idea, and to some degree is what HL7 is (http://en.wikipedia.org/wiki/HL7) However it is a 'framework' and there can and will be some variation in how any given hopital uses it. Is most usful for getting ADT information between disparate systems (Admissions / Discharge / Transfer ). You mediacal record though is likely to be more then that. A lot of information is going to be images as well and can be in lots of dirrerent formats (JPEG, tif ect.) for just 'paper' documents that have been digitized. Actual diagnotic images has many many different formats (for example see
http://www.dclunie.com/medical-image-faq/html/) How many formats would a given 'viewing' application need to support, what about licesnsing for all those systems as some formats are proprietary?)
The best analogy I can come up with offhand is similar to your suggestion of using CSV for DB information, while thats a useful starting point, you can quickly run into issues. What if system 'a' has 7 columns of information and system 'b' uses 6? Or take the example of convertnig an WORD document to RTF and then importing into another word processor program. Sure you will get ;most' of the information correct, but some information may not be just right or formatted oddly, a minor PITA when trying to collaberate on a school/wrok project, potentially deadly when dealing with health records.
I'm all for the govt. laying down a more strict set of standards to allow basic communication between facilities, but its a duanting project and there will be lots of competing intrests looking to get 'their' way recognized as correct. Remmeber as well many hospitals still use mainframe/as400 for admitting/registration ect. how to rewrite all that code in a cost effective manner?
The best thing patients can do is get a complete copy of their medical records in some format (pdf say...) and store it on a jump drive when travelling. Worst case the hospital can print off a hard copy and give to the Dr.
I think this keeps getting buried in my other replies, but this standard basically already exists. It's called HL7, and it's universally accepted. It's just each individual healthcare system hasn't had any reason to bother to implement connections to other individual systems (as opposed to different internal systems that one healthcare system may use) because there was no upside for them. They would need to buy and maintain secure external links and modify the incoming data to properly file to their own customized version of whatever system they are using, all for the extremely few cases where they'd be getting patients from another healthcare system that used an electronic record.
There just weren't enough places using EMRs to make it worth it. As the usage ramps up, the interest in making systems talk to each other will increase and people will implement what's already available.
Basically, to outright steal from the group that focuses on reforming healthcare (control costs, improve care through IT and research on effectiveness, etc) and the group that focuses on expanding healthcare (there are 46 million without any coverage, get them on board first).
The Obama plan clearly caters to both, and all signs are that this is going to happen, but it's worth keeping an eye on where people are coming from when they advocate for various things.
Basically, a lot of medical software companies have "Not Invented Here" syndrome, and hospitals want it backwards compatible with retard-o formats.
Beyond that, it actually already is happening. Just not universally across all systems. I'm pretty sure we're going to need further government mandates for this to happen any faster.
Also, I can't show you what the exported text files look like, but let me assure you they are as retarded as you can imagine. Imagine an .ini file with no labels to identify one thing from another, mixed up together with no whitespace, but in a very specific order such that if you transpose two fields, the hospital is suddenly missing $10,000.