On-Site Bidder Solution Demonstration Requirements

During the On-Site Vendor Solution Demonstration, selected vendors will be invited to demonstrate the solution they are proposing to meet the OMH’s requirements for an EMR. Bidders will be required to address Functional Requirements from four scripted scenarios, set forth as Exhibit_1, during the presentation:

The scripts for the Vendor Solution Demonstrations are composed of a subset of requirements from the Exhibit 17 requirements and a set of expected Bidder and/or System responses. The scripted steps to follow for the four scenarios are set forth as:

• Exhibit 1_Scenario_Demo_Scripts.xlsx Background for the scripts is set forth as:

• Exhibit 1_Inpatient Scenario.doc • Exhibit 1_Laboratory Scenario.doc • Exhibit 1_Outpatient Scenario.doc • Exhibit 1_Pharmacy Scenario.doc

The scenario background documents describe the current business processes in place at a selected number of Facilities and ask the Bidder to demonstrate how their proposed solution will enable OMH to perform these processes in the proposed solution. The main categories of requirements within these scenarios are:

Inpatient Scenario:

A. Admission Referral Work and Data Flow B. Forms, Shells, Template Customization Process C. Alerts/Flags and Clinical Decision Support D. Inpatient Preadmission/Admission (Other)

F. Preadmission/Admission Process – SOMTA G. Treatment Planning

H. Scheduler (Inpatient Scheduling and Staff Scheduling) I. Progress Notes

J. Psychiatrist and medical specialist K. Nursing

L. Psychology & Social Work M. Nutrition N. Recreational/Rehabilitation Services O. Generic P. Leave/Transfer Q. Discharge R. Administrative S. Miscellaneous Laboratory Scenario: • ADT Process

• Ad Hoc reporting, e.g., a “To-Do” list of patients who have not had a required test • Link outside labs into VistA

• Link point of care device (e.g., glucometer) into VistA • Electronic Alerts to Medical Staff for critical lab values

Outpatient Scenario:

A. Preadmission/Admission Process B. Scheduler

C. Treatment Planning Documents D. Scripts

E. Service Recording F. Progress Notes G. Ongoing Treatment H. Discharge

I. Administrative and Reports J. Miscellaneous

Pharmacy:

A. Capability of system to ensure that the pharmacy obtains the patient’s demographic information from EMR

B. Computerized Physician Order Entry C. Processing Orders

D. Decision Support

E. Medication Monitoring F. Pharmacy Inventory Control G. Laboratory Data Migration/Flow H. Report Generation

I. E-Prescribing

J. Availability of Medications/Dose/Frequency in EMR

4.12.2.

User Interface

It is the intent of the OMH to use the CPRS or a CPRS ‘look alike’ as the base interface for the OMH VistA EMR product. A set of wireframes, based on existing VistA features, MHARS, and

assistance of staff at 3 OMH Facilities. These wireframes, which are set forth as Exhibits 2_1 through 2_13, while intended to demonstrate a potential look and feel for certain portions of the desired EMR functionality, are mainly included to represent information structure and do not represent actual screen designs. They include wireframes for:

• Chart Inquiries • Clinical Notes • Consults

• Discharge Summary Tab • EMR Main

• Lab Results • Meds • Orders

• Patient Summary • Problem List Tab • Treatment Plan • Vital Signs • Ward Journal

The Bid Proposal should specifically detail where the Contractor is proposing end user interfaces for the VistA GUI that are an improvement over the old style ‘roll and scroll’ interfaces present in many legacy systems.

4.13. ADDITIONAL REQUIREMENTS

4.13.1.

General

• The Contractor will develop a centralized server environment allowing for a single application with a single database with security to ensure that data is appropriately partitioned so facilities cannot access other Facilities’ data and that the integrity of data for each individual Facility is strictly maintained in accordance with HIPAA and HI-Tech provisions. Statewide user access will be LDAP compatible, and will be allowed within the necessary access groups and will not require a separate 'log on', user id or password/token process to gain access to multiple partitions. Access to the individual and specific database files will be limited to each Facility and a global access will be available to the OMH Central Office. The Contractor will ensure that VistA configuration and security model will meet the needs of OMH and maintain a secure environment and flexible access model. The Contractor will ensure that the system will operate within the OMH’s existing computer network environment to the fullest extent possible, complying with security, topology, and protocol requirements. To minimize costs, the utilization of existing computer and network hardware and software identified in Section 5 - Supporting Information is of paramount importance.

• The Contractor will provide future upgrades/updates to Contractor-provided Third Party Software for the life of the Contract and provide the necessary maintenance and support. • The Contractor will provide full installation and Implementation of VistA and

recommended third party applications once approved by the OMH.

• The Contractor will be responsible for maintaining VistA at its most current version and ensure that all customization/modifications and interfaces are compatible with the current version.

• The Contractor will work with the U.S. Department of Veterans Affairs (VA) FOIA office to ensure that future plans, software development, corrections and modifications are immediately available to the OMH upon release by the VA. The OMH also requires that the Contractor maintain its software migration plans to incorporate all technology upgrades consistent with migration and deployment of a web based product when it is available from the VA.

• The Contractor must configure a testing and development environment as well as a live production environment at the OMH’s Central Office that is fully licensed, fully functional, and operates independently, yet allows moving tested modules to the production environment without re-creation of coding changes in production.

• The Contractor must follow the OMH’s Change Management process to ensure new functionality is fully tested before it is moved to the production environment. A flowchart of this process and a Change Management Meeting protocol is located in Exhibit 12.

• The Contractor will provide recommendations to the OMH for technical solutions for load balancing and high availability, disaster recovery and data replication as part of the Infrastructure Architecture Design document (Deliverable 15). These solutions must have been previously implemented and the Contractor is required to prepare

documentation to support its current use and reliability.

4.13.2.

HL7 Compliant

The Contractor supplied solution must be capable of producing standard HL7 Messages. The Contractor must provide an explanation outlining their technical and procedural solution. The HL7 information may be found at the following link:

http://www.hl7.org/implement/standards/index.cfm

This information must be provided as part of the Technical Approach portion of the Bidder’s response.

5. Supporting Information