Saving My Mother Yet Again. EHR Legible Gibberish - Another Example, the ED EHR Allergy List - And Legal Threats for Exposing Problems
My brain-injured mother was admitted to a suburban hospital (recently acquired by the "big hospital" where her EHR-related injuries of 2010 had occurred) Saturday morning.
She was again in a confusional state (delirium) of unknown cause, probably recurrent infection.
She was again in a confusional state (delirium) of unknown cause, probably recurrent infection.
Of note, almost every time I see hospital EHRs, I note a problem.
In my Jan. 2011 post on this issue at the same organization, "EHR Problems? No, They're Merely Anecodotal; the Truth Must Be That I Attract Bad Electrons and Stale Bits" I observed a nurse-stated "glitchy-ness" that day that manifested as unreliability in pulling up the patients' current med lists. I had to be the conduit of my mother's meds, despite having gone through them in detail for computer entry in the exact same ED just 24 hours prior after a fall:
This was not the "FirstNet" ED EHR by Cerner forensically analyzed by Dr. Jon Patrick (as I wrote about here), but another ED EHR, by a company whose ICU physiological monitoring system I once as CMIO struggled with due to repeated, unexplained crashing.
On this most recent ED visit/admission to the satellite just days ago, I noted another problem with the ED EHR system (the same one that started my mother's travails at the main facility in May 2010, and now in use at the satellite).
When the ED nurse brought up my mother's allergies, they were repeated over and over and over on the ED screen, in a long recurrent list dozens of lines long, as if they'd been cut-and-pasted multiple times at each visit. She apologized to me. See images of a printout that was provided to me by an ED attendant upon my request as my mother's POA, below (names of hospital, patient, EHR, and EHR screen layout digitally redacted):
Allergy list, page 1 (excerpted from an on-screen continuous list). Click to enlarge.
Allergy list, page 2 (excerpted from an on-screen continuous list). Click to enlarge.
Allergy list, page 3 (excerpted from an on-screen continuous list). Click to enlarge.
Note that on-screen these appeared as a long, confusing list.
The repetition made the list near useless to the ED personnel (for example, they don't have time to look for the one crucial item that ISN'T a duplicate in the mess).
Legible gibberish indeed.
The ED RN just asked me about my mother's allergies, saying she could not make sense of the computer list and wanted to make sure no mistakes occurred. This is an appropriate attitude - the only appropriate attitude - for a clinician. Fortunately, I'm a doctor and know the allergies well.
The hospitalist then called me that night suggesting she would give my mother Levaquin, an antibiotic. For the umpteenth time I had to tell a doctor at these facilities my mother was allergic to Levaquin. This was in fact one of my complaints on my April 2010 warning letter to the hospital's CEO and CMO on EHR deficiencies I'd noted in my mother's care. This was just one month prior to her catastrophe, when a critical heart medication "disappeared" in the ED EHR, causing a cascade of medication continuity failure.
Yesterday I insisted the duplicate entries be removed (more precisely, "made inactive" - they still appear, but in a different color than "active" entries).
It is, on first principles, inherently harmful to the public to have critical patient data stored in disarray in an Emergency Room electronic health record.
See the above images, and ask if this is what you'd want busy ED doctors to have to wade through to figure out if a drug they're about to administer might injure or kill you.
-- SS
Post legal-threat addendum:
I'd originally posted actual screen shots (PHI and hospital name redacted) of the allergy lists provided to me by an ED attendant upon my request as my mother's POA.
On April 8, 2011, however, I received a threatening letter from the attorney representing the hospital claiming these screens were viewed by the client as "copyrighted and proprietary information" that I had "misappropriated" (stolen).
(This raises the question as to who, exactly, the "client" is - the hospital, or the EHR vendor?)
In any case, I was asked to "retract from the blog the copyrighted and proprietary information" under threat of the hospital "pursuing all remedies under the state's trade secret laws and Federal Law." Further, I was accused of "inappropriate behavior" in trying to protect my mother from further EHR-related accidents.
The allegations (actually, fabrications) of "medical records misappropriation" and "inappropriate behavior" were especially outrageous and unprofessional, considering the hospital had already altered my mother's medical record by adding the medication they missed to the ICU H&P as at this post, was caught at it, and had admitted it to me.
I have now done as asked, only posting the allergy information and dates without the background EHR tabs of the screen header, the only component that could even remotely be viewed as protected IP (i.e., of the EHR vendor).
I had a followup discussion with a senior nurse involved in the EMR project about those screens and the legal threats, which I viewed as potential retaliation aimed at discriminatorily denying my mother and I use of public accommodations, i.e., the hospital, through intimidation. (If my seeking records legitimately was "inappropriate behavior", who knew what else I might be falsely accused of to "discourage" my return?)
I was informed with a straight face that the allergy repetition was a "feature", not a bug.
The problem was "the nurse in the ED", who did not understand they needed to "look at the dates" to understand the allergy list. ["Blame the user" is typical in this domain - ed.] This senior nurse clearly had an amateur's understanding of HCI and clarity of presentation of information - or was simply talking down to me.
I provided a reminder that with 20 years of Ivy academic, big hospital (much larger than hers) and Big Pharma experience in this domain, I found her arguments specious.
Amateurism on presentation of information is a factor that promotes EHR-related error. (It is my hope the original ED nurse is not punished for protecting patients instead of "protecting the computer" and its faults.)
-- SS
In my Jan. 2011 post on this issue at the same organization, "EHR Problems? No, They're Merely Anecodotal; the Truth Must Be That I Attract Bad Electrons and Stale Bits" I observed a nurse-stated "glitchy-ness" that day that manifested as unreliability in pulling up the patients' current med lists. I had to be the conduit of my mother's meds, despite having gone through them in detail for computer entry in the exact same ED just 24 hours prior after a fall:
... My mother was having a repeat of the ischemia to the brain or "TIA" (transient ischemic attack, i.e., threatening to have a stroke), only this time the ED EHR itself was also having a TIA.
This was not the "FirstNet" ED EHR by Cerner forensically analyzed by Dr. Jon Patrick (as I wrote about here), but another ED EHR, by a company whose ICU physiological monitoring system I once as CMIO struggled with due to repeated, unexplained crashing.
On this most recent ED visit/admission to the satellite just days ago, I noted another problem with the ED EHR system (the same one that started my mother's travails at the main facility in May 2010, and now in use at the satellite).
When the ED nurse brought up my mother's allergies, they were repeated over and over and over on the ED screen, in a long recurrent list dozens of lines long, as if they'd been cut-and-pasted multiple times at each visit. She apologized to me. See images of a printout that was provided to me by an ED attendant upon my request as my mother's POA, below (names of hospital, patient, EHR, and EHR screen layout digitally redacted):
Allergy list, page 1 (excerpted from an on-screen continuous list). Click to enlarge.
Allergy list, page 2 (excerpted from an on-screen continuous list). Click to enlarge.
Allergy list, page 3 (excerpted from an on-screen continuous list). Click to enlarge.Note that on-screen these appeared as a long, confusing list.
The repetition made the list near useless to the ED personnel (for example, they don't have time to look for the one crucial item that ISN'T a duplicate in the mess).
Legible gibberish indeed.
The ED RN just asked me about my mother's allergies, saying she could not make sense of the computer list and wanted to make sure no mistakes occurred. This is an appropriate attitude - the only appropriate attitude - for a clinician. Fortunately, I'm a doctor and know the allergies well.
The hospitalist then called me that night suggesting she would give my mother Levaquin, an antibiotic. For the umpteenth time I had to tell a doctor at these facilities my mother was allergic to Levaquin. This was in fact one of my complaints on my April 2010 warning letter to the hospital's CEO and CMO on EHR deficiencies I'd noted in my mother's care. This was just one month prior to her catastrophe, when a critical heart medication "disappeared" in the ED EHR, causing a cascade of medication continuity failure.
Yesterday I insisted the duplicate entries be removed (more precisely, "made inactive" - they still appear, but in a different color than "active" entries).
It is, on first principles, inherently harmful to the public to have critical patient data stored in disarray in an Emergency Room electronic health record.
See the above images, and ask if this is what you'd want busy ED doctors to have to wade through to figure out if a drug they're about to administer might injure or kill you.
-- SS
Post legal-threat addendum:
I'd originally posted actual screen shots (PHI and hospital name redacted) of the allergy lists provided to me by an ED attendant upon my request as my mother's POA.
On April 8, 2011, however, I received a threatening letter from the attorney representing the hospital claiming these screens were viewed by the client as "copyrighted and proprietary information" that I had "misappropriated" (stolen).
(This raises the question as to who, exactly, the "client" is - the hospital, or the EHR vendor?)
In any case, I was asked to "retract from the blog the copyrighted and proprietary information" under threat of the hospital "pursuing all remedies under the state's trade secret laws and Federal Law." Further, I was accused of "inappropriate behavior" in trying to protect my mother from further EHR-related accidents.
The allegations (actually, fabrications) of "medical records misappropriation" and "inappropriate behavior" were especially outrageous and unprofessional, considering the hospital had already altered my mother's medical record by adding the medication they missed to the ICU H&P as at this post, was caught at it, and had admitted it to me.
I have now done as asked, only posting the allergy information and dates without the background EHR tabs of the screen header, the only component that could even remotely be viewed as protected IP (i.e., of the EHR vendor).
I had a followup discussion with a senior nurse involved in the EMR project about those screens and the legal threats, which I viewed as potential retaliation aimed at discriminatorily denying my mother and I use of public accommodations, i.e., the hospital, through intimidation. (If my seeking records legitimately was "inappropriate behavior", who knew what else I might be falsely accused of to "discourage" my return?)
I was informed with a straight face that the allergy repetition was a "feature", not a bug.
The problem was "the nurse in the ED", who did not understand they needed to "look at the dates" to understand the allergy list. ["Blame the user" is typical in this domain - ed.] This senior nurse clearly had an amateur's understanding of HCI and clarity of presentation of information - or was simply talking down to me.
I provided a reminder that with 20 years of Ivy academic, big hospital (much larger than hers) and Big Pharma experience in this domain, I found her arguments specious.
Amateurism on presentation of information is a factor that promotes EHR-related error. (It is my hope the original ED nurse is not punished for protecting patients instead of "protecting the computer" and its faults.)
-- SS
Saving My Mother Yet Again. EHR Legible Gibberish - Another Example, the ED EHR Allergy List - And Legal Threats for Exposing Problems
Reviewed by MCH
on
September 18, 2013
Rating:
Reviewed by MCH
on
September 18, 2013
Rating:
No comments: