What about micro, bloodbank and pathology results as well as the summary
reports?

 

Babette Thomas

LIS Coordinator

Delnor-Community Hospital

[EMAIL PROTECTED]

630-208-4205

________________________________

From: meditech-l@mtusers.com [mailto:[EMAIL PROTECTED] On Behalf
Of Tommy Finley
Sent: Tuesday, June 05, 2007 7:03 AM
To: meditech-l@mtusers.com
Subject: [MEDITECH-L] FW: Joint Commission and Report Date&Time

 

>From my Lab Director as a followup post from last week.  Thanks for all
of the responses and for those interested she has detailed a JCAHO
clarification below

 

Tommy Finley, CIO

Rutherford Hospital

288 S Ridgecrest Ave.

Rutherfordton, NC  28139

828-286-5529

________________________________

From: Lynn Reinhardt 
Sent: Tuesday, June 05, 2007 7:59 AM
To: Tommy Finley
Subject: Joint Commission and Report Date&Time

 

Tommy,

Can you forward the following message to the Meditech-L list so everyone
can have the benefit of the answers received and clarification from
Joint Commission.

>From the variety of answers I got , a lot of labs are interpreting this
differently....thanks.....Lynn

************************************************************************
*****************

 

Thanks to everyone who responded to my request for help with Joint
Commission and their standard requiring report date/time on the printed
report.

>From the variety of responses I got back, I can see that everyone has
been interpreting this differently, and solving it in different ways.
Many are

using the report run date and time which didn't fly when we asked Joint
Commission about that and the internal audit trail.

 

No, the time of printing is not what they were getting at...they want
the time the result is externally available and explained as the time of
report completion, either final or preliminary.  The problem with the
RUN DATE/TIME is that it isn't static.  It changes every time a report
prints.  We tried to use the internal audit trail as evidence, and they
said that was acceptable to show test level detail, but that the printed
report itself needed the reported date/time on it showing preliminary or
final completion.  From what they provided, translated to Meditech, this
is the date that a specimen goes to COMP status because at that point
the results are externally available electronically even if the report
itself prints later (and that opens a whole other can of worms of
electronic availability vs paper report).  Here is the clarification the
Joint Commission Standards group sent to me....

 

"The intent of the EP is for the date and time of reporting to be
physically present on the charted report. This means each laboratory
report should have a single date and time of reporting, which reflects
the time that report (preliminary or final) was released for use by a
healthcare provider It is not the intent of the requirement to have the
individual date and time printed for each analyte. Thus, Joint
Commission will accept a single date and time of reporting printed on
the report, either the preliminary or the finalized date and time. Then,
if your organization can track the individual dates and times for each
analyte in the LIS, that is sufficient for the audit trail."

 

Tony Frith of the Meditech-L list and finally, Meditech provided the
following Knowledge Based article that allowed us to capture the
date/time the last test on a specimen is verified, causing the specimen
to go to COMP status.  It now prints on the first printing of the report
and no matter how many times the report "reprints," it's still that same
date and time which is what Joint Commission wants.

 

Meditech solution 5/31/07:

Article ID: 23428
Date: 1/4/2006
Published: 1/9/2006

Application: LAB
Subject: Report Writer
Platform: ALL

LAB.L.SPEC: Printing the Most Recent Verify Date and Time 

A number of different tests can be performed on one specimen, to print
the verified date and time of the last test which was verified for a
completed specimen, you can use the following fields.  Please note that
the computed field xx.ver.date loops through tests which means that you
do not want your detail segment to be the tests segment or any child
segment of the tests segment or this code could produce an infinite
loop.  This code was used in a report which used the main
(lab.l.specimen.file) segment as the detail segment.

xx.ver.date:

[EMAIL PROTECTED]"COMP" ""^VTM^test,
[EMAIL PROTECTED](test) [EMAIL PROTECTED],
VAL=%Z.date.in.magic([EMAIL PROTECTED])}

xx.ver.time
VAL=%Z.time.out([EMAIL PROTECTED])

The xx.ver.date field will loop through the tests and perform a maximum
on the verify time field to produce the most recent verify time.  This
value is then used to produce the output.  

 

 

thanks

Lynn Reinhardt, MT(ASCP)

Laboratory Manager

Rutherford Hospital, Inc.

Rutherfordton, NC

[EMAIL PROTECTED]

 

 

________________________________



----- Confidentiality Notice -----
This e-mail and any attached documents contain confidential
information belonging to the sending entity, Rutherford Hospital,
Inc, and is intended only for the use of the individual(s) or
entity(s) associated with the recipient addresses listed in the
message header. The authorized recipient of this information is
prohibited from disclosing this information to any other party. If
you are not the intended recipient, you are hereby notified that
any disclosure, copying, distribution or action taken in reliance
on the contents of the email and/or attachments is strictly
prohibited. If you received this e-mail transmission in error,
please notify the sender immediately to arrange for return or
destruction of this information. To report abuse or inappropriate
use, please email [EMAIL PROTECTED]


=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
To subscribe or unsubscribe to the meditech-l, visit MTUsers.NET.

To check the status of the meditech-l, visit MTUsers.NET.

For help, email [EMAIL PROTECTED]

Visit the MTUsers WikiPedia at MTUsers.NET/mwiki
______________________________________
meditech-l mailing list
meditech-l@MTUsers.com
http://mtusers.com/mailman/listinfo/meditech-l

Reply via email to