Download Single or Multiple Databases in MediMizer

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Transcript
Single or Multiple Databases in MediMizer
Two DB or Not Two DB?
If you are converting from another product and have multiple accounts planning to use
MediMizer (such as biomedical engineering, facilities, maintenance, IT, fire safety, or
security – or maybe different sites or customers), you will want to consider whether to
put all data in a single MediMizer database or use multiple databases with a single copy
of MediMizer.
Each database is completely separate and isolated from the others – so it can have
different personnel, different Work Orders, different Equipment, different Equipment
Types and Model information, and different inspection schedules and procedures. If your
departments work fairly separately and independently, you may want to have them use
separate databases.
If your departments tend to work together very closely, often sharing personnel and
equipment, you may want to put all accounts into a single database. Each Account will
be shown as a separate Facility in MediMizer.
This document shows how one hypothetical company, Central City Health Care, might
have organized their data originally in another software when they upgraded to
MediMizer X3. In each section, there is a screenshot that shows how the data would look
with a single database. Then there is a separate screenshot for how it would look if it
were split into separate databases for each account.
The data shown is based on an actual MediMizer X3 user coming from Sentinel and
using MediMizer successfully.
Both approaches have been used successfully by a variety of companies. Which
approach is better for you depends on how your organization is structured and what your
requirements are.
Please feel free to contact us to discuss the benefits and tradeoffs of each approach and
how we can address your company’s needs.
Single or Multiple Databases in MediMizer.doc 081809 JC
Page 1 of 7
Single or Multiple Databases in MediMizer
Login Screen
Accounts in one Database, Separate Facilities
Accounts in Separate Databases
Single or Multiple Databases in MediMizer.doc 081809 JC
Page 2 of 7
Single or Multiple Databases in MediMizer
Facility List
Accounts in one Database, Separate Facilities
Accounts in Separate Databases
Single or Multiple Databases in MediMizer.doc 081809 JC
Page 3 of 7
Single or Multiple Databases in MediMizer
Department List
Accounts in one Database, Separate Facilities
Accounts in Separate Databases
Single or Multiple Databases in MediMizer.doc 081809 JC
Page 4 of 7
Single or Multiple Databases in MediMizer
Equipment List
Accounts in one Database, Separate Facilities
Accounts in Separate Databases
Single or Multiple Databases in MediMizer.doc 081809 JC
Page 5 of 7
Single or Multiple Databases in MediMizer
Work Order List
Accounts in one Database, Separate Facilities
Accounts in Separate Databases
Single or Multiple Databases in MediMizer.doc 081809 JC
Page 6 of 7
Single or Multiple Databases in MediMizer
Benefits of Each Approach
Single Database
+ Report on all equipment or all works
orders together
+ Use filters to report on each
department’s data separately
+ Uniform Service Codes, Cause Codes,
etc. across departments
+
+
+
Employees can easily work on data in
other departments without having to
login again
If single piece of equipment is serviced
by multiple departments, anyone can
see complete cross-department history
of the equipment
Slightly lower initial system cost
+
Slightly lower annual support cost in
some cases.
+
Can later split database into multiple
databases if needed
Multiple Databases
+ Users can only see data that applies
to their department
+ Report on each department’s data
separately
+ Can run created scheduled work
orders for following month at
different times
+ Can have different Service Codes and
standards
+
Users only see data that applies to
their department: needed equipment
types, models, etc.
+
Performance for a large system
might be faster because of smaller
tables in each database
If departments used the same
equipment control number or work
order number in their previous
systems, these numbers can be
retained in MediMizer
+
Not Sure?
Not sure whether to have your databases together or separate? It is more difficult to recombine databases once they have been split. So if you are in doubt, start with all your
data in a single database.
But if you are two separate operations, such as biomedical and facilities, it is suggested
you separate data to allow completely separate settings and policies.
If your separation is only sites or clinics managed by the same group of people, it is likely
you want them together in one database.
Single or Multiple Databases in MediMizer.doc 081809 JC
Page 7 of 7