Background: In the Clinical Documentation module, nursing staff have
the ability to recall the last documentation that was documented in a
field using the F5 key. Sometimes documentation is recalled and left
unchanged from the previous documentation, which appears like
assessments have been unchanged from shift to shift.
Question(s): What education have you provided to nursing staff about
the F5 recall key?
Does your ministry allow the use of the F5 key?
Has anyone found a workaround for the F5 key?
Has anyone experienced problems similar to this?
Thanks in advance for your information!
Josie McMurtrey, RN
Solutions Development Clinical Analyst
Ascension Health Information Services
Meditech Community of Excellence
St. Joseph Regional Medical Center
CONFIDENTIALITY NOTICE:
This email message and any accompanying data or files is confidential and may
contain privileged information intended only for the named recipient(s). If
you are not the intended recipient(s), you are hereby notified that the
dissemination, distribution, and or copying of this message is strictly
prohibited. If you receive this message in error, or are not the named
recipient(s), please notify the sender at the email address above, delete
this email from your computer, and destroy any copies in any form immediately.
Receipt by anyone other than the named recipient(s) is not a waiver of any
attorney-client, work product, or other applicable privilege.
====================================
Please do NOT send messages that ask "Please post to the list" These are useless messages that just waste the email server's resources. Instead, email the original requester and ask that they send you or post the results of their question.
To UNSUBSCRIBE, go to http://MTUSers.net
for information.
The meditech-l archives (and other tips) can be found at
http://mtusers.net/zarchives
Job opportunities in the Meditech community can be found at
http://mtusers.net/zjobs
Regards,
Glenda DeBord, RN/BSN
Sr. Analyst, Information Technology
Duke Raleigh Hospital
(919) 954.3347 office
"McMurtrey, Josie" <jmcmu...@sjrmc.org>
Sent by: meditech-...@mtusers.com
11/17/2009 05:14 PM
To
<medit...@mtusers.com>
cc
Subject
[MEDITECH-L] F5 recall key
Trish Hahn, R.N.
Nursing Coordinator, M.I.S.
Little Company of Mary Hospital
Evergreen Park, IL 60805
th...@lcmh.org
Phone - 708.229.5196
Fax - 708.499-8512
www.lcmh.org
"In Pursuit of Pain Free Health Care (SM)"
>>> "McMurtrey, Josie" <jmcmu...@sjrmc.org> 11/17/2009 4:13 PM >>>
We had Meditech disable the F5 key over the summer as a request of
nursing administration due to staff mindlessly cruising through
assessments and some sporadic poor documentation findings, which were
probably border line of legal concern.
Unfortunately 1:1 counseling was not working and it was a global
problem. It seemed ill advised for us to just state that it was an
accountability issue alone. We felt we were being negligent as
healthcare leaders if we did not focus on becoming risk averse and
recognize when an element in our practice that is inherently flawed or
too easily misapplied was being used daily; particularly when some poor
documentation incidents could have been avoided or paused the clinician
had the F5 option not existed - kind of like the 'time out' in surgery.
Because many clinical staff were misusing or depended on the F5 recall
function led us to think that the underlying purpose of F5 was too
easily morphed into a time saver which was not its original intended
use.
It took us a few months to plan the F5 disable as nursing was not used
to viewing the information from the previous documentation under View
History. We also knew they liked to copy one another's comments, word
for word or add an 's' or period if we had an attribute that warned
against the same comment with F5. The general argument was the nurses
quickly F5 through the screens, and F5 disable will cause overtime and
fragmented charting. So we took some time to add just a few attributes
(less than 40) that with <enter> will default the last response similar
to F5. Because most professional staff will document accurately, we
created a committee and the fields that needed an attribute fix with the
F5 removal were added and tested. Most were locations such as IVs,
wounds, drains, and due dates for tubing changes, last BM, etc for
continuity of documentation. None of the attribute fixes were for an
assessment value that the nurse should be documenting per her unique
assessment Q4H or QSHIFT.
Below are the attributes we used in place of F5:
To default a single response query like F5:
DFT=@p.ADM.PAT.ccdqr.response["QUERY"]
Defaulting previous responses to multiple line queries was difficult,
however I used the below attribute and it is working well. Thanks to
Kenny Whiteside for his post on the L-list with this one.
IFE=IF{+/[ANS%0,"QUERY"]M[""];
IFE=""^ZX,
IFE=DO{+(*AA.CCDQR[@t.ADM.PAT.urn,"QUERY"]M
IFE=[ZX],ZV)^ZX ZV|0^/[ANS%0,"QUERY"]M[ZX]|0,
IFE=IF{ZX'>2 P(R-1+ZX,S,ZV|0:25L)^#}},
IFE=DO{ZX'>2 P(R-1+ZX,S," ":25)^#,ZX+1^ZX}},1
- Replace the QUERY with the desired query mnemonic whose responses are
to default.
- Change the two >2's in the last two lines to the number of lines in
your multiple query.
- The two 25's in the last two lines should be changed to the length of
your query.
- You may replace the 1 at the end with "" to make the response default
and not be editable.
I hope this helps.
Thanks,
~Marie Kihm
Clinical Informatics Coordinator
CareTech Solutions, Inc.
Blanchard Valley Health System
1900 S. Main St., Findlay, OH 45840
Office: 419.423.5162
Fax: 419.423.5540
mk...@bvhealthsystem.org
"Whatever It Takes!"
CONFIDENTIALITY NOTICE: This message, including any attachments, is for
the sole use of the intended recipient(s) and may contain confidential
and privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient,
please contact the sender by reply e-mail and destroy all copies of the
original message.
Please consider the environment before printing this email.