In the recent article Targeting
EHR Workarounds, the author makes the following comments: Workarounds, depending on the system and the
user, might be harmless in some cases but potentially dangerous in others.
Whatis.com states the
definition: A workaround is a method,
sometimes used temporarily, for achieving a task or goal when the usual or
planned method isn't working. In information technology, a workaround is often
used to overcome hardware, programming, or communication problems.
The fundamental problem is
that these workarounds may solve problems, but may inadvertently create
hidden/unknown downstream issues.
1.
Potentially created by a non-authorized user,
circumventing safeguards2. Putting the facility, the user, and the supervising hierarchy at liability risk
3. Affecting data collection
4. Missing financial credit for the documentation
5. Missing data qualifying for “meaningful use” credit
6. Potentially using macros with cut and paste that obscure the individuality of the encounter
7. Potential fraud issues as to what discussions and acts were actually performed.
8. Very important: avoiding definitive resolution of the issue. That is, by taking the workaround short-cut, and not communicating with the vendor about the problem (sometimes easier said than done), it will continue to appear for everyone.
9. Customization may be creative but cost-prohibitive.
10. ETC.
Many workarounds are designed to avoid alert fatigue. These
may do the job most (99%) of the time but can be disastrous if key information
happens to be ignored at a crucial time. See our prior blog on “Alert
Fatigue”. For example, scanning-in of relevant
documents (say, a medication list) may make life apparently simpler, but if
physician eyes do not see a key item (e.g. warfarin) the EH R and its decision
support mechanisms will be missing critical data (so, the patient may bleed to
death if sent to surgery without anticoagulant reversal).
No comments:
Post a Comment