Medsphere's Enterprise Assessment process determines each hospital's unique requirements and presents alternatives for meeting those goals. Our collaborative approach answers questions about hosting, server virtualization and other issues before an implementation plan commences.
Hardware and Operating System
A client/server solution, OpenVista runs effectively on a single Linux or Windows server, even in large hospitals. Workstation requirements are modest, enabling many OpenVista client sites to save money by using existing Windows workstations.
OpenVista requires either InterSystems Caché (Linux or Windows) or FIS GT.M (Linux only) database management systems. Caché is a commercial product that supports some of the largest hospitals and EHR implementations in the USA. GT.M is an open source product with professional support that runs both hospitals and some of the largest banking systems in the world. Caché and GT.M each have a long track record of exceptional reliability and performance in healthcare scenarios.
OpenVista's extensive library of reports addresses common client needs. OpenVista FileMan offers power users and IT personnel access to EHR data through a flexible user interface.
The bandwidth requirements for OpenVista client operations are modest. A reliable DSL or cable connection is adequate for a small satellite clinic; to accommodate more users and interfaces, a larger site, such as a hospital, will require more bandwidth.
Availability, Recovery, Data Assurance
OpenVista provides the range of backup, replication and recovery options a healthcare organization needs to comply with HITECH and meet or exceed expectations for availability and recoverability. OpenVista can quickly recover data from full backups or from journals (i.e., transaction logs). OpenVista supports log-shipping and real-time replication to a second server or site and can be deployed in a cluster configuration for high availability.
Medsphere works with clients to determine availability, backup and disaster recovery options that fit requirements and budget.
OpenVista supports the three primary components of HIPAA security compliance: administrative, physical and technical.
- Access Controls: OpenVista requires adherence to strict user identification (username and password) rules through several approaches--passwords are only valid for a fixed number of days, previously-used passwords cannot be reused, strong passwords are enforced, etc.--that can be managed by systems administrators. After a pre-determined amount of inactive time, users are given a warning window and then automatically logged off. OpenVista is also customizable according to a given site's requirements for emergency access.
- Audit Controls: OpenVista tracks all sign-on activity, whether successful or unsuccessful, and allows the system manager to track users who access specific options. At the database level, any field in any file can be audited for changes; the user's identification, previous field value, and time-of-change are captured. Also, OpenVista can be set up so that there is an ongoing audit of every user who merely looks at a patient record.
- Integrity: OpenVista can require electronic signatures for a form or document before any information can be changed, added to or otherwise altered. In conjunction with a user ID, OpenVista can "lock" a terminal device after several successive unsuccessful sign on attempts to insure that unauthorized users cannot log in.