Positives Negatives

Do Nothing •
•
No Cost to EHR project
Less technical resources/training required
• No Standardization of processes and
documentation
• Existing systems are technically feasible to • Uniqueness
be continued • Maintenance of paper records
• Reduced Cost of IT • Lack of efficiency and delay in services
• Greater chances of medical errors
• Absence of new technology
• Eventual project cost of legacy system
migration (newer version or Commercial HIS)
• Retention of existing software staff
• Migrate Care2000 to In-house modules when
Care2000 converts to Care2005

A Package • Standardization of processes and

documentation
• Gaps in functionality of Departmental
modules
• One system across AKU
• Meeting full scope of work - business MEDITECH
needs • Relatively closed Architecture
• Minimal technical resources requirement • Limited Customization
• Additional cost for non-usable
MEDITECH modules
• Closest to existing AKU
requirements EPIC
EPIC • Very High capital and operational Cost
• Top of the line solution
• Facilitation for research
• Enhanced Productivity (Workflows)

A Portal •
•
Instant Benefit
Less immediate capital and operational
• Migration of Care 2000 to In-house
developed modules
cost • Eventual project cost of legacy system
migration
ORION • Integration effort
• High level of flexible customization
and business rule options ORION
ALERT • Create functionality and templates
• User Interface supports touchscreen • Eventual Standardization
ALERT
• Partial Solution
 Positives Negatives
Do Nothing • Already trained IT resources to support
existing applications
•
•
Support Cost of legacy systems for ever
Care2000 Support – Vendor Dependence
• Prompt Support for in-house developed • Conversion of Care2000 to In-house modules
modules – No Vendor Dependence

A Package • Support of Legacy Systems will only be

required for next four years
MEDITECH
• Complete Vendor dependence for
• Less requirement for technical resources technical issues
• No customization • Two different platforms and Multiple
• High performance reporting tools
• Quality of staff in MEDITECH South Africa
MEDITECH office
• Experience of MAGIC
EPIC
EPIC • High yearly maintenance cost
• Advanced programming and
technical training for IT staff
• High staff-to-client ratio

A Portal • Administrator and Technical Training for IT

staff
•
•
Integration Support
Support legacy systems till its migration
• Dependence on AKU and Vendor technical
ORION resources
• Highly Customizable • IBM Dependence
• Best Integration Engine • More software staff requirements

ALERT ORION
• Ease of use • Enhancement requests in new EHR
modules

ALERT
• Limited/No Customization
 Positives Negatives

Do Nothing • Our Practices • No Standardization of processes and

documentation
• We can not hire support staff

A Package • Standardization of processes and

documentation

A Portal • Easy to adopt new practices • Eventual Standardization

ORION ORION
• Adoption of practices based on • Clinical Decision Support is not
input from AKU users extensive

ALERT ALERT
• Clinical Decision Support • None
• Clinical Workflow mechanisms
 Positives Negatives
Do Nothing • User are accustomed /satisfied with legacy
systems
• We would have raised user dissatisfaction by
creating expectations and giving them
• No Change Management required demonstrations

• Limitations due to old technology (Eventual

conversion to latest Microsoft product)

A Package • All modules on single platform will reduce

complexity of architecture and back-and-
• Un-Comfortable for users to replace legacy
systems in the next four years
forth of data
• Lack of acceptance and satisfaction amongst
MEDITECH users
• Closest to old Magic System
• Physical Presence of vendor staff MEDITECH
• No flexibility in their offering • Old and proprietary technology
• Implementation Sequence
EPIC
• Suits large academic hospitals
EPIC
• Difficult to learn and adopt
• Remote Implementation

A Portal • No replacement, just adding new module

will involve less risk
• Acceptance of AKU In-house modules in EA will
be a big challenge
• Web-based solution • Eventual replacement of legacy system

ORION ORION
• No Change Management required • More user Involvement required during
• Provision of Customization implementation phase
• More acceptability
ALERT
ALERT • Partial Solution
• Ease of use
• Physical presence of vendor
implementation team