Date post: | 24-Jul-2015 |
Category: |
Health & Medicine |
Upload: | informa-australia |
View: | 346 times |
Download: | 1 times |
Department of Health is a Smoke Free Workplace
eMM Plug and Play – Isn’t it?
Continuing business when
something goes wrong
Business continuity
2
Continuing business in the face of adversity
What do we need? Should this just be for eMM?
eMM Plug and Play – Isn’t it?
3
Continuing business in the face of adversity
Disaster recovery vs
high availability
What are your
recovery time
objectives – the time
to resumption of
service.
Hot swap vs warm
swap vs cold swap
What are your
recovery point
objectives - a
measurement of
tolerance for data
loss.
4
Other things to consider.
A separate backup
network
Allocating a separate
link for replicating
Allocating a proportion
of the bandwidth to
replication.
How to access the
DR solution when
switched over
2 different icons
Something smarter
What to replicate
Patient data?
Drug database?
What data do you need
to re-instate the
services
Testing failover – 6
months
How to switch to the
DR data
6
What do we do?
Utilise a real time
server mirroring
service.
Data is written
immediately to the
backup server for all
events
Not replicating server
OS
Use a VLAN for
syncing data
Manual remote
switching to DR.
Manual switching if no
network outside
hospital site.
Test every six months.
7
Monitoring
Use a 24/7 data
centre
On call server an
database
techs/administrators
User tolerance for
offline system is low
for eMM.
Patient care is
adversely affected by
system unavailability.
Users normally will be
in contact before the
data centre contacts
us.
9
Wireless network
issues
Wireless certificates
Domain controllers
Power failure
Communications loss
System/application
unavailable due to
fault
Application
maintenance
Upgrading application
Installing patches
Updates
Planned/unplanned downtime
10
Offline Chart capability
Ability to generate a
printed medication
chart.
These create a up-to-
date PDF of the
current chart.
Direct connection to
printer on essential
power
Used in unplanned
outages. If short time
period expected.
Remote sites with no
network connection back
to Darwin
11
Is this perfect?
Remote sites
Local copy of servers
and data
Automatic switching
when networks or
application fails
Automated switching
when application fails
Cloud capability
traditionally back-up to
the cloud
Run in the cloud and
back-up locally on
physical servers
12
Ongoing clinical
refinements:
How do you know what
to change?
Who decides on what
change is right?
What do you do across
multiple sites?
Drug updates and new
products - How much
time?
Rules/ warnings/
requests for new
functionality
New functionality and
versions
testing/configuring/valid
ating
Refinement
13
Drug updates and new products
Drug updates – testing/configuring/validating
How much time & what are we looking for?
Looking for removed products that are already in setup
quicklists/ordersets/protocols/picklists.
Adding new products
SAS, locally made/compounded, not included in drug database
Trial medications
Simple task (most of the time)
Add & Test across all environments (test/training/prod)
14
Configuration - what to change
How do you know what to change?
Clinical and application knowledge needed
Important to assess risk of current practice vs changed practice
Who decides on what change is right?
Governance is the key, representation from multiple disciplines
What do you do across multiple sites?
Rules/warnings/requests/new functionality