Appendix I Microbiology Downtime Document
Appendix I Microbiology Downtime Document
Appendix I Microbiology Downtime Document
Quality Manual
Section: LIS Downtime and System Maintenance
Prepared by: LIS Committee
Issued by: Laboratory Information System
Approved by: Laboratory Director
Policy QIMMI04011.04
Page 1 of 22
PURPOSE...........................................................................................................................................3
2.0 INTRODUCTION...................................................................................................................................3
3.0
DEFINITIONS....................................................................................................................................4
Policy QIMMI04011.03
Page 2 of 22
Department of Microbiology
UNIV ERSITY HEALTH NETWORK/MOUNT SINAI HOSPITAL, DEPARTMENT OF MICROBIOLOGY
NOTE: This is a CONTROLLED document. Any documents appearing in paper form that are not stamped in red "MASTER COPY" are not
controlled and should be checked against the document (titled as above) on the server prior to use
/var/www/apps/conversion/tmp/scratch_5/340454645.doc
Policy QIMMI04011.03
Page 3 of 22
2.0 Introduction
A downtime is any period of time when a computer information system is not available. This
includes scheduled downtimes (planned downtimes for system maintenance and upgrades)
and unscheduled downtimes (due to hardware/software failures).
The information systems at Mount Sinai Hospital are highly integrated. Interfaces exist
between the Hospital Information Systems (HIS) which are Cerner and Mysis-EPR, the
Laboratory Information System, SCC and the MDI Solutions and Courtyard Group Ltd.
interface engines. Downtimes can occur within Cerner, Mysis-EPR, one of the departmental
systems, or the interface between them. Downtimes in any of these areas likely to affect other
areas and the impact must be considered. Each area should have sufficient workarounds to
ensure continuity of services during a downtime.
An accurate record of all information related to a patients care must be maintained at all times.
In the event that a system is not available, information will be recorded manually on designated
forms. When the system becomes available, information captured manually will be entered
into the system in the recovery phase to ensure the retention of complete and accurate
information.
Policy QIMMI04011.03
Page 4 of 22
Procedures. The intended audience for User Downtime Procedures includes departmental
managers, application specialists and system users.
3.2 Communications/Escalation Plan
All notification of system failures must be made to the HP Customer Care Centre (Helpdesk) at
Extension 4357. Upon notification of a problem, HP will initiate the escalation plan to alert the
appropriate technical staff to respond to the problem, to update users, and to notify users when
the system is once again available. The Escalation Procedures include a predefined list of
messages for communication to users to ensure that they understand the impact and which
downtime procedure to implement.
The intended audience for the Escalation Procedures is the staff of the Customer Care Centre.
3.3 HP/Informatics Recovery Procedures
HP maintains a separate Disaster Recovery Plan to coordinate staff responsibilities in
responding to a system failure, and to provide the necessary information to speed the recovery
phase. This plan is triggered by notification of a failure via the Escalation Procedures, and
ends when the recovery team notifies the Customer Care Centre that the problem is resolved.
The intended audience for the HP Disaster Recovery Plan is HP and MSH Informatics staff.
3.4 Evaluation of the Downtime Procedure
An important part of downtime planning is evaluation of the event in downtime. Debriefing of
the event is important to evaluate the strengths and weaknesses of the procedure.
4.0 Definitions
4.1 Scheduled Downtime
Scheduled downtime is defined as a planned period of time when the system is unavailable for
use. These are scheduled during a time when the system usage is low to minimize impact on
end users. The established downtime window for all clinical applications may commence
23:30 hrs on the third Wednesday of the month until the 03:30 hrs of the third Thursday of the
month as approved by the Technical Advisory Board (TAB) and the Change Advisory Board
(CAB). Scheduled downtimes are used for updating the sytem with new hardware/software
releases, fixes, or enhancements. User Downtime Procedures for scheduled downtimes are
essentially the same as for unscheduled downtimes, but may involve some preparation before
the downtime that could not be done if the downtime were not expected ahead of time.
4.2 Unscheduled Downtime
Unplanned failures caused by power failures, software problems, or hardware problems.
4.3 HP
Shared Information Management Services (SIMS) provides technical support for Mount Sinai
Hospital and the University Health Network (UHN).
UNIV ERSITY HEALTH NETWORK/MOUNT SINAI HOSPITAL, DEPARTMENT OF MICROBIOLOGY
NOTE: This is a CONTROLLED document. Any documents appearing in paper form that are not stamped in red "MASTER COPY" are not
controlled and should be checked against the document (titled as above) on the server prior to use
/var/www/apps/conversion/tmp/scratch_5/340454645.doc
Policy QIMMI04011.03
Page 5 of 22
HIS
(MysisEPR
Cerner or
Meditech)
Healthlink
Interface
engine
HIS order
entry
(MysisEPR,
Cerner or
Meditech)
HIS ADT
(Cerner or
MysisEPR)
HIS
results
reporting
(Cerner,
MysisEPR or
Meditech)
F
LIS
Policy QIMMI04011.03
Page 6 of 22
Stage
Time period
1
2
System
A
Mysis-EPR
order/acce
ssioned by
SMC or
Cerner and
Meditech
order recd
AA1
AA1
B
HIS order
no SMC
accessio
n or
Cerner or
Meditech
order not
received
AB1
AB2
C
Results
reporting
AC1
AC1
3
4
After 24 hours
AA1
Policy QIMMI04011.03
Page 7 of 22
AB3
AC2
AA1 For Mysis-EPR, the downtime occurred between accessioning by SMC and the arrival of
specimens in the microbiology lab. For Cerner, downtime occurred after the order was placed
but the specimen has not been received in the lab. For Meditech, the downtime occurred after
the batch transmission was sent but the specimen has not arrived by courier.
The specimens are received as usual in the LIS.
5.5.2 AB Mysis-EPR order that has not been accessioned by SMC. Meditech order that
was not transmitted. A stat Cerner order that must be ordered and collected
manually.
The Mysis-EPR downtime occurred between specimen collection and the arrival of the
specimens at SMC. The Meditech downtime occurred after the order was placed and
specimen collected but prior to the batch transmission for Meditech. A stat Cerner specimen
would be sent with a requisition.
AB1 Immediately
All un-accessioned specimens from Ulitcare are sent to the Microbiology Lab. The specimens
are held refrigerated for up to one hour. No other action is taken.
All non-transmitted specimens from Meditech are held by the facilities until the system is back
up. The stat Cerner specimen would be entered manually into the LIS and follow the
procedures under AB3.
AB2 After 1 hour
Mysis-EPR only:
1. Blood cultures: keep a list of specimens with patient name, MRN, HIS number and bottle
ID. Incubate off line in incubator. If the HIS is not back up, one hour before the lab closes,
load bottles in the Bact/Alert by scanning the bottle ID.
2. All other specimens: use the HIS specimen number for labeling plates and smears during
planting. Save the specimens in a separate basket for recovery.
3. Specimens that arrive with requisitions with complete patient information (MRN and visit #),
generate the order in the LIS.
UNIV ERSITY HEALTH NETWORK/MOUNT SINAI HOSPITAL, DEPARTMENT OF MICROBIOLOGY
NOTE: This is a CONTROLLED document. Any documents appearing in paper form that are not stamped in red "MASTER COPY" are not
controlled and should be checked against the document (titled as above) on the server prior to use
/var/www/apps/conversion/tmp/scratch_5/340454645.doc
Policy QIMMI04011.03
Page 8 of 22
4. Specimens that arrive with requisitions with incomplete patient information, use an internal
numbering system. Place the internal lab number on the requisition and plant the
specimens.
Policy QIMMI04011.03
Page 9 of 22
5.6.2 AB Mysis-EPR order that has not been accessioned by SMC. Meditech order that
was not transmitted and a stat Cerner order that must be ordered and collected
manually.
AB1 Immediately
Take specimens from storage, receive in LIS and plant as usual. Specimens will arrive from
Rouge valley and a batch transmission will have been sent.
Policy QIMMI04011.03
Page 10 of 22
Policy QIMMI04011.03
Page 11 of 22
Stage
1
2
3
4
Time period
System
A
HIS
orders
Less than 1
hour
After 1 hour
After 24 hours
B
Results
reportin
g
BA1
BB1
BA2
BA2
BB1
BB2
Policy QIMMI04011.03
Page 12 of 22
No change. Call Stat and critical results and force print important results to fax, print or deliver
at the technologists discretion.
Policy QIMMI04011.03
Page 13 of 22
Stage
1
2
3
4
Time period
System
Immediate
After 1 hour
A
Order
entry
CA1
CA2
Policy QIMMI04011.03
Page 14 of 22
Policy QIMMI04011.03
Page 15 of 22
Time period
System
Immediate
After 1 hour
A
ADT
DA1
DA2
Policy QIMMI04011.03
Page 16 of 22
Policy QIMMI04011.03
Page 17 of 22
Stage
1
2
3
4
Time period
System
Immediate
After 24 hour
A
Order
entry
EA1
EA2
Policy QIMMI04011.03
Page 18 of 22
No change. Call Stat and critical results and force print important results to fax, print or deliver
at the technologists discretion.
Policy QIMMI04011.03
Page 19 of 22
Time period
System
Immediate
After 1 hour
After 5 hours
A
Order
entry
FA1
FA2
FA3
B
Results
reportin
g
FB1
FB2
FB3
Policy QIMMI04011.03
Page 20 of 22
FB1 Immediately
No action is taken. All Stats and critical results are phoned and documented.
FB2 After 1 hour
UNIV ERSITY HEALTH NETWORK/MOUNT SINAI HOSPITAL, DEPARTMENT OF MICROBIOLOGY
NOTE: This is a CONTROLLED document. Any documents appearing in paper form that are not stamped in red "MASTER COPY" are not
controlled and should be checked against the document (titled as above) on the server prior to use
/var/www/apps/conversion/tmp/scratch_5/340454645.doc
Policy QIMMI04011.03
Page 21 of 22
1. All technologists will be issued blank requisitions which will be numbered from the plates as
they are read.
2. All observations and test results will be written on the backs of the requistions.
3. All Stats and critical results will be phoned and documented.
Once the auxiliary system is functioning, all results can be entered into the LIS.
The results documented on requisitions will have to be re-entered into the LIS.
Results that file back to the HIS(S) will be automatically sent out.
The LIS officer(s) will manually print other print runs for distribution of reports to the wards.
During the switch back to the main system, all necessary observations, test results and
phoned results will need to be recorded again on paper.
Policy QIMMI04011.03
Page 22 of 22