Wednesday, 9 March 2011

Princess Health and ONC: "The Benefits Of Health Information Technology: A Review Of The Recent Literature Shows Predominantly Positive Results" .Princessiccia

The Office of the National Coordinator for Health IT in the US (ONC) has just published an article in "Health Affairs" entitled "The Benefits Of Health Information Technology: A Review Of The Recent Literature Shows Predominantly Positive Results", Buntin, Burke, Hoaglin and Blumenthal, Health Affairs, 30, no.3 (2011):464-471, doi: 10.1377/hlthaff.2011.0178.

It is available at the hyperlink above, but may not be publicly accessible.

The authors all are, or were, ONC officials:

Melinda Beeuwkes Buntin (Melinda.buntin@hhs.gov) is director of the Office of Economic Analysis, Evaluation, and Modeling, Office of the National Coordinator for Health Information Technology (ONC), Department of Health and Human Services, in Washington, D.C. Matthew F. Burke is a policy analyst at the ONC. Michael C. Hoaglin is a former policy analyst at the ONC. David Blumenthal is the national coordinator for health information technology.

The abstract is as follows:

ABSTRACT
An unprecedented [indeed- ed.] federal effort is under way to boost [coerce? - ed.] the adoption of electronic health records and spur innovation in health care delivery.We reviewed the recent literature on health information technology to determine its effect on outcomes, including quality, efficiency, and provider satisfaction.We found that 92 percent of the recent articles on health information technology reached conclusions that were positive overall. We also found that the benefits of the technology are beginning to emerge in smaller practices and organizations, as well as in large organizations that were early adopters. However, dissatisfaction with electronic health records among some providers remains a problem and a barrier to achieving the potential of health information technology. [Some? That sounds like an understatement - ed.] These realities highlight the need for studies that document the challenging aspects of implementing health information technology more specifically and how these challenges might be addressed.

I have long stated, at least since 1999, that:

Healthcare information technology (HIT) holds great promise towards improving healthcare quality, safety and costs.

The new ONC review article is certainly pointing in this direction. Perhaps Health Affairs will release it to general circulation.

However, I also wrote:

As we enter the second decade of the 21st century, however, this potential has been largely unrealized. Significant factors impeding HIT achievement have been false assumptions concerning the challenges presented by this still-experimental technology, and underestimations of the expertise essential to achieve the potential benefits of HIT. This often results in clinician-unfriendly HIT design, and HIT leaders and stakeholders operating outside (often far outside) the boundaries of their professional competencies. Until these issues are acknowledged and corrected, HIT efforts will unnecessarily over-utilize precious healthcare resources, will be unlikely to achieve claimed benefits for many years to come, and may actually cause harm.

Whether the new ONC article demonstrates that these issues are starting to approach resolution, or is just another opinion paper not fully supported by facts, is not certain.

Two charts are presented that summarize the findings (click to enlarge):


(Click to enlarge.) Evaluations Of Outcome Measures Of Health Information Technology, By Type And Rating



(Click to enlarge.) Health Information Technology: Study Design And Scope Factors Associated With Positive Overall Conclusions

There are several caveats. The first has to do with possible selection bias that can be present in any review article.

On article selection for the review:

... we decided that to be included in this review, an article had to address a relevant aspect of health IT, as listed in the Appendix [7]; examine the use of health information technology in clinical practice; and measure qualitative or quantitative outcomes. Analyses that forecast the effects of a health IT component were included only if they were based on effects experienced during actual use. ... Using this framework, the review team removed 2,692 articles based on their titles. An additional 1,270 articles were determined to be outside the study�s scope after the team examined the article abstracts. For example, 269 abstracts focused solely on health IT adoption.

[What, exactly, does that mean? Were the problems with HIT adoption potentially significant towards causation of lack of benefit, and/or presence of harm, for instance? - ed]

By the third review stage, the review team had 231 articles. An additional forty-three were excluded after further review because they did not meet the criteria, and thirty-four review articles were dropped from the analyses because they did not present new work.

[What does that mean? Did they drop highly comprehensive articles showing uncertainty in the literature about HIT, such as Greenhalgh's "Tensions and Paradoxes in Electronic Patient Record Research: A Systematic Literature Review Using the Meta-narrative Method" from University College London? That article appeared in the Dec. 2009 Milbank Quarterly. I wrote about it at this link.]

This left 154 studies that met our inclusion criteria, 100 of which were conducted in the United States. This is comparable to the 182 studies found over a slightly longer time period that were evaluated by Goldzweig and colleagues.

I should also note that no mention is made of independent reviewers of the article corpus and elimination process. It appears the entire effort was conducted within ONC itself, where a bias towards finding positive results is likely present (and understandable).

Another caveat is the the Health Affairs/ONC article appears to bypass a body of literature, both peer-reviewed and non-peer reviewed, that sheds doubt on health IT in its present form from a number of angles such as I recently aggregated at "An updated reading list on HIT" and at "2009 a pivotal year in healthcare IT." Bypassing literature such as this is a possible major weakness.

Further, in the current political environment, it is not hard to imagine that articles highly critical of health IT, or revealing major mishaps and possibly exposing organizations to litigation, are scarce.

I addressed that in a paper "Remediating an Unintended Consequence of Healthcare IT: A Dearth of Data on Unintended Consequences of Healthcare IT." The paper itself was initially found needing revisions, largely in format, by a small group of blinded reviewers in the Medical Informatics community (with the exception of one faux-newshound who commented that "material like this could be read in any major newspaper", a rather perplexing comment considering the topic). Rather than revise, and not being on the tenure treadmill, I chose instead to publish at the Scribd link above.

The ONC paper does acknowledge this:

A recent study found that for clinical trials, studies with positive results are roughly four times more likely to be published than those without positive findings. Because the articles were limited to health IT adopters, we anticipated that authors more often approached studies looking for benefits rather than adverse effects.

They do, however, then issue a value judgment:

It is important to note that although publication bias may lead to an underestimation of the trade-offs associated with health IT, the benefits found in the published articles are real.

I"m not sure a dear relative of mine would find that value judgment heartening. They suffered a crippling injury that would likely not have occurred if paper had been used in the ED rather than an EHR.

I note that if a pharmaceutical company were to issue such a value judgment about a drug as justification for national marketing, they'd likely be nailed to the cross...

The ONC paper also ignores accounts of "near misses" and actual patient injury from impeccable sources, such as in "Health informatics � Guidance on the management of clinical risk relating to the deployment and use of health software. UK National Health Service, DSCN18 (2009), formerly ISO/TR 29322:2008(E)":

Annex A

Examples of potential harm presented by health software

GP prescribing decision support
In 2004 the four most commonly used primary care systems were subjected to eighteen, potentially serious, realistic scenarios including an aspirin prescription for an eight year old, penicillin for a patient with penicillin allergy and a combined oral contraceptive for a patient with a history of deep vein thrombosis. Using dummy records, all eighteen scenarios failed to produce appropriate alerts by all of the systems, most of the time. The best score was a system that flagged up seven appropriate alerts. The health organization clearly has, in such a system deployment, a key responsibility to ensure that knowledge bases used within a design are correctly populated and aligned with clinical practice within their organization.

Inadvertent accidental prescribing of dangerous drugs (such as methotrexate)
This incident occurred when a user of a primary care system attempted to issue two repeat items. The items were highlighted and instead of the issue selected repeats button, the prescribe acute issues from the formulary button was pressed. This brought up the formulary dialogue which contained the high risk items. Either the issue button was then pressed or the particular items were double clicked. When the warning messages came up, they were all ignored and proceed and issue selected. The user chose the first item presented on the formulary list, which just so happened to be a methotrexate injection. In this particular case, it was determined that patient risk was minimal as the treatment was rarely used in primary care and would, in practice, be rejected by the pharmacist. To preclude any recurrence of the problem, access to the high risk formulary was removed from the formulary part of the acute drug issue dialogue. This example again demonstrates the need to align clinical practice and authority levels with the knowledge and rule bases within the system. Wherever possible, design and implementation of health software systems should be undertaken to improve control and accuracy, note introduce new exposures. Furthermore the hazard and risk assessment of this situation may well not apply in other settings, e.g. prescription issue by nursing staff on a ward versus a pharmacist in a retail store.

Incorrect patient details retrieved from radiology information system
This incident arose from the fact that medical reference numbers (MRNs) are usually prefixed by an alpha code. Some hospitals however do not use these prefixes and identical MRNs can be generated. This gave rise to the creation of shared MRNs and subsequent confusion of records in the central datastore when retrieval key is the Medical Record Number. Four specific instances were found where a patient number had been entered in the radiology information system and incorrect patient details had been retrieved. The manufacturer could have built in an appropriate format check during development. Alternatively, the problem could have been spotted by the health organization if a structured risk assessment had been undertaken.

Drug mapping error
Sodium valproate 200 mg slow release was incorrectly mapped to sodium valproate 200 mg in a formulary encoded into a health software system. These are anti-epilepsy drugs and thus the implications for patient safety could be significant. This particular incident is just one of many that have been reported in relation to drug mapping.

An initial investigation indicated that 35 prescriptions had been generated using the incorrect map. Corrective action included contacting the relevant primary care practices to check upon patient health and the supplier to correct the mapping process to ensure no further incorrect prescriptions were generated. As before, this was a design/coding error by the manufacturer but was compounded by the health organization not checking the mappings and failing either to build in appropriate prescribing controls, or map the controls to health organization individuals with the appropriate experience and authority.

Pre-natal screening
The ages of women who had undergone pre-natal screening were wrongly computed by a health software system. As a result 150 women were wrongly notified that they were at no risk. Of these, four gave birth to Down's syndrome babies and two others made belated decisions to have abortions.

Patient identification
A student died of meningitis because of a misspelling of her name and inadequacy in computer use. The student was admitted and a blood test proved negative for meningitis. The following day another blood test was taken and filed on a new computer entry but the letter ?p was missed in the spelling of the name. When a doctor looked up results they were presented with only the first negative tests result because of the misspelling. If the second result had been seen it would have triggered further investigations and probable diagnosis of meningitis. The investigating panel concluded that problems with the health software system had been greater than first thought and in this case there was a combination of a misspelled name and the doctor not being able to use the computer system property. The health software system could have been designed to use unique numbers either instead of the name or in addition to it.

They also missed consideration of serious IT defects reports as in the FDA's Maude database that I wrote about at my Jan. 2011 post "MAUDE and HIT Risks."

Another confounding factor is the issue of possible unreliability of the medical literature itself as expressed in a recent post on the IBM Watson supercomputer exuberance:

Consider the issue of the medical literature suffering from numerous conflict of interest and dishonesty-related phenomema making it increasingly untrustworthy, as pointed out by Roy Poses in a Dec. 2010 post "The Lancet Emphasizes the Threats to the Academic Medical Mission", at my Aug. 2009 post "Has Ghostwriting Infected The "Experts" With Tainted Knowledge, Creating Vectors for Further Spread and Mutation of the Scientific Knowledge Base?" and elsewhere on this blog.

They do state what I have been writing about for over a decade now:

... In fact, the stronger finding may be that the �human element� is critical to health IT implementation. The association between the assessment of provider satisfaction and negative findings is a strong one. This highlights the importance of strong leadership and staff �buy-in� [which will only occur if the systems are not miserable examples of poor engineering, not due to P.R. or the irrational exuberance of others - ed.] if systems are to successfully manage and see benefit from health information technology. The negative findings also highlight the need for studies that document the challenging aspects of implementing health IT more specifically and how these challenges might be addressed.

Dear ONC: see this site, and the many posts since 2004 on this blog.

I was surprised to see this:

... Taking a cue from the literature on continuous quality improvement, every negative finding can be a treasure if it yields information on how to improve implementation strategies and design better health information technologies.

As in my post at this link, does this mean that 'anecdotal' accounts of HIT problems will no longer be summarily dismissed? I wonder.

I have also written in the past that in order to truly understand a domain, one must look at both evidence of the upside, and evidence of the downside. My concern is that the latter was not well addressed in this paper. A beneficial technology with a significant downside, especially in medicine, is not ready for national rollout (cf. Vioxx).

In summary, the new ONC paper may present a glimmer of hope that health IT is starting to produce real results. On the other hand, its possible deficiencies and biases might also make it more a political statement than anything else. It will certainly be used as such from the high government perch of HHS regardless. This has already started:

... President Obama and Congress envisioned that the HITECH Act would provide benefits in the form of lower costs, better quality of care, and improved patient outcomes. This review of the recent literature on the effects of health information technology is reassuring: It indicates that the expansion of health IT in the health care system is worthwhile.

[Note the use of "is worthwhile" as opposed to "may be worthwhile", a continuation of the "it's proven, nothing else to say" style I noted
at my July 2010 post "Science or Politics? The New England Journal and "The 'Meaningful Use' Regulation for Electronic Health Records." Such statements of absolute certainty are of concern; they remind me of the global warming debate - ed.]

...Thus, with HITECH, providers have an unparalleled opportunity to accelerate their adoption of health information technology and realize benefits for their practices, institutions, patients, and the broader system. [Ditto - ed.]

Does the article truly show a breakthrough, or is it a flawed review by a governmental agency that will be used for political purposes? I simply do not know which.

I am certain, however, that there will be active debate and dissection of this paper and its source articles in the months to come by those with more time, resources, and expertise than I have at my disposal.

-- SS

March 10, 2011 addendum:

Trisha Greenhalgh at Barts and The London School of Medicine and Dentistry and the author of the aforementioned comprehensive review article "Tensions and Paradoxes in Electronic Patient Record Research: A Systematic Literature Review Using the Meta-narrative Method" (link to my essay), had this observation about the following passage in the ONC paper:

�Our findings must be qualified by two important limitations: the question of publication bias, and the fact that we implicitly gave equal weight to all studies regardless of study design or sample size.�

Prof. Greenhalgh relates: "Given these very fundamental acknowledged biases, I�m very surprised anyone published this paper in its present form.�

-- SS

March 14, 2011 addendum:

Dr. Roy Poses had this to say:

Dr Silverstein commented on a new review of research of health care information technology whose results were mainly optimistic. The authors were from the US government agency that promotes health care IT, so its optimism is not surprising. However, its credibility was unclear, since it did not appear to be systematic. [In general, one at least assesses and takes into account the methodologic quality of studies used in a systematic review, and does not "give equal weight to all studies regardless of study design or sample size" - ed.]

Furthermore, the authors had no methodologic standards whatsoever for article inclusion. [They did, sort of, as in my paragraphs "On article selection for the review:", but one might term the standards "loose" - ed.] The review included qualitative studies that were probably not meant to be evaluative, and observational studies subject to severe methodologic bias.

The publication of this review demonstrated how the conventional wisdom is continually reinforced based on the strength of the influence of its proponents, rather than the strength of the supporting evidence. Adaptation of new drugs and devices should be based on evidence that their benefits outweigh their harms, rather than the enthusiasm and financial interests of their proponents.


-- SS
Princess Health and "Cogs in the Corporate Machine" - More on the Plight of Corporate Physicians .Princessiccia

Princess Health and "Cogs in the Corporate Machine" - More on the Plight of Corporate Physicians .Princessiccia

We discussed last week some of the perils of the latest trend towards the corporatization of medicine, practicing physicians becoming employees of hospital systems, including for-profit corporate systems.  A recent article in Medscape Business of Medicine included a striking anecdote about the life of a corporate physician.

Controlling Referrals by Contractual Provision
It started with the revelation that some employed physicians may sign contracts that obligate them to refer patients within the corporate system, even if that is not in their best interests:
Victoria Rentel, a family physician in Columbus, Ohio, joined a hospital-owned group several years ago. At first, nearly everything went fine. There were a few glitches: she'd occasionally order tests or consults at competing facilities, either for patient convenience or because of health plan coverage. When the hospital's administrators found out, they told her it was a violation of her contract; but that didn't stop her because she knew the hospital never enforced this provision.
A Non-Compete Clause, Even for a Laid-Off Physician

It also included the observation that corporate physicians may be abruptly laid off. Worse, being laid off means having to leave town, because apparently even laid-off physicians are still obligated by non-compete clauses in their contracts:
Then, out of the blue, she was informed that the hospital was going to close her practice within 45 days. She knew this wasn't her fault; the recession had hit the hospital hard, and it was laying off nearly half of the primary care doctors in her group. Still, it was a hard pill to swallow.

Making matters worse, her contract's noncompete clause prohibited her from going to work for any of the other healthcare systems in town. To avoid legal sanctions, she joined the student health service at Ohio State University.
Signing Contracts Without Understanding Them
The article's introduction emphasized the problem of physicians signing onerous contracts, perhaps without fully understanding them or without getting adequate legal advice:
Many other physicians -- especially those who, like Rentel, were previously in private practice -- complain about their jobs. In some cases, it's because physicians rushed into the arms of a hospital without looking carefully at their contracts or asking the right questions during their job interviews.
Cogs in the Corporate Machine

The introduction ended ominously:
Ultimately, the loss of control over their own professional lives is what irks employed doctors the most if they used to be in private practice. But some doctors also get the sinking feeling that they've become cogs in the corporate machine.

'The reality is that when you work for a hospital system, you're a service line,' says Rentel. 'And because primary care reimbursement is relatively low, you're a service line that feeds more lucrative service lines.'

Oddly enough, after that striking beginning, the article peters off into a discussion of some "gripes of employed physicians," which either soft-pedaled or failed to include the issues listed above.

The specific issues, and the general response of physicians to their role as corporate wage slaves deserve further consideration.

Signing Bad Contracts

First, the notion that physicians frequently sign contracts, particularly such important contracts as their own employment agreements, without reading them, without clearly understanding them, and without obtaining competent legal counsel is very disturbing.   A physician who signs a contract without reading it, understanding it, and getting competent legal advice about it is at best naive to the point of foolishness. 

My late father, an attorney, done told me to "never sign a contract you haven't read and understood."  Contracts are - surprise - enforceable legal documents that may involve surrendering important rights.  One should never sign a contract without being satisfied that its benefits outweigh its harms.

It could be that physicians who so blithely sign contracts are exhibiting learned helplessness.  Maybe they feel somehow pressured to apparently voluntarily agree to doing something that ultimately will harm them.  I am not sure that simply declaring on a blog that we will have to unlearn our helplessness if we are ever to save medicine and health care will do much to solve what may be a fairly deep problem.  But we must do so.

In addition, contracts are valid if entered into voluntarily.  It may be that some physicians truly sign contracts under duress.  Those contracts may not be valid, and could be challenged if they were so signed (again, if physicians are willing to unlearn their helplessness enough to get the counsel of a competent attorney.)

Stopping "Leakage" Possibly Unethically, Maybe Illegally?

The physician in the example above apparently had a contract provision which was violated simply by referring patients to competing facilities.  This appears to be an extreme way for a hospital to deal with the problem of "leakage," that is, the financial problem to the hospital caused when patients are referred outside the system.  Note that we discussed (here and here) the example of a for-profit hospital system with a large number of physician employees pushed to choke off "leakage" of patient referrals outside the system.

Although leakage may pose financial problems for hospitals, fighting leakage may lead to ethical problems.  Physicians are supposed to decide how to manage patients, and specifically to decide where to refer patients in the patients' interests, not just to keep money flowing to the health care system. "Leakage reduction" may possibly threaten physicians' first commandment, to make decisions to maximize benefits and minimize harms to individual patients, before all other considerations.

Worse, in the example cited in the Medscape paper, the leakage reduction was apparently implemented not by just trying to persuade doctors to keep patients within the system, but by a contract provision that somehow forbade referrals out of the system.  That may have not only been unethical, but it could have been illegal.  

The "Stark Law" (Title 42, Chapter 7, Subchapter XVIII, Part E, Section 1395 of the US Code) generally prohibits basing referral decisions on payments.  Full-time employed physicians are exempt from some of its provisions, but only if the physicians' "amount of remuneration under employment" "is not determined in a manner that takes into account (directly or indirectly) the volume or value of any referrals by the referring physician."  Therefore, were the contract referred to above to have forbidden outside referrals on pain of termination or reduction in remuneration, it could potentially violate this law. 

There have been rumors that physicians have been pushed to sign contracts that could so violate the Stark Law, but the published example above makes this a real possibility.

Physicians ought not to sign contracts that seem to limit referrals under penalty of pay reduction or termination, which may be both unethical and illegal.  Any physician presented with or who has signed such a contract ought to consult a competent attorney.

If hospitals and hospital systems are trying to force physicians to make referrals based on the hospitals' financial advantage instead of in the best interests of patients, that is reprehensible.  If these organizations are trying to do so via contractual provisions, this deserves investigation, including investigation by the relevant law enforcement agencies. 

Don't Be a Corporate Cog

This article underscores my previously expressed fears about how making physicians into corporate employees may remove the last barriers preventing patients from becoming corporate financial cannon fodder.  Physicians' most central professional value is to put patients' interests first.  Practicing physicians who practice as corporate employees are at risk of being pressured, or even threatened under the cover of contract enforcement to put their corporate employers' revenues ahead of patients' interests. 

Physicians should not let their patients, and their own values be so threatened.  Physicians who have inadvertently, foolishly, or under duress signed contracts that could threaten their professionalism and their patients' welfare need to do the right thing and challenge these contracts, or else there will soon be nothing left of the medical profession, and no one left to ethically care for patients. 

Tuesday, 8 March 2011

Princess Health and Those Big Doors Keep Revolving .Princessiccia

Princess Health and Those Big Doors Keep Revolving .Princessiccia

A few months ago, we discussed the revolving door that seems to connect US government leadership positions and leadership positions of commercial health care firms. There are other such revolving doors, like two recently discovered just north of here.

State Government to For-Profit Hospitals

As reported by the Boston Herald:
David Morales, a longtime trusted adviser to [Massachusetts] Gov. Deval Patrick, became the latest official to leave the administration as he stepped down from a top health-care post for a private sector gig.

Morales resigned abruptly yesterday to take a position with Steward Health Care System.

Furthermore,
Morales worked as a top adviser during the governor�s first term before taking a $128,000-a-year post in 2009 as commissioner of the Division of Health Care Finance and Policy. His resignation was effective yesterday.

Note that we have previously discussed the Steward Health Care System, the new name given to the Caritas Christi system after it was bought out by private equity firm Cerberus Capital Management. Steward's aggressive plan to stamp out "leakage" raised concerns that the new movement to make practicing physicians employees could push them to do what is best for the company's bottom line rather than for patients.

We previously suggested that deals that turn previously non-profit health systems and physicians' practices into for-profit corporations deserve considerable scrutiny. After Caritas became Steward, state government officials promised close oversight. Now Steward has acquired a new executive who has friends in state government.

Non-Profit Health Insurance/ Managed Care by Way of a Political Campaign to Health Care Venture Capital

This story also came from the Boston Herald:
Four months after his failed Massachusetts gubernatorial bid, Charlie Baker has landed a private-sector job at a Cambridge venture capital firm.

The former Harvard Pilgrim Health Care CEO is now an 'executive in residence' for General Catalyst Partners. He�ll focus on working with small and midsize health-care services companies for the VC firm, which has $1.7 billion under management across five funds.

In addition,
Health-related companies already in General Catalyst�s portfolio include iWalk, a Cambridge developer of orthotic and prosthetic devices, and North Carolina-based TearScience, which specializes in diagnostic and treatment devices for evaporative dry eye in addition to several still in stealth mode.

Note that managed care was originally touted as a way to control health care costs, and that the commercial health care insurance companies/ managed care organizations claim to be doing all they can to control costs. Such a focus on cost control would imply that they ought to be able to vigorously negotiate at arms' length with health care providers and drug and device companies.  Now some device companies have acquired a new venture capital overseer who has friends in insurance and managed care.

Summary

Not only are there revolving doors connecting the national government and large commercial health firms, but also connecting state government and regional hospital systems, and non-profit health care insurers/ managed care organizations and device companies.

This is just some more evidence that people in the leadership of large health care organizations have more in common with each other, even if their organizations are supposed to be competing or negotiating at arms length, than they have with patients, clients, customers and the public at large. 

The various revolving doors appear not to align the interests of leaders of health care organizations with their organizations' stated missions, or with promoting the health of patients.  To truly reform health care, we need to expose these doors to more sunlight, and then think about retarding their spin or even locking them in place.
Princess Health and The Future Pathways for e-Health in NSW .Princessiccia

Princess Health and The Future Pathways for e-Health in NSW .Princessiccia

Prof. Patrick has now added a new section to his report on health IT in NSW Australia, entitled "The Future Pathways for e-Health in NSW." It is available at this link (PDF).

It inoculates against most of the 'Ten Plagues' that bedevil health IT projects (such as the IT-clinical leadership inversion, lack of transparency, suppression of defects reporting, magical thinking about the technology, and lack of accountability of the bureaucrats).

Emphases mine:

In Short Term ( 0-3 months)

1. Halt further rollouts of Firstnet or other CIS systems. The current roll-out programs use significant efforts in training staff for a system that is counterproductive to patient well being.
2. Complete a full and thorough risk assessment analysis and usability of the software. The CIS report indicates there are a number of risks in the current software that are not likely to have been assessed in the past.
3. Address the current problems before doing anything else. There are a number of problems that appear solvable in the short term that would improve the situation for current users, such as providing needed reports.
4. Create the NSW IT Improvement Panel composed of ED Directors, IT-savvy clinical and quality improvement staff responsible for advising on the preparedness and process of the rollout.
5. Create an effective error and bug reporting mechanism that is viewable by all ED directors and with the display of the priority of each entry and expected completion time.
6. Initiate a high profile campaign to encourage staff to lodge fault records on anything they discover wrong, problematic or inefficient in using the system.

In the longer term (3-12 months)

1. Review the Health Support Services and make it clinically accountable by appointing a clinical head with an IT education.
2. Create a culture change in the HSS. The current operation of the HSS seems to be devoid of influence from the clinical community.
3. All NSW CIS system procurement should be guided by an IT Advisory Board of IT experienced clinical, academic and medical software industry experts.
4. Create pathways for hospitals that wish to be early adopters and take a lead role in the development of new methods for using and deploying IT systems.
5. Support innovation within the Australian medical software communities that contribute to a culture of innovation and continuous quality improvement.
6. Adopt transparency rules in all new healthcare information acquisitions. Secrecy has bedevilled the efforts of staff and management to get improvements in the CIS systems and hold service agents accountable for their failure to comply to service level agreements. All agreements about a signed contract should be available to the ED Directors.
7. Replace the State Based Build policy with a policy of providing a technology to match the technology experience of the individual departments so that leaders are not dragged backwards with inappropriate technology installation

The de facto "National Program for IT in the HHS" here in the United States needs a similar inoculation.

I can only add that our own ONC office (Office of the National Coordinator for Health IT of the Dept. of HHS) had more granular recommendations about expertise levels required for leadership roles in such undertakings. I wrote about them at my Dec. 2009 post "ONC Defines a Taxonomy of Robust Healthcare IT Leadership."

--SS

Monday, 7 March 2011

Princess Health and Are Those Sockpuppers From Down Under? .Princessiccia

We at Healthcare Renewal have had experience with the healthcare sock puppets. They are shills, a person or group working on behalf of a company or other special interest. They attempt to use distraction, ad hominem, misdirection and other psyops tactics to attack points of view they don't like. They also plant memes they or their sponsor deem desirable.

They are universally anonymous in their postings.

One got careless and got nailed via IP forensics, as at my Jan. 2010 post "More on Perversity in the Healthcare IT World: Is Meditech Employing Sockpuppets?" and my semi-satirical followup post a few days later, "Socky the Meditech Sockpuppet on Vacation?" after he/she disappeared after exposure.

A Healthcare Renewal reader with an MBA at that time non-anonymously related the following (emphases mine):

In reading this thread of comments I have to believe IT Guy [the Sock puppet - ed.] is a salesperson. My only question is: Were you assigned this blog or did you choose it? We had this problem a number of years ago where a salesperson was assigned a number of blogs with the intent of using up valuable time in trying to discredit the postings.

In my very first sales class we learned to focus on irrelevant points, constantly shift the discussion, and generally try to distract criticism. I would say that HCR is creating heat for IT Guy�s employer and the industry in general.

I find it sad that a company would allow an employee to attack anyone in an open forum. IT Guy needs to check with his superiors to find out if they approve of this use of his time, and I hope he is not using a company computer, unless once again this attack is company sanctioned.

Steve Lucas

It seems this foul type of creature is starting to crawl out of the woodwork regarding Prof. Jon Patricks' analysis of an ED EHR system mandated by the state's government of NSW for public hospitals, as I wrote about in my posts such as on Mar. 5, 2011 at "On an EMR Forensic Evaluation by Professor Jon Patrick from Down Under: More Thoughts.".

They may be corporate, they may be government. They likely have a financial stake in the ED EHR project as well.

For instance, the sockpuppet/shill comments are starting to appear at the Australian Health Information Technology blog of Dr David More MB, PhD, FACHI at http://aushealthit.blogspot.com:

This blog has only three major objectives.

The first is to inform readers of news and happenings in the e-Health domain, both here in Australia and world-wide.

The second is to provide commentary on what seems to have become the lamentable state of e-Health in Australia and to foster improvement.

The third, sadly, is now to try and force accountability for the actions of, and the funds spent, by NEHTA. [
National E-Health Transition Authority as at this link - ed.]

(Sounds like a kindred mission relative to HC Renewal.)

For instance at Dr. More's post "Prof Patrick Has Really Hit the Bullseye It Would Seem. Lots of Supportive Comments From All Over!" we see the following sock puppet-like comments rearing their holey (not holy) woven head:

... It seems that the heuristic axiom of Ockham�s Razor (as presented by Jon) is the design criteria by which Jon thinks NSW Health should have selected their CIS ... unbelievable!

Unfortunately Jon has not proposed any practical alternatives in his papers. His papers are full of opinions, unfounded claims and incorrect facts (not to mention the countless flaws in his research methodologies).

and

Dr Patrick - you are so misinformed. There are so many untruths in what you report. Why is this? Because you interviewed 7 people. Being Directors, what is the likelihood they are hands on with the system? Minimal I would say from experience in the EDs. Call yourself a researcher - huh! It is a totally biased report which reflects the opinions of those with an axe to grind. Why don't you talk to some nurses,clerical staff and junior doctors? There are hundreds of them working in EDs across the state. Their opinion should matter as they are the ones caring for our patients. You should be ashamed of yourself! I certainly would not hire you to do a research project if this is the biased and blatantly incorrect rubbish that you come up with. Shame on you!!

and the ever-so-common refrain of:

Has Dr Patrick ever completed (or even been involved in) an implementation of an EMR (at all or of any scale)? Can someone tell us what makes him an authority the subject? [I, OTOH, have done so, authoring, implementing, managing for hospitals and major pharma - ed.]

... His view is unbalanced and his paper is clearly bias. How Sydney University tolerates papers of such poor quality and biasness (being published by their professors) is beyond me. [Paper is 'clearly bias'? Biasness? This person needs a grammar lesson - ed.]

Ink is never put to specifics of the supposed transgressions in these largely ad hominem, anonymous attacks.

If those who wrote them had the fortitude to identify themselves, perhaps they might be somewhat credible. However that rarely if ever is the case.

In my humble opinion, such comments are risible, not even worth the electrons they're written with.

Except for amusement:

Socky the Health IT Sockpuppet. Click to enlarge.

p.s. an ED EHR-injured relative of mine has a message to the sockpuppets of the world. It's not fit for a public site, but it has to do with travel to a very hot, deep, sulfurous place in the earth.

-- SS
Princess Health and EHR ED's in New South Wales.  Will the Problems Magically "Disappear?" .Princessiccia

Princess Health and EHR ED's in New South Wales. Will the Problems Magically "Disappear?" .Princessiccia

It occurs that one could look at Prof. Jon Patrick's recent health IT forensic analysis as a kind of "indictment" of the industry.

He can be seen as suggesting the industry needs to be "put on trial" (figuratively) regarding "crimes" (again, figuratively speaking) they've committed with regard to IT robustness and reliability. The latter translate directly to patient safety.

In a lawsuit such as a medical malpractice trial, obvious as well as potential evidence is put under "legal hold." For instance, if an EHR defect is suspected, metadata, audit trails, and patient data are asked (or should be asked) to be frozen or archived in the state they were in at the time of the alleged accident.

It can take a page or three (or more) of specifications simply to define what information, exactly, needs to be put on legal hold. My former staff were frequently required to place myriad materials on legal hold at Merck Research Labs, for example, baed on the lawsuit du jour.

Once frozen, discovery and forensic analysis of these now-static data can then proceed. In fact, cases can be lost on the basis of evidence of an archiving omissions, destruction or tampering when information holds are requested.

It occurs to me that Prof. Patrick has given the industry a detailed look into factors they could start to remediate, without publicity and without telling anyone. While this would be a net plus for patients, it might result in less of a learning experience to the industy than that industry needs, to motivate the industry to avoid future product engineering and quality issues and put quality (not simply margin) as priority #1.

I therefore would believe a "hold" put on the present state of these ED EMR systems, or a "snapshot" of their current state (i.e., an evaluation environment mirrored from the present operational one) would allow a careful evaluation of the impact of the issues noted in the study.

Such an evaluation would be far more difficult with a cybernetic moving target.

The "snapshot" idea would allow evaluation of system risk levels, intermittent "glitches", interference with workflows, etc. in a controlled testing environment, using mock data or data drawn from actual cases.

The "snapshot" approach would also allow incremental remediation of the "live" system that comes out of safe, controlled testing, rather than sticking with what exists now until the studies could be completed on the as-is system, and then applying all the fixes as one or more large "upgrades."

I, for one, would be interested in studying this "built by software professionals" system and comparing it to health IT systems we "academic nerds" were authoring, say, 10-15 years ago.

-- SS
Princess Health and Getting Out of Our RUC - "An Open Letter To Primary Care Physicians" .Princessiccia

Princess Health and Getting Out of Our RUC - "An Open Letter To Primary Care Physicians" .Princessiccia

Since 2007, we have been writing about the secretive RUC (RBRVS Update Committee), the private AMA committee that somehow has managed to get effective control over how Medicare pays physicians.  The RUC has been accused of setting up incentives that strongly favor invasive, high technology procedures while disfavoring primary care and other "cognitive medicine."  Despite the central role of (perverse) incentives in raising health care costs while limiting access and degrading quality, there has been surprisingly little discussion about the pivotal role played by the RUC. 

Now there is a movement afoot to replace the RUC.  In a new post on the Care and Cost blog, and the Replace the RUC site, Paul M. Fischer and Brian Klepper urged four approaches:

1. Make the public aware of the RUC�s role and urge the primary care societies to stop �enabling� the RUC through their participation.
2. Recruit experts who can credibly calculate the economic impacts of the RUC�s actions, and who can devise alternative payment methodologies.
3. Demonstrate the unlawfulness of CMS� (and HCFA�s) two-decades long reliance on the RUC.
4. Develop a collaboration between primary care and non-health care business.

They are also urging three specific actions:
1. Contact your primary care society to demand that they withdraw from the RUC.
2. Broaden awareness of what we�re doing and why by rebroadcasting to your primary care colleagues.
3. Get in touch to help us with resources, relationships or approaches that can strengthen this project.

They have set up an electronic petition that people can use to urge the three major medical societies that represent primary care physicians to quit the RUC.

On Health Care Renewal, we have been trying to make the systemic problems with with the leadership of health care organizations less anechoic in the hopes that greater realization that these problems exist would lead to actions to solve them. The regulatory capture by the RUC of Medicare's payment setting mechanism is one problem that really cries out for a solution. In 2007, I called for "an unbiased re-evaluation of the components of the RBRVS by people who are dedicated to doing it fairly, not benefiting one group of physicians, or the organizations that benefit from the increased use of procedures"; and "an unbiased investigation of what went awry with the process used by Medicare to determine physician payments."  Your heard it here first on Health Care Renewal.  It is nice to now have such distinguished company. 

I urge our readers to consider the actions urged above. 

True health care reform will require a transparent, honest, fair process for governments to decide on how they will pay for physicians' care and other health care services and goods. 
Princess Health and Dr. Scott Monteith on "The Best Compromise" on Physicians and Use of Troublesome Health IT .Princessiccia

Princess Health and Dr. Scott Monteith on "The Best Compromise" on Physicians and Use of Troublesome Health IT .Princessiccia

I have posted two guest posts by Dr. Scott Monteith, a psychiatrist/informaticist, at the Jan. 2011 post "Interesting HIT Testimony to HHS Standards Committee, Jan. 11, 2011, by Dr. Monteith" and the Dec. 2010 post "Meaningful Use and the Devil in the Details: A Reader's View".

Here is another, with his permission. He is responding to a talking point from a health IT commentary website that was distributed among the AMIA evaluations special interest group readership.

Dr. Monteith asks some very probing questions. He writes:

I would like to respond to what I see as being one of the most important and challenging �real-life� issues confronting clinicians, and is captured in this excerpt [below, from the multi-vendor sponsored site HISTalk - ed.]:

HisTALK: ... Somewhere between �we vendors are doing the best we can given a fiercely competitive market, economic realities, and slow and often illogical provide procurement processes that don�t reflect what those providers claim they really want� and �we armchair quarterbacks critics think vendors are evil and the answer is free, open source applications written by non-experts willing to work for free under the direct supervision of the FDA� is the best compromise.

That is, this excerpt performs the helpful task of framing �the best compromise� somewhere between two extreme viewpoints.

It would be helpful (at least for me) if this group could discuss what �the best compromise� actually �looks like� in practice. How does one actually understand and live within �the best compromise�?

Let�s start with a relatively simple scenario:

What should clinicians do when they are working with EHRs that have known �problems� that are putting patients at risk, and the problems are not being immediately addressed, either directly or indirectly through, for example, an acceptable �work around,� or other adjustments to the EHR or local business processes?

Should the clinician continue to use the EHR and�

  • assume that others (e.g., vendor, IT department, administration, etc.) will fix the problem(s)?
  • report the problem(s)? Once? Twice? Three or more times? (How many?) To whom?
  • inform the patient of the known problem(s) (if the problem(s) apply to the patient)?
  • inform the patient that we do not have a good understanding of how to balance or even understand the risks posed by the EHR, given the dearth of peer-reviewed literature and algorithms? (What is �acceptable risk� for a given EHR problem? Does the EHR-related problem�s risk/benefit analysis change if the patient is in the hospital for a simple, nonlife-threatening problem vs. a complex, life-threatening problem)?
  • give the patient the option to NOT use the EHR? (Note that we almost always give patients the choice to refuse other �risky ventures� such as diagnostic procedures and treatments.)
  • inform their medical malpractice insurance company of the EHR-related problems?
  • submit the problem(s) to the organization�s ethics committee, if there is one?
  • report the problem(s) to the organization�s risk management staff?
  • report the problem(s) in writing or verbally?
  • stop using the EHR?

Etc. (including some combination of things).

Can providers (especially physicians) legitimately rationalize, given our ethical (to patients and our colleagues) and legal obligations (to patients and the state where we are licensed), the use of tools that are posing risks to patients and providers, when those risks are not spelled-out, not well understood, not peer-reviewed, etc.?

(Obviously everything we do has risks, but we are obligated to revel and discuss those risks as noted above. Further, the risks/benefits of a given diagnostic or treatment intervention are the product of peer-reviewed algorithms. Are patient�s aware of the risks associated with their doctor�s or hospital�s EHR?)

Again, the above excerpt suggests that there is a � best compromise.� But what is/are �the best compromise(s)�?

I joke with friends that I am a �radical moderate� � that is, I usually find myself committed to the �middle ground� in most complex and thoughtful discussions. But when it comes to EHRs, I am finding it difficult to define or understand what a �moderate� or an acceptable �best compromise� looks like.

Given the current EHR exuberance driven by ONC�s incentive dollars and vendor profits (or hoped-for profits), we all know that the �politically correct� approach is to �go along� and be an �early adopter� (without too many protests). But is the politically correct approach really the �best compromise,� especially in light of our ethical and legal obligations?

I am anxious to hear what other people think about this matter. I am sincerely seeking help in better understanding a sensible, real-life �best compromise� for those of us in the trenches.

Note that if we cannot define �the best compromise,� then what does that say about us? How can we justify �getting on board� with patient care tools (e.g., EHRs, eRx�ing, etc.) that are posing risks (known and unknown), with no clear processes for informing patients, not giving patients their choice to use these e-tools, no clear evidence-based risk/benefit analyses, etc.?

My own pithy, initial responses are as follows:

Re: Given the current EHR exuberance driven by ONC�s incentive dollars and vendor profits (or hoped-for profits), we all know that the �politically correct� approach is to �go along� and be an �early adopter� (without too many protests). But is the politically correct approach [i.e, "go along to get along" - ed.] really the �best compromise,� especially in light of our ethical and legal obligations?

No, for the reasons after your comma. [i.e., in light of our ethical & legal obligation - ed.]

One should look to the past for lessons in what the "compromises" might be.

How about the Flexner Report of 1910 as a start?

The treatises on human research protections penned largely after the Tuskegee experiments and the horrors of WW2, such as these as listed on an NIH web page "Office of Human Subjects Research, Regulations and Ethical Guidelines" might also shed some light:

  • The Belmont Report Ethical Principles and Guidelines for the Protection of Human Subjects of Research

I further opine:

Re: How can we justify �getting on board� with patient care tools (e.g., EHRs, eRx�ing, etc.) that are posing risks (known and unknown), with no clear processes for informing patients, not giving patients their choice to use these e-tools, no clear evidence-based risk/benefit analyses, etc.?

Perhaps with the line that "I never make mistakes ... everything I do is an experiment."

The technology is experimental. Perhaps the best way forward is to treat it as such.

In medicine I think there's a rich history of how to conduct proper (and improper) experimental research.

Again, Dr. Monteith raises some critical questions that need to be answered.

Or, more correctly, needed to be answered a long time ago, and long before planned national rollouts of healthcare information technology.

-- SS
Princess Health and Australian ED EHR Study:  An End to the Line "Your Evidence Is Anecdotal, Thus Worthless?" .Princessiccia

Princess Health and Australian ED EHR Study: An End to the Line "Your Evidence Is Anecdotal, Thus Worthless?" .Princessiccia

At my Sept. 2010 post "The Dangers of Critical Thinking in A Politicized, Irrational Culture" I lamented that while my early mentor in biomedicine Victor P. Satinsky MD taught the wise credo "critical thinking always, or your patient's dead" in the 1970's, our culture had become so perverse that this credo had been largely supplanted with:



"Critical thinking anytime, and your career's dead."



That post was in reaction to continued heckling on a professional mailing list, the American Medical Informatics Association (AMIA) Clinical Information Systems Working Group (cis-wg). On this list, Oregon Health Sciences University professor William Hersh expounded on how the evidence of health IT dangers was largely "anecdotal" therefore to be discounted, and how I, specifically, "didn't know the literature on health IT."



In that post I put the lie to the latter figment. On the former prevarication Dr. Jon Patrick, author of the recent thorough dissection of problems with the ED EHR system being rolled out in public hospitals in New South Wales, Australia (see my Mar. 5, 2011 post "On an EMR Forensic Evaluation by Professor Jon Patrick from Down Under: More Thoughts"), hit the ball out of the park:



Prof. Patrick to AMIA cis-wg:



I think such defences are particularly unuseful especially with respect to the dismissal of personal stories and experiences as "anecdotes", hence committing them to the realm of folklore. I offer these notions as a counterpoint.



Discounting Anecdotes:



1. Is a perfidious and specious act.



2. It denies early warning signs of problems.



3. It denies a voice and disempowers the working clinical community who have to operationalise decisions made by others.



4. It denies a route to process improvement within an institution - which is most important for EBM and incremental review of local processes.



5. It defends software manufacturers from fault rectification - cuts off even a need to deliberate on it. Critics of the value of anecdotes are squarely on the side of the faulty and deficient manufacturer.



6. A rule of project management is that projects consist of 3 components, cost, quality and time and if their needs to be a compromise it has to be on quality. Anecdotes are early warning signs of such a compromise.



Prof. Patrick had to once again put the lie to this refrain at a comment on the HISTalk blog yesterday, where the anonymous proprietor had written in a review of Patrick's EHR study:



... On the other hand, I wouldn�t say it�s [Prof. Patrick's Cerner FirstNet study] necessarily unbiased, it focuses on implementation of a single department application that didn�t go well for a variety of reasons (despite many successful FirstNet implementations elsewhere), it uses the unchallenged anecdotal comments of unhappy users who make it clear they liked their previous EDIS better, and it nitpicks (I wasn�t moved to find a pitchfork when I learned that the primary keys in the Millennium database aren�t named consistently).



[Considering the complexity and changeability of healthcare and the corresponding software lifecycle, I duly note that that latter attitude about 'failing to find pitchforks' regarding breaches of sound software engineering practices seems to be a symptom of the larger health IT disease that Prof. Patrick writes about - ed.]


Dr. Patrick then knocked the ball out of the Southern Hemisphere with a comment of his own about anecdotalism and a link to an expansion of the aforementioned ideas he'd shared on "discounting anecdotes":



Prof. Patrick to HISTalk owner:



Your Comment �it uses the unchallenged anecdotal comments of unhappy users � is not only unfair but unreasonably inaccurate. The comments made by the users are the Directors of 7 EDs and so they have a right to carry authority by virtue of the experience but also the number of 6 out 7 presenting a view of Firstnet as unfit for purpose has numeric validity, which they justify with about 20+ pages of their comments � see Part 2 Appendix 2.



I would also point readers to my editorial about the role of personal experiences being the most useful information to understand the nature of socio-technical failures. http://aci.schattauer.de/en/contents/archive/issue/1124/manuscript/15463/show.html


The essay at that link, "The Validity of Personal Experiences in Evaluating HIT", is an editorial in Johns Hopkins informaticist Chris Lehmann's brilliant new journal "Applied Clinical Informatics."



The editorial is available free, and is a must-read for anyone in a decision-making or managerial role in mission critical domains, including our elected representatives.



In the editorial Dr. Patrick concludes. similarly to his earlier AMIA mailing list opinion:



... the denial of recounted personal experiences in discussion and analysis of HIT is biased and specious and has the effect of:



1. Denying early warning signs of problems.



2. Denying a voice for the working clinical community who have to operationalise decisions made by others and thus disempowers them.



3. Denying process improvement within an institution � which is most important for Evidence Based Medicine and incremental review of local processes.



4. Discourages staff from engaging in any form of process improvement hence worsening the sense of disenchantment.



Every legitimate personal experience of a HIT deserves to be considered on its merits lest we wish to retreat from process and product improvement. Mechanisms of censorship both implicit due to contrived processes of disinformation and disempowerment or explicit due to contractual specifications will lead to more waste, lost productivity, contempt for the providers, and distress among frontline staff rather than increased productivity and improved patient health and safety as we all desire.



In my view, the drivers or motivators for the "anecdotalist" accusation are these, singly or in combination:



  • Too much "education" to see the nose on one's face, as in, to think zebras and unicorns instead of horses when hearing hoofbeats outside one's midwest U.S. abode (eggheads);

  • Too little common sense (fools), as in Scott Adams' example: "IGNORING ALL ANECDOTAL EVIDENCE - Example: I always get hives immediately after eating strawberries. But without a scientifically controlled experiment, it�s not reliable data. So I continue to eat strawberries every day, since I can�t tell if they cause hives";

  • Too much concern for the possible interruption of flow of money or power in one's direction (gonifs).



In conclusion, the anecdotalist refrain of "your evidence is anecdotal" [therefore of little or no value] when used repetitively against competent observers is the refrain of eggheads, fools and gonifs.



In healthcare, the end result is "your patient's dead."



My "anecdotal relative" injured in a mid-2010 HIT mishap is sadly an example.



[June 2011 addendum: my relative, after much suffering, has now died of complications of the "anecdotal HIT mishap" - ed.]



As for myself, I am a Markopolist (see my Sept. 2010 post "Health IT: On Anecdotalism and Totalitarianism").



-- SS